Make sure the tests pass immediately after installation and before you file a trouble ticket. The sipXcom administration portal (sipXconfig) provides automated tests that allow the verification of proper configuration of all such network services. If you deploy sipXcom in a high-availability configuration the complexity of the DNS SRV configuration increases dramatically. sipXcom uses DNS SRV records, which requires proper setup. Please consult the respective information on how to configure such services to work with sipXcom. However, more often you already have DNS and DHCP services deployed on your network. It is possible to use the sipXcom server for such network services. sipXecs, including the complete sipXecs Web based management system, are licensed by SIPfoundry under AGPL with an additional Contributor Agreement. SipXcom does not work unless DNS and DHCP services are properly configured. sipX is a native SIP communications solution strictly following and implementing all the relevant SIP IETF standards. An SBC is required and we have typically used Acme Packet (now Oracle), Sangoma or Frafos ABC SBC for this purpose. SIP Trunking requires both near-end NAT traversal as well as interoperability with the ITSP providing the SIP trunking service. Other products might require NAT traversal assistance at the far-end as well. Therefore, at the far-end there is no special equipment required and phones connected behind a traditional firewall/router will work fine. Some products, such as the Frafos ABC SBC or Sangoma SBC provide support for both. Remote worker configurations require both near-end and far-end NAT traversal assistance. This gets external SIP signaling and media off of the server allowing the server to scale better and provide a more reliable connection for Trunks and Remote workers. External Session Border ControllersĪ SBC is still recommended for most installations. The user should utilize a session border controller for this functionality. These services do not scale properly and do not support a HA configuration. Use of these services is only encouraged for Lab purposes only. There are two services utilized for this sipXrelay for NAT traversal and sipXbridge for trunking support. Up to and including sipXcom release 3.10 an external Session Border Controller (SBC) is required for NAT traversal.Īs of release 4.0 sipXcom includes native support for both remote worker configurations as well as SIP trunking. NAT traversal at the near-end or far-end represents a significant challenge for the SIP protocol as both signalling (SIP) and media (RTP) needs to be mapped to traverse NATs successfully. As long as all the hosts are reachable a routed network works fine and also network segments reachable via VPN are not a problem. As long as you have no NATs between the sipXcom server and all the phones and gateways there should be no challenges from a network topology perspective.
0 Comments
Leave a Reply. |