The Voice Insights Call Summary provides a glimpse into call metadata, connection parameters, and quality indicators in a single cumulative view for every call placed on the Twilio platform. Call summary details are gathered and incomplete summary details are available while the call is in-progress. Completed all summaries are typically available within a few minutes after the call ends, though it may take up to 30 minutes for all the details to be aggregated and displayed.
The call summary is divided into different sections to isolate details based on the call flow, direction, and the type(s) of media edges present on the call. The sections are:
The From section contains metadata about the calling party. The To section contains metadata about the called party. Different metadata are availble depending on the direction and type of call; e.g. an Elastic SIP Trunking origination call will have different metadata compared with an iOS Voice SDK call.
|From||The caller ID of the calling party.|
|To||The called party.|
|Connection||Describes the method by which the call was delivered to/from Twilio; e.g. twilio_sdk, sip_trunk, landline, etc.|
|SIP Interface/SIP Trunking only: endpoint device type; e.g. PBX version, SIP phone model, etc.|
|SIP Call ID||SIP Interface/SIP Trunking only: SIP call ID for the call between Twilio & your SIP infrastructure.|
|Signaling IPs||The IP address for Twilio's signaling gateway. Not available for calls to/from the PSTN.|
|Media IPs||The IP address for Twilio's media gateway. Not available for calls to/from the PSTN.|
|Region||The AWS region where Twilio's signaling and media gateway reside.|
|Country||The country based on the IP address or E.164 country code.|
|Operating System||Voice SDK only: the OS reported by the application.|
|Engine||JS Voice SDK only: the engine reported by the application.|
|Browser||JS Voice SDK only: the browser reported by the application.|
|SDK Version||Voice SDK only: Twilio Voice SDK version number.|
|Selected Region||Voice SDK only: Twilio Region selected by the application; default selection is GLL.|
|Client Name||Voice SDK only: registered username for call delivery.|
|Client IP Address||Voice SDK only: IP address reported by the application.|
|Client Location||Voice SDK only: location derived from IP address reported by the application.|
|Who Hung Up||Which party ended the call as determined by the direction of the SIP BYE received at Twilio's signaling gateway.|
|Last SIP Response||Final SIP reponse code for the dialog.|
|Twilio RTP Latency||Twilio-internal RTP traversal time from ingress to egress; aka the amount of time in milliseconds that media spent in Twilio's voice infrastructure. Average and max values shown.|
|Post-dial Delay||The amount of time between the SIP INVITE and a 18x response; how long it took for the calling party to hear ringing.|
|Call State||Call status as defined here.|
|Silence Detected||Boolean. Will be
The Metrics section provides an overview of the inbound media stream quality as received at the specified edge. The condition of the outbound stream from the edge can be determined by looking at the inbound stream on the parent/child call, or other conference participants. This allows you to understand the source of the underlying issue and troubleshoot accordingly.
For example, if you are looking at an Elastic SIP trunking call and see that the Carrier edge metrics do not show packet loss or jitter, but the SIP edge shows both, that indicates the problems on the call were due to the condition of the RTP stream received from your SIP PBX and not the PSTN.
A view of both inbound and outbound stream condition is available in Console through the Metrics page and via API with Voice Insights Advanced Features.
|Codec||The RTP profile name of the codec used for the call; e.g. Opus, PCMU, etc.|
|Packet Loss Detected||
Boolean. Will be
Boolean. Will be
|Low MOS||Voice SDK only: Boolean. Will be
|High Round Trip Time||Voice SDK only: Boolean. Will be
|ICE Failure||Voice SDK only: Boolean. Will be
NOTE: In some call flows with multiple SSRCs we may indicate that an issue was detected where the values do not breach the thresholds defined above. This is due to the fact that each SSRC is analyzed individually, but the metrics displayed are the cumulative metrics of all SSRCs.