Set Up for Cisco Unified Border Element (CUBE)

This document describes the necessary steps and configuration commands needed to setup a CUBE for data collection.

1. Before starting, it is highly recommended to install an SSH client on your server that will be hosting the Vyopta collector.

2. Open all required ports between the server hosting the collector and the CUBE(s). This may require opening ports on a firewall, or allowing traffic via access control lists within the network.

• The data collector needs to be able to access ISR/CUBE:

  • On TCP port 22 (SSH)

  • On UCP port 161 (SNMP agent)

• The ISR/CUBE needs to be able to send SNMP traps to the Vyopta data collector.

  • On UDP port 162

3. Configure the ISR/CUBE for SNMP access:

• Enable SNMP in IOS

snmp-server community vyoptacpm RO
snmp-server enable traps dial
snmp-server host <data collector host IP address>

• SSH port 22. Configure a limited IOS service account for Vyopta CPM. NOTE – a different privilege level can be used at customer discretion. The levels below are the minimum requirement.

privilege configure all level 5 logging
privilege exec all level 5 show dial-peer voice summary
privilege exec all level 5 show dial-peer voice
privilege exec level 5 show dial-peer
privilege exec level 5 show

• Create the required service account that has SSH access to ISR/CUBE

username vyopta_svc privilege 5 secret <password>

4. Enable status tracking on individual dial-peers per router.

• For each dial-peer, utilize the below commands to configure Out-of-dialog (OOD) OPTIONS Ping for Specified SIP

dial-peer voice tag voip
voice-class sip options-keepalive {up-interval seconds | down-interval seconds | retry retries}

• Example:

enable
configure terminal
dial-peer voice 200 voip
voice-class sip options-keepalive up-interval 100 down-interval 50 retry 6

(these are the recommended and tested values)

5. Enable media statistics.

• Perform the below globally to enable the tracking of jitter, packet loss, and latency

voice services voip
media statistics

• Example

enable
configure terminal
voice services voip
media statistics
exit

IMPORTANT NOTES

• For IOS (legacy operating systems) enabling RTCP only provides latency information into debug as per Cisco documentation

• For IOS-XE (recommended operating system) enabling RTCP provides latency information into CDRs and Debug as per Cisco documentation

• RTCP being enabled could cause interference with CUCM configurations on media termination point settings. This may have an impact on DTMF (“press 1 to talk to sales”) functionality. If enabled, you must check to see that all permutations of DTMF are still working as expected.

Reference: https://www.cisco.com/c/en/us/td/docs/iosxml/ios/voice/cube/configuration/cube-book/voi-cube-voice-quality-monitoring.html