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).
Configuring the VoIP PSTN Service (H.248-based or MGCP-based)

Configuring the VoIP PSTN Service (H.248-based or MGCP-based)

This topic describes how to configure the VoIP PSTN service when the protocol adopted by the Access node is H.248 or MGCP.

Application Context

The voice over IP (VoIP) service uses the IP packet switched network for transmission after the traditional analog voice signals are compressed and packetized, to lower the cost of the voice service.

In the NGN network, the Access node functions as an access gateway (AG) and exchanges signaling with the media gateway controller (MGC) through the MG control protocol (mainly H.248 and MGCP). In this way, the VoIP, FoIP, and MoIP services are implemented under the control of the MGC. The MG interface, as an interface for the communication between the Access node (AG) and the MGC, plays a decisive role in the H.248-based or MGCP-based VoIP service.

H.248, also called MeGaCo, is a protocol developed based on MGCP by combining the features of other media gateway control protocols. Compared with MGCP, H.248 supports more types of access technologies and supports mobility of terminals; however, the configuration of the H.248-based VoIP service is the same as that of the MGCP-based VoIP service.

Prerequisite

  • To implement the VoIP service, the MG interface must be configured and must be in the normal state.
  • According to the actual network, a route from the Access node to the MGC must be configured to ensure that the Access node and the MGC are reachable from each other.
  • The voice daughter board on the control board works in the normal state.
  • Electronic switch 1 must be in location-0 (indicating that the VoIP service is supported) If the SCUB control board is used. For details about how to configure the electronic switch, see electro-switch.

Precaution

The MG control protocols (H.248 and MGCP) are master/slave protocols, and the MGC controls the AG to implement the call connection. Therefore, the data on the AG for interconnection with the MGC, including the attributes of the MG interface and the attributes of the VoIP user, must be the same as the corresponding data on the MGC. Before configuring the VoIP service, you must make the data plan by considering interconnection with the MGC.

Data preparation

Table 1-35 provides the data plan for configuring the VoIP service.
Table 1-35 Data plan for configuring the H.248-based or MGCP-based VoIP service

Item

Remarks

MG interface data

(The data configuration must be the same as the data configuration on the MGC.)

Media and signaling parameters

Media and signaling upstream VLAN

It is used as the upstream VLAN of the VoIP service to be configured. Standard VLAN is recommended.

Media and signaling upstream port

It is used as the upstream port of the VoIP service to be configured.

Media and signaling IP addresses

These IP addresses must be selected from the media and signaling IP address pools. The media and signaling IP address pools consists of all the IP addresses of the Layer 3 interface of the media and signaling upstream VLAN.

NOTICE:

The MGCP interface on the Access node does not support the isolation of media streams and signaling flows. Therefore, when the MGCP protocol is used, the media IP address pool and the signaling IP address pool must be the same. When the H.248 or SIP protocol is used, the media IP address pool and the signaling IP address pool can be the same or different.

Default IP address of the MG

It is the next hop IP address from the Access node to the MGC.

Parameters of the MG interface

NOTE:

Parameters listed here are mandatory, which means that the MG interface fails to be enabled if these parameters are not configured.

MG interface ID

It is the MG interface ID used for the VoIP service to be configured, which determines the virtual access gateway (VAG) specified for the user.

Signaling port ID of the MG interface

It is the transport layer protocol port ID used for the signaling exchange between the Access node (AG) and the MGC.

  • Default signaling port ID defined in H.248: 2944 (text) and 2945 (binary)
  • Default signaling port ID defined in MGCP: 2727

IP address of the primary MGC to which the MG interface belongs

When dual homing is not configured, the parameters of the primary MGC need to be configured. When dual homing is configured, the IP address and the port ID of the secondary MGC also need to be configured.

Port ID of the primary MGC to which the MG interface belongs

Coding mode of the MG interface

Currently, the text coding mode is supported.

NOTE:

For the MG interface that supports MGCP, the default coding mode is the text coding mode. This parameter can be queried, but cannot be configured.

Transmission mode of the MG interface

The transmission mode is selected according to the requirements on the MGC side. Generally, UDP is adopted.

NOTE:

For the MG interface that supports MGCP, the default transmission mode is UDP. This parameter can be queried, but cannot be configured.

Domain name of the MG interface

It corresponds to the parameter domainName of the MG interface.

  • When the MGCP protocol is used, this parameter must be configured. Otherwise, the MG interface fails to be enabled.
  • When the H.248 protocol is used, this parameter must be configured if the parameter MIDType of the H.248 message is configured as the domain name. Otherwise, the MG interface fails to be enabled. In other situations, this parameter is optional.

Profile index of the MG interface

If the MGC interconnected with the MG is also made by Huawei, set the profile index to 1 or do not set it (it is 1 by default); if the MGC interconnected with the MG is made by another manufacturer, set the profile index to the corresponding value of the manufacturer.

Device name of the MG interface

It is supported by the H.248 protocol, and corresponds to the parameter deviceName of the MG interface that uses the H.248 protocol.

When the H.248 protocol is used, this parameter must be configured if the parameter MIDType of the H.248 message is configured as the domain name. Otherwise, the MG interface fails to be enabled. In other situations, this parameter is optional.

Digitmap of the MG interface

The digitmaps here are used for certain special applications such as emergency calls and emergency standalone. The digitmaps for common phone services are issued to the AG by the MGC, and therefore such digitmaps do not need to be configured on the AG. If the services such as emergency calls and emergency standalone are not required, the digitmaps do not need to be configured.

Software parameters of the MG interface

According to the service requirements, the configuration of software parameters determines whether the MG interface supports the functions such as dual homing and emergency standalone.

Ringing mode of the MG interface

According to the service requirements, the ringing modes of the MG interface need to be determined.

Terminal ID (TID) format of the MG interface

The TID format determines the generation mode of various types of user terminals on an MG interface.

Voice user data

(The data configuration must be the same as the data configuration on the MGC.)

Slot of the voice service board

-

User data

Phone number

The phone numbers allocated by the MGC need to be determined, and the paging numbers for users' emergency standalone need to be planned if the emergency standalone function is provided.

TID

If the TID template with which the PSTN user is bound does not support terminal layering, this parameter needs to be configured.

User priority

According to the service requirements, user priority needs to be specified. The user priority includes the following:

  • cat1: government1 (category 1 government users)
  • cat2: government2 (category 2 government users)
  • cat3: common (common users)

User type

According to the service requirements, user type needs to be specified. The user type includes the following:

  • DEL: direct exchange lines (default)
  • ECPBX: earth calling PBX
  • LCPBX: loop calling PBX
  • PayPhone: pay phone

System parameters

The system parameters including the overseas version flag and message waiting indication (MWI) mode need to be configured according to the local standards to ensure that the response of the user terminal complies with the local standards.

Overseas parameters

The attributes such as the upper and lower thresholds of the flash-hooking duration need to be configured according to the local standards to ensure that the response of the user terminal complies with the local standards.

PSTN port attributes

If the PSTN port needs to support the polarity reversal accounting, the PSTN port needs to be configured to support the polarity reversal pulse. Other attributes do not need to be modified if there is no special requirement.

Ringing current attributes

You can adjust the ringing volume by modifying the attributes of the ringing current. In general, the attributes of the ringing current do not need to be modified. You need to modify the attributes of the ringing current according to the local standards only when the default ringing current attributes do not meet the local standards.

Procedure

Translation
Download
Updated: 2019-02-22

Document ID: EDOC1100067358

Views: 13142

Downloads: 129

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