Voice Insights shows why carriers block your calls
Voice Insights now displays the FCC-required reason header when carriers block calls using analytics, showing which network blocked the call and how to contact them for redress. The reason header is available in Call Summary, Console, Voice Insights REST API, and Event Streams.
Voice Insights now tells you why a carrier blocked your call and how to reach that carrier for redress.
The FCC requires carriers that block calls using analytics to return the reason header to the caller. It names the network that blocked the call and tells you how to contact them: a URL, a phone number, or an email address. Until now a blocked call showed you only a 603 response. Now you can see which network blocked it and petition them directly.
The reason header appears alongside Last SIP Response in the Call Summary, in Twilio Console, the Voice Insights REST API, and Event Streams.
If you are seeing a high volume of 603 responses, confirm your traffic is signed with STIR/SHAKEN and registered with Twilio Voice Integrity before you start filing redress requests.
Learn more in our Call Summary documentation.
Source: original entry ↗
More from Twilio
Follow Twilio to get its new changes in your feed and email digest.
Voice Insights now tags HD audio calls
Voice Insights now automatically tags calls as HD Audio when they use AMR-WB or Opus codecs, helping you confirm endpoint configuration and correlate HD audio usage with transcription accuracy and customer satisfaction. The system also tags calls as Downsampled when HD audio is converted to narrowband, visible in Console, REST API, and Event Streams.
Live support coverage across Twilio platform and Segment
Paid support customers can now reach Twilio through live chat for help with Segment and all Twilio platform applications and products, starting October 5, 2026.
TaskRouter and Studio Public Beta in Ireland Region
TaskRouter and Studio are now available in public beta in Twilio's Ireland (IE1) region, providing EU data residency and control over where contact center routing and workflow automation data is stored.