Twilio Changelog

As previously communicated we have updated the status callback behavior for mobile Voice SDK calls. This change more accurately reflects the actual condition of the call; i.e. calls sent to powered off or otherwise unreachable devices will no longer return a ringing call progress event. If your application logic depends on the ringing status callback for its performance, you will need to update your application to handle this condition appropriately.

Effective May 3rd, 2023, Twilio SendGrid customers will be able to configure multiple endpoints for our Event Webhook feature. This enhanced feature provides customers with greater flexibility and control with the ability to  deliver event data to multiple endpoints, each configured to receive whichever events make sense for your email program. For example, you could have one Event Webhook to monitor engagement data and another for delivery events, or one Webhook sending data to your marketing analytics pipeline and another feeding your application monitoring stack.

We have updated the TaskRouter SDK V1 & Taskrouter SDK for Flex with the introduction of retries and the use of truncated exponential backoff in case of network call failures.

Twilio has updated its Text-To-Speech offering adding support for new Amazon Polly Neural Voices. This release includes the following new voices and languages: Ruth-Neural (en-US), Stephen-Neural (en-US), Sergio-Neural (es-ES), Andres-Neural (es-MX), Remi-Neural (fr-FR), Adriano-Neural (it-IT), Kazuha-Neural (ja-JP), Tomoko-Neural (ja-JP), and Thiago-Neural (pt-BR).

Starting 26 June 2023, “Alice” voices will no longer be supported for Text-To-Speech. Any request for “Alice” voices will be redirected to an alternative voice. No action is required from customers and no service disruption is expected.

Going forward, requests for “Alice” voices will be automatically mapped to the existing “Woman” voices when available for the selected language, and requests for non-available languages would be mapped to a paid alternative.

It is recommended to update configuration in Console, Studio flows and application to remove any references to “Alice”. Alternatively, Twilio encourages to review and re-test applications currently using “Alice” with the re-mapped voices to confirm that they work as intended.

For additional information, see this help center article.

Voice Intelligence is now in Public Beta. Create call transcriptions and apply Natural Language Understanding to get valuable data insights from your call recordings. It is available with a new API and in the Twilio Console.

With Voice Intelligence you can:

• Transcribe your calls from Twilio or 3rd party recordings.
• Apply Natural Language Understanding (Language Operators) to your call transcriptions to analyze calls, redact PII or identify keywords and phrases.
• Search and share data insights from your transcriptions in your software with an embeddable view.
• Integrate the Transcription Viewer with Flex using the Voice Intelligence plugin.

 

Learn more about Voice Intelligence in our docs.

Effective May 3rd, 2023, Twilio SendGrid customers will be able to configure multiple endpoints for our Event Webhook feature. This enhanced feature provides customers with greater flexibility and control with the ability to  deliver event data to multiple endpoints, each configured to receive whichever events make sense for your email program. For example, you could have one Event Webhook to monitor engagement data and another for delivery events, or one Webhook sending data to your marketing analytics pipeline and another feeding your application monitoring stack.

With this new feature roll-out we have updated the user interface (UI). All the webhook settings are in one place. In the SendGrid UI, click on Mail Settings in the left navigation, and you will see Event Webhooks below the  Webhook settings heading.. We have consolidated our security features: Signature Verification and OAuth 2.0 in one place, providing you with a streamlined user interface.

Additionally, we have added four new fields in the UI and API:
1. Friendly Name
2. Webhook ID
3. Created Date
4. Updated Date

Note:
* Existing webhooks will not be affected by this change, but customers can add additional endpoints as desired.
* The number of endpoints per user is dependent on the TSG plan you are on. See the SendGrid pricing page for details.

We hope this new feature will enhance our customers' experience with Twilio SendGrid and improve their ability to track and analyze their email engagement and delivery data.

 

Effective May 3rd, 2023, Twilio SendGrid customers will be able to configure multiple endpoints for our Event Webhook feature. This enhanced feature provides customers with greater flexibility and control with the ability to  deliver event data to multiple endpoints, each configured to receive whichever events make sense for your email program. For example, you could have one Event Webhook to monitor engagement data and another for delivery events, or one Webhook sending data to your marketing analytics pipeline and another feeding your application monitoring stack.

With this new feature roll-out we have updated the user interface (UI). All the webhook settings are in one place. In the SendGrid UI, click on Mail Settings in the left navigation, and you will see Event Webhooks below the Webhook settings heading.. We have consolidated our security features: Signature Verification and OAuth 2.0 in one place, providing you with a streamlined user interface.

Additionally, we have added four new fields in the UI and API:
1. Friendly Name
2. Webhook ID
3. Created Date
4. Updated Date

Note:
* Existing webhooks will not be affected by this change, but customers can add additional endpoints as desired.
* The number of endpoints per user is dependent on the TSG plan you are on. See the SendGrid pricing page for details.

We hope this new feature will enhance our customers' experience with Twilio SendGrid and improve their ability to track and analyze their email engagement and delivery data.

 

On 10 October 2023 Twilio will be updating the public media IPs and port ranges for SIP and Voice SDK calls in all regions. We are 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 10000-60000.

Old IP and port ranges will no longer accept or send traffic after 10 October 2023 but will need to be kept open in your infrastructure until that time. We are making this change to provide flexibility, reliability, and scalability for the next ten years. You will need to update your network infrastructure to ensure that you have allowlisted the full IP and port ranges before 10 October 2023. Failure to do so will result in one-way audio and dropped calls.

Impacted Edge locations include: Sydney (AU1), Sao Paulo (BR1), Dublin (IE1), Frankfurt (DE1), Tokyo (JP1), Singapore (SG1), Ashburn (US1), Umatilla (US2).

Twilio Interconnect connections are excluded from these initial changes, but will be migrated separately in the future.

This release reversed changes made to the usage of Sync for outbound, transfer and conference state workflows that were introduced in v1.33. For full details on the changes included in this version read the release notes.

For more info on what changes were introduced in v1.33 and are now being reversed, refer to ‘Changes to Sync usage in Flex UI’ in the Flex UI release notes.