Twilio Changelog

Additions and changes to the Twilio platform

Filter by:Clear all

With this release developers can pass custom parameters when dialing Twilio Client using Twilio Voice REST API. You can build personalized application experiences for end users by displaying valuable contextual details about the incoming call. For example, you can pass the customer name, type, or product of interest when dialing Twilio Client, and display to the agent. 

The custom parameters can be specified as a query string in the ‘To’ parameter of the Create Call Resource and delivered via the Twilio Voice Client.  

Learn more about how to share custom information between your applications


We have updated TaskRouter’s error and warning messages to improve clarity and troubleshooting.

The following list of Error and Warning messages have been added:

TitleLevelDescription
40139ERRORFailed to issue Dequeue instruction due to missing or invalid Activity Sid.
40147ERRORFailed to issue Supervise instruction due to missing or invalid ‘contact_uri’ property.
40149ERRORFailed to issue Conference instruction due to missing ‘conference_sid’.

The following list of Error and Warning messages have been updated:

TitleLevelChange
40005WARNINGChanged Type from Twilio to Application.
40140ERRORUpdated message text and description for clarity.
40142ERRORUpdated message text and description for clarity.
40148ERRORUpdated message text and description for clarity.


For Editions customers, we are introducing a more flexible way to view the Audit Event data in the Twilio Console. This allows viewing by user and filtering the event data.
The list of events now tracked by Audit Events includes new event types, such as console logins. The new event types are only visible in the Twilio console in Audit Event Insights are documented with the other Audit Event data: https://www.twilio.com/docs/usage/monitor-events.
These changes do not impact the Audit Event API. New event types are not available yet in the Audit Event/Monitor Event API


Programmable Messaging

Twilio Deactivations API for US Messaging now available GA

A new Deactivations API for US Messaging is now available. This API returns you a file that contains phone numbers that have been removed from the US Carriers on the specified date. This allows you to automatically keep your subscriber lists clean by removing deactivated phone numbers from your campaigns. 

For more information, please take a look at our Handling Deactivated Phone Numbers FAQ and our Deactivations API Documentation.


When you send a verification attempt via SMS One-Time-Passcode, you can now view the SMS's Delivery Status & Error Codes in your Twilio Console. Navigate to Verify > Services > Logs as shown in the example screenshot below. This helps you to troubleshoot non-delivery of SMS. 

verification-details.jpg


CVE-2020-24655 - A race condition in the Twilio Authy 2-Factor Authentication Application allowed a user to potentially approve/deny an access request prior to unlocking the application with a pin on older Android devices, effectively bypassing the PIN requirement. This issue has been fixed as part of the 24.3.7 Release of the Twilio Authy App. Other operating systems (iOS, MacOS, Linux and Windows) are not affected by this vulnerability.

See 24.3.7 release details here.


Cloud calling solution provided by ZoomPhones has support for “bring your own carrier” (BYOC) giving ZoomPhone customers access to a range of PSTN connectivity services to fit their business needs. You can leverage global SIP trunking services from third-party providers, including Twilio, and realize geographic coverage, pricing, flexibility and other advantages. 

This release increases the security of the Zoom Phones BYOC to Twilio Elastic SIP Trunking Interconnection to use Secure Real-time Protocol (SRTP) to encrypt media and Transport Layer Security (TLS) to encrypt signaling. 

If you're configuring your Elastic SIP Trunk to interconnect to Zoom Phones BYOC, please ensure you enable Secure Trunking. To learn more about how to configure your Elastic SIP Trunk please see here.

zoomphones.png


Programmable Video

Support for iOS 14.0 Local Network Privacy Policy GA

The Programmable Video iOS SDK 3.7.0 release adds support for the new local network privacy policy introduced in iOS 14.0 and iPadOS 14.0. This policy requires user permissions for local network access and Peer-to-Peer applications using previous versions of our iOS SDK may break if permission is not granted. Applications that use Group Rooms are unaffected.

With this SDK release the local network path is no longer automatically included as one of the connection candidates. This modification ensures that users will not see a change in application behavior when upgrading to iOS 14.0 or iPadOS 14.0. Developers can still opt to include the local network as a connection candidate by setting a parameter. We recommend developers upgrade their Peer-to-Peer application to ensure correct behavior with iOS 14.0 and avoid any adverse changes to the experience.

For additional information, see the iOS SDK changelog and our helpdesk article.


Flex-Salesforce integration v1.3.1 and Flex-Zendesk integration v1.2.0 introduce the use of Flex Native Outbound Dialing for its click-to-dial feature. Check our migration guides for Salesforce and Zendesk integrations to see how you can upgrade your integration.


Super SIMs can now be put into a new state called ready.  Ready state lets your Super SIMs connect to cellular networks without incurring a monthly subscription fee until one of the following 3 conditions are met:

  • The Super SIM has been in ready for 90 days
  • The Super SIM has used 250 KB of data
  • The Super SIM has sent or received 5 SMS Commands

Use ready state to enable and test your device’s connectivity, without incurring monthly fees,  before it’s sent to your customer or deployed into the field.

Once any of those 3 conditions are met, the Super SIM’s status will automatically update to active, at which point, the monthly subscription fee will start being charged.

Super SIM state diagram

Learn more about all of the Super SIM states here.


Super SIM Usage Records can now be filtered to show usage incurred on a single Super SIM, Fleet, Network (e.g. AT&T US, Telstra) or within a single country (e.g. United States, Australia).  You can combine those filters with others to do complex filtering such as getting the usage for a single SIM on a single Network, or all SIMs within a Fleet.

You can also now group Usage Records around a resource type (e.g. Super SIMs, Fleets, Networks, or Countries) within the response data.  For example, if you group your Usage Records by Super SIM, each record will contain the aggregated usage per Super SIM over the requested period. You can use this to efficiently pull usage for large fleets without having to make separate API calls for each resource.  You can combine groupings with different filters to make complex requests like:

  • How much data did each of my Super SIMs use within a particular Fleet yesterday?
  • How much data did each of my Super SIMs use in France in the last 30 days?
  • How much data did my Super SIMs use on each Network in Argentina last week?
  • How much data did each of my Fleets use on AT&T in the United States in the last 3 days?

Programmable Messaging

Upcoming Changes to Media Deletion GA

Starting October 14, Deleting a Message log will also automatically remove any Media objects associated with that message. This allows a more intuitive experience when customers issue delete requests on messages containing media. The change will apply to all messaging channels supporting media including MMS, WhatsApp and Facebook Messenger.

More details of the changes to coming message records and media availability are published here


Marketing Campaigns

Segmentation based on Automation Events GA

Twilio SendGrid now offers the ability to segment contacts based on their engagement with your automated emails. For more information, visit our Knowledge Center.


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

This release of Flex UI introduces new filter options for the Teams View. With Hidden Filters, your developers can control which users each supervisor is able to view and manage. This is useful if you want a supervisor to only manage their team, instead of being able to view all agents by default.

Other notable changes:

  • Flex UI API Reference now includes the list of component children for dynamic components (with information such as key, condition, type, alignment and description)

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

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


Elastic SIP Trunking

Upgrade your Elastic SIP Trunking calls-per-second (CPS) on-demand GA

Trunking Termination Calls per Second (CPS) refers to how many new SIP Trunking call setups are allowed in one second for Trunking Termination calls (outgoing traffic from your communications infrastructure to the PSTN). Twilio, by default, provides the ability for you to place 1 CPS per Trunk per Region (see limits). 

With this release you are now able to immediately increase your Trunk CPS settings per region (up to 15cps) in the Console, under the specific Trunk, under Termination settings.

Screen Shot 2020-09-09 at 12.30.27 PM.png

For details please refer to our user documentation and Trunking CPS pricing.


Serverless

All New Functions and Assets UI is now available! Beta

All new Functions and Assets UI is now available. The new Functions Editor brings together Functions, Assets, Logs and Settings in single intuitive design for an effective development experience. This UI utilises Functions and Assets API and delivers a seamless experience between UI and API. Previous version of Functions Editor continues to be available under Functions (Classic).

Check out the docs or try it out now in Twilio Console!

Functions Editor Main Page


Twilio Conversations (Chat and SMS channels), Programmable Chat, and Twilio Sync 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.


Twilio <Pay> now enables PCI-Compliant contact center payment use cases with the launch of Agent Assisted <Pay>. Developers can build payment flows that allow agents to securely capture caller payment information during a voice conversation using the Agent Assisted <Pay> API. This launch extends Twilio’s existing support for IVR payments via our PCI DSS compliant Voice platform, <Pay> TwiML, and integrations with <Pay> connectors to Agent Assisted payments. 

When leveraging the Agent Assisted <Pay> feature within their contact center (including Flex), agents control the payment flow and guide callers by requesting payment information one at a time (e.g., payment card number, expiration date, security code). Agents can continue to converse with callers but will not hear their DTMF, ensuring the security of the payment information. For additional details visit the Agent Assisted <Pay> blog post

Get started with Agent Assisted <Pay> APIs. Learn more about PCI Compliance, <Pay>, capturing IVR payments, and PCI Recordings.


Programmable Voice

Android AudioSwitch is now Generally Available

Android AudioSwitch is now Generally Available. This Android library reduces the complexity of adding support for audio routing and device selection in an Android app. You can now integrate AudioSwitch into your app with just a few lines of code. It handles audio routing and selecting built-in, wired, or Bluetooth headsets seamlessly.

Learn more about AudioSwitch in our blog post and check out our open source repository here.


Programmable Messaging

120 days of data available in Messaging Insights GA

All Messaging Insights reports now contain 120 days of data. This data becomes visible upon choosing 120 days in the Date-Time picker dropdown within Messaging Insights available via the Programmable Messaging console.  

This is an enhancement from the 30 days of data that we launched into General Availability in June and was one of the top three requests from early customers.


Show more