Cisco Prime Collaboration Assurance - Advanced and Analytics Guide, 12.x

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

• Introduction
  • Overview of Cisco Prime Collaboration Assurance and Analytics
  • Concepts
  • Get Started with Cisco Prime Collaboration Assurance
  • Enable Third-Party CA Signed Certificate
  • Manage Licenses
  • Manage Users
  • Manage Customers
  • Manage Domains
  • Configure System Parameters
  • Manage Device Credentials
  • Set Up Clusters
  • Discover Devices
  • Manage Device Groups
  • Manage Inventory
  • Poll Devices
  • Configure Notifications
  • Set Threshold Rules
  • Monitor Alarms and Events
  • Monitor Video Endpoints
  • Monitor Conferences
  • Enable Cisco APIC-EM to Troubleshoot Conference
  • Monitor the Cisco Prime Collaboration Assurance Server
  • Cisco Prime Collaboration Assurance Dashboards
  • Cisco Prime Collaboration Assurance Reports
  • Cisco Prime Collaboration Analytics Dashboards and Reports
  • Diagnostics for Voice Endpoints
  • Troubleshooting Workflow for Video Endpoints
  • Media Path Analysis
  • Collect Logs
  • Analyze Call Signaling
  • Manage Jobs
  • Purge Policies
  • Perform Backup and Restore
  • Set Log Levels
  • Responder Settings
  Find Matches in This Book Log in to Save Content Available Languages Download Options

  Book Title

  Cisco Prime Collaboration Assurance - Advanced and Analytics Guide, 12.x

  Cisco Prime Collaboration Analytics Dashboards and Reports

  • PDF - Complete Book (8.39 MB)PDF - This Chapter (1.4 MB) View with Adobe Reader on a variety of devices

  Results

  Updated: December 20, 2017

  Chapter: Cisco Prime Collaboration Analytics Dashboards and Reports

  Chapter Contents
  • Cisco Prime Collaboration Analytics Dashboards and Reports
  • Cisco Prime Collaboration Analytics Dashboards and Reports
    • Cisco Prime Collaboration Analytics User Roles
    • Global Customer Selection
    • Global Domain Selection
    • User Interface
    • Managing Customer Logo
    • Configure sFTP Server
    • Prerequisites for Data Population in the Cisco Prime Collaboration Analytics Dashlets
    • Technology Adoption
      • Deployment Distribution by Endpoint Model
        • Endpoints Deployment Summary
        • Call Volume by Endpoint Model
        • Call Volume by Endpoint Types
        • Least Used Endpoint Types
        • Video TelePresence Rooms Utilization
        • No Show Video TelePresence Endpoint
          • No Show Video TelePresence Endpoint
          • Top N Callers
          • Top N Dialed Numbers
          • Top N Off-Net Traffic Locations
            • OffNet and OnNet Calls
            • Analytics Group Management
            • Location CAC Bandwidth Utilization
            • Trunk Utilization
            • Busy-Hour Trunk Capacity
              • Calculating Erlang
              • Editing the GOS Properties File
              • Configuring Maximum Capacity for a Trunk or Gateway
              • Importing Trunk Utilization Data for All Clusters
              • Service Experience Distribution
                • Call Quality Analysis
                • Endpoints with Call Quality Issues
                • Call Status For Locations
                • Users with Call Quality Issues
                • Video Conference Analysis
                • Video Conference Statistics
                • Top N Video Conference Locations
                • Conferencing Devices Video Utilization
                • Conductor Bridge Pool Utilization
                • Contact Center Enterprise
                • Customer Voice Portal
                  • Aggregating Devices
                  • Aggregating Devices
                  • Creating Custom Reports

                  Cisco Prime Collaboration Analytics Dashboards and Reports

                  This section explains the following:

                  Cisco Prime Collaboration Analytics Dashboards and Reports

                  Cisco Prime Collaboration Analytics dashboards have time-period dependency. A report cannot be generated until enough time has passed to process data for the time period, specific to that report (daily, weekly, or monthly).

                  For Cisco Prime Collaboration Release 11.0 and earlier

                  You can generate custom reports for any period within the last one year only. And all report data older than one year are purged.

                  Following must be complete to enable data display on the Cisco Prime Collaboration Analytics dashboards for the first time you launch Cisco Prime Collaboration Analytics:

                  • Device Discovery
                  • For Cisco Prime Collaboration Release 11.1 and earlier Session Import
                  • Conference Import
                  • Device Polling

                  Cisco Prime Collaboration Analytics User Roles

                  User roles are used to define the authorizations of tasks that the users can access.

                  The user can be assigned to one of the following roles:

                  • Helpdesk—Does not have access to Analytics menu.
                  • Operator—Can view all the dashboards, but do not have access to edit and delete scheduled reports. Also, operator users does not have any configuration capabilities.
                  • Report viewer—Have access to all the dashboards except Capacity Analysis, License Usage, and My Dashboard. Report viewer cannot schedule reports and do not have access to the Scheduled Reports menu.
                  • Network Administrator, System Administrator and Super Administrator—Can access all the dashboards and can perform all the configuration tasks.

                  If you have deployed Cisco Prime Collaboration Assurance in MSP Mode, you do not have access to Custom Report Generator menu.

                  For more information about Cisco Prime Collaboration Assurance roles and its capabilities refer Cisco Prime Collaboration Assurance-Advanced User Roles in Cisco Prime Collaboration Assurance Advanced Guide.

                  User Roles and Tasks lists the Cisco Prime Collaboration Analytics user roles and tasks they are mapped to.

                  Global Customer Selection

                  For Cisco Prime Collaboration Release 11.5 and later

                  This section applies only if you have deployed Cisco Prime Collaboration Assurance in MSP mode.

                  On the Cisco Prime Collaboration Assurance home page, you can select customers. To select customers, click the settings icon at the top right, and choose Customer. From the Customer dialogbox select the required customer names and click Ok. Based on the customer selection, data is displayed in analytics dashboards.

                  For more information on global customer selection refer Global Customer Selection section in Cisco Prime Collaboration Assurance Advanced Guide.

                  Global Domain Selection

                  For Cisco Prime Collaboration Release 11.5 and later

                  This section applies only if you have deployed Cisco Prime Collaboration Assurance in Enterprise mode.

                  On the Cisco Prime Collaboration Assurance home page, you can select domain. Based on the domain selection, data is displayed in analytics dashboards.

                  For more information on global domain selection refer Global Assurance Domain Selection section in Cisco Prime Collaboration Assurance Advanced Guide.

                  User Interface

                  You can use the Prime Collaboration Analytics user interface (UI),

                  • To view the dashlet details in chart mode or grid mode
                  • To export data
                  • To change the chart types
                  • To view the detailed view or quick view - These also let you choose chart or grid display.
                  • To view data tips for the corresponding pie wedges or bar wedges
                  • To maximize the dashlet

                  You can filter the data displayed based on Cluster and Duration in the Filters pane.

                  You can maximize the dashlet by clicking the maximize icon at the top right corner of the dashlet. When you click the maximize icon, the dashlet opens in a new tab.

                  

                  By default, the layout template for all Analytics dashlets is set as 50/50. In order to gain an optimum view, we do not recommend you to change this setting. However, if you wish to set a custom layout, click icon at the top right, choose Layout Template and select your desired layout.

                  Quick View

                  You can click a pie wedge or a bar wedge on the chart to launch the quick view of the corresponding endpoint. The quick view displays graph only for the selected endpoint. Similar to the dashlet view, quick view also allows you:

                  • To view the dashlet details in chart mode or grid mode
                  • To change the chart types
                  • To export data
                  • To launch the detailed view

                  Global Filter Option

                  Filter option is available at the top left of the UI for each dashlet. You can filter the data displayed for all dashlets based on duration (for example, last one week, one month and so on) and other attributes based on the dashlet type; for example call types (audio or video) in Traffic Analysis dashboards.

                  For Cisco Prime Collaboration Release 11.1 and earlier

                  Global filters are not applicable for the Metrics in the Technology Adoption dashboard.

                  Detailed Analysis

                  Prime Collaboration Analytics provides a detailed analysis (click See Details at the bottom-right) of each dashlet (endpoints, devices, technology usage. ).

                  The Detailed Analysis page consists of Metrics and Filter pane, and Graph pane:

                  Metrics and Filter pane- You can filter data based on time period, call direction, call type, call status, calculation (of absolute values or percentage), call count, call duration, endpoint type, endpoint model, deployment status, cluster, or location/device pool.

                  Note

                  For all dashlets in Capacity Analysis, you can filter the results using custom group, utilization, individual graphs(display each entity one below the other and is limited to 20 graphs per page) or merged graphs (display all entities in a single graph). You can sync custom dates in all graphs by selecting 'Keep selected time span in sync across all graphs'.

                  The Export option, available after the Metrics and Filter pane, at the top-right, allows you to schedule the export. You can generate reports for a dashlet according to your scheduling preferences, and download or send them to the preferred e-mail ID (You can even send the failure notification if the report generation is unsuccessful). You can also send the scheduled reports to the configured sFTP server. To configure sFTP server, see Configuring sFTP Server . The data from charts can be exported in CSV format or PDF, and the data from tabular-based dashlet can be exported in CSV format.

                  Graph pane- The graph displayed is based on values set for each parameter in Filter pane. The slider below the graph displays the desired time range (set in the Filter pane), you can drag the slider to zoom into a particular time period (narrow the time period) or alter values in x-axis and y-axis, resulting in the data being filtered for that period.

                  Tabular view- Prime Collaboration Analytics also provides option to view data in a tabular format that provides in-depth/detailed analysis of the data, such as detailed call record, hourly network usages, endpoint information and so on. Tabular view, in the Detailed Analysis, pops-up when you click legends/series displayed below the slider, or when you double-click at any point on the graph. You can also filter the data in the table or export it.

                  • In detailed view, dashlets with Cisco VCS registered endpoints display the device pool and location, whenever the sub-zones are not configured. The Cisco VCS cluster or sub-zone details are displayed in the following dashlets:
                    • All dashlets in Traffic Analysis.
                    • All dashlets in Service Experience.
                    • —All dashlets except for Deployment Distribution by Endpoint Model Endpoints Deployment Summary in Technology Adoption.
                    • Least Used Endpoint Types (Asset Usage).

                    If the sub-zones are not configured in Cisco VCS, location, codec, and device pool details are displayed as VCS_Unknown. Impairment details are not applicable for Cisco VCS registered calls and is displayed as zero in the detailed view.

                    • The IP address must be in the format x.x.x.x, and the range can be between 0.0.0.0 and 255.255.255.255, excluding these two values. It must not contain any special characters.
                    • For Directory Numbers, only the following special characters are allowed: +, @, and . (period).

                    The Quick Tips help you customize the graphical view for your convenience.

                    Schedule Report, Export and Import

                    The drop-down icon available in the bottom-left, of the each dashlet, provides you with an option to choose among print, export and scheduling the report. You can generate reports for a dashlet according to your scheduling preferences, and download or send them to the preferred e-mail ID (You can even send the failure notification if the report generation is unsuccessful). You can also send the scheduled reports to the configured sFTP server. To configure sFTP server, see Configuring sFTP Server .

                    When you schedule a reporting job, you can only select the start date and not the start time. Prime Collaboration schedules the job through the Job Scheduler. A periodic job runs every 60 minutes to check and execute the reports created newly on the current day, irrespective of the recurrence interval. By default any new report created on the current day with recurrence interval only once is executed again at 10.59PM in the respective time zone.

                    All the scheduled recurrent reports(daily, weekly, and monthly) runs between 5Am-8Am in the respective time zone everyday based on the recurrence interval. These reports are prioritized as low and high based on the time taken to run the reports. The reports that take more time is categorized as low priority and those which take less time to run as high priority reports. The high priority reports are executed first in a serial fashion followed by the low priority reports. Low priority reports are run in batches of 4.

                    The data from charts can be exported in CSV format or PDF, and the data from tabular-based dashlet can be exported in CSV format. You can also specify the number of instances that can be saved per report. After the number of instances reach the specified limit, the first report that was saved in the chronological order will be purged.

                    1. Data Purging in Bottom Table: During purging, the Bottom Table (BT) data will be purged after 35 days but the history of execution will have the exact number of times the Scheduled Report has been generated.
                    2. Custom Interval in Scheduled Reports: For the custom interval, if the Scheduled Report is generated, a report will be generated for the same interval when it is scheduled.

                    Note	Hence, it is recommended not to schedule a report for the custom interval.

                    Managing Customer Logo

                    For Cisco Prime Collaboration Release 11.5 and later

                    If you have deployed Cisco Prime Collaboration Analytics in MSP mode, you can assign a logo to the customer. These logos are displayed in the reports generated from the dashlet(scheduled or exported). The generated report will contain the logo of the customer selected in the global customer selection.

                    Note	The customer logo will be available only in the PDF format of the report.

                    You can upload, delete, and reset the logo of the customer.

                    To upload customer logo:

                    Before you begin

                    You must have administrator privilege to perform this task.

                    Procedure

                    Choose Analytics Administration > Upload Customer Logo.

                    Choose the appropriate customer name.

                    Click Browse and select the appropriate image.

                    You can upload images only in the format .jpg, .jpeg, .bmp, or .gif.

                    Click Submit to save the image as customer logo.

                    To delete the logo, click Delete Logo. You can click Reset to update the logo.

                    Configure sFTP Server

                    To configure sFTP server:

                    Before you begin

                    • The user < userid >is available in the sFTP server.
                    • The folder /< path >/ < userid >is available in the sFTP server and accessible only by that specific user < userid >and the administrator.

                    Procedure

                    Choose Analytics Administration > sFTP Settings .

                    Enter the required details on the sFTP Settings page. Refer Table 1 for field description.

                    Click Test Connection to check the connectivity to the sFTP server.

                    In MSP mode, using test connection you can verify whether the folder /< path >/ < userid >is available in the sFTP server.

                    Upon successful connection, click Save.

                    For Cisco Prime Collaboration Release 11.1 and earlier

                    In MSP mode, the operator users do not have access to Analytics Administration menu and cannot configure sFTP server.

                    sFTP Server(IP Address)

                    IP address of the sFTP server where the scheduled reports must be saved.

                    Port number of the sFTP server.

                    Directory path in the sFTP server where the scheduled reports must be saved.

                    If you have deployed Cisco Prime Collaboration Analytics in MSP mode, the reports are saved in the location /< path >/ < userid >and if you have deployed Cisco Prime Collaboration Analytics in enterprise mode, the reports are saved in the location /< path >.

                    Username for accessing the sFTP server.

                    Password for accessing the sFTP server.

                    Prerequisites for Data Population in the Cisco Prime Collaboration Analytics Dashlets

                    Ensure that the following prerequisites are met for data to be populated in the Cisco Prime Collaboration Analytics dashlets.

                    • Endpoints registered with Unified CM and Cisco VCS are discovered ( Inventory ).
                    • CDR records for Unified CM and Cisco VCS registered endpoints is available ( Reports > CDR & CMR Reports ).
                    • Confirm data collection for the registered Unified CM in Alarms & Events Administration > CDR Source Settings > Manage Call Quality Data Sources .
                    • Verify data population by setting the global filters empty in the respective dashboard.
                    • Analytics uses historical data collected for a selected period of time. While selecting the filters for days, weeks, and months, the data is displayed excluding the current day, week, and month.

                    Technology Adoption

                    Use the Technology Adoption dashboard to validate technology investments made so far. This dashboard also provides key decision-support metrics that you can use in future investment decisions.

                    Prerequisite : The endpoints registered to Unified CM and Cisco VCS should be discovered.

                    Data Source : 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.

                    All dashlets in this dashboard display data for endpoints registered with Unified CM and VCS.

                    The deployment details for the Unknown endpoints will not be displayed in the Technology Adoption dashlets.

                    The Technology Adoption dashboard displays metrics that provide a quick update and a snapshot view of audio endpoints and video endpoints deployed in your organization.

                    The Technology Adoption dashboard displays the following metrics:

                    • Total video endpoints in use
                    • Change in the number of endpoints in the last 1 month
                    • Percentage of video endpoints deployed
                    • Total duration of video calls
                    • Change in the duration of video calls in the last 12 weeks
                    • Trend of video call usage
                    • Total number of audio endpoints
                    • Change in the number of endpoints in the last 1 month
                    • Percentage of audio endpoints deployed
                    • Total duration of audio calls
                    • Change in the duration of audio calls in the last 12 weeks.

                    Use the drop-down list to choose a time period for which to view metrics.

                    The following dashlets are available in the Technology Adoption dashboard:

                    Deployment Distribution by Endpoint Model

                    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.

                    Endpoints Deployment Summary

                    For Cisco Prime Collaboration Release 11.5 and later

                    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 Cisco Prime Collaboration Assurance 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 Cisco Prime Collaboration Assurance 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.

                    Call Distribution by Endpoint Model

                    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.

                    Call Volume by Endpoint Model

                    For Cisco Prime Collaboration Release 11.5 and later

                    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.

                    Call Distribution by Endpoint Types

                    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.

                    Call Volume by Endpoint Types

                    For Cisco Prime Collaboration Release 11.5 and later

                    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.

                    Technology Usage

                    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.

                    Asset Usage

                    This dashboard helps you to track the asset usage. For example, it helps you to determine if endpoints have been effectively allocated and used, and so on.

                    Prerequisite : The endpoints registered to Unified CM and Cisco VCS should be discovered.

                    Data Source : 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.

                    The following dashlets are available in the Asset Usage dashboard:.

                    Least Used Endpoint Types

                    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.

                    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.

                    Video TelePresence Rooms Utilization

                    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.

                    No Show Video TelePresence Endpoint

                    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.

                    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

                    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.

                    No Show Video TelePresence Endpoint

                    For Cisco Prime Collaboration Release 11.1 and later

                    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.

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

                    Traffic Analysis

                    The Traffic Analysis dashboard displays the technology usage by various users, departments, or business units in the organization. It helps you to plan and allocate business costs across various organizational units or departments.

                    Data Source : Call details of the dashlets in Traffic Analysis dashboard are obtained from CDR that the Cisco Unified Communications Manager generates.

                    In Detail View, the filters are based on Top N. In Bottom Table all the records are displayed based on other filter conditions selected in Detail View page. However, the database only holds raw data for 35 days. The Bottom Table displays the data accordingly.

                    The following dashlets are available in the Traffic Analysis dashboard:

                    Top N Callers

                    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.

                    Top N Dialed Numbers

                    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.

                    Top N Off-Net Traffic Locations

                    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.

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

                    OffNet and OnNet Calls

                    Calls within the Cisco Unified CM (private network) are termed as OnNet calls. For example, a call from an internal cisco IP phone to another internal IP phone is an OnNet call. OnNet calls can be routed over intercluster trunks (ICT) or Session Initiation Protocol (SIP) trunks to integrate with remote Cisco Unified CM clusters or third-party SIP vendor equipment.

                    OffNet calls are normally the calls that are routed outside the private telephony system to the PSTN. Most OffNet calls are routed across gateways to the PSTN. A call can also be categorized as OffNet when at least one endpoint is a trunk or a gateway, and when one of the following holds good of the endpoint.

                    • The Call Classification parameter is set to OffNet in the gateway configuration or the trunk configuration in Unified Communications Manager (Administration).
                    • Call Classification parameter is set to System default in the gateway or trunk configuration.
                    • System default service parameter is set to OffNet.
                    • The endpoint is an analog gateway.

                    Any call that does not meet the criteria for an OffNet call is considered to be an OnNet call.

                    By default, all route patterns and all calls to or from a gateway are classified as OffNet.

                    Top N Call Traffic Locations

                    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.

                    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.

                    Call Traffic Analysis

                    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.

                    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.

                    Capacity Analysis

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

                    For all the dashlets in Capacity Analysis dashboard, the data for the current day will be processed only on the following day. Therefore, the dashlets display the data for the current day as zero.

                    Data Source :The utilization data for this dashboard is obtained from the voice utilization polled data.

                    The quick view, dashlet view and the detailed view of these dashlets provide data for the time period for which the filter has been applied.

                    You can see the details of SIP Trunk types supported in the capacity analysis dashboard in the following table:

                    SIP Trunk Type

                    % Utilization Report

                    Busy-hour Trunk Traffic Report

                    SIP Trunk terminated at Cisco CUBE

                    Polling the CUBE directly

                    UCM logical SIP trunk (ICT, Trunk to WebEx, etc)

                    RTMT UCM SIP Performance Counter

                    SIP Trunk terminated at non-Cisco border element (ACME, etc)

                    RTMT UCM SIP Performance Counter

                    You can view the following dashlets from the Capacity Analysis dashboard:

                    Analytics Group Management

                    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.

                    • 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).

                    Location CAC Bandwidth Utilization

                    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.

                    Trunk Utilization

                    This dashlet helps you to identify the trunks which are most heavily or least utilized. Trunk utilization information is obtained from voice utilization polled data. This dashlet displays the maximum concurrent calls (configured data), concurrent calls (data used), trunk type (protocol of the trunk), and the utilization in percentage of each trunk.

                    For Cisco Prime Collaboration Release 11.6 and later

                    As an enhancement to the current feature, utilization of CUCM SIP trunks is also included from 11.6.

                    The utilization is displayed in terms of audio and video utilization of the trunk, when the user hovers on the utilization column for each CUCM SIP trunk in dashlet view. In the quick and detailed view, the same information is displayed in the chart and grid view as well. In chart view, the utilization is displayed against time. In grid view it is shown as separate columns for each day/month/week as applicable.

                    The utilization of each CUCM SIP trunk is calculated as:

                    (Total calls / Total configured calls)*100

                    The audio utilization of each CUCM SIP trunk is calculated as:

                    (Audio calls / Configured audio calls)*100

                    The video utilization of each CUCM SIP trunk is calculated as:

                    (Video calls / Configured video calls)*100

                    Sum of audio and video utilization in percentage will be equal to total utilization of the trunk.

                    • Trunk groups that are created under Analytics Administration > Group Management page are listed on the dashlet to enable the user to view the utilization of trunks in that group.
                    • You must update the maximum capacity for CUCM-SIP trunks for the first time when the trunks are configured. The utilization will be displayed after the capacity is set on the GUI. You can either update the maximum capacity for CUCM-SIP trunks using the Utilization Monitor > UCM SIP Trunk Utilization > Set Maximum Capacity link (or) By clicking missing trunk in the trunk utilization dashlet (on the top-left corner of the dashlet below the filters) and click CUCM SIP Trunk Max Concurrent Calls link (in Analytics).

                    You can filter the details displayed in the detailed view of the trunk utilization based on trunk, calculation type, calculation mode, custom groups (this drop-down list is enabled only if you choose the Custom Groups option in the detailed view), or when the threshold level is above or below the selected percentage of utilization (this drop-down list is enabled only if you choose the Utilization option in the detailed view) or cluster (this drop-down list is enabled only if you choose the Utilization option in the detailed view).

                    Click Max Concurrent Call to specify the maximum number of concurrent calls that can go through the SIP Trunk in Cisco Prime Collaboration Analytics.

                    For other trunks, such as MGCP, inter-cluster and so on, the data is collected through polled data.

                    For non-CUCM trunks, audio and video utilization is not available and hence it is shown as NA in the corresponding columns of the bottom table and in exported CSV file.

                    Busy-Hour Trunk Capacity

                    This dashlet helps you identify the trunks experiencing high average bouncing busy hour (ABBH) traffic. ABBH is calculated by analyzing the traffic load on a switching system during the peak hour of each day, over a certain period (typically one week), and then calculating the average for the time period.

                    Prerequisite :The maximum capacity for the CDR utilization trunks must be configured to see the available capacity in this dashlets. To configure maximum capacity for the CDR utilization trunks click Missing Busy-Hour Trunk? at the top left corner of the dashlet, below the filters.

                    You can also view the following capacity details of the trunk groups or route groups:

                    • Available Capacity
                    • Average Bouncing Busy Hour Traffic
                    • Maximum Bouncing Busy Hour Traffic

                    The maximum capacity required for a resource is calculated from the maximum BBH value, represented in erlangs. Maximum BBH is the maximum Bouncing Busy Hour value of a particular trunk for the selected time period. BBH is the peak value of that day.

                    The average capacity required is calculated from the ABBH value. Average capacity, here, means the minimum capacity required for a resource to maintain good traffic flow. ABBH is the average of all BBH values of a particular trunk or a route group for the selected time period.

                    Note

                    ABBH value will be calculated only for the working days, for the selected time period. For example, if you have specified the time period as one week, Analytics will first calculate the ABBH for seven days. The days that have BBH value less than 25 percentage of ABBH are considered as non-working days. Analytics ignores the non-working days and calculates the ABBH value for all the other days of that week.

                    By default, Analytics uses the Grade of Service (GOS) value as 0.01 to calculate the average required capacity and maximum required capacity. To calculate the average and maximum required capacity for a different GOS (for example, 0.1, 0.001 and so on), you must edit the gos.properties file. See Editing the GOS Properties Filefor details .

                    BBH of the current day is calculated only at the end of the day and you can see it only on the next day. There is no Inbound or Outbound traffic for ABBH. It is applicable only for BBH.

                    You can filter the details displayed in the detailed view based on trunk , traffic type, direction, bandwidth used, or cluster (this drop-down list is enabled only if you choose the Select option in the detailed view). When you select a cluster, all the devices for that cluster gets listed, regardless of whether the devices are maximum or least utilized.

                    You need to configure the maximum capacity for the CDR utilization trunks in order to see the available capacity in the dashlets. If the maximum capacity for the CDR trunks is not configured or zero, the data for these trunks will not be shown in the dashlet.

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

                    Calculating Erlang

                    An erlang is used to describe the total traffic volume of one hour. For example, If a group of users made 30 calls in one hour, and each call had an average call duration of 5 minutes, then the number of erlangs this represents is worked out as follows:

                    Minutes of traffic in the hour = number of calls x duration (30*5) = 150

                    Hours of traffic in the hour = 150/60 = 2.5

                    Therefore, the total traffic = 2.5 Erlangs.

                    Erlang traffic measurements are made in order to understand traffic patterns within your voice networks. It can also be used to work out the number of lines that will be required between a telephone system and a central office (PSTN exchange lines), or between multiple network locations.

                    Editing the GOS Properties File

                    Analytics uses the Grade of Service (GOS) value as 0.01 to calculate the average required capacity and maximum required capacity. To calculate the average and maximum required capacity for a different GOS (for example, 0.1, 0.001 and so on), you must edit the GOS properties file:

                    Procedure

                    Log in to the Prime Collaboration Assurance server with the administrator privilege.

                    Open a new tab in browser and enter the URL this link https:///emsam/applications/emsam/PCDiagnostics/fileEditor.jsp.

                    Where, pc-service-ip is the Prime Collaboration Assurance server IP address.

                    Choose the following:

                    1. In the Location drop-down list, /opt/emms/emsam/advance_reporting/conf/.
                    2. In the File Type drop-down list, properties.
                    3. In the Files drop-down list, gos.properties.

                    Edit the gos value and click Save .

                    Configuring Maximum Capacity for a Trunk or Gateway

                    To configure the maximum capacity for a trunk or gateway:

                    In MSP mode, the operator users do not have access to Analytics Administration menu, so you cannot configure the maximum capacity for a trunk or gateway.

                    Procedure

                    Choose Analytics Administration > Trunk Traffic Max Capacity Settings .

                    From the drop-down list, select the Cisco Unified CM cluster that you want to configure.

                    Select a gateway or trunk type.

                    Click Configure Maximum Capacity and make the appropriate entries.

                    Click Apply , and then click Close.

                    Importing Trunk Utilization Data for All Clusters

                    To import the trunk utilization data for all Cisco Unified CM clusters:

                    In MSP mode, the operator users do not have access to Analytics Administration menu, so you cannot import the trunk utilization.

                    Procedure

                    Choose Analytics Administration > Trunk Traffic Max Capacity Settings .

                    Click Bulk Export .

                    In the Export Trunk Configuration window, click Export to accept the default named export CSV file.

                    Open the CSV file and edit the data as needed.

                    All the gateways and trunks will be listed in the file. You just need to enter the values in the file.

                    Click Bulk Import.

                    Browse to the location of the CSV file, and then click Import .

                    Route Group/Trunk Group Utilization

                    For Cisco Prime Collaboration Release 11.6 and later

                    This dashlet displays information about the most utilized route groups and trunk groups in terms of channel usage. The utilization data for this dashlet is obtained from the voice utilization polled data. The dashlets details include Route Group/Trunk Group, Concurrent Calls (data used), Max Concurrent Calls (configured data), and the utilization in percentage for each route/trunk.

                    Prerequisite :

                    • To view the aggregated data, you must associate the trunks to a route group, by clicking Missing Route Group/Trunk Group? on the top-left corner of the dashlet below the filters..
                    • To view data for user-defined trunk groups, you must create custom groups, by clicking Missing Route Group/Trunk Group? on the top-left corner of the dashlet below the filters.
                    • For the SIP trunk data to be populated, you must configure the maximum capacity for SIP trunks, by clicking Missing Route Group/Trunk Group? on the top-left corner of the dashlet below the filters.. For other trunks, such as MGCP, inter-cluster and so on, the data is collected through polled data.
                    • If you want to view data for the custom groups, you must define these groups using Analytics Administration > Group Management .

                    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 28 days.

                    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, peak or average utilization, percentage or absolute values, and individual or merged graphs.

                    Busy-Hour Route-Group Capacity

                    This dashlet helps you identify the route groups experiencing high, average bouncing busy hour (ABBH) traffic. ABBH is calculated by analyzing the traffic load on a switching system during the peak hour of each day, over a certain period (typically one week), and then calculating the average for the time period.

                    Prerequisite :The maximum capacity for the CDR utilization trunks must be configured to see the available capacity in this dashlets. To configure maximum capacity for the CDR utilization trunks click Missing Busy-Hour Route Group? at the top left corner of the dashlet, below the filters.

                    You can also view the following capacity details of the trunk groups or route groups:

                    • Available Capacity
                    • Average Bouncing Busy Hour Traffic
                    • Maximum Bouncing Busy Hour Traffic

                    The maximum capacity required for a resource is calculated from the maximum BBH value, represented in erlangs. Maximum BBH is the maximum Bouncing Busy Hour value of a particular route group for the selected time period. BBH is the peak value of that day.

                    The average capacity required is calculated from the ABBH value. Average capacity, here, means the minimum capacity required for a resource to maintain good traffic flow. ABBH is the average of all BBH values of a particular route group for the selected time period.

                    Note

                    ABBH value will be calculated only for the working days, for the selected time period. For example, if you have specified the time period as one week, Analytics will first calculate the ABBH for seven days. The days that have BBH value less than 25 percentage of ABBH are considered as non-working days. Analytics ignores the non-working days and calculates the ABBH value for all the other days of that week.

                    By default, Analytics uses the Grade of Service value as 0.01 to calculate the average required capacity and maximum required capacity. To calculate the average and maximum required capacity for a different GOS (for example, 0.1, 0.001 and so on) you must edit the gos.properties file. See Editing the GOS Properties Filefor details .

                    BBH of the current day is calculated only at the end of the day and you can see it only on the next day. There is no Inbound or Outbound traffic for ABBH. It is applicable only for BBH.

                    In the detailed analysis page, you can filter the details displayed based on route group, traffic type, direction, bandwidth used, or cluster (this drop-down list is enabled only if you choose the Select option in the detailed view). When you select a cluster, all the devices for that cluster gets listed, regardless of whether the devices are maximum or least utilized.

                    In addition, you can view the traffic type and direction of the associated trunks for a route group when you select Show Trunks . The tabular view (pops up when the legend is clicked) also displays associated trunks details for a route group.

                    You need to configure the maximum capacity for the CDR utilization trunks in order to see the available capacity in the dashlets. If the maximum capacity for the CDR trunks is not configured or zero, the data for these trunks will not be shown in the dashlet.

                    To configure maximum capacity for CDR trunks, see Configuring Maximum Capacity for a Trunk or Gateway.

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

                    DSP Utilization

                    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.

                    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.

                    Service Experience

                    This dashboard helps you to analyze the service quality distribution and traffic trends based on number of calls, location, or call duration.

                    Prerequisite :The Call Measure Records(CMR) must provide either Mean Opinion Score (MOS) or Severely Concealed Seconds Ratio (SCSR) values.

                    Data Source :The device details for this dashlet is collected from Prime Collaboration inventory and the call quality details for this dashlet is obtained from CDR.

                    In addition to other filters in the detailed analysis view, for each dashlet of the Service Experience dashboard, you can also filter the results based on a selected user (specify the userid in the User field). The tabular view (pops-up when you click legends/series displayed below the slider, or when you double-click at any point on the graph) also has the user field. The same results, containing details of a selected user, can be also be exported.

                    Issue found:

                    Detail view page for "Users with Call Quality Issues" shows 'No data'.

                    Work around provided:

                    You can find the Detail view page from Quick view shows data.

                    1. Login to Prime Collaboration Assurance server address 10.197.94.104 with the username globaladmin and password Ecmbu!23.
                    2. Go to 'Analytics -> Service Experience'
                    3. Observe the data available in 'Users with Call Quality Issues' dashlet .
                    4. Click on 'See Details'.
                    5. Detail view page shows 'No data'.

                    Service Experience Distribution

                    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.

                    Call Quality Analysis

                    For Cisco Prime Collaboration Release 11.5 and later

                    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 Thresholds, see Configuring Global Thresholds 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.

                    Endpoints with Service Quality Issues

                    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.

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

                    Endpoints with Call Quality Issues

                    For Cisco Prime Collaboration Release 11.5 and later

                    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.

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

                    Top N Call Failure Locations

                    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.

                    Call Status For Locations

                    For Cisco Prime Collaboration Release 11.5 and later

                    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.

                    Users with Service Quality Issues

                    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.

                    Users with Call Quality Issues

                    For Cisco Prime Collaboration Release 11.5 and later

                    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.

                    Call Grade for Locations

                    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.

                    Video Conferences

                    For Cisco Prime Collaboration Release 11.1 and earlier

                    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:

                    Video Conference Analysis

                    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:

                    Video Conference Statistics

                    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

                    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.

                    Top N Video Conference Locations

                    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

                    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.

                    Conferencing Devices Video Utilization

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

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

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

                    Conductor Bridge Pool Utilization

                    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:

                    • Pool Name—Name of the conference bridge pool
                    • Video Ports/Screen License Utilization—Number of video ports/screen licenses currently in use
                    • Max Video Ports/Screen License Utilization—Number of video ports/screen licenses available.
                    • Utilization—Percentage of video ports utilized from maximum available video ports.
                    • Conference Bridge Type
                    • Conductor Name—Name of the conductor that manages the conference bridge pool.

                    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.

                    UC System Performance

                    This dashboard helps you analyze system performance, based on CPU and Memory for the UC applications. You can use these trends to determine UC applications that are consuming high CPU/memory consistently over a period of time.

                    Prerequisite :The endpoints registered to Unified CM and Cisco VCS should be discovered.

                    Data Source :The performance utilization details for this dashboard is obtained from RTMT polled data

                    The quick view, dashlet view and the detailed view of these dashlets provide data for the time period for which the filter has been applied.

                    The following dashlets are available:

                    CPU Utilization - This dashlet displays the CPU utilization data (as a percentage) in terms of peak, average, and minimum utilization, for each device.

                    Memory Utilization - This dashlet displays the total memory and used memory (peak, average, and minimum) in terms of MB terms. Also, it displays the memory utilization as a percentage in terms of peak, average, and minimum utilization.

                    • These dashlets display a maximum of 25 rows at an instant.
                    • Also, they display data (peak, average, and minimum) as a sparkline trend for last 2 days.

                    License Usage

                    This dashboard helps you to track the license usage of applications such as Unified Contact Center Enterprise (UCCE) and Cisco Voice Portal (CVP).

                    Prerequisite : Contact Center Assurance License is required to populate data in the license usage dashboard.

                    Data Source : The license usage details for this dashboard are obtained from voice utilization polled data.

                    The following dashlets are available in License Usage dashboard:

                    Contact Center Enterprise

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

                    • Device—Device name
                    • Capability—Capability of the device such as router or peripheral gateway
                    • Instance Name—Name of the instance
                    • Agents logged on—Number of contact center agents currently logged on

                    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.

                    Customer Voice Portal

                    This dashlet displays the license usage of CVP call servers.

                    • Device—Device name.
                    • For Cisco Prime Collaboration Release 11.1 and earlier Type—Device Type. For aggregated device, the device type is Multidevice. For Cisco Prime Collaboration Release 11.5 and later Type—Device Type. For aggregated device, the device type is Device Group.
                    • Port in use—Number of port licenses currently in use.
                    • Max ports—Number of port licenses available for the processing of new calls. If there is any change in the ports utilized in the selected period, then minimum- maximum available port range is displayed.
                    • Utilization (%)—Percentage of ports utilized from maximum available ports.
                    • Port request denied—Number of port license checkout requests that were denied since the start of the system.

                    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.

                    Aggregating Devices

                    For Cisco Prime Collaboration Release 11.1 and earlier

                    You can select multiple CVP devices, and view the aggregated license usage of these devices. To select the devices for aggregation:

                    Procedure

                    Click the device in the first row. The Aggregated Devices dialog box appears.

                    In the Aggregated Devices dialog box, edit the Name as required.

                    Select the required devices.

                    Click Save & Close.

                    You can view the aggregated device values populated in the first row of the dashlet.

                    Aggregating Devices

                    For Cisco Prime Collaboration Release 11.5 and later

                    You can select multiple CVP devices, and view the aggregated license usage of these devices.

                    You must have administrator privilege to perform this task.

                    To select the devices for aggregation:

                    Procedure

                    Click CVP Aggregation Configuration on the top left corner of Customer Voice Portal dashlet.

                    In the CVP Aggregation Configuration page, based on the mode of deployment, do the following:

                    • In Enterprise mode, select the devices for aggregation as required.
                    • In MSP mode, you can aggregate devices for individual customers as follows:
                      1. Click the customer name. The devices associated with the customer are displayed.
                      2. From the displayed devices, select the required devices for aggregation.
                      3. Enter a name for the aggregated devices.

                    Click Save.

                    You can find the aggregated device values populated in the Customer Voice Portal dashlet with the device type as Device Group.

                    Video Communication Server / Expressway

                    For Cisco Prime Collaboration Release 11.6 and later

                    This dashlet displays the license usage of VCS standalone or cluster servers.

                    You can view the Traversal and Non-Traversal license usage for all VCS clusters, individual VCS servers in a cluster, standalone VCS servers, Cisco Expressway-Core, Cisco Expressway-Edge, or a Cisco VCS with Cisco Collaboration Edge or Core. For Cisco Expressway-Core and Cisco Expressway-Edge clusters, you can also view the peak number of calls since last restart in the Expressway Peak Concurrent column.

                    • Cluster/Standalone Server
                    • Peak Traversal
                    • Peak Non-Traversal
                    • Peak Registration
                    • Expressway Peak Concurrent

                    When the device operates in expressway mode, you can view valid Expressway Peak Concurrent value. If the device operates in VCS mode, the Expressway Peak Concurrent value will be displayed as not applicable.

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

                    To launch a quick view of the device, click the information icon available against the respective device. The quick view shows the used and utilization information for Peak Traversal, Peak Non-Traversal, and Peak Registration 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 devices based on time period, peak or average utilization, percentage or absolute values, and individual or merged graphs.

                    My Dashboard

                    You can customize dashboards on My Dashboard page and add existing dashlets to it.

                    You can also do the following:

                    • Create new dashboards.
                    • Add existing dashlets.
                    • Move dashlets around a dashboard by dragging and dropping them.
                    • Edit and delete dashlets.
                    • Add global filters.
                    • Change layout template. By default, the layout template for My Dashboard is set as 100.

                    To add a new dashboard:

                    Procedure

                    Click the Settings icon on the top-right corner of the My Dashboard page, and then click Add New Dashboard.

                    Enter a name in the text box provided, and click Apply.

                    Click Add Dashlet(s).

                    Click Add next to the dashlet you want to add.

                    Custom Report

                    The Prime Collaboration Analytics custom reports are based on the OLAP cube technique. When you select a report, you have the flexibility of choosing the required attributes and values to generate an analytics report.

                    The attributes include elements such as DialledNumber, Date, Time, Cluster, MeetingCategory, and so on; the values, which represents the numeric value includes count, duration, and so on. For detailed description on attributes and values for analytics cubes, see Prime Collaboration Analytics Custom Report – Attributes and Values page.

                    You can generate Analytics custom reports for:

                    • Caller Call Status and Callee Call Status: Displays call status, such as dropped, failed and so on for the originated or destination endpoint.
                    • Caller Call Grade and Callee Call Grade: Displays call quality data, such as No MOS, poor call, short call, and so on for the originated or destination endpoint. It also provides details on the call grades (using the CMR records) for the originated or destination EP.
                    • Caller Call Class and Callee Call Class: Displays call traffic types, such as external, internal, conference, and so on for the originated or endpoint information. It also provides the onnet and offnet call indicator.
                    • Caller Call Cause Code and Callee Call Cause Code: Displays call termination code, such as temporary failure (41), Destination out of order (27), no user responding (18), and so on for the originated or destination endpoint information.
                    • Location CAC Bandwidth Utilization: Displays CAC bandwidth usage details along with the number of calls failed because of less bandwidth.
                    • Conferencing Devices Video Utilization: Displays channel utilization for conferencing devices, such as Cisco MCU, Cisco TPS.
                    • Busy-Hour Trunk Capacity: Displays ABBH (Average Bouncing Busy Hour) data that are collected from the Unified CM CDR.
                    • Utilization: Trunk, DSP, MTP/Transcoder, Route Group and Trunk Group.
                    • Conference Locations: Displays conference details, such as conference category, count, and so on for endpoints.
                    • Conference Statistics: Displays conference details, such as participants count, duration and so on.

                    CPU and memory utilization.

                    Creating Custom Reports

                    To create a custom report:

                    Procedure

                    Choose Analytics > Custom Report Generator .

                    Choose a report from the Reports drop-down list.

                    From the Attributes and Values panes, choose the elements.

                    Double-click the Attributes element to view and select the required parameters.

                    The elements of a Attributes can be organized as a hierarchy, a set of parent-child relationships, where a parent member summarizes its children. Parent elements can further be aggregated as the children of another parent; for example, May 2014's parent is second Quarter 2014 which is in turn the child of Year 2014.

                    For network analysis or UC utilization related custom reports, if you have selected to view hourly data for over 13 months, the report may take a long time to generate. It is recommended to select hourly data for a time period less than 13 months.

                    Custom Report Generator is not supported in MSP mode.

                    You can view the generated report in chart or grid mode. You can export the report in PDF, MS Excel, PNG, and so on based on the view mode.

                    For the query that you have defined, you can view the corresponding query in the MDX language. MDX is a language for querying an OLAP cube. MDX is similar to SQL, but has added support for the multidimensional nature of cubes. For more details on the MDX query, see the Mondrian Documentation. While writing the MDX query, you must use the attributes and values to generate the report; you can refer to the Attributes and Values page.

                    Scheduled Reports

                    This dashboard displays the list of entities (reports) that have been scheduled (when you click Schedule Report from the drop-down on the bottom-left of a dashlet). To view this dashboard, go to Analytics > Scheduled Reports .

                    You can view the report name, report type, frequency of the schedule, the filters that you have used while scheduling (displayed in Filter Settings when you click Schedule Report from the drop-down on the bottom-left of a dashlet), the status indicating success/failure when the report was last generated, and next scheduled run time.

                    The top Metric panel displays data on the disk utilization, reports e-mailed and reports exported to SFTP server.

                    You can also suspend or resume a job (select a job and click Suspend/Resume). In case of errors, rest your mouse over a job to view the errors.

                    Also, you can add or remove the columns displayed, based on your business needs. To do this, click Settings icon available on the top-right corner of the page and rest your mouse on Columns .

                    To generate the report immediately:

                    • Click Run Now (at the end of the row of each report listed).
                    • Click the Run History (adjacent to Run Now) - shows the number of times the report has been run but the number of files listed are limited for the last 30/35 days only . List of reports that have been run are displayed.
                    • You can download a report or purge the selected report.
                    • You cannot use Run Now on a report for which the schedule time has expired (reached end date).
                    • Clicking Run Now does not change the original schedule of the job (daily, weekly, and such).

                    For Cisco Prime Collaboration Release 11.6 and later

                    Concurrent Hourly Report (Top N Call Traffic Locations):

                    1. Launch PCA.
                    2. Click Analytics.
                    3. Click ‘Traffic Analysis’ from the drop down list.
                    4. Click ‘See Details’ on the right bottom, from the ‘Top N Call Traffic Locations’ dashlet to view the Detailed Analysis page.
                    5. Click ‘Export’ and then click on ‘Scheduled Export’ to generate Scheduled Reports dialogue box.
                    6. Check the box against ‘check this to Schedule hourly reports for previous day’ to generate Concurrent Hourly Scheduled Reports which is available in the bottom of ‘Scheduled reports’ Dialogue box below the ‘Filter Settings’. If you do not check the Concurrent Call Hourly check box, then “Time period” in filter remains the same and so, the generated PDF will not have hourly data.

                    For Top N locations dashlet, when you select one-day interval, generated scheduled reports (PDF) is in a ‘Bar Chart’ manner. Grid/Table will have Concurrent hourly/ daily data. Bar chart/grids both are shown in the same PDF report generated from Top N locations dashlet.

                    Daily Report (Top N callers and Top N dialed numbers):

                    1. Launch PCA.
                    2. Click Analytics.
                    3. Click ‘Traffic Analysis’ from the drop down list.
                    4. From the ‘Top N callers/Top N Dialed Numbers’ Dashlet click ➦ (right bent arrow) which is in the bottom of Top N callers and Top N dialed numbers dashlets.
                    5. Click Scheduled Reports from the drop down menu to see the Scheduled Report window.
                    6. Click the check box against ‘Check this to schedule daily report’ to view daily reports. Check this box to see the modified title and time period in the filters shown in Scheduled Reports.

                    Troubleshooting Prime Collaboration Analytics Dashboard

                    The following table has the details to troubleshoot data population in individual dashboard:

                    Associated reports to confirm data collection

                    • Trunk Utilization:Configure maximum SIP trunk capacity, and define custom trunk groups .
                    • Busy-Hour Trunk and Busy-Hour Route-Group Capacity: Maximum CDR trunk capacity must be configured.
                    • Route Group/Trunk Group Utilization: Configure Maximum SIP trunk capacity, and define custom trunk groups, and Associate trunks to route group .
                    • Conferencing Devices Video Utilization: Conference bridges must be deployed and discovered in device work center, and calls from any of these media resources (MCU, TPS, CTMS) must be present.
                    • DSP Utilization:Gateways must be discovered.

                    For Cisco Prime Collaboration Release 11.1 and earlier

                    For Cisco Prime Collaboration Release 11.5 and later

                    Video Conference Analysis

                    • At least two video endpoints in a conference must be available.
                    • Video Conference Statistics: Endpoints visibility must be set to Full (Inventory > Edit (under Current Inventory)) and session details must be polled.