Twilio Changelog

Today we are announcing the Public Beta launch of the native integration between Twilio Programmable Voice and Dialogflow Essentials (ES). With this integration you can bring the power of conversational AI to your Twilio calls to provide rich and natural caller experiences within your Twilio IVR. This integration is powered by a new TwiML <VirtualAgent> which is also available as a Connect Virtual Agent Studio Widget. When executed, they connect a Twilio call to your configured Dialogflow ES Agent.

To get started, select Twilio as a “One-Click” telephony partner on the Dialogflow ES console and finish with selecting one or more Twilio phone numbers to associate with your Dialogflow ES agent. Callers calling into those numbers will then be connected directly to Dialogflow. You can always use TwiML and Studio to modify the call flow.

Learn more about the integration, <VirtualAgent> TwiML, and the Connect Virtual Agent Studio Widget.

The Flex Plugins CLI now provides the ability to archive a plugin, a plugin version, or a configuration. When archived, admins or developers can no longer enable the plugin for agents via the Plugins Dashboard or Plugins CLI. Developers can archive a configuration to prevent it from being redeployed. The archive command can be used to indicate that a plugin is no longer actively maintained or it has defects and should not be enabled. Information on archived plugins or configurations can still be viewed on the Plugins Dashboard and the Plugins CLI. For more details on this feature, refer to our documentation.

With this feature, you will be able to search Twilio Elastic SIP Trunk at ease. From the console, navigate to the Elastic SIP Trunking “Trunks” page and you can now use any of the filters such as Trunk SID, Trunk Name, Termination and Origination SIP URI to better search the trunk(s) of your interest. You can see more details here.

Every US(+1) Toll-Free number is now enabled with MMS capability, out-of-the-box. Starting today, you can use Toll-Free numbers to send and receive media messages from recipients in US and Canada.

To learn more about emerging use cases for media messaging, please visit our blog post.

You can now see detailed performance data on individual emails within an Automation. Stats include information on emails triggered, emails delivered, clicks, opens, unsubscribes, bounces, and spam over time. Click Tracking data and Email Details are also available.

To see performance data on emails in an Automation, navigate to the Automations section of Marketing Campaigns, click into the detail view for an Automation, and select View Stats from the action menu to the right of an individual email in the Automation.

To correctly end an Execution for an inbound Voice call, Studio needs the “hangup” event from the Voice status callback. When that event is not received, the Execution may be left open (or “stuck”) indefinitely.

To address this, Studio now automatically configures the status callback shortly after configuring your phone number for Studio. This ensures the final “hangup” event is always received. With this release, manually setting the status callback is no longer necessary and helps avoid “stuck” Executions for inbound calls.

To learn more, review our knowledge base article.

Twilio 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.

There is a new header called X-Twilio-VerStat with the verification result. The new header is only present for incoming calls with SHAKEN PASSporT identity headers. Today, the United States is the only country where carriers instrument a call authentication framework like SHAKEN/STIR.

Twilio Programmable Voice 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.

The request webhook presents the StirVerstat parameter with the verification result. The new parameter is only present for incoming calls with SHAKEN PASSporT identity headers. Today, the United States is the only country where carriers instrument a call authentication framework like SHAKEN/STIR.

The following Programmable Video SDK versions will End of Life on September 8th, 2021 for all customers:

• Android - 4.x and below
• iOS - 2.x and below
• Javascript - 1.x

TThe above versions of the Video SDKs utilize infrastructure that is no longer considered reliable for customers. Therefore, they are currently not supported, and as of 5:00pm PT on September 8th, 2021, they will cease to function for all customers.

We are consistently updating the Twilio Video SDKs in order to provide the best possible experience for you. Upgrading to the latest SDK version will not only ensure you benefit from various performance enhancements and bug fixes, but will also allow you to take advantage of new capabilities such as the Track Priority API, Network Bandwidth API, and much more.

If you are still using one of these SDK versions and wish to continue using Twilio Programmable Video, you must upgrade your SDK to a supported version. If you are using a mobile SDK, please ensure your apps have been released and your end-users have updated before the End of Life date.

When upgrading your SDK, please refer to the following migration guides:

• Android - 1.x to 2.x, 2.x to 3.x, 3.x to 4.x, 4.x to 5.x, 5.x to 6
• iOS - 1.x to 2.x, 2.x to 3.x, 3.x to 4.x
• JS - 1.x to 2.x

All Flex applications are now required to register their external domains when flex.twilio.com is loaded within an iframe. This restriction is now enforced for new applications. Existing Flex applications have until May 3, 2021 to confirm their registered domains.

To prevent potential phishing attacks or abuse by malicious third parties, we are applying a Content Security Policy to flex.twilio.com that restricts Flex from being rendered in an iframe by untrusted domains. To continue using Flex within an iframe, including through Salesforce and Zendesk integrations, admins must register their external domains on the Flex Settings page. We have pre-populated this list based on your current application activity.

Refer to our documentation for more details.