Twilio Changelog

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.

Twilio Alarms, a near real-time monitoring and alerting experience for Twilio customers, is now Generally Available (GA).

The first full scale implementation of Alarms supports Error Logs. This enables you to proactively monitor error logs at the minute level and receive a notification whenever there is a spike in errors, warnings, or informational events of interest, across your Twilio applications.

You can learn how to create and use Alarms with this Twilio guide or watch this demo.

We are sunsetting our old Alert Triggers product. If you have created Alerts on our old platform, they have already been migrated onto this new Alarms platform. You will be able to access these in the Manage Alarms page.

Twilio SendGrid has always grouped your email statistics by mailbox provider in our console. This allows you to easily see how your email is performing at Yahoo compared to Microsoft, for example. Our system also helps clean up this data by grouping mailbox providers together. On November 16, 2022, Twilio SendGrid will release an update to our current Mailbox Provider groupings that will make this part of our application even more powerful. Specifically, we will be adding more mailbox providers to our list, increasing from 50 to almost 250. This will result in far less data being lumped into the “Other” bucket when you review your mailbox provider statistics. Check out our blog post to learn more about the change and see examples for more information.