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 an MG Interface

Configuring an MG Interface

This topic describes how to configure an MG interface for implementing the communication between the MA5600T/MA5603T/MA5608T (AG) and the MGC.

Context

  • The MA5600T/MA5603T/MA5608T communicates with the MGC through either the H.248 or the MGCP protocol. One MA5600T/MA5603T/MA5608T can run only one protocol.
  • One MA5600T/MA5603T/MA5608T supports up to eight MG interfaces. If a CKMC daughter board is configured in the MA5600T/MA5603T/MA5608T, up to 32 MG interfaces can be supported. Each MG interface can be configured with the interface attributes independently. Each MG interface can be configured with the attributes (such as authentication and ringing mapping) independently.

Procedure

Configuring the Upstream VLAN Interface

This topic describes how to specify the upstream VLAN interface for the media stream and the signaling flow, and how to configure the IP addresses of the Layer 3 interface. These IP addresses are the sources of the media and signaling IP address pools.

Context

Multiple IP addresses can be configured for the same VLAN Layer 3 interface. Only one IP address functions as the primary address, and other IP addresses function as the secondary addresses.

Procedure

  1. Run the vlan command to add an upstream VLAN for the media stream and the signaling flow.
  2. Run the port vlan command to add the upstream ports to the VLAN.
  3. Configure the IP addresses of the VLAN Layer 3 interface.
    1. Run the interface vlanif command to enter the Layer 3 interface of the upstream VLAN for the media stream and the signaling flow.
    2. Run the ip address command to configure the IP addresses of the Layer 3 interface.
  4. Run the display interface vlanif command to check whether the IP addresses of the Layer 3 interface are the same as those in the data plan.
Example

Assume that the media stream and the signaling stream are transmitted upstream through upstream port 0/19/0. To create media and signaling upstream VLAN 3 and configure IP addresses 10.13.4.116/16 and 10.13.4.117/16 of the Layer 3 interfaces for the media IP address pool and the signaling IP address pool respectively, do as follows:

huawei(config)#vlan 3 standard
huawei(config)#port vlan 3 0/19 0
huawei(config)#interface vlanif 3
huawei(config-if-vlanif3)#ip address 10.13.4.116 16
huawei(config-if-vlanif3)#ip address 10.13.4.117 16 sub
huawei(config-if-vlanif3)#quit
huawei(config)#display interface vlanif 3
vlanif3 current state : UP
Line protocol current state : UP
Description : HUAWEI, SmartAX Series, vlanif3 Interface
The Maximum Transmit Unit is 1500 bytes
Forward plane MTU: -
Internet Address is 10.13.4.116/16
Internet Address is 10.13.4.117/16 Secondary
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc32-1118
VLAN Encap-mode : single-tag

Configuring the Media and Signaling IP Address Pools

The media IP address pool defines all media IP addresses that can be used by the AG, and the signaling IP address pool defines all signaling IP addresses that can be used by the AG.

Prerequisites

The IP address of the Layer 3 interface of the media and signaling upstream VLAN must be configured. For details about how to configure the IP address, see Configuring the Upstream VLAN Interface.

Context
  • The media IP address and the signaling IP address for the MG interface must be selected from the IP address pools configured here.
  • The signaling IP address pool is used to store the IP addresses of the MG interfaces, and the media IP address pool is used to store the IP addresses of the media streams controlled by the signaling.
  • The media IP address pool and the signaling IP address pool can be the same. Similarly, the media IP address and the signaling IP address can be the same.

    The MGCP interface on the MA5600T/MA5603T/MA5608T 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.

Procedure

  1. Run the voip command to enter the VoIP mode.
  2. Configure the media IP address pool.
    1. Run the ip address media command to add the media IP address to the media IP address pool.

      The media IP address needs to be selected from the IP addresses of the Layer 3 interface of the media and signaling upstream VLAN.

    2. Run the display ip address media command to check whether the media IP address pool is the same as that in the data plan.
  3. Configure the signaling IP address pool.
    1. Run the ip address signaling command to add the signaling IP address to the signaling IP address pool.

      The signaling IP address needs to be selected from the IP addresses of the Layer 3 interface of the media and signaling upstream VLAN.

    2. Run the display ip address signaling command to check whether the signaling IP address pool is the same as that in the data plan.
Example

To add IP addresses 10.13.4.116/16 and 10.13.4.117/16 of Layer 3 interfaces of the media and signaling upstream VLAN to the media IP address pool and the signaling IP address pool respectively, do as follows:

huawei(config)#voip
huawei(config-voip)#ip address media 10.13.4.116 10.13.0.1
huawei(config-voip)#ip address media 10.13.4.117 10.13.0.1
huawei(config-voip)#ip address signaling 10.13.4.116
huawei(config-voip)#ip address signaling 10.13.4.117
huawei(config-voip)#display ip address media               
  Media:               
  IP Address...........: 10.13.4.116       
  Subnet Mask..........: 255.255.0.0         
  Gateway..............: 10.13.0.1     
  MAC Address..........: 00-E0-FC-AF-91-33      
 
  IP Address...........: 10.13.4.117   
  Subnet Mask..........: 255.255.0.0        
  Gateway..............: 10.13.0.1           
  MAC Address..........: 00-E0-FC-AF-91-33       
huawei(config-voip)#display ip address signaling                
  Signaling:                                                                    
  IP Address...........: 10.13.4.116                                            
  Subnet Mask..........: 255.255.0.0                                            
  MAC Address..........: 00-E0-FC-AF-91-33                                      
                                                                                
  IP Address...........: 10.13.4.117                                            
  Subnet Mask..........: 255.255.0.0                                            
  MAC Address..........: 00-E0-FC-AF-91-33

Adding an MG Interface

This topic describes how to add an MG interface, through which the Access node can communicate with the MGC.

Context
  • One Access node supports a maximum of 8 MG interfaces. If a CKMC daughter board is configured in the Access node, up to 32 MG interfaces can be supported. Each MG interface can be configured with the interface attributes independently.
  • The configuration of the attributes of an MG interface is valid only to the MG interface.

Procedure

  • Add an MG interface that supports H.248.
    1. Run the display protocol support command to query the current system protocol.

      • If the current system protocol is H.248, go to 8.
      • If the current system protocol is MGCP, go to 2.

    2. Run the display if-mgcp all command to query whether an MG interface that supports MGCP exists.

      • If such an MG interface does not exist, go to 5.
      • If such an MG interface exists, go to 3.

    3. Delete all configuration data of this MG interface, and then run the shutdown(mgcp) command to disable the MG interface.

      This operation directly interrupts all the services on the MG interface. Hence, exercise caution when performing this operation.

    4. Run the undo interface mgcp command to delete the MG interface.
    5. Run the protocol support command to change the system protocol to H.248.
    6. Run the save command to save the configuration data, and then run the reboot system command to restart the system to make the new configuration data take effect.
    7. After the system is restarted, log in to the system, and enter the global config mode.
    8. Run the interface h248 command to add an MG interface that supports H.248.
    9. Run the if-h248 attribute command to configure the attributes of the MG interface according to the data plan.
    10. Run the display if-h248 attribute command to check whether the attributes of the MG interface are the same as those in the data plan.
  • Add an MG interface that supports MGCP.
    1. Run the display protocol support command to query the current system protocol.

      • If the current system protocol is MGCP, go to 8.
      • If the current system protocol is H.248, go to 2.

    2. Run the display if-h248 all command to query whether an MG interface that supports H.248 exists.

      • If such an MG interface does not exist, go to 5.
      • If such an MG interface exists, go to 3.

    3. Delete all configuration data of this MG interface, and then run the shutdown(h248) command to disable the MG interface.

      This operation directly interrupts all the services on the MG interface. Hence, exercise caution when performing this operation.

    4. Run the undo interface h248 command to delete the MG interface.
    5. Run the protocol support command to change the system protocol to MGCP.
    6. Run the save command to save the configuration data, and then run the reboot system command to restart the system to make the new configuration data take effect.
    7. After the system is restarted, log in to the system, and enter the global config mode.
    8. Run the interface mgcp command to add an MG interface that supports MGCP.
    9. Run the if-mgcp attribute command to configure the attributes of the MG interface according to the data plan.
    10. Run the display if-mgcp attribute command to check whether the attributes of the MG interface are the same as those in the data plan.
Example

Assume that the MG interface ID is 0 and the H.248 protocol is used for interconnecting with the MGC. To add the MG interface, do as follows:

huawei(config)#display protocol support
System support H248 protocol     
huawei(config)#interface h248 0
  Are you sure to add MG interface?(y/n)[n]:y

Assume that the MG interface ID is 0 and the MGCP protocol is used for interconnecting with the MGC. The current system protocol, however, is the H.248 protocol. It is confirmed that the H.248 interface exists in the system but is not in use. To add MG interface 0, do as follows:

huawei(config)#display protocol support
System support H248 protocol     
huawei(config)#display if-h248 all
  ----------------------------------------------------------------------------
  MGID     Trans     State     MGPort MGIP            MGCPort MGCIP/DomainName
  ----------------------------------------------------------------------------
  0        -         Closed     -      -               -       -
  ----------------------------------------------------------------------------
huawei(config)#undo interface h248 0
  Are you sure to del MG interface?(y/n)[n]:y
huawei(config)#protocol support mgcp 
huawei(config)#save             
huawei(config)#reboot system
  Please check whether data has saved, the unsaved data will lose if reboot
system, are you sure to reboot system? (y/n)[n]:y

After the system is restarted, re-log in to the system.

huawei(config)#display protocol support
System support MGCP protocol     
huawei(config)#interface mgcp 0
  Are you sure to add MG interface?(y/n)[n]:y

(Optional) Configuring the Software Parameters of an MG Interface

The software parameters of an MG interface mainly define certain common service attributes of the MG interface. After the configuration of the software parameters of an MG interface, the software parameters take effect immediately and the configuration is valid only to the MG interface.

Context

There are 34 software parameters (numbered from 0 to 33) of an MG interface that supports H.248. Table 1-41 lists the configurable parameters, and the other parameters are reserved in the system.

Table 1-41 Software parameters of an MG interface that supports H.248

Parameter

Description

Default Setting

2

Indicates whether the MG interface supports dual homing.

To configure an MG interface to or not to support dual homing, use this parameter.

If the MG interface does not support dual homing (value: 0), even if the secondary MGC is configured, the MG interface does not switch to register with the secondary MGC when the MG interface fails to register with the primary MGC. If the MG interface supports dual homing and auto-switching (value: 2), even if the MG interface has registered with the secondary MGC, the MG interface can automatically switch back to the primary MGC when the primary MGC recovers.

0: indicates that dual homing is not supported.

4

Indicates whether a wildcard is used for the registration of the MG interface.

To configure whether a wildcard is used for the registration of an MG interface, use this parameter.

Using a wildcard for registration can reduce the quantity of messages between the MG interface and the MGC. When the wildcard is not used for registration, all the terminals on the MG interface need to register with the MGC in order.

The registration without a wildcard is also called "single-endpoint registration".

0: indicates that a wildcard is used.

6

Indicates whether the MG interface supports device authentication.

To configure an MG interface to or not to support authentication, use this parameter.

After the device authentication is supported, run the auth(h248) command to configure the authentication parameters, and then run the reset(h248) command to reset the MG interface. In this way, the MGC can manage the security of the MGs and avoid illegal registration with the MGC.

1: indicates that device authentication is not supported.

7

Indicates whether the MG interface supports security header.

To configure an MG interface to or not to support security header, use this parameter.

1: indicates that security header is not supported.

11

Indicates whether the MG interface supports emergency standalone.

To configure whether an MG interface supports emergency standalone, use this parameter.

If the MG interface supports emergency standalone, the users on the MG interface can make phone calls even if the MG fails to communicate with the MGC.

0: indicates that no call is permitted.

13

Digitmap matching mode

2: indicates the minimum matching.

15

Indicates whether the function of filtering media streams by source port is enabled on an MG interface.

To enable or disable the function of filtering media streams by source port on an MG interface, use this parameter.

When the function of filtering media streams by source port is enabled on the MG interface, only the media streams from the specific ports can be received.

0: indicates that media streams are not filtered by source port.

16

Indicates the length of the timer for filtering the media stream source port of the MG interface.

To configure the length of the timer for filtering the media stream source port of an MG interface, use this parameter.

When an MG interface does not filter the source port, the MG interface automatically filters the source port if the filtering timer times out.

5s

22

Indicates the type of the prompt tone that is played after the communication between the MG and the MGC is interrupted.

To configure the type of the prompt tone after the communication between the MG and the MGC is interrupted, use this parameter.

0: indicates the busy tone.

23

Indicates the length of the timer for synchronizing the port status.

To configure the length of the timer for synchronizing the port status, use this parameter.

35s

24

Indicates the maximum value of the Real-Time Transport Protocol (RTP) termination ID.

-

25

Indicates the maximum random value for the protection against avalanche of the H.248 interface.

-

26

Indicates the type of local blocking play tone.

0: indicates the busy tone.

27

Indicates the type of remote blocking play tone.

0: indicates the busy tone.

28

Indicates the duration of the howler tone.

60s

29

Indicates the duration of message waiting tone.

3s

30

Indicates the time limit of the alarm for extra long call.

60 minutes

31

Indicates whether to report the alarm for extra long call.

1: indicates that the alarm is not reported.

32

Min. auto registration interval of remotely-blocked port(s).

1800s

33

Whether MG heartbeat is shut down.

1: No, heartbeat is enabled

There are 17 software parameters (numbered from 0 to 16) of an MG interface that supports MGCP. Table 1-42 lists the configurable parameters, and the other parameters are reserved in the system.

Table 1-42 Software parameters of an MG interface that supports MGCP

Parameter

Description

Default Setting

1

Indicates whether the ongoing call is maintained if the communication between the MG interface and the MGC is abnormal.

To maintain the ongoing call when the communication between the MG interface and the MGC is abnormal, use this parameter.

1: disconnects all the calls at once.

2

Indicates whether the MG interface supports dual homing.

To configure whether an MG interface supports dual homing, use this parameter.

If the MG interface does not support dual homing (value: 1), even if the secondary MGC is configured, the MG interface does not switch to register with the secondary MGC when the MG interface fails to register with the primary MGC.

0: indicates that dual homing is supported.

3

Indicates whether the heartbeat message between the MG and the MGC is disabled.

To configure whether the heartbeat message between the MG and the MGC is disabled, use this parameter.

1: indicates that the heartbeat message is not disabled.

4

Indicates whether a wildcard is used for the registration of the MG interface.

To configure whether a wildcard is used for the registration of an MG interface, use this parameter.

Using a wildcard for registration can reduce the quantity of messages between the MG interface and the MGC. When the wildcard is not used for registration, all the terminals on the MG interface need to register with the MGC in order.

The registration without a wildcard is also called "single-endpoint registration".

0: indicates that a wildcard is used.

5

Indicates the MGC type.

To select the MGC of a different type, use this parameter.

0

6

Indicates the maximum time threshold for responding to the heartbeat messages.

To configure the maximum times for transmitting the heartbeat message continuously, use this parameter.

3

7

Indicates whether to report the heartbeat with the MG as an endpoint.

To configure whether to report the heartbeat with the MG as an endpoint, use this parameter.

0: indicates that reporting the heartbeat with the MG as an endpoint is not supported.

10

Indicates the point-to-point (P2P) fault reporting.

To configure whether the MG interface supports the P2P fault reporting from the ISDN terminals, use this parameter.

0: indicates that the P2P fault is reported.

11

Indicates the point-to-multipoint (P2MP) fault reporting.

To configure whether the MG interface supports the P2MP fault reporting from the ISDN terminals, use this parameter.

1: indicates that the P2MP fault is not reported.

12

Indicates the type of local blocking play tone.

0: indicates the busy tone.

13

Indicates the type of remote blocking play tone.

0: indicates the busy tone.

14

Indicates the RTP filtering switch of the MGCP interface. To configure whether the RTP filtering function is enabled, use this parameter.

When the RTP filtering function is enabled, only the media stream from the specific ports can be received.

1: indicates that the RTP filtering function is not enabled.

15

Indicates the duration of the howler tone.

60s

16

Whether the timer symbol "T" follows the number string reported by the signaling.

0: Yes

Procedure

  • When the system protocol is H.248, perform the following operations to configure the software parameters of an MG interface.
    1. In the global config mode, run the interface h248 command to enter the MG interface mode.
    2. Run the mg-software parameter command to configure the software parameters listed in the data plan.
    3. Run the display mg-software parameter command to check whether the software parameters of the MG interface are the same as those in the data plan.
  • When the system protocol is MGCP, perform the following operations to configure the software parameters of an MG interface.
    1. In the global config mode, run the interface mgcp command to enter the MG interface mode.
    2. Run the mg-software parameter command to configure the software parameters listed in the data plan.
    3. Run the display mg-software parameter command to check whether the software parameters of the MG interface are the same as those in the data plan.
Example

To configure software parameter 11 of H.248-based MG interface 0 to 1 so that the MG interface supports emergency standalone and allows only internal calls, do as follows:

huawei(config)#interface h248 0
huawei(config-if-h248-0)#mg-software parameter 11 1
huawei(config-if-h248-0)#display mg-software parameter 11                      
  -------------------------------------------------                             
  Interface Id:0           para index:11  value:1                               
  -------------------------------------------------                             
 APPENDIX:                                                                      
  -------------------------------------------------                             
   Interface software parameter name:                                           
   11: Stand alone flag                                                      
       0: None                                                                  
       1: Inner                                                                 
       2: Emergency                                                             
       3: Both                                                                  

(Optional) Configuring the TID Format of an MG Interface

The TID format determines how various user terminal IDs on the MG interface are generated.

Prerequisites

The configuration of the TID format is relatively complicated. The information such as the syntax rules with which the terminal prefix must comply and the requirements for the character string of the TID template is defined in the protocol, and is not described here. This topic describes only some basic information. It is recommended that you refer to the TID description in ITU-T H248.1 (applicable to H.248) or RFC 3435 (applicable to MGCP) before configuring the TID format.

Context

The TID format consists of the terminal prefix and the TID template. The TID template defines the generation mode of the TID excluding the terminal prefix. A TID consists of a terminal prefix and a character string generated by a TID template.

The TID templates that are bound to various types of users on the MG interface determine whether the users support terminal layering.
  • If the parameter list of the TID template includes only keyword "G", the TID template is used by the non-layering users. Users bound with this template do not support terminal layering.
  • If the parameter list of the TID template includes only keywords "F", "S", "P", "B" ("B" is not available to PSTN users), the TID template is used by the layering users. Users bound with this template support terminal layering.
NOTE:
The meaning of each keyword is as follows:
  • F indicates the subrack ID.
  • S indicates the slot ID.
  • P indicates the port ID.
  • B indicates the B channel ID (only for ISDN terminals).
  • G indicates the general permanent termination index.
  • R indicates the RTP ephemeral termination index (only for the RTP ephemeral termination, which exists only when the system protocol is H.248. This termination is not involved unless special remarks are provided.)

When adding a user that supports terminal layering, you cannot and do not have to specify the parameter terminalid because the system automatically allocates a terminal ID. When adding a user that does not support terminal layering, you must specify the parameter terminalid.

You can run the display tid-format(h248) command or display tid-format(mgcp) command to query the TID formats of various types of users on the current MG interface. In the query result, template-index indicates the index of the TID template that is bound to the type of users. Then, run the display tid-template command to check whether the TID template supports the layering configuration. Hence, you can check whether the user supports terminal layering.

Precaution
  • There are 19 default TID templates (templates 0-18) in the system. The default TID templates can be referenced, but cannot be added, modified, or deleted.
  • The configuration of terminal layering on the MG must be the same as that on the MGC.
  • If certain type of terminals exists on an interface and the interface is not disabled, the terminal prefix of this type of terminals cannot be modified.
  • If a certain type of terminals exists on an interface, the TID format (including the terminal prefix and the index of the TID template) of this type of terminals cannot be changed.
  • The terminal prefix must comply with the following syntax rules: The prefix must not exceed 64 characters. Only letters, digits, "_", and "/" are the characters allowed for input. The first character must be a letter, and the last character must not be a digit.
  • The length of the TID, which is generated by combining the TID template and the terminal prefix that you configured, must not exceed 64 characters.

Procedure

  • If the system protocol is H.248, to configure the TID format on the current MG interface, do as follows:
    1. Run the display tid-template command to query the information about the default TID template of the system.
    2. If the default TID template cannot meet the service requirements, run the tid-template add command to add a TID template that meets the service requirements. If the default TID template meets the service requirements, proceed to 3.
    3. Run the interface h248 command to enter the H.248 mode.
    4. Configure the TID templates and the terminal prefix of various types of users on the current MG (VAG).

      The terminal prefix of PSTN, BRA and PRA must be all identical or unique.

      • In the H.248 mode, run the tid-format rtp command to configure the TID template and the terminal prefix of the RTP ephemeral termination.
      • In the H.248 mode, run the tid-format pstn command to configure the TID template and the terminal prefix of the PSTN user.
      • In the H.248 mode, run the tid-format bra command to configure the TID template and the terminal prefix of the ISDN BRA user.
      • In the H.248 mode, run the tid-format pra command to configure the TID template and the terminal prefix of the ISDN PRA user.

    5. Run the display tid-format(h248) command to check whether the TID templates and the terminal prefixes of various types of users on the current MG interface are the same as those in the data plan.
  • If the system protocol is MGCP, to configure the TID format on the current MG interface, do as follows:
    1. Run the display tid-template command to query the information about the default TID template of the system.
    2. If the default TID template cannot meet the service requirements, run the tid-template add command to add a TID template that meets the service requirements. If the default TID template meets the service requirements, proceed to 3.
    3. Run the interface mgcp command to enter the MGCP mode.
    4. Configure the TID templates and the terminal prefix of various types of users on the current MG (VAG).

      • In the MGCP mode, run the tid-format pstn command to configure the TID template and the terminal prefix of the PSTN user.
      • In the MGCP mode, run the tid-format bra command to configure the TID template and the terminal prefix of the ISDN BRA user.
      • In the MGCP mode, run the tid-format pra command to configure the TID template and the terminal prefix of the ISDN PRA user.

    5. Run the display tid-format(mgcp) command to check whether the TID templates and the terminal prefixes of various types of users on the current MG interface are the same as those in the data plan.
Example

Assume that in the H.248 mode, the terminal prefix of the PSTN user on MG interface 1 is aln/, and the layering TID template 3 is used. To add a PSTN user on port 0/2/0 and check whether the system automatically allocates a TID generated according to the template, do as follows:

huawei(config)#display tid-template 3//Query the information about TID template 3
  -------------------------------------------------                             
  Index      : 3                                                                
  Format     : %u/%u/%u                                                         
  Para-list  : F+1,S+1,P+1  //The parameter list of the TID template includes keyword "F", "S", 
                   //and "P", which indicates that this template supports terminal layering. 
  Name       : Aln_Not_Fixed_1                                                  
  -------------------------------------------------                             
huawei(config)#interface h248 1
huawei(config-if-h248-1)#tid-format pstn prefix aln template 3
huawei(config-if-h248-1)#quit
huawei(config)#esl user
huawei(config-esl-user)#mgpstnuser add 0/2/0 1
huawei(config-esl-user)#display mgpstnuser 0/2/0
{ <cr>|endframeid/slotid/portid<S><1,15> }:                                     
                                                                                
  Command:                                                                      
          display mgpstnuser 0/15/0                                             
  ------------------------------------------------------------------------      
  F  /S /P    MGID     TelNo            Priority PotsLineType TerminalID        
  ------------------------------------------------------------------------      
  0  /2 /0    1        -                Cat3     DEL          aln/1/3/1
             //The system allocates the terminal ID according to the TID format.
  ------------------------------------------------------------------------      

Enabling an MG Interface

Enabling an MG interface is to reset an MG interface to make the MG interface register with the MGC (or to make the modified attributes of the MG interface take effect) after the configuration of the MG interface is complete, so that the MG interface can work in the normal state.

Precaution

For the MG interface that has been in service, this operation interrupts the ongoing services carried on the MG interface. Hence, exercise caution when performing this operation.

Procedure

  • Enable the MG interface that adopts the H.248 protocol.
    1. Run the interface h248 command to enter the H.248 mode.
    2. Run the reset coldstart command to enable the MG interface.
    3. Run the quit command to return to the global config mode, and then run the display if-h248 all command to check whether the MG interface is in the normal state.
  • Enable the MG interface that adopts the MGCP protocol.
    1. Run the interface mgcp command to enter the MGCP mode.
    2. Run the reset command to enable the MG interface.
    3. Run the quit command to return to the global config mode, and then run the display if-mgcp all command to check whether the MG interface is in the normal state.
Example

To enable H.248-based MG interface 0, do as follows:

huawei(config)#interface h248 0
huawei(config-if-h248-0)#reset coldstart
  Are you sure to reset MG interface?(y/n)[n]:y
huawei(config-if-h248-0)#quit
huawei(config)#display if-h248 all
--------------------------------------------------------------------------------
MGID     Trans     State          MGPort MGIP           MGCPort MGCIP/DomainName
--------------------------------------------------------------------------------
0        UDP       Normal         2944   10.10.10.11     2944   10.10.20.11     
--------------------------------------------------------------------------------

To enable MGCP-based MG interface 0, do as follows:

huawei(config)#interface mgcp 0
huawei(config-if-mgcp-0)#reset
  Are you sure to reset MG interface?(y/n)[n]:y
huawei(config-if-mgcp-0)#quit
huawei(config)#display if-mgcp all
  --------------------------------------------------------------------------    
  MGID     State          MGPort MGIP            MGCPort MGCIP/DomainName       
  --------------------------------------------------------------------------    
  0        Normal         2727   10.10.10.11     2727    10.10.20.11            
  1        Wait ack       2527   10.10.10.12     2727    10.10.20.12            
  --------------------------------------------------------------------------
Translation
Download
Updated: 2019-02-22

Document ID: EDOC1100067358

Views: 13163

Downloads: 129

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