Chapter 12 IP Video Telephony Configuration
Gatekeeper Configuration for IP Video Telephony
| ================================ | | |
CallSignalAddr | Port RASSignalAddr | Port Zone Name | Type | Flags |
--------------- ----- --------------- ----- --------- | ---- | ----- |
0.9.10.5 | 33209 10.9.10.5 | 32783 SJC-MP-GK-1 | H323-GW | |
H323-ID: SJC-RFD-MP-1-CM1_2_3 | | | |
Voice Capacity Max.= Avail.= Current.= 0
Zone prefixes were configured in the Cisco Unified CallManager zone for intercluster call flows. This configuration is required for intercluster gatekeeper-controlled call routing. The other two zones do not require a local zone prefix to be configured. The endpoints and MCUs are directed to these zones by the Zone Subnet command in the gatekeeper configuration.
The Cisco Unified CallManager cluster uses the default technology prefix 1#* to register its gatekeeper-controlled intercluster trunks in the Cisco Unified CallManager zone. Then,
Cisco Unified CallManager cluster registers a dedicated H.225 gatekeeper-controlled trunk to the MCU zone. The trunk and the MCU zone are used for invites initiated from the MCU Conference control web pages. Finally, the Cisco Unified CallManager cluster registers a special trunk called RasAggregator to the H.323 endpoints zone. This trunk is dynamically created and registered as a result of the H.323 endpoints device pool configuration in Cisco Unified CallManager.
The following partial output from the Show Gatekeeper Endpoints command shows a single
Cisco Unified CallManager RasAggregator trunk that is registered to a gatekeeper:
SJC-RFD-GK-1#show gatekeeper endpoints | |
| | GATEKEEPER ENDPOINT REGISTRATION | |
| | ================================ | |
CallSignalAddr | Port | RASSignalAddr | Port Zone Name | Type |
--------------- | ----- --------------- ----- --------- | ---- |
10.9.10.5 | 33206 | 10.9.10.5 | 32783 SJC-VIDEO-GK-1 | H323-GW |
H323-ID: RasAggregator_1#*_SJC-VIDEO-GK-1_3 | |
Voice Capacity Max.= Avail.= Current.= 0 | |
A single RasAggregator trunk was created for all gatekeeper-controlled H.323 endpoints that share the same gatekeeper zone and Cisco Unified CallManager group. All gatekeeper-controlled H.323 endpoints within the same gatekeeper endpoint zone must be configured as part of the same Cisco Unified CallManager group and device pool, otherwise Cisco Unified CallManager will register multiple RasAggregator trunks to a single gatekeeper endpoint zone. In this situation, some incoming calls from the H.323 endpoints will fail.
Note This configuration prevents gatekeeper-controlled H.323 endpoints from being load balanced across multiple Cisco Unified CallManager servers by using device pools and Cisco Unified CallManager groups. One way to accomplish such load balancing is to create multiple gatekeeper zones dedicated to H.323 endpoints for each device pool or Cisco Unified CallManager group.
For an example of a video gatekeeper configuration, see the >>>>>>>
| System Test Architecture Reference Manual for IP Telephony |
12-8 | OL-11591-01 |
