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


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


HUAWEI Bar 500 V600R019C00 Maintenance Guide

Describes how to maintain, and troubleshoot the Videoconferencing Endpoint.
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


You can use either of one-click trace diagnosis and signaling diagnosis at a time.

Sound and Color Bar Tests

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

Table 4-1 Sound and color bar tests


Item to Be Tested

Signal Stream


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 display 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. If a remote loopback test is performed, data is transmitted from the local site to a remote site, and then back to the local site. Table 4-2 lists the 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 4-2 Loopback tests


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 4-3 Network test


Item to Be Tested

Signal Stream


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 IP address, enter an IP address 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 IP address, enter a public IP address. Then click Start. If the test succeeds, the gateway address, NAT address, and IP address of your endpoint are correct.

Route Test

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

  1. Choose Maintenance > Diagnostics > Tracert.
  2. Set the parameters listed in Table 4-4.

    Table 4-4 Route parameters




    IP address

    Specifies the IP address of the destination device.


    Maximum hops

    Specifies the maximum allowed hops.

    Example: 5

    Timeout period (s)

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

    Example: 1

  3. Click Start to start route test.

One-Click Diagnostics Using the Web Interface

Web administrators and API users can perform one-click diagnostics on the endpoint. Diagnosis files help with fault location, including module log files, error reports, and trace information, and CHR files.

  1. Choose Maintenance > Diagnostics > One-Click Diagnostics.

    The One-Click Diagnostics dialog box is displayed.

  2. Select the module to diagnose and click Start.

    The diagnostics takes about 5 minutes.

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

    CHR files need to be uploaded to the SessionInsight for analysis. For details, see the SessionInsight Product Documentation.

Signaling Diagnostics

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.
  • Signaling diagnosis can last at most 10 minutes. Even if you do not click Stop, signaling diagnosis will automatically stop in 10 minutes from the time when the diagnosis starts. The diagnosis file cannot exceed 10 MB.
  1. Choose Maintenance > Diagnostics > Signaling Diagnostics.

    The Signaling Diagnostics dialog box is displayed.

  2. Click Start to start signaling diagnosis.

    When prompted, click OK.


    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.
Updated: 2019-06-25

Document ID: EDOC1100054964

Views: 8923

Downloads: 9

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