> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Bandwidth

> Identify the Bandwidth platform and SIP routing objects before preparing a future Threetone carrier integration.

Start by identifying which Bandwidth platform your account uses. Configuration differs between Build SIP Trunking and Universal Platform. Threetone has no Bandwidth-specific import variant or verified carrier adapter.

## Prepare the correct platform configuration

| Platform | Review with the account owner |
| - | - |
| Build SIP Trunking | Realm, SIP credentials, inbound routes, and number-level SIP selection. |
| Universal Platform | Voice Configuration Package, associated numbers, and the intended routing configuration. |

Bandwidth's [Build SIP guide](https://dev.bandwidth.com/docs/voice/sip-trunking/sip-getting-started/) describes realms and prioritized inbound routes. For Universal Platform, use its [Voice Configuration Package guide](https://dev.bandwidth.com/docs/universal-platform/create-a-vcp/). Do not combine their configuration instructions.

## Review the candidate route

<Steps>
  <Step title="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.</Step>
  <Step title="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.</Step>
  <Step title="Map the Threetone candidate">Compare the resulting destination, source restrictions, authentication, transport, and media requirements with the [SIP reference](/agents-platform/deploy/telephony/sip-reference). Do not put management API credentials in SIP fields.</Step>
  <Step title="Prepare release evidence">Require a supported runtime destination and credential handoff. Define separate inbound, outbound, and fallback tests before moving an existing number.</Step>
</Steps>

## 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

<AccordionGroup>
  <Accordion title="Can I follow either platform's instructions?" id="bandwidth-faq-platform">No. Use the documentation that matches your Bandwidth account and product.</Accordion>
  <Accordion title="Does a saved generic SIP record switch my Bandwidth number?" id="bandwidth-faq-switch">No. Threetone import does not change number routing or provision provider resources.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.