From the SIP Trunking Experts

March 11, 2014

Is Your VoIP Network Protected with Session Border Controllers?

By Susan J. Campbell SIP Trunking Report Contributing Editor

For companies who have taken the leap and embraced the benefits of VoIP, there are a number of different technologies they have actually accepted. Not only are they completing voice calls over the Internet, they are also investing in trunks, session border controllers, authentication, and so much more. Staying connected just got a little more complex.

For the end user, it doesn’t matter if they are completing the call over the traditional landline or a VoIP line provided by a third party. They can still pick up the same phone, dial the same phone numbers, and enjoy the same high quality connections they have come to expect. What’s happening on the backend, however, is what is ensuring this level of capability remains available and safe to use.

Companies like InGate are experts at providing the safe communications companies need in a VoIP environment. A recent post by the company highlighted the critical role session border controllers play in SIP trunking deployments. At the same time, there are a number of different providers and options on the market, making it more challenging to make the right choice.

Fortunately, the company provided a checklist you can use to ensure your final selection will actually meet your needs. Let’s take a look at what they have to say:

Know Your SIP – it’s important to know whether you have SIP or SIP Lite. It’s not uncommon for SBCs to refer to a modified version of SIP, which will fall short of the SIP standard. SIP SBCs should adhere to the industry standard and nothing less.

Will it Simplify Deployment – it is possible for the SBC to complicate the deployment process, especially if it takes considerable tie to configure. Look for an installation wizard that can help speed the process.

Interoperability – if the SBC doesn’t normalize the SIP signaling between the IP-PBX at the customer site and the service provider’s network, there’s a problem. The SIP-capable SBC will ensure the needs of the trunking implementation and authentication levels can be met.

Authentication and Encryption – the provision of both should be standard with the SBC. If it’s lacking, you’ll miss key standards within the service provider’s requirements and miss out on key privacy controls.

Deep Packet Inspection – this is a powerful way to protect SIP traffic, as well as the network. If your environment is at risk of DoS attacks, buffer overflow attacks and even sophisticated intrusions, this will be an important element to have in place.

To learn more about InGate’s SBCs and what they are doing in the market as of late, the company was on hand at ITEXPO. TMCnet’s Rachel Ramsey caught up with them on the show floor. To capture their conversation in full, check out this ITEXPO video.

Edited by Cassandra Tucker