Twilio Changelog

ISV customers registering their customers' US 10DLC Brands and Campaign Use Cases have full functional parity between the API and console registration experience for Starter and Standard.

Customers can now use the Trust Hub console to register Starter and Standard Brands and Campaign Use Cases. Illustrated screenshots and guidance on which brand type to choose for your customers is provided in the documentation.

You can now remove contacts from an Automation automatically when they have achieved the goal of that Automation. To add a custom Exit Criteria to an Automation, click to edit or create a new Automation, select ‘Contact meets following criteria’ in the Exit Criteria dropdown, and choose an engagement event. Learn more about building Automations in our Knowledge Center.

ISV Customers with a registered US A2P ISV Brand can now test their API integrations with Twilio by registering Mock Brands and Campaigns. The Mock Brand and Campaign API allows you to develop and test applications against Twilio’s A2P Brand and Campaign APIs without incurring any A2P 10DLC related fees.

Mock brands and mock campaigns are created similarly to brands and campaigns registered against the non-mock A2P APIs. Any campaign registered alongside a Mock Brand will automatically be considered a Mock Campaign and will not allow Messages to be routed on US A2P routes. And Mock Brands and campaigns expire after 30 days. These are some important restrictions and considerations to keep in mind when you’re using this API, with detailed explanations available in this guide.

We are excited to announce the release of the Video Diagnostics Web App, an open source ReactJS application demonstrating how to test a participant’s ability to have a high-quality video call with the Twilio platform - now available in Public Beta for WebRTC Go, P2P, and Group Room developers.

The application is built using diagnostics and call-readiness features in Twilio’s RTC Diagnostics SDK and Twilio’s Video Javascript SDK, including the recently released Preflight API Public Beta.

It can be customized, embedded into your application, and used as part of onboarding to ensure a successful first video call or for diagnosing issues that relate to the device, software, or network conditions of the end-user.

For more information on the Video Diagnostics application, see our blog post or visit the README.

ISV customers can now view additional brand registration information for any Secondary Brand they are registering for US A2P 10DLC. On the successful registration of an A2P brand, customers can view this additional information when using the GET Brand Registration API.

“russell_3000” is returned ‘true’ by TCR when the brand is verified as a Russell 3000 brand.

“tax_exempt_status” returns the verified tax-exempt status of a US-based nonprofit brand, such as ‘501c3’, as verified by TCR. Otherwise, this is returned as ‘N/A’.

“skip_automatic_sec_vet” is returned 'true' for ISV customers who choose to skip automated secondary vetting for a secondary brand.

You can find more details for these in ISV Onboarding API docs.

ISV customers can now choose to skip automated secondary vetting for any Secondary Brand they are registering for US A2P 10DLC. Twilio continues to recommend secondary vetting because it raises both campaign throughput and daily volume limits beyond minimums allowed by carriers. With automated secondary vetting, customers can maximize throughput and daily limits without extra registration steps.

That being said, we understand that some of our ISV customers may not want to complete secondary vetting for some of their customers based on the additional vetting fees and the usage patterns of those customers. Customers can review the usage limits available to a brand without secondary vetting in throughput for US A2P 10DLC.

This parameter SkipAutomaticSecVet is an optional parameter during brand registration, which can be used to skip secondary vetting for an A2P brand. You can find more details in ISV Onboarding API docs.

In preparation for the arrival of Windows 10 and Edge email device testing options, we will be adding the following devices on September 9th, 2021:

• Web.de Windows 10 (Chrome, Firefox, Edge)
• GMX Windows 10 (Chrome, Firefox, Edge)
• Mail.ru Windows 10 (Chrome, Firefox, Edge)

• Android - 4.x and below
  
• iOS - 2.x and below
• Javascript - 1.x

The above versions of the Video SDKs utilize older infrastructure that is no longer considered reliable for customers. Brownouts will begin this week, meaning there will be partial loss of service for a short period of time for the above SDKs, and will continue periodically until 5:00PM PDT on November 1st, 2021. After this, the older infrastructure will be fully shut off and these SDKs will cease to function for all customers. The brownouts will start with a duration of one hour and progressively increase in duration and frequency as time goes on.

If you are still using one of these SDK versions and wish to continue using Twilio Programmable Video, you must upgrade your SDK to a supported version. If you are using a mobile SDK, please ensure your end-users have updated their applications.

For more information, please see the initial changelog entry and when upgrading your SDK, please refer to the following migration guides:

• Android - 1.x to 2.x, 2.x to 3.x, 3.x to 4.x, 4.x to 5.x, 5.x to 6
  
• iOS - 1.x to 2.x, 2.x to 3.x, 3.x to 4.x
• JS - 1.x to 2.x

The Voice Insights Advanced Features Call Summary API now supports reading multiple resources with query parameters. This capability allows developers to request call summary records for specific time ranges, call states, call types, and other dimensions including whether or not Twilio detected any issues on the call or if the SIP session ended with a non-200 OK response.

For more information see our docs.

The Voice Insights Advanced Features Call Summary API now supports reading multiple resources with query parameters. This capability allows developers to request call summary records for specific time ranges, call states, call types, and other dimensions including whether or not Twilio detected any issues on the call or if the SIP session ended with a non-200 OK response.

For more information see our docs.