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).
Call Emulation Test

Call Emulation Test

A call emulation test emulates call functions to verify data configuration for the voice service. The call emulation test can also be used to locate voice service faults.

Introduction to the Call Emulation Test

Definition
In a call emulation test, the device emulates the call function of a voice user. It is used to test the services on the POTS user port. A call emulation test includes:
  • Calling party emulation test: The POTS user port on the device functions as the calling party. In this test, a test engineer acting as a called party is required.
  • Called party emulation test: The POTS user port on the device functions as the called party. In this test, a test engineer acting as a calling party is required.
  • Calling and called party emulation test: Two POTS user ports function as the calling and called parties. The test does not require manual operations. Specifically, the device automatically performs the process from calling party off-hook to called party off-hook to set up a call between the two parties and stops the test after the call hold time expires.
Application Scenarios
A call emulation test can be used in the following scenarios:
  • Acceptance test during a new deployment: The software and hardware functions, including service configurations, of the device need to be verified after the device is installed. The verification ensures follow-up service provisioning.

    Traditionally, the engineer goes to the device installation site, makes cables, connects a test phone set to the ONT, uses the test phone set as a caller or callee, and verifies basic voice services.

  • Fault locating in the OAM phase: After the device enters the OAM phase, it is usually necessary to test basic voice services in order to locate a fault. In the access network, however, a large number of devices are installed in complicated environment, geographically dispersed, and remotely located. It is inconvenient and costly either to test a newly installed device or locate faults.

Call emulation tests can be conducted remotely. In a call emulation test, the test engineer does not need to prepare cables on the device installation site, connect test terminals to the device, or perform dialup tests on site. Instead, the test engineer enables the call emulation function in the maintenance center through the command line interface (CLI) or network management system (NMS) and uses a test phone set in the central office (CO) to make calls to the emulation port on the device. In this way, the test engineer can verify the data configurations and basic service functions.

Benefits
  • The call emulation feature can be used to remotely verify and accept services and locate faults, which greatly reduces the operating expense (OPEX) for carriers.
  • The call emulation feature shortens fault location time, which significantly improves the fault locating efficiency.

Principles of the Call Emulation Test

In a call emulation test, the system emulates the actions of a user port to achieve the emulation of the calling party and called party. The actions of a user port include off-hook, on-hook, number dialing, and ringing detection. Figure 1-136 shows the principles of a call emulation test. The test phone set, placed at the central office (CO), is used to perform a call emulation test with a configured port on the access node. This test method remotely checks whether the voice service on the device is functional.
NOTE:
For a calling and called party emulation test, no phone set is required. Both the calling and called parties are emulated by the POTS ports on the access node.
Figure 1-136 Principles of a call emulation test

Networking Application
Figure 1-137 shows the example network of a call emulation test.
Figure 1-137 Example network of a call emulation test
A call emulation test checks whether the voice service is functional only on the network side of the device.
  • If a conversation channel cannot be established during a call emulation test, check whether the network data configurations are correct.
  • If the conversation channel is established but the voice is not clear during a call emulation test, check whether the cables are connected properly.
If test engineers need to check whether the voice service is functional on the user side, they can:
  • Perform a POTS user loop line test to check whether the line between the device and the user phone set is functional. For details, see POTS User Loop Line Test.
  • Perform a POTS user circuit test to check whether the POTS board on the device is functional. For details, see POTS User Circuit Test.
Calling Party Emulation Test
In a calling party emulation test, the device port emulates user off-hook, number dialing, communication, and on-hook.
  1. Start a calling party emulation test.

    On the access node, the test engineer sets the POTS_1 port as the calling party emulation port, configures the phone number to be dialed, and starts the calling party emulation test. If the function of playing alert tones upon the test beginning is enabled, alert tones are played after the test is started.

  2. Initiate the calling party emulation test.
    Figure 1-138 Interaction between the POTS_1 port and phone set during a calling party emulation test

    NOTE:

    The information marked red in the following figure indicates the operations that need to be performed by the test engineer on the test phone set at the CO.

    1. The calling party emulation test is started on the access node and the calling party emulation port automatically emulates user off-hook. After detecting the dial tone, the port emulates number dialing.
    2. The called party (whose number is automatically dialed by the calling party emulation port) waits for the phone to ring. If the phone rings, the signaling channel is functional and the configured data is correct. If the phone does not ring, the test engineer needs to check service data (such as route, VLAN, and core-network data), troubleshoot the voice fault if any, and perform the test again.
    3. The called party picks up the phone. The call is set up.
    4. The calling party emulation port plays announcements for the called party.
    5. The test engineer checks whether the announcements are clearly heard. After hearing the announcements, the test engineer presses the specified verification number (a matched DTMF number, the asterisk key (*) by default), indicating that the media channel is functional. The test result is "Test Succeed."
      NOTE:
      If the function of playing alert tones based on the DTMF matching result is enabled, the system plays the alert tones after the test engineer presses the DTMF number. The alert tones include the DTMF number matching success alert tone and DTMF number matching failure alert tone.
  3. Obtain the test result. If the test fails, the system outputs the failure causes, with which the test engineer can identify the possible cause of the fault.

    Table 1-17 lists the test results.

Called Party Emulation Test
In a called party emulation test, the POTS port on the access node emulates a called party. The called party emulation port automatically emulates user off-hook after detecting the ringing current.
  1. Start a called party emulation test.

    On the access node, the test engineer sets the POTS_1 port as the called party emulation port and starts the called party emulation test. If the function of playing alert tones upon the test beginning is enabled, alert tones are played after the test is started.

  2. Initiate the called party emulation test.
    Figure 1-139 Interaction between the POTS_1 port and phone set during a called party emulation test

    NOTE:

    The information marked red in the following figure indicates the operations that need to be performed by the test engineer on the test phone set at the CO.

    1. The test engineer picks up the phone, hears the dial tone, and dials the number of the POTS_1 port.
    2. If the called party emulation port of the device detects the ringing current, the configured user data is correct. If the called party emulation port does not detect the ringing current, the test engineer needs to check service data (such as route, VLAN, and core-network data), troubleshoot the voice fault if any, and perform the test again.
    3. If the calling party hears ringback tones before the called party picks up the phone (in this test, off-hook is automatically emulated by the called party emulation port), the signaling channel is functional. Otherwise, the test engineer needs to verify the configured service data and perform the test again.
    4. The called party emulation port emulates off-hook. The call is set up.
    5. The called party emulation port plays announcements for the calling party.
    6. The test engineer checks whether the announcements are clearly heard. After hearing the announcements, the test engineer presses the specified verification number (a matched DTMF number, the asterisk key (*) by default), indicating that the media channel is functional. The test result is "Test Succeed."
      NOTE:
      If the function of playing alert tones based on the DTMF matching result is enabled, the system plays the alert tones after the test engineer presses the DTMF number. The alert tones include the DTMF number matching success alert tone and DTMF number matching failure alert tone.
  3. Obtain the test result. If the test fails, the system outputs the failure causes, with which the test engineer can identify the possible cause of the fault.

    Table 1-18 lists the test results.

Calling and Called Party Emulation Test
In a calling and called party emulation test, two POTS ports emulate the calling party and called party respectively. The calling party emulation port emulates the actions of the calling party, while the called party emulation port emulates the actions of the called party. These two ports automatically emulate calling party off-hook, number dialing, called party off-hook (after detecting the ringing current), mutual DTMF number sending for media channel verification, and on-hook after the verification.
NOTE:
A calling and called party emulation test does not require any manual operation, which greatly improves the test efficiency. In this test, the device automatically verifies whether the media channel is functional. However, the device's sensitivity to media streams may vary from the human ears' sensitivity to media streams. Therefore, the call quality cannot be verified.
  1. Start a calling and called party emulation test.

    On the access node, the test engineer sets the POTS_1 port as the calling party emulation port and the POTS_2 port as the called party emulation port, configures the phone number to be dialed, and starts the calling and called party emulation test.

  2. Initiate a calling and called party emulation test.
    Figure 1-140 Interaction between the POTS_1 and POTS_2 ports during a calling and called party emulation test

    1. The calling and called party emulation test is started on the access node and the POTS_1 port automatically emulates user off-hook. After detecting the dial tone, the port emulates number dialing.
    2. The POTS_2 port (whose number is automatically dialed by the POTS_1 port) waits and checks whether the ringing current can be detected. If the POTS_2 port detects the ringing current, the signaling channel is functional and the configured user data is correct. If the POTS_2 port does not detect the ringing current, the test engineer needs to check service data (such as route, VLAN, and core-network data), troubleshoot the voice fault if any, and perform the test again.
    3. The POTS_2 port emulates off-hook. The call is set up.
    4. The POTS_1 and POTS_2 ports send the DTMF number to each other to verify whether the media channel is functional. If the DTMF numbers sent by POTS_1 and POTS_2 ports are correct, the media channel is functional. The test result is "Test Succeed."
  3. Obtain the test result. If the test fails, the system outputs the failure causes, with which the test engineer can identify the possible cause of the fault.

    Table 1-17 and Table 1-18 list the test results.

Test Results
Table 1-17 Results of a calling party emulation test

Test Result

Description

Test Succeed

The test is successful. The media channel of the test port is functional.

Test Failed: No dialing tone is played when the calling party dials a number

The calling party emulation port does not detect the dial tone. Possible causes are as follows:
  • The calling party emulation port does not detect the off-hook signal.
  • The off-hook signal is not reported.
  • No dial tone is issued after the off-hook signal is reported.

Test Failed: Busy tone is played after the calling party picks up the phone off the hook

The calling party emulation port detects the busy tone. Possible causes: The calling party emulation port does not subscribe to the POTS services or the digital signal processor (DSP) is faulty.

Test Failed: Busy tone is played when the calling party dials a number

The calling party emulation port detects the busy tone during number dialing. Possible cause: The number that the calling party emulation port dials does not match the digitmap.

Test Failed: The calling party does not dial a number

The calling party emulation port does not automatically emulate number dialing after detecting the dial tone. Possible cause: The internal processing mechanism of the system encounters an error.

Test Failed: Busy tone is played after the calling party dials a number

The calling party emulation port detects the busy tone after number dialing. Possible causes: The dialed number is busy or the dialed number is incorrect.

Test Failed: The calling party does not communicate with the called party after dialing a number

The call is not set up. Possible cause: The called party does not pick up the phone.

Test Failed: Release before pick-up of the calling party

The call is released before the calling party and called party enter a conversation. Possible cause: The signaling processing mechanism encounters an error.

Test Failed: The number matching of the calling party is not complete

The calling party emulation port fails to match the DTMF number sent by the called party after entering the conversation. Possible causes: The called party does not press the DTMF number or the DTMF number is lost during the transmission.

Test Failed: The number sending of the calling party is not complete

The called party does not complete the sending of the DTMF number to the calling party emulation port after entering the conversation. Possible cause: The called party hangs up the phone before the sending of the DTMF number is completed.

Test Failed: The number matching of the calling party fails

The DTMF number sent from the called party is incorrect.

Test Failed: The calling port is abnormal

The calling party emulation port is faulty. Possible causes are as follows:
  • The board is faulty.
  • The board is removed.
  • The calling party emulation port is faulty.
Table 1-18 Results of a called party emulation test

Test Result

Description

Test Failed: The phone of the called party does not ring

The called party emulation port does not receive any call. Possible causes: The calling party dials the wrong number or the signaling transmission encounters an error.

Test Failed: The called party does not pick up the phone off the hook

The called party emulation port does not automatically emulate off-hook after detecting the ringing current. Possible cause: The internal processing mechanism of the system encounters an error.

Test Failed: Busy tone is played after the called party picks up the phone off the hook

The called party emulation port detects the busy tone after off-hook. Possible cause: The calling party hangs up the phone.

Test Failed: The called party does not communicate with the calling party

The called party emulation port cannot enter the conversation after off-hook. Possible cause: The called party emulation port emulates off-hook so slowly that the calling party has hung up the phone.

Test Failed: Release before pick-up of the called party

The call is released before the calling party and called party enter a conversation. Possible cause: The signaling processing mechanism encounters an error.

Test Failed: The number matching of the called party is not complete

The called party emulation port fails to match the DTMF number sent by the calling party after entering the conversation. Possible causes: The calling party does not press the DTMF number or the DTMF number is lost during the transmission.

Test Failed: The number sending of the called party is not complete

The calling party does not complete the sending of the DTMF number to the called party emulation port after entering the conversation. Possible cause: The calling party hangs up the phone before the sending of DTMF number is completed.

Test Failed: The number matching of the called party fails

The DTMF number sent from the calling party is incorrect.

Test Failed: The called port is abnormal

The called party emulation port is faulty. Possible causes are as follows:
  • The board is faulty.
  • The board is removed.
  • The called party emulation port is faulty.

Principle Demonstration of the Call Emulation Test

The principle demonstration for a call emulation test includes three parts: calling party emulation test, called party emulation test and calling and called party emulation test.

NOTE:

See the following the principle demonstration. In actual applications, commands are executed to start calling party emulation test, called party emulation test and calling and called party emulation test, in which, port IDs are set according to specific devices.

Configuring the Call Emulation Test

Prerequisites

  • The voice service must be configured.
  • A normal phone must be provided.

Procedure

  1. Run the simulate call parameter command to configure the parameters for the call emulation test.

    The type of the call emulation alert tone and DTMF number must be set before the automatic call emulation test is performed on the port.

    By default, the type of the call emulation alert tone is voice announcement.

  2. Run the display simulation call parameter command to query the parameters configured for the current call emulation test.
  3. Start a call emulation test. You can start a calling party emulation test, a called party emulation test, or a calling and called party emulation test based on actual requirements.

    • To start a calling party emulation test, run the simulate call start caller command.
    • To start a called party emulation test, run the simulate call start callee command.
    • To start a calling and called party emulation test, run the simulate call start call command.

Result

After completing the call emulation test, the device directly outputs the test result. The test result is used to check whether the call is normal.

Translation
Download
Updated: 2019-02-22

Document ID: EDOC1100067358

Views: 15883

Downloads: 161

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