Cisco Prime Collaboration Analytics Guide, 10.0
Prime Collaboration Analytics Dashboards
Downloads: This chapterpdf (PDF - 1.32MB) The complete bookPDF (PDF - 2.17MB) | Feedback

Prime Collaboration Analytics Dashboards

Contents

Prime Collaboration Analytics Dashboards

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

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 Prime Collaboration Analytics dashboards for the first time you launch Prime Collaboration Analytics:

  • Device Discovery
  • Session Import
  • Device Polling

See Cisco Prime Collaboration Assurance Guide - Advanced 10.5 for more information about these tasks.

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

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

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.

Schedule Report- The Export/Print drop-down 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).

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 that runs every 60 minutes and checks for jobs scheduled to run on the current day. If a new job is scheduled to run on the current day, with recurrence interval like "Only Once", "Daily" or "Weekly", and such, the job scheduler runs the job within 60 minutes interval. Any new job submitted for the first time, will run in a similar manner.

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.

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

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

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

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.


Note


  • In detailed view, dashlets with VCS registered endpoints display the location, codec, and device pool details as VCS_Unknown. Impairment details are not applicable for VCS registered calls and will be displayed as zero in the detailed view.
  • The detailed view of the CDR based dashlets displays the CDR or CMR data only for the last 30 days. The call details of the endpoints prior to 30 days is not displayed by the dashlets, however, the aggregation of CDR or CMR data for the endpoints is available for the time period of one year.
  • For dashlets with IP address and Directory Number filters, ensure that you enter the details in the following order:
    • 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).

Global Filter Option

Filter option is available at the top left of the UI for each dashboard. You can filter the data displayed for all the dashlets in that dashboard based on the CUCM cluster and duration (for example, last one week, one month and so on).


Note


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


Pre-requisites for Data Population in the Prime Collaboration Analytics Dashlets

Ensure that the following pre-requisites are met for the data to be populated in the Prime Collaboration Analytics dashlets.

  • Endpoints registered to CUCM and VCS are discovered.
  • Deployment Distribution by Endpoint Model - Endpoint status in DWC is either registered, partially registered, or non-registered.
  • Call Distribution by Endpoint Model and Types - CDR records for CUCM and VCS registered endpoints are available.
  • Top and Bottom N Utilized Video Conferencing Devices - Calls from any of the media resources (MCU,TPS,CTMS) is present.

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. All dashlets in this dashboard display data for endpoints registered with CUCM 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:

Metrics Provides a quick update on
Video endpoints deployed
  • Total video endpoints in use
  • Change in the number of endpoints in the last 1 month
  • Percentage of video endpoints deployed
Video call minutes
  • Total duration of video calls
  • Change in the duration of video calls in the last 12 weeks
  • Trend of video call usage
Audio endpoints deployed
  • Total number of audio endpoints
  • Change in the number of endpoints in the last 1 month
  • Percentage of audio endpoints deployed
Audio call minutes
  • Total duration of audio calls
  • Change in the duration of audio calls in the last 12 weeksthe

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


Note


In dashlet view and detailed view, Cluster ID filtering is not supported for the endpoints registered with VCS.


The following dashlets are available in the Technology Adoption dashboard:

Deployment Distribution by Endpoint Model

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

  • All endpoints that are managed in Cisco Prime Collaboration, irrespective of their registration status are categorized as configured endpoints.
  • Endpoints in Cisco Prime Collaboration 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 Prime Collaboration was installed till the current date. If you select the time period as one week ago, the graph will display all the endpoints that were deployed from the day you installed Prime Collaboration till the current date (one week 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 VCS, the count of active and configured endpoints will be the 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 will be moved to Deleted state only when the status remains to be unregistered for more than 24 hours.

Call Distribution by Endpoint Model

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 Call Details Record (CDR) and VCS that the Cisco Unified Communications Manager generates.

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 or location.

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

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.

You can view the call distribution details for the following endpoint types:

Table 1  Supported Endpoint Models and Endpoint Types
Endpoint Types Endpoint Models
Multipurpose TelePresence
  • Cisco TelePresence C20
  • Cisco TelePresence C40
  • Cisco TelePresence C60
  • Cisco TelePresence C90
  • Cisco TelePresence SX20
  • Cisco TelePresence Profile Series
  • Cisco TelePresence System MX 200
  • Cisco TelePresence System MX 300
  • Polycom ( HDX,VSX )
Immersive TelePresence
  • Cisco TX9000 series
  • CTS 3000 series
  • CTS 3200 series
  • Cisco TelePresence TX1300 series
  • Cisco TelePresence T3
Personal TelePresence
  • EX60
  • EX90
  • CTS 500
  • CTS 1100
  • MXP
Mobile Video
  • Android
  • iPhone
  • Blackberry
  • iPad
  • CIUS
  • Cisco Jabber for Tablet
  • Nokia-S60
Audio IP Phones
  • 79XX
  • 39XX
  • 69XX
Wireless IP Phones
  • 792X
Personal Communicator
  • CUPC
  • CIPC
  • CSF
  • Mac
  • Windows
  • IP Communicator
Desktop Video
  • 99XX
  • 89XX
  • 7985
  • Cisco Jabber Video for TelePresence (Movi)
  • E20

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

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 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 CUCM CDR and VCS.

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

This dashboard has only one dashlet-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 CUCM and VCS. Device details for this dashlet is collected from Prime Collaboration inventory and the call details are collected from CDR.


Note


In dashlet view and detailed view, Cluster ID filtering is not supported for the endpoints registered with VCS.


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, cluster, or location.


Note


The data displayed for the unused endpoints per week in the detailed view graph is not in synchronization with the Least Used Endpoint Types Report table in the detailed view. This is because, the table lists only the endpoints that were not used or least used for the selected duration in the detailed view graph.


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.

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

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 number to any other number.

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

You can view the number of calls or the duration of calls either in absolute or percentage mode.

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 CUCM CDR and VCS.


Note


In dashlet view and detailed view, Cluster ID filtering is not supported for the endpoints registered with 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 CUCM CDR 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.

Note


In dashlet view and detailed view, Cluster ID filtering is not supported for the endpoints registered with VCS.


Top N Off-Net Traffic Locations

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

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.


Note


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, or cluster.


Note


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


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

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

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

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 Adding a Call Category in Cisco Prime Collaboration Assurance Guide - Advanced 10.0.


Note


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


This dashlet includes only the details for the calls processed on Cisco Unified Communications Manager. Call category information is collected from Call Details Record.

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

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 view the following dashlets from the Capacity Analysis dashboard:

Top N Utilized Video Conferencing Devices

This dashlet helps you to track the most utilized conferencing devices. It also:

  • Provides statistics of the peak and average usage of video ports in conferencing devices over a given period of time.
  • Helps you see the usage trends of the video ports configured in your network, and manage them better.

You can filter the details in the detailed analysis, based on conferencing device, utilization, peak or average ports 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).

This dashlet displays data for both CUCM and VCS registered endpoints. Device details for this dashlet is gathered from Prime Collaboration inventory and the conferencing device utilization information is collected from Communications Manager.

This dashlet displays only the percentage of the each port used. It does not display the actual port count.

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

Bottom N Utilized Video Conferencing Devices

This dashlet helps you to identify the least utilized conferencing devices. It also,

  • Provides statistics of the Average video ports used in conferencing devices over a given period of time.
  • Helps you see the trends of the video ports, and manage them better.

You can filter the details in the detailed view based on conferencing device, utilization, traffic type, cluster, location, device types (MCU, CTMS, or TPS), and peak or average ports. You can also select a Conductor and individual device information.

This dashlet displays data for endpoints registered with CUCM and VCS. The device details for this dashlet is gathered from Prime Collaboration inventory and the conferencing device utilization information is collected from UCMS.

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

This dashlet displays only the percentage of the each port used. It does not display the actual port count.

Top N 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.

This dashlet lists the top N locations/ location nodes with the highest bandwidth usage. Locations where bandwidth utilization has been average are also displayed in this dashlet.

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

Bottom N Location CAC Bandwidth Utilization

This dashlet helps you to identify the WAN locations where bandwidth usage is minimal. Locations where bandwidth utilization has been average are also displayed in this dashlet.

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

The dashlet can be filtered based on utilization type as Audio, Video, or Immersive. By default, it displays the locations where audio bandwidth utilization has been least for the last 28 days.

You can filter the details displayed in the detailed view based on WAN location, bandwidth used, utilization type, failed calls, or cluster.

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


Note


Locations with unlimited bandwidth utilization will not be displayed in this dashlet.


Top N Utilized Trunks

This dashlet helps you to identify which trunks or route groups are the most heavily utilized. By default, the Top 10 Utilized Trunks or Route Groups (RG) can be seen in this dashlet. You can also view the pattern of peak and average trunk utilization over a period of months. The utilization data for this dashlet is obtained from GSU records. This dashlet will not include the details for the calls processed on VCS.

You need to configure the maximum capacity for SIP trunks for the data to be populated in this dashlet.

To configure the maximum capacity for SIP trunks:


    Step 1   From the Home dashboard, go toInfrastructure.
    Step 2   Click Utilization Settings in Top 10 Utilized Trunks /Route Groups.
    Step 3   Configure max capacity for SIP trunks (cube only) and Save the configuration.

    Bottom N Utilized Trunks

    This dashlet helps you to identify which trunks or route groups are minimally utilized. By default, the Bottom 10 utilized trunks or route groups is displayed in this dashlet. It also displays the pattern of peak and average trunk utilization for these trunks. The utilization data for this dashlet is obtained from GSU records.

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

    Top N Busy-Hour Trunk Capacity

    This dashlet helps you identify the trunks top N trunks or 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. 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 or 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 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 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), login to the server as root and edit the file gos.properties available at /opt/emms/emsam/conf. After making the changes, save the file and refresh the UI.

    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 need to configure the maximum capacity for the CDR utilization trunks inorder to see the available capacity in the dashlets.

    To configure maximum capacity for CDR trunks:


      Step 1   From Administration drop-down, click System Setup.
      Step 2   From Assurance Setup drop-down, click CDR Trunk Utilization Settings.
      Step 3   Select a cluster and a gateway and click Configure Maximum Capacity.
      Note   

      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.

      You can filter the details displayed in the detailed view based on trunk or 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.


      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.

      Bottom N Busy-Hour Trunk Capacity

      This dashlet helps you to identify the trunk or route groups that have minimal ABBH traffic. You can also view the capacity details (The available capacity, minimum required capacity, average required capacity, minimum BBH) for these trunks or route groups.

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

      You can filter the details displayed in the Detailed View based on trunk or route group, traffic type and direction, bandwidth used, cluster (when you choose Select option in the detailed view).

      Service Experience

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

      The following dashlets are available from the Service Experience dashboard:

      Service Experience Distribution

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

      • Good-The Mean Opinion Score (MOS) value exceeds the acceptable MOS threshold.
      • Acceptable-The MOS value falls between the acceptable MOS threshold and the poor MOS threshold.
      • Poor-The MOS value falls below the poor MOS threshold.
      • Short Calls-A short duration call with zero MOS.
      • No MOS calls-A call for which Unified Communications Manager sets MOS to zero.
      • Unknown Calls-Occurs when the corresponding Call Measure Records (CMR) are not available.

      To configure Thresholds, see Configuring Global Thresholds section in Cisco Prime Collaboration Assurance Guide - Advanced, 10.5.

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

      • Graded calls-Good, Acceptable, and Poor calls
      • Graded and Ungraded calls-Short, Unknown, and No MOS calls

      By default, the dashlet view displays the chart for the 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 is collected from Prime Collaboration inventory and the call quality details for this dashlet is obtained from CDR.

      Based on the Exclude options given below, the percentage of distribution of calls are shown in the detailed view.

      • Exclude Short Calls-Displays the percentage of call grades, except for short calls.
      • Exclude Unknown and No MOS calls-Displays the percentage of call grades, except for Unknown and No MOS calls.

        Note


        Exclude option will be enabled only when you select the percentage option in the detailed view and uncheck the Short, Unknown and No MOS check boxes.


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

      Endpoints with Service Quality Issues

      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 the following endpoints:

      • Soft Clients
      • Conference Video
      • Hard Phones
      • Desktop Video
      • Mobile Video

      Refer Table 1 for the list of supported endpoint models.

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

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

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

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

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

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

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


      Note


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


      Top N Call Failure Locations

      This dashlet displays the top N 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.