-
Cisco CallManager System Guide, Release 4.1(2)
-
Index
-
Preface
-
Introduction
-
Cisco IP Telephony Overview
-
System Configuration Overview
-
Multilevel Administration Access
-
System-Level Configuration Settings
-
Clustering
-
Redundancy
-
Call Admission Control
-
Cisco TFTP
-
Device Support
-
Services
-
Auto-Registration
-
Partitions and Calling Search Spaces
-
Time-of-Day Routing
-
Understanding Route Plans
-
Application Dial Rules Overview
-
Understanding the Directory
-
Managing User Directory Information
-
Media Resource Management
-
Annunciator
-
Conference Bridges
-
Transcoders
-
Music On Hold
-
Media Termination Points
-
Cisco DSP Resources for Transcoding, Conferencing, and MTP
-
Voice Mail Connectivity to Cisco CallManager
-
SMDI Voice Mail Integration
-
Cisco Unity Messaging Integration
-
Cisco DPA Integration
-
Call Park
-
Call Pickup and Group Call Pickup
-
Cisco IP Phone Services
-
Cisco CallManager Extension Mobility and Phone Login Features
-
Cisco CallManager Attendant Console
-
Cisco IP Manager Assistant
-
Understanding Cisco CallManager Voice Gateways
-
Understanding IP Telephony Protocols
-
Understanding Session Initiation Protocol (SIP)
-
Understanding Cisco CallManager Trunk Types
-
Cisco IP Phones
-
Understanding Video Telephony
-
Computer Telephony Integration
-
Cisco ATA 186 and Cisco ATA 188
-
Administrative Tools Overview
-
Administrative Accounts and Passwords
-
Feedback
Table Of Contents
Understanding Cisco CallManager Trunk Types
Cisco CallManager Trunk Configuration
Trunks and Gatekeepers in Cisco CallManager
Non-Gatekeeper-Controlled Trunks
Trunk Types in Cisco CallManager Administration
H.225 Trunk (Gatekeeper Controlled)
Intercluster Trunk (Gatekeeper Controlled)
Intercluster Trunk (Non-Gatekeeper Controlled)
Transferring Calls Between Trunks
Configuring Transfer Capabilities Using Trunk Configuration
Configuring Transfer Capabilities by Using Call Classification Service Parameter
Blocking Transfer Capabilities by Using Service Parameters
Dependency Records for Trunks and Associated Route Groups
Where to Find More Information
Understanding Cisco CallManager Trunk Types
In a distributed call-processing environment, Cisco CallManager communicates with other Cisco CallManager clusters, the public switched telephone network (PSTN), and other non-IP telecommunications devices, such as private branch exchanges (PBXs) by using trunk signaling protocols and voice gateways.
This section covers the following topics:
•
Cisco CallManager Trunk Configuration
•
•
•
•
•
Cisco CallManager Trunk Configuration
Trunk configuration in Cisco CallManager Administration depends on the network design and call-control protocols that are used in the IP WAN. All protocols require that either a signaling interface (trunk) or a gateway be created to accept and originate calls. For some IP protocols, such as MGCP, you configure trunk signaling on the gateway. You specify the type of signaling interface when you configure the gateway in Cisco CallManager. For example, to configure QSIG connections to Cisco CallManager, you must add an MGCP voice gateway that supports QSIG protocol to the network. You then configure the T1 PRI or E1 PRI trunk interface to use the QSIG protocol type. For more information about configuring gateways, see the "Understanding Cisco CallManager Voice Gateways" chapter.
Related Topics
•
•
Trunks and Gatekeepers in Cisco CallManager
In addition to using gateways to route calls, you can configure trunks in Cisco CallManager Administration to function in either of the following ways:
•
Gatekeeper-Controlled Trunks
Gatekeepers that are used in a distributed call-processing environment provide call routing and call admission control for Cisco CallManager clusters. Intercluster trunks that are gatekeeper-controlled can communicate with all remote clusters. Similarly, an H.225 trunk can communicate with any H.323 gatekeeper-controlled endpoints including Cisco CallManager clusters. Route patterns or route groups can route the calls to and from the gatekeeper. In a distributed call-processing environment, the gatekeeper uses the E.164 address (phone number) and determines the appropriate IP address for the destination of each call, and the local Cisco CallManager uses that IP address to complete the call.
For large distributed networks where many Cisco CallManager clusters exist, you can avoid configuring individual intercluster trunks between each cluster by using gatekeepers.
When you configure gatekeeper-controlled trunks, Cisco CallManager creates a virtual trunk device. The gatekeeper changes the IP address of this device dynamically to reflect the IP address of the remote device. Specify these trunks in the route patterns or route groups that route calls to and from the gatekeeper.
Refer to the Cisco IP Telephony Solution Reference Network Design guide for more detailed information about gatekeeper configuration, dial plan considerations when using a gatekeeper, and gatekeeper interaction with Cisco CallManager.
Non-Gatekeeper-Controlled Trunks
With no gatekeepers in the distributed call-processing environment, you must configure a separate intercluster trunk for each remote device pool in a remote cluster that the local Cisco CallManager can call over the IP WAN. You also configure the necessary route patterns and route groups to route calls to and from the various intercluster trunks. The intercluster trunks statically specify the IP addresses of the remote devices.
Related Topics
•
•
Trunk Types in Cisco CallManager Administration
Your choices for configuring trunks in Cisco CallManager depend on whether the IP WAN uses gatekeepers to handle call routing. Also, the types of call-control protocols that are used in the call-processing environment determine trunk configuration options.
You can configure these types of trunk devices in Cisco CallManager Administration:
•
•
•
H.225 Trunk (Gatekeeper Controlled)
In an H.323 network that uses gatekeepers, use an H.225 trunk with gatekeeper control to configure a connection to a gatekeeper for access to other Cisco CallManager clusters and to H.323 devices. An H.225 trunk can communicate with any H.323 gatekeeper-controlled endpoint. When you configure an H.323 gateway with gatekeeper control in Cisco CallManager Administration, use an H.225 trunk. To choose this method, use Device > Trunk and choose H.225 Trunk (Gatekeeper Controlled).
You also configure route patterns and route groups to route calls to and from the gatekeeper. For more information about gatekeepers, see the "Gatekeepers and Trunks" section.
Intercluster Trunk (Gatekeeper Controlled)
In a distributed call-processing network with gatekeepers, use an intercluster trunk with gatekeeper control to configure connections between clusters of Cisco CallManager systems. Gatekeepers provide call admission control and address resolution for intercluster calls. A single intercluster trunk can communicate with all remote clusters. To choose this method, use Device > Trunk and choose Inter-Cluster Trunk (Gatekeeper Controlled) in Cisco CallManager Administration.
You also configure route patterns and route groups to route the calls to and from the gatekeeper. In this configuration, the gatekeeper dynamically determines the appropriate IP address for the destination of each call, and the local Cisco CallManager uses that IP address to complete the call
For more information about gatekeepers, see the "Gatekeepers and Trunks" section.
Intercluster Trunk (Non-Gatekeeper Controlled)
In a distributed network that has no gatekeeper control, you must configure a separate intercluster trunk for each device pool in a remote cluster that the local Cisco CallManager can call over the IP WAN. The intercluster trunks statically specify the IP addresses or host names of the remote devices.To choose this method, use Device > Trunk and choose Inter-Cluster Trunk (Non-Gatekeeper Controlled) in Cisco CallManager Administration.
Note
You also configure the necessary route patterns and route groups to route calls to and from the intercluster trunks.
SIP Trunk
In a call-processing environment that uses Session Initiation Protocol (SIP), use SIP trunks to configure a signaling interface with Cisco CallManager for SIP calls. SIP trunks (or signaling interfaces) connect Cisco CallManager clusters with a SIP proxy server. A SIP signaling interface uses port-based routing, and Cisco CallManager accepts calls from any gateway as long as the SIP messages arrive on the port that is configured as a SIP signaling interface. The SIP signaling interface uses requests and responses to establish, maintain, and terminate calls (or sessions) between two or more endpoints.
To choose this method, use Device > Trunk and choose SIP Trunk in Cisco CallManager Administration.
You must also configure route groups and route patterns that use the SIP trunks to route the SIP calls.
For more information about SIP and configuring SIP trunks, see the "SIP and Cisco CallManager" section.
Related Topics
•
•
Transferring Calls Between Trunks
Using Cisco CallManager Administration, you can configure trunks as OnNet (internal) trunks or OffNet (external) trunks by using Trunk Configuration or by setting a clusterwide service parameter. Used in conjunction with the clusterwide service parameter, Block OffNet to OffNet Transfer, the configuration determines whether calls can be transferred over a trunk.
To use the same trunk to route both OnNet and OffNet calls, associate the trunk with two different route patterns. Make one trunk OnNet and the other OffNet with both having the Allow Device Override check box unchecked.
Configuring Transfer Capabilities Using Trunk Configuration
Using Cisco CallManager Administration Trunk Configuration, you can configure a trunk as OffNet or OnNet. The calls coming to the network through that trunk are considered OffNet or OnNet, respectively. Use the Trunk Configuration window field, Call Classification, to configure the trunk as OffNet, OnNet, or Use System Default. See Table 39-1 for description of these settings.
The Route Pattern Configuration window provides a drop-down list box called Call Classification, which allows you to configure a route pattern as OffNet or OnNet. When Call Classification is set to OffNet and the Allow Device Override check box is unchecked, the system considers the outgoing calls that use this route pattern as OffNet (if configured as OnNet and check box is unchecked, then outgoing calls are considered OnNet).
The same trunk can be used to route both OnNet and OffNet calls by associating the trunk with two different route patterns: one OnNet and the other OffNet, with both having the Allow Device Override check box unchecked. For outgoing calls, the outgoing device setting classifies the call as either OnNet or OffNet by determining if the Allow Device Override check box is checked.
In route pattern configuration, if the Call Classification is set as OnNet, the Allow Device Override check box is checked, and the route pattern is associated with an OffNet Trunk, the outgoing call is considered OffNet.
Configuring Transfer Capabilities by Using Call Classification Service Parameter
To configure all trunks to be OffNet (external) or OnNet (internal), perform the following two steps:
1.
2.
Blocking Transfer Capabilities by Using Service Parameters
Block transfer restricts the transfer between external devices, so fraudulent activity gets prevented. You can configure the following devices as OnNet (internal) or OffNet (external) to Cisco CallManager:
•
•
•
•
•
If you do not want OffNet calls to be transferred to an external device (one that is configured as OffNet), set the Cisco CallManager clusterwide service parameter, Block OffNet to OffNet Transfer, to True.
If a user tries to transfer a call on an OffNet trunk that is configured as blocked, a message displays on the user phone to indicate that the call cannot be transferred.
Related Topics
•
•
•
Dependency Records for Trunks and Associated Route Groups
To find route groups that use a specific trunk, click the Dependency Records link that is provided on the Cisco CallManager Administration Trunk Configuration window. The Dependency Records Summary window displays information about route groups that are using the trunk. To find out more information about the route group, click the route group, and the Dependency Records Details window displays. If the dependency records are not enabled for the system, the dependency records summary window displays a message.
For more information about Dependency Records, refer to Accessing Dependency Records, in the Cisco CallManager Administration Guide.
Related Topics
•
•
Trunk Configuration Checklist
Table 39-2 provides an overview of the steps that are required to configure trunk interfaces in Cisco CallManager, along with references to related procedures and topics.
Table 39-2 Trunk Configuration Checklist
Step 1
Gather the endpoint information, such as IP addresses or host names, that you need to configure the trunk interface.
Cisco IP Telephony Solution Reference Network Design
Step 2
For gatekeeper-controlled trunks, configure the gatekeeper.
For SIP trunks, perform proxy configuration.
Gatekeeper and Trunk Configuration Checklist
Step 3
Add the appropriate trunks in Cisco CallManager Administration.
•
•
•
•
Adding a Trunk, Cisco CallManager Administration Guide
Trunk Configuration Settings, Cisco CallManager Administration Guide
Step 4
Configure the gatekeeper-controlled intercluster trunks or H.225 trunks to specify gatekeeper information.
Configure the non-gatekeeper-controlled trunks with the IP address or host name for the remote Cisco CallManager server.
Trunk Configuration Settings, Cisco CallManager Administration Guide
Step 5
Configure a route pattern or route group to route calls to each gatekeeper-controlled trunk.
Configure a route pattern or route group to route calls to each non-gatekeeper-controlled trunk.
Route Pattern Configuration,Cisco CallManager Administration Guide
Route Group Configuration, Cisco CallManager Administration Guide
Step 6
Reset the trunk interface to apply the configuration settings.
Resetting a Trunk, Cisco CallManager Administration Guide
Related Topics
•
•
•
•
Where to Find More Information
Related Topics
•
•
•
•
Additional Cisco Documentation
•
•
•
