Twilio Changelog

Outbound calls made using the REST API are throttled and queued to never exceed the Calls Per Second (CPS) threshold value that is set up on the Account. This throttling may create undesirable behavior as call establishment may be delayed. With this release, a new attribute "QueueTime " is available to monitor the call queue time. Prior to this change, there was no indication into whether the outbound calls were being queued and delayed, which made it difficult to know when to update the CPS to an appropriate value. This change returns QueueTime with the value of the estimated call queuing time in milliseconds. This can be used to detect when CPS updates are needed.

This release of Flex UI introduces an Initial Audio Device Check. This feature allows you to perform an audio device availability check when Flex starts up to make sure you are ready to receive voice calls.

Initial Audio Device Check is currently available as a Pilot feature. To enable it, visit the Pre-Release Features Page. You can learn more about this feature within our documentation.

For a full changelog, visit the Flex UI release notes.

Twilio is now blocking outgoing calls that use unassigned calling numbers for Programmable Voice and Elastic SIP Trunking. Unassigned numbers are numbers not in service. This change will protect you and the platform from unlawful From number overrides.

You can see calls blocked by inspecting Error notifications, 13247, 21212, 32206.

Flex Insights Historical Reporting now has out of the box metrics for reporting on holds in calls. You can now build reports that identify calls where agents put customers on hold and how long the holds in calls are. Users can find agents, queues and teams that may need attention as they have too many or too long holds in their calls. See Hold Time documentation article for more details.

This release introduces loglevellogger integration to enable flexibility in handling log messages by allowing integration with other loggers and dynamic log level setting. Prior to this release, Voice Client JS logging could only be configured during Device.setup. With this release, Voice Client JS exposes a loglevel based logger which allows for runtime logging configuration that includes setting the log level to “trace”, “debug”, “info”, “warn”, and “error”. Loglevel is a versatile logger library that includes level-based logging and filtering, and provides a plugin API to enable functionality such as sending the log messages to a log server.

Answering Machine Detection (AMD) introduces several seconds in silence for the callee since the call is not connected until AMD detection has executed. This behavior leads to undesirable user experience and often leads to hung up calls. With the release of async AMD, machine detection can be executed asynchronously. When Async mode is enabled, the callee is connected immediately and AMD is executed in the background, improving the callee experience.

Learn how to enable async AMD in the Twilio AMD documentation.

The latest Twilio PHP helper library v6.0 is now available on GitHub. This latest version has full support for many of the features in PHP 7 such as scalar and return type declarations and of course the illustrious spaceship operator <=>. For PHP applications running PHP 7.2 and later, we recommend upgrading to this latest version to take advantage of the new PHP features and continue getting Twilio updates.

Note that with this release, we are officially ending support for PHP versions that are already end-of-life, including PHP 5.5, 7.0, and 7.1. If your application requires PHP versions 7.1 or below, you can continue using older versions of the Twilio helper libraries, but they will not receive updates.

You can download the latest PHP library from Packagist or source code on GitHub.

The Regulations API is moving to Public Beta. The Regulations API resource allows users to programmatically fetch the Regulations for a given phone number’s country, type, and the end-user type. The Regulations API is in sync with the Regulatory Guidelines webpage and is continually updated.

For additional details:

• Regulations Public API
• Regulatory Guidelines
• Getting Started: Creating a new Regulatory Bundle

Twilio Interconnect has been expanded with a new Interconnect Exchange Installation in Sydney, Australia.

The new exchange provides customers with connectivity via cross connect, VPN, Bring-Your-Own-MPLS, and the Equinix Cloud Exchange with initial product support for Elastic SIP Trunking, SIP Interface and Voice WebRTC.

Twilio now has three Interconnect Exchanges in the APAC region, one in Singapore, another in Tokyo and this new one in Sydney, Australia. This allows APAC customers to set up redundant interconnects from their networks to Twilio adding an additional layer of resiliency while benefiting from the security and consistency of a dedicated interconnect.

Click here for information about Twilio Interconnect and here for documentation.

Provisioning new phone numbers with identity regulations through the Twilio /IncomingPhoneNumbers API now requires an approved BundleSid. End-users will be required to include the proper documentation for regulated phone numbers, which are most phone numbers outside the US and Canada. API calls to provision regulated phone numbers that do not include a compliant BundleSID that is valid for the phone number will fail with error code 21649.

For additional details:

• Blog post on this change
• Phone Number Regulatory FAQ