Yes! I have finally joined the realm of fellow Vol 2 Cisco nerds.
On Question 4.2, make sure to uncheck "Wait for far end H.245 terminal
capability set" on the H.225 gatekeeper-control trunk configured in
CUCM. Otherwise, your call from HQ to BR2 will ring, but not be
established.
The reason for it is found in the CUCM SRND, page 8-46
The Wait For Far End H.245 Terminal Capability Set (TCS) option must be
unchecked to prevent
stalemate situations from occurring when the H.323 devices at both sides
of the trunk are waiting
the far end to send TCS first and the H.245 connection times out after a
few seconds.
And again on 16-11
By default, the Wait for Far-End to Send TCS option is enabled
(checked). However, you must uncheck
(disable) it in the following circumstances:
*When the H.323 device communicating with Unified CM is also waiting for
the far-end to send its TCS*
In this case, a stalemate occurs because neither side sends its TCS, and
the H.245 connection times
out after a few seconds. Examples of devices that also wait for the
far-end to send TCS are some
H.323 routed-mode gatekeepers, H.320 gateways, H.323 proxies (or
IP-to-IP gateways) and some
H.323 multipoint conference bridges. These devices wait for the far-end
to send TCS for the same
reason Unified CM does: because they are waiting for both sides of the
connection to send their
TCSs before forwarding them to the other side.
*When communicating with another Unified CM cluster over an intercluster
trunk*
In many scenarios, Unified CM performs the role of a software switch
connecting two endpoint devices
(such as two H.323 clients that are trying to call each other). In such
cases, it is best if Unified CM waits
until both devices have sent their TCS messages so that it knows the
capabilities of each device and can
therefore make the most intelligent decision about what TCS to send back
to each party (depending on
region and location configs, among other things). In these cases, the
Wait for Far-End to Send
TCS feature should be enabled.
However, some other H.323 devices (such as an H.320 gateway, which
connects an H.323 device to an
H.320 device) also perform the function of connecting two or more
parties together. The gateway also
prefers to wait until both ends send their TCS messages, so that it can
make the most intelligent choice
about how to set up the call. A stalemate could result if Unified CM and
the gateway both wait for the
other side to send their TCSs. To avoid this stalemate situation,
disable (uncheck) the Wait for Far-End
to Send TCS feature.
*Matthew Berry*
/A+, CCENT, CCNA, CCNA Voice, CCVP, CCIE Voice Written/
*_Vitals:_*
*GVoice: *+1.612.424.5044
*Gmail*: ciscovoiceg...@gmail.com
*Skype*: ciscovoiceguru
*Twitter*: ciscovoiceguru
*_Cert Stats:_*
Cisco Cert Journey Began: Jan 1, 2009
1st Lab Attempt: Aug 16, 2010
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
