Prepare the correct platform configuration
Bandwidth’s Build SIP guide describes realms and prioritized inbound routes. For Universal Platform, use its Voice Configuration Package guide. Do not combine their configuration instructions.
Review the candidate route
1
Inventory the existing number route
Record the platform, number assignment, current destination, and fallback. In Build, selecting SIP Trunking for a number changes its handling away from Voice API traffic, so review existing applications before making that change.
2
Collect the SIP boundary
For Build, collect the realm and its SIP credentials, then review the route endpoints and their priorities. For Universal Platform, obtain the routing details associated with the intended Voice Configuration Package.
3
Map the Threetone candidate
Compare the resulting destination, source restrictions, authentication, transport, and media requirements with the SIP reference. Do not put management API credentials in SIP fields.
4
Prepare release evidence
Require a supported runtime destination and credential handoff. Define separate inbound, outbound, and fallback tests before moving an existing number.
Failure handling
If calls disappear after a routing change, inspect the number’s selected service and associated route before editing the agent. For failover problems, check endpoint priority and the provider’s result for the primary destination. Preserve the prior configuration for rollback.Frequently asked questions
Can I follow either platform's instructions?
Can I follow either platform's instructions?
No. Use the documentation that matches your Bandwidth account and product.
Does a saved generic SIP record switch my Bandwidth number?
Does a saved generic SIP record switch my Bandwidth number?
No. Threetone import does not change number routing or provision provider resources.