<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5655" class=""><span id="yiv2415871091yui_3_16_0_1_1445522215842_6052" style="font-family: 'Courier New'; white-space: pre-wrap;" class="">Hi Michale,</span></div><div dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5655" class=""><span style="font-family: 'Courier New'; white-space: pre-wrap;" id="yui_3_16_0_1_1445522215842_8052" class=""><br clear="none" id="yui_3_16_0_1_1445522215842_8054" class=""></span></div><div dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5655" class=""><span id="yiv2415871091yui_3_16_0_1_1445522215842_6053" style="font-family: 'Courier New'; white-space: pre-wrap;" class="">- I use SIP INFO since I need to bypass media (no RTP stream for local calls).</span></div><div dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5655" class=""><span id="yiv2415871091yui_3_16_0_1_1445522215842_6054" style="font-family: 'Courier New'; white-space: pre-wrap;" class="">- I reported it to both vendors. Gigaset say they are compliant with many PBX vendors, so they don't need to change it. Yealink should answer soon. </span></div><div dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5655" class=""><span style="font-family: 'Courier New'; white-space: pre-wrap;" id="yui_3_16_0_1_1445522215842_8061" class=""><br clear="none" id="yui_3_16_0_1_1445522215842_8063" class=""></span></div><div dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5655" class=""><span id="yiv2415871091yui_3_16_0_1_1445522215842_6055" style="font-family: 'Courier New'; white-space: pre-wrap;" class="">Anyway Gigaset IP Cordless are good and cheap, so many customers would like to use them, that's why I'm asking the patch.</span></div><div dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5655" class=""><span style="font-family: 'Courier New'; white-space: pre-wrap;" id="yui_3_16_0_1_1445522215842_8068" class=""><br clear="none" id="yui_3_16_0_1_1445522215842_8070" class=""></span></div><div dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5655" class=""><span style="font-family: 'Courier New'; white-space: pre-wrap;" id="yui_3_16_0_1_1445522215842_8073" class="">Thank you. </span></div><div dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5655" class=""><span style="font-family: 'Courier New'; white-space: pre-wrap;" id="yui_3_16_0_1_1445522215842_8076" class=""><br clear="none" id="yui_3_16_0_1_1445522215842_8078" class=""></span></div><div dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5655" class=""><span style="font-family: 'Courier New'; white-space: pre-wrap;" id="yui_3_16_0_1_1445522215842_8081" class=""><br clear="none" id="yui_3_16_0_1_1445522215842_8083" class=""></span></div><div dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5655" class=""><span id="yiv2415871091yui_3_16_0_1_1445522215842_6056" style="font-family: 'Courier New'; white-space: pre-wrap;" class="">>I don't think it exists. It might be possible to add one and we would</span><br clear="none" id="yui_3_16_0_1_1445522215842_8087" class=""></div><div class="" dir="ltr" id="yiv2415871091yui_3_16_0_1_1445522215842_5798"><pre class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5819">>probably review that patch, but why wouldn't you just use rfc2833 instead
>and/or report this error to the vendors?
>
>>On Thursday, October 22, 2015, Chris B. Ware <<a rel="nofollow" shape="rect" class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5821" target="_blank" href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" style="color: rgb(25, 106, 212);">chrisbware at yahoo.it</a>> wrote:
>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5823"> Hi guys,
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5825">
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5827"> I've discovered that Gigatset and Yealink IP cordless send SIP INFO in a
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5829"> wrong way, according to SDP RFC.
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5831"> If I press 4, I get on SDP
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5833">
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5835"> Signal=4\r\n
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5837"> Duration=100
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5839">
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5841"> While should be
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5843">
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5845"> Signal=4\r\n
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5847"> Duration=100\r\n
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5849">
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5851">
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5853"> Freeswitch (1.4.23) answers with 400 Bad Request. I wonder if there's
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5855"> something like a NDLB params to accept this format, based on SDP Content
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5857"> Length.
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5859">
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5861">
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5863"> Thank you
</i>>><i class="" id="yiv2415871091yui_3_16_0_1_1445522215842_5865">
</i>>></pre></div></div></body></html>