[asterisk-users] Sip trunk mystery

[Dirk Enrique Seiffert]

Hi Jared,

>
> Notice how the Contact Header and the SDP all have the IP address of
> 192.168.8.3?  If your firewall isn't masquerading (rewriting) those
> addresses as the SIP traffic goes through it, then the device on the
> other end is going to try to contact 192.168.8.3, and I'm guessing it's
> going to have a hard time doing that.  (This would also explain why
> you're seeing outbound traffic only in your tcpdump traces.)
>

My firewall is masquerading, anyhow I modified also the
externalip=mypublicIP . Now it looks like this:

Retransmitting #4 (NAT) to 190.144.151.212:5060:
INVITE sip:xxxxx46022 at sip.net-voz.com SIP/2.0
Via: SIP/2.0/UDP mypublicIP:5060;branch=z9hG4bK01757b08;rport
From: "901" <sip:901 at sip.net-voz.com>;tag=as69ce5a7a
To: <sip:5756646022 at sip.net-voz.com>
Contact: <sip:901 at mypublicIP>
Call-ID: 060bfbb24ecf6c88348d72d91e3ea978 at sip.net-voz.com
CSeq: 103 INVITE
User-Agent: Grandstream BT100 1.0.4.49
Max-Forwards: 70
Proxy-Authorization: Digest username="5515816168", realm="VoipSwitch",
algorithm=MD5, uri="sip:5756646022 at sip.net-voz.com",
nonce="120406066426160405702174408208",
response="a6c72a47ea39c1200f2add823369ebce", opaque=""
Date: Tue, 26 Feb 2008 21:20:58 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY

What else might might be wrong here?


Thanks

Enrique
Cartagena - Colombia
http://www.sipcolombia.com