SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Resolving Twilio IE1 Region Verified Non-Twilio Caller ID Failures

Issue

If you are experiencing issues using a verified non-Twilio phone number as your caller ID for outbound calls in the Twilio IE1 (Ireland) region, you are not alone. This article explains why this happens, how Twilio’s regional support for Verified Caller ID works, and what steps you can take to resolve or work around the issue.

Symptoms

  • Outbound calls using a verified non-Twilio number as the caller ID fail in the IE1 (Ireland) region.
  • Error message:
    "Error: The source phone number provided, +[number], is not yet verified for your account. You may only make calls from phone numbers that you've verified or purchased from Twilio."
  • The same setup works in the US1 (United States) region.
  • API requests to endpoints like /OutgoingCallerIds.json may return error code 20004 or HTTP 405.

 

Product

Programmable Voice

 

Environment

Twilio Console

 

Cause

Twilio’s Verified Caller ID feature is only supported in the US1 data routing region. It is not available in the IE1 (Ireland) or AU1 (Australia) regions. Even if you have verified a non-Twilio number in your account, it will not be recognized as a valid caller ID for outbound calls in regions where this feature is not supported.

 

Resolution

If You Need to Use a Non-Twilio Number as Caller ID

  • Deploy your application and verify your caller ID in the US1 region.
    Only the US1 region supports using verified non-Twilio numbers as caller IDs for outbound calls.

If You Must Use the IE1 (Ireland) Region

  • Use a Twilio-purchased number as your caller ID.
    Verified non-Twilio numbers are not supported as caller IDs in IE1. Only Twilio numbers can be used.

Additional Steps

  • Verify the number in the correct subaccount and region.
    Caller ID verification is account- and region-specific. Double-check that the number is verified in the same subaccount and region as your application.
  • Remove and re-verify the number if issues persist.
    Sometimes re-verifying the number in the correct context can resolve lingering issues.

 

Additional Information

 

Summary Table

Region Verified Caller ID Support Twilio Number Support
US1 Yes Yes
IE1 No Yes
AU1 No Yes

 

If you have followed these steps and are still experiencing issues, please reach out for further assistance. Be sure to include error messages, account details, and the region you are using for faster troubleshooting.

Have more questions? Submit a request
Powered by Zendesk