Twilio Changelog

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.

With this release developers can pass custom parameters when dialing Twilio Client using Twilio Voice REST API. You can build personalized application experiences for end users by displaying valuable contextual details about the incoming call. For example, you can pass the customer name, type, or product of interest when dialing Twilio Client, and display to the agent.

The custom parameters can be specified as a query string in the ‘To’ parameter of the Create Call Resource and delivered via the Twilio Voice Client.

Learn more about how to share custom information between your applications

For Editions customers, we are introducing a more flexible way to view the Audit Event data in the Twilio Console. This allows viewing by user and filtering the event data.
The list of events now tracked by Audit Events includes new event types, such as console logins. The new event types are only visible in the Twilio console in Audit Event Insights are documented with the other Audit Event data: https://www.twilio.com/docs/usage/monitor-events.
These changes do not impact the Audit Event API. New event types are not available yet in the Audit Event/Monitor Event API

We have updated TaskRouter’s error and warning messages to improve clarity and troubleshooting.

CVE-2020-24655 - A race condition in the Twilio Authy 2-Factor Authentication Application allowed a user to potentially approve/deny an access request prior to unlocking the application with a pin on older Android devices, effectively bypassing the PIN requirement. This issue has been fixed as part of the 24.3.7 Release of the Twilio Authy App. Other operating systems (iOS, MacOS, Linux and Windows) are not affected by this vulnerability.

See 24.3.7 release details here.

A new Deactivations API for US Messaging is now available. This API returns you a file that contains phone numbers that have been removed from the US Carriers on the specified date. This allows you to automatically keep your subscriber lists clean by removing deactivated phone numbers from your campaigns.

For more information, please take a look at our Handling Deactivated Phone Numbers FAQ and our Deactivations API Documentation.