Issue
When dialing a SIP URI in TwiML from one account to another account’s SIP Domain, calls fail with warning 32214: “Your TwiML can only Dial out to Twilio SIP Domains that your account owns.”
Product
Programmable Voice
Cause
Calls to sip.twilio.com domains are restricted to the same account (or subaccount) that executes the TwiML. Cross-account dialing to another account's SIP Domain is not supported, because the SIP Domain feature is designed to provide PSTN access for SIP endpoints owned by the same account.
This restriction also applies when the parent account and the subaccount do not match the SIP Domain's owning account.
Resolution
Verify ownership alignment:
- Confirm the SIP Domain you are dialing is owned by the same account/subaccount that executes the TwiML.
If ownership does not match, use one of these supported approaches:
Option 1 — Consolidate under one account/subaccount
Move the target SIP Domain and its SIP endpoints into the same account/subaccount that initiates the call. This is the simplest approach when both sides are under your control and there is no business reason to keep them separated.
Option 2 — Route via a phone number (PSTN handoff)
From Account A, <Dial> a phone number owned by Account B.
In Account B, configure that number's voice webhook to return TwiML that routes the call to its SIP
Note: PSTN handoff may incur standard telephony charges on both legs.
Option 3 — Use <Dial><Application> across accounts (recommended for cross-account SIP without PSTN)
This keeps the call on Twilio's network (no PSTN charges) while letting Account B terminate the call to its own SIP Domain.
How it works:
In Account B (termination side), create a TwiML App whose Voice Request URL returns TwiML that dials the destination SIP endpoint (A Twiml Bin as URL will do the trick), e.g.:
<Response> <Dial> <Sip>sip:alice@your-domain.sip.twilio.com</Sip> </Dial> </Response>
In the same TwiML App, enable "Allow Application Dialing from other Twilio Accounts" and authorize Account A's SID. Without this setting, Account A's <Dial><Application> request will be rejected.
In Account A (origination side), dial the TwiML App by its SID:
<Response> <Dial> <Application>APxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</Application> </Dial> </Response>
When Account A executes this TwiML, Twilio invokes Account B's TwiML App, which runs in Account B's context — so the <Sip> inside it is dialing a SIP Domain that Account B owns. The 32214 restriction does not trigger because the SIP dial is performed by the owning account.
Billing: each leg is billed to the account that executes its TwiML (A for the origination leg, B for the SIP termination leg).
Option 4 — Use an external SIP server you control
Dial a non-Twilio SIP URI (e.g., your own SIP proxy / PBX) and have it route the call back into the destination account's SIP Domain. Dialing non-Twilio SIP URIs is permitted; the 32214 restriction applies only to Twilio SIP Domains (sip.twilio.com).
Verify
Place a test call after applying one of the supported options and confirm warning 32214 no longer appears in the Console Debugger.
Additional Information
Dialing non-Twilio SIP URIs is always permitted; the restriction applies only to Twilio SIP Domains (sip.twilio.com).
<Dial><Application> across accounts requires explicit opt-in on the receiving TwiML App via Allow Application Dialing from other Twilio Accounts; it is off by default.
PSTN handoff and call routing may incur standard telephony charges.