Voice Insights Call Tags
Tags
Calls can be tagged for one or more conditions that may impact the subjective experience of quality on the call. Tags are based on analysis of the call at the Twilio Gateway. The tags for carrier, client, and SIP edges are:
- silence: silence detected on the line; either due to a missing audio stream or a completely silent stream received
- high_jitter: two conditions can result in calls being tagged with high jitter, average jitter of 5ms and max jitter of 30ms, or more than 1% of packets delayed by 200ms or more
- high_packet_loss: >5% packet loss
- high_pdd: post-dial delay (time between SIP INVITE and 18x response) > p95 for this country
- high_latency: the average Twilio-internal RTP traversal time for packets received at this edge to this call SID exceeded 150ms. The call SID that received the delayed packets is the one that is tagged.
SDK Edge Tags
SDK Tags are based on analysis of the call at the SDK sensors on the local device. They report on the cumulative condition of the media streams sent to the SDK from the Twilio Gateway. The tags for SDK edge are:
- high_latency: Round Trip Time (RTT) > 400 ms
- low_mos: Mean Opinion Score (MOS) < 3.5
- high_jitter: average jitter of 5ms and max jitter of 30ms
- high_packet_loss: >5% packet loss
- ice_failure: The ICE candidate has checked all candidates pairs against one another and has failed to find compatible matches for all components of the connection.
Call Tagging FAQs
- Why is Voice Insights focused on network metrics instead of audio quality?
- How does Twilio's silence detection work?
- Why is post-dial delay tagging based on a percentile and not a numeric threshold?
- Did Twilio introduce jitter/packet loss on this call?
- The metrics are terrible but the call sounded fine, what gives?
- What does high latency mean?
- How is Twilio internal RTP traversal time calculated?
- What contributes to high RTP traversal time?
- What's the difference between RTT and latency?
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.