Session border controller
CarrierX SBC
Multi-tenant session control on the network CarrierX owns. Software based and billed per minute, with no port fees or software licences.
Trunk group
Example
- Routing
- Weighted, 70 / 30 across two trunks
- Failover
- SIP failure codes and OPTIONS
- Codecs
- AMR-WBG.722G.711 µ-law
- Transcoding
- On
- Identity
- STIR/SHAKEN preserved
- Limits
- 50 CPS · 2,000 channels each way
Built through the API, with no provisioning wait
Exchange
One multi-tenant exchange between every party
- Multi-tenant and isolated from the start, not a tenancy layer on single-tenant hardware
- Aggregate your long tail of carriers behind a single interface
- Every party sends and receives the way it already supports, and CarrierX normalizes between them
- Peer with other exchange members, or bring your own private peers for us to mediate
- Full B2BUA on every leg, so neither side sees the other's network; media bypass where the topology allows
- Carriers
- Mobile operators
- MVNOs
CarrierX SBC
Normalizes between every pair
- CLECs
- Voice service providers
- Platforms
- Enterprises
Control
Routing and policy set on each trunk group
- Route by prefix, source trunk group or failover priority, or use weighted round-robin to split traffic by percentage
- Transform headers and digits at the trunk or trunk-group level
- Dead-trunk detection from SIP failure codes and OPTIONS monitoring, with cooldown and last-resort behaviour
- Post any call to your own routing engine and act on its response, for time-of-day or any other custom logic
- Per-trunk codec lists, wideband list, identity mode, ring control, RTP timeout and capacity
Trunk groupand its trunks
- Prefix, source, failover and weighted routing
- Header and digit transformations
- External routing handlers
- Codec lists and a separate wideband set
- Identity mode and ring control
- Capacity and access control
Fraud controls
STIR/SHAKEN and call limits on every trunk
- Calls arriving from a peering partner can be signalled as such
- STIR/SHAKEN preserved end to end: Identity headers are not signed, re-signed or stripped
- CPS and channel counts limited per trunk, in each direction
- Access control rules per trunk and trunk group, by number pattern and direction
Codecs
Wideband audio that works with the switches you already run
- Interoperates with off-the-shelf switches and custom application stacks
- Workarounds for the AMR-WB problems common in deployed SIP and RTP stacks
- Flexible codec negotiation profiles for the highest quality each side supports
- Cost-efficient transcoding, with no per-port licence fees
NarrowbandG.711 µ-law, A-law, G.729
WidebandAMR-WB, G.722, Opus, SILK
Works with
- Cisco
- Ribbon / Sonus
- Lucent
- Asterisk
- FreeSWITCH
Connectivity
Trunks built through the API, on the transport you choose
Trunk builds are API-driven and immediate, with no separate physical or network provisioning to wait on. You can change transport later, or move to transcoder-free operation as the far end allows, without onboarding again.
Transport
- Direct interconnect (PNI)
- Megaport
- IPsec VPN
- Public internet
Protocol
- SIP over UDP, TCP or TLS
- RTP and SRTP
- DTMF via RFC 2833
Codec
- AMR-WB, G.722, Opus, SILK
- G.711 µ-law, A-law, G.729
- Transcoding and media normalization
Example
Voice transit for mobile operators and their partners
Originating and terminating calls both pass through the partner before the call is set up, so each partner sees its own SIP traffic.
- A dedicated trunk group from the operator's core, on its existing physical connectivity
- Each partner on its own CarrierX account, with its own configuration and self-management
- Routing from the operator to each partner by trunk group, port-based forwarding or per-number provisioning
- Adding a partner changes nothing on the operator's side, because all traffic arrives normalized to the same profile
Mobile operator core
Existing trunk group
CarrierX SBC
Normalize and route
Partner
Its own CarrierX account
- On-net subscriber
- Partner's existing termination
- CarrierX termination
Getting started
How to get started
01
Technical deep dive
Architecture, routing and media handling, worked through with our engineers.
02
Lab interop
A test trunk group, end to end, against your own equipment.
03
Commercial discussion
Structure and terms for your traffic.
Contact us
Own your network with CarrierX
Talk to our team about how CarrierX can restructure your communications costs and put you in control.