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

Voice Feature Guide 01

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).
POTS Port Loop Test

POTS Port Loop Test

A POTS port loop test is used to test the hardware and configurations related to POTS services during device installation or before POTS service provisioning. It helps reduce the number of site visits and minimize maintenance costs.

Overview

Maintenance engineers can locally start a POTS port loop test on the device, or remotely log in to the device and then start the test. A POTS port loop test consists of two parts:
  • Device hardware test: This test targets at access nodes that are not yet provisioned with the voice service. When an access node is newly deployed, the hardware of the voice module needs to be tested to evaluate the hardware capabilities in supporting future voice services.

  • Device service test: This test targets at access nodes that are already provisioned with the voice service. Before voice services are provisioned from the access node to a user, a device service test is performed to determine whether the voice service capabilities are supported by the access node.

NOTE:
  • Do not pick up the phone during a loop test. Otherwise, the test results will be incorrect.
  • If the dialup mode of a PSTN port is set to DTMF-only, no loop test can be started on the PSTN port.

Device Hardware Test

The device hardware test involves the following items:
  • Off-hook detection
  • On-hook detection
  • Ringing and ringing stopping detection on a service port
  • Speech path detection
For the first 3 test items, a POTS board emulates off-hook, on-hook, ringing, and ringing stopping, while the control board of the device performs the loop test on the POTS board. The last test item (speech path detection) is used to verify the service processing capability of the chip through service loopbacks. A speech path detection involves 3 loopback tests: SLIC loopback test, CODEC loopback test, and DSP loopback test.
  • In a SLIC loopback test, a POTS port is connected to a DSP channel, and the DSP chip generates the DTMF authentication code, which is sent to the TDM side. The DSP chip then detects the DTMF returned from the TDM side to check whether the channel between the DSP, CODEC, and SLIC is normal, as shown in Figure 1-143.
    Figure 1-143 Working principles of a SLIC loopback test

  • In a CODEC loopback test, the CODEC loopback is set to the network side (remote loopback), and the DSP chip generates the DTMF authentication code, which is sent to the TDM side. The DSP chip then detects the DTMF returned from the TDM side to check whether the channel between the DSP and the CODEC is normal, as shown in Figure 1-144.
    Figure 1-144 Working principles of a CODEC loopback test

  • In a DSP loopback test on the TDM side, a DSP channel is looped back from the TDM side to the IP side, and the DSP chip generates the DTMF authentication code, which is sent to the TDM side. The DSP chip then detects the DTMF returned from the TDM side to verify the transmit and receive functions of the TDM side, as shown in Figure 1-145.
    Figure 1-145 Working principles of a DSP loopback test on the TDM side

NOTE:
In test mode, run the pots path-test frameid/slotid port portid type hardware command to start a device hardware test. The test results will be displayed after the test is completed. Engineers diagnose whether the system functions normally based on the test results.

Device Service Test

The principles of a device service test are similar to those of a call emulation test. In a device service test, the device acts as both the calling party and called party (that is, the dest port on the device calls another assistant port on the same device), and the system checks whether the configurations are correct. User ports do not enter the conversation state during a POTS port loop test. When the called port detects the ringing, the calling port emulates user on-hook, and therefore, no charge record is generated. A device service test checks:
  • Device interface data, including the signaling data (such as MG interface data, protocol parameters, and call server parameters)
  • User port data, including the media gateway (MG) IDs and terminal IDs (TIDs) of H.248 users and user accounts and service rights of SIP users
NOTE:
In test mode, run the pots path-test frameid/slotid port portid type business command to start a device service test. The test results will be displayed after the test is completed. Engineers diagnose whether the system functions normally based on the test results.
Translation
Download
Updated: 2019-02-22

Document ID: EDOC1100067358

Views: 12820

Downloads: 114

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