<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Switch to TCP or TLS instead of UDP.<div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 14, 2021, at 8:33 PM, nycphoneservice <<a href="mailto:nycphoneservice@gmail.com" class="">nycphoneservice@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Looks like you have an issue with packet fragmentation.</div><div class="">I had a similar issue with grandstream a few years back due to ISP improperly handling fragmentation.</div><div class="">
<pre class="gmail-aLF-aPX-K0-aPE">send 1509 bytes to udp/[34.210.91.114]:5060 at 15:59:12.585438:
------------------------------------------------------------------------
</pre></div><div class="">Your packet size is 1509 bytes which is more than standard 1500, thus it may be an fragmentation issue @ your router or further down the line.</div><div class="">That's why you don't get replies to the invite - flowroute don't get a complete request and just ignores it.</div><div class="">I would disable these to prove the point (will make a packet < 1500 for sure):</div><div class="">
<pre class="gmail-aLF-aPX-K0-aPE">disable P-Access-Network-Info
disable P-Emergency-Info
<br class=""></pre><pre class="gmail-aLF-aPX-K0-aPE">Also, I would disable alert-info because I've seen some carriers reject the invite with this header.<br class="">
</pre>
</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 14, 2021 at 9:20 PM Steven Schoch <<a href="mailto:schoch%2Bfreeswitch.org@xwin32.com" class="">schoch+freeswitch.org@xwin32.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class="">The sip trace is attached.<div class="">It seems to show that it sends INVITE messages, but never gets a response.</div><div class="">However, when it sends an OPTIONS message, it does get a response.</div><div class="">When calling from a different extension (using a Polycom instead of a Grandstream ATA), the INVITE gets answered and the call proceeds.</div><div class=""><br class=""></div><div class="">It seems that there is something "wrong" with this INVITE that makes Flowroute ignore it. What could that be, and how do I fix it?</div><div class=""><br class=""></div><div class="">I may have enough data here to ask Flowroute directly, so I'm going to give that a try as well.</div><div class=""><br class=""></div><div class="">-- </div><div class="">Steve</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 14, 2021 at 12:43 PM Brian West <<a href="mailto:brian@freeswitch.com" target="_blank" class="">brian@freeswitch.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class="">That's the FMTP for OPUS. Chances are that invite breaks the Polycom, what does the SDP look like coming back from that invite? I'll be you, it's broken.<div class=""><br class=""></div><div class="">/b</div><div class=""><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 14, 2021 at 1:51 PM Bote Man <<a href="mailto:botelist@gmail.com" target="_blank" class="">botelist@gmail.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US" class=""><div class=""><p class="MsoNormal">I am absolutely no expert on SDP, but that SDP line that begins<u class=""></u><u class=""></u></p><p class="MsoNormal">a=fmtp:102 useinbandfec=1…<u class=""></u><u class=""></u></p><p class="MsoNormal">looks to me like it’s trying to set up a video call. I saw this behavior with the newer Polycom VVX501 before I beat those eager beavers into submission.<u class=""></u><u class=""></u></p><p class="MsoNormal"><br class="">It also looks like the Grandstream is offering a lot more codecs which you might prefer to trim down to only those necessary to get the job done. Sometimes additional codecs or codecs listed in the “wrong” sequence can cause mystery problems.<u class=""></u><u class=""></u></p><p class="MsoNormal"><u class=""></u> <u class=""></u></p><p class="MsoNormal">You might have to resort to siptrace logging between FS and your carrier.<u class=""></u><u class=""></u></p><p class="MsoNormal">sofia profile external siptrace on <span style="font-family:Wingdings" class="">ç</span> or whatever profile handles your provider; or maybe internal to snoop what’s going on between FS and your Grandstream.<u class=""></u><u class=""></u></p><p class="MsoNormal"><u class=""></u> <u class=""></u></p><p class="MsoNormal">Hope this helps.<u class=""></u><u class=""></u></p><p class="MsoNormal"><u class=""></u> <u class=""></u></p><p class="MsoNormal"><u class=""></u></p></div></div></blockquote></div></blockquote></div></blockquote></div></div></blockquote></div><br class=""></div></body></html>