No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

GK Registration Fails on the Standalone SC

Publication Date:  2019-04-10 Views:  102 Downloads:  0

Issue Description

The TE60 fails to register with the GK. A message is displayed on the web interface indicating that the GK is not found. Signaling diagnosis shows that the SC receives the RRQ message from the endpoint but does not reply.

Alarm Information

NONE

Handling Process

1. Signaling diagnosis shows that the SC receives the RRQ message from the endpoint but does not reply.

2. Confirm that the version of the customer's SMC matches the version of the endpoint.

3. It is suspected that there is a conflict between GK and SIP registrations. However, after the SIP is disabled, the GK registration still fails.

4. Check the SC configuration, SC routing table, and network configuration of the endpoint.

dis sys-config and dis static-route

As shown in the following figures, the IP address of the endpoint seemingly in the same network segment is actually in a different network segment from that of the IP addresses in the SC's routing table, because the subnet masks are different. In this case, the SC does not accept registration messages from an endpoint that is in a different network segment.

5. The customer is advised to configure a static route on the lan1 interface by command lines.

<SC(system-view)>static-route add dest-address *.*.*.* mask-or-prefix *.*.*.* network-port lan1

The customer replies that adding the configured static route always fails, as shown in the following:

<SC(system-view)>static-route add dest-address *.*.33.194 mask-or-prefix 255.255.255.192 network-port lan1
execute failed
ERR_BUSINESS_COMMAND_PARAM_ERROR

Later the static route is successfully configured through remote access to the customer's PC. It is suspected that the command manually entered by the customer is incorrect because of Chinese characters in the command or other errors.

<SC(system-view)>static-route add dest-address *.*.33.194 mask-or-prefix 255.255.255.255 network-port lan1

After the problem is solved, the endpoint can register with the GK.

Suggestions

When the customer adds a route, there are always messages indicating parameter errors, which may be caused by manual input of addresses in the command. The Tab key is recommended to complete a command being entered, to prevent incorrect input of command parameters.

END