Twilio Changelog

Twilio Alarms, a near real-time monitoring and alerting experience for Twilio customers, is now Generally Available (GA).

The first full scale implementation of Alarms supports Error Logs. This enables you to proactively monitor error logs at the minute level and receive a notification whenever there is a spike in errors, warnings, or informational events of interest, across your Twilio applications.

You can learn how to create and use Alarms with this Twilio guide or watch this demo.

We are sunsetting our old Alert Triggers product. If you have created Alerts on our old platform, they have already been migrated onto this new Alarms platform. You will be able to access these in the Manage Alarms page.

Twilio SendGrid has always grouped your email statistics by mailbox provider in our console. This allows you to easily see how your email is performing at Yahoo compared to Microsoft, for example. Our system also helps clean up this data by grouping mailbox providers together. On November 16, 2022, Twilio SendGrid will release an update to our current Mailbox Provider groupings that will make this part of our application even more powerful. Specifically, we will be adding more mailbox providers to our list, increasing from 50 to almost 250. This will result in far less data being lumped into the “Other” bucket when you review your mailbox provider statistics. Check out our blog post to learn more about the change and see examples for more information.

In 2H 2023 Twilio will be updating the media IPs and port ranges for SIP and Voice SDK calls in all regions. We will be moving from a per-region IP range allocation to a single global range; 168.86.128.0/18. Additionally, we will be expanding the media port range from 10000-20000, to 10000-60000.

We are making this change to provide flexibility, reliability, and scalability. There is no action required at this time, and we will provide a more precise timeline approximately six months before the change. At that time you will need to update your network infrastructure to ensure that you have whitelisted the full IP and port ranges. Failure to do so will result in one-way audio and dropped calls.

We are launching a new attribute `requireMatchingInputs` within <Prompt> verb which is used in conjunction with the `for` attribute to prompt the caller to enter a specific payment detail twice. The first <Prompt> verb prompts the user to enter a given payment information.

The second <Prompt> which contains `requireMatchingInputs` set to `true` will give the caller a different prompt asking the caller to enter the information again. Once the customer enters the information, both inputs are validated against each other and if they match, they will be sent to the downstream payment gateway for processing.

This attribute works for ACH-debit <pay> transactions of type purchase/tokenization that require users to enter a bank account number or routing number. This enhancement was introduced to catch any user input errors upfront, reducing the error rates reported by payment gateways to meet the error thresholds defined by NACHA.

For more information about this feature, check out the API Docs.

Super SIM Usage Insights now lets you export a CSV file containing your SIMs’ usage record data. With just the click on a button, you can download an extract of the table currently being displayed in the browser. Having this data in the form of a CSV allows you the flexibility to perform subsequent analysis using any application of your choice – a database, spreadsheet, or data visualization tool.

All of the Usage Insights tabs support the CSV Download feature:

• Usage by Time
• Usage by SIM
• Usage by Fleet
• Usage by Country
• Usage by Network

Access CSV Download for Super SIM Usage Insights in Console by navigating to Monitor > Insights > Super SIM and clicking on the button labeled “Export CSV”.

We are excited to announce that the Conversations API is now generally available in Ireland (chat only). The availability of Conversations API in Ireland gives you control over where you data is processed and stored. It also offers data processing that is closer to your applications, therefore reducing latency and improving performance.

Click here to learn more on how to get started with Conversations API in Ireland.

Twilio Microvisor is now in Public Beta. Microvisor provides managed connectivity as well as managed security for the lifetime of IoT devices. With Microvisor, you can continuously debug and improve a connected hardware product after it has been mass-manufactured and deployed to the field – by offering unbrickable over-the-air firmware updates and secure remote line-by-line debugging live on deployed devices. Microvisor leverages Arm TrustZone to achieve security and failsafe connectivity through hardware-level separation of communications and application and a hypervisor architecture.

If a SIM exceeds its data limit, it won’t be able to use any more data until the data limit resets at the end of its current billing period. Today, the Super SIM details page in Console now allows you to easily identify how close a particular SIM is to reaching its monthly data limit. There is a new section on the page which shows:

• the SIM’s current billing period start and end timestamps (1 month duration)
• its data consumption within this timeframe
• its monthly data limit, as defined by its Fleet

Use the data limit usage information to determine whether you need to take action such as:

• Move some SIMs to another Fleet with a higher data limit
• Update the data limit on the Fleet your SIMs are assigned to

When requesting a Super SIM eSIM Profile from the /ESimProfile API, you can now request that the eSIM profile be reserved with a matching ID by setting the new generate_matching_id request parameter to true. When you reserve a profile this way, you don’t need to provide the EID of the eSIM that will use the profile, which depending on your use case may be very difficult to know ahead of time or obtain.

When you want to download and install the eSIM profile, you will need to provide the matching ID to your device along with the SM-DP+ URL, both of which can be read from the ESimProfile when your reserved profile is available. The combined SM-DP+ URL and matching ID is often referred to as an “activation code” and often provided to end users via a QR code that they scan with their device during the workflow to add a new eSIM profile.

Refer to the docs to learn more about eSIM Profiles and different eSIM download methods.

This solution enables organizations using Avaya Aura Contact Center solutions that include the Avaya Enterprise Session Border Controller (ESBC) to connect to the PSTN via Twilio Elastic SIP Trunking. You can learn more about this solution by referencing the blueprint guide here: Twilio Elastic SIP Trunking Solution Blueprints.