I'm trying to configure CM connected to a GK with H.323 clients registered with the GK.
It should be fairly simple but I've only got communication in one direction:
Calls from CM to the GK work perfectly. But calls from the GK-clients to CM do not work.
CM sees the call setup come in but, as it doesn't recognise the IP address, it just drops the call. We can MAKE it work by hardcoding the IP address as an H.323 phone but as they typically use DHCP this isn't a solution.
- Can anyone suggest the workaround - at the moment the CSS of the trunk is simply ignored?
- Is there anyway to force the setup message to come into CM from the GK instead of the originating device?
The SRND says DHCP clients are supported by configuring a route pattern to point to the H.225 trunk - but it doesn't say how to make it work in the opposite direction!
Re: H.323 clients connected via GK-controlled Trunks?
Thank you - we're using 5.1 but that still has the "Accept Unknown TCP Connection".
I've tried changing this but it makes no difference. The SRND says:
"As discussed in previous sections, when a gatekeeper routes a call to the H.225 trunk of
Cisco CallManager, Cisco CallManager looks at the source IP address of the calling endpoint and tries to match that address to a device in its database. If it finds a matching IP address, Cisco CallManager applies that device's calling search space and other relevant settings. If it does not find a match, Cisco CallManager applies the calling search space and other relevant settings of the trunk."
I'm just not sure how it associates the incoming call with the trunk - any ideas?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...