Measures reported by CUCMTrnkStatTest

Phone calls can be routed over the IP network using a trunk interface configuration in CUCM. The definition of trunk is expanded beyond physical connections such as a PRI, T1, or analog trunk, to also include virtual connections between two entities. The virtual connection defines a TCP/IP session between the two entities that is used for call signaling, and associated with the connection is a path over a TCP/IP network used for the media. The signaling path and the media path may terminate on different sets of endpoints and also may take different paths through the TCP/IP network. In some cases the trunk may define an entity that is the destination where the VoIP media stream of the call ultimately terminates, or it may define an entity that provides an intermediate routing function. In the first case, there must exist a separate configuration for each pair of endpoints, and the relationship between the two entities is peer-to-peer. In the latter case, a single trunk may be defined to specify a gatekeeper that provides a routing function between all entities registered to that gatekeeper. This relationship is one-to-many. In Cisco Unified CallManager, trunks may be configured with one of two protocols: H.323 or SIP.

When Cisco Unified Communications Manager receives a call setup request from a local endpoint or from another call control system, then the manager analyzes the target of the received request to find the best matching entry in its call-routing table. The source of the call setup request can be through trunk, gateway or IP phone. A call request received through a trunk is looked up in the call-routing table. Then the manager forwards the call setup request to the destination device that is associated with the matched call-routing table entry. But, when the trunk is inactive or busy, then the call setup request cannot be established leading to termination of the call request. This can cause serious service level bottlenecks.

This test monitors the gateway trunks in the Call manager and reports the number of trunks that are active. This test also reveals the number of gateway trunks that are inactive, busy and unknown. This helps administrators to proactively detect any unavailable trunks and resolve the issue before the end user is affected.

Outputs of the test : One set of results for the target Cisco Unified Communications manager being monitored

The measures made by this test are as follows: