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:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP mypublicIP:5060;branch=z9hG4bK01757b08;rport From: "901" <sip:[EMAIL PROTECTED]>;tag=as69ce5a7a To: <sip:[EMAIL PROTECTED]> Contact: <sip:[EMAIL PROTECTED]> Call-ID: [EMAIL PROTECTED] 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:[EMAIL PROTECTED]", 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 _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
