What is a Session Controller (SBC)? Part II: Connectivity and Interoperability 2022-12-09

VoIP knowledge

What is an SBC? Part II: Connectivity & Interoperability

  • Today, more and more companies are choosing unified communications and SIP-based VoIP telephone systems as communication solutions. However, connectivity issues in complex networks such as multi-site locations and remote work, or interoperability problems between different networks, SIP endpoints and SIP servers, IP PBX remain their puzzles. The SBC session controller, as a critical component of VOIP networks, is designed to solve connectivity and interoperability problems, ensure the stability of your IP telephone systems and the continuity of your business.
    In this article, we will share how the SBC can perfectly solve the problems of NAT traversal, inter-network communications, and compatibility between different terminals and various SIP servers.
    Session Border Controller—SBC, as a key component of VoIP business in the new telecom era, is specifically designed to address network security issues, NAT/Firewall traversal, QoS assurance, and interconnection of various SIP server platforms worldwide!
    In this document, we are pleased to share how the Dinstar SBC can perfectly solve the problems of enterprises crossing NAT, inter-network communications, and compatibility of different terminals and various SIP servers.
    Challenges of SIP-based audio/video communication
    SIP NAT/firewall traversal RTP NAT/firewall traversal Detection and handling of abnormal packets Compatibility with various SIP endpoints/terminals Compatibility with different SoftSwitch platforms Conversion of various protocols and codecs
    Voice absent/unidirectional voice issues caused by NAT between different subnets
    sbc-Compatibility_1.png
    Compatibility issues with SIP endpoints, IP PBX, SIP servers and softswitches from different vendors
    sbc-Compatibility_2.png
    How the SBC overcomes the above obstacles
    A major feature of the SIP protocol is its openness, which gives different manufacturers room for customization and flexibility based on SIP specifications. Unfortunately, this also leads to compatibility issues in interconnections of various SoftSwitches, IP PBXs, and different SIP endpoints from various vendors. Additionally, the complexities of enterprise networks, such as NAT traversal and firewalls, can cause SIP signaling and media failures when crossing these networks.
    The SBC is designated as a B2BUA (back‑to‑back user agent) located at the network edge. It can perfectly handle traversing various NATs and firewalls in call services. Like a surgeon’s scalpel, it can perform traffic control, monitoring, identification, modification of SIP headers or even their removal, as well as manipulation of media information in the SDP of the SIP signaling session, ensuring smooth session establishment between various endpoints, interconnection of signaling and media, realization of various call services, and VoIP services guaranteeing quality.
    What magic tricks does the Dinstar SBC have?
    1. NAT/firewall traversal for SIP signaling and media
    SBC NAT Traversal
    sbc-Compatibility_3.png
    SBC as a media proxy in multi‑NAT networks
    sbc-Compatibility_4.png
    1.1 Local NAT Function
    In the scenario where the SBC is deployed behind the enterprise firewall and communicates with the outside via translation, it may happen that the SBC does not receive messages sent by the external network.
    Dinstar SBC Solution
    The "Local NAT" feature ensures that the SBC behind the firewall can normally receive SIP signaling and RTP media streams from external network users or SIP trunk service providers. You can enable local NAT configuration in the SBC or trunk access network: set the firewall’s public IP; the SIP signaling NAT listening port; the RTP media NAT port range. With local NAT enabled, the SBC uses the configured public IP and NAT port in the SIP Contact header, as well as the SDP media information. This mechanism ensures NAT traversal for signaling and media.
    See the configuration screenshot below for more details :
    sbc_c_5.png
    1.2 Adaptive auto‑reporting/media function
    Due to the deployment of DMZ/NAT firewalls in call services, the address in VIA/FROM/TO/Contact/SDP of SIP messages from the intranet SoftSwitch or remote SIP terminals may be inconsistent with the actual IP address. Additionally, potential changes or refreshes of media information during the call can result in an incorrect address or invalid port for signaling/media interaction, ultimately leading to call establishment failure.
    Dinstar SBC Solution
    With the “Auto‑Adaptive Media/Signaling” feature: unlock the media and signaling address, support remote media refresh, the Dinstar SBC will automatically learn the media path of the NAT network on the peer side, ensuring intercommunication of signaling/media between the two parties.
    sbc_c_6.png
    2. Process of abnormal SIP packets
    2.1 SIP Signaling Traffic Control
    The SBC can dynamically verify incoming SIP signaling messages in real time. If it detects abnormal signaling messages from a certain IP or account, it can block them or even add them to a blacklist based on the configured threshold and criteria.
    2.2 SIP packet format detection
    The SBC will verify the content format of all received SIP packets and automatically reject packets with missing key fields, unreadable content, incorrect "call-id", incorrect "to tag", incorrect Cseq, and any other malformed format.
    3. UDP/TCP/TLS Interoperability
    The SBC sits at the boundary of different networks and is connected to various VoIP service providers. The transmission protocols used by the different networks may be inconsistent. The SBC can convert communication protocols such as UDP to TCP, UDP to TLS, ensuring session connectivity between different networks, enterprises, and service providers.
    4. WebRTC Gateway
    The Dinstar SBC is also a WebRTC to SIP gateway, providing seamless connections between WebRTC clients and the enterprise unified communications system. More details on WebRTC will be covered in our next article.
    5. IPv4 and IPv6 Interoperability
    Users may encounter issues such as a LAN in IPv4 and a WAN in IPv6. The Dinstar SBC supports IPv4/IPv6 interoperability for media and signaling. Different SIP endpoints or SIP servers, whether they use IPv4 or IPv6 addresses, can be connected transparently via the SBC.
    6. Protocol Conversion
    The primary operating mode of the SBC is B2BUA (proxy back-to-back). For example, some clients use TLS encryption, others use WebRTC, but the company's central network server only supports UDP. The SBC can then convert the different protocols to correctly establish session communication between the company and various clients.
    7. Voice codec transcoding and seamless video transmission
    7.1 Voice Transcoding
    In real call service, different SIP terminals and SIP server/IP PBX/SoftSwitch platforms can use different codecs. The SBC will automatically transcode codecs if the voice codecs negotiated by the terminal device differ from those supported by the central server (e.g., G.711 to G.729). Thus, it ensures successful voice call interaction.
    7.2 DTMF Transcoding
    The SBC automatically detects the DTMF mode used in the call negotiation by both parties. If the two parties use different DTMF modes, for example, the caller sends DTMF signals Inband while the recipient only supports RFC2833, the SBC will automatically transcode between Inband and RFC2833 modes. This ensures successful business interaction with different DTMF modes.
    7.3 Transparent Video Transmission
    The SBC supports video calls. After enabling this feature, it can automatically transmit video information from both parties and enable video call services.
    8. SIP compatibility processing methods
    8.1 SIP header transmission
    The SIP protocol has strong scalability to connect different SIP servers and various service types. Some manufacturers can add extension header fields to implement special services. The SBC can transparently pass SIP headers or ignore them based on designated services (e.g., History‑Info, user‑agent headers).
    8.2 SIP method compatibility
    If the request methods supported by both parties differ, the SBC can use B2BUA mode to implement unilateral signaling interaction to ensure normal communication (e.g., PRACK/Session Timer/REFER/UPDATE/Re-INVITE/SUBSCRIBE/NOTIFY, etc.).
    8.3 Handling Oversized SIP Messages
    Some SIP messages sent by the server contain a lot of unnecessary content (such as the large SDP of a video conference), making the message too large and preventing the remote side from handling it. The SBC can filter out unnecessary headers and SDP media resource information, reducing the message length to a normal size.
    8.4 Business model compatibility
    Compatible with platforms such as IMS/Huawei/Avaya/Cisco/Genesys, including call hold, call transfer, call parking, three‑way conferencing and other services.
    8.5 URI Domain Delivery
    Some central SIP servers require registered users and calls to carry the domain name specified in the /FROM/TO request line, used for registration and call message authentication (e.g., IMS platform). The SBC can add the specific domain name to the SIP trunk and forward it to the central network.
    8.6 SIP header manipulation
    The content of SIP messages sent by some SIP servers and terminal devices is not standard. Or special values are required in connection with certain SoftSwitch/IP PBX/SIP server platforms. In this scenario, the SBC can modify/delete SIP header fields or the SDP body content.
    You may want to know
    Click to learn more about our SBC session controllers
    Click to learn more Why do you need an SBC?
    What is a session controller (SBC)? Part III: High Availability
    What is a session controller (SBC)? Part I: Enhanced VoIP/SIP security.