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

# Bandwidth SIP trunk

> Route Bandwidth numbers to the platform using account-specific signaling IPs

## Recommended profile

In Bandwidth, route the number's Voice Configuration Package to the platform SIP FQDN. In the platform, use the exact DID in `+E.164` and select **Provider source IPs**.

<Warning>
  Bandwidth does not provide one safe global signaling allowlist for this setup. The address depends on the account, zone, product, and trunk group, and can change during SBC migrations.
</Warning>

Open the Bandwidth App and copy **every signaling IP** for the relevant entry under **Account → Trunk Group Configurations**. Choose the addresses for the transport in use; standard SIP and SIP-over-TLS can use different endpoints. Do not substitute media ranges or an address copied from another Bandwidth customer.

Bandwidth's documented digest realm is for customer-to-Bandwidth termination. For Bandwidth-to-platform delivery, authenticate by the account's current source IPs unless Bandwidth explicitly enables a different downstream method for your account.

## Validate

Call the exact DID externally. Confirm a new inbound record, the assigned assistant, and two-way audio. Save a screenshot or export of the current Bandwidth trunk-group addresses with the setup record so future changes can be compared safely.

Sources: [Bandwidth Vapi integration](https://dev.bandwidth.com/docs/voice/integrations/vapi/), [Bandwidth Voice Configuration Packages](https://dev.bandwidth.com/docs/universal-platform/create-a-vcp/). Accessed 22 August 2026.