200ms agents on your 3CX lines.
Bland runs the full voice stack itself, so agents answering your 3CX DIDs and extensions respond in 200 milliseconds and call data never passes through a third-party AI provider.
Bland + 3CX
Connect 3CX to Bland over a SIP trunk and put 200ms voice agents on your DIDs and extensions, with transfers straight back to your 3CX users.
What Bland does inside 3CX.
Guided 3CX setup.
3CX is in the SIP setup wizard's provider catalog. Enter your 3CX SIP trunk FQDN and the wizard works out host, port, and transport.
Discovery recognizes 3CX.
Auto-discovery probes your endpoint with SIP OPTIONS and detects 3CX, along with the codecs and methods it supports.
Register or trust by IP.
Use IP-based auth, or have Bland register with 3CX over SIP REGISTER. Bland can generate a strong password that pastes into 3CX without escaping.
Extensions, not just numbers.
Attach DIDs and dial-plan extensions like 2001 alongside E.164 numbers, each with its own inbound and outbound configuration.
Transfers to 3CX users.
Send a caller to a 3CX extension with SIP REFER so your PBX places the call, or have Bland bridge it or run a warm transfer.
How it deploys.
Start a trunk.
At All agents, open Dispatch, then Phone numbers, then SIP, click Add trunk, and choose 3CX.
Enter the 3CX FQDN.
Paste your 3CX SIP trunk FQDN and let discovery confirm the port, transport, and detected system.
Open the firewall and authenticate.
Allow-list Bland's signaling and media IPs, then choose IP-based auth or registration with a generated PBX-safe password.
Attach DIDs and extensions.
Attach the DIDs and extensions the agent should answer, press Test connection, and place a test call.
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 connect an AI voice agent to 3CX?
Yes. Bland connects to 3CX over a standard SIP trunk. Add a trunk in the Bland SIP setup wizard, choose 3CX, enter your SIP trunk FQDN, allow-list Bland's IPs, and attach the DIDs or extensions you want the agent to answer.
Which address do I enter for 3CX?
Your 3CX SIP trunk FQDN. The wizard also accepts hostnames, IPs, full SIP URIs, or shorthand like tls://host, and works out host, port, and transport. Discovery then recommends the port and transport and reports the detected system.
Does Bland support SIP registration with 3CX?
Yes. Choose registration-based auth and Bland registers with 3CX using a username and password, returning a derived password to configure in 3CX. IP-based auth is the recommended alternative and needs no credentials.
Can the agent transfer a caller to a 3CX extension?
Yes. Turn on Allow SIP/DID targets on a Transfer Call node and enter the extension, for example 2001. With SIP REFER on, 3CX places the call to the extension; otherwise Bland sends a new INVITE or runs a warm transfer.
What does my firewall need to allow for 3CX?
TLS on port 5061 to Bland's signaling IPs, and UDP 16384 to 32768 to and from its media IPs, for your region. Bland's SIP edges encrypt every call with TLS and SRTP, so enable both on the 3CX trunk.
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.