Twilio Changelog

Emergency Caller ID is now available for Programmable Voice SIP Interfaces. Customers are now able to set a single phone number on a SIP Domain as the Caller ID to be used as the Emergency callback number on that domain. This is the phone number that will be used by emergency responders as the callback number in case the call gets disconnected.

Click here to learn more.

Studio and Functions can now be used to develop compliant healthcare applications that contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Products and Services.

Learn more about how to build on Twilio for HIPAA compliance.

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 the Android Voice quickstart for an example of how to utilize this library.

Twilio Voice Client JS SDK (twilio.js) will officially end support for Microsoft Edge Legacy on September 1st, 2020. After this date, Twilio Client apps used with Microsoft Edge Legacy will no longer be able connect to Twilio to place or receive calls.

For continuity of service, Microsoft Edge Legacy users should upgrade to the latest version of Microsoft Edge or another supported browser, before September 1st, 2020.

For more information and FAQ, check this advisory.

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.