200ms agents in your dial plan.
Calls your Asterisk or FreePBX dial plan sends to Bland reach agents that respond in 200 milliseconds, on a voice stack Bland hosts end to end.
Connect Asterisk or FreePBX to Bland over SIP and put 200ms voice agents on your DIDs and extensions, with transfers straight back into your dial plan.
Calls your Asterisk or FreePBX dial plan sends to Bland reach agents that respond in 200 milliseconds, on a voice stack Bland hosts end to end.
Asterisk and FreePBX are a guided provider in the SIP setup wizard. Enter your public IP or hostname to start.
Discovery resolves A, AAAA, and SRV records, probes SIP ports, and detects Asterisk or FreeSWITCH along with supported codecs.
The password generator avoids ambiguous characters and anything that needs escaping in a PBX config or SIP URI, so it pastes safely into Asterisk.
Attach extensions like 2001 to the trunk, and point Transfer Call nodes at an extension or a SIP URI such as sip:2001@pbx.example.com.
Map call variables to SIP headers on the trunk's outbound mapping, and they ride along on transfers to your Asterisk box.
At All agents, open Dispatch, then Phone numbers, then SIP, click Add trunk, and choose Asterisk / FreePBX.
Use the public IP or hostname of your Asterisk or FreePBX server and let discovery recommend port and transport.
Trust Bland's signaling and media IPs as SIP peers, or set up registration with a generated password, and save the trunk.
Attach the DIDs and extensions to route, press Test connection, and call an extension routed to Bland.
Our FDE team scopes the integration, maps Bland to your stack, and stays on through go-live. Enterprise deployments go live in 30 days.
MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly.
Yes. Add a SIP trunk in the Bland setup wizard, choose Asterisk / FreePBX, and enter your public IP or hostname. Attach the DIDs or extensions to route, and calls your dial plan sends to Bland are answered by a Bland agent.
Bland works with any standard SIP endpoint. Discovery detects Asterisk, FreeSWITCH, Kamailio, 3CX, and Cisco, among others, and recommends the port and transport. Asterisk and FreePBX have a guided entry in the wizard; others use Other.
Trust all of Bland's media IPs as SIP peers, since transfers connect from them, and enable SRTP on the trunk toward Bland. A 403 means an IP is missing from the trust list; a 488 means SRTP is off.
Yes. Target an extension or SIP URI from a Transfer Call node, and map call variables to SIP headers on the trunk's outbound mapping. With SIP REFER, have your PBX copy those headers onto the new INVITE, or switch REFER off and Bland sends them directly.
Yes. A SIP trunk carries the numbers on your own carrier, so they stay where they are. Bland also supports porting numbers in if you would rather move them, which typically takes 7 to 14 business days.
See every integration on the integrations hub.
They map Bland to your stack, design the rollout, and stay on through go-live. Enterprise deployments go live in 30 days.
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.