<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I am attempting to setup FS as an B2BUA SBC between a telco platform and a telco SIP trunk. Everything is fine except for one call-flow scenario: <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We need to sometimes “reject” calls by sending reason code 17, which is quite easy by sending a SIP 486. The issue is that the far-end first receives early media and then the reason code 17, and the far-end switch is bonding the B-leg media for 55 seconds instead of moving on in the dial-plan. When comparing this to our PRI build-out, the difference is that in the PRI-buildout, no early-media is sent. In the SIP world, we are sending a 183 with SDP to setup the early media… <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If I don’t send early media, the telco will inject their own early media path… so I need a work-around.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The telco is asking that we send specifically a 183 WITHOUT SDP, which I am having trouble figuring out how to do. I know how to send the 180 WITHOUT SDP, a 183 WITH SDP, but I cannot find the solution to sending 183 WITHOUT SDP…<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I know it is unusual to send 183 without SDP, but it is still RFC compliant…<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thoughts?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Matthew Meek<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>