Software Session Border Controller (SBC): Overview, Application Scenarios, and Practical Implementation Experience

Session Border Controllers (SBC) are devices or software deployed at network boundaries to control SIP sessions, providing functions such as protocol conversion, codec translation, NAT traversal, topology hiding, and security enforcement, effectively acting as a firewall for VoIP traffic.

The article identifies three primary SBC application scenarios: (1) SIP inter‑office networking between enterprises or headquarters and branches; (2) SIP client access where client devices connect to the IP voice network via an SBC proxy; and (3) carrier IMS integration for SIP trunking and voice‑over‑IP interconnection.

To meet internal requirements, the authors chose an open‑source, software‑based SBC approach, leveraging Linux virtualization and container technologies for performance and flexibility.

1. Mobile Softphone VAG (VoIP Accessing Gateway) – By combining OpenSIPS and RTPProxy, VAG enables mobile app clients to register, initiate calls, perform SIP/NAT handling, and exchange RTP streams through the SBC. Key steps include SIP registration forwarding, INVITE relay with NAT handling, media path setup via SDP, and session termination via BYE. Common issues involve SIP NAT traversal (requiring correct public address configuration) and RTP address mismatches causing one‑way audio.

advertised_address = "x.x.x.x" advertised_port = 5060

2. Internal Branch Network VIG (VoIP Interconnect Gateway) – Using FreeSWITCH, VIG connects separate corporate voice networks via SIP trunks, handling protocol adaptation, codec conversion, and topology hiding. It simplifies internal communication, improves security, and abstracts underlying voice systems. Issues include NAT handling (minimal for dedicated lines), protocol compatibility, and numbering conflicts, which are mitigated by number mapping and prefix insertion.

3. SIP Voice Trunking Gateway (VTG) – VTG integrates carrier SIP trunking with internal phone systems, also built on FreeSWITCH. It requires dual network interfaces for external carrier connectivity and internal routing, and addresses SIP/RTP NAT when the carrier provides a public IP. High‑concurrency testing is performed with SIPp, and high‑availability is achieved via virtual IP failover using keepalived (or heartbeat). Additional challenges such as in‑band DTMF support for G711 codecs are discussed.

In conclusion, the software SBC solution supports deployment on both private and public clouds, offers performance and business‑layer monitoring, real‑time data persistence, and standard data interfaces, aiming to become a professional, scalable SBC offering for future 5G and IMS networks.