Twilio Changelog

Twilio Elastic SIP Trunking and SIP Interfaces have added support for a new codec, G.711 A-Law, also referred to as PCMA. Twilio now supports both G.711 versions, µ-Law (PCMU) and A-Law (PCMA).

This addition allows customers more flexibility in configuring their SIP infrastructure, especially in countries where G.711 A-Law is the prevailing standard codec. It also makes connecting with their SIP customers easier, as most SIP implementations will support at least one of the G.711 codec versions. Additionally, acceptance of a new codec could conceivably reduce transcoding on customer networks, which in turn could reduce network overhead and improve performance.

Please see our Elastic SIP Trunking documentation for more information.

We have updated all Flex projects that use Automatic Updates to Flex UI 1.15.

This Flex UI release introduces minor fixes for chat interaction, a new Action for updating agent activity, and UI performance improvements.

For a full changelog, visit the Flex UI release notes.

Reminder: You can pin to individual versions of the Flex UI or manage your Automatic Updates within the Flex Admin UI.

Twilio Interconnect has been expanded with a new Interconnect Exchange Installation in Tokyo, Japan.

The new exchange provides customers with connectivity via cross connect, VPN, Bring-Your-Own-MPLS, and the Equinix Cloud Exchange with initial product support for Elastic SIP Trunking, SIP Interface and Voice WebRTC.

Twilio now has two Interconnect Exchanges in the APAC region, one in Singapore and one in Tokyo. This allows APAC customers to set up redundant interconnects from their networks to Twilio adding an additional layer or resiliency while benefiting from the security and consistency of a dedicated interconnect.

Click here for information about Twilio Interconnect and here for documentation.

The new v2 Regulatory Compliance suite, backed by programmatic public APIs and a Console workflow leveraging the intelligence of the Regulatory Rules Engine.

For additional details:

Regulatory Compliance APIs

Getting Started: using the Public API to create new Bundles

Console: Regulatory Compliance Report Getting Started

Getting Started: How to use the Compliance Report

Push notifications are critical for reaching your end users. But not every message or user event deserves a push.

Starting today, you can intercept any event using Chat’s Pre-Webhooks and choose to suppress the push by returning "mute_notification": "true". Now, system messages or user joined / left events don’t have to show up on the lock screen.

More flexibility and control over how you interact with your customers! Read more in the Chat Webhook documentation

In new TaskRouter projects and Flex projects, TaskRouter workspaces are now always multitasking and TaskRouter no longer supports switching the workspace from multitasking to single-tasking.

Existing projects with single-tasking workspaces are excluded from this change.

To learn more about multi-tasking in TaskRouter, refer to our documentation on multitasking.

Previously, 2FA was implemented at the account-level for the console. This caused owners or admins to inadvertently turn on 2FA for every user with access to their account.

With this change, users can add an extra layer of protection to secure themselves without enforcing 2FA on all other users on an account. You can view the new setting under User Settings in console. When enabled, this setting will take precedence at login.

Owners and admins can still add 2FA as a security requirement for an account through General Settings. When both settings are enabled, we will give precedence to the stronger of the two settings. Moreover, users will never have to do 2FA more than once per login session. For more information, read our 2FA help article.

Previously, when a TaskQueue had been configured for multi-reservation of workers, TaskRouter would try to establish an audio connection for every worker that accepted the reservation request, before rescinding all but one reservation. In rare circumstances, that could lead to more than one worker being placed into conference with the customer.

Now, TaskRouter will only establish the audio connection for the first worker accepting the reservation, while all other worker reservations are immediately rescinded.

To learn more about multi-reservation in TaskRouter, refer to our documentation on multi-reservation in TaskQueues.

Build multi-language flows faster and without duplicating widgets by using Liquid template variables in the Language and Voice fields of Say/Play and Gather widgets.

We are officially ending support for the Epic Conference functionality in Programmable Voice. This was a long-running beta program that allowed developers to create a Voice Conference with up to 1000 participants. It did not prove to be as useful to developers as first envisioned and so we are ending support effective today.

Our standard Programmable Voice Conference provides flexible support for multi-party voice use cases with up to 250 participants. Additional details are available here.