Skip to content
Vobiz integration

Connect a Vobiz SIP trunk to Wixzel Voice

To run an AI voice agent on a Vobiz number, connect your Vobiz SIP trunk to Wixzel Voice: add the platform_ip your trunk returns to the IP ACL so outbound calls are accepted, and send inbound calls to its origination_uri so inbound calls arrive. Vobiz keeps billing you for the line at your rates; Wixzel Voice bills the voice engine per second from a prepaid balance.

Last updated

Published

Vobiz is the carrier; Wixzel Voice is the voice AI API that runs the agent on top of it. They work together over standard SIP. Vobiz is a trademark of its owner, and Wixzel Voice is not affiliated with or endorsed by Vobiz.

Create an accountFull setup steps

What do you need before you start?

  • A Vobiz account, and the host and credentials of the trunk.
  • A phone number you own at Vobiz, attached to that trunk. Wixzel Voice does not sell or port numbers.
  • A Wixzel Voice API key and some prepaid credit. The minimum top-up is $5; there is no free tier.
  • Wixzel Voice is in alpha and runs 5 concurrent calls per account by default, raised on request; web and app sessions count toward the same limit.

How do you create the Vobiz trunk in Wixzel Voice?

Vobiz auto-generates a SIP domain per trunk in the form <trunkId>.sip.vobiz.ai. Use that as the trunk host, not a bare IP.

cURL
curl https://api.voice.wixzel.com/v1/sip-trunks \
  -H "Authorization: Bearer $WIXZEL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Vobiz",
    "host": "<trunkId>.sip.vobiz.ai",
    "transport": "udp"
  }'

Add username and password to the body if Vobiz authenticates by credentials rather than IP. The password is encrypted at rest and never returned by the API again. The response carries platform_ip and origination_uri: the two values the next step needs.

What do you set at Vobiz?

SettingWhat Vobiz calls itValue
Allowlist calls from Wixzel VoiceIP ACL95.216.218.102
Send inbound calls to Wixzel VoiceThe destination for inbound calls; the setup steps name the fieldsip:95.216.218.102:5090

Both values are today's: read platform_ip and origination_uri from GET /v1/sip-trunks rather than copying them from a page. Then register each number on the trunk with POST /v1/phone-numbers and give it an inbound_agent_id, so an agent answers it. The AI phone call API walkthrough has those requests, and the full setup steps for Vobiz go through the console field by field.

What goes wrong on Vobiz?

  • The word "origination" points the other way on Vobiz. Do not paste the Wixzel Voice origination_uri into a Vobiz field just because the names match; read what the field does first.
  • Vobiz expects the leading +, so leave send_plus at its default of true.

Why did a call over Vobiz not connect?

A call Vobiz refused has status: "failed", a failure_code (the Q.850 cause from the carrier) and a failure_reason saying what to do, and it costs nothing. Every failure code, every refusal and how to debug a trunk are on the integrations page.

What does an AI call over Vobiz cost?

Vobiz bills you for the line at your rates; Wixzel Voice bills only the voice engine, per second of actual usage, from $0.0466 per connected minute on gemini-live to $0.1851 on deepgram-agent. Every engine's price.

Frequently asked questions

What host do I use for a Vobiz trunk?
The SIP domain Vobiz generates for the trunk, in the form <trunkId>.sip.vobiz.ai. Use it as the Wixzel Voice trunk's host rather than a bare IP.
Does the Wixzel Voice origination_uri go in the Vobiz origination URI field?
Not without reading the field first. On Vobiz, "origination URI" is where calls leaving your trunk are routed, the opposite direction from Twilio's Origination SIP URI, and Vobiz allows several with priority-based failover and weighted load balancing. Read what each Vobiz field does before pasting an address into it.

Other carriers

Twilio

Elastic SIP Trunking. Allowlist the platform IP in a Termination IP ACL, and set the Origination SIP URI for inbound calls.

Telnyx

An IP-authenticated SIP Connection. Add the platform IP as an authorised address, pick an inbound region, and match the transport.

Plivo

Zentrunk. An outbound trunk with the platform IP in its IP ACL, and a separate inbound trunk whose Primary URI points at the platform.

Vonage

Programmable SIP. Add the platform IP to the trunk's ACL in the SIP Dashboard, and send inbound calls to the origination URI.

Bandwidth

No SIP REGISTER, so a static IP is required. Add the platform IP to the location, configure Termination and Origination separately, or use network-bridge credentials.

Exotel

Virtual SIP Trunking (vSIP), for Indian numbering, over TCP. The platform IP mapped to the trunk as an ACL, and the Destination URI pointed at the platform's TCP port for inbound.

Any SIP provider

The pattern is the same everywhere: allowlist the platform IP, set the inbound destination to the origination URI, and match the number format and transport.

Bring your own SIP trunk

How the two halves of a trunk work, every failure code, and every carrier guide on one page.