Thats exactly what the "Enable NAT traversal" does. When its enabled, it anchors media that is outside its local subnet and then re-writes the sip packet with its external IP to keep the media anchored. This is preformed by sipxrelay.
So when you have it disabled, the proxy does NOT use the public ip, but media will fail as the media will attempt to go between the endpoints (softphones) and the Cisco based sip trunk directly. Which typically wont work. The real issues is you cant use re-invites with your trunk which is the normal way for the "NAT" function to operate. One thing you could try is to setup sipxbridge for both inbound and outbound. Sipxbridge has the option to leave the private or public ip in the invite independent of sipxrelay. But of course, you'll have the issue with reinvites. I think your only real option is a 2nd SBC in between sipx and the cisco trunk that can handle the media relay without reinvites. Or repalce the cisco trunk..... -M >>> Sven Evensen <[email protected]> 09/06/12 10:42 AM >>> This is a continuation of my issue from a week or so back. So my sipx 4.4 is in EC2 using a SIP trunk which is Cisco based and does not support re-invites. So we have to use unmanaged gateway. But I have been having issues that sipxProxy uses sipx's external IP adress in VIa: when it should use internal. I got a tips that the ITSP should send INVITE to us using FQDN, but they could not do that. SO I hoped that they could send on 5080 TO us and we use unmanaged GW to them. The problem is this: When "Enable NAT Traversal" is ON, sipxProxy sends with external IP address and media fails later in the call. When "Enable NAT Traversal" is OFF, sipxProxy sends with internal IP adress and media is fine. THis is for SIP trunk to SIP trunk calls. Now that "Enable NAT Traversal" id off, softphones have no media, but that is secondary compared to the sipxProxy issue. Please look at line 3 in "ad1-incoming-call-nat-on" and observe the first Via entry uses external IP address Then look at line 4 in "ad1-incoming-call-nat-off" and observe the first Via entry uses internal IP address These are identical calls except "Enable NAT Traversal" on and off. So, why is a call coming in through SIP trunk affected by the " Enable NAT Traversal". And how do I get around this problem. Sven -- Sven Evensen, Operations Consultant OnRelay Elizabeth House │ 39 York Road, London SE1 7NQ, UK │ +44 (0) 207 902 8123 │ mailto:[email protected] │ www.onrelay.com This electronic message transmission contains information from OnRelay, Ltd., that may be confidential or privileged. The information is intended solely for the recipient and use by any other party is not authorised. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information or any attachment, is prohibited. If you have received this electronic transmission in error, please notify us immediately by electronic mail ([email protected]) and delete this message, along with any attachments, from your computer. Registered in England No 04006093 | Registered Office 1st Floor, 236 Gray's Inn Road, London WC1X 8HB
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
