Twilio Changelog

In our efforts to constantly improve customer experience and increase our adherence to compliance best practices, the Generic Pay Connector is now available in the TEST and LIVE mode. In the TEST mode, you can configure your payment gateway URL and perform testing using test credit card and bank account numbers. 

By default, any new Generic Pay connector instance will be created in the TEST mode. In order to move your connector to LIVE mode to perform live transactions, you will need to file a support ticket with Twilio with following details: The latest (non-expired) PCI Attestation Of Compliance (AOC) document received from your payment gateway, the configured URL of your payment gateway and a confirmation that you have reviewed the AOC document of your payment gateway.

Once approved, you can switch your connector instance to LIVE mode and your payment gateway URL will become immutable. After moving to LIVE mode, any changes to the configured payment gateway URL will require a support ticket with the details mentioned above.

Learn more about this feature in our API Docs.

Voice Integrity for Spam Remediation is now available in Public Beta.  We have added  Voice Integrity Trust Product in Trust Hub which enables you to register your Twilio phone numbers to remediate spam labeling through the Trust Hub API.

This allows you to:

• Increase your call answer rates by making sure your phone numbers do not get labeled as spam and avoiding calls getting blocked due to negative reputation. 

If you are currently using Voice Integrity in private beta, you will need to update your code. 

To learn more about Voice Integrity, please check our docs. 

Read more about Voice Integrity in this blog post.

Twilio has updated the behavior of status callbacks for calls placed to Android and iOS Voice SDK applications. Starting 15 March 2023, Twilio will emit the ringing callback after the mobile application has successfully received the push notification and established a connection to Twilio. Previously, we would emit the ringing the callback as soon as the push notification was sent. Devices that were powered off, unreachable due to network availability, or users who were not logged in were inaccurately reporting the call progress events before this change.

Fraud Guard is now enabled by default for all new and existing Verify services*. 

Check it on your Twilio Console by navigating to the Verify Services page and selecting your Service, where you can view Fraud Guard under the SMS tab. Read our documentation and blog to learn more about it. 

*not applicable to Verify customers using custom verification codes.

Twilio Event Streams Segment Sink is now Generally Available. Check out Segment Quickstart to learn more, and start sending Twilio events. With this Sink:

• You can send your data to one of 400+ destinations available via Segment.
• You can use Segment Profiles to link your Twilio data to an individual for an omni-channel view of your customer’s interactions, or use customer engagement tools, such as Engage, to deliver personalized, omnichannel experiences.

Twilio releases end-user usability improvements on the Phone Number detail(configuration) page.
As an example, you can navigate to this page from Console UI -> Phone Numbers -> Active Phone Numbers -> Click on the phone number.

The Console UI improvement introduces two new sections/tabs for faster navigation.

1) Properties tab: Contains details about the phone number.
Such as: Friendly Name, Number type, Location, Capabilities. It allows you to edit the friendly name from here and also release the phone number from this tab.

2) Configure tab: Enables configurations related to: routing updates, configuration updates, integrations with messaging services, add/remove emergency address.

No previous functionality has been removed and no action is required.

Geographic permissions exist to help you protect your application from fraud and abuse, or simply avoid unexpectedly high costs for voice or messaging usage. Voice Geo Permissions control which countries and subsets of phone numbers you can dial out to from your Twilio project and can be managed in the Console via the Voice Geo Permissions page or using the API.

We have updated the country name for the code +672 from “Norfolk Island” to “Australian External Territories” to be more consistent with the definition by the International Telecommunications Union (ITU): 

• Australian External Territories (country code +672)  
• Norfolk Island (external territory of Australia) (country code +672 3)

This will not impact the number ranges that can be reached by your account as we have not updated the code. With the Australian External Territories country code (+672) enabled, you will be able to reach Norfolk Island destinations (+672 3).

For more information, please see our article International Voice Dialing Geographic Permissions (Geo Permissions) and How They Work and our docs.

Geographic permissions exist to help you protect your application from fraud and abuse, or simply avoid unexpectedly high costs for voice or messaging usage. Voice Geo Permissions control which countries and subsets of phone numbers you can dial out to from your Twilio project and can be managed in the Console via the Voice Geo Permissions page or using the API.

We have updated the country name for the code +672 from “Norfolk Island” to “Australian External Territories” to be more consistent with the definition by the International Telecommunications Union (ITU): 

• Australian External Territories (country code +672)  
• Norfolk Island (external territory of Australia) (country code +672 3)

Twilio PHP SDK major version 7.x is now available. 

Behind the scenes the PHP Helper is now auto-generated via OpenAPI with this release. This enables us to rapidly add new features and enhance consistency across versions and languages.

You can find the new version on Packagist.

To learn more about the PHP Helper Library, check out our docs.

Microvisor developers need a lightweight, scalable, and reliable way to send high volumes of sensor and other device data to their cloud platforms to perform analytics that can then drive business decisions. Microvisor therefore now supports MQTT, a lightweight network protocol for machine-to-machine messaging, predominantly used in low-power IoT architectures.

The general MQTT architecture looks as follows:

Microvisor provides a set of system calls which allow your application, acting as the MQTT client, to communicate with public and private MQTT brokers to subscribe to topics, post messages to those topics, and to be notified of inbound messages. 

Your application will ask Microvisor to perform MQTT tasks on its behalf, and Microvisor will respond immediately, either accepting the command or providing a reason why it is unable to do so. It will respond asynchronously with the outcome of accepted operations. Microvisor’s notification system is used to manage this asynchronicity.

For more information, visit How to Issue MQTT Requests Under Microvisor.