Twilio Changelog

You can now bulk delete Automations using the multi-select tool from the Automation homepage.

To select one or more Automations to delete, click the checkbox to the left of the Automation. Next, open the Selected dropdown and then click Delete.

Programmable Voice SIP Registration has been updated to allow SIP Endpoints to be registered to Twilio via all of Twilio’s Edge Locations globally. Previously, all SIP endpoints were required to register to the US1/Ashburn edge.

The format for the Edge-specific domains is now as follows:

{domain-name}.sip.{edge-location}.twilio.com

You should typically have your SIP devices register and send SIP messages via the Edge Locations closest to their physical location.

When sending a call to a registered SIP endpoint it is no longer necessary to include the edge location in the URI. Twilio's backend infrastructure knows which edge location the endpoint has registered on and will automatically route the traffic to the appropriate destination. The new URI format for calls to registered SIP endpoints is:

{domain-name}.sip.twilio.com

This change will not affect SIP endpoints using the previous method, i.e., endpoints registered using the US1/Ashburn edge will still work using the previous format.

Learn more in our blog post, or see the SIP Registration documentation for more details.

You can now add any reserved field or custom fields to a signup form. This means marketers can capture more of the data that they rely on when contacts sign up via a signup form.This means marketers can capture more of the data that they rely on when contacts sign up via a signup form. The collected data will then flow directly into Contacts within Marketing Campaigns.

Programmable Voice SIP interface now supports Inbound SIP REFER to Twilio. When an inbound SIP REFER message is received on a SIP call initiated using the TwiML <Dial> verb, Twilio accepts the REFER message and generates a webhook to customer application. This allows customers to initiate call transfers from their SIP devices. Please see the SIP REFER-to-Twilio documentation for more details.

In addition, Programmable Voice SIP interface now supports multidial to <Sip> endpoints, allowing you to dial up to 10 different <Sip> endpoints using the TwiML <Dial> verb, prior to this release TwiML <Dial> only supported multidial on <Number>, or <Client>.

Learn more in our blog post, or see the SIP Multidial documentation for more details.

Emergency Calling is now generally available in the United Kingdom for Elastic SIP Trunking. Customers are now able to make Emergency Calls from their Twilio United Kingdom local phone numbers that are capable of emergency calling using Elastic SIP Trunking with the Twilio platform, which will route emergency calls to the appropriate Public Safety Answering Point (PSAP) and pass along the corresponding emergency address.

Learn more here.

In order to enhance security for all of our users, Twilio SendGrid now requires customers on paid plans to use API Key authentication on all API requests and SMTP configurations. Customers must also enable Two-Factor Authentication (2FA) for all users, subusers, and teammates. Visit our documentation for more information on Upgrading to API Keys and Enabling Two-Factor Authentication.

This release of Flex UI and WebChat UI introduces new syntax options for Chat Markdown and overall improvements in stability of this feature including several bug fixes. To learn more about Markdown, visit our Flex docs. Markdown is currently in Beta and can be enabled for your account using a Pre-release feature flag.

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

Emergency Calling is now generally available in the United Kingdom for Programmable Voice SIP Interfaces. Customers are now able to make Emergency Calls from their Twilio United Kingdom local phone numbers that are capable of emergency calling using Programmable Voice SIP Interfaces with the Twilio platform, which will route emergency calls to the appropriate Public Safety Answering Point (PSAP) and pass along the corresponding emergency address.

Learn more here.

Voice Insights Subaccount Dashboard has been updated to allow for filtering based on the edge location or media region where subaccounts' calls took place.

This allows you to compare the performance of subaccounts across regions. For example, you may find that a subaccount that is performing well in Ashburn (us1) is actually an outlier in terms of call behavior for calls in Dublin (ie1).

Edge locations can be included or excluded from the results, and the underlying data can be exported to CSV.

For more information see our docs.

Voice Insights Subaccount Dashboard has been updated to allow for filtering based on the edge location or media region where subaccounts' calls took place.

This allows you to compare the performance of subaccounts across regions. For example, you may find that a subaccount that is performing well in Ashburn (us1) is actually an outlier in terms of call behavior for calls in Dublin (ie1).

Edge locations can be included or excluded from the results, and the underlying data can be exported to CSV.

For more information see our docs.