Enterprise-grade by default.
Bland is SOC 2 Type II and HIPAA ready, encrypts every SIP connection, and runs its own voice stack, so agents on your Cisco DIDs respond in 200 milliseconds.
Bland + Cisco UCM and CUBE
Connect Cisco Unified CM or CUBE to Bland over encrypted SIP and put 200ms voice agents on your DIDs, with transfers to extensions inside your network.
What Bland does inside Cisco UCM and CUBE.
Point at your gateway.
Cisco UCM and CUBE are a guided provider in the SIP setup wizard. Enter your gateway address and discovery takes it from there.
Cisco detected automatically.
Discovery probes the gateway with SIP OPTIONS and identifies Cisco, the codecs it offers, and the transport to use.
TLS and SRTP end to end.
Bland encrypts signaling with TLS on port 5061 and media with SRTP, so enable both on the trunk toward Bland.
G.729 and friends.
Reorder or disable PCMU, PCMA, Opus, G.722, and G.729 per number to match what your gateway negotiates, with optional transcoding.
Transfers inside Cisco.
Send callers to a DID, extension, or SIP URI with SIP REFER, a new INVITE, or a warm transfer with a briefing.
How it deploys.
Start a trunk.
At All agents, open Dispatch, then Phone numbers, then SIP, click Add trunk, and choose Cisco UCM / CUBE.
Enter the gateway address.
Paste your CUBE or UCM gateway address and let discovery recommend port, transport, and codecs.
Trust Bland as a SIP peer.
Allow-list Bland's signaling IPs and all media IPs, since transfers and consult calls connect from the media IPs.
Attach numbers and test.
Attach DIDs and extensions, press Test connection, and run a call that ends in a transfer.
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 Cisco CUBE route calls to an AI voice agent?
Yes. Build a SIP trunk in the Bland setup wizard, choose Cisco UCM / CUBE, and enter your gateway address. Attach the DIDs or extensions to route, and calls your Cisco environment sends to Bland are answered by a Bland agent.
How should CUBE media be configured for Bland?
Enable SRTP on the trunk toward Bland and run signaling over TLS on port 5061. Bland encrypts audio and signaling on every call, so a 488 Not Acceptable Here means the CUBE side offered plain RTP.
Which Bland IPs should CUBE trust?
Trust Bland's signaling IPs and all of its media IPs for your region as SIP peers. Transfers and warm transfer consult calls connect from the media IPs, so a 403 with no 401 or 407 first means one is missing.
Does Bland support G.729 with Cisco?
Yes. Per-number codec settings let you reorder and enable or disable PCMU, PCMA, Opus, G.722, and G.729, with optional transcoding, so you can match what your Cisco gateway negotiates.
Who actually wires this up?
Our FDE team scopes the integration, works with your voice team on the trunk, 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.