[VoiceOps] Broadworks media server not playing well with early media

Scott Berkman scott at sberkman.net
Tue Apr 24 17:00:38 EDT 2012

What is on the network side?


I don't believe BroadSoft allows for multiple 18X responses, and in my
opinion no system should.  Once you have sent an offer, the only way to
modify it should be a RE-INVITE.  I believe the RFC's do technically allow
for this though, and in that case the newer 18X message will
override/replace the previous.


Another issue may be that 183 messages usually are accompanied with SDP,
where 180 message are used when no early media (and therefore no SDP) is to
be used.  So a second 183 with no SDP is all kinds of wrong to me.


Hope that helps,




From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of John Myhre
Sent: Monday, April 23, 2012 4:19 PM
To: voiceops at voiceops.org
Subject: [VoiceOps] Broadworks media server not playing well with early


I seem to be having a problem with Broadworks thinking an early media stream
has ended.


I'm sending a call out to the PSTN and receiving back a 183 with SDP
(presumably early media).  Broadworks is dutifully passing everything down
to the device.


I'm then receiving a second 183, this time with no SDP (presumably because
someone's gateway received a CPG).  In this case, Broadworks appears to
interpret the lack of SDP as meaning the early media has ended (not the
case) and plumbs the media server into the bearer path to play ringing.  


Anyone run into this problem?  Any ideas for a way around it?  


I've found a reference for dealing with this problem from the access side,
but not when the 183s are coming from the network side.


I'm running Broadworks Rel14sp4.


Many thanks for any ideas!



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20120424/5075411e/attachment.html>

More information about the VoiceOps mailing list