[Spce-user] NAT problems

[Jeremy Ward]

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?

Jeremy D. Ward, CWNE
(954) 661-4965
On Feb 15, 2015 12:04 PM, "stefanormc" <stefanormc at gmail.com> wrote:

> could it be overrun in any other way (the missing route header)?
>
> because I’m beginning to think I will never get a reply from the provider…
>
>
>
> > On 15 Feb 2015, at 11:53, Daniel Grotti <dgrotti at sipwise.com> wrote:
> >
> > Hi,
> > Nat traversal is done out of the box on ngcp.
> > You need to disable other nat traversal features on client side, like
> stun for example.
> >
> > What I noticed though was a missing route headers in the ACK. This
> doesn't look have relationship with nat.
> >
> > DanielOn 15 Feb 2015 11:38, stefanormc <stefanormc at gmail.com> wrote:
> >>
> >> changes in the nat section of the server?
> >>
> >>
> >>
> >>> On 15 Feb 2015, at 10:56, stefanormc <stefanormc at gmail.com> wrote:
> >>>
> >>> hello again
> >>>
> >>> still no reply from the provider; any other possible solutions?
> >>>
> >>> thanks
> >>>
> >>> ciao
> >>>
> >>> setfano
> >>>
> >>>
> >>>> On 07 Feb 2015, at 16:50, stefanormc <stefanormc at gmail.com> wrote:
> >>>>
> >>>> 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
> >>>>
> >>>> I sent a request to the provider. I’ll post the reply
> >>>>
> >>>> thanks for now
> >>>>
> >>>> helpful as always
> >>>>
> >>>>
> >>>>
> >>>>> On 07 Feb 2015, at 13:42, Daniel Grotti <dgrotti at sipwise.com> wrote:
> >>>>>
> >>>>> The ACK from cirpack doesn't contain route headers. They must be
> there.
> >>>>> Please check this with them.
> >>>>>
> >>>>> Daniel
> >>>>> On 7 Feb 2015 13:09, stefanormc <stefanormc at gmail.com> wrote:
> >>>>>>
> >>>>>> hi
> >>>>>>
> >>>>>> way too technical…
> >>>>>>
> >>>>>> how do I do that? Or is it something the provider should do?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On 07 Feb 2015, at 11:39, Daniel Grotti <dgrotti at sipwise.com>
> wrote:
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>> Looks like an ACK issue here.
> >>>>>>> ACK seems is not containing Route headers.
> >>>>>>> ACK must contains route headers taken from the record-route
> headers in the 200ok and put it in the reverse order.
> >>>>>>>
> >>>>>>> Daniel
> >>>>>>>
> >>>>>>> On 7 Feb 2015 10:42, stefanormc <stefanormc at gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> hello again,
> >>>>>>>>
> >>>>>>>> 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.
> >>>>>>>>
> >>>>>>>> Any suggestion please?
> >>>>>>>>
> >>>>>>>> Feb  7 10:30:08 centrale proxy[4109]: NOTICE: <script>: Forcing
> request via B2BUA 'sip:127.0.0.1:5080' - R=
> sip:0110133249 at 87.253.112.141:5060 ID=
> 19046-VT-0353f94d-23d801696 at voip.digitelitalia.it
> >>>>>>>> Feb  7 10:30:08 centrale proxy[4109]: NOTICE: <script>: Request
> leaving server, D-URI='sip:127.0.0.1:5080' - R=
> sip:0110133249 at 87.253.112.141:5060 ID=
> 19046-VT-0353f94d-23d801696 at voip.digitelitalia.it
> >>>>>>>> Feb  7 10:30:08 centrale proxy[4100]: NOTICE: <script>: NAT-Reply
> - S=100 - Connecting M=INVITE IP=109.238.17.166:5060 (127.0.0.1:5080) ID=
> 19046-VT-0353f94d-23d801696 at voip.digitelitalia.it
> >>>>>>>> Feb  7 10:30:09 centrale proxy[4091]: NOTICE: <script>: NAT-Reply
> - S=180 - Ringing M=INVITE IP=109.238.17.166:5060 (127.0.0.1:5080) ID=
> 19046-VT-0353f94d-23d801696 at voip.digitelitalia.it
> >>>>>>>> Feb  7 10:30:11 centrale proxy[4104]: NOTICE: <script>: NAT-Reply
> - S=200 - OK M=INVITE IP=109.238.17.166:5060 (127.0.0.1:5080) ID=
> 19046-VT-0353f94d-23d801696 at voip.digitelitalia.it
> >>>>>>>> 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=
> sip:3355416588 at voip.digitelitalia.it;user=phone T=sip:0110133249 at 127.0.0.1;user=phone
> IP=109.238.17.166:5060 (127.0.0.1:5060) ID=
> 19046-VT-0353f94d-23d801696 at voip.digitelitalia.it
> >>>>>>>> Feb  7 10:30:11 centrale proxy[4097]: NOTICE: <script>: Dropping
> mis-routed request - R=sip:127.0.0.1:5080;prxroute=1 ID=
> 19046-VT-0353f94d-23d801696 at voip.digitelitalia.it
> >>>>>>>> Feb  7 10:30:11 centrale proxy[4114]: NOTICE: <script>: NAT-Reply
> - S=200 - OK M=INVITE IP=109.238.17.166:5060 (127.0.0.1:5080) ID=
> 19046-VT-0353f94d-23d801696 at voip.digitelitalia.it
> >>>>>>>> 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=
> sip:3355416588 at voip.digitelitalia.it;user=phone T=sip:0110133249 at 127.0.0.1;user=phone
> IP=109.238.17.166:5060 (127.0.0.1:5060) ID=
> 19046-VT-0353f94d-23d801696 at voip.digitelitalia.it
> >>>>>>>>
> >>>>>>
> >>>>
> >>>
> >>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20150215/69c1639c/attachment-0001.html>