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.
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 Prime Collaboration Analytics dashboards for the first time you launch Prime Collaboration Analytics:
See Cisco Prime Collaboration Assurance Guide - Advanced for more information about these tasks.
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.
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:
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.
Note | Global filters are not applicable for the Metrics in the Technology Adoption dashboard. |
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:
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.
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.
The Quick Tips help you customize the graphical view for your convenience.
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).
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.
To configure sFTP server:
Step 1 | Choose Analytics Administration > sFTP Settings. |
Step 2 | Enter the required details on the sFTP Settings page. Refer Table 1 for field description. |
Step 3 | Click Test Connection to check the connectivity to the sFTP server. |
Step 4 | Upon successful connection, click Save. |
In MSP mode, the operator users do not have access to
Analytics
Administration menu and cannot configure sFTP server.
Field
Description
sFTP
Server(IP Address)
IP address
of the sFTP server where the scheduled reports must be saved.
sFTP Port
Port number
of the sFTP server.
Path(Directory)
Directory
path in the sFTP server where the scheduled reports must be saved.
User Name
Username for
accessing the sFTP server.
Password
Password for
accessing the sFTP server.
Ensure that the following prerequisites are met for data to be populated in the Prime Collaboration Analytics dashlets.
Endpoints registered with Unified CM and Cisco VCS are discovered (Device InventoryInventory).
CDR records for Unified CM and Cisco VCS registered endpoints is available (
).Confirm data collection for the registered Unified CM in
.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.
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.
The following dashlets are available in the Asset Usage dashboard:.
This dashlet shows the deployment trend of the configured and active endpoints.
By default, this dashlet will display the graph for all endpoints that were deployed from the date Cisco Prime Collaboration 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.
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.
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 or location, or cluster.
Note | The data displayed for the unused endpoints per week in the detailed view graph is not in synchronization with the Least Used Endpoint Types Report table in the detailed view. This is because, the table lists only the endpoints that were not used or least used for the selected duration in the detailed view graph; in the dashlet, the formula used for calculating the least used endpoint is: Least used endpoint type = (total number of calls by each endpoint type across the selected number of weeks / selected number of weeks) > = number of selected calls. |
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 and Analytics—Business 11.5, see Supported Devices for Prime Collaboration Business 11.5
You can view the call distribution details for the following endpoint types:
Endpoint Types | Endpoint Models |
Multipurpose TelePresence |
|
Immersive TelePresence |
|
Personal TelePresence |
|
Mobile Video |
|
Audio IP Phones |
|
Wireless IP Phones |
|
Personal Communicator |
|
Desktop Video |
|
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, or location.
This dashlet displays the call distribution based on call volume per endpoint model. You can view the details for the calls that are,
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, 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.
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:
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.
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.
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.
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:
This dashlet displays data for endpoints registered with Unified CM and VCS.
Note | In dashlet view and detailed view, Cluster ID filtering is not supported for the endpoints registered with VCS. |
This dashlet displays the OffNet versus OnNet traffic trend per location.
You can filter the data displayed in the detailed view page based on off net or onnet traffic, call type, call count, call duration, cluster, location, device pool, endpoint details (such as IP, directory number, or source URI and so on), call direction, or user ID.
Note | You can also filter the data in the detailed view based on the call direction, such as, incoming or outgoing calls. Incoming calls are the calls received by the gateway from the CUCM, whereas the outgoing calls are the calls made from the gateway to the CUCM. So when you filter incoming calls, you must enter the endpoint details of the source or the caller and when you filter outgoing calls , you must enter the endpoint details of the callee or the destination. When you filter data based on the endpoints the directory numbers of those endpoints that are managed in the Cisco Prime Collaboration Assurance are displayed, the external directory numbers are not displayed. |
In dashlet view, the formula used to calculate the percentage of OnNet calls is:
Total number of OnNet calls in the location/ Total number of OffNet calls and OnNet calls in that location * 100
The formula used to calculate the percentage of OffNet calls is:
Total number of OffNet calls in the location/ Total number of OffNet calls and OnNet calls in that location * 100
The dashlet does not include the calls processed on Video Communication Server (VCS).
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. |
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.
This dashlet displays the distribution of calls that belong to the following predefined call categories:
External
Internal
Conference
Emergency
Long distance
Toll free
H 323 (Incoming and outgoing gateways/trunks) or MGCP (Incoming and outgoing gateways) or SIP (Incoming and outgoing trunks)
Voicemail
Local
International
To add a call category, see section Call Category Creation.
Note | A call can be included in more than one call category; for example, an internal call can also be a conference call. Therefore, the sum of all calls that belong to all categories might be greater than the reported total number of calls. |
This dashlet includes only the details for the calls processed on Unified CM. Call category information is collected from CDR.
In dashlet view, the formula used to calculate the percentage of the distribution of calls is:
Total number of calls or the duration of calls that belong to a specific traffic category / Total number of calls or duration of calls of all categories * 100.
In detailed view, the formula used to calculate the percentage of the distribution of calls is:
Total number of calls of a traffic type which belongs to one call status (failed, dropped, completed, attempted / Total number of calls of a traffic type which belong to Attempted call status * 100.
You can filter the details in the Detailed View based on location, call type, call status, call count, call duration, call direction, or cluster.
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.
SIP Trunk Type |
% Utilization Report |
Busy-hour Trunk Traffic Report |
||
Data Source | Support | Data Source | Support | |
SIP Trunk terminated at Cisco CUBE |
Polling the CUBE directly |
Available |
CDR |
Available |
UCM logical SIP trunk (ICT, Trunk to WebEx, etc) |
RTMT UCM SIP Performance Counter |
NA |
CDR |
Available |
SIP Trunk terminated at non-Cisco border element (ACME, etc) |
RTMT UCM SIP Performance Counter |
NA |
CDR |
Available |
You can view the following dashlets from the Capacity Analysis dashboard:
If you want to view the data for the custom trunk groups, you must define these groups using Administration > Analytics Group Management.
You must configure the maximum capacity for SIP trunks for the SIP data to be populated in this dashlet. You can configure the maximum SIP capacity using Operate > Utilization Monitor > Trunk Utilization > SIP Trunk Capacity Settings.
For other trunks, such as MGCP, inter-cluster and so on, the data is collected through polled data.
This dashlet helps you track route group utilization.
This dashlet displays the aggregated data for trunk/route group. The utilization data for this dashlet is obtained from the voice utilization polled data. You can view maximum concurrent calls (configured data), concurrent calls (data used) and the utilization in percentage. You can also view the pattern of peak route group utilization over a period of months.
To view the aggregated data, you must associate the trunks to a route group using
.For the SIP trunk data to be populated, you must configure the maximum capacity for SIP trunks using
. 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 Administration > Analytics Group Management.
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 and audio, video or immersive. By default, it displays the locations where bandwidth utilization has been peak for the last 28 days.
You can filter the details displayed in the detailed analysis based on WAN location, bandwidth used, utilization type, failed calls, or cluster. You can also filter the calls based on locations. Use the Select option to choose a location.
This dashlet will not include the details for the calls processed on VCS.
You can track DSP resource utilization, so that you can optimize it's usage. In this dashlet, you can view the average and minimum DSP utilization for a gateway.
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
or from the DSP Detailed Analysis page. In the Detailed Analysis page, click Save Results after applying the required filter parameters. While creating the custom groups, you must ensure that the number of gateways selected must not exceed 100. You can edit or delete the custom groups from the Device Work Center page only.Note | In MSP mode, the operator user do not have the privilege to create custom group, hence the Save Result button is grayed out. |
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.
Issue found:
Detail view page for "Users with Call Quality Issues" shows 'No data'.
Work around provided:
Note | You can find the Detail view page from Quick view shows data. |
Login to Prime Collaboration Assurance server address 10.197.94.104 with the username globaladmin and password Ecmbu!23.
Go to 'Analytics -> Service Experience'
Observe the data available in 'Users with Call Quality Issues' dashlet
.Click on 'See Details'.
Detail view page shows 'No data'.
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.
This dashlet displays the top N locations that have highest number of failed calls (calls that failed to establish due to lack of bandwidth).
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.
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
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.
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.
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:
Refer Table 1 for the list of supported endpoint models.
The device information details for this dashlet are gathered from Prime Collaboration inventory and the call quality information for this dashlet is obtained from CMR.
In dashlet view, the formula used for calculating the percentage of the acceptable and poor quality calls is:
Total number of Poor and Acceptable calls of an endpoint model or endpoint type / Total number of calls of same endpoint model or endpoint type * 100.
In detailed view, the formula used for calculating the percentage of the acceptable and poor quality calls is:
One type of call grade of an endpoint model or endpoint type / Total number calls of the same endpoint model or endpoint type * 100.
You can filter the details in the Detailed View based on endpoint type, endpoint model, call type, call grade, calculation (absolute or percentage), call count, call duration, cluster, location, device pool, IP Address, directory number, or URI.
This dashlet includes only the details for the calls processed on Cisco Unified Communications Manager.
Note | The call count data displayed in the detailed view graph will not be in synchronization with the data displayed in the Call Records table. This is because, the detailed view graph aggregates the data at the endpoint level (using CMR) but the Call Records table displays data at call details level (using CDR). |
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.
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:
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 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.
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.
You can customize dashboards on My Dashboard page and add existing dashlets to it.
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 Analyze > 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 and reports e-mailed.
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 . List of reports that have been run are displayed.
You can download a report or purge the selected report.
Note |
|
The following table has the details to troubleshoot data population in individual dashboard: