Enterprise Session Border Controller (SBC)
Yeti Switch can act as an enterprise Session Border Controller (SBC) at the edge of your network, connecting your PBX or unified communications platform to external SIP trunk providers and the public phone network — securing, normalizing, and routing all of your external voice traffic on one platform.
Get started · Try the live demo · Browse the documentation
Features for an enterprise SBC
- Security at the border — TLS signaling and SRTP media encryption, topology hiding (full B2BUA), and access control so internal systems are never exposed directly to providers.
- Interoperability — normalize SIP headers and translate numbers between your PBX and each carrier, and transcode between codecs when endpoints disagree.
- Multi-trunk resilience — connect several SIP trunk providers at once, with least-cost routing and automatic failover.
- One point of control — a single platform for all external voice connectivity, with detailed CDRs for every call.
- Carrier-grade — runs behind the Yeti load balancer for high availability.
- Open source — public packages, source code and documentation.
Explore the related documentation: Gateways · Codec Groups · Routing Plans · Headers transit · Numbers translations
Frequently asked questions
What is an enterprise Session Border Controller (SBC)?
An enterprise SBC sits at the edge of a company network, between the internal PBX or unified communications platform and external SIP trunk providers. It secures signaling and media, hides internal topology, normalizes SIP and codecs for interoperability, and routes calls across one or more carriers.
Can Yeti connect our PBX to multiple SIP trunk providers?
Yes. Yeti can front any SIP PBX or UC platform and route calls across several SIP trunk providers at once, with least-cost routing and automatic failover if a provider becomes unavailable.
Is Yeti an open-source enterprise SBC?
Yes. Yeti Switch is an open-source SBC and softswitch with public package repositories and open documentation.