I am testing an ipsec connection and routing calls from a 4.0.4 system and a 4.2 system via a site-to-site rule.
Both my sipx systems can resolve each others DNS SRV records, ping and traceroute to each other via the ipsec connection. When initiating a call from 4.2 to the remote system, it fails with "Too Many Hops". In doing a trace, I see the Record-Route: with the internet ip address for my 4.2 system. When I created the unmanaged gateway, it does not use the built-in sbc, so why is it getting involved with the call routing? I have seen identical issues when using a sip trunk or unmanaged gateway. While I think this should be a simple configuration, I find that everything I do shows me that the built-in SBC is part of the record-route and hence it tries to traverse nat.Why is that? Is what I am trying to do outside the design? It will work over the native Internet traversing NAT in either direction, but it will bypass the SBC for an ipsec connection. I don't understand. -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
