3.4 Trunk Implementation Overview

This topic describes H.323 and SIP trunk implementation.

The figure shows the most important configuration elements for implementing a SIP or nongatekeeper-controlled ICT in Cisco Unified Communications Manager. These elements are the configuration of the trunk itself, in which you must specify the IP address of the peer, as well as the route group, route list, and route pattern configuration. This implementation is like the implementation of a gateway.

Gatekeeper-Controlled ICT and H.225 Trunk Configuration Overview

The figure shows the most important configuration elements for implementing a gatekeeper-controlled ICT orH.225 trunk in Cisco Unified Communications Manager.

The trunk (which points to the gatekeeper), the route group, the route list, and the route pattern configuration are the elements of the gatekeeper in which you must specify the IP address of the gatekeeper. This implementation is like the implementation of a gateway.

Trunk Types Used by Special Applications

Some applications require special trunk types to be configured.

For example, when you implement Cisco EMCC, you must configure a dedicated trunk between the Cisco Unified Communications Manager clusters that allow users of the remote cluster to log in locally using Cisco EMCC. These trunks, which are exclusively configured for Cisco EMCC, must use the SIP protocol; H.323 is not supported by Cisco EMCC. Another application that requires special trunks to be configured is CCD. When you use CCD, internal directory numbers and the associated external PSTN numbers are advertised and learned from a SAF-enabled network. These trunks can be either SIP or H.323 and must be explicitly enabled for SAF.

Advertisements