-
Cisco Unified Communications Manager System Guide, Release 7.1(2)
-
Index
-
Preface
- Understanding Cisco Unified Communications Manager
- Understanding Cisco Unified Communications Manager System Configuration
- Dial Plan Architecture
- User Configuration and Credential Policy
- Media Resources
- Voice Mail and Messaging Integration
- System Features
-
Devices and Protocols
-
Understanding Cisco Unified Communications Manager Voice Gateways
-
Understanding IP Telephony Protocols
-
Understanding Session Initiation Protocol
-
Understanding Cisco Unified Communications Manager Trunk Types
-
Cisco Unified IP Phones
-
Understanding Video Telephony
-
Computer Telephony Integration
-
Cisco ATA 186
-
- System Maintenance
-
Feedback
Table Of Contents
Understanding Cisco Unified Communications Manager Trunk Types
Cisco Unified Communications Manager Trunk Configuration
Trunks and Gatekeepers in Cisco Unified Communications Manager
Non-Gatekeeper-Controlled Trunks
Trunk Types in Cisco Unified Communications Manager Administration
H.225 Trunk (Gatekeeper Controlled)
Intercluster Trunk (Gatekeeper Controlled)
Intercluster Trunk (Non-Gatekeeper Controlled)
Trunks and the Calling Party Normalization Feature
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 Unified Communications Manager Trunk Types
In a distributed call-processing environment, Cisco Unified Communications Manager communicates with other Cisco Unified Communications Manager 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:
•
Trunk Configuration Checklist
•
•
•
•
•
Trunk Configuration Checklist
Table 43-1 provides an overview of the steps that are required to configure trunk interfaces in Cisco Unified Communications Manager, along with references to related procedures and topics.
See the following sections:
•
•
•
Configuration Considerations for SIP trunks
In a call-processing environment that uses Session Initiation Protocol (SIP), use SIP trunks to configure a signaling interface with Cisco Unified Communications Manager for SIP calls. SIP trunks (or signaling interfaces) connect Cisco Unified Communications Manager clusters with a SIP proxy server. The SIP signaling interface uses requests and responses to establish, maintain, and terminate calls (or sessions) between two or more endpoints. For more information about SIP and configuring SIP trunks, see the "SIP and Cisco Unified Communications Manager" section on page 42-2.
Because Cisco Unified Communications Manager does not perform validation on your configuration, consider the following restrictions when you configure SIP trunks:
•
•
–
–
The Incoming Transport Protocol, Incoming Port, and X.509 Subject Name parameters get configured in SIP Trunk Security Profile Configuration in Cisco Unified Communications Manager Administration. Choose System > Security Profile > SIP Trunk Security Profile. This menu option yields the Find and List SIP Trunk Security Profile window. Use this window to search for existing SIP Trunk Security Profiles or click Add New to add a new profile.
The Destination Address and the selected SIP Trunk Security profile get configured on the Trunk Configuration window in Cisco Unified Communications Manager. Choose Device > Trunk. This menu option yields the Find and List Trunks window. Use this window to search for existing trunks or click Add New to add a new trunk and choose SIP trunk as the Trunk Type.
The following example shows a valid configuration:
Trunk#1: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination Address=10.10.10.1Trunk#2: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination Address=10.10.10.2Trunk#3: Incoming Transport Protocol=TCP/UDP, Incoming Port=5080, Destination Address=10.10.10.1Trunk#4: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject Name=my_ccm1, my_ccm2Trunk#5: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject Name=my_ccm3Trunk#6: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject Name=my_ccm_1The following example shows an invalid configuration:
Trunk#1: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination Address=10.10.10.1Trunk#2: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination Address=10.10.10.1Trunk#3: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject Name=my_ccm1, my_ccm2Trunk#4: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject Name=my_ccm2Trunk#5: Incoming Transport Protocol=TLS, Incoming Port=5061, X.509 Subject Name=my_ccm2Trunk#6: Incoming Transport Protocol=TLS, Incoming Port=5081, X.509 Subject Name=my_ccm2Trunk#7: Incoming Transport Protocol=TCP/UDP, Incoming Port=5060, Destination Address=myhost.domain.comTrunk #2 conflicts with Trunk #1 because the protocol, incoming port, and destination address are identical.
Trunk #5 conflicts with Trunk #3 because the protocol and incoming port are identical, and both trunks include my_ccm2 in their list of X.509 Subject Names.
Trunk #6 conflicts with Trunk #4 because the protocol, incoming port, and X.509 Subject Name are identical.
Trunk #7 conflicts with Trunk #1, because if myhost.domain.com resolves to 10.10.10.1, the protocol, incoming port, and destination address are identical.
Table 43-1 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 Unified Communications Solution Reference Network Design (SRND)
Step 2
For gatekeeper-controlled trunks, configure the gatekeeper.
Gatekeeper and Gatekeeper-Controlled Trunk Configuration Checklist, page 8-3
Cisco Unified Communications Manager SIP Endpoints Overview, page 42-25
Step 3
Add the appropriate trunks in Cisco Unified Communications Manager Administration.
•
•
•
Configuring a Trunk, Cisco Unified Communications Manager Administration Guide
Trunk Configuration Settings, Cisco Unified Communications Manager 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 Unified Communications Manager server.
Trunk Configuration Settings, Cisco Unified Communications Manager 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 Unified Communications Manager Administration Guide
Route Group Configuration, Cisco Unified Communications Manager Administration Guide
Cisco Unified Communications Manager SIP Endpoints Overview, page 42-25
Step 6
Reset the trunk interface to apply the configuration settings.
Resetting a Trunk, Cisco Unified Communications Manager Administration Guide
Step 1
Gather the endpoint information, such as IP addresses or host names, that you need to configure the trunk interface.
Cisco Unified Communications Solution Reference Network Design (SRND)
Cisco Unified Communications Manager SIP Endpoints Overview, page 42-25
Step 2
Configure the SIP proxy.
Step 3
Create a SIP profile.
Create a SIP trunk security profile.
Create a SIP trunk.
Configure the destination address(es).
Configure the destination port.
Configuring SIP Profiles, Cisco Unified Communications Manager Administration Guide
Configuring a Trunk, Cisco Unified Communications Manager Administration Guide
Trunk Configuration Settings, Cisco Unified Communications Manager Administration Guide
Step 4
Associate the SIP trunk to a Route Pattern or Route Group.
SIP Route Pattern Configuration, Cisco Unified Communications Manager Administration Guide
Route Group Configuration, Cisco Unified Communications Manager Administration Guide
Route List Configuration, Cisco Unified Communications Manager Administration Guide
Step 5
Reset the SIP trunk.
Configuring a Trunk, Cisco Unified Communications Manager Administration Guide
Step 6
Configure SIP timers, counters, and service parameters, if necessary.
If you are using PUBLISH to communicate to a Cisco Unified Presence, choose the configured trunk in the CUP PUBLISH Trunk field of the Service Parameters Configuration window.
TipService Parameters Configuration, Cisco Unified Communications Manager Administration Guide.
Cisco Unified Communications Manager Trunk Configuration
Trunk configuration in Cisco Unified Communications Manager 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 Unified Communications Manager. For example, to configure QSIG connections to Cisco Unified Communications Manager, 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 Unified Communications Manager Voice Gateways" section on page 40-1.
Related Topics
•
•
Trunks and Gatekeepers in Cisco Unified Communications Manager
In addition to using gateways to route calls, you can configure trunks in Cisco Unified Communications Manager 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 Unified Communications Manager 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 Unified Communications Manager 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 Unified Communications Manager uses that IP address to complete the call.
For large distributed networks where many Cisco Unified Communications Manager clusters exist, you can avoid configuring individual intercluster trunks between each cluster by using gatekeepers.
When you configure gatekeeper-controlled trunks, Cisco Unified Communications Manager 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 Cisco Unified Communications Solution Reference Network Design (SRND) for more detailed information about gatekeeper configuration, dial plan considerations when using a gatekeeper, and gatekeeper interaction with Cisco Unified Communications Manager.
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 Unified Communications Manager 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 Unified Communications Manager Administration
Your choices for configuring trunks in Cisco Unified Communications Manager 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 Unified Communications Manager 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 Unified Communications Manager 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 Unified Communications Manager 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, see the "Gatekeepers and Trunks" section on page 8-10.
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 Unified Communications Manager 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 Unified Communications Manager 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 Unified Communications Manager uses that IP address to complete the call
For more information about gatekeepers, see the "Gatekeepers and Trunks" section on page 8-10.
Intercluster trunks support location-based call admission control (CAC) through use of the specially designated Phantom location. See "Location-Based Call Admission Control Over Intercluster Trunk" section on page 8-9 for additional information.
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 Unified Communications Manager 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 Unified Communications Manager Administration.
Note
You also configure the necessary route patterns and route groups to route calls to and from the intercluster trunks.
Intercluster trunks support location-based call admission control (CAC) through use of the specially designated Phantom location. See "Location-Based Call Admission Control Over Intercluster Trunk" section on page 8-9 for additional information.
SIP Trunk
In a call-processing environment that uses Session Initiation Protocol (SIP), use SIP trunks to configure a signaling interface with Cisco Unified Communications Manager for SIP calls. SIP trunks (or signaling interfaces) connect Cisco Unified Communications Manager clusters with a SIP proxy server. The SIP signaling interface uses requests and responses to establish, maintain, and terminate calls (or sessions) between two or more endpoints. For more information about SIP and configuring SIP trunks, see the "SIP and Cisco Unified Communications Manager" section on page 42-2.
To configure a SIP trunk in Cisco Unified Communications Manager Administration, choose Device > Trunk and then SIP Trunk. For information on configuration tasks, see the "Cisco Unified Communications Manager SIP Endpoints Overview" section on page 42-25.
Tip
SIP trunks support location-based call admission control (CAC) through use of the specially designated Phantom location. See "Location-Based Call Admission Control Over Intercluster Trunk" section on page 8-9 for additional information.
Related Topics
•
•
Trunks and the Calling Party Normalization Feature
In line with E.164 standards, calling party normalization enhances the dialing capabilities of some phones and improves call back functionality when a call is routed to multiple geographical locations; that is, the feature ensures that the called party can return a call without needing to modify the directory number in the call log directories on the phone. Additionally, calling party normalization allows you to globalize and localize phone numbers, so the appropriate calling number presentation displays on the phone.
Configuring calling party normalization alleviates issues with toll bypass where the call is routed to multiple locations over the IP WAN. In addition, it allows Cisco Unified Communications Manager to distinguish the origin of the call to globalize or localize the calling party number for the phone user.
For information on how to configure this feature for your trunk, see the "Calling Party Normalization" section in the Cisco Unified Communications Manager Features and Services Guide.
You can configure the international escape character, +, to globalize the calling party number. For information on the international escape character, +, see the "Using the International Escape Character +" section in the Cisco Unified Communications Manager System Guide.
Transferring Calls Between Trunks
Using Cisco Unified Communications Manager 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 Unified Communications Manager Administration Trunk Configuration, you can configure a trunk as OffNet or OnNet. The system considers calls that are coming to the network through that trunk as 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 43-2 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, outgoing calls are considered OnNet).
You can use the same trunk 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 whether 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 system considers the outgoing call as 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 Unified Communications Manager:
•
•
•
•
•
If you do not want OffNet calls to be transferred to an external device (one that is configured as OffNet), set the Cisco Unified Communications Manager 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, choose Dependency Records from the Related Links drop-down list box that is provided on the Cisco Unified Communications Manager Administration Trunk Configuration window. The Dependency Records Summary window displays information about route groups that are using the trunk. To find 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 Unified Communications Manager Administration Guide.
Related Topics
•
•
H.235 Support for Trunks
This feature allows Cisco Unified Communications Manager trunks to transparently pass through the shared secret (Diffie-Hellman key) and other H.235 data between two H.235 endpoints so that the two endpoints can establish a secure media channel.
For more information, see the Cisco Unified Communications Manager Security Guide.
Where to Find More Information
Related Topics
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Additional Cisco Documentation
•
•
•
