<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<font size="+1"><font face="Helvetica, Arial, sans-serif">Jared,<br>
<br>
the Portech SIMbox is registering to a DNS name. The firewall is off
and the NAT is a Zyxel NBG-419 router.<br>
<br>
No mather what port I set, It is not working :<br>
<br>
</font></font><font size="+1"><font face="Helvetica, Arial, sans-serif"><small><---
SIP read from my_public_ip:5070 ---><br>
REGISTER sip:sip.sipserver.tld SIP/2.0<br>
Via: SIP/2.0/UDP 192.168.1.25:5070;branch=z9hG4bK4465928ede<br>
From: "SIM 1-1" <a class="moz-txt-link-rfc2396E" href="mailto:sip:simsim1@sip.sipserver.tld"><sip:simsim1@sip.sipserver.tld></a>;tag=6672a4c3<br>
To: "SIM 1-1" <a class="moz-txt-link-rfc2396E" href="mailto:sip:simsim1@sip.sipserver.tld"><sip:simsim1@sip.sipserver.tld></a><br>
Call-ID: <a class="moz-txt-link-abbreviated"
href="mailto:277210db31b0ae184675c3245d5e949f@192.168.1.25">277210db31b0ae184675c3245d5e949f@192.168.1.25</a><br>
Contact: <a class="moz-txt-link-rfc2396E"
href="mailto:sip:simsim1@192.168.1.25:5070"><sip:simsim1@192.168.1.25:5070></a><br>
CSeq: 56 REGISTER<br>
Max-Forwards: 70<br>
Expires: 60<br>
Allow: INVITE,CANCEL,ACK,BYE,NOTIFY,REFER,OPTIONS,INFO,MESSAGE,UPDATE<br>
User-Agent: Mv-37x (904290)<br>
Content-Length: 0<br>
<br>
<br>
<-------------><br>
[May 2 10:38:51] --- (12 headers 0 lines) ---<br>
[May 2 10:38:51] Using latest REGISTER request as basis request<br>
[May 2 10:38:51] Sending to 192.168.1.25 : 5070 (no NAT)<br>
[May 2 10:38:51] <br>
<--- Transmitting (NAT) to my_public_ip:5070 ---><br>
SIP/2.0 100 Trying<br>
Via: SIP/2.0/UDP
192.168.1.25:5070;branch=z9hG4bK4465928ede;received=my_public_ip<br>
From: "SIM 1-1" <a class="moz-txt-link-rfc2396E" href="mailto:sip:simsim1@sip.sipserver.tld"><sip:simsim1@sip.sipserver.tld></a>;tag=6672a4c3<br>
To: "SIM 1-1" <a class="moz-txt-link-rfc2396E" href="mailto:sip:simsim1@sip.sipserver.tld"><sip:simsim1@sip.sipserver.tld></a><br>
Call-ID: <a class="moz-txt-link-abbreviated"
href="mailto:277210db31b0ae184675c3245d5e949f@192.168.1.25">277210db31b0ae184675c3245d5e949f@192.168.1.25</a><br>
CSeq: 56 REGISTER<br>
User-Agent: Asterisk PBX<br>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY<br>
Supported: replaces<br>
Content-Length: 0<br>
<br>
<br>
<------------><br>
[May 2 10:38:51] <br>
<--- Transmitting (NAT) to my_public_ip:5070 ---><br>
SIP/2.0 401 Unauthorized<br>
Via: SIP/2.0/UDP
192.168.1.25:5070;branch=z9hG4bK4465928ede;received=my_public_ip<br>
From: "SIM 1-1" <a class="moz-txt-link-rfc2396E" href="mailto:sip:simsim1@sip.sipserver.tld"><sip:simsim1@sip.sipserver.tld></a>;tag=6672a4c3<br>
To: "SIM 1-1" <a class="moz-txt-link-rfc2396E" href="mailto:sip:simsim1@sip.sipserver.tld"><sip:simsim1@sip.sipserver.tld></a>;tag=as12309a5f<br>
Call-ID: <a class="moz-txt-link-abbreviated"
href="mailto:277210db31b0ae184675c3245d5e949f@192.168.1.25">277210db31b0ae184675c3245d5e949f@192.168.1.25</a><br>
CSeq: 56 REGISTER<br>
User-Agent: Asterisk PBX<br>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY<br>
Supported: replaces<br>
WWW-Authenticate: Digest algorithm=MD5, realm="103001vc",
nonce="7c2508cc"<br>
Content-Length: 0<br>
<br>
<big>Is it normal that there is a Via-header sent from the SIMbox with
its local IP-address in it ??<br>
Is it normal that "SIP read from my_public_ip:5070" has the same port
number as the SIP-account (simsim1) 192.168.1.25:5070 ??<br>
Could it be that NAT is not working correctly in my router ??<br>
<br>
<br>
Jonas.<br>
</big></small></font></font><font size="+1"><font
face="Helvetica, Arial, sans-serif"><br>
</font></font><br>
On 04/22/2010 05:53 PM, Jared Smith wrote:<br>
<blockquote cite="mid:1271951636.3278.2.camel@localhost.localdomain"
type="cite">
<pre wrap="">Is the device registering to an IP address, or do a DNS name? What type
of NAT firewall are you using?
This reminds me of a problem I had years ago with a Cisco PIX firewall,
where it would rewrite IP addresses in the SIP Request URI, causing the
authentication to fail. One solution was to have it register to a
fully-qualified domain name instead of an IP address, so that the
Request URI wouldn't get overwritten.
It's certainly worth a shot...
--
Jared Smith
Digium, Inc.
</pre>
</blockquote>
</body>
</html>