AudioCodes SBC under the Miercom microscope

Quite often companies prefer to keep their cards close to their chest, no need to open up the product for others to find its soft points. We decided to take a different approach and let an independent 3rd party company put our products under attack, pushing their performance, resiliency and security to their boundaries. We are now putting our cards on the table giving everyone access to the results of these tests. The full Miercom report can be found here.

For this purpose we asked Miercom to run our SBCs through their brutal tests and report their results.

Miercom is a US-based network consultancy company, specializing in networking and communications-related product testing and analysis.

The products to be tested were the Mediant 4000B, Mediant 9000 and Mediant Virtual Edition (VE) Session Border Controllers. End result is a certification we received from Miercom for our SBCs’ performance, scalability and resiliency while under attack and overload conditions. The tests also verified the SBCs’ WebRTC Gateway functionality and monitoring capabilities with AudioCodes Session Experience Manager (SEM).

The AudioCodes Mediant SBCs

AudioCodes’ Mediant family of Session Border Controllers (SBC) is a line of versatile IP communications platforms that connect VoIP and TDM networks. SBCs are deployed at the border between the enterprise and the service provider. In the enterprise environment, they form an effective demarcation point between the business’ VoIP network and the service provider’s SIP Trunk, performing SIP protocol mediation and media handling (interoperability) and securing the enterprise VoIP network. In the service provider core, SBCs provide security and protocol normalization. Given this role, the performance, reliability and security of the SBC is imperative for successful operation of enterprise and service provider voice networks.

Miercom findings

“AudioCodes’ SBCs exhibit rich interoperability along with impressive performance and resiliency.”

AudioCodes Mediant SBCs offer advanced security capabilities that enable security detection, protection and analysis. They have a built-in application level Intrusion Detection System (IDS) feature that detects and suppresses malicious attacks directed at the SBC. Reactions can include blacklisting the assaulting IP addresses for a user-defined period of time and/or sending alerts (SNMP traps) with full details of the suspected malicious activity.

“The Mediant SBCs have proved fully resilient against Distributed Denial of Service (DDoS) attacks on both signaling and RTP/media ports, maintaining excellent MOS ratings and with no dropped calls or system degradation.”

AudioCodes SBC VNF

Ideally, all of the functionalities that are available within an appliance-based SBC should also be available within a Network Function Virtualization (NFV) version. While this may seem straightforward, some vendors struggle to deliver due to legacy product architectures, which rely on hardware-specific feature implementations. This leads to challenges in assuring adequate performance and quality of service without purpose-built hardware.

AudioCodes Mediant VE can run as a Virtualized Network Function (VNF) in an NFV environment. It is one of the first SBC VNFs proven by Miercom to deliver effective protection against DDoS attacks, sustaining high performance while under heavy attack without sacrificing call quality.

AudioCodes NFV-based SBC provides full parity with traditional appliance-based SBC products, in large part because it has been available on leading industry x86 platforms since 2012. The virtual SBC design and software implementation allow it to protect against attacks without the need for purpose-built hardware.

To read the entire report, or for more details on how the tests were carried out, please refer to the full Miercom reports available on our website.

This post was written by

Learn more about this topic at scansourcecatalyst.com >Learn more about this topic at scansourcecommunications.com >

Leave a Comment

Previous post:

Next post: