I have an H323 gateway configured with primary and alternate gatekeepers. Priorities were not configured, so both gatekeepers SHOULD show as 127. However, the first gatekeeper configured shows a priority of 127, the other gatekeeper shows a priority of 0.
I am able to connect to both gatekeepers from the gateway.
I did some research and see that there are some bugs out there on earlier versions which cause the priority to show incorrectly. but i'm wondering if the bug would only be cosmetic (show the priority as incorrect) or if the priority is actually incorrect.
This is happening on multiple gateway / gatekeeper configurations all with the same gatekeeper priority default configuration and showing the same 0 / 127 priorities in the show gateway
I am wondering if the registration failure alerts is due to the priority showing as 0, and if the fix might be to manually configure the gatekeepers' priority.
Has anyone else seen this issue?
H.323 ITU-T Version: 4.0 H323 Stack Version: 0.1
H.323 service is up Gateway GATEWAY is registered to Gatekeeper GATEKEEPER-PRI
Alias list (CLI configured) H323-ID GATEWAY Alias list (last RCF) H323-ID GATEWAY
H323 resource thresholding is Disabled Permanent Alternate Gatekeeper List priority 0 id GATEKEEPER-ALT ipaddr 10.76.155.172 1719 register needed priority 127 id GATEKEEPER-PRI ipaddr 10.76.155.171 1719 register needed Primary gatekeeper ID GATEKEEPER-PRI ipaddr 10.76.155.171 1719
Showing alerts in logs:
074975: Mar 14 10:45:51.195 EDT: %CCH323-2-GTWY_REGSTR_FAILED_ALT_GK: Gateway GATEWAY failed attempt to register with Alternate Gatekeeper GATEKEEPER-ALT 074976: Mar 14 10:45:51.251 EDT: %CCH323-6-REGSTR: Gateway GATEWAY registered with Gatekeeper GATEKEEPER-PRI 074994: Mar 14 10:46:06.715 EDT: %CCH323-2-GTWY_REGSTR_FAILED_ALT_GK: Gateway GATEWAY failed attempt to register with Alternate Gatekeeper GATEKEEPER-ALT 074995: Mar 14 10:46:06.771 EDT: %CCH323-6-REGSTR: Gateway GATEWAY registered with Gatekeeper GATEKEEPER-PRI
interface Loopback0 ip address 10.174.102.171 255.255.255.255 ip pim sparse-dense-mode h323-gateway voip interface h323-gateway voip id GATEKEEPER-PRI ipaddr 10.176.155.171 1719 h323-gateway voip id GATEKEEPER-ALT ipaddr 10.176.155.172 1719 h323-gateway voip h323-id GATEWAY h323-gateway voip tech-prefix 700# h323-gateway voip bind srcaddr 10.174.102.171
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.