Twilio Changelog

Embedding VoIP calling functionality on Android requires adding support for Audio Device switching and routing. This functionality is complex as it requires development and testing to support various Android versions and the variety of input and output device types available.

The new open source Twilio AudioSwitch Library for Android removes this complexity and can be easily embedded in just a few lines of code to handle switching to and selecting the built-in, wired, or Bluetooth mics and speakers seamlessly.

This library is available in open source format and can be found here.

See Video Android quickstart and Twilio Video App for examples of how to utilize this library.

Twilio’s Evaluations API resource is in public beta so you can receive transparent feedback to understand the evaluation and failure reason(s) of your Regulatory Bundle via API.

Resources:

• Evaluations Public API Resource Reference
• Evaluations Public API Blog Post

The Marketing Campaigns Single Sends API has been updated to simplify the steps to create, schedule, and send Single Sends via the API. Users no longer need to create a template first. To create and save a new Single Send, all that is required is a name. For complete details, please see our overview page and the API reference documentation.

Twilio conference log console page has been updated to reflect the correct duration of conference and participants. Previously, conference and participant durations were displayed based on the duration of the underlying call(s), which did not accurately calculate the duration for scenarios where a call leg spanned more than one conference (i.e. call transfers). Conference duration will now be displayed as the time between conference creation and conference completion. Participant duration will now be displayed as the total time between when the participant joined the conference and left the conference. This is strictly a change to the Twilio console, and does not impact how conferences are billed.

We have added the Task property task_queue_entered_date to all relevant TaskRouter Events to enhance historical reporting and TaskQueue insights.

When retrieving TaskRouter Events history, the task_queue_entered_date is now included with the following Events’ data:

• task.created
• task.updated
• task.canceled
• task.wrapup
• task.completed
• task.deleted
• task.system-deleted
• reservation.created
• reservation.accepted
• reservation.rejected
• reservation.timeout
• reservation.canceled
• reservation.rescinded
• reservation.completed
• reservation.wrapup
• reservation.failed
• task-queue.entered
• task-queue.timeout
• task-queue.moved
• task.transfer-attempt-failed
• task.transfer-canceled
• task.transfer-completed
• task.transfer-failed
• task.transfer-initiated
• workflow.entered
• workflow.target-matched
• workflow.timeout
• workflow.skipped

To learn more about the Task property task_queue_entered_date, please refer to our documentation on Task properties.

To learn more about the TaskRouter Events resource, please refer to our documentation on TaskRouter Events.

Voice Insights now contains information about Branded Calls and SHAKEN/STIR attestation, and allows for filtering and aggregation based on these values in the Dashboard.

Branded call and verified call answer rate is available as a subgraph in the Connection Rate section. This allows you to compare the answer rate for branded/verified calls against the answer rate for non-branded/non-verified calls.

Additionally, the Voice Insights Dashboard has new top-level filter options that allow you to filter results based on whether a call was branded or had a verified caller ID.

Note that if no branded calls are placed on an account these options will not be present. At least one branded or verified call needs to have been placed in the timeframe for which the Dashboard has been filtered.

For more information, see the docs.

The Client Insights preview API is officially end-of-life May 1, 2020 and will no longer respond to API requests. The preview API also powered the Client Insights Dashboard which has been removed from Console and now redirects to the Voice Insights Dashboard.

If your application is making requests to any of the preview API endpoints described below, you will need to migrate to the new API endpoint.

• Client Call Summary
  • https://preview.twilio.com/insights/Calls/{call_sid}/Summary
  • Call summaries for all call types are now provided via the Summary API
• Client Events
  • https://preview.twilio.com/insights/Calls/{call_sid}/Events
  • Call events for all call types are now provided via the Events API
• Client Metrics
  • https://preview.twilio.com/insights/Calls/{call_sid}/Metrics
  • Call metrics for all call types are now provided via the Metrics API
• Client Reports
  • https://preview.twilio.com/insights/Calls/Report
  • The Reports API is not being directly replaced at this time

If you need assistance moving your application over to the new endpoints we have created a migration guide to assist. For more information, see the initial end-of-life changelog entry and the preview API shutdown documentation.

Single Sends in Marketing Campaigns are now easier to find using new search and filter functionality. Users can search for a Single Send by name, or can filter to view all Single Sends by a particular status (draft, scheduled, or triggered) as well as by category.

With Flow publishing support built into the Studio REST API v2, you can now create, publish, and manage your Flows programmatically without having to log in to Twilio Console.

Flow definitions are exposed as JSON schemas and can be easily updated via the Twilio helper libraries and Twilio CLI.

With the new Flows endpoint you can

• Integrate Flow publishing into your CI/CD pipeline to automate Studio deployments
  
• Programmatically move Flows between accounts or subaccounts
• Create your own custom, branded Studio front-end UI

The Studio REST API v2 is now available on all customer accounts.

To learn more, read the announcement on our blog or try the quickstart.

Twilio Programmable Call Recordings now allows PCI compliant call recordings within the Twilio Programmable Voice environment. By providing a public key to encrypt recordings and enabling PCI Mode in Console, call recordings can be captured in a PCI compliant manner.

Traditionally, call recordings are used to analyze agent and customer interactions. However, they require special handling when capturing credit card information. To continue to record your voice calls and maintain PCI compliance within Twilio, you must have PCI Mode, Voice Recording Encryption and PCI compliance for Voice Recording enabled using Voice Settings Console page.

Once these settings are enabled on a project, Call Recordings will only be stored by Twilio for 72 hours and must be retrieved within this period. Once deleted, these recordings will no longer be recoverable by either Twilio Console or API request.

To learn more about Twilio PCI compliance and to access customer responsibility matrix, please vist https://www.twilio.com/pci-compliance