For Cisco Prime Collaboration Release 11.1 and earlier

This dashlet shows the deployment trend of the configured and active endpoints.

• All endpoints that are managed in Cisco Prime Collaboration Assurance, irrespective of their registration status are categorized as configured endpoints.
• Endpoints in Cisco Prime Collaboration Assurance which are either in registered or partially registered status are active endpoints.

By default, this dashlet will display the graph for all endpoints that were deployed from the date Cisco Prime Collaboration Assurance was installed till the current date. You can filter data based on weeks. If you select the time period as 7 days ago, the graph will display all the endpoints that were deployed from the day you installed Prime Collaboration till the current date (7 days ago).

As an example, you would be able to determine the rate of increase in addition/deployment of a specific endpoint model, say CTS 1000 series, over a period of time.

Note	The Duration global filter is not applicable for this dashlet.

The device details (such as model number, version, and so on) are collected from Prime Collaboration inventory and also by polling the endpoints using SNMP or HTTP. This device information is stored in the Analytics database and is used to group endpoints based on the model. The details thus collected are represented as pie chart.

You can filter deployment data on the detailed view based on endpoint type, endpoint model, device pool, cluster or location. You can also view the cumulative count for active and configured devices for a specific endpoint model.

For Cisco Jabber phones that are registered with Cisco VCS, the count of active and configured endpoints are same irrespective of their registration status. This is because, if the status of Cisco Jabber is unregistered, inventory immediately moves it to Deleted state. For the other phones (like soft client CSF, CUPC and so on) the device is moved to Deleted state only when the status remains to be unregistered for more than 24 hours.

For Cisco Prime Collaboration Release 11.1 and earlier

This dashlet displays the call distribution based on call volume per endpoint model. You can view the details for the calls that are,

• Attempted-All calls, including the completed and failed.
• Completed-All the successful calls made from that endpoint model.
• Dropped-Non zero duration failed calls.
• Failed-All calls that failed.

The device details for this dashlet is collected from Prime Collaboration inventory and the call details are collected from Unified CM and Cisco VCS CDR.

You can filter the call distribution details in the detailed view page based on device pool, IP address, endpoint type, endpoint model, call type, call status, call direction, call count, call duration, cluster, user ID, or location.

The Cluster filter does not support Cisco VCS.

Call direction, in the above sentence means Incoming or Outgoing. It is determined based on the perspective of the endpoint or location making a call. For example, if an endpoint A calls endpoint B, it is an outgoing call from the perspective of endpoint A and incoming call from the perspective of endpoint B.

For Cisco Prime Collaboration Release 11.1 and earlier

This dashlet displays the call distribution based on endpoint types-Audio endpoints and Video endpoints.

Audio endpoints are devices from which you can make and receive audio calls. Audio IP Phones, wireless IP Phones, and personal communication endpoints are categorized under Audio endpoints.

Video endpoints are devices from which you can make and receive the video calls. Multipurpose TelePresence, immersive TelePresence, personal TelePresence, mobile video and desktop video devices are categorized as Video endpoints.

For a list of Supported Audio and Video Endpoints in Cisco Prime Collaboration Assurance, see Supported Devices for Cisco Prime Collaboration Assurance.

The device details for this dashlet is gathered from Prime Collaboration inventory and call details for this dashlet is obtained from Unified CM and Cisco VCS CDR.

You can filter the call distribution details in the detailed view page based on device pool, URI, directory number, IP address, endpoint type, endpoint model, call type, call status, call direction, call count, call duration, cluster, user ID, or location.

This dashlet shows the trend of audio and video usage. It shows the endpoint with maximum number of calls. You can view the data for each week in a graphical or tabular format. By default, data is displayed for the last 1 month.

The endpoints details for this dashlet is collected from Prime Collaboration inventory and the call details are collected from Unified CM and Cisco VCS CDR.

In detailed view, the formula used for calculating the percentage of the audio and video usage is:

Endpoint Count >= number of calls per week with the same call status (failed/dropped/completed/attempted) / Device Count >= number of calls per week (with the same model and call type) * 100.

You can filter the details in the detailed view page based on call type, URI, directory number, endpoint model, call status, usage status, location, device pool, cluster, user ID, or IP address.

This dashlet displays the endpoint types that are least used, based on the number of calls made per week. By default, the dashlet displays only the unused endpoints (endpoints with no calls). The 'No more than X calls per week' category in the dashlet view includes, the unused endpoints and the endpoints with x calls per week.

This dashlet displays data for endpoints registered with Unified CM and VCS. Device details for this dashlet is collected from Prime Collaboration inventory and the call details are collected from CDR.

The detailed view displays only the data that is aggregated weekly. You can filter the data in the detailed view page based on endpoint type, endpoint model, usage status, device pool or location, user ID, or cluster.

Note

The data displayed for the unused endpoints per week in the detailed view graph is not in synchronization with the Least Used Endpoint Types Report table in the detailed view. This is because Least Used Endpoint Types Report table shows aggregated data for the selected time filter. This is same as the dashlet view on Asset Usage.

You can track the most utilized and least utilized endpoints. This dashlet displays a list of Endpoint Names, Session Count, Used Duration, and Utilization for a week. You can filter the data by time period, endpoint type, and utilization percentage.

You can customize the number of working hours per day (by default, 8 hours) and working days per week (by default, 5 days)for each of the managed endpoints using Change Utilization (Assurance Reports > Telepresence Endpoint Reports > Endpoint Utilization Report ). These values are used while analyzing the asset usage for TelePresence Rooms.

You can launch the quick view if you rest the mouse over an endpoint name or utilization, which launches the graph and grid view consisting of number of sessions, duration, and utilization percentage.

In detailed analysis, you can filter the results displayed by time period, All Endpoints or a specific endpoint type, percentage or absolute values, individual or merged graphs. If you choose All Endpoints, you can also filter by utilization percentage.

You can identify endpoints that did not participate in the scheduled sessions. This dashlet displays the data based on the scheduled completed sessions. In this dashlet, you can view total scheduled sessions, scheduled sessions that have occurred, and No Show sessions- scheduled sessions that did not start and scheduled sessions completed but endpoints that were part of the scheduled session did not join (you can also view the data for this column in terms of percentage and absolute value). The endpoints with the no show count greater than zero are listed. You can filter the data by time period, endpoint type, and no show.

In detailed analysis, you can filter the data by time period, endpoint name, endpoint type, endpoint model, no shows (absolute and percentage), cluster, location, device pool to see the No Shows and No Shows percentage trend of endpoints. When you click on an endpoint legend, you can view endpoint model and type, show and no show count along with total scheduled sessions.

Note	This dashlet is not supported in Cisco Prime Collaboration Analytics in MSP mode.

Prerequisites for No Show Video Telepresence Endpoint

For Cisco Prime Collaboration Release 12.1 SP2 and later

Note	Ensure to enable Conference Diagnostics to populate the data.

The following are required for No Show Video Telepresence Endpoint:

• Unified CM and Cisco VCS must be in the Managed state.

• Endpoints and controllers, such as MCU must be in the Managed state.

• Ensure to set the visibility of the devices to "Full Visibility" state.

• JTAPI must be configured on Unified Communications Manager. For information on how to enable JTAPI on Unified Communications Manager, see the Configure Devices for Cisco Prime Collaboration Assurance.

• Cisco Prime Collaboration Assurance server must be registered as a feedback server in Cisco VCS.

• For Conference Diagnostics and Audio Phone Feature Synthetic Tests to work, ensure that CUCM is as per the listed version(s) before applying Cisco Prime Collaboration Assurance Service Pack 1 bundle. For more information, see Supported Devices for Cisco Prime Collaboration Assurance for 12.1 Service Pack 1.

This dashlet lists the top N numbers from which calls originated, based on the total number of calls made from the directory number to any other number within the Prime Collaboration managed deployment.

You can filter the data displayed in the detailed view page based on directory number, call type, call count, call duration, cluster, location, device pool or endpoint details (such as IP, caller number, or source URI and so on). The directory numbers of those endpoints that are managed in the Prime Collaboration are displayed, the external directory numbers are not displayed.

You can view the number of calls or the duration of calls either in absolute or percentage mode. You can also view the users or directory numbers when you filter by endpoint or users respectively.

The formula used for calculating the percentage of top N callers is:

Total number of calls or the duration of calls for a particular number in a week / Total number of calls or duration of calls for all callers in that week * 100.

This dashlet displays data for endpoints registered with Unified CM and VCS.

Using the zoom selector graph displayed in the detailed view, you can adjust the pointer in the time window (x axis) of the graph to view details of the calls that were placed from that particular number, for the selected time period.

You can also view the top N callers for each individual cluster by using the global cluster filter.

This dashlet lists the Top N dialed numbers based on destination, for a specified time period. You can view the Top N numbers that were:

• Called the most number of times (call count)

• Engaged for the longest duration (call duration)

This dashlet displays data for endpoints registered with Unified CM and VCS.

You can filter the details displayed in the detailed view based on directory number, call type, call count, call duration, cluster, or location. The directory numbers of those endpoints that are managed in the Prime Collaboration are displayed, the external directory numbers are not displayed.

This dashlet displays the OffNet versus OnNet traffic trend per location.

You can filter the data displayed in the detailed view page based on off net or onnet traffic, call type, call count, call duration, cluster, location, device pool, endpoint details (such as IP, directory number, or source URI and so on), call direction, or user ID.

Note

You can also filter the data in the detailed view based on the call direction, such as, incoming or outgoing calls. Incoming calls are the calls received by the gateway from the CUCM, whereas the outgoing calls are the calls made from the gateway to the CUCM. So when you filter incoming calls, you must enter the endpoint details of the source or the caller and when you filter outgoing calls , you must enter the endpoint details of the callee or the destination. When you filter data based on the endpoints the directory numbers of those endpoints that are managed in the Cisco Prime Collaboration Assurance are displayed, the external directory numbers are not displayed.

In dashlet view, the formula used to calculate the percentage of OnNet calls is:

Total number of OnNet calls in the location/ Total number of OffNet calls and OnNet calls in that location * 100

The formula used to calculate the percentage of OffNet calls is:

Total number of OffNet calls in the location/ Total number of OffNet calls and OnNet calls in that location * 100

The dashlet does not include the calls processed on Video Communication Server (VCS).

This dashlet helps you to identify the top N locations that have highest number of calls, based on the call count or call duration.

You can filter the details in the detailed view based on location (both Top N and Bottom N), device pool (both Top N and Bottom N), IP Address, directory number, URI, call type, call status, call count, call duration, call direction, user ID, or cluster.

Note	The dashlet displays call locations based on attempted calls only. Filters for the other statuses like completed, dropped, and failed calls are enabled in the detailed view.

In dashlet view, the formula used for calculating the percentage of the locations with highest number of calls is:

Total number of calls or duration of calls in a location / Total number of calls or duration of calls in all locations * 100.

This dashlet displays the distribution of calls that belong to the following predefined call categories:

• External

• Internal

• Conference

• Emergency

• Long distance

• Toll free

• H 323 (Incoming and outgoing gateways/trunks) or MGCP (Incoming and outgoing gateways) or SIP (Incoming and outgoing trunks)

• Voicemail

• Local

• International

To add a call category, see section Call Category Creation.

Note	A call can be included in more than one call category; for example, an internal call can also be a conference call. Therefore, the sum of all calls that belong to all categories might be greater than the reported total number of calls.

This dashlet includes only the details for the calls processed on Unified CM. Call category information is collected from CDR.

In dashlet view, the formula used to calculate the percentage of the distribution of calls is:

Total number of calls or the duration of calls that belong to a specific traffic category / Total number of calls or duration of calls of all categories * 100.

In detailed view, the formula used to calculate the percentage of the distribution of calls is:

Total number of calls of a traffic type which belongs to one call status (failed, dropped, completed, attempted / Total number of calls of a traffic type which belong to Attempted call status * 100.

You can filter the details in the Detailed View based on location, call type, call status, call count, call duration, call direction, user ID, or cluster.

Prime Collaboration Analytics allows you to create custom groups for Trunks, Route Groups, and CAC Locations, based on your business needs. Click Analytics Administration > Group Management. Choose a group from the Group Type drop-down on the top-right. You can create new groups, modify the members of existing group, or remove a group.

For instance, all trunks in your network are displayed in the Analytics Group Management page. Select a trunk, under All Trunks, and add it to an existing group (Click Add to Group) or a new group (Click Add New Group).

After you create a group, the list of available groups are displayed under Trunk Groups in the left pane. These groups are also listed under All Trunks drop-down (in Trunk Utilization dashlet) of the Capacity Analysis dashboard

You can follow a similar approach for creating custom Route Groups and CAC Locations, the corresponding utilization thresholds are listed in the dashlets. When you apply a threshold, the results will be filtered based on threshold filter.

Use the Settings icon on the top-right corner to add or remove the columns displayed.

Note

In MSP mode, the operator users do not have access to Analytics Administration menu, hence cannot create custom group. Group names can only be added or deleted, but cannot be edited. The trunk/route groups for Analytics Group Management and other dashlets in Prime Collaboration Analytics are imported from Prime Collaboration Assurance database, but the custom groups created in Prime Collaboration Analytics are not visible/used in Prime Collaboration Assurance. If you want to display the aggregated data in the Trunk/Route Group Utilization dashlet, you need to define the custom groups using Monitor > Utilization Monitor > Route Group Utilization > RouteGroup Aggregation Settings. If you want create custom groups for DSP, use Device Inventory > Inventory Management > Create Group (under Device Group).

Call Admission Control (CAC) enables you to control the audio and video quality of calls over a wide-area (IP WAN) link by limiting the number of calls that are allowed on that link.

Audio and video quality can begin to degrade when too many active calls exist on a link and the amount of bandwidth is oversubscribed. Call admission control operates by rejecting a call when there is inadequate bandwidth and makes it a failed call.

It displays the location name, the number of calls that failed (calls that failed to establish due to lack of bandwidth), and the bandwidth used per location, as a percentage. By default, the table is sorted based on the Bandwidth Used.

The dashlet can be filtered based on utilization type as Peak and audio, video or immersive. By default, it displays the locations where bandwidth utilization has been peak for the last 28 days.

You can filter the details displayed in the detailed analysis based on WAN location, bandwidth used, utilization type, failed calls, or cluster. You can also filter the calls based on locations. Use the Select option to choose a location.

This dashlet will not include the details for the calls processed on VCS.

You can track DSP resource utilization, so that you can optimize it's usage. In this dashlet, you can view the average and minimum DSP utilization for a gateway.

Prerequisite :The gateways must be discovered to populate data in this dashlet.

You can view the details of utilization based on the time period, through the Quick view (launched when you rest your mouse pointer on a value in the Gateway column).

In detailed analysis page, you can filter by custom group or DSP utilization, time period, MTP, Transcoder, cluster, and gateway. The tabular view (pops up when you click the legend) displays the peak, average and minimum DSP usage, and total number of channels used on an hourly basis.

You can create a DSP custom group either using the Device Inventory or from the DSP Detailed Analysis page. In the Detailed Analysis page, click Save Results after applying the required filter parameters. While creating the custom groups, you must ensure that the number of gateways selected must not exceed 100. You can edit or delete the custom groups from the Device Work Center page only.

Note	For Cisco Prime Collaboration Release 11.1 and earlier In MSP mode, the operator user do not have the privilege to create custom group, hence the Save Result button is grayed out.

For Cisco Prime Collaboration Release 11.1 and earlier

This dashlet displays the percentage distribution of calls that belong to the following predefined service categories:

• Good—The Severely Concealed Seconds Ratio (SCSR) value falls below the long call and short call SCSR threshold.

• Acceptable—The SCSR value exceeds or equals the long call and short call SCSR threshold.

• Poor—The SCSR value exceeds the long call and short call SCSR threshold.

• Grade Not Available—Occurs when the corresponding SCSR value is not available.

To configure threshold, see the Overview of Voice Call Grade Settings section in Cisco Prime Collaboration Assurance Guide - Advanced.

In the dashlet view, you can select the chart to be displayed for:

• Graded calls— Good, Acceptable, and Poor calls

• Graded and Ungraded calls—Good, Acceptable, Poor, and Grade Not Available calls

By default, the dashlet view displays the chart for Graded calls.

You can filter the call quality data in the Detailed View based on the call type, call quality, device pool, directory number, IP address, URI, cluster, or location.

The device details for this dashlet are collected from Prime Collaboration inventory and the call quality details for this dashlet are obtained from CDR.

This dashlet includes only the details for the calls processed on Cisco Unified Communications Manager.

For Cisco Prime Collaboration Release 11.1 and earlier

This dashlet lists the top N endpoint types and endpoint models that experience service quality issues. It shows the trend of acceptable and poor quality calls for all IP Phones except Cisco DX650, DX70, DX80, 88xx, and 78xx.

The device information details for this dashlet are gathered from Prime Collaboration inventory and the call quality information for this dashlet is obtained from CMR.

In dashlet view, the formula used for calculating the percentage of the acceptable and poor quality calls is:

Total number of Poor and Acceptable calls of an endpoint model or endpoint type / Total number of calls of same endpoint model or endpoint type * 100.

In detailed view, the formula used for calculating the percentage of the acceptable and poor quality calls is:

One type of call grade of an endpoint model or endpoint type / Total number calls of the same endpoint model or endpoint type * 100.

You can filter the details in the Detailed View based on endpoint type, endpoint model, call type, call grade, calculation (absolute or percentage), call count, call duration, cluster, location, device pool, IP Address, directory number, or URI.

This dashlet includes only the details for the calls processed on Cisco Unified Communications Manager.

Note

The call count data displayed in the detailed view graph will not be in synchronization with the data displayed in the Call Records table. This is because, the detailed view graph aggregates the data at the endpoint level (using CMR) but the Call Records table displays data at call details level (using CDR).

For Cisco Prime Collaboration Release 11.1 and earlier

This dashlet displays the top N locations that have highest number of failed calls (calls that failed to establish due to lack of bandwidth).

This dashlet displays the locations that have highest number of failed calls (calls that failed to establish due to lack of bandwidth). A call is considered good when each endpoint clears the call successfully.

The location information for this dashlet is collected from CDR.

You can filter the details in the Detailed View based on location, call type, call status, call count, call duration, call direction, or cluster.

You can view the Cause Code Analysis report that summarizes user-selected cause codes in the detailed view. Each slice of the pie chart corresponds to a cause code. To see the number of occurrences of the cause code and its percentage in the graph, place the cursor over a slice of the pie chart.

In dashlet view, the formula used to calculate the percentage of failed calls is:

Total number of failed calls in a location / Total number of calls in the same location * 100

This dashlet includes only the details for the calls processed on Cisco Unified Communications Manager.

In detailed view, the formula used for calculating the percentage of failed calls is:

Total number of calls or duration of calls of a particular call status (failed, dropped, completed, attempted / Total number of attempted calls or duration of calls in the same location, call type and call direction * 100

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

For Cisco Prime Collaboration Release 11.1 and earlier

This dashlet lists the users who have experienced most service quality issues. It displays the trend of acceptable and poor audio and video call quality for users.

In the Detailed View, you can filter based on call type (audio or video), call grade (good, acceptable, poor), calculation (absolute or percentage), call count, call duration, cluster, location, device pool, endpoint IP Address, and user.

For Cisco Prime Collaboration Release 11.5 and later

This dashlet lists the total number of poor, acceptable and good calls based on the location. You can also view the overall call experience where the poor calls are represented in red, acceptable calls in orange, good calls in green, and grade not available in yellow.

The location information for this dashlet is collected from the CDR.

You can view the detailed information of the call grade by clicking the See Details at the bottom-right corner of the dashlet. In the Detailed Analysis page, you can filter the call grade data based on the call type, call quality, call count, call duration, calculation (absolute or percentage), device pool, cluster, or location, and individual or merged graphs.

In the detailed view, the formula used for calculating the percentage is:

Total number of calls in a particular call grade(good, acceptable, poor or grade not available) / Total number of calls (good + acceptable + poor + grade not available ) * 100

For Cisco Prime Collaboration Release 11.1 and earlier

You can also configure the threshold range for poor, acceptable and good calls from the Detailed Analysis page. To configure call grade threshold, click Configure in the Detailed Analysis page. For details about configuring the call grade threshold, refer the Overview of Voice Call Grade Settings section in Cisco Prime Collaboration Assurance Guide - Advanced.

For Cisco Prime Collaboration Release 11.5 and later

This dashboard displays the usage trends of the conference resources. This information helps you to effectively plan for future capacity addition or dilution where needed.

Prerequisite : The dashboard data is populated only if there are at least two video endpoints (Multipurpose, Immersive, or Personal TelePresences) in a conference.

This dashboard provides information on locations with highest number of conferences, conference duration (in minutes) and number of participants. The quick view, dashlet view and the detailed view of these dashlets provide data for a selected time period.

You can view the following dashlets from the Conferences dashboard:

You can analyze the conference calls in your site based on call type and call category.

This dashlet displays number of participants, conference count and duration based on call type (adhoc, scheduled) and call category (p2p, multisite and multipoint).

In the detailed view, you can filter based on conference, participants, and duration for conference type and conference category. You can customize your display based on number of participants per conference and duration per conference.

Note	In MSP mode, you cannot filter the dashlet details based on the call type such as adhoc, scheduled and all filters.

Prerequisites for Video Conference Statistics

For Cisco Prime Collaboration Release 12.1 SP2 and later

Note	Ensure to enable Conference Diagnostics to populate the data.

The following are required for Video Conference Statistics:

• Unified CM and Cisco VCS must be in the Managed state.

• Endpoints and controllers, such as MCU must be in the Managed state.

• Ensure to set the visibility of the devices to "Full Visibility" state.

• JTAPI must be configured on Unified Communications Manager. For information on how to enable JTAPI on Unified Communications Manager, see the Configure Devices for Cisco Prime Collaboration Assurance.

• Cisco Prime Collaboration Assurance server must be registered as a feedback server in Cisco VCS.

• For Conference Diagnostics and Audio Phone Feature Synthetic Tests to work, ensure that CUCM is as per the listed version(s) before applying Cisco Prime Collaboration Assurance Service Pack 1 bundle. For more information, see Supported Devices for Cisco Prime Collaboration Assurance for 12.1 Service Pack 1.

You can analyze the number of participants in conference calls and overall conference duration for every location. You can filter these data on call type (adhoc and scheduled) and call category (p2p, multisite and multipoint).

In the detailed view, you can filter based on locations with maximum or minimum conferences. You can view details on conference type (adhoc, scheduled), session type (P2P, Multi-Point, Multi-Site), and clusters within a location.

The Cluster filter does not support Cisco VCS.

Note	In MSP mode, you cannot filter the dashlet details based on the call type such as adhoc, scheduled and all filters.

Prerequisites for Top N Video Conference Locations

For Cisco Prime Collaboration Release 12.1 SP2 and later

Note	Ensure to enable Conference Diagnostics to populate the data.

The following are required for Top N video Conference Locations:

• Unified CM and Cisco VCS must be in the Managed state.

• Endpoints and controllers, such as MCU must be in the Managed state.

• Ensure to set the visibility of the devices to "Full Visibility" state.

• JTAPI must be configured on Unified Communications Manager. For information on how to enable JTAPI on Unified Communications Manager, see the Configure Devices for Cisco Prime Collaboration Assurance.

• Cisco Prime Collaboration Assurance server must be registered as a feedback server in Cisco VCS.

• For Conference Diagnostics and Audio Phone Feature Synthetic Tests to work, ensure that CUCM is as per the listed version(s) before applying Cisco Prime Collaboration Assurance Service Pack 1 bundle. For more information, see Supported Devices for Cisco Prime Collaboration Assurance for 12.1 Service Pack 1.

This dashlet helps you to track the utilization of conferencing devices.

Prerequisite :Conference bridges must be deployed and discovered in device work center.

It also:

• Provides statistics of the peak and average usage of video ports in conferencing devices over a given period of time.

• Helps you see the usage trends of the video ports configured in your network, and manage them better. Provides information on the maximum number of a video ports that is configured on a device and number of ports used.

You can filter the details in the detailed analysis, based on conferencing device, utilization, peak or average ports, utilization percentage, and the device types such as Multipoint Control Unit (MCU), Cisco TelePresence Multipoint Switch (CTMS), or TelePresence Server (TPS). You can also select a Conductor and device information for each device type (these drop-down lists are enabled only if you choose the Select option in the detailed view).

Only the peak and average ports usage filters are applicable in the dashlet, detailed view, and quick view.

For Cisco Prime Collaboration Release 11.5 and later

This dashlet displays the cumulative utilization of the conference bridges for each conductor pool in your network.

The dashlet displays the following details:

You can filter the data based on the utilization type(peak and average) and utilization percentage.

You can also view detailed information of the devices by clicking the See Details link. In the detailed view, you can filter the details of all the devices or selected device based on device type, device, time period, peak or average utilization, utilization percentage and individual or merged graphs.

This dashlet displays the license usage of Unified Contact Center Enterprise.

You can filter the data based on the utilization type such as peak and average. By default, the dashlet displays the list of devices with peak utilization for the last 14 days.

To launch a quick view of the device, click the information icon available against the respective device name. The quick view shows the number of agents logged on for a particular time period, in the form of graph or grid view.

You can also view detailed information of the devices by clicking the See Details link. In the detailed view, you can filter the details of all the devices or selected device based on time period, cluster, capability, device, peak or average utilization, and individual or merged graphs.

This dashlet displays the license usage of CVP call servers.

For Cisco Prime Collaboration Release 11.5 and later

You can view the aggregated license usage of multiple devices. For aggregating devices, see Aggregating Device.

You can filter the data based on the utilization type such as peak and average. By default, the dashlet displays the list of devices with peak utilization for the last 14 days.

To launch a quick view of the device, click the information icon available against the respective device. The quick view shows the ports in use and its utilization for a particular time period, in graph or grid view.

You can also view the detailed information of the devices by clicking the See Details link. In the detailed view, you can filter the details of all the devices, selected or aggregated devices based on time period, utilization range, clusters, devices, peak or average utilization, percentage or absolute values, and individual or merged graphs.