Your carrier, Bland's voice stack.
Your numbers stay on Vonage while Bland runs speech recognition, the language model, and voice on its own infrastructure, responding in 200 milliseconds.
Bland + Vonage
Keep your Vonage numbers and run Bland voice agents on them over encrypted SIP, with 200ms responses, automatic failover, and SIP traces on every call.
What Bland does inside Vonage.
Vonage in the wizard.
Vonage is a guided provider in the SIP setup wizard. Paste your Vonage SIP endpoint as a hostname, IP, or full SIP URI.
Two ways to authenticate.
Trust by IP with no credentials to manage, or register with a username and password, plus optional credentials on each INVITE.
Failover and failback.
List primary, secondary, and tertiary servers. Bland fails over on unreachable, auth failure, or timeout, and fails back automatically or manually.
Transfers over the trunk.
Send callers to a DID, extension, or SIP URI with SIP REFER, a new INVITE, or a warm transfer that briefs the receiving agent.
Regional edges.
Connect to the Bland edge closest to you in the US, Canada, Asia-Pacific, or Europe, each with static signaling and media IPs.
How it deploys.
Start a trunk.
At All agents, open Dispatch, then Phone numbers, then SIP, click Add trunk, and choose Vonage.
Enter your Vonage endpoint.
Paste the SIP endpoint and let discovery recommend port, transport, and codecs.
Open the firewall and authenticate.
Allow-list Bland's regional signaling and media IPs, then choose IP-based or registration-based auth.
Attach numbers and test.
Attach the Vonage numbers to automate, press Test connection, and place a test call in each direction.
Our FDE team scopes the integration, maps Bland to your stack, and stays on through go-live. Enterprise deployments go live in 30 days.
Drop Bland into your editor.
MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly.
curl -X POST https://api.bland.ai/v1/calls \
-H "Authorization: $BLAND_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"phone_number": "+14155552120",
"task": "Qualify refi lead",
"voice": "june"
}'
Frequently asked questions.
Can I use Vonage numbers with a Bland AI voice agent?
Yes. Connect Vonage to Bland with a SIP trunk built in the setup wizard, where Vonage is a guided provider. Attach your Vonage numbers to the trunk and Bland agents answer inbound calls and place outbound calls on them.
Can I keep my numbers on Vonage?
Yes. A SIP trunk carries the numbers on your own carrier, so they stay on Vonage. If you would rather consolidate, Bland also supports porting numbers in, which typically takes 7 to 14 business days.
What happens if a Vonage SIP server goes down?
Configure primary, secondary, and tertiary servers on the number. Bland fails over automatically when an endpoint is unreachable, fails authentication, or times out, and fails back automatically or manually.
Which Bland SIP region should I use?
The one closest to your infrastructure. Bland runs SIP edges in the US, Canada, Asia-Pacific, and Europe, each reached over TLS on port 5061 with its own static signaling and media IPs to allow-list.
Who actually wires this up?
Our FDE team scopes the integration, sets up the trunk with you, and stays on through go-live. Enterprise deployments go live in 30 days.
Related integrations.
See every integration on the integrations hub.
With our team
Our FDE team scopes the integration with you.
They map Bland to your stack, design the rollout, and stay on through go-live. Enterprise deployments go live in 30 days.
On your own
Or drop Bland into your editor.
The Bland MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly. Free sandbox, no credit card.