View Single Post
Unread 08-15-2009, 07:08 AM   #7
boatman
Senior Member
 
boatman's Avatar
 
Join Date: Jul 2007
Location: Oregon, USA
Posts: 365
Thanks: 17
Thanked 77 Times in 64 Posts
boatman is on a distinguished road
Default

Quote:
Originally Posted by scaev View Post
..."Symmetric NAT handling" option is set to "Yes" (if set to "No", nothing is working).
As far as I know, Voxalot's optional "Symmetric NAT handling" is a feature that can be activated only when there is a fault that causes a non-routable LAN IP address to be used as the Contact Address in a SIP SDP packet. This can happen when the ATA is behind a symmetric NAT router, the ATA is mis-configured, or a STUN server is not working, etc. The Contact Address is supposed to be your public IP address.

Strangely, your Voxalot to Voxalot calls are being routed through SipBroker. This is not normal. Below, part of a SIP packet captured from your incoming test call shows the servers which handled the SIP packet. Note that sipbroker (64.34.162.221) is the second hop for the call.

Record-Route: <sip:64.34.173.199;lr=on;ftag=as0461a5eb>
Record-Route: <sip:72.51.47.59;lr=on;ftag=as0461a5eb>
Record-Route: <sip:64.34.162.221;lr=on;ftag=as0461a5eb>
Via: SIP/2.0/UDP 64.34.173.199;branch=z9hG4bK2b69.a30ed691.0
Via: SIP/2.0/UDP 72.51.47.59;branch=z9hG4bK2b69.6d3f4d22.0
Via: SIP/2.0/UDP 64.34.162.221;branch=z9hG4bK2b69.eeddfa11.0
Via: SIP/2.0/UDP 64.34.173.199:5061;branch=z9hG4bK5197bd11;rport=50 61
From: "840146" <sip:840146@64.34.173.199:5061>;tag=as0461a5eb
To: <sip:*010608019@sipbroker.com>
Contact: <sip:840146@64.34.173.199:5061>
Call-ID: 6be93ba43f255ff234fdf3977a9e2c54@64.34.173.199
CSeq: 102 INVITE
User-Agent: voxaLot
Max-Forwards: 67
boatman is offline   Reply With Quote