Table Of Contents

Trunk Configuration

Use a trunk device to configure a logical route to a gatekeeper (that is, the wholesale network or an intercluster trunk with gatekeeper control) or to an intercluster trunk without a gatekeeper. Choose from the following available trunk types:

Finding a Trunk

Because you might have multiple trunks in your network, Cisco CallManager lets you search for trunks on the basis of specified criteria. Follow these steps to search for a specific trunk in the Cisco CallManager database.

Note During your work in a browser session, Cisco CallManager Administration retains your trunk search preferences. If you navigate to other menu items and return to this menu item, Cisco CallManager Administration retains your trunk search preferences until you modify your search or close the browser.

Procedure

Step 1 Choose Device > Trunk.

The Find and List Trunks window displays.

Step 2 Choose the field that you want to use to locate a trunk.

Note To find all trunks that are registered in the database, choose Device Name from the list of fields and choose "is not empty" from the list of patterns; then, click Find.

Step 3 Choose the appropriate search pattern for your text search. If you do not want to perform a text search, choose "is empty."

Step 4 Enter your search text, if any, in the Find field.

Step 5 If you choose calling search space or device pool in Step 2, the options available in the database display. From the drop-down list box below the Find button, you can choose one of these options.

Step 6 Click Find.

A list of devices that match the criteria displays. The field that you chose in Step 2 determines how the devices in the list are sorted.

This window also lists the total number of devices and windows in this window.

Step 7 To view the next set of discovered devices, click Next.

Note You can delete or reset multiple trunks from the Find and List Trunks window by checking the check boxes next to the appropriate trunks and clicking Delete Selected to delete the trunks or clicking Reset Selected to reset the trunks. You can choose all of the trunks in the window by checking the check box in the Matching records title bar.

Deleting a Trunk

Perform the following steps to delete a trunk.

Before You Begin

You cannot delete a trunk that is assigned to one or more route patterns. To find out which route patterns are using the trunk, click the Dependency Records link from the Trunk Configuration window. For more information about dependency records, see the "Accessing Dependency Records" section on page A-1. If you try to delete a trunk that is in use, Cisco CallManager displays an error message. Before deleting a trunk that is currently in use, you must perform either or both of the following tasks:

Step 6 Click Reset Trunk to reset or restart the trunk and apply the new settings.

Note Resetting a trunk drops any calls in progress that are using that trunk. Restarting a gateway tries to preserve the calls in progress that are using that gateway, if possible. Other devices wait until calls complete before restarting or resetting. Resetting/restarting an H323 device does not physically reset/restart the hardware; it only reinitializes the configuration that is loaded by Cisco CallManager

For trunks, device pools specify a list of Cisco CallManagers that the trunk uses to distribute the call load dynamically.

Note Calls that are initiated from a phone that is registered to a Cisco CallManager that does not belong to the trunk's device pool use different Cisco CallManagers of this device pool for different outgoing calls. Selection of Cisco CallManager nodes occurs in a random order.

A call that is initiated from a phone that is registered to a Cisco CallManager that does belong to the trunk's device pool uses the same Cisco CallManager node for outgoing calls if the Cisco CallManager is up and running.

Media Resource Group List

This list provides a prioritized grouping of media resource groups. An application chooses the required media resource, such as a Music On Hold server, from among the available media resources according to the priority order that is defined in a Media Resource Group List.

Location

Choose the appropriate location for the trunk. The location specifies the total bandwidth available for calls between this location and the central location, or hub. A location setting of None specifies unlimited available bandwidth.

AAR Group

Choose the automated alternate routing (AAR) group for this device. The AAR group provides the prefix digits that are used to route calls that are otherwise blocked due to insufficient bandwidth. An AAR group setting of None specifies that no rerouting of blocked calls will be attempted.

Media Termination Point Required

Indicate whether a media termination point (MTP) is used to implement features that H.323 does not support (such as hold and transfer).

Check the Media Termination Point Required check box if you want to use a media termination point to implement features. Uncheck the Media Termination Point Required check box if you do not want to use a media termination point to implement features.

Use this check box only for H.323 clients and those H.323 devices that do not support the H.245 empty capabilities set or if you want media streaming to terminate through a single source.

Call Routing Information

Inbound Calls

Significant Digits

Significant digits represent the number of final digits that are retained on inbound calls. Use for the processing of incoming calls and to indicate the number of digits that are used to route calls that are coming in to the H.323 device.

Choose the number of significant digits to collect, from 0 to 32. Cisco CallManager counts significant digits from the right (last digit) of the number that is called.

Calling Search Space

Choose the appropriate calling search space for the trunk. The calling search space specifies the collection of route partitions that are searched to determine how to route a collected (originating) number.

AAR Calling Search Space

Choose the appropriate calling search space for the device to use when performing automated alternate routing (AAR). The AAR calling search space specifies the collection of route partitions that are searched to determine how to route a collected (originating) number that is otherwise blocked due to insufficient bandwidth.

Prefix DN

Enter the prefix digits that are appended to the called party number on incoming calls.

Cisco CallManager adds prefix digits after first truncating the number in accordance with the Significant Digits setting.

Redirecting Number IE Delivery - Inbound

Check this check box to accept the Redirecting Number IE in the incoming SETUP message to the Cisco CallManager.

Uncheck the check box to exclude the Redirecting Number IE in the incoming SETUP message to the Cisco CallManager.

You use Redirecting Number IE for voice-mail integration only. If your configured voice-mail system supports Redirecting Number IE, you should check the check box.

Note Default leaves the check box unchecked.

Outbound Calls

Calling Party Selection

Choose the directory number that is sent on an outbound call on a gateway.

The following options specify which directory number is sent:

•Originator—Send the directory number of the calling device.

•First Redirect Number—Send the directory number of the redirecting device.

•Last Redirect Number—Send the directory number of the last device to redirect the call.

•First Redirect Number (External)—Send the external directory number of the redirecting device.

•Last Redirect Number (External)—Send the external directory number of the last device to redirect the call.

Calling Party Presentation

Choose whether the Cisco CallManager transmits or blocks caller ID.

Choose Allowed if you want the Cisco CallManager to send caller ID.

Choose Restricted if you do not want the Cisco CallManager to send caller ID.

Called party IE number type unknown

Choose the format for the type of number in called party directory numbers.

Cisco CallManager sets the called directory number (DN) type. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans, such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the called directory number to be encoded to a non-national numbering plan type.

Choose one of the following options:

•Cisco CallManager—Cisco CallManager sets the directory number type.

•Unknown—The dialing plan is unknown.

•National—Use when you are dialing within the dialing plan for your country.

•International—Use when you are dialing outside the dialing plan for your country.

•Subscriber—Use when you are dialing a subscriber by using a shortened subscriber number.

Calling party IE number type unknown

Choose the format for the type of number in calling party directory numbers.

Cisco CallManager sets the calling directory number (DN) type. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans, such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the calling directory number to be encoded to a non-national numbering plan type.

Choose one of the following options:

•Cisco CallManager—Cisco CallManager sets the directory number type.

•Unknown—The dialing plan is unknown.

•National—Use when you are dialing within the dialing plan for your country.

•International—Use when you are dialing outside the dialing plan for your country.

•Subscriber—Use when you are dialing a subscriber by using a shortened subscriber number.

Called Numbering Plan

Choose the format for the numbering plan in called party directory numbers.

Cisco CallManager sets the called DN numbering plan. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans, such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the called numbering plan to be encoded to a non-national numbering plan.

•ISDN—Use when you are dialing outside the dialing plan for your country.

•National Standard—Use when you are dialing within the dialing plan for your country.

•Private—Use when you are dialing within a private network.

•Unknown—The dialing plan is unknown.

Calling Numbering Plan

Choose the format for the numbering plan in calling party directory numbers.

Cisco CallManager sets the calling DN numbering plan. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans, such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco CallManager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the calling numbering plan to be encoded to a non-national numbering plan.

•ISDN—Use when you are dialing outside the dialing plan for your country.

•National Standard—Use when you are dialing within the dialing plan for your country.

•Private—Use when you are dialing within a private network.

•Unknown—The dialing plan is unknown.

Caller ID DN

Enter the pattern, from 0 to 24 digits, that you want to use to format the caller ID on outbound calls from the trunk.

For example, in North America

•555XXXX = Variable Caller ID, where X represents an extension number. The Central Office (CO) appends the number with the area code if you do not specify it.

•5555000 = Fixed Caller ID. Use this form when you want the Corporate number to be sent instead of the exact extension from which the call is placed. The CO appends the number with the area code if you do not specify it.

Display IE Delivery

Check this check box to enable delivery of the display information element (IE) in SETUP and CONNECT messages for the calling and called party name delivery service.

The default setting leaves this check box unchecked.

Redirecting Number IE Delivery - Outbound

Check this check box to include the Redirecting Number IE in the outgoing SETUP message from the Cisco CallManager to indicate the first redirecting number and the redirecting reason of the call when the call is forwarded.

Uncheck the check box to exclude the first redirecting number and the redirecting reason from the outgoing SETUP message.

You use Redirecting Number IE for voice-mail integration only. If your configured voice-mail system supports Redirecting Number IE, you should check the check box.

Note The default setting leaves this check box unchecked.

Gatekeeper Information

(for gatekeeper-controlled H.225 trunks and intercluster trunks)

Gatekeeper Name

Choose the gatekeeper that controls this trunk.

Terminal Type

Use the Terminal Type field to designate the type for all devices controlled by this trunk.

Always set this field to Gateway for normal trunk call admission control.

Technology Prefix

Use this optional field to eliminate the need for entering the IP address of every Cisco CallManager when configuring the gw-type-prefix on the trunk:

•If you leave this field blank (the default setting), you must specify the IP address of each Cisco CallManager that can register with the trunk when you enter the gw-type-prefix command on the trunk.

•When you use this field, make sure that the value that is entered here exactly matches the type-prefix value that is specified with the gw-type-prefix command on the trunk.

For example, if you leave this field blank and you have two Cisco CallManagers with IP addresses of 10.1.1.2 and 11.1.1.3, enter the following gw-type-prefix command on the trunk:

gw-type-prefix 1#* default-technology gw ip 10.1.1.2 gw ip 11.1.1.3

If you enter 1#* in this field, enter the following gw-type-prefix commandon the trunk:

gw-type-prefix 1#* default-technology

Zone

Use this optional field to request a specific zone on the trunk with which Cisco CallManager will register. The zone specifies the total bandwidth that is available for calls between this zone and another zone:

•If you do not enter a value in this field, the zone subnet command on the trunk determines the zone with which Cisco CallManager registers. Cisco recommends the default setting for most configurations.

•If you want Cisco CallManager to register with a specific zone on the trunk, enter the value in this field that exactly matches the zone name that is configured on the trunk with the zone command. Specifying a zone name in this field eliminates the need for a zone subnet command for each Cisco CallManager that is registered with the trunk.

Refer to the command reference documentation for your trunk for more information.

Remote Cisco CallManager Information

(for non-gatekeeper-controlled intercluster trunks)

Server 1 IP Address/Host Name

Required. Enter the IP address or host name of the first remote Cisco CallManager that this trunk accesses.

Server 2 IP Address/Host Name

Optional. Enter the IP address or host name of the second remote Cisco CallManager that this trunk accesses.

Note If this non-gatekeeper-controlled intercluster trunk accesses the device pool of a remote non-gatekeeper-controlled intercluster trunk and that device pool has a second Cisco CallManager node, you must enter the second remote Cisco CallManager IP address/host name in this field.

Server 3 IP Address/Host Name

Optional. Enter the IP address or host name of the third remote Cisco CallManager that this trunk accesses.

Note If this non-gatekeeper-controlled intercluster trunk accesses the device pool of a remote non-gatekeeper-controlled intercluster trunk and that device pool has a third Cisco CallManager node, you must enter the third remote Cisco CallManager IP address/host name in this field.