I don&#39;t think it exists.  It might be possible to add one and we would probably review that patch, but why wouldn&#39;t you just use rfc2833 instead and/or report this error to the vendors?<span></span><br><br>On Thursday, October 22, 2015, Chris B. Ware &lt;<a href="mailto:chrisbware@yahoo.it">chrisbware@yahoo.it</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="color:#000;background-color:#fff;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:13px"><div>Hi guys,</div><div><br></div><div dir="ltr">I&#39;ve discovered that Gigatset and Yealink IP cordless send SIP INFO in a wrong way, according to SDP RFC.</div><div dir="ltr">If I press 4, I get on SDP</div><div dir="ltr"><br></div>Signal=4\r\n<br>
Duration=100<br>
<br>
While should be<br>
<br>
Signal=4\r\n<br><div dir="ltr">Duration=100\r\n</div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">Freeswitch (1.4.23) answers with 400 Bad Request. I wonder if there&#39;s something like a NDLB params to accept this format, based on SDP Content <font face="monospace">Length.</font></div><div dir="ltr"><font face="monospace"><br></font></div><div dir="ltr"><font face="monospace"><br></font></div><div dir="ltr"><font face="monospace">Thank you</font></div><div dir="ltr"><br></div><div dir="ltr"> </div><div dir="ltr"><br></div></div></div></blockquote>