Improving the business case for UC using SBCs
For any CIO looking to build their business case for a UC implementation, an SBC must be considered part of the solution. We recommend using the following arguments:
- SBCs integrate with existing IP-PBX platforms: For enterprises looking to protect legacy investments, SBCs play a vital intermediation between UC voice platforms and existing IP-PBX systems. SIP normalization allows a smooth integration between the voice network and the IP PBX. For enterprises with a disparate IP-PBX base including equipment from multiple vendors, the SBC is able to normalize, transcode and translate the various SIP variations. This ensures calls are routed correctly with the most efficient use of the network at the lowest cost.
- SBCs ensure QoS: Particularly with voice communications, it is vital that sound quality is not degraded and there is no delay on the line when people are trying to communicate. SBCs can decide which calls can be allowed at what time to keep the network running smoothly during busy periods and monitor the network's health in terms of latency, jitter and other metrics.
- SBCs secure communications at every stage: Denial-of-Service attacks, caller ID spoofing, toll fraud, attempts to steal secrets - all of these things should be considered when deploying UC. An SBC should be able to provide Denial of Service (and Distributed Denial of Service) prevention, topology hiding, rogue RTP encryption, media encryption, signalling encryption, NAT traversal - everything you need at every stage.
Sign up for CIO Asia eNewsletters.