Twilio Changelog

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

This release of Flex UI includes native outbound dialing and Dialpad being Generally Available. The Generally Available release of outbound dialing brings improvements in quality and reliability and solves several known limitations that include:

• Improved and more granular error reporting when an outbound call fails
  
• Flex agents can no longer place concurrent outbound calls
• Recordings are no longer stopped when an outbound call is transferred

For more information, refer to the Flex Dialpad documentation. For more details on this release, please visit the release notes for Flex UI.

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

It is now possible to do a configure per-service webhooks in the Conversations. With this feature, you can control the effects of webhooks in a particular Conversation Service. This means you can include different metadata in the URLs or even trigger different behavior for different services.

Explore the per-service webhooks documentation and give it a try!

The Workforce Management Real-Time Adherence Feed (WFM RTA Feed) is designed for partners to monitor and report on the activity of agents within a Flex contact center. Events from this feed can be used to generate a real-time snapshot of agent status.

The WFM RTA Feed is now Generally Available, and it can be used alongside historical reporting in Flex Insights to support workforce management integrations to Flex. Review our WFM RTA Feed documentation for details on getting started with the feed and the event data.

Runtime Handler version 1.2.1 introduces access to headers and cookies for incoming requests to Twilio Functions through the new event.request object. Visit our documentation to learn more about this feature.

You can use this version today by setting @twilio/runtime-handler to use version 1.2.1.

For new projects and those that don't specify a specific Runtime Handler version, we'll be rolling out version 1.2.1 over the coming weeks as the new default version.

Check out our docs to learn more about specifying which Runtime Handler version to use.

We are excited to announce the availability of 24 hour participant durations for video rooms.

You can now configure the Maximum Participant Duration for any Twilio Video room type. This value is set at the time of room creation, and upon reaching the limit, a participant will be disconnected from the room.

The default value for maximum participant duration is 4 hours. You can change this value either through the Console under Rooms Settings to make it the default for Ad-hoc rooms or as a configurable parameter via the REST API upon room creation.

For more information on configuring the maximum participant duration, view the participant duration documentation. If you are composing room recordings of participants with long durations, you may want to review the composition size limitations.

IP Commands for Super SIM® is now in Public Beta. IP Commands are a secure and lightweight solution to send UDP messages from your cloud to your Super SIM enabled devices. A cellular network typically has firewalls that block incoming connections from the Internet to the devices attached to it. This means that if your IoT device is using a cellular connection to connect to the Internet or your cloud, you can’t reach the device until the device sets up an outbound connection to your cloud. IP Commands provides a solution for this by allowing you to send the message to Twilio via the IP Commands API, which we then convert into an IP/UDP datagram and forward to the device.

IP Commands work in both directions. We also support Mobile Originated (MO) IP Commands from the device to the cloud. MO IP Commands can either be sent as a response to an IP Command received by the device or even as an unsolicited message originated by the device.

IP Commands are already enabled for your devices using Super SIM. To use IP Commands, please refer to the API documentation and a tutorial on using IP Commands.

We continue to invest in infrastructure improvements to provide scale and high reliability for our customers, and today we are excited to increase both the default maximum concurrent Room limit to 10,000 as well as the maximum concurrent Participant limit to 10,000 for Group and Peer-to-Peer Rooms.

The maximum concurrent Room threshold limits the number of Rooms that can be in-flight at the same time while the max concurrent Participant threshold limits the number of Participants that can be connected to your rooms at the same time. Both limits operate independently at the account level.

You can view your account room limit and participant limit in the Console under Room Settings. If a limit is reached, an error code (53119, 53206) is returned and it is also displayed in the Console Debugger. If your account limits were previously above 10,000, they will remain unchanged.

The default limits are designed to give developers ample room to grow while ensuring runaway issues get caught quickly. If you need to increase your account limits beyond the default maximum concurrent Room or maximum concurrent Participant limit, please contact Sales.

With Verify’s TOTP (Soft Token) channel you can support authentication through software-based authenticator apps like Authy or Google Authenticator. It’s great for businesses looking for a more secure and lower-cost option compared to SMS OTP that works offline and doesn’t require a phone number. With this release, the API is publicly available and supports production-scale workloads. Learn more here.

We have rolled back our release to Public Beta for the new Calls resource property, CallToken, back to Private Beta due to unexpected behavior on a small number of accounts. We are working on a fix and will re-release as soon as possible.

If you were already part of the Private Beta, everything will continue to work as it has been. For more information see original changelog here.

A new Calls resource property, CallToken, has been added to the Programmable Voice API. CallToken is an optional parameter that customers can use to forward their calls. A CallToken is generated when an incoming call is received on Twilio. Customers can now populate the CallToken parameter with the CallToken from the incoming call to forward their calls and maintain the same caller-id from the inbound call on the outbound call.

In the future in the United States, when SHAKEN/STIR DIV PASSporT is supported by carriers, end to end call authentication will be possible by using the CallToken.