Product changelog and announcements

Effective October 10, 2023, Twilio will migrate the public media IPs and port ranges for Elastic SIP Trunking calls, Programmable SIP calls, Voice SDK calls, Flex calls, and SIPREC sessions in all regions. 

We’re moving from a per-region IP range allocation to a single global range (168.86.128.0/18), and we’re expanding the media port range from 10000-20000 to 10000-60000. We’re soft launching the new range as follows:

• September 26, 2023: 1% of all calls will use the new range
• October 5, 2023: 20% of all calls will use the new range 
• October 10, 2023: 100% of all calls will use the new range

Impacted Edge locations include: Sydney (AU1), São Paulo (BR1), Dublin (IE1), Frankfurt (DE1), Tokyo (JP1), Singapore (SG1), Ashburn (US1), Umatilla (US2). After the migration, Voice SDK calls can select US2 for GLL edge location selection.

We’re providing testing capabilities and we’ll offer opt-in for production traffic before the migration begins; however, these testing capabilities are intended for non-production traffic only. 

We are thrilled to announce that customers registering Brands and Campaigns for A2P Messaging can now set up subscriptions to events, which will notify when Brand or Campaign’s status changes. This setup and subscription is through Event Streams.

This new feature is designed to streamline your A2P registerations, making it easier than ever to manage your Brands and Campaigns. 

For more information on how to set up Event Streams and subscribe to notifications, be sure to check out our code samples and API guidelines in Twilio docs. 

A2P 10DLC Registration Status Tool is now available on the console.  With the latest update, customers can request a .csv download of all of the numbers on their primary/sub accounts and view the most up to date A2P Registration Status for their numbers.

Effective 5 February, 2024, Twilio will deprecate HTTP voice media endpoint and redirect requests to fetch recordings media files to HTTPS. As a result, CNAME to serve media from custom hostname will no longer be supported.

Effective November 16, 2023, Twilio will stop using the current IP pools for sending Media Streams’ media, and will begin sending Media Streams media from a broad range of publicly available AWS IPs, so that we can improve the flexibility, reliability, and scalability of our Voice products.

We’re giving advance notice to allow customers time to update your network infrastructure and applications, but before November 16, 2023, you must:

1. Update your network infrastructure to stop allowlisting the old IP range used for U.S. Media Streams media:
      34.203.254.0/24
      3.235.111.128/25
      (Traffic is secure web socket over TCP)
   
   
2. Configure your firewall rules to allow secure websocket connections (TCP port 443) to their websocket servers from any public IP address.

You should also configure your application to validate the X-Twilio-Signature header, to verify that the media stream is coming from an authentic Twilio source, as described here:  https://www.twilio.com/docs/usage/security#validating-requests

If customers do not update their network infrastructure, then forked media from Media Streams will not continue to be successfully delivered to your applications.

Twilio now supports Meta's new requirements for authentication template approval in both the standard WhatsApp templates editor and Content Editor (Public Beta) areas of Twilio Console.

Error codes for campaign reviews are now available on the Console. With this latest update, customers can view the reason for campaign rejection with an error code and description directly within the Console and through the US App to Person (A2P) Campaign Resource.

For a detailed list of all error codes please visit Twilio Error and Warning Dictionary. To learn more about these error codes, please read the Twilio support article.

Twilio’s self-service Toll-Free verification tooling is now in Public Beta. Customers who are looking to submit toll-free phone numbers for verification can now do so directly within Messaging Compliance API or Twilio Console without going through Support or Sales.

With Toll-Free verification tooling, you can:

• Submit a new US or Canadian toll-free phone number for verification
• Utilize customer profiles for a Toll-Free verification that were created in other compliance programs like A2P 10DLC, Shaken/Stir, etc
• Get a list of toll-free verification records, including status and rejection reason (if rejected). Historical verifications submitted manually through CSV process are available for most toll-free numbers.
• Re-submit a rejected verification (if rejection type is allowed to resubmit)
• Subscribe to Event Stream’s webhook for toll-free verification events

Learn more about Toll-Free verification with Twilio docs:

• Messaging Compliance API documentation
• Toll-Free Verification within Twilio Console
• Toll-Free Message Verification overview
• Required Information for Toll-Free verification
• Toll-Free Verification for ISVs
• Information and best practices for using Toll-Free SMS and MMS in the US and Canada
• Forbidden Message Categories for SMS and MMS in the US and Canada
• What are the differences between long codes (A2P 10DLC), short codes, and Toll-Free numbers for messaging to US/Canada?”