Twilio Changelog

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.

Voice Insights has been updated to appropriately identify the codec of calls using a dynamic RTP payload ID. Previously, some calls established using a codec with a dynamic RTP payload ID may not have displayed the correct ID in the Call Summary API response and the codec name may have been missing in Console.

If your application has logic built around the RTP payload ID from Call Summary API responses, you should be aware that codes like Opus will now return a broad range of potential payloads. Calls established with non-dynamic RTP payload IDs are not impacted by this change.

Voice Insights has been updated to appropriately identify the codec of calls using a dynamic RTP payload ID. Previously, some calls established using a codec with a dynamic RTP payload ID may not have displayed the correct ID in the Call Summary API response and the codec name may have been missing in Console.

If your application has logic built around the RTP payload ID from Call Summary API responses, you should be aware that codes like Opus will now return a broad range of potential payloads. Calls established with non-dynamic RTP payload IDs are not impacted by this change.