11-07-2012 04:52 AM - edited 03-18-2019 12:05 AM
Hi
Problem - built-in gatekeeper on Cisco MCU 4501 can't connect to a neighboring gatekeeper:
In a neighboring gatekeeper this one configured as a neighbor.
Why could this be?
Solved! Go to Solution.
11-09-2012 06:58 AM
In that case I think you would need to enable the H323/SIP logging feature on the MCU under logs->h323/SIP log, try to make a call and see what requests show up from the endpoint in the resulting log.
11-07-2012 09:34 AM
Hi Alexander,
Could you please translate the error you are getting in English? Its hard to understand the error in russian language.
Thanks
Saurabh
11-07-2012 10:28 AM
Hi Saurabh
Actually, there is no error messages appear.
The marked text says that 0 requests sent
11-08-2012 01:38 AM
If it hasn't sent any requests to the neighbour gatekeeper, then the MCU's gatekeeper hasn't received any requests from endpoints registered to it that it is unable to resolve itself. What testing have you done to establish that it cannot connect to the neighbouring gatekeeper? The gatekeeper will not send LRQs to the neighbour for locally-registered addresses (aliases it has in its own DB) or IP addresses - in both cases it will reply to the endpoint with an ACF without consulting the neigbour.
11-09-2012 06:17 AM
Thanks for reply
Local endpoin unable to establish a call to endpoint, connected to the neighbouring gatekeeper
11-09-2012 06:58 AM
In that case I think you would need to enable the H323/SIP logging feature on the MCU under logs->h323/SIP log, try to make a call and see what requests show up from the endpoint in the resulting log.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide