http://sipx-wiki.calivia.com/index.php/SipX_Roadmap#SIP_trunking_gateway_and_near-end_.2F_far-end_NAT_traversal_for_remote_workers
Near-end / far-end NAT traversal support in the proxy ThesipXecs proxy server will natively support near-end and far-end NATtraversal in order to support remote workers and remote branch officesconnected without a VPN. This includes support for PATH header XECS-265.The NAT traversal capability is directly integrated into the sipXecsproxy server so that it can auto-detect dynamically whether an endpoint requires NAT traversal assistance or not. A media relay is addedto each proxy for anchoring the media as necessary. The NAT traversalcapability also works in a redundant system offering an HAconfiguration. >>> Michael LeBlanc <[email protected]> 02/10/09 1:28 PM >>> We're currently using OpenSBC to provide far-end NAT traversal for UAs on private networks. Reading though the sipXbridge wiki page, it seems to be intended for near-end NAT traversal -- but it mentions another service called sipxrelay. Could this service allow for FENT, eliminating the need for far-end NAT traversal proivided by OpenSBC? If sipXecs 4.0 will allow for FENT, will it support SIP SUBSCRIBE commands? We've noticed that OpenSBC doesn't support SIP SUBSCRIBE, so UAs connected via OpenSBC don't get presence. Cheers, Mike _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
