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.

Does Elastic SIP Trunking alter the caller ID on calls?

Elastic SIP Trunking does not alter the Caller ID for calls:

  • Outgoing calls on a Twilio Elastic SIP trunk (SIP Termination) must use a valid Twilio phone number owned on this project, or a verified Caller ID (using E.164 formatting).
  • Incoming calls on a Twilio Elastic SIP trunk (SIP Origination) will have the originating caller ID Twilio receives passed along with the SIP INVITE (using E.164 formatting).

This being said, it's possible for Caller IDs in general to be changed in transit for a number of reasons. For more details, please see the following resources:

Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk