<p dir="ltr">Just out of curiosity, are you subscribed to this provider's SIP trunking services, or are you subscribed to their retail SIP services, as in the type intended for an individual end-user device?<br></p>
<p dir="ltr">Jeremy D. Ward, CWNE<br>
(954) 661-4965</p>
<div class="gmail_quote">On Feb 15, 2015 12:04 PM, "stefanormc" <<a href="mailto:stefanormc@gmail.com">stefanormc@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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 provider…<br>
<br>
<br>
<br>
> On 15 Feb 2015, at 11:53, Daniel Grotti <<a href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a>> wrote:<br>
><br>
> Hi,<br>
> Nat traversal is done out of the box on ngcp.<br>
> You need to disable other nat traversal features on client side, like stun for example.<br>
><br>
> What I noticed though was a missing route headers in the ACK. This doesn't look have relationship with nat.<br>
><br>
> DanielOn 15 Feb 2015 11:38, stefanormc <<a href="mailto:stefanormc@gmail.com">stefanormc@gmail.com</a>> wrote:<br>
>><br>
>> changes in the nat section of the server?<br>
>><br>
>><br>
>><br>
>>> On 15 Feb 2015, at 10:56, stefanormc <<a href="mailto:stefanormc@gmail.com">stefanormc@gmail.com</a>> wrote:<br>
>>><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>
>>>> On 07 Feb 2015, at 16:50, stefanormc <<a href="mailto:stefanormc@gmail.com">stefanormc@gmail.com</a>> wrote:<br>
>>>><br>
>>>> enabling ICE on the client side seems to solve the problem on X-Lite and on a Snom 190. No luck with a Gigaset 510IP<br>
>>>><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>
>>>>> On 07 Feb 2015, at 13:42, Daniel Grotti <<a href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a>> wrote:<br>
>>>>><br>
>>>>> The ACK from cirpack doesn't contain route headers. They must be there.<br>
>>>>> Please check this with them.<br>
>>>>><br>
>>>>> Daniel<br>
>>>>> On 7 Feb 2015 13:09, stefanormc <<a href="mailto:stefanormc@gmail.com">stefanormc@gmail.com</a>> wrote:<br>
>>>>>><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>
>>>>>>> On 07 Feb 2015, at 11:39, Daniel Grotti <<a href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a>> wrote:<br>
>>>>>>><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 record-route headers in the 200ok and put it in the reverse order.<br>
>>>>>>><br>
>>>>>>> Daniel<br>
>>>>>>><br>
>>>>>>> On 7 Feb 2015 10:42, stefanormc <<a href="mailto:stefanormc@gmail.com">stefanormc@gmail.com</a>> wrote:<br>
>>>>>>>><br>
>>>>>>>> hello again,<br>
>>>>>>>><br>
>>>>>>>> with help from the community I managed to get the phones ringing on incoming calls, but now I get a NAT problem of Dropping mi-routed request only on incoming calls, outbound calls work fine.<br>
>>>>>>>><br>
>>>>>>>> Any suggestion please?<br>
>>>>>>>><br>
>>>>>>>> Feb 7 10:30:08 centrale proxy[4109]: NOTICE: <script>: Forcing request via B2BUA 'sip:<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a>' - R=<a href="http://sip:0110133249@87.253.112.141:5060" target="_blank">sip:0110133249@87.253.112.141:5060</a> ID=<a href="mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it">19046-VT-0353f94d-23d801696@voip.digitelitalia.it</a><br>
>>>>>>>> Feb 7 10:30:08 centrale proxy[4109]: NOTICE: <script>: Request leaving server, D-URI='sip:<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a>' - R=<a href="http://sip:0110133249@87.253.112.141:5060" target="_blank">sip:0110133249@87.253.112.141:5060</a> ID=<a href="mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it">19046-VT-0353f94d-23d801696@voip.digitelitalia.it</a><br>
>>>>>>>> Feb 7 10:30:08 centrale proxy[4100]: NOTICE: <script>: NAT-Reply - S=100 - Connecting M=INVITE IP=<a href="http://109.238.17.166:5060" target="_blank">109.238.17.166:5060</a> (<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a>) ID=<a href="mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it">19046-VT-0353f94d-23d801696@voip.digitelitalia.it</a><br>
>>>>>>>> Feb 7 10:30:09 centrale proxy[4091]: NOTICE: <script>: NAT-Reply - S=180 - Ringing M=INVITE IP=<a href="http://109.238.17.166:5060" target="_blank">109.238.17.166:5060</a> (<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a>) ID=<a href="mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it">19046-VT-0353f94d-23d801696@voip.digitelitalia.it</a><br>
>>>>>>>> Feb 7 10:30:11 centrale proxy[4104]: NOTICE: <script>: NAT-Reply - S=200 - OK M=INVITE IP=<a href="http://109.238.17.166:5060" target="_blank">109.238.17.166:5060</a> (<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a>) ID=<a href="mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it">19046-VT-0353f94d-23d801696@voip.digitelitalia.it</a><br>
>>>>>>>> Feb 7 10:30:11 centrale proxy[4097]: NOTICE: <script>: New request on proxy - M=ACK R=sip:127.0.0.1:5080;prxroute=1 F=<a href="mailto:sip%3A3355416588@voip.digitelitalia.it">sip:3355416588@voip.digitelitalia.it</a>;user=phone T=<a href="mailto:sip%3A0110133249@127.0.0.1">sip:0110133249@127.0.0.1</a>;user=phone IP=<a href="http://109.238.17.166:5060" target="_blank">109.238.17.166:5060</a> (<a href="http://127.0.0.1:5060" target="_blank">127.0.0.1:5060</a>) ID=<a href="mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it">19046-VT-0353f94d-23d801696@voip.digitelitalia.it</a><br>
>>>>>>>> Feb 7 10:30:11 centrale proxy[4097]: NOTICE: <script>: Dropping mis-routed request - R=sip:127.0.0.1:5080;prxroute=1 ID=<a href="mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it">19046-VT-0353f94d-23d801696@voip.digitelitalia.it</a><br>
>>>>>>>> Feb 7 10:30:11 centrale proxy[4114]: NOTICE: <script>: NAT-Reply - S=200 - OK M=INVITE IP=<a href="http://109.238.17.166:5060" target="_blank">109.238.17.166:5060</a> (<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a>) ID=<a href="mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it">19046-VT-0353f94d-23d801696@voip.digitelitalia.it</a><br>
>>>>>>>> Feb 7 10:30:11 centrale proxy[4094]: NOTICE: <script>: New request on proxy - M=ACK R=sip:127.0.0.1:5080;prxroute=1 F=<a href="mailto:sip%3A3355416588@voip.digitelitalia.it">sip:3355416588@voip.digitelitalia.it</a>;user=phone T=<a href="mailto:sip%3A0110133249@127.0.0.1">sip:0110133249@127.0.0.1</a>;user=phone IP=<a href="http://109.238.17.166:5060" target="_blank">109.238.17.166:5060</a> (<a href="http://127.0.0.1:5060" target="_blank">127.0.0.1:5060</a>) ID=<a href="mailto:19046-VT-0353f94d-23d801696@voip.digitelitalia.it">19046-VT-0353f94d-23d801696@voip.digitelitalia.it</a><br>
>>>>>>>><br>
>>>>>><br>
>>>><br>
>>><br>
>><br>
<br>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</blockquote></div>