Call Leg Details window field descriptions

Last Updated : Dec 07, 2012 |
Prolog information
Metadata
Keywords:
Field
Description
Call Leg
The number of the call leg.
Contact ID
The unique identifier for the call assigned by the Media Server.
If the call uses an H.323 connection, this field is in the format MPPName-Port-SessionID, where:
  • MPPName is the name of the MPP server.
  • Port is the Avaya Experience Portal port number.
  • SessionID is the session ID assigned to the call.
If the call uses a SIP connection, this field is in the format MPPName-SIPPortGroup-SIPChannel-SessionID, where:
  • MPPName is the name of the MPP server.
  • SIPPortGroup is the SIP port group number.
  • SIPChannel is the SIP channel number.
  • SessionID is the session ID assigned to the call.
Session ID
The unique identifier for the session assigned by the Media Server.
Port
The number of the port used for the call.
Start Date/Time
The day and time that the call leg started.
Contact Type
The options are:
  • Inbound
  • Outbound
Duration
The length of the call in seconds.
Application Name
The name of the application that handled the call.
Originating Number
The calling party number or Automatic Number Identification (ANI).
Destination Numbers
The destination number or numbers to which this call was routed.
Reason Code
The options are:
  • No Resource
  • Busy
  • No Answer
  • Network Busy
  • No Route
  • Network Disconnect
  • Unknown
  • Near End Disconnect
  • Far End Disconnect
  • Transferred
  • Internal Error
End Type
The options are:
  • Near End Disconnect: The application completed and terminated the contact.
  • Transfer: The application transferred the contact.
  • Far End Disconnect: The calling party terminated the contact by hanging up.
  • Interrupted: The contact was terminated because the grace period expired for an Media Server shutdown request from the EPM.
  • Not Routed: The contact was not routed because no applications exist for this DNIS.
  • No Resource: The contact was not handled because no speech resources could be allocated.
  • Session Manager Error: The session encountered a problem and could not continue.
  • Redirected: The contact was redirected. For example, SIP Refer.
  • Rejected: The contact was rejected. For example, set when a contact is rejected through a CCXML app, or if the contact is rejected when attempting to connect the contact because the contact is disconnected before it is answered.
  • Merged: The contact was merged with another contact. For example, SIP Refer w/replace.
End Details
Additional information about why the call leg ended, including the event that triggered the end of the call leg.
Media Server
The name of the Media server that handled the call.
Switch Protocol
The options are:
  • H.323
  • SIP
  • SIPS
Time Until Call Connected
The number of milliseconds until the call was connected.
First Prompt Latency
The number of milliseconds after Avaya Experience Portal received the call before the initial prompt began playing.
Note:
The First Prompt Latency value includes both the time it took Avaya Experience Portal to answer the phone as well as the time it took the first application page to load and request that a prompt be played.
Round Trip Between Server and Far End
The delay, expressed in milliseconds, between receiving the last SR packet from source SSRC_n and sending a reception report block.
Note:
If no SR packet has been received yet from SSRC_n, this field is set to zero.
Far End Reported Jitter
The Jitter reported from the far end of the RTP stream.
Number of Packets Media Server Sent
The total number of RTP data packets transmitted by the sender.
Number of Packets Far End Lost
The total RTP data packets lost as reported by the far end of the RTP stream.
Media Server
An estimate of the statistical variance of the RTP data packet inter-arrival time, measured by comparing timestamp units and expressed as an unsigned integer. Jitter provides a measure of transient network congestion, where lower numbers represent better audio quality.
Number of Packets Server Received
The total number of RTP data packets received from the source.
Number of Packets Server Lost
The total number of RTP data packets from source that have been lost since the beginning of reception.
This is the number of packets expected minus the number of packets actually received, where the number of packets received includes any which are late, or duplicates.
Related links
SMS Processors tab on SMS page field descriptions