Cisco Prime Collaboration Network Monitoring, Reporting, and Diagnostics Guide, 9.0
Voice Reports
Downloads: This chapterpdf (PDF - 234.0KB) The complete bookPDF (PDF - 3.25MB) | Feedback

Voice Reports

Table Of Contents

Voice Reports

Voice Call Quality Event History Reports

Voice Call Quality Reports

Configuring Settings for Most-Impacted Endpoints Reports

Understanding Sensor Reports

Viewing Sensor Stream Correlation Data

Enabling the Sensor Stream Correlation Window to Display

Understanding Endpoints Report

UCM/CME Phone Activity Reports

Audio Phone Move Report

Audio Phone Audit Report

Removed IP Phones Report

Extension Number Changes Report

Suspect Phone Report

Duplicate MAC/IP Address Report

Video Phone Move Report

Video Phone Audit Report

Removed Video Phones Report

Video Phone Extension Number Changes Report

Understanding the Time Period Covered by Audio IP Phone Activity Reports

Tracking Phone Status when a Cisco Unified Communications Manager Is Down

UCM/CME Phone Inventory Reports

IP Phone Inventory Analysis Report

Audio Phones/Lines Report

SRST Audio Phones Report

Audio SIP Phones Report

IP Communicators Report

CTI Applications Report

ATA Devices Report

Cisco 1040 Sensors Report

Video Phone Inventory Analysis Report

Video Phones/Lines Report

SRST Video Phones Report

SIP Video Phones Report

Displaying or Hiding Columns in a Report


Voice Reports


Prime Collaboration provides predefined and customizable reports that help you to identify the issues affecting the voice transmission quality in your network. The reports show the times when MOS has been below configured thresholds, the codec in use, and the endpoints on which the violations have occurred.

Prime Collaboration provides separate reports for data obtained from:

Cisco 1040 sensors—Prime Collaboration obtains data from sensors every 60 seconds.

Cisco Unified CM clusters—Prime Collaboration obtains CVTQ data from clusters every 60 seconds. However, data for a given call becomes available only after the call completes. Therefore, these reports are generated only after the call has completed.

Voice Call Quality Event History Reports

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

MOS

Destination

Codec

Phone model

Sensor

Date

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

The 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.

Voice Call Quality Reports

You can use the Call Quality reports to examine the voice transmission quality in your network.

Table 8-1 provides information about the Call Quality reports.

Table 8-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. See Understanding Sensor Reports for more information

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.

Note In order to get all CDRs for all device pools or locations, you should not use the Device Pool or Location radio buttons, but use the End Point radio button.


Table 8-2 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.


Table 8-2 Voice Call Quality Report Contents 

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

Caller Termination Cause—String that describes why the call was terminated on the caller endpoint.

Called Termination Cause—String that describes why the call was terminated on the called endpoint.

See Call termination cause codes section in Cisco Unified Communications Manager Call Details Record Administration Guide for the cause codes for failed calls.

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 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 week, 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 Enabling the Sensor Stream Correlation Window to Display.


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.

Table 8-3 lists the data that is displayed in the Stream Summary table. Table 8-4 lists information from the related CDR. Table 8-5 lists details for streams with the same SSRC as the one in Table 8-3.

Table 8-3 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.


Table 8-4 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 8-4 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.


Table 8-5 lists data from streams with an SSRC that matches the one in Table 8-3.

Table 8-5 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

Audio Phone Audit Report

Removed IP Phones Report

Extension Number Changes Report

Suspect Phone Report

Duplicate MAC/IP Address Report

Video Phone Move Report

Video Phone Audit Report

Removed Video Phones Report

Video Phone Extension Number Changes Report

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, choose Reports > 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, choose Reports > 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 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.


Tips 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.

UCM/CME Phone Inventory Reports

Inventory reports provide information about audio phones, video phones, SRST phones, audio SIP phones, and IP communicators. It also provides information about the CTI applications, Cisco Analog Telephone Adaptor (ATA) devices, and Cisco 1040 sensors.

The following Inventory reports are available:

IP Phone Inventory Analysis Report

Audio Phones/Lines Report

SRST Audio Phones Report

Audio SIP Phones Report

IP Communicators Report

CTI Applications Report

ATA Devices Report

Cisco 1040 Sensors Report

Video Phone Inventory Analysis Report

Video Phones/Lines Report

SRST Video Phones Report

SIP Video Phones Report

IP Phone Inventory Analysis Report

You can use the IP Phone Inventory Analysis report to view IP phones that meet the specified criteria; for example, IP phones that are registered to a particular Cisco Unified CM or IP phones that are not connected to a particular switch.

Inventory Analysis searches for phones using:

An implicit "or" within each field—If you enter more than one value in a field, Inventory Analysis searches for phones that match any value that you entered.

An implicit "and" for all fields—If you enter values in more than one field, Inventory Analysis searches for phones that match at least one value from each field.

For example, if you enter two phone models, such as 7910 and 7935, in the IP Phone Model field, the Inventory Analysis report includes all phones of these models.

If you enter the VLAN ID and switch name, Prime Collaboration searches for phones that meets these criteria. The report includes only phones that are connected to the switch and located in the selected VLAN.

To generate the IP Phone Inventory Analysis report, choose Report > Inventory Reports > IP Phone Inventory Analysis.

Audio Phones/Lines Report

Use the Audio Phones/Lines report to view and manage the list of audio phones in your network.

To generate the Audio Phones/Lines report, choose Report > Inventory Reports > Audio Phones/Lines.

You can launch the following tests from this page:

SRST Test

Phone Tests—Batch and on Demand Tests

Synthetic Test

Phone Status Test

SRST Audio Phones Report

Use the SRST Audio phones report to view the IP phones that are configured for SRST.

IP phones that are configured for SRST are also included in the Audio Phones/Lines report and Inventory Analysis report.

To generate the SRST IP Phones report, choose Report > Inventory Reports > SRST Audio Phones.

Audio SIP Phones Report

Use the Audio SIP Phones report to view the audio SIP phones that are monitored by Prime Collaboration.

To generate the Audio SIP Phones report, choose Report > Inventory Reports > Audio SIP Phones.

IP Communicators Report

This report provides information about the IP Communicators. IP Communicators are also included in the Audio Phones/Lines, Inventory Analysis, and CTI Applications reports

To generate the IP communications reports, choose Report > Inventory Reports > IP Communicators.

CTI Applications Report

The CTI Applications report lists CTI applications that are registered with Cisco Unified CM.

The following applications are registered to Cisco Unified CM as CTI devices or CTI ports:

Cisco Personal Assistant

Cisco Customer Response Applications

Cisco IP Contact Center

Cisco Emergency Responder

To generate the CTI Applications report, choose Report > Inventory Reports > CTI Applications.

ATA Devices Report

The ATA Devices report provides information about the ATA devices that are registered with Cisco Unified CM.

To generate the ATA Devices report, choose Report > Inventory Reports > ATA Devices.

Cisco 1040 Sensors Report

The Cisco 1040 Sensors report provides information about Cisco 1040 sensors that are deployed in your network.

When a web interface is accessible for an IP phone, you can open it from Cisco 1040 sensor report by clicking the hyperlink for one of the following:

Extension number

MAC address

IP address

To generate the Cisco 1040 Sensors report, choose Report > Inventory Reports > Cisco 1040 Sensors.

Video Phone Inventory Analysis Report

Use Video Phone Inventory Analysis report to view the video phones that meet the specified criteria. For example, video phones that are registered to a particular Cisco Unified CM or video phones that are not connected to a particular switch.

To generate the Video Phone Inventory Analysis report, choose Reports > Video IP Phones > Inventory > Video Phone Inventory Analysis.

Video Phones/Lines Report

Video Phones/Lines report provides information about the video phones that are monitored by Prime Collaboration.

To generate the Video Phones/Lines report, choose Reports > Video IP Phones > Inventory > Video Phones/Lines.

SRST Video Phones Report

Use the SRST Video Phones report to view information about the video phones that are configured for Survivable Remote Site Telephony (SRST).

Video phones that are configured for SRST are also included in the All Video Phones/Lines and Inventory Analysis report.

To generate the SRST Video Phones report, choose Reports > Video IP Phones > Inventory > SRST Phones.

SIP Video Phones Report

Use the SIP Video Phones report to view information about the SIP video phones that are monitored by Prime Collaboration.

When a web interface is accessible for a video phone, you can open it from the SIP video phone report by clicking the hyperlink for one of the following:

Extension number

MAC address

Video phone IP address

To generate the SIP Video Phones report, choose Reports > Video IP Phones > Inventory > SIP Video Phones.


Note TelePresence endpoint details are included in the IP Phone Inventory Analysis, Audio Phones/Lines, Video Phone Inventory Analysis, and Video Phones/Lines reports.


Displaying or Hiding Columns in a Report

By default, Sensor Report, Endpoint Report, and CDR Call Report do not display every possible column of data.

To select the data that you would like to display or hide:


Step 1 In the upper-right corner of a report, click the Filter Report button .

Step 2 From the Available Column(s) list or the Displayed Column(s) list, choose the column you want to display or hide.

Step 3 Click Add or Remove, and then click Update.