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

Maintenance Guide

TE30, TE40, TE50, TE60, and TX50 Videoconferencing Endpoint V600R006C10

This document guides the operator to maintain the device
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Conference Initiation

Conference Initiation

Table 8-9 lists the troubleshooting methods for common problems you may encounter during conference initiation.

Table 8-9 Methods for troubleshooting common conference initiation problems

Problem

Possible Cause

Solution

Your site and a remote site cannot call each other using site numbers.

Your site or the remote site has not registered with a GK or SIP server. A GK or SIP server is responsible for translating site numbers into IP addresses. If either your site or the remote site does not register with a GK or SIP server, the translation cannot be implemented, and your site cannot place a call to the remote site using the site number.

If a remote site places a call to your site by site number, it will receive a message from the GK or SIP server indicating that your site has not registered with the GK or SIP server, and the call cannot be set up.

Verify GK or SIP server registration settings and register your site and the remote site with a GK or SIP server.

The local or remote endpoint is not connected to an IP network.

  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. On the remote control 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. On the remote control UI, choose Advanced > Settings > Network > IP. Verify IP network settings.

Your site cannot place a call to a remote site using the IP address of the remote site.

The local or remote endpoint is not connected to an IP network.

  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. On the remote control 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. On the remote control UI, choose Advanced > Settings > Network > IP. Verify IP network settings.

NAT settings are incorrect. Specifically, the local endpoint is on a private network while the remote endpoint is on a public or different private network. Check whether your endpoint can communicate with a public network. If the endpoint cannot, NAT settings are incorrect.

Choose Advanced > Settings > Network > Firewall and verify NAT settings.

The GK with which the local or remote endpoint registers does not support the function for placing calls using IP addresses.

Choose Advanced > Settings > Network > IP > H.323 at your site and the remote site, respectively. Then, disable GK functions.

After the endpoint starts, it fails to register with the GK.

The parameters (GK address, encryption password, and user name) used for GK registration are incorrect.

On the endpoint web interface, choose Advanced > Settings > Network > IP > H.323 and correct the settings.

Another site with the same number as your site has already registered with the GK.

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.

The endpoint is not connected to an IP network.

  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. On the remote control 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. On the remote control UI, choose Advanced > Settings > Network > IP. Verify IP network settings.

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.

Choose Advanced > Settings > Network > Firewall and verify NAT settings.

The GK listening port, such as port 1719, is restricted by the network firewall.

Contact the videoconferencing system administrator to resolve this problem.

A predefined conference fails to be initiated on the endpoint.

The endpoint is not connected to an IP network.

  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. On the remote control 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. On the remote control UI, choose Advanced > Settings > Network > IP. Verify IP network settings.

Multiple conferences are currently being held while port resources in the videoconferencing system are insufficient.

Wait until the resources are available. Alternatively, reduce the number of sites attending the conference and then add sites as required after the conference is held successfully.

The SiteCall account for using the 4E1 lines is incorrect.

Contact the videoconferencing system administrator to resolve this problem.

Translation
Download
Updated: 2019-01-31

Document ID: EDOC1000184611

Views: 30515

Downloads: 162

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next