Cisco Prime Collaboration Assurance Guide, 9.5
Monitoring Sessions
Downloads: This chapterpdf (PDF - 808.0KB) The complete bookPDF (PDF - 4.16MB) | Feedback

Table Of Contents

Monitoring Sessions

Cisco Unified CM

Cisco VCS

Working with the Session Monitoring Dashboard

Realtime Visibility of an Endpoint

360° Session View

Session Topology

Endpoint Statistics


Monitoring Sessions


Cisco Prime Collaboration tracks the lifecycle of video collaboration sessions in your network. It correlates session data received from various sources and provides end-to-end details on the session.

Prime Collaboration receives session events from call and session control components, such as Cisco Unified CM and Cisco TelePresence Video Communication Server (VCS). It also retrieves session details from applications, such as management applications, call and session control components, conferencing components, and endpoints.

The session data retrieved from the video collaboration applications includes both scheduled and unscheduled sessions. Prime Collaboration differentiates sessions in the following ways:

Ad hoc—An end-user dials the extension of the TelePresence system at the other end. There is no scheduling involved.

Scheduled—Scheduled in advance of the session through the company's groupware application, such as Microsoft Exchange, Outlook, and so on. You could have scheduled the session directly, using Cisco TelePresence Management Suite (TMS) too.

Static—Preconfigured TelePresence session available all the time. Each static meeting has its own associated meeting number. On some applications, such as Cisco TelePresence MSE, Multipoint Control Unit (MCU), Cisco TelePresence Server (TS), these meetings are called permanent meetings.

Following are the meeting types supported by CTX system in a Managed Service Provider (MSP) environment:

Meet-Me—A Meet-Me meeting is scheduled using CTX for CTS and other third party endpoints. A Meet-Me meeting typically includes a Media Resource such as a CTMS/MSE depending upon the type of endpoints.


Note In a Meet-Me meeting, a conference resource (with no actual values) is displayed in the Session Topology until the meeting status becomes InProgress; The conference device is then replaced with devices such as MCU, TPS, or CTMS, and the active endpoints are connected through Session Border Controller (SBC).


Rendezvous meeting—Preconfigured TelePresence session available all the time. Each Rendezvous meeting has its own associated meeting number. In this case the media resource is allocated when the first participant of the meeting joins and the media resource is de-allocated on the exit of the last participant.


Note Adhoc, Scheduled and Static sessions are not displayed in the MSP mode. Also, Remote Meeting and Direct Dial meeting types are not supported by Prime Collaboration.


Prime Collaboration classifies the sessions structure as follows:

Point-to-point—Session between two endpoints.

Multipoint—Session with more than two endpoints. Between endpoints, you may have either
Cisco TelePresence Multipoint Switch or MCU.
In MSP mode, all sessions are multipoint and therefore session structure column is not displayed in the Session table.

Multisite—Session with more than two endpoints, without MCU. The endpoints are connected directly. Any endpoint can participate in a multisite call with the center endpoint being multisite capable. The center endpoint acts as a conferencing device (like MCU). This type of session structure is supported for multisite capable endpoints such as
Cisco Codec C and EX series TelePresence Systems, Cisco TelePresence MX series, and Cisco Profile series with a multisite license.

The sessions status can be:

In-progress

Scheduled

Completed

No Show, a scheduled session without any participants joining the session until the end time. The scheduled sessions are moved to No show only after the scheduled end time and after Prime Collaboration is synchronized with either Cisco TelePresence Manager (CTS-Manager) or Cisco TMS, after the scheduled end time.

If an endpoint did not join an In-Progress session, a no-show icon is displayed on the endpoint. This status is shown even after the session moves to completed state.

If an endpoint joins a session, but later disconnects from the call before the session is over, a disconnect icon is visible on this endpoint in the session topology. Disconnected could mean that there was a problem, or the caller had to leave the session early.

Prime Collaboration periodically polls the following video service infrastructure devices to get information on the sessions:

Management devices (CTS-Manager and Cisco TMS)—Prime Collaboration gets information on the scheduled point-to-point and multipoint sessions. For Cisco TMS, if an unscheduled endpoint is added when the session is in progress, Prime Collaboration shows the session details for the newly added endpoint.


Note In the MSP mode, Prime Collaboration polls only CTX for session information. Any change in CTX MeetMe sessions are displayed in Prime Collaboration.


Prime Collaboration collects scheduled sessions data for five days (for the past one day, the current day, and for three days ahead).


Note If you are using Cisco TMS 13.0 or 13.1 you must configure the Booking API feature. For Cisco TMS 13.2 and above, you need not configure the Booking API feature.


Multipoint Switches—Prime Collaboration gets information on the multipoint sessions. It also identifies and supports cascading of multipoint sessions.

Multipoint Control Units (MCU and Cisco TS)—Sessions that are scheduled using these systems are always listed as ad hoc sessions in Prime Collaboration. These types of sessions are listed in the Session Monitoring page only after the session is started. Prime Collaboration polls these systems after receiving an event from the endpoints.

Prime Collaboration polls MCU and Cisco TS whenever these systems receive a call. Prime Collaboration polls MCUs that are not managed by Cisco TelePresence Conductor directly.

For sessions that are hosted by MCUs controlled by Cisco TelePresence Conductor, Prime Collaboration polls only the Cisco TelePresence Conductor.

Prime Collaboration does not support cascading of MCU sessions. Only Cisco TelePresence Conductor controlled MCU cascading is supported.

Call and Session Controls (Cisco Unified CM and Cisco VCS)—Prime Collaboration gets information on the participants using call processors. It collects details, such as when a user joins the session or disconnects from it. Prime Collaboration polls call and session controllers periodically.

Prime Collaboration receives Connect/Disconnect events in realtime from Cisco Unified CM and Cisco VCS. Whenever Connect/Disconnect events are missed, as a backup mechanism, Prime Collaboration polls Cisco Unified CM and Cisco VCS periodically for all In Progress calls. Hence, they are synchronized.

In MSP mode, Prime Collaboration gets information on the participants using CTX. It collects details, such as, when a user joins the session or disconnects from it. Prime Collaboration polls CTX periodically.

Prime Collaboration receives Connect/Disconnect events in realtime from CTX. Whenever Connect/Disconnect events are missed, as a backup mechanism, Prime Collaboration polls CTX periodically for all In Progress calls. Hence, they are synchronized.

Cisco Unified CM

All endpoints need to be added as JTAPI controlled devices in Cisco Unified CM. Otherwise, call detection for the endpoints does not happen in Prime Collaboration. The configured JTAPI user must have permission to access all endpoints that are managed in Prime Collaboration.

Prime Collaboration listens to the JTAPI events from the Cisco Unified CM. The endpoints are polled once the call is In Progress. Prime Collaboration depends on the JTAPI event to move the session to the completed status.

Prime Collaboration manages multiple Cisco Unified CM clusters. It monitors sessions within a cluster and among clusters (intracluster and intercluster sessions). You must configure unique cluster IDs.

Prime Collaboration must manage the cluster publisher to monitor a cluster. The JTAPI must be configured on the cluster publisher and the computer telephony integration (CTI) service must be running on all subscribers.


Note In the MSP mode, Prime Collaboration listens to JTAPI events from the Cisco Unified CM only for endpoint registration.


Cisco VCS

Prime Collaboration listens to HTTP feedback events from the Cisco VCS. The endpoints are polled once the call is In Progress. Prime Collaboration depends on the HTTP feedback event to move the session to the completed status.

Prime Collaboration manages multiple Cisco VCS clusters. It monitors sessions within a cluster and among clusters (intracluster and intercluster sessions). You must configure unique cluster names.

Prime Collaboration identifies and supports Cisco VCS Expressway traversal calls. For these calls, the media signal flows through Cisco VCS Control and Cisco VCS Expressway and the call details are displayed in the session topology.

See the Cisco TelePresence Video Communication Server Control online help for details on traversal calls.

If there is a call outside the enterprise firewall, Cisco VCS Expressway is used. This device is configured to the Cisco VCS Control device. The Cisco VCS Control and Cisco VCS Expressway are displayed in the session topology. However, the endpoints that are registered to the Cisco VCS Expressway are displayed as Unknown endpoints.


NotePrime Collaboration ignores Cisco VCS Expressway Connect/Disconnect events.

In the MSP mode, Prime Collaboration listens to feedback from VCS for endpoint registration.


Figure 16-1 shows the end-to-end scheduled session workflow.

Figure 16-1 Scheduled Session Workflow

The following are a few scenarios where Prime Collaboration might not contain up-to-date details on sessions or might display different session structure data:

Prime Collaboration might show a scheduled session (point-to-point, multipoint, or multisite) as an ad hoc session if the session gets scheduled and was In Progress after the last CTS-Manager or Cisco TMS poll and before the next scheduled/on demand polling of the CTS-Manager or Cisco TMS takes place.

For scheduled multipoint sessions, if Prime Collaboration is not synchronized with the management applications, the session is shown as an ad hoc session and it collects information from the participating Cisco TelePresence Multipoint Switch or Cisco MCU after Prime Collaboration receives a Connect event.

If a conferencing system has moved either to the Unmanaged or Unknown state from the Managed state, then the multipoint sessions are displayed as multiple point-to-point sessions.

Cisco TMS and Cisco MCU displays the session status as Active immediately after the scheduled time is passed. However, Prime Collaboration does not change the session status to In Progress until an endpoint joins the session.

Prime Collaboration displays sessions that include unmanaged endpoints. However:

For point-to-point sessions, one of the endpoints must be managed in Prime Collaboration.

For multisite sessions, the endpoints that conference the other endpoints must be managed in Prime Collaboration.

For multipoint sessions, the conferencing devices must be managed in Prime Collaboration.

If you have used Cisco TMS to reserve only TelePresence rooms, then Prime Collaboration does not display these sessions. (In Cisco TMS, this conference call type is identified as Reservation Only.)

If Cisco VCS expressway is in the Inaccessible state, Prime Collaboration can still monitor the sessions. However, the endpoints will be displayed as Unknown endpoints.

The session monitoring feature does not support endpoints, which are configured with multiple lines in Cisco Unified CM. However, you can manage these endpoints in the Prime Collaboration inventory database.


Note The session monitoring feature is supported only on Cisco Unified CM 8.5, 8.6, and 9.0.


Only the Peripherals and Session details are displayed on the Session Monitoring page, if there is a session between a TelePresence and an audio endpoint (such as a WebEx call). This session is identified as an Inlocalconference session.

Table 16-1 describes the various session scenarios that are monitored in Prime Collaboration:

Table 16-1 Session Scenarios 

Session Classification
Session Type
Session Structure
Session Topology Elements

Cisco Unified CM intracluster and intercluster sessions

Ad hoc
Scheduled

Point-to-point

Cisco TelePresence System 500, 1000, 3000, TX9000 series.

Cisco Unified CM intracluster and intercluster sessions

Ad hoc
Scheduled
Static

Multipoint

Cisco TelePresence System 500, 1000, 3000, TX9000 series, and CTMS.

Cisco VCS intracluster and intercluster sessions

Ad hoc
Scheduled

Point-to-point

Cisco C series, Ex series, Cisco MX series, Cisco MXP series, Cisco IP Video Phone E20, Cisco Cius, and Cisco Jabber.

If a call is identified as a traversal call, Cisco VCS Control or Cisco VCS Expressway is displayed in the session topology.

Cisco VCS intracluster and intercluster sessions (with MCU)

Ad hoc
Scheduled
Permanent (displayed as static)

Multipoint

Cisco C series, Ex series, Cisco MCU, Cisco MSE1 , or Cisco TelePresence Server.

If a call is identified as a traversal call, Cisco VCS Control or Cisco VCS Expressway is displayed in the session topology.

Cisco VCS intracluster and intercluster sessions (without MCU)

Ad hoc
Scheduled

Multisite

Cisco C series, Ex series, Cisco MX, Cisco MXP series, Cisco IP Video Phone E20.

If a call is identified as a traversal call, Cisco VCS Control or Cisco VCS Expressway is displayed in the session topology.

Sessions between Cisco Unified CM and Cisco VCS clusters2

Ad hoc

Point-to-point
Multipoint

Cisco C series, Ex series, Cisco MX series, Cisco MXP series, Cisco IP Video Phone E20

Cisco TelePresence System 500, 1000, 3000, and TX9000 series

Cisco TelePresence Server

Cisco Unified CM (8.6(1), 8.6(2), and 9.0) intracluster sessions3

Ad hoc

Point-to-point

Cisco C series, Ex series, Cisco MX series

Cisco TelePresence System 500, 1000, 3000, and TX9000 series

Cisco Unified CM (8.6(1), 8.6(2), and 9.0) intracluster sessions

Ad hoc
Scheduled

Note Scheduler must be CTS-Manager 1.7, 1.8, or 1.9.

Multipoint

Cisco C series, Ex series, Cisco MX series, Cisco IP Video Phone E20

Cisco TelePresence System 500, 1000, 3000, and TX9000 series

CTMS 1.8 or Cisco TelePresence Server

Sessions outside the enterprise firewall - Cisco VCS Expressway

Ad hoc
Permanent (displayed as static)

Point-to-point
Multipoint
Multisite

Cisco C series, Ex series, Cisco MX series, Cisco MXP series, Cisco IP Video Phone E20

Cisco MCU or Cisco TelePresence Server

Cisco VCS Control and Cisco VCS Expressway

1 The codian software must be running on Cisco MSE.

2 This scenario is supported on CTS 1.7.4, and TC 4.1, 4.2, and 5.0. The troubleshooting workflow is supported on TC 4.2, 5.0, and above.

3 This scenario is supported on CTS 1.7.4 and TC 5.0 and above.


3 Cisco Cius and Cisco Jabber devices support only ad hoc sessions.



Working with the Session Monitoring Dashboard

To access the session monitoring dashboard, choose Operate > Diagnose > Session Diagnostics.

The Session Monitoring dashboard provides details on a session and the endpoints that are involved in that session. In addition to monitoring the session, you can troubleshoot and identify faults in the network segment.

You can monitor sessions based on device type, by selecting the desired group from the Group drop-down filter. You can further filter based on the session type using the Show filter on the Video Collaboration Sessions pane.

Figure 16-2 shows the Session Monitoring Dashboard.

Figure 16-2 Session Monitoring Dashboard

1

Predefined Group filter drop-down list. Also includes a launch point for a calendar. By default, the All Video Collaboration Sessions table contains information for the current date (24 hours).

You can view sessions for the past 30 days and the next 3 days.

2

Quick summary pane for alarms and sessions.

3

Predefined filters drop-down list.

Also, includes Refresh icon and Table setting icon. Using the Table setting icon, you can customize the table column and fix any row to either the top or bottom.

4

Video Collaboration Sessions

5

Count for total number of in-progress sessions (normal and alarmed) and in-progress alarmed sessions for the specified date.

6

Session topology pane.

7

Session statistics pane.

8

Endpoint statistics pane. This pane contains details on peripherals, system, and sessions.

9

Launch point for the import session task. Rest your mouse pointer over the Import Sessions button to see details on when the data was last imported into the Prime Collaboration database.
NOTE: In MSP mode, Import sessions will fetch data from CTX system only.

   

The summary pane displays the session details for the current day (00:00:00 hours to 23:59:00 hours). You can view the icon-based summary of the data available in the Video Collaboration Sessions table.

The Video Collaboration Sessions table displays the details of in-progress sessions for the current date (00:00:00 hours to 23:59:59 hours). The latest session detail is listed at top of the table.

If you want to view details for the previous or the next day, you can choose the date, using the calendar. You can choose any of the filters from the Show drop-down list to view other session details.

Prime Collaboration persists session details for the last 30 days and the next 3 days from the current date.

Topology View with restricted endpoint

If you do not have access to certain customers, then you can view such customer endpoints with quick view only displaying customer name, endpoint name and endpoint type.

Realtime Visibility of an Endpoint

The visibility feature for a managed endpoint determines to what level Prime Collaboration monitors the operations of the endpoint. Only endpoints in the Managed state can be edited for visibility. If you edit the visibility settings for endpoints whose visibility level exceeds the maximum visibility, the changes will not be updated. Visibility setting controls the polling of endpoints in addition to session monitoring. Polling is done only for devices configured for real time full visibility.

Prime Collaboration supports the following types of visibility:

Full Visibility—Call detection using JTAPI/ HTTP feedback and realtime monitoring information such as session statistics, session information, and troubleshooting is supported.

Limited Visibility—Automatic call detection using JTAPI/ HTTP feedback takes place, but realtime monitoring information such as session statistics, session information, and troubleshooting is not supported. Endpoints with limited visibility are indicated with a half-dimmed icon in the Session Topology.

Off—Neither call detection using JTAPI/ HTTP feedback nor realtime monitoring information are supported. These endpoints are displayed in the Session Monitoring page with a fully dimmed
icon .

The following table lists the default and maximum visibility details for the endpoints:

Endpoint Type
Default Visibility
Maximum Visibility

CTS 500, 1000, and 3000 series

Cisco C Series Codec

Cisco TelePresence SX20

Cisco TelePresence MXP series

Full

Full

Cisco Jabber

Polycom

Limited

Limited

Cisco Cius

Off

Limited

Cisco IP Phones (89xx, 99xx)

Off

Limited

Cisco IP Video Phone E20

Off

Full


There is full visibility (default and maximum) for high-end multi-codec, high-end single-codec and midrange endpoints (except Polycom). There is no visibility for mass endpoints by default. The maximum visibility for mass endpoints is full. See the previous table for exclusions.

For a point-to-point ad hoc session, if visibility is Off for one endpoint and Limited or Full for the other, the endpoint with Off visibility is shown with a fully dimmed icon in the session topology.

For a Multipoint session, an endpoint with Off visibility is not displayed in the session topology.

For scheduled point-to-point or multipoint sessions, endpoints with Off visibility are shown with a fully dimmed icon in the session topology.

To view the visibility of an endpoint, choose Operate > Device Work Center and then view the Visibility column in the inventory table for the corresponding endpoint.


Note If you are not able to view this column, click the Settings button, click Columns, and then click Visibility in the list that appears.


To change the visibility of an endpoint:


Step 1 Choose Operate > Device Work Center.

Step 2 From the Current Inventory table, select an endpoint, and then click Edit. You will see the current visibility of the endpoint.

Step 3 Make your changes and click OK.



Note If you select more than one endpoint, you will not be able to view the current visibility of the endpoints.


Any changes to the visibility settings are implemented from the next session onward.

The visibility feature is applied on the Session Monitoring page only. That is, even if you have set visibility to either Limited or Off, the endpoint is listed in the Endpoint Monitoring and Device Inventory pages.

360° Session View

The 360° Session View provides a complete view of pertinent data about endpoint, infrastructure devices, alarms, and call records. It also enables you to cross launch other Prime Collaboration features. To see the 360° Session View for a session, rest your mouse pointer over the Session Subject column in the Video Collaboration Sessions table and click on the 360° Session View icon.

The 360° Session View contains the following tabs:

Alarms—Displays the alarm severity, the source that triggered the alarm, the description of the generated alarm, and the time stamp.

Endpoints—Displays the endpoint name, IP address, physical location, session duration, and device model.

Infrastructure—Displays the details of the infrastructure devices in use. You can launch the Infrastructure Devices login page using the IP address link. You can also launch the Device Inventory page to view the inventory details of the device by clicking the Device Name.

The following table lists the actions that you can perform in the 360° Session View:

Table 16-2 Actions Performed in 360o Session View 

Icon
Description

Launches the Troubleshooting page for the selected session, where you can select the direction for troubleshooting. This link is enabled for in-progress sessions.

Enables you to add a session to the watch list. This is enabled for scheduled and in-progress sessions.

If you have added an in-progress session to the watch list, the troubleshooting workflow starts immediately between endpoints, for a point-to-point session and between an endpoint and a multipoint switch, for a multipoint session.

If you have added a scheduled session to the watch list, the troubleshooting workflow starts after the session starts.

If you have scheduled a recurring session, you must add each instance of the recurring session to the watch list. For example, if you have scheduled a recurring session for every day over 5 days, you have to add the session to the watch list for every day (5 days).

To monitor troubleshooting, click the icon in the 360° Session View.

View the troubleshooting report. This link is displayed for a completed session only if you performed troubleshooting, either manually or automatically.

Launches the Alarm browser. The Alarm browser lists all alarms for the selected session (includes both session and endpoints alarms).

Launches the Endpoint Monitoring page.

Rendezvous meeting type

MeetMe meeting type


Session Topology

The session topology displays the endpoints that are part of a session. If it is a multipoint session, the conferencing devices are displayed along with the endpoints. Also, if the call is a traversal call, Cisco VCS is displayed.

To launch the session topology, you must select a session in the Video Collaboration Sessions table.

The alarm badge displayed on the link and endpoints indicates a fault in the delivery of packets and the peripherals, respectively.

If you suspend an In Use endpoint in DWC for an in progress session, then in session topology it appears as a greyed icon.

Figure 16-3 shows the different statuses displayed in the session topology.

Figure 16-3 Session Topology

1

An endpoint with a limited visibility icon that participates in the session.

2

A No-Show icon associated with an endpoint.

3

An active link between an endpoint and a multipoint switch without alarms.

4

An endpoint with a major alarm that participates in the session. The problem is in peripheral devices.

5

An active link between an endpoint and a multipoint switch with a major alarm.

6

A Disconnect icon associated with an endpoint.

7

Unknown endpoint; an endpoint that is not currently managed in Prime Collaboration. The inventory details for these endpoints may not be available in the Prime Collaboration database.

The endpoints that are registered to the Cisco VCS Expressway are also displayed as Unknown endpoints.

A managed endpoint in Prime Collaboration can make a call to an unsupported endpoint.

   

If there is a fault in the network, the alarm badge is displayed on the network line. You can launch a quick view on the topology to identify the network link direction where the fault has occurred.

In the MSP mode, if you select a customer, sessions for a specific customer is displayed. However, the session topology also displays session info specific to the other customer in the session.

If you do not have access to the other customer in the session, then you can view such customer endpoints with quick view only displaying customer name, endpoint name and endpoint type.

Network Link Quick View

To launch the quick view, rest your mouse pointer over the alarm badge and click on the quick view icon. The network link quick view contains the following tabs:

Link Summary—Displays the alarm status between the endpoints for point-to-point sessions and between an endpoint and multipoint switch for multipoint sessions.

Alarms Summary—Displays the alarm severity, the source that triggered the alarm, and the description of the generated alarm.

Call Details—Displays the endpoint name, phone number, and protocol. These details are displayed for the endpoints connected through the selected network link.

Endpoints Quick View

You can launch a quick view for endpoints in the Managed and Unknown states. To launch the quick view, rest your mouse pointer over an endpoint and click on the quick view icon.

For devices in Managed state, the following details are displayed:

Endpoint Summary—Displays the endpoint details such as system type, IP address, physical location, usage status, directory number (SIP URI and/or H323 ID), cluster ID, and so on. In case of MSP, the customer name is also displayed. (360 degree view- In the participant tab, the customer name is displayed in the Customer column.)

Alarms Summary—Displays the Alarm Severity, the Category of the alarm, and the Description of the generated alarm.

From the quick view, you can add an endpoint to the watch list, launch the Endpoint Monitoring page, and view the alarms for the selected endpoint.

Conferencing Resource - Prime Collaboration also lets you view information about the region that the MCU belongs to.

In the MSP mode, quick view on the individual endpoint is enhanced to add detail about a specific organization that the endpoint belongs to.

You can select one or more customer from a quick view or select the option- All, which displays all customers at once. The option- All displays aggregate information for all customers (for example, dashlets, reports) unlike the specific option that displays data for a specific customer only.

Endpoint Statistics

You can monitor the Quality of Service (QoS) of the endpoints in this pane. Endpoint statistics are displayed for in-progress and past sessions (see Figure 16-4). Also, the peripheral status and system information are available for the scheduled sessions.

This page displays information on the peripheral status, endpoint system details, session details, and session statistics for a selected endpoint in the session topology pane.

In MSP mode, the system information contains the Customer name in addition to other details.

In a multisite session, the session statistics (audio and video) and session information are displayed for each connected endpoint when the center endpoint (conferencing device) is selected.

If you suspend an In Use endpoint in DWC for an in progress session, then no details appear in the Session Information pane. You will see a message that Data is not available for Suspended endpoints.


Note Session statistics details (present and past) are not displayed for Cisco Cius and Cisco IP Phones.


Session Statistics

The Session Statistics pane (see Figure 16-4) displays the statistics information, such as packet loss, latency, jitter, and so forth for:

Audio—Primary codec, secondary codec 1 and 2, auxiliary and primary legacy.

Video—Primary codec and secondary codec 1 and 2.

Figure 16-4 Session Statistics

The information displayed varies, based on the endpoint type that you have selected.

A black vertical line indicates the threshold value. You can define the threshold value for Rx packet loss, average period jitter, and average period latency using the Administration > Alarm and Event Configuration option.

Red indicates the value has exceeded the defined threshold. Gray indicates the current value. This color is used for those parameters that do not contain threshold values.

An alarm badge indicates the actual fault in the network. For past sessions, Prime Collaboration does not display the threshold value or alarm badge in session statistics.

All session and endpoint statistics data older than one day are purged.

If you suspend an In Use endpoint in DWC for an in progress session, then no details appear in the Session Statistics pane. You will see a message that Data is not available for Suspended endpoints.