<p dir="ltr">They are not following Rfc.<br>
There's nothing you can't do on ngcp.<br>
They must fix it on their side.</p>
<p dir="ltr">Daniel<br>
</p>
<div class="gmail_quote">On 7 Mar 2015 14:25, stefanormc <stefanormc@gmail.com> wrote:<br type='attribution'><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">hi<div><br /></div><div>I tried the audiocode workaround but got the same result</div><div><br /></div><div>audio in and out working ok for 30 sec while getting</div><div><br /></div><div><div style="margin:0px;font-size:11px;font-family:'menlo'">Mar 7 14:19:46 centrale proxy[30917]: NOTICE: <script>: Dropping mis-routed request - R=sip:192.168.2.2:5080;prxroute=1 <a href="mailto:ID=03852-RX-012acaf4-213165de5@voip.digitelitalia.it">ID=03852-RX-012acaf4-213165de5@voip.digitelitalia.it</a></div></div><div><br /></div><div><br /></div><div>Disappointingly I still haven’t got a reply from cirpak/digitel</div><div><br /></div><div>thanks</div><div><br /></div><div>stefano</div><div><br /></div><div><br /></div><div><br /></div><div><br /><div><blockquote><div>On 24 Feb 2015, at 17:25, Daniel Grotti <<a href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a>> wrote:</div><br /><div>Well,<br />I would ask for, I mean that's a Cirpack issue, which are not following<br />RFC here.<br /><br />Daniel<br /><br /><br />On 02/24/2015 05:07 PM, Daniel Grotti wrote:<br /><blockquote>This is out of SIP RFC, but I saw this problem before.<br />You can ask them why they are not setting, probably they can reply that<br />they do not like the 127.0.0.1 in the Via/Record-route headers.<br /><br />If this is the issue, please follow this:<br /><a href="https://www.sipwise.com/doc/mr3.7.1/spce/ar01s05.html#_audiocodes_devices_workaround">https://www.sipwise.com/doc/mr3.7.1/spce/ar01s05.html#_audiocodes_devices_workaround</a><br /><br /><br />some softswitches, like Audiocodes have issue with that.<br />Don't know if Circpack has the same, probably. But please ask them first.<br /><br /><br />Daniel<br /><br /><br />On 02/24/2015 04:42 PM, Daniel Grotti wrote:<br /><blockquote>Hi Stefano,<br />The problem here is that the ACK from Cirpack is not setting the Route<br />headers:<br /><br />ACK<br />sip:ngcp-lb@192.168.252.155:5060;ngcpct=7369703a3132372e302e302e313a353038303b707278726f7574653d31<br />SIP/2.0<br />Call-ID: 18288-RU-00221b20-0aba21985@voip.digitelitalia.it<br />Contact: <sip:109.238.17.166:5060><br />CSeq: 2057622 ACK<br />From: "3355416588"<br /><sip:3355416588@voip.digitelitalia.it;user=phone>;tag=18288-ZM-00221b21-2ac08e736<br />Max-Forwards: 28<br />To:<br /><sip:011013338@127.0.0.1;user=phone>;tag=5A56F94D-54EB3F51000A5A27-16A20700<br />Via: SIP/2.0/UDP 109.238.17.166:5060;branch=z9hG4bK-RNFE-66710c29-4050198a<br />User-Agent: Cirpack/v4.58 (gw_sip)<br />Content-Length: 0<br /><br /><br /><br />They must take from the 200 OK the Record-Route headers and set Route<br />headers in the ACK/BYE in the reverse order.<br /><br />This is an issue of your provider.<br /><br />Daniel<br /><br /><br /><br />On 02/24/2015 04:28 PM, stefanormc wrote:<br /><blockquote>Please find attached the pcap file. I can’t seem to find a solution.<br /><br />thanks<br /><br />ciao<br /><br />stefano<br /><br /><br /><br /><br /><br /><br /><br /><blockquote>On 24 Feb 2015, at 11:04, stefanormc <stefanormc@gmail.com<br /><mailto:stefanormc@gmail.com>> wrote:<br /><br /><br /><blockquote>On 15 Feb 2015, at 23:57, stefano Rogna Manassero di Costigliole<br /><stefanormc@gmail.com <mailto:stefanormc@gmail.com>> wrote:<br /><br />It's a wholesale service provided on a per line account base, it's<br />not a trunk. I just configured the peer server and put auth details<br />on each subscriber details.<br /><br />------------------------------------------------------------------------<br />Da: Jeremy Ward<br />Inviato: 15/02/2015 22:43<br />A: stefanormc<br />Cc: Daniel Grotti; Spce-user<br />Oggetto: Re: [Spce-user] NAT problems<br /><br />Just out of curiosity, are you subscribed to this provider's SIP<br />trunking services, or are you subscribed to their retail SIP<br />services, as in the type intended for an individual end-user device?<br /><br />Jeremy D. Ward, CWNE<br />(954) 661-4965<br /><br />On Feb 15, 2015 12:04 PM, "stefanormc" <stefanormc@gmail.com<br /><mailto:stefanormc@gmail.com>> wrote:<br /><br /> could it be overrun in any other way (the missing route header)?<br /><br /> because I’m beginning to think I will never get a reply from the<br /> provider…<br /><br /><br /><br /><blockquote>On 15 Feb 2015, at 11:53, Daniel Grotti <dgrotti@sipwise.com<br /></blockquote> <mailto:dgrotti@sipwise.com>> wrote:<br /><blockquote><br />Hi,<br />Nat traversal is done out of the box on ngcp.<br />You need to disable other nat traversal features on client<br /></blockquote> side, like stun for example.<br /><blockquote><br />What I noticed though was a missing route headers in the ACK.<br /></blockquote> This doesn't look have relationship with nat.<br /><blockquote><br />DanielOn 15 Feb 2015 11:38, stefanormc <stefanormc@gmail.com<br /></blockquote> <mailto:stefanormc@gmail.com>> wrote:<br /><blockquote><blockquote><br />changes in the nat section of the server?<br /><br /><br /><br /><blockquote>On 15 Feb 2015, at 10:56, stefanormc <stefanormc@gmail.com<br /></blockquote></blockquote></blockquote> <mailto:stefanormc@gmail.com>> wrote:<br /><blockquote><blockquote><blockquote><br />hello again<br /><br />still no reply from the provider; any other possible solutions?<br /><br />thanks<br /><br />ciao<br /><br />setfano<br /><br /><br /><blockquote>On 07 Feb 2015, at 16:50, stefanormc <stefanormc@gmail.com<br /></blockquote></blockquote></blockquote></blockquote> <mailto:stefanormc@gmail.com>> wrote:<br /><blockquote><blockquote><blockquote><blockquote><br />enabling ICE on the client side seems to solve the problem<br /></blockquote></blockquote></blockquote></blockquote> on X-Lite and on a Snom 190. No luck with a Gigaset 510IP<br /><blockquote><blockquote><blockquote><blockquote><br />I sent a request to the provider. I’ll post the reply<br /><br />thanks for now<br /><br />helpful as always<br /><br /><br /><br /><blockquote>On 07 Feb 2015, at 13:42, Daniel Grotti<br /></blockquote></blockquote></blockquote></blockquote></blockquote> <dgrotti@sipwise.com <mailto:dgrotti@sipwise.com>> wrote:<br /><blockquote><blockquote><blockquote><blockquote><blockquote><br />The ACK from cirpack doesn't contain route headers. They<br /></blockquote></blockquote></blockquote></blockquote></blockquote> must be there.<br /><blockquote><blockquote><blockquote><blockquote><blockquote>Please check this with them.<br /><br />Daniel<br />On 7 Feb 2015 13:09, stefanormc <stefanormc@gmail.com<br /></blockquote></blockquote></blockquote></blockquote></blockquote> <mailto:stefanormc@gmail.com>> wrote:<br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><br />hi<br /><br />way too technical…<br /><br />how do I do that? Or is it something the provider should do?<br /><br /><br /><br /><blockquote>On 07 Feb 2015, at 11:39, Daniel Grotti<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> <dgrotti@sipwise.com <mailto:dgrotti@sipwise.com>> wrote:<br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><br />Hi,<br />Looks like an ACK issue here.<br />ACK seems is not containing Route headers.<br />ACK must contains route headers taken from the<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> record-route headers in the 200ok and put it in the reverse order.<br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><br />Daniel<br /><br />On 7 Feb 2015 10:42, stefanormc <stefanormc@gmail.com<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> <mailto:stefanormc@gmail.com>> wrote:<br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><br />hello again,<br /><br />with help from the community I managed to get the phones<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> ringing on incoming calls, but now I get a NAT problem of<br /> Dropping mi-routed request only on incoming calls, outbound calls<br /> work fine.<br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><br />Any suggestion please?<br /><br />Feb 7 10:30:08 centrale proxy[4109]: NOTICE: <script>:<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> Forcing request via B2BUA 'sip:127.0.0.1:5080<br /> <http://127.0.0.1:5080/>' - R=sip:0110133249@87.253.112.141:5060<br /> <http://sip:0110133249@87.253.112.141:5060/><br /> ID=19046-VT-0353f94d-23d801696@voip.digitelitalia.it<br /> <mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it><br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote>Feb 7 10:30:08 centrale proxy[4109]: NOTICE: <script>:<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> Request leaving server, D-URI='sip:127.0.0.1:5080<br /> <http://127.0.0.1:5080/>' - R=sip:0110133249@87.253.112.141:5060<br /> <http://sip:0110133249@87.253.112.141:5060/><br /> ID=19046-VT-0353f94d-23d801696@voip.digitelitalia.it<br /> <mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it><br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote>Feb 7 10:30:08 centrale proxy[4100]: NOTICE: <script>:<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> NAT-Reply - S=100 - Connecting M=INVITE IP=109.238.17.166:5060<br /> <http://109.238.17.166:5060/> (127.0.0.1:5080<br /> <http://127.0.0.1:5080/>)<br /> ID=19046-VT-0353f94d-23d801696@voip.digitelitalia.it<br /> <mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it><br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote>Feb 7 10:30:09 centrale proxy[4091]: NOTICE: <script>:<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> NAT-Reply - S=180 - Ringing M=INVITE IP=109.238.17.166:5060<br /> <http://109.238.17.166:5060/> (127.0.0.1:5080<br /> <http://127.0.0.1:5080/>)<br /> ID=19046-VT-0353f94d-23d801696@voip.digitelitalia.it<br /> <mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it><br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote>Feb 7 10:30:11 centrale proxy[4104]: NOTICE: <script>:<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> NAT-Reply - S=200 - OK M=INVITE IP=109.238.17.166:5060<br /> <http://109.238.17.166:5060/> (127.0.0.1:5080<br /> <http://127.0.0.1:5080/>)<br /> ID=19046-VT-0353f94d-23d801696@voip.digitelitalia.it<br /> <mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it><br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote>Feb 7 10:30:11 centrale proxy[4097]: NOTICE: <script>:<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> New request on proxy - M=ACK R=sip:127.0.0.1:5080;prxroute=1<br /> F=sip:3355416588@voip.digitelitalia.it<br /> <mailto:sip%3A3355416588@voip.digitelitalia.it>;user=phone<br /> T=sip:0110133249@127.0.0.1<br /> <mailto:sip%3A0110133249@127.0.0.1>;user=phone<br /> IP=109.238.17.166:5060 <http://109.238.17.166:5060/><br /> (127.0.0.1:5060 <http://127.0.0.1:5060/>)<br /> ID=19046-VT-0353f94d-23d801696@voip.digitelitalia.it<br /> <mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it><br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote>Feb 7 10:30:11 centrale proxy[4097]: NOTICE: <script>:<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> Dropping mis-routed request - R=sip:127.0.0.1:5080;prxroute=1<br /> ID=19046-VT-0353f94d-23d801696@voip.digitelitalia.it<br /> <mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it><br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote>Feb 7 10:30:11 centrale proxy[4114]: NOTICE: <script>:<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> NAT-Reply - S=200 - OK M=INVITE IP=109.238.17.166:5060<br /> <http://109.238.17.166:5060/> (127.0.0.1:5080<br /> <http://127.0.0.1:5080/>)<br /> ID=19046-VT-0353f94d-23d801696@voip.digitelitalia.it<br /> <mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it><br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote>Feb 7 10:30:11 centrale proxy[4094]: NOTICE: <script>:<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote> New request on proxy - M=ACK R=sip:127.0.0.1:5080;prxroute=1<br /> F=sip:3355416588@voip.digitelitalia.it<br /> <mailto:sip%3A3355416588@voip.digitelitalia.it>;user=phone<br /> T=sip:0110133249@127.0.0.1<br /> <mailto:sip%3A0110133249@127.0.0.1>;user=phone<br /> IP=109.238.17.166:5060 <http://109.238.17.166:5060/><br /> (127.0.0.1:5060 <http://127.0.0.1:5060/>)<br /> ID=19046-VT-0353f94d-23d801696@voip.digitelitalia.it<br /> <mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it><br /><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><blockquote><br /></blockquote></blockquote><br /></blockquote></blockquote><br /></blockquote><br /></blockquote><br /></blockquote></blockquote><br /> _______________________________________________<br /> Spce-user mailing list<br /> Spce-user@lists.sipwise.com <mailto:Spce-user@lists.sipwise.com><br /> https://lists.sipwise.com/listinfo/spce-user<br /><br /></blockquote><br /></blockquote><br /></blockquote>_______________________________________________<br />Spce-user mailing list<br />Spce-user@lists.sipwise.com<br />https://lists.sipwise.com/listinfo/spce-user<br /><br /></blockquote>_______________________________________________<br />Spce-user mailing list<br />Spce-user@lists.sipwise.com<br />https://lists.sipwise.com/listinfo/spce-user<br /><br /></blockquote>_______________________________________________<br />Spce-user mailing list<br /><a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br />https://lists.sipwise.com/listinfo/spce-user<br /></div></blockquote></div><br /></div></div></blockquote></div>