Introduction
HP WXP Collaboration application provides monitoring and analytics support for Cisco CUBE trunks. This article explains the naming convention followed for CUBE trunk names in WXP Collaboration.
Understanding CUBE Trunks
A trunk represents a logical connection between two systems and is defined at the target protocol level. For Cisco Unified Border Element (CUBE), trunks are derived from dial peers.
Each unique trunk is identified by a combination of the Trunk Name and the System.
CUBE Trunk Naming Convention
Outbound CUBE to IP or Host
This naming pattern is used when all dial peers for a system are mapped to a specific target IP address or host.
Example: Outbound CUBE to ipv4:192.168.1.201:5555
If the description field is the same for all dial peers, WXP Collaboration uses the description as the trunk name.
Outbound CUBE to Text Target
This pattern is used when all dial peers are mapped to a text-based target.
Example: Outbound Dial-Peer for Calls to CUCM ABCD Subscriber
Non-Target Peer Groups
This pattern applies to dial peers with no defined target and functions as a catch-all.
Example: Non-Target Peer Groups
Server Group to IP or Host
This pattern is used when all dial peers are mapped to a server group that contains multiple target IP addresses or hosts. Each target is listed as a separate trunk.
Server group 1-ipv4:192.168.1.100
Server group 1-ipv4:192.168.1.101
Server group 1-ipv4:192.168.1.102
CUBE Trunk Monitoring
WXP Collaboration monitors CUBE trunks by creating logical trunk representations from CUBE dial peer data. The platform provides trunk availability status and supports filtering, sorting, and multi-sorting by Trunk Name, Target IP, Target Host, Protocol, Status, Data Source, and System.
Contact Us
For any assistance, create a support case or email support@wxp.hp.com.