Twilio Changelog

The previous-generation language models that are currently available with IBM Watson Speech to Text AddOn will be deprecated and stop functioning as of March 3rd 2023. To avoid any issues with transcribing your call recordings use IBM Speech To Text AddOn, please update to use next-generation language models as soon as possible.

The following table has the mapping between previous generation language models, and the next generation language models to make it easier for you to make appropriate changes. We recommend that you make this change at your earliest convenience.

Twilio SendGrid has launched support for Domain Connect with GoDaddy to improve the Domain Authentication process. The updated Twilio SendGrid user interface eliminates the need to manually copy and paste CNAME records from Twilio SendGrid to GoDaddy, allowing you to onboard more quickly and start sending mail. Customers are now able to click a button and sign into their GoDaddy accounts from within the SendGrid platform. Twilio SendGrid will then authenticate their domains automatically by making the necessary DNS entries for them.

There are no other changes to existing capabilities. No action is required for customers at this time.

We are keeping your runtime up to date in accordance with industry standards. Based on the Node.js support schedule, Node.js v14 will no longer be in Maintenance long-term support (LTS) status after April 30, 2023. Production applications should only use releases of Node.js that are Active LTS or Maintenance LTS.

Your currently deployed functions will continue to execute on the existing Node.js v14 runtime if no changes are made.

Follow these instructions to upgrade, test, and deploy your code and ensure a safe transition to Node.js v16.

This release improves Flex UI’s resiliency by updating functionality used in conferences, outbound calling and voice transfers to remove dependencies.

Twilio has released changes to the US A2P 10DLC Campaign creation process in the Twilio API and Twilio Console to reflect the latest ecosystem guidelines. These changes include collection of new fields regarding user consent (e.g., opt-out keywords and auto-reply messages), as well as enforcement of length requirements to existing and new fields. Please read more about this change from the Twilio support article, and check out code samples and API guidelines from Twilio docs.

Twilio C# Helper Library major version 6.x is now available.We ensured that you can upgrade to the 6.x version without any breaking changes

Behind the scenes C# Helper is now auto-generated via OpenAPI with this release. This enables us to rapidly add new features and enhance consistency across versions and languages.

To learn more about the C# Helper Library, check out our docs.

In 2H 2023 Twilio will be updating the media IPs and port ranges for Elastic SIP Trunking calls in all regions. We will be moving from a per-region IP range allocation to a single global range; 168.86.128.0/18. Additionally, we will be expanding the media port range from 10000-20000, to 1024-65535.

We are making this change to provide flexibility, reliability, and scalability. There is no action required at this time, and we will provide a more precise timeline approximately six months before the change. At that time you will need to update your network infrastructure to ensure that you have whitelisted the full IP and port ranges. Failure to do so will result in one-way audio and dropped calls.

In 2H 2023 Twilio will be updating the media IPs and port ranges for Flex calls in all regions. We will be moving from a per-region IP range allocation to a single global range; 168.86.128.0/18. Additionally, we will be expanding the media port range from 10000-20000 to 1024-65535.

We are making this change to provide flexibility, reliability, and scalability. There is no action required at this time, and we will provide a more precise timeline approximately six months before the change. At that time you will need to update your network infrastructure to ensure that you have whitelisted the full IP and port ranges. Failure to do so will result in one-way audio and dropped calls.

Twilio is changing how we persist caller ID information for <Dial> calls where the inbound caller ID is withheld; e.g. ANONYMOUS, RESTRICTED, etc. Today Programmable Voice translates the alpha string into digits. This behavior will change and we will begin to persist the alpha string from the inbound call to the outbound <Dial> leg for calls where the caller ID is withheld by the calling party.

This represents a significant change in the behavior of our APIs and developers will need to ensure that their systems can gracefully handle alpha characters in the To and From fields for requests and responses to the /Calls API, in TwiML,webhooks, and in status callbacks.

If the callerId parameter is used with the <Dial> verb, the outbound caller ID will reflect what was provided with callerId, regardless of the caller ID on the inbound call.

In 2H 2023 Twilio will be updating the media IPs and port ranges for Frontline calls in all regions. We will be moving from a per-region IP range allocation to a single global range; 168.86.128.0/18. Additionally, we will be expanding the media port range from 10000-20000, to 1024-65535.

We are making this change to provide flexibility, reliability, and scalability. There is no action required at this time, and we will provide a more precise timeline approximately six months before the change. At that time you may need to update your internal network infrastructure to ensure that you have whitelisted the full IP and port ranges. Failure to do so could result in one-way audio and dropped calls.