A system in TMS is not given the choice to call an H.323 Alias. Why?

Introduction

This article relates to Cisco TelePresence Management Suite.

Q. A system in TMS is not given the choice to call an H.323 Alias. Why?

A. To make scheduled H.323 calls to an alias (E.164 number, URI or H.323 ID), TMS must know that the systems (endpoints and/or MCUs) have IP bandwidth and are registered to an H.323 gatekeeper. To ensure this:

1. Check the IP Bandwidth:

   1. Go to Systems > Navigator

   2. Select the system.

   3. Click Settings.

   4. In the Call Settings pane, ensure that Maximum IP Bandwidth is greater than 0. (If not, and you have the necessary permissions, click Edit Settings, enter the bandwidth and click Save.)

2. Check the Gatekeeper Status:

   Still in Settings, in the Network Settings pane, ensure that Gatekeeper Registration Status is Registered. (If not, register the system to a gatekeeper following the instructions provided with that system.)

In routing scheduled calls, TMS performs gatekeeper neighboring checks to ensure that the number being called can be resolved to a known managed system. TMS looks up the gatekeeper of the remote system in the TMS database and checks it against the gatekeeper address of the requesting system:

• If they are the same, the systems are considered compatible and alias dialing is allowed.

• If they are not the same but the gatekeepers are managed by TMS, TMS checks the neighbors defined for each gatekeeper and if the two gatekeepers are listed as neighbors of each other, alias dialing is allowed. (To disable this neighboring gatekeeper check, go to Administrative Tools > Configuration > Conference Settings and in the Advanced Conference Options section select Yes for Use Flat E164 Dialing Plan When Routing Calls).

• If the gatekeepers are not direct neighbors, but the IP Zones of the requesting system and destination system both have a URI dialing domain defined, TMS allows calling using the format alias@URIdomain.

• If the gatekeepers are different and not neighbors then, by default, TMS cannot assume that you can dial aliases directly and does not allow dialing by alias.

When attempting a call using scheduling, the TMS Scheduling Settings (also in Settings) of both systems are also taken into account. (For each call protocol there are two 'allow permissions': one for incoming calls and the other for outgoing calls.) TMS does not offer a call route if the 'allow permission' is not granted for the appropriate call direction/protocol combination for each system.

Related Information

• Technical Support & Documentation - Cisco Systems