Cisco Trunk Concepts

In addition to adding gateways to the CallManager configuration, trunks can also provide connectivity to outside devices. Trunks are seen by Cisco CallManager as logical links to other networks. These links have the ability to determine the location of an endpoint, but do not carry voice traffic. This underscores the major difference between trunks and gateways: Gateways can typically locate (or represent) an endpoint and carry the voice traffic to that endpoint; trunks only locate an endpoint. For example, you could create an intercluster trunk from your CallManager cluster containing 3XXX extensions to another CallManager cluster containing 4XXX extensions. When a user in your cluster (extension 3505) dials an extension in the other cluster (extension 4505), the local CallManager signals over the trunk to the remote CallManager. This signaling occurs to locate the IP address of extension 4505. After this IP address has been found, the audio path opens directly between the local extension 3505 and the remote extension 4505.

Your choices for configuring trunks in Cisco CallManager depend on whether the IP WAN uses gatekeepers to handle call routing and on the types of call-control protocols that are used in the call-processing environment.

Cisco CallManager Administration supports the following trunk types:

Категории