A2P 10DLC Campaign Vetting Delays: Twilio cannot approve 10DLC Campaigns ourselves, and must rely on third parties who control our connections to carriers to sign off. These external processes are creating several week delays for our customers. We continue to escalate these issues and are working to reduce delays wherever possible. Further details will be shared in the Campaign Vetting Changes article as they become available.

Read Custom Headers from a SIP Calls in Studio

Custom data can be passed from a SIP call to a Studio flow execution using User To User information headers. Twilio will prepend the UUI header with SipHeader_ prefix in your webhook request to your Studio flow. This data can be read in Studio using the variable:

{{trigger.call.SipHeader_User-to-User}}

Other custom headers can be read by Twilio if they prepend a X- in the name, for instance X-TestHeader: param1=value1;param2=value2;param3=value3 They can be read in the flow as:

{{trigger.call.SipHeader_X-TestHeader}}

Have more questions? Submit a request