Cisco Unified Border Element (CUBE) Management and Manageability Specification White Paper

White Paper

Available Languages

Download Options

  • PDF
    (1.0 MB)
    View with Adobe Reader on a variety of devices
Updated:July 6, 2021

Bias-Free Language

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.

Available Languages

Download Options

  • PDF
    (1.0 MB)
    View with Adobe Reader on a variety of devices
Updated:July 6, 2021
 

 

1. Product/Feature

This Cisco Unified Border Element (CUBE) Manageability document contains information about the Simple Network Management Protocol (SNMP) MIBs, critical system log (syslog) messages and general Cisco IOS-XE commands for monitoring and troubleshooting a CUBE deployment. CUBE has a wide range of capabilities that may be used to secure, monitor, and maintain business-critical connections and to ensure compliance with industry standards. In addition to physical hosts from Cisco Integrated Services Router (ISR), Cisco Catalyst Edge Routers and Aggregation Services Router (ASR) product families, CUBE features are available for virtualized environments with the Cisco Cloud Services Router (CSR) and Catalyst Edge Software.

CUBE is an integrated Cisco IOS-XE enterprise Session Border Controller (SBC) feature set facilitating simple and cost-effective connectivity between independent unified communications, voice over IP (VoIP), and video networks. Typical connectivity deployments where CUBE is used include:

     Connect Cisco Unified Communication Manager (CUCM) enterprises to service provider SIP trunks

     Connect 3rd party enterprise IP PBXs to PSTN interconnect using Internet service provider SIP trunks

     Migration from TDM to SIP public telephony trunk services. As a number of Cisco routers allow the concurrent use of voice gateway and CUBE features, a phased trunk migration is possible without requiring changes to the enterprise call control platform.

     Certified connection to Cisco and third-party cloud collaboration services, including Webex Edge Audio, Webex Cloud Connected Audio (CCA and CCA-SP), Webex Calling, Cisco Hosted Collaboration Solution (HCS) and Direct Routing for Microsoft Phone System (Microsoft Teams), call recording, among others.

SBCs such as CUBE, offer unified communications network interoperability features such as:

     Session management: Real time session management at the network border, such as call admission control, dial-plan interpretation and routing, SLA monitoring, QoS policy marking etc.

     Interworking: Features that interconnect networks with different protocols or capabilities, such as SIP interworking, SIP normalization, DTMF type conversion, payload type conversion, IPv4-IPv6 interworking, transcoding and transrating etc.

     Demarcation: Allows a single point of troubleshooting for SIP trunks and voice quality issues with features such topology hiding, statistics and billing (call detail records, or CDR) at the border of the network.

     Security: Security enforcement at the network border through features such as SIP registration, SIP port protection, hostname validation, authentication and encryption features etc.

1.1 Overview/Description

Four aspects of CUBE Manageability are addressed in this document:

     License Management

General Cisco IOS-XE Command Line Interface (CLI) and Cisco Smart Licensing are used. Cisco Smart Licensing is a software licensing model that provides visibility of ownership and usage through the Cisco Smart Software Manager (CSSM) portal. CSSM is a central license repository that manages licenses across all Cisco products that the customer owns, including CUBE.

     Provisioning

The main method to provision CUBE is using the CLI. Alternatively customers can provision certain aspects of CUBE using Arcana Manage Express Border Manager (MEBM) for SIP trunk configurations.

Cisco IOS XE supports the Yet Another Next Generation (YANG) data modeling language. YANG can be used with the Network Configuration Protocol (NETCONF) to provide the desired solution of automated and programmable network operations. NETCONF (RFC 6241) is an XML-based protocol that client applications use to request information and make configuration changes to the device. YANG is primarily used to model the configuration and state data used by NETCONF operations. CUBE SDWAN based configurations/monitoring using Cisco vManage is under development.

CUBE provisioning includes the following elements:

    General router attributes

    Routing protocols, router interfaces, access lists, DNS connectivity, NTP (clock settings), QoS policies, SNMP connectivity, AAA/RADIUS connectivity, security features etc.

    Global CUBE attributes

    Turn on CUBE and specify the protocols that should be handled

    DSP hardware configuration and attributes (if present)

    SIP provisioning

    Global SIP parameters and attributes

    SIP header manipulation

    Dial-peers for SIP call sources and destinations

    SIP User Agent parameters and attributes

    Dial-Plan provisioning

    Dial-peers, translation rules and digit manipulation features for interpreting the dial plan and routing calls as desired

     Monitoring

General Cisco IOS-XE router monitoring using CLI, syslog and SNMP are supported.

CUBE supports most of the general Cisco IOS-XE unified communications SNMP MIBs as well as several object identifiers (OIDs) developed specifically for CUBE use cases.

Certain aspects of IOS-XE can be configured using Representational State Transfer Configuration Protocol (RESTCONF). RESTCONF provides a programmatic interface based on standard mechanisms for accessing configuration data, state data, data-model-specific Remote Procedure Call (RPC) operations and events, defined in the YANG model.

CUBE monitoring includes the following elements:

    Router Inventory and Health: CPU, memory, flash, modules, software image and release etc.

    Interface Health: General IOS-XE router interfaces, status and packet traffic statistics.

    SIP Trunk Status: Up or Down status of a SIP trunk to a service provider or application

    Call Traffic Statistics (Calls, Sessions, Capacity Planning, Errors):

    Trunk utilization and SIP Session Capacity

    Call arrival rate

    Call success/failure statistics

    SIP retries statistics

    Transcoding Session Capacity and DSP Utilization

    Call Admission Control

    Voice Quality: Statistics on packet loss, delay and jitter that can be calculated into metrics such as ICPIF, MOS and R-factor scores

    Billing: CDR, call patterns, toll fraud monitoring

     Troubleshooting

General Cisco IOS-XE router troubleshooting using CLI show and debug commands, as well as packet capture methods, are supported.

CUBE supports most of the general Cisco IOS-XE unified communications show and debug commands.

Table 1 provides an overview of CUBE management capabilities that can be used during different operations phases.

Table 1.           Operations Phase and Management Capabilities

Operations Phase

Management capability

Staging/Configuration

  Cisco IOS-XE CLI
  Arcana Manage Express Border Manager (MEBM) Configuration

Installation/Provisioning

  Cisco IOS-XE CLI
  Configuration examples at Interoperability Portal

Change Management/Archiving

  Cisco IOS-XE CLI

Fault Monitoring/Management

  Cisco IOS-XE CLI
  Arcana Manage Express Border Manager (MEBM)
  Vyopta
  Solarwinds
  Any SNMP-based management system

Performance Monitoring/Management

  Cisco IOS-XE CLI (show and debug commands)
  Arcana Manage Express Border Manager (MEBM)
  Vyopta
  Any SNMP-based management system

Troubleshooting

  Cisco IOS-XE CLI (show and debug commands)
  Cisco IOS-XE syslog
  Wireshark
  Voip trace
  Collaboration Solution Analyzer (CSA)

2. Embedded management

Key embedded management capabilities of the Cisco IOS-XE router where CUBE is deployed are covered in this section. This includes:

     CLI

     SNMP

     Syslog

     IP SLA

     EEM

     NetFlow

2.1 CLI Provisioning

This section summarizes the key or common CUBE CLI used to provision basic system functionality. Most specialized CUBE features and deployments have additional CLI to turn on specific features. General Cisco IOS-XE router configuration is assumed known and is not covered here.

Additional in-depth CUBE configuration resources include:

     CUBE configuration guide

     CUBE interoperability portal

     CUBE solution overview presentation

     CUBE configuration examples

2.2 SNMP Monitoring

Simple Network Management Protocol (SNMP) is based on the manager/agent model consisting of an SNMP manager, an SNMP agent, a database of management information, managed SNMP devices and the network protocol. The SNMP manager provides the interface between the human network manager and the management system. The SNMP agent provides the interface between the manager and the physical device being managed.

An SNMP-managed network consists of the following:

     Managed device — A network node that contains an SNMP agent that resides on a managed network. Managed devices collect and store management information and use SNMP to make this information available to the Network Management System (NMS). Managed devices, sometimes called network elements, can include routers and access servers, switches and bridges, hubs, computer hosts, and printers.

     Agent — A network management software module that resides in a managed device. An agent has local knowledge of management information and translates that information into a form compatible with SNMP.

     NMS — Executes applications that monitor and control managed devices. NMSs provide most of the processing and memory resources required for network management. Every managed network must have one or more NMS.

The SNMP agent exchanges network management information with the SNMP manager software that is running on an NMS. The agent responds to requests for information and actions from the managed device (in this case the CUBE router). The agent controls access to the agent’s MIB, the collection of objects that can be viewed or changed by the SNMP manager. By polling managed devices, an SNMP manager collects information on network connectivity, activity, and events.

CUBE monitoring via SNMP includes the following capabilities:

     Router and Interface Health

     Call Traffic Reports

    Trunk utilization and SIP Session Capacity

    Call arrival rate

    Call success/failure statistics

    SIP retries statistics

    Transcoding Session Capacity and DSP Utilization

    MTP Session Capacity

     Call Admission Control

     Voice Quality: Statistics on packet loss, delay and jitter that can be calculated into metrics such as ICPIF, MOS and R-factor scores

2.2.1 Router and Interface Health

These MIBs/OIDs allow you to monitor the physical chassis, interface connectivity, CPU and memory.

     Router Inventory and Health: CPU, memory, flash, modules, software image and release etc.

     Interface Health: General IOS-XE router interfaces, status and packet traffic statistics.

Critical router functions, like routing protocol processing and process packet switching, are handled in memory and share the CPU. Thus, if CPU utilization is very high, it is possible that a routing update cannot be handled or packets are dropped. The CISCO-PROCESS-MIB reports the percentage of the processor in use over a five-minute average.

Table 2.           CISCO-PROCESS-MIB

OID

OID#

New/Changed

Platform

Use/Operation

cpmCPUTotal5minRev

1.3.6.1.4.1.9.9.109.1.1.1.1.8

Original IOS-XE

All

Health Monitoring

Memory use can be monitored using the CISCO-MEMORY-POOL-MIB.

Table 3.           CISCO-MEMORY-POOL-MIB

OID

OID#

New/Changed

Platform

Use/Operation

ciscoMemoryPoolEntry

1.3.6.1.4.1.9.9.48.1.1.1

Baseline

All

Health Monitoring

The status of physical interfaces on the router platform can be monitored using the IF-MIB.

Table 4.           IF-MIB

OID

OID#

New/Changed

Platform

Use/Operation

IfEntry

1.3.6.1.2.1.2.2.1

Baseline

All

Fault Monitoring

2.2.2 SIP Trunk Status

SIP trunk status is an important element of CUBE monitoring. The CISCO-VOICE-DIAL-CONTROL MIB is used to track the list of dial-peers configured in CUBE.

The OID for the dial-peer table is “cvPeerCfgTable” "1.3.6.1.4.1.9.9.63.1.2.1"

For every dial-peer configured, an entry is created under the cvPeerCfgTable. The dial-peer tag is used as the index. A corresponding entry for the dial-peer is also created under the IF-MIB ifTable. The cvPeerCfgIfIndex (OID “1.3.6.1.4.1.9.9.63.1.2.1.1.2”) value in the dial-peer entry identifies the index for the entry in the IF-MIB ifTable.

The ifOperstatus (OID “1.3.6.1.2.1.2.2.1.8 “) value in the IF-MIB ifTable entry identifies the status of the dial-peer.

Traps are generated when the dial-peer moves from “up” to “testing” state and vice versa.

The IF-MIB “linkdown” (OID “1.3.6.1.6.3.1.1.5.3”) trap is generated when the dial-peer moves to busy out state. The trap will include the “ifIndex” and “ifOperStatus” values. The “ifIndex” value maps to the “cvPeerCfgIfIndex” value in the dial-peer table.

The IF-MIB “linkup” (1.3.6.1.6.3.1.1.5.4) trap is generated when the dial-peer moves from busy out to active state. The trap will include the “ifIndex” and “ifOperStatus” values. The “ifIndex” value maps to the “cvPeerCfgIfIndex” value in the dial-peer table.

When the linkup or linkdown trap are generated, the following steps need to performed to determine if it is related to dial-peer.

Check if the ifType value for the ifIndex is equal to voiceOverIp(104). This determines that the interface is associated with the voip dial-peer. For example if the trap is generated with ifIndex 5, then 1.3.6.1.2.1.2.2.1.3.5 should be equal to voiceOverIp(104).

Walk through the dial-control-mib peerCfgTable and find the entry whose cvPeerCfgIndex matches the ifIndex value received in the trap. The matching peerCfgTable index points to the dial-peer tag for which the trap has been received.

2.2.3 Call Traffic Statistics

A key element of CUBE monitoring is call traffic reports, both for the volume of calls over time, or for monitoring of call arrival rates. This is useful for various business purposes, including:

     Trunk utilization, both real-time and historical

     Capacity planning

     Troubleshooting

     Highlighting errors occurring in call routing or call handling that may indicate a network outage, dial-plan deficiencies, or perhaps an architectural call flow that is not implemented correctly

     Detecting call spikes, caused by both normal (an uptick in traffic due to an advertisement or other business event) and malicious (a SIP DOS attack) traffic patterns

CUBE call traffic reports can be provided by information in several SNMP MIBs, some of which have been available historically in all Cisco IOS-XE releases, and others specifically introduced with CUBE to aid in traffic reporting.

     Trunk utilization and SIP session capacity statistics

     Call arrival rate statistics

     Call success/failure statistics

     SIP error and timeout/retry statistics

     DSP utilization and transcoding session capacity

     MTP utilization and session capacity

Cisco IOS-XE voice/video call SNMP information is generally kept in the set of MIBs given below. These MIBs are used for TDM voice calls as well as VoIP calls. Some OIDs are only populated for certain types of calls.

     DIAL-CONTROL-MIB

     CISCO-DIAL-CONTROL-MIB

     CISCO-VOICE-DIAL-CONTROL-MIB

     CISCO-VOICE-COMMON-DIAL-CONTROL-MIB

     CISCO-CALL-HISTORY-MIB (this MIB is only populated for ISDN calls on TDM voice gateways and therefore does not apply to CUBE and will not be discussed further here.)

These MIBs generally provide information on:

     Currently active calls: Real-time statistics of call activity

     Call history: Historical statistics after calls have disconnected (similar to CDR)

Table 5.           CISCO IOS-XE MIBs that Contain Active Call Information

MIB

OID

Table Name

Number of Entries per Call

DIAL-CONTROL-MIB

1.3.6.1.2.1.10.21

callActiveTable

2

CISCO-VOICE-COMMON-DIAL-CONTROL-MIB

1.3.6.1.4.1.9.10.55

cvCommonDcCallActiveTable

2

CISCO-VOICE-DIAL-CONTROL-MIB

1.3.6.1.4.1.9.9.63

cvCallActiveTable

0 (used for TDM GW calls only)

CISCO-VOICE-DIAL-CONTROL-MIB

1.3.6.1.4.1.9.9.63

cvVoIPCallActiveTable

2

Table 6.           CISCO IOS-XE MIBs that Contain Historical Call Information

MIB

OID

Call History

Number of Entries per Call

DIAL-CONTROL-MIB

1.3.6.1.2.1.10.21

callHistoryTable

Not implemented, do not use

CISCO-DIAL-CONTROL-MIB

1.3.6.1.4.1.9.10.25

cCallHistory

2

CISCO-VOICE-COMMON-DIAL-CONTROL-MIB

1.3.6.1.4.1.9.10.55

cvCommonDcCallHistoryTable

2

CISCO-VOICE-DIAL-CONTROL-MIB

1.3.6.1.4.1.9.9.63

cvCallHistoryTable

0 (used for TDM GW calls only)

CISCO-VOICE-DIAL-CONTROL-MIB

1.3.6.1.4.1.9.9.63

cvVoIPCallHistory

2

The following “show call active” commands provide information on active voice, video and fax calls in the system:

show call active?

  fax    show all active calls for fax store & forward

  media  show all active calls for media

  video  show all active calls for video

  voice  show all active calls for voice

!

show call active video ?

  brief           show brief version of active video calls

  compact         show compact version of active video calls

  id              show only call with specified id

!

show call active fax ?

  brief    show brief version of active fax calls

  compact  show compact version of active fax calls

2.2.3.1 Real-time Trunk Utilization

Various aspects of real-time Trunk Utilization statistics on currently active calls are available from the MIBs and OIDs covered in this section.

When a callActiveTable (1.3.6.1.2.1.10.21.1.3.1) entry is created for a call, an associated cvCallActiveTable (1.3.6.1.4.1.9.9.63.1.3.1) and cvCommonDcCallActiveTable(1.3.6.1.4.1.9.10.55.1.1.1) entries are created. They are indexed by the callActiveSetupTime (1.3.6.1.2.1.10.21.1.3.1.1.1) and callActiveIndex (1.3.6.1.2.1.10.21.1.3.1.1.2) as defined in DIAL-CONTROL-MIB.

The DIAL-CONTROL-MIB provides:

     RFC-2128 information

     Monitoring of active calls on a particular dial peer

     Packet received/transmitted statistics for active calls

The usefulness of the DIAL-CONTROL-MIB entries (callActiveTransmitPackets, callActiveTransmitBytes, callActiveReceivePackets, callActiveReceiveBytes) is essentially for packet received and transmitted statistics. For most other call parameters, the information provided in the CISCO-VOICE-DIAL-CONTROL-MIB is most useful.

Table 7.           Real-time Trunk Utilization: DIAL-CONTROL-MIB

OID

OID#

New/Changed

Platform

Use/Operation

dialCtlPeerStatsTable

1.3.6.1.2.1.10.21.1.2.2

Baseline

ISR4K, ISR1100, Cat8K, CSR1K, ASR

Provides statistics on overall dial-peer use, indexed by dial-peer number.

callActiveTable

1.3.6.1.2.1.10.21.1.3.1

Baseline

ISR4K, ISR1100, Cat8K, CSR1K, ASR

Provides packet statistics on active calls, indexed by callActiveSetupTime and callActiveIndex.

The CISCO-VOICE-DIAL-CONTROL-MIB provides the number of active calls based on:

     Protocol

     Dial-Peer

     Interface

Table 8.           Real-time Trunk Utilization: CISCO-VOICE-DIAL-CONTROL-MIB

OID

OID#

New/Changed

Platform

Use/Operation

cvVoIPCallActiveTable

1.3.6.1.4.1.9.9.63.1.3.2

Baseline

ISR4K, ISR1100, Cat8K, CSR1K, ASR

Provides statistics on active VoIP calls, indexed by callActiveSetupTime and callActiveIndex.

cvCallVolume

1.3.6.1.4.1.9.9.63.1.3.8

Baseline

ISR4K, ISR1100, Cat8K, CSR1K, ASR

Total, per-protocol, per-dial-peer and per-interface call active statistics.

Total Trunk Utilization

A snapshot summary of overall call active statistics on the platform is given by the cvCallVolConnTotalActiveConnections (1.3.6.1.4.1.9.9.63.1.3.8.2) OID.

More detailed information per call (packet statistics, VAD, SRTP etc.) is given in the cvVoIPCallActiveEntry (1.3.6.1.4.1.9.9.63.1.3.2.1) OID.

Trunk Utilization by Protocol

A snapshot of call active statistics per protocol is given by the cvCallVolConnEntry (1.3.6.1.4.1.9.9.63.1.3.8.1.1) OID. The cvCallVolConnIndex (1.3.6.1.4.1.9.9.63.1.3.8.1.1.1) defines the protocol type, H.323 = 1, SIP = 2. Therefore:

     SIP(2) call statistics are in the CvCallVolConnActiveConnection.2 (1.3.6.1.4.1.9.9.63.1.3.8.1.1.2.2) OID

Trunk Utilization by Dial-Peer

A snapshot of call active statistics per dial-peer is given by the cvCallVolPeerEntry (1.3.6.1.4.1.9.9.63.1.3.8.4.1) OID. This table augments the dial-peer configuration table in the cvPeerCfgTable (1.3.6.1.4.1.9.9.63.1.2.1) OID, and uses the dial-peer tag as an index. Therefore:

     Incoming call statistics for dial-peer 200 are in the cvCallVolPeerIncomingCalls.200 (1.3.6.1.4.1.9.9.63.1.3.8.4.1.1.200) OID

     Outgoing call statistics for dial-peer 200 are in cvCallVolPeerOutgoingCalls.200 (1.3.6.1.4.1.9.9.63.1.3.8.4.1.2.200) OID

Trunk Utilization by Interface

A snapshot of call active statistics per interface is given by the cvCallVolIfTableEntry (1.3.6.1.4.1.9.9.63.1.3.8.5.1) OID. This table is indexed by the interface number using the ifIndex (1.3.6.1.2.1.2.2.1.1) OID in the IF-MIB. Therefore:

     Incoming call statistics for interface 5 are in the cvCallVolMediaIncomingCalls.5 (1.3.6.1.4.1.9.9.63.1.3.8.5.1.1.5) OID

     Outgoing call statistics for interface 5 are in cvCallVolMediaOutgoingCalls.5 (1.3.6.1.4.1.9.9.63.1.3.8.5.1.2.5) OID

The cvCallVolume OID in the CISCO-VOICE-DIAL-CONTROL-MIB contains the following call volume information:

Table 9.           CISCO-VOICE-DIAL-CONTROL-MIB cvCallVolume Information

OID

OID#

Use/Operation

cvCallVolConnIndex

1.3.6.1.4.1.9.9.63.1.3.8.1.1.1

Index to the cvCallVolConnTable. A value of 1 denotes H.323 calls, and 2 SIP calls.

cvCallVolConnActiveConnection

1.3.6.1.4.1.9.9.63.1.3.8.1.1.2

Number of calls active of the type determined by cvCallVolConnIndex.

cvCallVolConnTotalActiveConnections

1.3.6.1.4.1.9.9.63.1.3.8.2

Total number of active calls on the platform.

cvCallVolPeerIncomingCalls

1.3.6.1.4.1.9.9.63.1.3.8.4.1.1

Number of active incoming calls for a dial-peer.

cvCallVolPeerOutgoingCalls

1.3.6.1.4.1.9.9.63.1.3.8.4.1.2

Number of active outcoming calls for a dial-peer.

cvCallVolMediaIncomingCalls

1.3.6.1.4.1.9.9.63.1.3.8.5.1.1

Number of active incoming calls for an interface.

cvCallVolMediaOutgoingCalls

1.3.6.1.4.1.9.9.63.1.3.8.5.1.2

Number of active outgoing calls for an interface.

2.2.3.2 Historical Trunk Utilization

Historical Trunk Utilization statistics on completed calls are available from the MIBs and OIDs covered in this section. Alternatively, you can also use the Real-time Trunk Utilization statistics in the previous section and store this info to provide your own aggregation and trending information. Up to 1200 call history records are stored in memory in a circular buffer.

Table 10.       Historical Trunk Utilization MIB Information

MIB

OID

OID#

New/Changed

Platform

CISCO-DIAL-CONTROL-MIB

cCallHistoryTable

1.3.6.1.4.1.9.10.25.1.4.3

Baseline

ISR4K, ISR1100, Cat8K, CSR1K, ASR

CISCO-VOICE-DIAL-CONTROL-MIB

cvVoIPCallHistoryTable

1.3.6.1.4.1.9.9.63.1.4.2

Baseline

ISR4K, ISR1100, Cat8K, CSR1K, ASR

CISCO-VOICE-COMMON-DIAL-CONTROL-MIB

cvCommonDcCallHistory

1.3.6.1.4.1.9.10.55.1.2.1

Baseline

ISR4K, ISR1100, Cat8K, CSR1K, ASR

2.2.3.3 Call Arrival Rate

Call arrival rate and call spikes can be monitored using the CISCO-VOICE-DIAL-CONTROL-MIB MIB information covered in this section.

Table 11.       Call Arrival Rate MIB Information

OID

OID#

New/Changed

Platform

cvCallRateMonitor

1.3.6.1.4.1.9.9.63.1.3.11

Baseline

ISR4K, ISR1100, Cat8K, CSR1K, ASR

By default call rate information is not gathered and the MIB information is empty. To turn on call rate monitoring, use the cvCallRateMonitorEnable (1.3.6.1.4.1.9.9.63.1.3.11.1) OID and set the monitoring period with the cvCallRateMonitorTime (1.3.6.1.4.1.9.9.63.1.3.11.2) OID. There is no facility to turn monitoring on or off via CLI.

The cvCallRateMonitor OID in the CISCO-VOICE-DIAL-CONTROL-MIB contains the following call rate information.

Table 12.       Call Arrival Rate: CISCO-VOICE-DIAL-CONTROL-MIB

OID

OID#

Use/Operation

cvCallRateMonitorEnable

1.3.6.1.4.1.9.9.63.1.3.11.1

A value of TRUE starts computation of call rate information. A value of FALSE turns it off.

cvCallRateMonitorTime

1.3.6.1.4.1.9.9.63.1.3.11.2

Value can from 1 to 12 – each value denotes a time unit of 5 seconds. That is, a value of 1 means 5 seconds, a value of 2 means 10 seconds. etc.

cvCallRate

1.3.6.1.4.1.9.9.63.1.3.11.3

Number of calls connected during the last monitoring period duration.

cvCallRateHiWaterMark

1.3.6.1.4.1.9.9.63.1.3.11.4

Peak value in any given cvCallRateMonitorTime duration if cvCallRateMonitorEnable is set to TRUE.

2.2.3.4 Call Success/Failure Statistics

Successful and failed call counts can be monitored for trending or troubleshooting purposes using the MIB information covered in this section.

Table 13.       Call Success/Failure MIB Information

MIB

OID

OID#

New/Changed

Platform

DIAL-CONTROL-MIB

dialCtlPeerStatsTable

1.3.6.1.2.1.10.21.1.2.2

Baseline

ISR4K, ISR1100, Cat8K, CSR1K, ASR

CISCO-SIP-UA-MIB

cSipStats

1.3.6.1.4.1.9.9.152.1.2

Baseline

ISR4K, ISR1100, Cat8K, CSR1K, ASR

The DIAL-CONTROL-MIB provides information per dial-peer for both H.323 and SIP using the following OIDs:

     Success:

    dialCtlPeerStatsSuccessCalls (1.3.6.1.2.1.10.21.1.2.2.1.3)

    dialCtlPeerStatsAcceptCalls (1.3.6.1.2.1.10.21.1.2.2.1.5)

     Failure:

    dialCtlPeerStatsFailCalls (1.3.6.1.2.1.10.21.1.2.2.1.4)

    dialCtlPeerStatsRefuseCalls (1.3.6.1.2.1.10.21.1.2.2.1.6)

The protocol that a call uses can be found by associating the dial-peer entry (dialCtlPeerStatsEntry, 1.3.6.1.2.1.10.21.1.2.2.1 OID) in the DIAL-CONTROL-MIB with the corresponding dial-peer entry (cvVoIPPeerCfgEntry, 1.3.6.1.4.1.9.9.63.1.2.3.1 OID) in the CISCO-VOICE-DIAL-CONTROL-MIB. The cvVoIPPeerCfgSessionProtocol (1.3.6.1.4.1.9.9.63.1.2.3.1.1) OID in the CISCO-VOICE-DIAL-CONTROL-MIB uses a value of “Cisco (2)” for H.323 and “sip (3)” for SIP.

The CISCO-SIP-UA-MIB provides information on SIP call success/failure using the following OIDs:

     Success

    cSipStatsSuccess (1.3.6.1.4.1.9.9.152.1.2.2)

    cSipStatsRedirect 1.3.6.1.4.1.9.9.152.1.2.3

     Failure

    cSipStatsErrClient 1.3.6.1.4.1.9.9.152.1.2.4 (4xx errors)

    cSipStatsErrServer 1.3.6.1.4.1.9.9.152.1.2.5 (5xx errors)

    cSipStatsGlobalFail 1.3.6.1.4.1.9.9.152.1.2.6 (6xx errors)

     Retry/Timeouts

    cSipStatsRetry 1.3.6.1.4.1.9.9.152.1.2.8 (retries/timeouts)

Table 14.       CISCO-SIP-UA-MIB MIB Fields for 4xx, 5xx and 6xx SIP Responses

OID

OID#

SIP 4xx Error

cSipStatsClientBadRequestIns

1.3.6.1.4.1.9.9.152.1.2.4.1

400

cSipStatsClientBadRequestOuts

1.3.6.1.4.1.9.9.152.1.2.4.2

400

cSipStatsClientUnauthorizedIns

1.3.6.1.4.1.9.9.152.1.2.4.3

401

cSipStatsClientUnauthorizedOuts

1.3.6.1.4.1.9.9.152.1.2.4.4

401

cSipStatsClientPaymentReqdIns

1.3.6.1.4.1.9.9.152.1.2.4.5

402

cSipStatsClientPaymentReqdOuts

1.3.6.1.4.1.9.9.152.1.2.4.6

402

cSipStatsClientForbiddenIns

1.3.6.1.4.1.9.9.152.1.2.4.7

403

cSipStatsClientForbiddenOuts

1.3.6.1.4.1.9.9.152.1.2.4.8

403

cSipStatsClientNotFoundIns

1.3.6.1.4.1.9.9.152.1.2.4.9

404

cSipStatsClientNotFoundOuts

1.3.6.1.4.1.9.9.152.1.2.4.10

404

cSipStatsClientMethNotAllowedIns

1.3.6.1.4.1.9.9.152.1.2.4.11

405

cSipStatsClientMethNotAllowedOuts

1.3.6.1.4.1.9.9.152.1.2.4.12

405

cSipStatsClientNotAcceptableIns

1.3.6.1.4.1.9.9.152.1.2.4.13

406

cSipStatsClientNotAcceptableOuts

1.3.6.1.4.1.9.9.152.1.2.4.14

406

cSipStatsClientProxyAuthReqdIns

1.3.6.1.4.1.9.9.152.1.2.4.15

407

cSipStatsClientProxyAuthReqdOuts

1.3.6.1.4.1.9.9.152.1.2.4.16

407

cSipStatsClientReqTimeoutIns

1.3.6.1.4.1.9.9.152.1.2.4.17

408

cSipStatsClientReqTimeoutOuts

1.3.6.1.4.1.9.9.152.1.2.4.18

408

cSipStatsClientConflictIns

1.3.6.1.4.1.9.9.152.1.2.4.19

409

cSipStatsClientConflictOuts

1.3.6.1.4.1.9.9.152.1.2.4.20

409

cSipStatsClientGoneIns

1.3.6.1.4.1.9.9.152.1.2.4.21

410

cSipStatsClientGoneOuts

1.3.6.1.4.1.9.9.152.1.2.4.22

410

cSipStatsClientLengthRequiredIns

1.3.6.1.4.1.9.9.152.1.2.4.23

411

cSipStatsClientLengthRequiredOuts

1.3.6.1.4.1.9.9.152.1.2.4.24

411

cSipStatsClientReqEntTooLargeIns

1.3.6.1.4.1.9.9.152.1.2.4.25

413

cSipStatsClientReqEntTooLargeOuts

1.3.6.1.4.1.9.9.152.1.2.4.26

413

cSipStatsClientReqURITooLargeIns

1.3.6.1.4.1.9.9.152.1.2.4.27

414

cSipStatsClientReqURITooLargeOuts

1.3.6.1.4.1.9.9.152.1.2.4.28

414

cSipStatsClientNoSupMediaTypeIns

1.3.6.1.4.1.9.9.152.1.2.4.29

415

cSipStatsClientNoSupMediaTypeOuts

1.3.6.1.4.1.9.9.152.1.2.4.30

415

cSipStatsClientBadExtensionIns

1.3.6.1.4.1.9.9.152.1.2.4.31

420

cSipStatsClientBadExtensionOuts

1.3.6.1.4.1.9.9.152.1.2.4.32

420

cSipStatsClientTempNotAvailIns

1.3.6.1.4.1.9.9.152.1.2.4.33

480

cSipStatsClientTempNotAvailOuts

1.3.6.1.4.1.9.9.152.1.2.4.34

480

cSipStatsClientCallLegNoExistIns

1.3.6.1.4.1.9.9.152.1.2.4.35

481

cSipStatsClientCallLegNoExistOuts

1.3.6.1.4.1.9.9.152.1.2.4.36

481

cSipStatsClientLoopDetectedIns

1.3.6.1.4.1.9.9.152.1.2.4.37

482

cSipStatsClientLoopDetectedOuts

1.3.6.1.4.1.9.9.152.1.2.4.38

482

cSipStatsClientTooManyHopsIns

1.3.6.1.4.1.9.9.152.1.2.4.39

483

cSipStatsClientTooManyHopsOuts

1.3.6.1.4.1.9.9.152.1.2.4.40

483

cSipStatsClientAddrIncompleteIns

1.3.6.1.4.1.9.9.152.1.2.4.41

484

cSipStatsClientAddrIncompleteOuts

1.3.6.1.4.1.9.9.152.1.2.4.42

484

cSipStatsClientAmbiguousIns

1.3.6.1.4.1.9.9.152.1.2.4.43

485

cSipStatsClientAmbiguousOuts

1.3.6.1.4.1.9.9.152.1.2.4.44

485

cSipStatsClientBusyHereIns

1.3.6.1.4.1.9.9.152.1.2.4.45

486

cSipStatsClientBusyHereOuts

1.3.6.1.4.1.9.9.152.1.2.4.46

486

cSipStatsClientReqTermIns

1.3.6.1.4.1.9.9.152.1.2.4.47

487

cSipStatsClientReqTermOuts

1.3.6.1.4.1.9.9.152.1.2.4.48

487

cSipStatsClientNoAcceptHereIns

1.3.6.1.4.1.9.9.152.1.2.4.49

488

cSipStatsClientNoAcceptHereOuts

1.3.6.1.4.1.9.9.152.1.2.4.50

488

cSipStatsClientBadEventIns

1.3.6.1.4.1.9.9.152.1.2.4.51

489

cSipStatsClientBadEventOuts

1.3.6.1.4.1.9.9.152.1.2.4.52

489

cSipStatsClientSTTooSmallIns

1.3.6.1.4.1.9.9.152.1.2.4.53

422

cSipStatsClientSTTooSmallOuts

1.3.6.1.4.1.9.9.152.1.2.4.54

422

cSipStatsClientReqPendingIns

1.3.6.1.4.1.9.9.152.1.2.4.55

491

cSipStatsClientReqPendingOuts

1.3.6.1.4.1.9.9.152.1.2.4.56

491

cSipStatsServerIntErrorIns

1.3.6.1.4.1.9.9.152.1.2.5.1

500

cSipStatsServerIntErrorOuts

1.3.6.1.4.1.9.9.152.1.2.5.2

500

cSipStatsServerNotImplementedIns

1.3.6.1.4.1.9.9.152.1.2.5.3

501

cSipStatsServerNotImplementedOuts

1.3.6.1.4.1.9.9.152.1.2.5.4

501

cSipStatsServerBadGatewayIns

1.3.6.1.4.1.9.9.152.1.2.5.5

502

cSipStatsServerBadGatewayOuts

1.3.6.1.4.1.9.9.152.1.2.5.6

502

cSipStatsServerServiceUnavailIns

1.3.6.1.4.1.9.9.152.1.2.5.7

503

cSipStatsServerServiceUnavailOuts

1.3.6.1.4.1.9.9.152.1.2.5.8

503

cSipStatsServerGatewayTimeoutIns

1.3.6.1.4.1.9.9.152.1.2.5.9

504

cSipStatsServerGatewayTimeoutOuts

1.3.6.1.4.1.9.9.152.1.2.5.10

504

cSipStatsServerBadSipVersionIns

1.3.6.1.4.1.9.9.152.1.2.5.11

505

cSipStatsServerBadSipVersionOuts

1.3.6.1.4.1.9.9.152.1.2.5.12

505

cSipStatsServerPrecondFailureIns

1.3.6.1.4.1.9.9.152.1.2.5.13

580

cSipStatsServerPrecondFailureOuts

1.3.6.1.4.1.9.9.152.1.2.5.14

580

cSipStatsGlobalBusyEverywhereIns

1.3.6.1.4.1.9.9.152.1.2.6.1

600

cSipStatsGlobalBusyEverywhereOuts

1.3.6.1.4.1.9.9.152.1.2.6.2

600

cSipStatsGlobalDeclineIns

1.3.6.1.4.1.9.9.152.1.2.6.3

603

cSipStatsGlobalDeclineOuts

1.3.6.1.4.1.9.9.152.1.2.6.4

603

cSipStatsGlobalNotAnywhereIns

1.3.6.1.4.1.9.9.152.1.2.6.5

604

cSipStatsGlobalNotAnywhereOuts

1.3.6.1.4.1.9.9.152.1.2.6.6

604

cSipStatsGlobalNotAcceptableIns

1.3.6.1.4.1.9.9.152.1.2.6.7

606

cSipStatsGlobalNotAcceptableOuts

1.3.6.1.4.1.9.9.152.1.2.6.8

606

2.2.3.5 Transcoding Session Capacity and DSP Utilization

Real-time call statistics for transcoding sessions, and the DSPs used by transcoding, are available in the CISCO-DSP-MGMT-MIB OIDs covered in this section, including:

     Total Statistics

    Transcoding sessions configured

    Transcoding sessions used

    Transcoding session available (unused)

     Per-profile Transcoding Statistics

    Transcoding sessions configured

    Transcoding sessions used

    Transcoding session available (unused)

Table 15.       Transcoding Session Capacity and DSP Utilization MIB Information

OID

OID#

Use/Operation

cdspTotAvailTranscodeSess

1.3.6.1.4.1.9.9.86.1.7.1

Total of all transcoding sessions configured in all profiles.

cdspTotUnusedTranscodeSess

1.3.6.1.4.1.9.9.86.1.7.2

Total of all unused transcoding sessions across all configured profiles.

cdspTranscodeProfileMaxConfSess

1.3.6.1.4.1.9.9.86.1.6.3.1.2

Number of transcoding sessions configured for the DSP profile given in cdspTranscodeProfileId.

cdspTranscodeProfileMaxAvailSess

1.3.6.1.4.1.9.9.86.1.6.3.1.3

Number of transcoding sessions available for the DSP profile given in cdspTranscodeProfileId.

The currently active, or used, total transcoding session count is given by:

cdspTotAvailTranscodeSess – cdspTotUnusedTranscodeSess

The currently active, or used, transcoding session count per DSP profile is given by:

cdspTranscodeProfileMaxConfSess – cdspTranscodeProfileMaxAvailSess

2.2.4 Voice Quality MIBs

Voice quality can be monitored by the packet loss, delay and jitter statistics given in the MIB and OID convered in this section. These basic metrics can be calculated and summarized into metrics such as ICPIF, MOS and R-factor scores by your NMS system.

Packet statistics are available in the following MIBs:

     CISCO-VOICE-DIAL-CONTROL-MIB

     CISCO-RTTMON-ICMP-MIB

     CISCO-RTTMON-MIB

     CISCO-RTTMON-RTP-MIB

     CISCO-MEDIA-QUALITY-MIB

The CISCO-VOICE-DIAL-CONTROL-MIB provides packet statistics both for currently active calls (real-time statistics) as well for historical trending (calls that are already completed).

Table 16.       Voice Quality: CISCO-VOICE-DIAL-CONTROL-MIB

OID

OID#

New/Changed

Use/Operation

cvVoIPCallActiveTable

11.3.6.1.4.1.9.9.63.1.3.2

Baseline

Real-time voice quality statistics on currently active calls.

cvVoIPCallHistoryTable

1.3.6.1.2.1.10.63.1.4.2

Baseline

Historical voice quality statistics for already completed calls.

 

MIB

OID

OID#

Use/Operation

CISCO-MEDIA-QUALITY-MIB

cmqVoIPCallActiveRxPred107RMosConv

1.3.6.1.4.1.9.9.769.1.1.1.1.31

MOS

The MOS Conversation Quality Estimate is computed on a running basis with a new value every 10 seconds of received speech. A value of 0 indicates an invalid score and a positive value indicates a valid score.

The IP RTTMON MIBs provide various levels of generic packet and transmission statistics based on IP SLA probes configured on the router (using the IP SLAs RTP-Based VoIP Operation feature).

Table 17.       Voice Quality: RTTMON MIBs

MIB

OID

OID#

Use/Operation

CISCO-RTTMON-ICMP-MIB

rttMonLatestIcmpJitterAvgJitter

1.3.6.1.4.1.9.9.42.1.5.4.1.44

ICMP Jitter

CISCO-RTTMON-MIB

rttMonJitterStatsAvgJitter

1.3.6.1.4.1.9.9.42.1.3.5.1.62

UDP Jitter

CISCO-RTTMON-RTP-MIB

rttMonRtpStatsIAJitterDSAvg

1.3.6.1.4.1.9.9.42.1.3.6.1.5

RTP Jitter

2.3 SNMP Traps

There are currently no SNMP traps implemented for CUBE.

2.4 Syslog Messages

Syslog is a method to collect messages from devices to a server running a syslog daemon. Logging to a central syslog server helps in aggregation of logs and alerts. Cisco devices can send their log messages to a Unix-style SYSLOG service. A SYSLOG service simply accepts messages, and stores the messages in files or prints according to a simple configuration file. These messages are useful in routine troubleshooting and in incident handling.

Cisco devices have literally thousands of different messages that may be sent to a syslog server when an identified event occurs in the network. Events range from catastrophic (priority 0) to informational (priority 6).

The syslog daemon handles the recording of syslog messages and events in log files. The syslog message is composed of two main parts:

     Header — Contains the date and time information along with the IP address or the computer name from which the message has originated.

     Message — Includes the program or subsystem name and the message. The program or subsystem name and the message are separated by a colon.

The following is a summary of voice and call related Syslog message categories. Further information on individual messages within these categories can be found on Cisco.com in the Cisco IOS-XE System Messages documentation.

     CALL_CONTROL Messages

     CALL_MGMT Messages

     CALLRECORD Messages

     CALLTREAT Messages

     CALLTREAT_NOSIGNAL Messages

     CCM Messages

     CSM Messages

     CSM_TGRM Messages

     CSM_TRUNK_MGR Messages

     CSM_VOICE Messages

     DSMP Messages

     DSP_CONN Messages

     DSPDUMP Messages

     DSPFARM Messages

     DSPRM Messages

     FLEX_DNLD Messages

     FLEXDSPRM Messages

     HWCONF Messages

     HWECAN Messages

     IVR Messages

     IVR_MSB Messages

     IVR_NOSIGNALING Messages

     PVDM Messages

     PVDMPWR Messages

     SIP Messages

     VOICE_CODEC Messages

     VOICE_ELOG Messages

     VOICE_FILE_ACCT Messages

     VOICE_IEC Messages

     VOICE_RC Messages

     VOICE_UTIL Messages

     VOIPAAA Messages

     VOIPFIB Messages

     VOIP_RTP Messages

     VTSP Messages

Table 18.       Syslog Error Message Severity Levels

Level

Description

System Impact

0

Emergency

System unusable

1

Alert

Immediate action needed

2

Critical

Critical condition

3

Error

Error condition

4

Warning

Warning condition

5

Notification

Normal but significant condition

6

Informational

Informational message only

7

Debugging

Appears during debugging only

2.5 Embedded Event Manager (EEM)

The Cisco IOS-XE Embedded Event Manager (EEM) is a unique subsystem within Cisco IOS-XE Software. EEM is a powerful and flexible tool to automate tasks and customize the behavior of Cisco IOS-XE Software and the operation of the device. You can use EEM to create and run programs or scripts directly on a router or switch. The scripts are referred to as EEM policies and can be programmed using a simple Command-Line-Interface (CLI)-based interface or using a scripting language called Tool Command Language (Tcl). EEM allows you to harness the significant intelligence within Cisco IOS-XE Software to respond to real-time events, automate tasks, create customer commands, and take local automated action based on conditions detected by the Cisco IOS-XE Software itself.

More information is available at www.cisco.com/go/eem.

In addition to EEM, Diagnostic Signatures are a good way to automate log collection. The following link is a good example of diagnostic signatures in Webex Calling deployments:

https://www.cisco.com/c/en/us/support/docs/storage-networking/call-home/215214-deploy-diagnostic-signatures-on-cube-in.html

2.6 IP SLA

Cisco IOS-XE IP Service Level Agreements (SLAs) is a network performance measurement and diagnostics tool that uses active monitoring, which generates traffic in a reliable and predictable manner to measure network performance.

A summary of IP SLA capabilities is given below. More information is available at www.cisco.com/go/ipsla.

Table 19.       Cisco IOS-XE IP SLAs Operations and Applications

IP SLA

Measurement Capability

Key Applications

RTP-Based VoIP

  Interarrival jitter
  Estimated R factor
  MOS-CQ
  Round-Trip Time (RTT) latency
  Packet loss
  Packets missing in action
  One-way latency
  Frame loss
  MOS-LQ (destination-to-source)

Networks that carry voice and video traffic

UDP Jitter for VoIP

  Round-trip delay, one-way delay, one-way jitter, one-way packet loss
  VoIP codec simulation G.711 μ-law, G.711 a-law, and G.729A
  MOS and ICPIF voice quality scoring capability
  One-way delay requires time synchronization between the Cisco IOS-XE IP SLAs source and target routers

Most common operations for networks that carry voice traffic, such as IP backbones

UDP Echo

Round-trip delay

Accurate measurement of response time of UDP traffic

UDP Jitter

  Round-trip delay, one-way delay, one-way jitter, one-way packet loss
  One-way delay requires time synchronization between the Cisco IOS-XE IP SLAs source and target routers

Most common operations for networks that carry voice or video traffic, such as IP backbones

TCP Connect

Connection Time

Server and application performance monitoring

Domain Name System (DNS)

DNS Lookup Time

DNS performance monitoring, trouble-shooting

Dynamic Host Configuration Protocol (DHCP)

Round-trip time to get an IP address

Response time to a DHCP server

Internet Control Message Protocol (ICMP) Echo

Round-trip delay

Trouble-shooting and availability measurement

ICMP Path Echo

Round-trip delay for the full path

Trouble-shooting

ICMP Path Jitter

Round-trip delay, jitter and packet loss for the full path

Trouble-shooting

2.7 NetFlow

Cisco IOS-XE NetFlow efficiently provides a key set of services for IP applications, including network traffic accounting, usage-based network billing, network planning, security, Denial of Service monitoring capabilities, and network monitoring. NetFlow provides valuable information about network users and applications, peak usage times, and traffic routing.

More information is available at www.cisco.com/go/netflow.

3. Supported Management Applications

The following table provides information on Management Applications that can be used to manage CUBE.

Table 20.       CUBE Management Applications

Management Application

Applicable Operations Phases

Application Description

Website

Arcana iManage

Provisioning, Monitoring, Change Management

A provisioning and monitoring solution to help companies deploy advanced services based on the Cisco Integrated Services Router and Unified Communications platforms.

https://www.arcananet.com/

Solarwinds

Fault and Performance Monitoring

Offers network managers a comprehensive and easy-to-understand view of network health - From fault and performance monitoring to configuration and IP address management

https://www.solarwinds.com/

Vyopta

Performance Monitoring

A UC network performance management and service assurance solution

https://www.vyopta.com/product/what-we-cover/cisco/

Nagios

Performance Monitoring

Network monitoring

https://www.nagios.org/

PRTG

Performance Monitoring

Network monitoring

https://www.paessler.com/prtg

4. Management Recommendations

All general Cisco IOS-XE router management (provisioning, monitoring and troubleshooting) methods and information are applicable to CUBE.

4.1 Provisioning Recommendations

CUBE can be provisioned using either the Cisco IOS-XE router CLI or by using a graphical provisioning management application.

4.1.1 Command Line (CLI)

General provisioning of CUBE is done via Cisco IOS-XE CLI. The CUBE IOS-XE CLI Configuration Guide can be found at https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book.pdf.

4.1.2 Graphical (GUI)

Certain routing configuration can be provisioned using the router GUI. The GUI can be accessed by browsing to the router IP address.

Dashboard

Arcana Manage Express Border Manager offers CUBE related configuration using GUI. General information on MEBM can be found at https://www.arcananet.com/border-manager.

The following image shows some of the MEBBM configuration, Reporting and Troubleshooting capabilities.

Border Manager

4.2 Monitoring Recommendations

The following aspects of CUBE are recommended to be monitored.

     Router Inventory and Health

     Interface Health

     SIP Trunk Status

     Call Traffic

    Trunk utilization and H.323/SIP Session Capacity

    Call arrival rate

    Call success/failure statistics

    SIP retries statistics

    Transcoding Session Capacity and DSP Utilization

    Media Termination Point (MTP) Session Capacity

     Call Admission Control

     Voice Quality

     Billing/CDR

The following table lists key “show” commands giving output that enables you to monitor CUBE health, traffic and activity.

Table 21.       Key “show” Commands on CUBE

Category

Command

Information Provided

Configuration

show version

Displays the version of the image on the router

show flash:

Displays information about flash: file system

show ip interface brief

Displays brief summary of IP status and configuration

show startup-config

Displays the startup configuration on the router

show running-config

Displays the present/running con configuration on the router

show debug

Displays the debugs currently enabled

show voice iec desc <>

Displays definition of an Internal Error Code

show logging

Displays the contents of logging buffers

Traffic

show call active voice

Displays complete details of an active call like media settings, call statistics, SRTP on/off etc.

show call active voice brief

Displays a brief version of active voice calls, e.g. transmitted and received packets and duration of call

show call active voice compact

Displays a compact version of active voice calls

show voip rtp connections

Displays active RTP connections

show call history voice

Displays calls stored in the history table for voice

Router Health

show call history stats cps

 

show processes cpu sorted

Displays sorted output based on percentage of CPU utilization

show process cpu platform sorted

Displays memory statistics

show processes memory sorted

Displays memory per process

show memory statistics history

Runs the memory leak detector

show platform resources

 

show platform hardware qfp active datapath utilization summary

 

show platform software system all

 

show memory debug leaks

Displays alignment data and spurious memory references

CAC

show call threshold config

Displays configured resource information

show call treatment config

Displays call admission control information

show call treatment stats

Displays call treatment statistics

Call Volume

show call history stats cps table

Displays the call rate per second

show call history watermark cps table

Displays the watermarks for calls per second

show call history watermark connected table

Displays the watermarks for active calls

show call history stats connected table

Displays the number of active calls during various periods

SIP

show sip-ua connections udp brief

Displays summary of SIP UDP connection information

show sip-ua connections udp detail

Displays details of SIP UDP connection information

show sip-ua connections tcp brief

Displays summary of SIP TCP connection information

show sip-ua connections tcp detail

Displays details of SIP TCP connection information

show sip-ua register status

Displays SIP registration status

Media/RTP

show voip rtp connections

 

show call active voice brief

 

show call active video brief

 

show interface

 

show voip fpi calls

 

DTMF Relay

show call active voice | inc tx_DtmfRelay

Displays the DTMF-relay used for the call

Security

show sip-ua connections tcp tls brief

Displays summary information on whether the transport used for the call is TLS or not

show crypto pki certificates

 

show sip-ua srtp

 

Show sip-ua connections tcp tls detail

Displays detailed information on whether the transport used for the call is TLS or not

4.3 Troubleshooting Recommendations

4.3.1 General

The following procedure is recommended to collect usable debug information:

     Configure “logging buffer 10000000” and “no logging console”

     Enter the “clear logging” command

     Perform the test

     Collect the logs using following two commands

    term length 0

    show logging

The following table lists key “debug” commands giving output that enables you to troubleshoot problems on CUBE.

Table 22.       Key “debug” Commands on CUBE

Category

Command

SIP

debug ccsip error

debug ccsip non-call

debug voip ccapi inout

debug voip dialpeer all

SIP

debug ccsip all

4.3.2 High-Traffic-Volume Troubleshooting

VoIP Trace is a Cisco Unified Border Element (CUBE) serviceability framework, which provides a binary trace facility for troubleshooting SIP call issues. The VoIP Trace framework records both successful and failed calls. All call trace data is stored in system memory. In addition, data for calls with IEC errors is also written to the logging location configured at the system level which includes logging to a buffer or a syslog server. VoIP Trace for CUBE Serviceability was introduced in IOS-XE 17.3.2

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voip-trace-for-cube.html

4.3.3 SIP Ladder Diagrams

The Cisco IOS-XE Embedded packet capture feature can be used to build SIP ladder diagrams for protocol troubleshooting. This feature captures packets on an interface and builds a pcap file that can be copied to an offline system for protocol analysis by a tool such Wireshark (freeware, from www.wireshark.org).

A summary of capturing and analyzing SIP protocols information using these tools include the following steps:

1.     Define the location where the capture will occur:

monitor capture CAP interface GigabitEthernet0/0/1 both

2.     Associate a filter. The filter may be specified inline, or an ACL or class-map can be referenced:

monitor capture CAP match ipv4 protocol tcp any

3.     Start the capture:

monitor capture CAP start

4.     The capture is now active. Allow it to collect the necessary data. Then stop the capture:

monitor capture CAP stop

5.     Examine the capture in a summary view:

show monitor capture CAP buffer brief

6.     In addition, export the capture in PCAP format for further analysis:

monitor capture CAP export ftp://10.0.0.1/CAP.pcap

7.     Once the necessary data has been collected, remove the capture:

no monitor capture CAP

Step 4: Display a ladder diagram using Wireshark

Display a ladder diagram using Wireshark

Another tool that can build SIP ladder diagrams is TranslatorX (freeware from https://translator.org/). The following image shows an example:

TranslatorX

5. Glossary

     AAA: Authentication, Authorization, and Accounting

     ACL: Access List

     ASR: Aggregation Services Routers

     CAC: Call Admission Control

     CDR: Call Detail Record

     CLI: Command Line Interface

     CUBE: Cisco Unified Border Element

     CUCM: Cisco Unified Communications Manager

     DOS: Denial of Service

     DSP: Digital Signal Processing

     DTMF: Dual-tone Multi Frequency

     EEM: Embedded Event Manager

     FQDN: Fully Qualified Domain Name

     GUI: Graphical User Interface

     GW: Gateway

     HA: High Availability

     ICPIF: Calculated Planning Impairment Factor

     ISR: Integrated Services Router

     LGW: Local Gateway

     LMS: LAN Management Solution

     MIB: Management Information Base

     MOS: Mean Opinion Score

     MTP: Media Termination Point

     NTP: Network Time Protocol

     OID: Object identifier

     OOD: Out of Dialog

     PBX: Private Branch Exchange

     PSTN: Public Switched Telephone Networks

     QoS: Quality of Service

     RADIUS: Remote Authentication Dial-in User Service

     RPID: Remote Party ID

     RTP: Real-time Protocol

     SBC: Session Border Controller

     SIP: Session Initiation Protocol

     SLA: Service Level Agreement

     SNMP: Simple Network Management Protocol

     SP: Service Provider

     SRTP: Secure RTP

     Tcl: Tool Command Language

     TCP: Transmission Control Protocol

     TDM: Time Division Multiplexing

     TLS: Transport Layer Security

     UC: Unified Communications

     UDP: User Datagram Protocol

     UNI: User to Network Interface

     URI: Universal Resource Identifier

     VAD: Voice Activity Detection

6 References

CUBE on Cisco.com

Cisco Interoperability Portal > Cisco Unified Border Element (CUBE)/SIP Trunking Solutions

CUBE IOS-XE Configuration Documentation

CUBE IOS-XE Configuration Application Notes and Examples Documentation

Cisco IOS-XE Voice Command Reference

Cisco SRND Portal (CUCM and CVP SIP Trunk Documentation)

Cisco.com MIB Locator tool

Cisco.com SNMP Object Navigator tool

 

 

 

Learn more