Twilio Changelog

Policy updated as of September 28, 2020

Twilio anticipates significant spikes in provisioning of US-based phone numbers as we approach November's 2020 U.S. election. Due to the finite capacity of the U.S. messaging ecosystem, we're implementing a Heightened Awareness Period (HAP) from October 2, 2020until November 4, 2020.

Our goal for this short-term policy is to ensure that all customers have fair access to a secure and reliable network.During this Heightened Awareness Period, the following limitations will apply:

• A maximum of 1,000,000 additional 10-digit long code phone numbers can be added to customers' existing accounts within the +1 country code. These numbers are available on a first-come, first-served basis, with inventory being added regularly.

For more information see this FAQ.

Twilio now supports sending up to 25 messages per second through WhatsApp.

If messages are sent at a rate higher than 25 MPS, Twilio maintains a queue. For very high outbound message volumes, messages can remain queued for up to 4 hours.

To achieve higher MPS, you can use Messaging Services. This allows you to distribute high volume across many WhatsApp senders within the Messaging Service.

Read more about MPS in our Best Practices guide.

Twilio Programmable Voice and Elastic SIP Trunking now perform SHAKEN/STIR verification on incoming calls to your Twilio local phone numbers. It can be used to display a trust indicator or to make a routing decision, such as bypassing a voice captcha or IVR and directing the call to an end user.

A verified call that has been given the highest attestation under SHAKEN/STIR means that the carrier that originated the call both (1) knows the identity of the caller, and (2) knows the caller has the right to use the phone number as the caller ID.

In Programmable Voice the request webhook presents the StirVerstat parameter, and in Elastic SIP Trunking there is a new header called X-Twilio-VerStat with the verification result. The new parameter and header are only present for incoming calls with SHAKEN PASSporT identity headers. Today, support for the SHAKEN/STIR call authentication framework is being deployed in the United States only.

You can now disable any Verify v2 delivery channel (SMS, Call, Email) that you are not using to reduce your risk of potential abuse. Navigate to your Verify Service Settings page to use this feature.

Twilio SendGrid now allows you to define multiple From addresses in personalizations objects. This allows you to override the default sender in each personalization as long as the default sending domain and personalizations sending domains match. For more information, visit our Personalizations documentation.

You could always have multiple SMS participants in the same conversation talking to each other. However, each participant was previously bound to a single proxy address number through which they received all of the messages in the Conversation. In this scenario, each participant had no way of knowing how many people the proxy number represented.

It is now possible to add your US or Canada based clients as Group participants, utilising a Group MMS protocol. As a result, your clients will observe an iMessage style experience and easily see who said what. This is especially valuable for use-cases which expect an active participation of all interested parties, like wealth management, personal shopping, or real-estate industry.

Explore the Group Texting documentation and give it a try!

This release of Flex UI and WebChat UI introduces the public beta version of chat attachments. Chat attachments now includes drag-n-drop for your files, and you can compose a single message with both text and an attachment. For a complete overview of the feature and developer guides to programmatically customize the experience, check out the chat attachment docs.

Other notable changes:

• Flex WebChat UI CDN bundle size has been reduced to 390kb.
• Real-time Queues View is now enabled for all accounts. For more details on this feature, visit our Real-time Queues View docs.

For more details on this release, please visit the release notes for Flex UI and WebChat UI.

This release of Twilio Voice SDK now uses Chromium WebRTC 83. With this release, users will hear audio much sooner after the Call.Listener#onConnected callback than in prior releases. This upgrade ensures that when Call.Listener#onConnected is raised to the developer the media connection has been fully established. Additionally, the MOS calculation algorithm has been updated to make it monotonically decreasing with increasing jitter and packets-lost-fraction values over a range of RTT values.

To learn more about this release on our changelog.

This major release of Twilio Voice SDK now uses WebRTC 83. With this release users will hear audio much sooner after the [TVOCallDelegate callDidConnect:] callback than in prior releases. This upgrade ensures that when [TVOCallDelegate callDidConnect:] is raised to the developer the media connection has been fully established. Additionally this release improves the interoperability of the SDK with Swift. Lastly, the MOS calculation algorithm has been updated to make it monotonically decreasing with increasing jitter and packets-lost-fraction values over a range of rtt values.

To migrate from 5.X to 6.X please see the migration guide.

To learn more about this release on our changelog.

Introducing the API for Elastic SIP Trunking Call Transfer (SIP Refer) feature. This feature enables you to move an active call from one endpoint to another. Twilio's Elastic SIP Trunking product supports "blind" call transfers. This allows you to configure SIP Refer on a Trunk using the API.

For details, please check our Elastic SIP Trunking API for Call Transfer via SIP REFER documentation.

As a side note, you can also configure Elastic SIP Trunking Call Transfer (SIP Refer) feature through Twilio console. Details of console configuration can be found here.