Cisco Prime Collaboration Assurance Guide - Advanced, 10.0
Prime Collaboration Reports
Downloads: This chapterpdf (PDF - 1.43MB) The complete bookPDF (PDF - 8.14MB) | Feedback

Prime Collaboration Reports

Contents

Prime Collaboration Reports

You can use the Prime Collaboration reports to identify problem areas, locate most commonly used and least used endpoints, and determine ideal locations and required endpoint types for future deployment.

Types of Reports

The following types of reports are available:

Report Type

Includes

Interactive Reports

  • Voice Call Quality Event History Reports
  • Voice Call Quality Reports
  • UCM/CME Phone Activity Reports
  • UCM/CME Phone Inventory Reports
  • TelePresence Reports

Scheduled Reports

  • Utilization
    • Monthly Utilization Report
    • Monthly No Show Report
    • Session Detail Report
  • Inventory
    • Managed Devices Report
    • Unmanaged Devices Report

Administrative Reports

  • System Status Report
  • Who Is Logged On Report
  • Process Status Report
  • Audit Log Report

Communications Manager Reporting

Communications Manager Reporting enables you to cross launch to the reporting pages for the Cisco Unified Communications Manager clusters.

You can download reports or receive them in your e-mail.

Types of Reports

The following types of reports are available:

Report Type

Includes

Interactive Reports

  • Voice Call Quality Event History Reports
  • Voice Call Quality Reports
  • UCM/CME Phone Activity Reports
  • UCM/CME Phone Inventory Reports
  • TelePresence Reports

Scheduled Reports

  • Utilization
    • Monthly Utilization Report
    • Monthly No Show Report
    • Session Detail Report
    Inventory
    • Managed Devices Report
    • Unmanaged Devices Report

Administrative Reports

  • System Status Report
  • Who Is Logged On Report
  • Process Status Report
  • Audit Log Report

You can download reports or receive them in your e-mail.

Administrative Reports

The following administrative reports are available:

Report

Description

System Status Report

Provides information about failed processes, data purging, notifications, phone licensing, and system limits. It also provides information about synthetic, phone status, and node-to-node tests.

Who Is Logged On Report

Helps you to identify users who are currently logged into Prime Collaboration.

Process Status

Shows the status of processes that are currently running on Prime Collaboration.

Audit Log Report

Provides information about user login and logout.

Communications Manager Reporting

Communications Manager Reporting enables you to cross launch to the reporting pages for the Cisco Unified Communications Manager clusters.

Go to Reports > Communication Manager Reporting , and click a cluster name to open the Cisco Unified Reporting application.

Interactive Reports

You can generate the following Interactive Reports:

Report

Description

UCM/CME Phone Inventory

Provides audio phone, video phone, SRST phone, audio SIP phone, and IP communicator inventory details. It also provides information about the Computer Telephony Interface (CTI) applications, Cisco Analog Telephone Adaptor (ATA) devices, and Cisco 1040 sensors.

Voice Call Quality Event History

Provides history of call quality events (for both devices and clusters). You can also generate customized reports for specific events and device groups.

UCM/CME Voice Call Quality

Provides information about the voice transmission quality in your network. Call Quality reports show the times when MOS has been below configured thresholds, the codec in use, and the endpoints on which the violations have occurred.

TelePresence

Provides information about the completed session, endpoint utilization, and No Show endpoints. It also provides information about the In Progress sessions, conferencing devices, and their average and peak utilization details.

Voice Call Quality Reports

You can use the Call Quality reports to examine the voice transmission quality in your network. For more information on voice call quality and MOS, see Overview of Call Quality Thresholds and Threshold Groups.

The following table provides information about the Call Quality reports

Table 1 Call Quality Reports

Report Name

Description

How to Generate

Sensor Report

Displays the name of the sensor that collected the data, endpoints involved, MOS, jitter, and time stamp.

Choose Reports > Interactive Reports > Call Quality Report > Sensor.

Endpoints Report

Displays the MOS and impairment details for the specified endpoints (caller and called).

Choose Reports > Interactive Reports > Call Quality Reports > Endpoints.

Most-Impacted Endpoints Report

Displays the endpoints where the greatest number of violations occurred. By default, Prime Collaboration determines the top 10 most-impacted endpoints .

Choose Reports > Interactive Reports > Call Quality Report > Most Impacted Endpoints by Sensor

or

Choose Reports > Interactive Reports > Call Quality Report > Most Impacted Endpoints by CVTQ.

CDR Call Report

Displays call details such as call category type, call class, call duration, termination type, call release code, and so on.

Choose Reports > Interactive Reports > Call Quality Report > CDR.

UCM/CME Voice Call Quality Report Contents
The following table describes the fields of Voice Call Quality reports.

Note


All the fields described in this table may not appear in all voice call quality reports.


Field Description
Sensor Name—Descriptive name for the sensor that collected the data and analyzed the MOS.
Note   

The name Cisco 1040 + < last 6 digits from MAC address > identifies a Cisco 1040 that automatically registered with Prime Collaboration.

ID—1040 MAC address or NAM IP address.

Speaker/Listener Directory Number—Displayed when the device is managed by a Unified Communications Manager that:
  • Is added to Prime Collaboration with the proper credentials
  • Has not been suspended from monitoring.

Device Type—Can provide the device type or one of these:

  • N/A—Some error prevents Prime Collaboration from obtaining the device type.
  • Unavailable-This is the first time Prime Collaboration has seen this phone and the device type is not yet known; or the corresponding Unified Communications Manager:
    • Has not been added to Prime Collaboration.
    • Did not provide a valid device type to Prime Collaboration.

IP Address—If an IP address is clickable, click it to launch the Detailed Device View page or Phone Detail window.

UDP Port—Transport layer port that is the source of the media stream.

Device Name.

Time Time at which the sensor calculated MOS.
TOS Type of Service (TOS).
MOS Average MOS value during the sample duration. The value might be N/A or not available if the sample duration is very short.

MOS reflects the experience of the listener. Click the value to open a Sensor Stream Correlation window.

Minimum MOS The minimum MOS score within the sample duration.

The value might be N/A or not available if the sample duration is very short.

Primary Degradation Cause One of these:
  • Jitter
  • Packet loss
  • None—Jitter and packet loss values are both 0 (zero). The value might be N/A or not available if the sample duration is very short.
Grade Based on the global threshold settings. Select one of the following
  • Good—The MOS value exceeds the acceptable MOS threshold.
  • Acceptable—The MOS value falls between the acceptable MOS threshold and the poor MOS threshold.
  • Poor—The MOS value falls below the poor MOS threshold.
  • No MOS—The sample interval is under three seconds, therefore the MOS value could not be calculated.
  • Short Call—A short duration call (less than 9 seconds) for which Unified Communications Manager set MOS to zero.
Jitter (ms) Milliseconds of jitter during the sample duration.
Packet Loss Number of packets lost due to network transmission during the sample duration. Computed based on observed RTP sequence number analysis.
Sample Duration(s) Number of seconds, between the first and last packet that is analyzed. The value is usually 60, but can be less for an initial or final stream.
Max Jitter (ms) Maximum milliseconds of jitter during the sample duration.
Adjusted Packet Loss(%) Percentage packet loss due to high jitter. Computed based on a reference jitter buffer with a fixed length delay. This value is not affected by network loss.
Packet Loss (%) Percent of packet loss. (Packets lost divided by total packets expected expressed as a percent.)
SSRC Synchronization source ID-Identifies the source of a stream of RTP packets.
Listener DN/IP Identifies the endpoint-called or caller-for which MOS and impairment details are reported; one of these:
  • IP address of the listener.
  • Directory number of the listener.
Cluster ID Unified Communications Manager cluster ID.
Caller/Called
  • Directory Number—Directory number where the call was made.
  • Device Type—Type of device making the call.
  • Signaling IP—IP address of the device that originated the call signaling. For IP Phones, this field specifies the address of the phone. For PSTN calls, this field specifies the address of the H.323 gateway.
  • B-Channel—B-channel number of the MGCP gateway, or NA, if not applicable.
  • Media IP—IP address where the call originated.
  • Media Port—Port through which the call originated.
  • Codec—Codec name.
  • Device Pool—Device pool where the call originated.
  • Location—Location where the call originated.
Signaling Start Time Date and time that the call started with respect to the Prime Collaboration server local time zone (not the time zone in which the Unified Communications Manager resides).
Impairment Details
  • Jitter (ms)—Milliseconds of jitter during the call.
  • Packet Loss—Number of packets lost during the call.
  • Concealment Seconds—Number of seconds that have concealment events (lost frames) from the start of the voice stream (includes severely concealed seconds).
  • Severely Concealed Seconds—Number of seconds during which a significant amount of concealment (greater than fifty milliseconds) was observed.
  • Latency—Delay
  • Concealment Ratio—Ratio of concealment frames to total frames.
Call Release Code
Call Category Names A comma-separated list of the categories to which the call belongs.
Call Category Types A comma-separated list of the category types to which the call categories belong.
Call Class One of these: • Offnet • Onnet Note For more information, see Understanding OffNet and OnNet Calls .
Configuring Settings for Most-Impacted Endpoints Reports
Use this procedure to configure:
  • The number of endpoints to be included in CVTQ and sensor most-impacted endpoint reports no matter when they run—daily, weekly, or on demand.
  • The most-impacted endpoints reports to export—CVTQ or sensor or both. Most-impacted endpoint reports can run daily and weekly, exporting the results to a comma-separated values file (CSV) or a portable document format (PDF) file. You can save the reports on the server and, optionally, automatically send them through e-mail.

Note


The maximum number of records that can be exported to a PDF file is 2,000. The maximum number of records that you can export to CSV is 30,000.

    Step 1   Choose Reports > Interactive Reports > Voice Call Quality Reports > Export Most Impacted Endpoints. The Export Settings (for Most-Impacted Endpoints) page appears, displaying the information described in the following table.
    GUI Element Description/Action
    Number of Endpoints field Enter the number of endpoints that you want to see on all-exported or directly launched-most-impacted endpoints reports.
    Daily at 1:00 AM check boxes To generate the report every day, select at least one of the following:
    • CSV check box-Save the report in CSV format.
    • PDF check box-Save the report in PDF format.

    If neither is selected, Prime Collaboration does not generate the reports.

    Weekly at 1:00 AM Monday check boxes To generate the report every day, select at least one of the following:
    • CSV check box-Save the report in CSV format.
    • PDF check box-Save the report in PDF format.

    If neither is selected, Prime Collaboration does not generate the reports.

    Report Type Select at least one of the following:
    • Sensor
    • CVTQ
    Note    Separate reports are generated for sensor and CVTQ data.
    Save at Enter a location for storing the reports on the server where Prime Collaboration is installed; a default location is displayed.
    Note    If you configure export settings to save files outside of opt/CSCOpx , be sure to also log into the Prime Collaboration server, create the folder that you entered on the Export Settings page, and provide write permission to the folder for the user casuser . If you do not, Prime Collaboration cannot create the export files.
    E-mail (to) (Optional) Enter one or more complete e-mail addresses separated by commas.
    Note    You should configure another e-mail address to which Prime Collaboration can send notifications for server process restarts. (Otherwise, Prime Collaboration sends notifications to the address defined in this field.)

    SMTP Server

    (Optional) Enter an SMTP server.

    E-mail (from) (Optional) This field does not appear in the Export Settings (for Most-Impacted Endpoints) page.
    To configure an e-mail address to appear in the From field, do the following:
    1. On the Prime Collaboration system, go to opt/CSCOpx/qovr (if the default location was selected during installation). You must log in as root.
    2. Open the qovrExport.properties file.
    3. In the qovrExport.properties file, add EmailFrom=<email address>.
    4. Save and close the file.
    5. Restart the QOVR process. From the command line, enter these commands:
      pdterm QOVR
      pdexec QOVR
    Step 2   Click Apply.

    Understanding Sensor Reports

    Two RTP streams—incoming and outgoing—make up a single voice call. Sensors capture voice traffic in various ways:

    • Cisco 1040s listen to RTP voice traffic on Switch Port Analyzer (SPAN) ports that have been configured to mirror voice traffic. Depending on the phone ports and the voice VLANs that a SPAN port mirrors, a Cisco 1040 might listen to only one or both RTP streams, calculating MOS and sending data to Prime Collaboration at 60-second intervals.
    • NAMs can also capture data from SPAN ports. Alternatively, you can configure NAMs to use other means of data capture. For a NAM to provide the data that Prime Collaboration needs, RTP stream monitoring must be enabled on the NAM. Prime Collaboration obtains data from NAMs at 60-second intervals.

    Sensor reports display the MOS that a sensor calculated for RTP streams on a minute-by-minute basis. For each interval, a sensor report displays one or two rows of data, depending on whether data from only one or both RTP streams was captured. Each row identifies the sensor that collected the data, the endpoints involved, MOS, milliseconds of jitter, and the time stamp.

    Viewing Sensor Stream Correlation Data
    To launch a Sensor Stream Correlation window, generate a sensor diagnostic report and click the MOS value for the stream that interests you. The MOS value that you click is a measure of the listener’s experience in the RTP stream.

    Note


    If a Cannot find server window appears instead of a Sensor Stream Correlation window, see Viewing Sensor Stream Correlation Data


    Prime Collaboration correlates data from sensors against one another and against Unified Communications Manager call records and displays tables with the following information:

    • Stream summary—A subset of the data that was displayed on the sensor diagnostic report. Additionally, the source synchronization ID (SSRC) for the stream is listed. An SSRC identifies the source of a stream of RTP packets and remains unique during an RTP session.

      Note


      Another SSRC is assigned to RTP streams sent when the listener endpoint and UDP port are the source of a stream of RTP packets. The Sensor Stream Correlation window correlates data for one SSRC only.


    • Call record—Information from the Unified Communications Manager CDR that correlates to the stream.

      Note


      If the call is not complete yet, No Call Detail Record found for these streams appears in the table heading.


    • Stream details—Details from one or more sensors where the SSRC matches the one in the stream summary.
    The following table lists the data that is displayed in the Stream Summary table.
    Table 2 Stream Summary
    Column Description
    Speaker/Listener
    • Directory Number-Displayed when the device is managed by a Unified Communications Manager that:
      • Is added to Prime Collaboration with the proper credentials.
      • Has not been suspended from monitoring.
    • IP Address-Depending on the device type, an IP Phone Details page or a Detailed Device View opens.
    • UDP Port-Transport layer port that is the source of the media stream.
    • Device Type-Can provide the device type or one of these:
      • N/A-Some error prevents Prime Collaboration from obtaining the device type.
      • Unavailable-This is the first time that Prime Collaboration has seen this phone and the device type is not yet known; or the corresponding Unified Communications Manager:
        • Has not been added to Prime Collaboration.
        • Did not provide a valid device type to Prime Collaboration.
    TOS Type of service.
    Codec Codec name.
    SSRC Synchronization Source ID-Identifies the source of a stream of RTP packets.
    The following table lists data from the CDR, if available. If the call has not completed yet, No Call Detail Record found for these streams appears in the table heading and the row is blank.
    Table 3 Call Record
    Column Description
    Call Disconnect The time that the call disconnected. Zero (0) is displayed if the call never connected.
    Cluster ID Unified Communications Manager cluster ID.
    Caller Signaling IP IP address of the device that originated the call signaling. For Cisco Unified IP Phones, this field specifies the address of the phone. For PSTN calls, this field specifies the address of the H.323 gateway.
    Caller B-Channel B-channel number of the MGCP gateway, or NA, if not applicable.
    Called Signaling IP IP address of the device that terminates the call signaling.
    Called B-Channel B-channel number of the MGCP gateway, or NA, if not applicable.
    Call Duration (s) Length of the call, in seconds.
    Caller Termination Cause Populated when the originating party releases the call.
    Note    Termination causes might not be populated.
    Called Termination Cause Populated when the terminating party releases the call or the call is rejected.
    Note    Termination causes might not be populated.
    The following table lists data from streams with an SSRC that matches the one in Stream Summary table.
    Table 4 Stream Details
    Column Description
    Sensor Name Display name of the Cisco 1040 or NAM.
    Time Time at which the sensor calculated the MOS.
    MOS Average MOS in the sample duration.
    Minimum MOS Minimum MOS in the sample duration.
    Primary Degradation Cause Jitter, Packet Loss, or None when jitter and packet loss values are zero (0).
    Jitter (ms) Milliseconds of jitter.
    Packet Loss Number of packets lost. (Actual packet loss for the sample duration.)
    Sample Duration (s) Number of seconds elapsed between the first and last packets that are analyzed.
    Max Jitter (ms) Maximum jitter, in milliseconds.
    Adjusted Packet Loss (%) Percentage packet loss due to high jitter. Computed based on a reference jitter buffer with a fixed length delay. This value is not affected by network loss.
    Packet Loss (%) Percentage packet loss. (Actual packets lost divided by total packets expected expressed as a percent.)
    Enabling the Sensor Stream Correlation Window to Display

    When you try to open a Sensor Stream Correlation window, if a window opens displaying a message such as "The page cannot be found", you can resolve the problem by disabling the proxy server setting in your browser. The setting is found in internet options on the Connection tab.

    Understanding Endpoints Report

    Using the Endpoint report filters, you can generate reports that include all call data from the clusters or reports that include a subset of call data, such as:

    • Where MOS was less than a specific value
    • When reported from specific clusters
    • Where particular codecs were used
    • A set of endpoints
    • All clusters or a subset of clusters
    • A given time period

    Note


    The number of minutes that Prime Collaboration searches for diagnostic report data is configurable.


    The Endpoint diagnostic report displays two lines for each call: one line with data for the listening experience at the called endpoint and another line for the caller endpoint.

    UCM/CME Phone Activity Reports

    UCM/CME Phone Activity reports provide information about the audio and video phones that have undergone a status change during the last 30 days.

    The following Activity reports are available:

    Audio Phone Move Report

    The Audio Phone Move report displays the details of IP phones that have been moved in the last 30 days. It also displays the Extension, Cisco Unified CM address, switch address, and switch ports used before and after the move.

    The Audio Phone Move report shows the time at which the IP phone move was detected, and not the time at which the move occurred.

    Prime Collaboration obtains fresh data for the Audio Phone Move report every 5 minutes. You can also close the report and regenerate it to refresh the data.

    To generate the Audio Phone Move report, choose Reports > Interactive Reports > Activity Reports > Audio Phone Move.


    Note


    Audio Phone Move report is not supported for the phones that do not support CDP.


    Audio Phone Audit Report

    The Audio Phone Audit report shows the changes that have occurred in the managed IP phone network. For example, this report shows the IP phones that have been added or deleted from your network, IP phone outage status, and so on. Phone status changes occur, for instance, when a phone becomes unregistered with the Cisco Unified CM.

    To generate the Audio Phone Audit report, choose Reports > Interactive Reports > Activity Reports > Audio Phone Audit.


    Note


    The IP Phone Audit report is not supported for Cisco Wireless IP Phone 7920.


    Removed IP Phones Report

    The Removed IP Phones report lists phones that have been removed during the last 30 days.

    Prime Collaboration gathers the information used in this report every 5 minutes.

    To generate the Removed IP Phones report, choose Reports > Interactive Reports > Activity Reports > Removed Audio Phones.


    Note


    The Removed IP Phone report is not supported for Cisco Wireless IP Phone 7920.


    Extension Number Changes Report

    The Extension Number Changes report lists the audio phones for which extension numbers were changed during the last 30 days.

    Prime Collaboration gathers the information used in this report every 5 minutes.

    To generate the Extension Number Changes report, chooseReports > Interactive Reports > Activity Reports > Audio Phone Extension Changes.


    Note


    The Extension Number Changes report is not supported for Cisco Wireless IP Phone 7920.


    Suspect Phone Report

    The Suspect Phone report displays the attributes of all IP phones that:

    • Have not registered with a Cisco Unified CM.
    • Have made an unsuccessful attempt to register with a Cisco Unified CM.

    To generate the Suspect Phone report, choose Reports > Interactive Reports > Activity Reports > Suspect Phones.

    Some IP phones appear marked as Suspect when they are not. To correct this, make sure that the Cisco Unified CM is managed by Prime Collaboration.

    • If the Cisco Unified CM is not managed by Prime Collaboration, add it to Prime Collaboration.
    • If the Cisco Unified CM is managed by Prime Collaboration but is not reachable, this can be due to loss of connectivity. Make sure that connectivity with Prime Collaboration is restored.

      Note


      The Suspect Phone report is not supported for Cisco Wireless IP Phone 7920.


    Duplicate MAC/IP Address Report

    The Duplicate MAC/IP Address report lists the attributes of all IP phones that have:

    • Duplicate MAC addresses; that is, a phone that has the same MAC address as another phone but a different IP address.
    • Duplicate IP addresses; that is, a phone that has the same IP address as another phone but a different MAC address.

    Prime Collaboration does not show a multihomed host as a phone with a duplicate MAC address.

    For the Duplicate MAC/IP Address report to display the correct information, the switch to which the phone is connected must be monitored by Prime Collaboration. If the switch is not monitored by Prime Collaboration, the report will not display any information.

    To generate the Duplicate MAC/IP Address report, chooseReports > Interactive Reports > Activity Reports > Duplicate MAC/IP.

    Video Phone Move Report

    The Video Phone Move report displays video phones that have been moved in the last 30 days. It also displays the Extension, Cisco Unified CM address, switch address, and switch ports used before and after the move.

    The Video Phone Move report shows the time at which the video phone move was detected, and not the time at which the move occurred.

    Information for the Video Phone Move report is gathered every 5 minutes using Video Phone Movement Tracking.

    Video Phone Movement Tracking is used to:

    • Check all the switches and Cisco Unified CMs
    • Identify the list of changes
    • Generate the data on video phone moves

    To generate the Video Phone Move report, choose Reports > Interactive Reports > Activity Reports > Video Phone Move.


    Tip


    Tip Video Phone Move report is not supported for the phones that do not support CDP.


    Video Phone Audit Report

    The Video Phone Audit report shows the changes that have occurred in the managed video phone network. For example, this report shows you the video phones that have been added or deleted from your network, changes in video phone status, and so on. Phone status changes occur, for instance, when a phone becomes unregistered with the Cisco Unified CM.

    To generate the Video Phone Audit report, choose Reports > Interactive Reports > Activity Reports > Video Phone Audit.

    Removed Video Phones Report

    The Removed Video Phones report lists phones that have been removed during the last 30 days.

    Prime Collaboration gathers fresh data for the Video Phone Move report every 5 minutes. You can also close the report and regenerate it to refresh the data.

    To generate the Removed Video Phones report, choose Reports > Interactive Reports > Activity Reports > Removed Video Phones.

    Video Phone Extension Number Changes Report

    The Extension Number Changes report lists the video phones for which extension numbers were changed during the last 30 days.

    To generate the Extension Number Changes report, choose Reports > Interactive Reports > Activity Reports > Extension Changes.

    Understanding the Time Period Covered by Audio IP Phone Activity Reports

    When you generate an Audio IP Phone or Video IP Phone Activity report, your results can be affected by the time zones in which each of following resides:

    • Your client system—Prime Collaboration calculates the time period (previous 24 hours through previous 7 to 30 days, depending on the report) for Phone Activity reports based on the date and time on your client system.
    • Prime Collaboration system—Prime Collaboration records some audits, such as extension number changes, based on the time that the change is detected on the Prime Collaboration system.
    • Cisco Unified Communications Manager—Prime Collaboration records some audits, such as phone moves, based on the time on Cisco Unified Communications Manager that changes were detected.

    If any of these systems is not in the same time zone as your system, you must take the time zone difference into account when you generate and view Phone Activity reports.


    Note


    If the audit date and time on the Prime Collaboration system is inconsistent with those shown in the Audio IP Phone or Video IP Phone Audit report, make sure that all Cisco Unified CMs in the network are set to synchronize.


    Tracking Phone Status when a Cisco Unified Communications Manager Is Down

    If a Cisco Unified Communications Manager that is configured with a backup goes down, audio and video IP phones fail over to the backup Cisco Unified Communications Manager.

    Prime Collaboration stores audit records for the phones that register with the backup and these status changes are included in IP Phone and Video Phone Audit reports.

    Prime Collaboration does not store audit records in the following cases:

    • An entire Cisco Unified Communications Manager cluster goes down. A Cisco Unified Communications Manager for which a backup is not configured goes down.

    Therefore, status changes for the phones registered to Cisco Unified Communications Managers in these situations are not included in Audio IP Phone Status and Video IP Phone Activity reports.

    Voice Call Quality Event History Reports

    You can search the Event History database for Voice Call Quality events based on:

    • MOS
    • Destination
    • Codec
    • Phone model
    • Sensor
    • Date
    • Export

    To generate Call Quality Event History report, choose Reports > Interactive Reports > Voice Call Quality Event History Reports.

    The Voice Call Quality Event History report is a scrollable table that lists up to 2,000 records, based on your search criteria. To view database contents beyond 2,000 records, click the Export tool button in the upper-right corner of the window. If more than 1,000 records match your search criteria, a popup window reports the total number of matching records found.

    TelePresence Reports

    You can use TelePresence reports to view endpoint utilization, conferencing device utilization, all session summary, no show endpoints, and session details.

    The following reports can be generated for TelePresence endpoints:


    Note


    To view TelePresence reports, you must have High-end Single-codec, High-end Multi-codec, or Mid-range endpoint license.


    Endpoint Utilization Report

    The Endpoint Utilization report enables you to identify the most utilized and least utilized endpoints.

    Average utilization of an endpoint is calculated using the following formula:

    • For system-defined (1 day, 1 week, 4 weeks) reports: (Total number of utilization in minutes / 
[maximum utilization * 60]) * 100
    • For custom reports: (Total number of utilization in minutes /
[maximum utilization * 60 * number of days]) * 100
      • 1 day: The maximum utilization is ten hours.
      • 1 week: The maximum utilization is 50 hours.
      • 4 weeks: The maximum utilization is 200 hours.
      • Custom report: The maximum utilization is 7.14 hours per day.

        Note


        The utilization is shown as 100% even if the utilization is more than 100%.

    You can customize the endpoint utilization settings. To do so, select an endpoint model (endpoint(s) of a particular model) and then click the Change Utilization button. You can select the number of working hours in a day and the number of working days in a week.

    To generate the Endpoint Utilization report, choose Reports > Interactive Reports > TelePresence Reports > Endpoint Utilization Report.

    Conferencing Device Utilization Report

    This report is generated based on the hourly utilization of conferencing devices.

    Average Utilization
    • 1 day: Average utilization of hour 1 + hour 2 + ... + hour 24) / 24.
    • 1 week: Average hourly utilization of each hour in the week is aggregated and divided by (7 x 24).
    • 4 weeks: Average hourly utilization of each hour in the 4 weeks is aggregated and divided by (7 x 24 x 4).
    • Custom period: Average hourly utilization of each hour in the custom period is aggregated and divided by (7 x 24 x number of days in custom period).

      Note


      The utilization is shown as 100% even if the utilization is more than 100%.


    Peak Utilization
    • 1 day: The peak utilization is analyzed from individual peak values of each of the 24 hours.
    • 1 week: The peak utilization is analyzed from individual peak values of each of the 7*24 hours.
    • 4 weeks: The peak utilization is analyzed from individual peak values of each of the 7*24*4 hours.
    • Custom periods: The peak utilization is analyzed from individual peak values of each hour in the custom period.

    To generate the Conferencing Device Utilization report, choose Reports > Interactive Reports > TelePresence Reports > Conferencing Device Utilization Report.

    No Show Endpoints Summary Report

    The No Show Endpoints Summary report provides information about the endpoints that did not participate in the scheduled sessions. This report is generated based on the scheduled completed sessions data.

    To generate the No Show Endpoints Summary report, choose Reports > Interactive Reports > TelePresence Reports > No Show Endpoints Summary Report.

    Session Detail Report

    The Session Detail report provides the following details: session ID, duration, start/end time, session type, status, and alarm severity.

    To generate the Session Detail report, choose Reports > Interactive Reports > TelePresence Reports > Session Detail Report.

    All Sessions Summary Report

    The All Sessions Summary report provides information about the in-progress and completed sessions. The reports are available for four weeks.

    This report includes the following information: endpoint name, device ID, total utilization, average duration, and longest session.

    To generate the All Sessions Summary report, choose Reports > Interactive Reports > TelePresence Reports > All Sessions Summary Report.

    Scheduled Reports

    Scheduled reports are utilization and inventory reports that you can schedule from the Report Launch Pad. You can generate them according to your scheduling preferences, and download or send them to the configured e-mail ID. These reports can be exported in both CSV and PDF format (except the Session Detail Report, which can be exported only in CSV format). The data for these reports will be available for 30 days only.

    These reports are not enabled by default. You can generate the reports on the spot or enable scheduling to generate them on predefined days.

    The following scheduled reports are available:

    Report Title

    Description

    Utilization Reports

    Monthly Utilization Report

    Provides aggregate monthly reports on the utilization of the endpoints. The aggregate value is calculated by Total utilization for all months / 12.

    Monthly No Show Report

    Provides aggregate monthly reports on the nonparticipation of endpoints in scheduled sessions. The average aggregate value is calculated by Total no show for all months / 12.

    Session Detail Report

    Provides details on the session statistics for all completed sessions.

    Inventory Reports

    Managed Devices Report

    Provides information about managed devices. If a device is unknown, only the IP address is displayed. Use this report to find devices for which credentials have been updated.

    Unmanaged Devices Report

    Provides information about unmanaged devices. Use this report to identify devices for which credentials need to be updated.


    Note


    Scheduled Utilization reports (Monthly Utilization, Monthly No Show, and Session Detail reports) are applicable for both video phones and TelePresence endpoints. Endpoint details will be populated in these reports based on the license that you purchased.


    Generating Scheduled Reports

    You can define the reporting period, the report generation date, and the frequency according to your preferences.

    To generate a scheduled report:


      Step 1   Select a report from the Reports pane.
      Step 2   Click the Settings tab under the Report Details pane, and click Enable Scheduling.
      Step 3   Schedule the report generation using options in the Scheduler and Settings pane.
      Step 4   Do either of the following:
      • Click Submit.
      • Generate the report on the spot:
        • Click Run Now (adjacent to the report you want to generate).
        • Click the Run History tab under the Report Details pane.
        • Download the report.

      To create a customized scheduled report, select a report from the Reports quick display in the left corner only, and click New under the Reports pane. Enter the required information and click Submit. Instances of the run report are queued as jobs under the Job Management page. You can manage and monitor these jobs from the Job Management page (Administration > Job Management).

      Accessing Data for Reports that Contain More than 2,000 Records

      Prime Collaboration reports display up to 2,000 records. If more than 2,000 records are returned when you generate a report, Prime Collaboration displays an informational message before displaying the report.

      In this case, you can:

      • Enter more specific filters to generate a report with fewer records.
      • Export the report data to a CSV file to access the additional records. To open the export window, click the Export icon in the top right of the report window. You can export up to 30,000 records to a CSV file.

      Note


      If your client system seems unresponsive when you try to export files, see Troubleshooting File Download Issues

      Troubleshooting File Download Issues

      If you try to export a report or other data to a file from Prime Collaboration and either the export dialog box or the window that prompts you to save the export file does not appear, use these procedures to try to fix the problem.
      1. If you set the custom levels of security in Internet Explorer to medium or greater, the option, Automatic prompt to file download, is disabled. If you try to download a PDF or CSV file to a client system where Adobe Acrobat Reader or Microsoft Excel not installed, nothing happens. The PDF file or the spreadsheet is not displayed nor is a window that prompts you to save the file. To enable file download windows to display, do this on your desktop:
        1. In Internet Explorer, select Tools > Options.
        2. Select the Security tab and click Custom Level.
        3. Scroll to Downloads and for Automatic prompt to file download, select Enable.
      2. If you are using Internet Explorer, Automatic prompt to file download is enabled, and the window that prompts you to save the file still does not appear, do this:
        1. Press the Ctrl key and click the OK button on the export dialog box.
        2. Continue to hold the Ctrl key down until the window that prompts you to save the file appears.