Hi, all!
Have a nice day to you!
The topic describes a solution to GK registration failure on the SMC.
Alarm Description
A device fails to register with the gatekeeper (GK).
Alarm
0x00900003
Impact on the System
The device cannot join an H.323 conference.
Possible Causes
The number of actually registered nodes reaches the maximum number allowed by the SC.
The registered H.323 ID and number, user name, or password on the participant side are different from those on the SMC side.
Troubleshooting
Log in to the SMC web interface and choose Devices > Switch Centers. On the page that is displayed, check the working status of the SC to register, click the SC, and choose Details > License Information > Maximum number of registered nodes. (If there is no license information, the maximum number of registered nodes is 10.)
Under Registered Nodes of the SC information page, check whether the number of registered nodes in the registration list is greater than Maximum number of registered nodes.
If yes, deregister some devices from the GK or contact the service provider to obtain a license with a larger capacity.
If no, go to Step 3.
For a manageable participant: Log in to the SMC web interface, and choose Devices > Participants. On the page that is displayed, select the participant, and choose Edit Participant > H.323 to modify corresponding information.
For an unmanageable participant:
Log in to the SMC web interface and choose Devices > Participants. On the page that is displayed, select the participant, choose Edit Participant > H.323, and record GK address, H.323 ID, and E.164 alias. If User name and Password are preset, record their settings also.
Log in to the device web interface and choose System Settings > Network > H.323/SIP Settings > H.323. On the page that is displayed, set H.323 ID and E.164 and set other parameters as required and ensure that the settings on the SMC side are the same as those on the device side.
Thanks for reading!
