Now you are in the deep dark places of the SIP Protocol with RFC 3261 and the multiple dozens of SIP Protocol RFC extensions. You are trying to accomplish multiple vendor integration, trying to leverage the equipment and solutions available, and each vendor has completely different SIP Protocol requirements. Different URIs, AOR, PAI, FQDNs, IP Addressing, and so much more.
You need an “all-purpose tool”, one that accepts all the different variations of the SIP being sent and provides the ability to rewrite every possible header and field within the SIP protocol messages. This ability enables an Enterprise to be less vendor dependent, and thus, opens up the flexibility of the solution to inter-connect with any other vendor.
The SBC is the key component in this multi-vendor scenario. Multiple IP-PBXs, carriers, phones, and other UC applications can all be inter-connected seamlessly with an SBC. Your SBC should allow you to rewrite the SIP protocol (and in the process, become less reliant on vendor certifications and recommendations) and focus on providing a solution that works for the uniqueness of your business requirements.
|Download this printable PDF Cheat Sheet for your reference on the powerful capabilities and features of the Session Border Controller.|