Huawei TE40 Administrator's Manual page 146

HUAWEI TE40&TE50&TE60 Videoconferencing
Endpoint
Administrator Guide
Problem
After the endpoint
starts, it fails to
register with the
GK.
Issue 01 (2013-09-30)
Possible Cause
are incorrect.
The GK with which the local
or remote endpoint registers
does not support the function
for placing calls using IP
addresses.
The parameters (GK address,
encryption password, and user
name) used for GK
registration are incorrect.
Another site with the same
number as your site has
already registered with the
GK.
The endpoint is disconnected
from an IP network.
NAT settings are incorrect.
Specifically, the local
endpoint is on a private
network while the GK is on a
public network. Check
whether your endpoint can
communicate with a public
network. If the endpoint
cannot, NAT settings are
incorrect.
The GK listening port, such as
port 1719, is restricted by the
network firewall.
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
12 Troubleshooting
Solution
Choose Advanced > Settings >
Network > IP > H.323 at your site
and the remote site, respectively.
Then, disable GK functions.
On the endpoint web interface,
choose Advanced > Settings >
Network > IP > H.323 and
correct the settings.
Contact the videoconferencing
system administrator to check
whether another site with the same
number as your site has already
registered with the GK. If such a
site exists, change the user name
of your site.
1. Verify that the endpoint is
connected to an IP network.
Specifically, the LAN indicator
on the rear panel of the
endpoint is steady green.
2. From the remote controlled UI,
choose Advanced >
Diagnostics > Network Test.
Enter the IP address of the
remote site and start a Ping
test. If the Ping test fails, a
network error has occurred. In
this case, contact the
administrator.
3. From the remote controlled UI,
choose Advanced > Settings >
Network > IP. Verify IP
network settings.
Choose Advanced > Settings >
Network > Firewall and verify
NAT settings.
Contact the videoconferencing
system administrator to resolve
this problem.
138