Add your SIP details
Enter the carrier hostname, port, transport, authentication, codecs, signaling IPs, and concurrency limit.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Bring Your Own Carrier
Connect your SIP carrier to PBXCall and keep the contracts, rates, and numbers you already trust. Your team still gets PBXCall routing, queues, IVR, analytics, recordings, and AI-powered workflows.
Overflow and new regions stay on PBXCall.
Keep numbers where they are
Migrate at your own pace
Consistent tools for every call
Guided setup
PBXCall keeps carrier changes deliberate. Nothing routes until the SIP endpoint is verified and you activate the connection.
Enter the carrier hostname, port, transport, authentication, codecs, signaling IPs, and concurrency limit.
PBXCall resolves the public endpoint and checks the signaling path before the trunk can be activated.
Add only the numbers that should use BYOC. Keep everything else on PBXCall for a controlled hybrid rollout.
Why BYOC
The carrier remains the call path. PBXCall becomes the operating system your team uses to route, answer, measure, and improve every conversation.
Preserve carrier contracts and volume commitments while upgrading agent tools.
Use approved local carriers in regulated markets without fragmenting workflows.
Calls still feed queues, recordings, dashboards, CRM context, and AI insights.
Route selected numbers through BYOC and use PBXCall carriers everywhere else.
Common questions
No. Your numbers and carrier contract stay in place. You route the selected numbers to PBXCall over SIP.
Yes. BYOC is configured per connection and number, so you can run a hybrid setup or migrate in stages.
PBXCall accepts UDP, TCP, and TLS signaling with PCMU, PCMA, G.722, and Opus. Carrier compatibility is checked before activation.
Keep the network you trust and give your team a modern communications workspace.