A SIP trunk is the connection your phone system uses to place and receive calls. Trunks here are managed objects: you create one, adjust it, and remove it when it is no longer needed - without a procurement conversation for each change. Running several trunks on one account is normal rather than exceptional, which is what you want when production and testing should not share a path.
Bring your own PBX
Standard SIP
API included
Create, update and remove SIP trunks from the portal, and run more than one trunk on the same account.
Trunks are self-serve objects
Create and change a trunk yourself rather than raising a ticket and waiting on a provisioning queue.
Run more than one
Separate trunks for production, staging or different sites, listed and managed together.
Change without rebuilding
A trunk's configuration can be updated in place as your setup evolves.
Remove what you stop using
Deleting a trunk is a normal operation, so unused capacity does not quietly persist.
End to end, in the order it actually happens.
Create a trunk from the portal.
Configure how your PBX will authenticate to it.
Point your PBX at the trunk and register or allow the IP.
Place a test call in each direction.
Attach numbers and move production traffic across.
Worth knowing before you build a process around it.
Replacing PRI lines
Connecting an on-premise PBX
Separating test and production voice paths
Adding a second site
SIP Credentials & Rotation
Reveal your trunk's SIP password when you need it, and rotate it without rebuilding the trunk.
Learn moreGateway Configuration
Define the gateways your calls traverse, and keep several configured so a route is a configuration change rather than a rebuild.
Learn moreNumbers on Your Trunk
Attach numbers to a trunk and change which trunk each one points at, without republishing the number.
Learn moreA SIP trunk is the connection your phone system uses to place and receive calls. Trunks here are managed objects: you create one, adjust it, and remove it when it is no longer needed - without a procurement conversation for each change. Running several trunks on one account is normal rather than exceptional, which is what you want when production and testing should not share a path.
1. Create a trunk from the portal. 2. Configure how your PBX will authenticate to it. 3. Point your PBX at the trunk and register or allow the IP. 4. Place a test call in each direction. 5. Attach numbers and move production traffic across.
Provisioning creates the trunk. Configuring your own PBX to use it correctly is still your side of the connection. This is provisioning, not a guided setup wizard - expect to work from the connection details rather than a walkthrough. Porting an existing number onto the trunk is a separate question; do not assume it is supported.
BPO, Hospitality, Manufacturing, Healthcare. Typical uses are replacing pri lines, connecting an on-premise pbx, separating test and production voice paths, adding a second site.
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.