Twilio anticipates significant spikes in provisioning of US-based phone numbers as we approach November's 2020 U.S. election. Due to the finite capacity of the U.S. messaging ecosystem, we're implementing a Heightened Awareness Period (HAP) from September 23, 2020 until November 4, 2020.
Our goal for this short-term policy is to ensure that all customers have fair access to a secure and reliable network.During this Heightened Awareness Period, the following limitations will apply:
- A maximum of 1,000,000 additional 10-digit long code phone numbers can be added to customers' existing accounts within the +1 country code. These numbers are available on a first-come, first-served basis, with inventory being added regularly.
For more information see this FAQ.
Twilio anticipates significant spikes in provisioning of US-based phone numbers as we approach November's 2020 U.S. election. Due to the finite capacity of the U.S. messaging ecosystem, we're implementing a Heightened Awareness Period (HAP) from September 23, 2020 until November 4, 2020. Our goal for this short-term policy is to ensure that all customers have fair access to a secure and reliable network.
During this Heightened Awareness Period, the following limitations will apply:
Account-level long code SMS rate limits have been implemented based on the amount of phone numbers:
- Customers with 2,000 or more 10-digit long code numbers on their project can send up to
2,000 MPStoward the United States.
- Customers with 100,000 or more 10-digit long code numbers on their project can send up to
4,000 MPStoward the United States.
For more details, please refer to this FAQ.
Twilio now supports sending up to 25 messages per second through WhatsApp.
If messages are sent at a rate higher than 25 MPS, Twilio maintains a queue. For very high outbound message volumes, messages can remain queued for up to 4 hours.
To achieve higher MPS, you can use Messaging Services. This allows you to distribute high volume across many WhatsApp senderes within the Messaging Service.
Twilio Programmable Voice and Elastic SIP Trunking now perform SHAKEN/STIR verification on incoming calls to your Twilio local phone numbers. It can be used to display a trust indicator or to make a routing decision, such as bypassing a voice captcha or IVR and directing the call to an end user.
A verified call that has been given the highest attestation under SHAKEN/STIR means that the carrier that originated the call both (1) knows the identity of the caller, and (2) knows the caller has the right to use the phone number as the caller ID.
In Programmable Voice the request webhook presents the StirVerstat parameter, and in Elastic SIP Trunking there is a new header called X-Twilio-VerStat with the verification result. The new parameter and header are only present for incoming calls with SHAKEN PASSporT identity headers. Today, support for the SHAKEN/STIR call authentication framework is being deployed in the United States only.
This release of Twilio Voice SDK now uses Chromium WebRTC 83. With this release, users will hear audio much sooner after the Call.Listener#onConnected callback than in prior releases. This upgrade ensures that when Call.Listener#onConnected is raised to the developer the media connection has been fully established. Additionally, the MOS calculation algorithm has been updated to make it monotonically decreasing with increasing jitter and packets-lost-fraction values over a range of RTT values.
To learn more about this release on our changelog.
You could always have multiple SMS participants in the same conversation talking to each other. However, each participant was previously bound to a single proxy address number through which they received all of the messages in the Conversation. In this scenario, each participant had no way of knowing how many people the proxy number represented.
It is now possible to add your US or Canada based clients as Group participants, utilising a Group MMS protocol. As a result, your clients will observe an iMessage style experience and easily see who said what. This is especially valuable for use-cases which expect an active participation of all interested parties, like wealth management, personal shopping, or real-estate industry.
Explore the Group Texting documentation and give it a try!
This release of Flex UI and WebChat UI introduces the public beta version of chat attachments. Chat attachments now includes drag-n-drop for your files, and you can compose a single message with both text and an attachment. For a complete overview of the feature and developer guides to programmatically customize the experience, check out the chat attachment docs.
Other notable changes:
- Flex WebChat UI CDN bundle size has been reduced to 390kb.
- Real-time Queues View is now enabled for all accounts. For more details on this feature, visit our Real-time Queues View docs.
Twilio SendGrid now allows you to define multiple From addresses in personalizations objects. This allows you to override the default sender in each personalization as long as the default sending domain and personalizations sending domains match. For more information, visit our Personalizations documentation.
You can now disable any Verify v2 delivery channel (SMS, Call, Email) that you are not using to reduce your risk of potential abuse. Navigate to your Verify Service Settings page to use this feature.
This major release of Twilio Voice SDK now uses WebRTC 83. With this release users will hear audio much sooner after the [TVOCallDelegate callDidConnect:] callback than in prior releases. This upgrade ensures that when [TVOCallDelegate callDidConnect:] is raised to the developer the media connection has been fully established. Additionally this release improves the interoperability of the SDK with Swift. Lastly, the MOS calculation algorithm has been updated to make it monotonically decreasing with increasing jitter and packets-lost-fraction values over a range of rtt values.
To migrate from 5.X to 6.X please see the migration guide.
To learn more about this release on our changelog.
Introducing the API for Elastic SIP Trunking Call Transfer (SIP Refer) feature. This feature enables you to move an active call from one endpoint to another. Twilio's Elastic SIP Trunking product supports "blind" call transfers. This allows you to configure SIP Refer on a Trunk using the API.
For details, please check our Elastic SIP Trunking API for Call Transfer via SIP REFER documentation.
As a side note, you can also configure Elastic SIP Trunking Call Transfer (SIP Refer) feature through Twilio console. Details of console configuration can be found here.
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.
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:
|40139||ERROR||Failed to issue Dequeue instruction due to missing or invalid Activity Sid.|
|40147||ERROR||Failed to issue Supervise instruction due to missing or invalid ‘contact_uri’ property.|
|40149||ERROR||Failed to issue Conference instruction due to missing ‘conference_sid’.|
The following list of Error and Warning messages have been updated:
|40005||WARNING||Changed Type from Twilio to Application.|
|40140||ERROR||Updated message text and description for clarity.|
|40142||ERROR||Updated message text and description for clarity.|
|40148||ERROR||Updated 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
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.
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.
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.
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.