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).
Fault Diagnosis Methods

Fault Diagnosis Methods

Sound and Color Bar Tests

Table 8-1 lists the sound and color bar tests.

Table 8-1 Sound and color bar tests

Test

Item to Be Tested

Signal Stream

Sound

2 audio output

2 → Speaker

Color bar

4 video output

4 → Monitor

  • Sound test: Choose Maintenance > Diagnostics. On the Diagnostics page, click Sound Test. While the test audio stored on your endpoint plays, check the sound quality.
  • Color bar test: Choose Maintenance > Diagnostics. On the Diagnostics page, click Color Bar Test. Seven color bars are shown on the monitor for you to check the color quality.

Loopback Test

Your endpoint can transmit audio or video data on a channel to simulate an actual application and test whether the output is satisfactory. You can perform a local loopback test to check the local network connection or a remote loopback test to check the remote network connection. When you perform a remote loopback test, data is transmitted from your site to a remote site, and then back to your site. Table 8-2 lists the types of loopback tests available on your endpoint.
  • To enable your endpoint to communicate with other endpoints, stop the loopback test.
  • You cannot perform a loopback test on remote video if you are in a dual-stream conference.
Table 8-2 Loopback tests

Test

Item to Be Tested

Signal Stream

Audio loopback

Local audio module

Microphone → 1 → 2 → Speaker

Video loopback

Local video module

Camera → 3 → 4 → Monitor

Remote audio loopback

  • Remote audio module
  • Network transmission

Microphone → 1 → 5 → 6 → 7 → 8 → 6 → 5 → 2 → Speaker

Remote video loopback

  • Remote video module
  • Network transmission

Camera → 3 → 5 → 6 → 9 → 10 → 6 → 5 → 4 → Monitor

Network Test

Table 8-3 Network test

Test

Item to Be Tested

Signal Stream

Network

IP access

endpoint → LAN or public network

Before a test, verify that the LAN network port indicator is green, which indicates that your endpoint is correctly connected to an IP network.

  • In Address, enter an IP address or a domain name that is in a different network segment from your endpoint IP address. Then click Start. If the test succeeds, the gateway settings and IP address of your endpoint are correct.
  • If your endpoint is on a private network, in Address, enter a public IP address or domain name. Then click Start. If the test succeeds, the gateway settings, NAT address, and IP address of your endpoint are correct.

One-Click Diagnosis

Web administrators and API users can perform one-click diagnosis on the endpoint. The diagnosis file helps with fault identification.

  1. Choose Maintenance > One-Click Diagnosis.

    The One-Click Diagnosis dialog box is displayed.

  2. Click Start to start diagnosis.

    The diagnosis takes about 5 minutes.

  3. Click Download to save the diagnosis file to the local computer.

Signaling Diagnosis

Web administrators and API users can perform signaling diagnosis and export the diagnosis file from the endpoint web interface. The diagnosis file helps with fault identification.

  • Only one user can perform signaling diagnosis.
  • If not manually stopped, signaling diagnosis automatically stops after 10 minutes or when the diagnosis file size reaches 10 MB.
  1. Choose Maintenance > Signaling Diagnosis.

    The Signaling Diagnosis dialog box is displayed.

  2. Click Start to start diagnosis.

    When prompted, click OK.

    NOTE:

    Signaling diagnosis does not monitor media stream data, but will obtain site information, such as site numbers. Perform this operation with caution.

  3. Click Stop to stop signaling diagnosis.
  4. Click Download to save the diagnosis file to the local computer.

Route Test

A route test helps determine the path that a data packet at the network layer uses to access a destination address.

Before you perform route test, choose System Settings > Network > Network diagnostics and set Network diagnostics to Enable.

Table 8-4 lists the parameters that you need to set before performing a route test.

Table 8-4 Route parameters

Parameter

Description

Setting

Address

Specifies the IP address or domain name of the destination device.

Example: 10.10.10.1

Maximum hops

Specifies the maximum allowed hops.

Example: 5

Timeout time (s)

Specifies the timeout duration for the call waiting time, in seconds.

Example: 1

CHR Collection

The SessionInsight can analyze Call History Record (CHR) data files to help you quickly locate faults.

  • Periodically sending CHR data files to eSight

    The endpoint periodically sends CHR data files to eSight. Then the SessionInsight obtains the CHR data files from eSight and analyzes them.

    To use the function of periodically sending CHR data files to eSight, enable CHR collection as follows:

    Log in to the web interface of theendpoint, choose System Settings > Conference > Normal, and set CHR collection to Enable.

  • Manually sending CHR data files to eSight

    You can also download the collected CHR data files to a local directory and upload them to the SessionInsight. Then the SessionInsight can analyze the files in offline mode.

    Before manually sending CHR data files to eSight, ensure that the CHR collection function is working. That is, CHR collection is set to Enable under System Settings > Conference > Normal on the web interface of the endpoint.

    If the endpoint encounters a fault during its operations, log in to its web interface, choose Maintenance > Diagnosis, and click CHR Download to download CDR data files to your local PC. Then upload the files to the SessionInsight for fault analysis. For the detailed upload procedure, see the SessionInsight Product Documentation.

Translation
Download
Updated: 2019-01-31

Document ID: EDOC1000184611

Views: 30623

Downloads: 162

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