Twilio Changelog

Super SIM now offers Distributed Internet Breakouts. Up until now, all traffic from/to an IoT device using Super SIM has been going through the Twilio Mobile Core instance deployed in Ashburn, USA. Twilio now has an additional location in Frankfurt to provide Internet breakout for Super SIM customers in Europe and Africa, with more locations to follow.

Using distributed breakout to the Internet is important to achieve low latency, which opens up new use cases such as adding real time voice/video communications to an IoT device. To make use of the breakout location in Frankfurt, Super SIM customers must configure “de1.super” as the APN (see Super SIM APN configuration). The existing default APN “super”, when used, results in traffic breaking out to the Internet via Twilio Mobile Core in Ashburn, USA.

If you are interested in using the Frankfurt Internet breakout location, please reach out to Twilio support.

Twilio has completed validation of the integration between Flex and Survey Dynamix. Survey Dynamix can capture feedback over post call voice IVR, outbound voice IVR, conversational SMS, Web SMS, email, and web surveys.

To learn more about Survey Dynamix’s capabilities and how to enable it for your application, visit our integration documentation.

The TwiML <Conference> noun and the Conference Create Participant API have been updated to provide a new announcement status callback event. This event will be sent to the provided status callback URL when the announcement to a conference or a participant ends normally or fails due to a Twilio-internal error.

This allows developers to be informed when an announcement has completed and additional call processing instructions can be executed, or when an announcement has failed and a retry attempt is needed.

For more info, see our docs for the <Conference> noun status callback event and for creating a Conference participant.

We are excited to announce that the Event Streams API is now in public beta.

Event Streams is a single API for delivering event data from multiple Twilio channels directly into your infrastructure, so that your Twilio data is easily accessible, automatically interpretable, complete, and accurate.Currently, events are available from Twilio Messaging, Voice Insights, and TaskRouter. Events can be delivered directly to a destination of your choice, starting with Amazon Kinesis and webhooks. We are actively adding events from more Twilio products and supporting more external destinations.

Check out our docs and start building with your Twilio event data through Event Streams.

You requested an ability to download Twilio data at scale so that you can easily support different business functions like fraud analytics, legal compliance needs, warehousing and business analytics based on this data. So, we created Twilio’s “Bulk Export” tool. The BulkExport API provides an efficient mechanism for retrieving all of your activity logs from the Twilio platform on an ongoing basis, or for one-off downloads. Using BulkExport, you can access daily or historical dumps of the previous day’s Messages, Calls, Conferences, or conference Participants, eliminating the need to iterate through the list resource one page at a time to download your record.

Changes since Beta launch are

• Addition of “EstimatedCompletionTime” and “QueuePosition’ parameters to help you determine when your job will complete
• Product hardening and enhanced security features (limit on per-day exports and export notifications for account owners/admins) to prevent data exfiltration in case an account takeover has happened.

The retention policy on Functions and Assets is being updated. Functions without any Function Versions and older than 30 days will be deleted.

Assets without any Asset Versions that are older than 30 days will also be deleted.

Function Versions or Asset Versions older than 30 days that are not part of a Build or an active deployment will also be deleted.

This policy will not impact any active deployments at any point. This policy will only apply to users using the API, serverless toolkit or the new UI editor. This policy does not apply to Functions(Classic) and Assets(Classic).

This new policy will come into effect on May 30th, 2021. You can read more about this deletion policy here.

Twilio has completed validation of the integration between Flex and Virtual Hold Technologies (VHT). VHT creates a better customer experience by allowing customers to avoid waiting on hold. This allows contact centers with peaks and valleys in incoming traffic patterns to optimize their staffing levels.

As part of the integration, we have documented the steps required to set up this integration as well as two sample deployment scenarios.

To learn more about VHT’s capabilities and how to enable it for your application, visit our integration documentation.

You can now include a “view in browser” link in your Marketing Campaigns emails using the Weblink Substitution Tag.

The "view in browser" link points to an online version of your email, which will display your HTML as designed, protecting against potential email client rendering issues. This ensures recipients have a fallback to view your email, and provides them an option to share the email with friends using the link in addition to forwarding the email.

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

This release of Flex UI introduces an improved troubleshooting experience for Flex UI users. Users of Flex UI will now be able to get error notifications via a Debugger UI and will be able to download a report with full error descriptions and logs. Flex UI developers will now be able to retrieve errors and logs programmatically to implement customized error monitoring and reporting. This Debugger UI is now in Pilot and can be enabled for your account on the Feature Settings Page.

To learn more about Flex UI troubleshooting, Debugger UI, and programmatic access to errors and logs, visit our Flex docs.

Other notable changes include

• Initial audio device check (previously in Pilot release) is now in GA and will be enabled by default for all accounts.
  

For a full changelog, visit the release notes for our client libraries:

Flex UI 1.25

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

You can now query for information about your calls in the Elastic SIP Trunking Call Log using the SIP Call ID found in your SIP network.