Programmable Voice Product Behavior Changes in non-us1 Home Regions
Not all Programmable Voice product features and functionality will be available in non-us1 home regions. Some aspects may be added at a later date, and some features may never be regionalized due to data sovereignty restrictions.
|Voice Insights Subaccount Dashboard||Calls homed outside of us1 will not be rolled up into Voice Insights Subaccount Dashboard results.|
|Feedback API||The Feedback API for Voice will not be available for calls homed outside of us1.|
|Bulk Export for Calls, Conferences, and Participants||Calls, Conferences, and Conference Participants homed outside of us1 will not be available via Bulk Export. Postflight logs for Calls and Conferences for non-us1 home regions will be available in Console and via API for 13 months.|
|Media Streams||Media Streams signaling and forking service will not initially be regionalized. Signaling and media will traverse us1 for all Media Streams regardless of home region.|
|Calls per second (CPS)||CPS value can only be updated in us1. The value set in us1 is mapped to non-us1 home regions.|
|<Sms> TwiML instruction||
The <Sms> TwiML instruction is deprecated in us1 and will not work in regions outside of us1.
|<Pay> TwiML instruction||
The <Pay> TwiML instruction will not initially work in regions outside of us1.
|Event Streams||Calls homed outside of us1 will not be available via Event Streams.|
|/Calls API priceUnit||
|/Recordings API priceUnit||
|/Transcriptions API priceUnit||
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.