We’ve discussed the need for session border controller (SBC) capability in VoIP and unified communications deployments, with a focus on improving security, transcoding, network management, and access control. However, there’s another good reason for using an SBC that our colleague Gary Audin covers in his latest tech note posted at Webtorials: business continuity.
In his piece, Audin notes that the Enterprise Session Border Controller (E-SBC) “can be configured to enhance the network survivability of a location when connected to SIP trunks.”
Explaining how to improve continuity when using multiple IP PBXs, Audin writes that the E-SBC can “connect to multiple IP PBXs or IP phone LANs or gateways to multiple SIP trunk providers. This is a capability normally associated with large communications sites. The common E-SBC can have 8 or more Ethernet ports, arranged as pairs for redundancy, which can be assigned in many configurations.”
He continues, saying “the E-SBC's physical Ethernet ports can be grouped into pairs where each pair group consists of an active port and a standby port. This provides Ethernet port redundancy within a group. If an active port is disabled, the E-SBC switches over to the standby port. This enables physical separation of network interfaces, providing a higher level of segregation of sub-networks. Two ports in a group can be configured to connect to the primary and backup IP PBX servers on separate LANs. If one server/LAN combination fails, the E-SBC can detect the failure and switch to the backup port in the group.”
Audin also looks at how to configure the E-SBC in the case of multiple SIP trunk providers, how to factor in multiple E-SBCs, and how to set up a network that includes both headquarters and branch locations—along with showing how the E-SBC can provide additional value.
You can read his full review by clicking here. Our thanks to Mr. Audin and to Webtorials for sharing this technical report.