Appearance
CUBE XCC Analytics Dashboard
Call Telemetry provides monitoring and analytics for your CUBE XCC integration through the Metrics and Health Dashboard. Track call quality, analyze performance metrics, and gain insights into your voice communications.
Feature Overview
By integrating your Cisco CUBEs with Call Telemetry, you gain access to historical data on call quality and performance. This dashboard is designed to help you monitor the health of your voice communications and identify potential issues.
The CUBE XCC Metrics and Health Dashboard offers:
- Historical Analysis: Analyze trends over time with customizable date ranges
- Call Quality Metrics: Report on Call MOS scores, packet loss, and round-trip time
- Call Volume Tracking: Monitor concurrent call volumes for capacity planning
- Hourly Distribution: View call volume patterns by hour of day for resource planning
- Inbound/Outbound Analysis: Compare incoming and outgoing call traffic patterns
- Detailed Call Records: Access comprehensive information about individual calls
- Disconnect Code Analysis: Identify patterns in call termination reasons
Feature Requirements
- Call Telemetry Server Appliance 0.8.4 or later
- Call Telemetry Advanced License
- Configured CUBE XCC Integration
- Add Disconnect Events to your CUBE XCC integration to enable quality reporting (bottom right corner of the integration page)
IOS Router Configuration
On the CUBE, add the following command to enable disconnect events:
bash
callmonitor
rtcpall-pass-through
media statistics
media bulk-stats
call-quality
max-dropout 100
max-reorder 100
Accessing the Dashboard
To access the CUBE XCC Metrics and Health Dashboard:
- Log in to your Call Telemetry dashboard
- Navigate to Analytics > CUBE XCC
- Select a specific CUBE from the overview page to view its metrics (click the metrics icon)
Time Period Selection
The dashboard allows you to select different time periods for data analysis:
- 1 Hour: View the most recent hour of data
- 24 Hours: View the last 24 hours (default view)
- 7 Days: View the last week of data
- 30 Days: View the last month of data
- Custom: Select a custom date and time range
Window Interval Size
Control data aggregation with the Window Size dropdown. For example, if you select a 1-hour time period with a 5-minute window size, the data will be aggregated into 5-minute intervals. This allows you to view trends and patterns over different time frames.
- Smaller window sizes (1 minute, 5 minutes): Provide more granular data, may impact query time and rendering of graphs
- Larger window sizes (1 hour, 4 hours): Better for viewing long-term trends
The system automatically suggests appropriate window sizes based on your selected time period.
Timezone Selection
The dashboard displays all times in your local timezone. You can change the timezone by clicking on the timezone dropdown in the top-right corner of the page. This allows you to view data in other timezones.
CUBE Call Reporting (via XCC)
Clicking on the metrics icon for a specific CUBE will take you to the detailed metrics dashboard for that CUBE. The dashboard provides a comprehensive overview of call quality and performance metrics, allowing you to monitor and analyze your CUBE XCC integration effectively.
Cube Health (XCC Metrics)
The Cube Health tab displays three key metrics that indicate the overall health of your voice communications:
MOS Score (Mean Opinion Score)
MOS is a numerical measure of the perceived quality of media received after compression and/or transmission. The MOS score ranges from 1 (bad) to 5 (excellent):
- 5.0: Perfect quality, imperceptible impairments
- 4.0-5.0: Excellent quality
- 3.5-4.0: Good quality
- 3.0-3.9: Fair quality, perceptible but not annoying
- 2.0-2.9: Annoying and objectionable
- Below 2.0: Very annoying and objectionable
Packet Loss Ratio
Packet loss occurs when data packets fail to reach their destination. In VoIP communications, packet loss can cause audio dropouts, choppy audio, or complete call failure:
- 0-1%: Excellent, generally unnoticeable
- 1-2%: Good, minor audio issues may be noticeable
- 2-5%: Fair, noticeable audio quality degradation
- 5-10%: Significant audio problems
- >10%: Severe call quality issues, likely unusable
RTT (Round Trip Time)
RTT measures the time it takes for a packet to travel from the source to the destination and back. High RTT can cause delays in conversation, leading to participants talking over each other:
- 0-100ms: Excellent, no noticeable delay
- 100-200ms: Good, slight delay but generally acceptable
- 200-300ms: Fair, noticeable delay, may affect conversation flow
- >300ms: Poor, significant delay, conversation becomes difficult
Each metric is displayed as a line chart showing trends over the selected time period.
Concurrent Calls
The Concurrent Calls tab shows the number of simultaneous active calls over time, useful for:
- Capacity planning
- Identifying peak usage periods
- Correlating call volume with quality issues
- Monitoring system load
Call Details
The Call Details tab provides a detailed table of individual calls, including:
- Time: When the call occurred
- Calling Number: The originating phone number
- Called Number: The destination phone number
- MOS Score: Call quality score
- Packet Loss: Percentage of lost packets
- RTT: Round trip time in milliseconds
- Codec: Audio codec used for the call
- Duration: Length of the call
The table can be sorted by any column by clicking on the column header.
Disconnect Codes
The Disconnect Codes tab provides comprehensive insights into call termination patterns through two complementary visualizations:
Disconnect Codes Overview
The stacked area chart shows the frequency of different call termination reasons over time. This helps identify patterns in call disconnections and potential issues.
Common disconnect codes include:
- Normal call clearing
- User busy
- No user responding
- No answer from user
- Call rejected
- Network congestion
- Service unavailable
Disconnect Codes Distribution
The Disconnect Codes Distribution chart provides a high-level view of normal versus abnormal disconnect codes, helping you quickly assess the health of your call termination patterns.
Normal Codes: Disconnect codes that represent normal call clearing events
- Code 16: "Normal Call Clearing"
- Code 31: "Normal, Unspecified"
Abnormal Codes: All other disconnect codes, which may indicate issues with the call
The chart displays:
- Total count of all disconnect codes in the selected period
- Count and percentage of normal disconnect codes
- Count and percentage of abnormal disconnect codes
- Visual representation of the distribution as a pie or donut chart
This visualization helps you quickly identify if your system is experiencing an unusual number of abnormal call terminations, which may warrant further investigation.
Calls by Hour
The Calls by Hour chart provides a visualization of call volume distribution across different hours of the day. This helps you identify:
- Peak calling hours
- Business hour patterns
- After-hours call volume
- Capacity planning opportunities
This view is particularly useful for identifying when your system experiences the highest load, allowing you to plan resources accordingly and ensure adequate capacity during peak hours.
Inbound/Outbound Calls
The Inbound/Outbound Calls tab provides a comparative analysis of incoming and outgoing call traffic over time. This visualization helps you:
- Monitor the balance between inbound and outbound calls
- Identify trends in call direction patterns
- Analyze customer service vs. outreach activities
- Optimize staffing for inbound call handling
The chart displays inbound calls (calls received by your system) and outbound calls (calls initiated from your system) as separate lines, allowing you to easily compare volumes and identify patterns or anomalies in either direction.
Data Export
Export your metrics data for further analysis or reporting:
- Navigate to the desired tab (Cube Health, Concurrent Calls, etc.)
- Click the Export button in the top-right corner
- Choose your preferred format (CSV, Excel, PDF)
- Select the time range for the export
- Click Download
Troubleshooting
If you notice issues in your metrics, consider the following troubleshooting steps:
Poor MOS Scores
- Check for packet loss and high RTT
- Verify network connectivity
- Check for QoS (Quality of Service) configuration
- Verify codec settings
High Packet Loss
- Check network connectivity
- Look for network congestion
- Verify router and switch configurations
- Check for bandwidth limitations
High RTT
- Check network path
- Verify WAN connectivity
- Look for routing issues
- Check for bandwidth saturation
Unusual Disconnect Codes
- Check SIP trunk configuration
- Verify dial plan settings
- Check for call routing issues
- Verify endpoint registration status