[OpenSIPS-Users] NATed REGISTERs are failing

[Jeff Pyle]

Team,

With Iñaki's help it appears we have discovered bug.  Replies are returning to the private IP, not the public IP of the NAT router.  See below.  Some information has been obfuscated to protect the guilty:

U +169.011646 60.70.68.231:5060 -> 60.70.82.42:5060
REGISTER sip:60.70.82.42 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK-e3bd0c30.
From: <sip:9993210093 at 60.70.82.42>;tag=eb13441c66af5e87o0.
To: <sip:9993210093 at 60.70.82.42>.
Call-ID: b19ef0af-bf3fe1f2 at 192.168.1.103.
CSeq: 27022 REGISTER.
Max-Forwards: 70.
Contact: <sip:9993210093 at 192.168.1.103:5060>;expires=1800.
User-Agent: Linksys/SPA2102-3.3.6.
Content-Length: 0.
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER.
Supported: 100rel, x-sipura.
.

#
U +0.002399 60.70.82.42:5060 -> 192.168.1.103:5060
SIP/2.0 100 Trying.
Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK-e3bd0c30;rport=5060;received=60.70.68.231.
From: <sip:9993210093 at 60.70.82.42>;tag=eb13441c66af5e87o0.
To: <sip:9993210093 at 60.70.82.42>.
Call-ID: b19ef0af-bf3fe1f2 at 192.168.1.103.
CSeq: 27022 REGISTER.
Content-Length: 0.
.

#
U +0.002064 60.70.82.42:5060 -> 192.168.1.103:5060
SIP/2.0 401 Unauthorized.
Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK-e3bd0c30;rport=5060;received=60.70.68.231.
From: <sip:9993210093 at 60.70.82.42>;tag=eb13441c66af5e87o0.
To: <sip:9993210093 at 60.70.82.42>;tag=99bce31ab9ba81d6766d9656ce4ac145.00bd.
Call-ID: b19ef0af-bf3fe1f2 at 192.168.1.103.
CSeq: 27022 REGISTER.
WWW-Authenticate: Digest realm="dummyrealm.net", nonce="49085eb50000004645e6a9744bd1d8cd123a1d3ccf0caea7".
Content-Length: 0.


At least now I know this isn't another symptom of my insanity.


- Jeff



-----Original Message-----
From: users-bounces at lists.opensips.org [mailto:users-bounces at lists.opensips.org] On Behalf Of Iñaki Baz Castillo
Sent: Wednesday, October 29, 2008 8:29 AM
Cc: users at lists.opensips.org
Subject: Re: [OpenSIPS-Users] NATed REGISTERs are failing

2008/10/29 Jeff Pyle <jpyle at fidelityvoice.com>:
> Iñaki,
>
> We're not getting that far.
>
> The REGISTER comes in, OpenSIPs sends a 100 (sl_send_reply), then a 401 (www_challenge).  Both the 100 and the 401 are being sent to the private (192.168.3.100) instead of the public.

Can you capture a complete SIP trace in the proxy server?

  ngrep -d any -W byline -T port 5060

--
Iñaki Baz Castillo
<ibc at aliax.net>
_______________________________________________