Sangoma SBC SIP Trunking Enterprise Scenario

Local and long distance dialing charges are greatly reduced by using Voice over Internet Protocol (VoIP) delivered via SIP trunks, rather than legacy Public Switched Telephone Network (PSTN) via TDM trunks. SIP trunks also allow for much greater flexibility. For example, in addition to just voice, Unified Communications (UC) can be delivered, including presence, video conferencing, file sharing and screen sharing.

However, using VoIP over a public medium such as the internet does open both the Internet Telephone Service Provider (ITSP) network and the corporate network to vulnerabilities that must be properly addressed. Just as the firewall protects the data network, an SBC is required to protect both the data and voice network when VoIP is integrated into the system.

The example shown in Figure 1 illustrates a legacy PBX on the corporate premises which has been converted to use SIP trunks rather than TDM trunks. In this example, the SIP trunks are provided by the ITSP and delivered over the internet. A Vega gateway converts between SIP and the TDM interface used by the PBX. An SBC guards against toll fraud and navigates across the firewall. It also protects the corporate network.

The ITSP protects its network with a carrier class Session Border Controller (SBC) that is designed to handle the high call volumes that the carrier will experience and provide the High Availability (HA) features required for carrier operations. The corporate network is protected by a Vega eSBC (enterprise SBC) which is sized to handle moderate call volumes. Both SBCs provide the same functionality, including prevention of toll fraud, denial of service and eavesdropping. They enable VoIP traffic to navigate firewalls and ensure interoperability between different SIP implementations.

¿Necesitas más ayuda?
No dudes en ponerte en contacto con nosotros aquí.

¿Te resultó útil?

Has indicado que este tema no te resultó útil...
¿Puedes decirnos por qué? ¡Gracias!
Gracias por darnos tu opinión.