Twilio Changelog

Effective February 21, 2024, Twilio will expand the Interconnect media IPs and port ranges for calls in all regions; we’ll also expand the RTP port range to 10000-60000 UDP. 

We’ve started migrating our non-Interconnect traffic, and we’ll migrate all Interconnect traffic to the expanded port ranges listed below before February 21, 2024. 

We’re making this change to improve the flexibility, reliability, and scalability of our Voice products. We previously communicated this change in November 2022 via Twilio Changelog. 

Update your network infrastructure to allowlist the new IP and port ranges below (in addition to the IP and port ranges your network infrastructure currently allows).

• 168.86.128.0/18
• UDP port range: 10000-60000 (expanding from 10000-20000)

For example, you will need to update your firewall and BGP prefix if you have a Cross Connect and Encryption Domain if you have a VPN.

Lastly, keep old IP and port ranges open in your infrastructure after February 21, 2024; these ranges won’t be able to accept or send Voice media traffic after this time, but they need to stay open for signaling and API traffic.

If you don’t take action by February 21, 2024, you will experience one-way audio and dropped calls.

Generic Pay Connector is now Generally Available. Generic Pay Connector provides you the ability to process charge and tokenization payment transactions with your payment gateway of choice in a PCI compliant manner. It includes support for credit card and ACH-debit payment methods. 

To use Generic Pay Connector, install and configure your connector in test mode, plug in your payment gateway URL and perform testing. When you're ready to go live, raise a support ticket and submit a valid PCI Attestation of Compliance (AoC) document of your payment gateway. For more details, check out our docs.

For details on Twilio Generic Pay Connector pricing, visit our pricing page.

Learn more about this feature in our API docs.

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 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.