Twilio Changelog

Twilio Super SIM® is available for download as an eSIM profile. Until now Super SIMs were available as physical SIMs in various form factors (2FF/3FF/4FF and MFF2). With the eSIM support, you can now reserve a SIM profile via a new API and then download the reserved SIM profile from Twilio’s SM-DP+ server to your eSIM/eUICC-enabled IoT device. Here is the typical call flow that you will use for downloading a Super SIM profile:

You can now undo or redo recent changes made in the Design and Code Editors. To undo an action, use the undo arrow in the top navigation above the editor, or use the Ctrl or Cmd + Z keyboard shortcut. To redo an action, use the redo arrow in the top navigation above the editor, or use the Ctrl or Cmd + Shift + Z keyboard shortcut. You cannot undo/redo changes once you have left the browser session.

You can now manage a Phone Number’s Messaging Service assignment from the Phone Number’s configuration page in Console.

If a Messaging Service assignment is important to the success of your Phone Numbers’ messaging use-case (such as A2P messaging with US local 10-digit long codes) and if the Messaging Service is configured to defer SMS handling to the Phone Numbers' configuration: you can now assign a Messaging Service while also configuring the Phone Number to handle messaging with Flex, Studio, Functions or TwiML App.

You can determine whether the Messaging Service is handling or deferring message handling with the Phone Number from the Phone Numbers’ instance page in Console.

Super SIM Connection Events allow you to follow a Super SIM connected device’s journey from when Twilio first sees it trying to connect to our mobile core, to when it gets connected and starts to use data, to when it ends its data session. Once a device has successfully started a data session, update events will be published while the device stays connected to give you near real-time usage information for each Super SIM.

The Console UI for Programmable Voice calls per second settings has been updated to provide a similar user experience to Elastic SIP Trunking CPS. Additionally, the self-service limit has been increased from 15 to 30.

A major version release of @twilio-labs/plugin-serverless and twilio-run is now available. With this release, we are saying goodbye to .twilio-functions in exchange for two files that should hopefully serve you all better.

This release contains breaking changes that you can read about in the announcement blog post.

On top of bug fixes, new features, and improved experience, we now have a brand new Twilio CLI Plugin: @twilio-labs/plugin-assets. An easy way to upload public assets from your command line:

twilio plugins: install @twilio-labs/plugin-assets

twilio assets: init

twilio assets: upload YOUR_FILE_NAME

Behind the scenes, we also moved the entire project to a monorepo which should enable us to ship new improvements faster in the future.

As a reminder: this is a Twilio Labs project meaning this isn’t a formal “GA” launch and users are encouraged to file issues on our GitHub.

The Serverless Toolkit is a collection of tools to improve the development of Twilio Functions and Assets. Read the blog to learn more about what features we added in the latest major version of the Serverless Toolkit and what things changed.

A new option for handling inbound messages on your Messaging Services has been launched. In addition to the previous options, you can now defer to the webhook set on the phone number, allowing each phone number to have a diferent configuration for incoming messages while they are part of the same messaging service.

This lets you utilize the benefits of a messaging service for outbound messages, but have inbound messages routed differently to fit the needs of your business.

You can find this new option in the Integrations section of your Messaging Service and is also available on the Messaging Services API as the property "use_inbound_webhook_on_number": true

We are changing the behavior of <Dial> for accounts which have enabled Enhanced Programmable SIP Features. This could represent a breaking change for some call flows. If your account has not enabled Enhanced Programmable SIP Features, this does not represent a change.

The changes are:

• If a <Dial> action url is specified, Twilio will make a request to the provided action callback when the parent call is transferred to a new TwiML via call modification. Twilio will not execute any TwiML returned by the action URL since processing of the call has been transferred to the new TwiML.
• If no <Dial> action url is specified, the parent call will continue to the next verb in the current TwiML document when the parent call is modified to use new TwiML. Note: in most cases the verb after the <Dial> will not be executed since the call has been modified, but if the next verb is <Redirect> Twilio will make a request to the provided URL.

This change brings Enhanced Programmable SIP Feature enabled accounts behavior in alignment with the behavior of TwiML for non-enabled accounts.

For more information about Enhanced Programmable SIP features, see our blog post and the TwiML changelog.

Twilio is adding functionality to the Programmable Voice <Dial> verb specific to SIP Connectivity. The new functionality may affect your existing applications. The deadline to account for these changes in your application code is 31 July 2021.

In most cases, your existing code will continue to function; however, there are some functional improvements and behavioral changes which could possibly impact your application. We recommend testing your existing application code in dev or staging environments before 31 July 2021 to identify any potential impacts..

The new features can be enabled on the Programmable Voice Settings page. This will activate the new features on an account-wide level. These features will be applied to all accounts after 31 July 2021.

We are planning to enable this new feature set across all Twilio accounts on 31 July 2021, and will allow you enough time to adjust your applications to use this new functionality, and fully test these changes. As always, Twilio will always be there to help you through this process, if you need assistance, or run into problems.

For more information see the TwiML changelog.

Video Log Analyzer records for Room and Participant summaries are now available via Event Streams. Developers can subscribe to these events and they will be sent to the provided destination. Room and Participant summary records are published to Event Streams when the processing of the summary is complete. For more information about Event Streams, see our blog post announcing the public beta.