Carriers are configurable objects on the platform, so you can define and manage the carrier your traffic uses rather than being confined to a single upstream. If you already hold negotiated rates or a contractual commitment with a carrier, this is what lets you keep that commercial relationship while still using the platform's routing, logging and application layer.
Bring your own PBX
Standard SIP
API included
Keep your existing carrier relationship and rates, and run the traffic through your own configured carrier rather than ours.
Keep negotiated rates
An existing carrier contract stays useful instead of being stranded by a platform migration.
Carriers are managed objects
Create, update and remove carrier configurations as your arrangements change.
More than one carrier
Carriers are listed and managed as a set rather than a single fixed upstream.
Commercial and technical decoupled
Who you buy minutes from is a separate decision from what runs your call logic.
End to end, in the order it actually happens.
Create a carrier configuration with your provider's connection details.
Add the gateways that carrier routes through.
Attach the carrier to the trunk that should use it.
Test calls in both directions before moving traffic.
Worth knowing before you build a process around it.
Existing carrier contracts
Multi-carrier strategies
Regional carrier requirements
Cost optimisation on committed volume
Gateway Configuration
Define the gateways your calls traverse, and keep several configured so a route is a configuration change rather than a rebuild.
Learn moreTrunk Provisioning
Create, update and remove SIP trunks from the portal, and run more than one trunk on the same account.
Learn moreRouting Applications
Define what happens to a call once it arrives, and point different trunks or numbers at different behaviours.
Learn moreCarriers are configurable objects on the platform, so you can define and manage the carrier your traffic uses rather than being confined to a single upstream. If you already hold negotiated rates or a contractual commitment with a carrier, this is what lets you keep that commercial relationship while still using the platform's routing, logging and application layer.
1. Create a carrier configuration with your provider's connection details. 2. Add the gateways that carrier routes through. 3. Attach the carrier to the trunk that should use it. 4. Test calls in both directions before moving traffic.
There is no certified-carrier programme or published compatibility list. Whether a specific carrier works is established by configuring and testing it, not by consulting a list. Call quality across your own carrier is your carrier's responsibility - the platform routes to them, it does not improve their route. Commercial terms remain between you and that carrier.
BPO, Enterprise IT, Telecom Resellers, Manufacturing. Typical uses are existing carrier contracts, multi-carrier strategies, regional carrier requirements, cost optimisation on committed volume.
SIP trunking is a method of delivering voice calls over the internet using the Session Initiation Protocol (SIP). It replaces traditional PRI/ISDN lines, connecting your PBX or contact center to the public telephone network (PSTN) via an internet connection.
SIP trunking uses internet connectivity instead of physical copper lines. It offers elastic capacity (add or remove channels instantly), lower cost per minute, geographic flexibility, and no need for on-premise telco equipment. PRI lines are fixed at 30 channels and require hardware installation.
Elastic SIP trunking with per-minute pricing. Connect the PBX you already run.