Skip to main content
Use your Bandwidth phone numbers with a Bland agent. A SIP trunk connects Bandwidth and Bland, so the agent answers inbound calls and places outbound calls on your Bandwidth numbers and network. Setup is configuration only, on both sides. No code.
Verified integration. Bandwidth built and tested this integration against the configuration on this page, on the Bandwidth Universal Platform. Integrations on Bandwidth’s legacy platform are supported best effort. Bandwidth publishes the same steps in its Bland integration guide.

What works

  • Inbound calls to your agent
  • Outbound calls from your agent
  • Transfers from your agent

Prerequisites

  • A Bandwidth Universal Platform account with Bland interconnect enabled. Open a ticket with your Bandwidth account representative, name the admin user who will configure it, and ask for a Bland integration
  • A Bland account with SIP trunking enabled. If there is no SIP tab under Phone numbers, contact Bland support

Configure Bandwidth

Bland needs a Bandwidth SIP endpoint for both directions, so create it even if you only plan to use one.
1

Create a SIP realm

In the Bandwidth App, go to Account, then SIP Credentials, then Manage Realms, and press Add. Name the realm, for example bland1.Bandwidth generates the realm’s FQDN, for example bland1-decce2.auth.bandwidth.com. Copy it exactly as shown.
2

Note your trunk group port

Go to Trunk Group Configurations and note the port assigned to your trunk group. It varies by account.Your SIP endpoint is the FQDN plus that port, for example bland1-decce2.auth.bandwidth.com:5239.
3

Route inbound calls to Bland

Go to Service Management, then Voice Configuration, and press Add Package. Name it, for example Bland.Under Routing, create the primary route, press Add endpoint, and set the type to Route to domain name. Enter Bland’s endpoint for your region, for example us2.sip.bland.ai:5061. The other regions are under Connection endpoints. Press Create Package.Open each number your agent should answer, select the package under Voice configuration package, and save. Many numbers can share one package.
4

Create outbound credentials

Skip this if you only need inbound calls.Go to Account, then SIP Credentials, and press Add. Enter a username and password, select the realm you created, and save.

Configure Bland

Every trunk the Bland wizard builds carries both directions, so create one even for inbound only.
1

Open the setup wizard

At All agents, go to Dispatch, then Phone numbers, then the SIP tab, and press Create trunk.
2

Provider

Pick Other and enter your Bandwidth SIP endpoint, for example bland1-decce2.auth.bandwidth.com:5239.
3

Firewall

Bandwidth has already allow-listed Bland on its side. Tick the box and continue.
4

Authentication

Pick IP-based, and leave Outbound routing on Via Bland’s carrier. Under Outbound call credentials, enter the username and password from your Bandwidth realm. Press Create trunk.
5

Numbers

Add each Bandwidth number in E.164 format, for example +19195551234.
6

Assign an agent

Under Phone numbers, press Configure on the number and pick the agent under Assignment.
You know it worked when a call to the number reaches the agent and shows up on the trunk’s Overview tab. For outbound, use the number as from in POST /v1/calls.
The wizard’s connection checks can report errors against a working Bandwidth endpoint. If they do, continue and confirm with a test call.

Common failures

The endpoint or credentials don’t match. The endpoint in Bland must match the realm FQDN exactly, and the username and password must match the credential assigned to that realm.
The endpoint or port is wrong. Copy the FQDN verbatim, and use the port from your own trunk group configuration.
The number isn’t on the Bland voice configuration package, or has no agent assigned in Bland. Check both.
Transport or media encryption doesn’t match. Bland requires TLS signaling and SRTP media.
Enter it in E.164 format, with the +.

Next steps

Transfers

Send callers onward from the agent.

Network and security

Bland’s regions, IPs, and TLS and SRTP.
Docs for agents: llms.txt