Carrier guides
Carriers
Bring the carrier you already use, or pick one by region, setup and price.
Quick picks
- Callers in IndiaTelnyx, Plivo, Exotel, VobizIndian numbersfor callers in India
- Cheapest US minute
Plivofrom $0.0046/minUS outbound, the carrier's price
- Quickest setupTwilio, Telnyx, Plivo, Vonage, Exotel, VobizPaste API keysthen buy numbers in the console
- Already have a carrier?Any SIP providerAny SIP trunk
Filters
Numbers in
Setup
Phone numbers
Transport
Plivofrom $0.0046/minZentrunk. An outbound trunk with the platform IP in its IP ACL, and a separate inbound trunk whose Primary URI points at the platform.Worldwide, United States, United Kingdom, Europe, India · One step: paste your API keys · Search and buy in the console · US number $0.50/month · India ₹0.38/min
Vobiz$0.0046/minA per-trunk SIP domain as the host, the platform IP in the trunk's IP ACL, and "origination URI" meaning the opposite of what it means on Twilio.India, Worldwide, United States, United Kingdom · One step: paste your API keys · Search and buy in the console · US number $1.00/month · India from ₹0.45/min · SIP channels from $125/month
Telnyxfrom $0.005/minAn IP-authenticated SIP Connection. Add the platform IP as an authorised address, pick an inbound region, and match the transport.Worldwide, United States, United Kingdom, Europe, India · One step: paste your API keys · Search and buy in the console · US number $1.00/monthTwilio$0.0100/minElastic SIP Trunking. Allowlist the platform IP in a Termination IP ACL, and set the Origination SIP URI for inbound calls.Worldwide, United States, United Kingdom, Europe · One step: paste your API keys · Search and buy in the console · US number $1.15/month
VonageSet by the carrierProgrammable SIP. Add the platform IP to the trunk's ACL in the SIP Dashboard, and send inbound calls to the origination URI.Worldwide, United States, United Kingdom, Europe · One step: paste your API keys · Search and buy in the console
ExotelSet by the carrierVirtual 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.India · One step: paste your API keys · Search and buy in the console · Plans from ₹4,999/month · Beta
Bandwidth$0.0100/minNo 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.United States · By hand: a SIP trunk · Bring your own numbers · US number $0.30/month
MobilySet by the carrierSaudi Arabia, ordered through Mobily Business sales and delivered over a private link. No one-step connect: your own SBC on the link relays calls, with G.711 A-law and a one-hour call cap.Middle East · By hand: a SIP trunk · Bring your own numbers · Bundles from SAR 598/month
- Any SIP providerSet by the carrierThe pattern is the same everywhere: allowlist the platform IP, set the inbound destination to the origination URI, and match the number format and transport.Worldwide · By hand: a SIP trunk · Bring your own numbers
Carrier prices are each carrier's own, copied from their pricing pages on 29 October 2026. Wixzel Voice adds nothing to them: the carrier bills you directly, and our per-minute price covers only the voice models.
Published . The carrier names are trademarks of their owners; Wixzel Voice integrates with them over standard SIP and is not affiliated with or endorsed by any of them.
Why bring your own SIP trunk?
- Your numbers stay yours
- Wixzel Voice never sells or ports numbers. Leaving is one setting at your carrier.
- Your rates stay yours
- Your carrier bills you for the line. Wixzel Voice bills only the voice engine, per second.
- Your compliance stays put
- Caller ID, KYC and registrations stay with the carrier you already trust.
- Any SIP provider
- Eight carriers have guides. Anything with a SIP trunk works.
How does a bring-your-own SIP trunk connect?
A Wixzel Voice trunk has two halves, and they live in different parts of your carrier's console. Both addresses are returned on every trunk, so read them from the API rather than trusting a page to stay current.
Add 187.126.120.231 to your carrier's IP allowlist. Nearly every carrier authorises outbound calls by source IP, and a trunk that is correct in every other respect still fails without it.
Set your carrier's inbound destination to sip:187.126.120.231:5090. Miss it and a number simply never rings: the carrier has nowhere to deliver the call, so nothing appears in any log.
curl https://api.voice.wixzel.com/v1/sip-trunks \
-H "Authorization: Bearer $WIXZEL_API_KEY" \
| jq '.data[0] | {platform_ip, origination_uri}'Which carriers have a setup guide?
Every carrier below has its own page with what to buy, what to allowlist, where inbound calls go, the trunk request that fits it, and the gotchas that are specific to it, with a link to the full console steps in the docs. Each carrier names the two settings differently; the setting is the same.
| Carrier | Product | Allowlist is called | Inbound destination is called | Transport |
|---|---|---|---|---|
| Twilio | Elastic SIP Trunking | IP Access Control List | Origination SIP URI | udp |
| Telnyx | SIP Connections | authorised addresses on an IP-authenticated SIP Connection | Not named in the guide yet | udp |
| Plivo | Zentrunk | IP Access Control List | Primary URI | udp |
| Vonage | Programmable SIP | ACL (Access Control List) | Not named in the guide yet | udp |
| Bandwidth | - | Voice IP addresses / DNS hosts on a location | Origination | udp |
| Exotel | Virtual SIP Trunking (vSIP) | ACL mapped to the trunk | Destination URI | tcp |
| Vobiz | - | IP ACL | Not named in the guide yet | udp |
| Mobily | SIP Trunk | trusted peers on the SBC that holds your Mobily link | SBC route for inbound Mobily calls | udp |
| Any SIP provider | - | IP ACL, allowlist or authorised address | Origination URI, or the carrier's name for it | udp |
What do carriers call the two settings?
| What it does | Names carriers use |
|---|---|
| Authorise calls from Wixzel Voice | IP ACL, IP Access Control List, Access Control List, allowlist, authorised address, network bridge |
| Deliver calls to Wixzel Voice | Origination URI, Primary URI, Destination URI, termination point, destination SIP URI, host |
Two more settings decide whether a correct-looking trunk works. Number format: Twilio, Telnyx and Vobiz expect the leading +; many wholesale carriers cannot parse it and time out with 408, which send_plus: false fixes. Transport: UDP is the default almost everywhere, but Exotel does not take UDP, so an Exotel trunk runs over TCP, and a mismatch looks like the carrier ignoring you.
What happens when a call does not connect?
A call the API accepted and the carrier then refused shows status: "failed" (or busy for cause 17 and no-answer for cause 19) on GET /v1/calls/{id}, with failure_code (the Q.850 cause from the carrier, the stable thing to branch on) and failure_reason (what to do, in plain language). Its cost_micros is null: a call that never connected costs nothing, and the credit reserved for it is released.
Read your carrier's own call log first. If the call is not listed, it never reached the carrier: the allowlist, the trunk host or a firewall is wrong. If it is listed with zero answered and zero cost, the carrier accepted the INVITE and then cleared it, which is a carrier permission problem far more often than a configuration one: the caller ID you present must be authorised on the account, KYC and any destination registration must be complete where the market requires them, and the destination range must be enabled, not just funded. These are the causes the API explains:
Every failure code, refusal and how to debug a trunk
| failure_code | Carrier said | What it means | What to do |
|---|---|---|---|
| 1 | 404 | The carrier does not recognise the number. | Check the number format. If the carrier needs a technical dial prefix, set dial_prefix on the trunk. |
| 3 | - | The carrier has no route to this destination. | The destination is probably not enabled on your carrier account. Ask the carrier to open the route. |
| 16 | - | Normal clearing: the far end ended the call deliberately. | On a call that was never answered, read it as something upstream choosing to end the call, not as a completed call. |
| 17 | 486 | The number is busy. | - |
| 18 | 480 | The destination did not respond. | The phone may be switched off or unreachable. |
| 19 | - | It rang and nobody answered. | Nothing to fix: the trunk and the number both work. |
| 20 | - | The subscriber is absent or unreachable. | - |
| 21 | 403 / 407 | The carrier rejected the call outright, before it tried the number. | In order of likelihood: the carrier account is suspended, closed or out of balance; the trunk username or password is wrong; platform_ip is not allowlisted; or the caller ID is not authorised on the account. Check the carrier dashboard first. |
| 22 | - | The number has changed and is no longer in service. | - |
| 27 | - | The destination is out of order. | - |
| 28 | 484 | The carrier rejected the number format. | If the carrier needs a technical dial prefix, set dial_prefix on the trunk. |
| 34 | - | The carrier has no circuits available (congestion). | Retry shortly. |
| 38 | 500 / 501 / 502 | The carrier returned a server error. | - |
| 41 | 503 | The carrier is reachable but refusing calls. | Usually capacity, balance, or a route being down at the carrier. |
| 42 | - | The carrier's switch is congested. | Retry shortly. |
| 58 | 488 | Codec mismatch: the carrier rejected the audio codecs offered. | Offer G.711 (PCMU or PCMA) on the carrier side. G.729 is not supported. |
| 88 | 493 | The carrier rejected the call as incompatible. | - |
| 102 | 408 | The carrier did not respond in time. | Verify the trunk host and port, and that the carrier accepts SIP from platform_ip. If the carrier shows the call as received but never answered, set send_plus to false. |
These are refused by POST /v1/calls before anything is dialled, and cost nothing:
| HTTP status | code | What it means |
|---|---|---|
| 400 | no_outbound_number | No caller ID: pass from_number_id, or set outbound_phone_number_id on the agent. |
| 400 | number_not_on_trunk | The calling number has no sip_trunk_id, so there is nowhere to send the call. |
| 400 | missing_idempotency_key | The raw HTTP request had no Idempotency-Key. The SDKs send one for you. |
| 402 | insufficient_credits | The balance cannot fund the first 15 seconds. Top up and retry. |
| 429 | rate_limit_exceeded | More than 10 requests per second on this key. Wait for Retry-After; a 429 is never charged. |
| 503 | - | The voice engine is unavailable, the account already has as many calls in progress as its concurrent-call limit (5 by default), or the API key has reached its spend limit. The message says which. |
GET /v1/sip-trunks/{id}/status shows whether the trunk is reachable right now and lists its last few carrier rejections; POST /v1/sip-trunks/{id}/test probes it on demand, and GET /v1/sip-trunks/{id}/logs returns the SIP log.
curl https://api.voice.wixzel.com/v1/sip-trunks/$TRUNK_ID/status \
-H "Authorization: Bearer $WIXZEL_API_KEY"An inbound number that never rings is not a failure you can look up: if the carrier has no destination set, the call never leaves the carrier, so there is no failed call to inspect. Check the inbound destination, that the number is attached to the trunk on the carrier side, and that it has an inbound_agent_id. If calls connect but nobody hears anything, the media is not getting through: a firewall in the path has to allow the RTP range, not just the signalling port.
Frequently asked questions
Why does Wixzel Voice need my own SIP trunk?
Which carriers work with Wixzel Voice?
What are the two settings a trunk needs?
platform_ip (187.126.120.231 today), so the carrier accepts calls from the platform. The inbound half is the carrier's destination for inbound calls set to origination_uri (sip:187.126.120.231:5090 today), so calls to your numbers reach the platform; a carrier that takes a bare host and port, or will not send UDP, needs a different form of it, which its guide gives. Both are returned on every trunk by GET /v1/sip-trunks: read them from there rather than copying them from a page.Can I keep my existing phone number?
POST /v1/phone-numbers on that trunk and give it an inbound_agent_id. Wixzel Voice does not port numbers, so the number stays with your carrier.How is my carrier password stored?
Do I need a SIP trunk for a web or mobile app?
POST /v1/realtime/sessions and the app talks to the agent over a WebSocket, with no trunk and no number.Do trunk changes need a restart?
Do I buy phone numbers from Wixzel Voice or from my carrier?
POST /v1/phone-numbers/purchase. Your carrier bills it at its price. On Bandwidth and Mobily, buy the number at the carrier. With any carrier, you can register a number you already own with POST /v1/phone-numbers on the trunk it lives on.Why does my number never ring the agent?
origination_uri your trunk returns (sip:187.126.120.231:5090 today), the number has to be attached to that trunk on the carrier side, and the number needs an inbound_agent_id in Wixzel Voice. Without the first, the call never leaves the carrier and nothing appears in any log.What does an AI call over my own SIP trunk cost?
Build your first voice agent

