Twilio Changelog

On May 3rd, 2022 responses to API requests for CSV representation of Incoming Phone Number and Outgoing Caller ID resources for both list and instance will change; specifically the order of the columns may be different.

The order of the columns in the CSV is not defined and may change when new fields are added to the API response. Your application design should be resilient to changes in the order of the columns in the CSV response.

See our docs for more information about how to leverage CSVs with Twilio.

When Twilio receives termination traffic from your communications infrastructure to the PSTN, your SIP message can sometimes include SIP Diversion headers if the call was previously forwarded. Twilio will forward SIP Diversion headers it receives to the carriers.

To combat any malicious addition of Diversion headers, Twilio will now check all Diversion headers it receives that contain the Twilio domain. Twilio will verify that the phone number included in the header matches one associated with your Twilio account (either a Twilio number owned by the account or a verified Caller ID). If the header fails this check, Twilio will remove the header.

See the docs for more information.

As previously communicated, we are continuing to roll out Enhanced Programmable SIP Features to all accounts. This could represent a behavior change for some call flows, including calls that do not use Programmable SIP. For more information, see our docs page detailing the changes in Programmable Voice behavior.

Every conference on Twilio is now being analyzed and aggregated by Conference Insights to provide visibility into participant behavior and offer prescriptive recommendations for resolving common quality and configuration issues.

Conference and Participant Summaries provide multiple views into conference metadata which allow users to see conference parameters, investigate participant event timelines, and understand detected quality issues. Both summary records return useful metadata about the conference and its performance.

Conference and Participant Summaries are available via Console, API and Event Streams.

Conference and Participant Summaries are included with all conferences at no additional cost via Console. Voice Insights Advanced Features are required for API and Event Stream access.

For more information see docs.

Twilio’s home region in Australia is now generally available, with Twilio Voice being the first available product. This gives you control over where Voice data is ingested, processed, and stored, enabling you to keep personal data at rest within the region of your choice. It also offers data processing that is closer to your applications, thus reducing latency and improving application performance for highly interactive, real time interactions.

To learn more on how to get started with Twilio Voice in Australia, head over to our developer docs.

Click here for documentation about Twilio Regions.

Voice can now be used on Twilio Frontline 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 Voice in Twilio Frontline and how to build on Twilio for HIPAA compliance.

The new Usage by SIM tab added to Super SIM Insights displays a per-SIM breakdown of your Super SIM data usage. Each row in the table shows how much data a SIM downloaded or uploaded and the total amount. Because the rows are sorted by total amount, you can easily identify which of your Super SIMs have exchanged the most data over a specified time period. View the top entries in the table to quickly single out any outliers. Filter the results by Fleet, Country, or Network to further slice-and-dice your usage.

In addition, the rightmost column contains spending information for each record. This data allows you to better understand your per-device spend on Super SIM usage. You can draw various insights, such as which of your SIMs have incurred the highest costs. It is particularly helpful to decouple data consumption and monetary spend into separate entries because different networks charge different rates. As such, although one SIM might be consuming less data than the other, it could still have incurred higher costs if it were operating on a more expensive network.

Access Usage Insights by SIM in Console via Monitor > Insights > Super SIM and select the “Usage by SIM” tab.

Twilio sells Call per second (CPS) which allows customers to increase the rate at which Twilio will execute new calls created via the Calls API. CPS is sold and billed in us1 and the CPS value is replicated to other Regions (e.g. au1/ie1) at no additional cost to allow customers to operate across all timezones. The replication of the CPS value also allows services to fallback to a different Region in the event that a Region becomes unavailable. Twilio has updated the Acceptable Use Policy regarding concurrent utilization of CPS across Regions; specifically persistent maximum utilization of CPS in multiple Regions concurrently is prohibited. For more information, see the Programmable Voice: No Concurrent Voice Calls per Second in Multiple Home Regions section of the AUP.

Twilio has completed validation of the integration between Flex and Lionbridge Language Cloud real-time language translation solution. Using a database of over 110 languages, this integration enables your agents to send SMS, Chat or WhatsApp messages in their native languages, and have customers read them and send return messages in their native languages.

To learn more about Lionbridge capabilities and how to enable it for your application, visit our integration documentation.

As previously communicated, the 2008 version of our Programmable Voice API has reached end-of-life and requests made to 2008 endpoints or resources will not receive responses. We have discovered a small subset of requests to 2008 resources that were not entirely shut down during the previously communicated end-of-life timeframe. Starting May 2, 2022 all requests to any 2008 Voice endpoint will receive a 404 response from Twilio.