Calls that Microsoft devices process can consist of simultaneous audio and video data streams with distinct call legs:
UC Monitor uses an identifying session ID to correlate call data for such calls. The collector assigns the ID when it detects similarities in endpoint identities and timestamps among audio and video data streams.
When session information is available for a call, the Session ID in the Calls Overview table provides a link to correlated session details.
When the collector identifies data from call legs as being from the same call, a separate data view shows statistics for each correlated data stream. A shared session ID identifies the correlated streams. The following table summarizes the data in the Session Details table:
The identifier for a call. UC Monitor automatically assigns the ID.
The code that the call server returns when a call fails during the setup phase. The code indicates the type of failure. For more information, see the list of call termination cause codes on the Cisco website.
The Location of the destination endpoint, or the gateway device that forwarded the call to the PSTN.
(Audio streams only) The MOS of the data stream at the destination endpoint.
The Mean Opinion Score (MOS) is an industry standard method for gauging call quality. MOS is an estimation of how impairments to a voice signal affect listener perception of call quality.
The directory number or SIP URI of the destination endpoint.
The length of the call.
The type of data in the call, either audio or video, or both.
The Location of the origination endpoint, or the gateway device that forwarded the call from the PSTN.
(Audio streams only) The MOS of the data stream at the origination endpoint.
The directory number or SIP URI of the origination endpoint.
The date and time the call began.
The Session Information table provides the following information.
The session identifier that UC Monitor assigns to identify call legs for audio and video data streams that are part of the same call.
The directory number or SIP URI of the origination endpoint.
The phone number or SIP URI that was dialed.
The directory number or SIP URI of the destination endpoint.
The date and time the call began.
The length of the call.
The type of data in the call, either audio or video, or both.
These tables provide detailed information about the origination and destination endpoints. The following information is provided, when available.
The host name of the endpoint, or the name that is associated with the device.
The firmware version and build number of the software on the endpoint.
The SIP URI of the logged-in user who is associated with the endpoint.
This table provides information to identify conference calls, such as the Conference URI. The Conferencing Server generates the URI and usually includes the URI of the user who established the conference call.
When call data is available from call legs in the same call, a separate data view shows statistics for each correlated data stream. A shared session ID identifies the correlated streams.
The Session Details table provides the following information:
The identifier for a call. UC Monitor automatically assigns the ID.
The code that the call server returns when a call fails during the setup phase. The code indicates the type of failure. For more information, see the list of call termination cause codes on the Cisco website.
The Location of the destination endpoint, or the gateway device that forwarded the call to the PSTN.
(Audio streams only) The MOS of the data stream, as perceived at the destination endpoint.
The directory number or SIP URI of the destination endpoint.
The length of the call.
The type of data in the call, either audio or video, or both.
The Location of the origination endpoint, or the gateway device that forwarded the call from the PSTN.
(Audio streams only) The MOS of the data stream, as perceived at the origination endpoint.
The directory number or SIP URI of the origination endpoint.
The date and time the call began.
|
Copyright © 2012 CA.
All rights reserved.
|
|