00385871 configuration guide (v100r007 02,ngn)

HUAWEI UMG8900 Universal Media Gateway

V100R007

Configuration Guide

Issue 02

Date 2008-05-07

Part Number 00385871

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2008. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

http://www.huawei.com

mailto:[email protected]

Contents

About This Document.....................................................................................................................1

1 Introduction.................................................................................................................................1-11.1 Data Configuration Methods...........................................................................................................................1-2

1.1.1 MML Using Methods.............................................................................................................................1-21.1.2 Methods of Using Device Panel.............................................................................................................1-41.1.3 Methods of Using Data Scripts..............................................................................................................1-4

1.2 Cautions for Data Configuration.....................................................................................................................1-5

2 General Description of Data Configuration.........................................................................2-12.1 General Procedures for Data Configuration....................................................................................................2-22.2 Configuration Index........................................................................................................................................2-3

2.2.1 TG Configuration Index.........................................................................................................................2-32.2.2 AG Configuration Index.........................................................................................................................2-42.2.3 VIG Configuration Index.......................................................................................................................2-52.2.4 Configuration Index of NGN-Enabled Switch.......................................................................................2-6

3 Preliminary Knowledge............................................................................................................3-13.1 Frames and Boards..........................................................................................................................................3-2

3.1.1 Introduction to the SSM-256 Frame.......................................................................................................3-23.1.2 Introduction to the SSM-32 Frame.........................................................................................................3-33.1.3 Numbering Cabinets and Frames...........................................................................................................3-33.1.4 Introduction to Boards............................................................................................................................3-7

3.2 Frame Cascading...........................................................................................................................................3-173.2.1 SSM-256 Self-Cascading.....................................................................................................................3-173.2.2 SSM-32 Self-Cascading.......................................................................................................................3-183.2.3 SSM-256 and SSM-32 Mixed Cascading (UG01NET and BLU.A Configured)................................3-203.2.4 SSM-256 and SSM-32 Mixed Cascading (UG02NET and BLU.C Configured)................................3-26

3.3 Centralized Forwarding.................................................................................................................................3-353.4 Dual Homing.................................................................................................................................................3-403.5 SCTP Multi-Homing.....................................................................................................................................3-403.6 Virtual Media Gateway.................................................................................................................................3-413.7 Interface Protection.......................................................................................................................................3-413.8 UAM Background Information.....................................................................................................................3-44

3.8.1 UA Frame Types..................................................................................................................................3-45

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide Contents

Issue 02 (2008-05-07) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

i

3.8.2 UA Frame Modes.................................................................................................................................3-473.8.3 Conversion Between the TID and the Subscriber Line Port................................................................3-483.8.4 Method to Number E1 Interfaces on the PV8/RSU by Mapping Them to E1 Cables on the SSM Side.......................................................................................................................................................................3-493.8.5 Method to Number E1 Interfaces on the RSP by Mapping Them to E1 Cables on the SSM Side......3-51

3.9 Route Backup................................................................................................................................................3-51

4 General Planning of Examples................................................................................................4-1

5 Configuring System Parameters..............................................................................................5-1

6 Configuring System Time........................................................................................................6-1

7 Configuring NMS Data.............................................................................................................7-17.1 Configuring the NMS Interface.......................................................................................................................7-27.2 Configuring SNMP.........................................................................................................................................7-5

8 Configuring Frames and Boards............................................................................................. 8-1

9 Configuring the Clock...............................................................................................................9-1

10 Configuring the MGW Control Interface and SIGTRAN Interface............................10-110.1 Configuring the Physical Interface in Single-Frame Networking Mode....................................................10-210.2 Configuring the Physical Interface in SSM-256 Self-Cascading Mode....................................................10-1010.3 Configuring the Physical Interface in SSM-32 Self-Cascading Mode......................................................10-1310.4 Configuring the Physical Interface in Mixed Cascading Mode................................................................10-1710.5 Configuring the E1 Physical Interface Carrying IP Signaling Packets.....................................................10-20

11 Configuring MGW Control Data........................................................................................11-111.1 Configuring MGW data..............................................................................................................................11-211.2 Configuring the Link...................................................................................................................................11-5

11.2.1 Configuring the Link over UDP.........................................................................................................11-511.2.2 Configuring the H.248 Link over SCTP............................................................................................11-811.2.3 Configuring the H.245 Link.............................................................................................................11-12

11.3 Activating the VMGW..............................................................................................................................11-15

12 Configuring TDM Bearer.....................................................................................................12-112.1 Configuring the TDM Interface..................................................................................................................12-2

12.1.1 Configuring the E1/T1 Interface........................................................................................................12-212.1.2 Configuring the E3/T3 Interface........................................................................................................12-312.1.3 Configuring the SDH Interface on the S2L/S1L................................................................................12-512.1.4 Configuring SDH Interface Protection...............................................................................................12-8

12.2 Configuring the TDM Timeslot................................................................................................................12-1112.3 Configuring Trunk Group Management...................................................................................................12-1312.4 Configuring Office Direction Information................................................................................................12-15

13 Configuring IP Bearer...........................................................................................................13-113.1 Configuring IP Interface..............................................................................................................................13-2

13.1.1 Configuring the FE Interface..............................................................................................................13-2

ContentsHUAWEI UMG8900 Universal Media Gateway

Configuration Guide

ii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)

13.1.2 Configuring the GE Interface.............................................................................................................13-413.1.3 Configuring the ATM Interface.........................................................................................................13-613.1.4 Configuring the IP over E1 Interface.................................................................................................13-9

13.2 Configuring the IP Interface Address........................................................................................................13-1313.3 Configuring IP Interface Protection..........................................................................................................13-1413.4 Configuring the Gateway Address............................................................................................................13-18

14 Configuring Signaling Transfer..........................................................................................14-114.1 Configuring SIGTRAN over L2UA............................................................................................................14-2

14.1.1 Configuring SIGTRAN over MTP2-M2UA......................................................................................14-214.1.2 Configuring SIGTRAN over LAPV5-V5UA....................................................................................14-814.1.3 Configuring SIGTRAN over Q.921-IUA.........................................................................................14-15

14.2 Configuring SIGTRAN over M3UA (MTP3-M3UA)..............................................................................14-2114.3 Configuring Semi-Permanent Connection................................................................................................14-2914.4 Configuring CAS.......................................................................................................................................14-32

15 Configuring UAM Data........................................................................................................15-115.1 Configuring UA Frames and Boards...........................................................................................................15-415.2 Configuring the Connection to the UA Frame............................................................................................15-7

15.2.1 Configuring the Connection Between the SSM Frame and the Main Frame as Well as the Direct Frame.......................................................................................................................................................................15-915.2.2 Configuring the Connection Between the RSP Main Frame and the RSP Subframe......................15-2015.2.3 Configuring the Connection Between the RSA Main Frame and the RSA Subframe.....................15-2315.2.4 Configuring the Connection Between the High-Density Main Frame and the High-Density Subframe.....................................................................................................................................................................15-25

15.3 Configuring Synchronous Tones...............................................................................................................15-2715.4 Configuring UAM Environment Monitoring Data...................................................................................15-2815.5 Configuring the DDI/AT0 Trunk Access Service.....................................................................................15-3015.6 Configuring the Hotline Service...............................................................................................................15-3215.7 Configuring the DDN Dedicated Line Service of the DSL.......................................................................15-3315.8 Configuring the DDN Dedicated Line Service of the HSL.......................................................................15-3615.9 Configuring the DDN Dedicated Line Service of the SDL.......................................................................15-4015.10 Configuring the Audio Dedicated Line Service......................................................................................15-44

16 Configuring StandAlone......................................................................................................16-1

17 Configuring Service Resource Parameters........................................................................17-117.1 Configuring Media Resource Parameters...................................................................................................17-217.2 Configuring Service Parameters..................................................................................................................17-617.3 Configuring QoS Parameters......................................................................................................................17-9

18 Configuring IP Network Security Data.............................................................................18-118.1 Configuration the Firewall..........................................................................................................................18-218.2 Configuring IPSec.......................................................................................................................................18-418.3 Configuring SSH.........................................................................................................................................18-8

A Data Planning...........................................................................................................................A-1

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide Contents


iii

B Glossary......................................................................................................................................B-1

Index.................................................................................................................................................i-1

ContentsHUAWEI UMG8900 Universal Media Gateway

Configuration Guide

iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)

Figures

Figure 1-1 MML command line...........................................................................................................................1-3Figure 2-1 Steps for data configuration of the UMG8900...................................................................................2-2Figure 3-1 Board position of the SSM-256 frame................................................................................................3-2Figure 3-2 Board position of the SSM-32 frame..................................................................................................3-3Figure 3-3 Numbering order of cabinets and frames in the SSM-256 self-cascading mode...............................3-4Figure 3-4 Numbering order of cabinets and frames in the SSM-32 self-cascading mode.................................3-5Figure 3-5 Numbering order of frames after configuration expansion of SSM-32 self-cascading......................3-5Figure 3-6 Numbering order of cabinets and frame in the SSM-256 and SSM-32 mixed cascading mode........3-6Figure 3-7 SSM-256 nine-frame cascading .......................................................................................................3-18Figure 3-8 Three-frame self-cascading of SSM-32 frames................................................................................3-19Figure 3-9 Three-frame self-cascading of SSM-32 frames................................................................................3-20Figure 3-10 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the TNB..................3-22Figure 3-11 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the TNB...................3-23Figure 3-12 Mixed cascading of one SSM-256 frame and one SSM-32 frame through the TNB.....................3-24Figure 3-13 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the BLU..................3-25Figure 3-14 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the TNB (without GEcascading)............................................................................................................................................................3-27Figure 3-15 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the TNB (without GEcascading)............................................................................................................................................................3-28Figure 3-16 Mixed cascading of one SSM-256 frame and one SSM-32 through the TNB (without GE cascading).............................................................................................................................................................................3-29Figure 3-17 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the TNB (with GEcascading)............................................................................................................................................................3-30Figure 3-18 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the BLU (without GEcascading) ...........................................................................................................................................................3-32Figure 3-19 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the BLU (with GEcascading)............................................................................................................................................................3-34Figure 3-20 Dual homing...................................................................................................................................3-40Figure 3-21 SCTP multi-homing........................................................................................................................3-41Figure 3-22 1+1 backup.....................................................................................................................................3-43Figure 3-23 1:N linear multiplex section protection..........................................................................................3-44Figure 3-24 UMG8900 connecting subscribers directly ...................................................................................3-45Figure 3-25 Route backup of IP addresses in different network segments........................................................3-51Figure 3-26 Route backup of IP addresses in the same network segment.........................................................3-52Figure 4-1 Networking example...........................................................................................................................4-1

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide Figures


v

Figure 6-1 Steps for configuring the host time.....................................................................................................6-2Figure 7-1 Index Mapping of Configuration Command Parameters....................................................................7-3Figure 7-2 Networking diagram...........................................................................................................................7-5Figure 7-3 Structure of MIB tree..........................................................................................................................7-6Figure 7-4 Access control based on view.............................................................................................................7-7Figure 7-5 Access control of SNMP v1/v2c........................................................................................................ 7-7Figure 7-6 Steps for the SNMP configuration......................................................................................................7-8Figure 7-7 Simplified steps for the SNMPv1/v2c configuration......................................................................... 7-9Figure 7-8 Index mapping of configuration command parameters....................................................................7-10Figure 8-1 Board layout of the UMG8900...........................................................................................................8-7Figure 9-1 Position that SSM is transmitted in E1 signals...................................................................................9-2Figure 9-2 Procedures for choosing clock reference source................................................................................ 9-4Figure 9-3 Steps for clock configuration..............................................................................................................9-6Figure 10-1 Networking diagram of a single SSM-256 frame...........................................................................10-8Figure 10-2 Networking diagram of a single SSM-32 frame.............................................................................10-9Figure 10-3 Networking diagram of the SSM-256 self-cascading...................................................................10-12Figure 10-4 Networking diagram of the SSM-32 self-cascading.....................................................................10-16Figure 10-5 Networking diagram of the SSM-256 and SSM-32 mixed cascading..........................................10-19Figure 10-6 Networking diagram of using the E1 physical interface to carry IP packets................................10-23Figure 11-1 Index mapping of the configuration command parameters of the MGW Data..............................11-2Figure 11-2 Networking diagram.......................................................................................................................11-4Figure 11-3 Networking diagram.......................................................................................................................11-8Figure 11-4 Networking diagram.....................................................................................................................11-12Figure 11-5 Networking Examples..................................................................................................................11-15Figure 12-1 Index mapping of the configuration command parameters of the MGW data...............................12-8Figure 13-1 Ethernet interface protocol stack....................................................................................................13-2Figure 13-2 Protocol stack of the Ethernet interface..........................................................................................13-5Figure 13-3 Protocol stack of the ATM interface..............................................................................................13-7Figure 13-4 Protocol stack supported by the IPoE1 interface............................................................................13-9Figure 13-5 Networking diagram of IP over E1...............................................................................................13-11Figure 13-6 Access of the UMG8900 to a core network..................................................................................13-15Figure 13-7 Configuration procedure for IP interface protection....................................................................13-15Figure 14-1 Signaling adaptation and transfer in MTP2-M2UA mode.............................................................14-3Figure 14-2 Index mapping of the configuration command parameters over M2UA........................................14-3Figure 14-3 Networking diagram.......................................................................................................................14-8Figure 14-4 Signaling adaptation and transfer in LAPV5-V5UA mode ...........................................................14-9Figure 14-5 Index and interconnection mapping of the configuration command parameters of the SG over V5UA...........................................................................................................................................................................14-10Figure 14-6 Networking diagram.....................................................................................................................14-14Figure 14-7 Signaling adaptation and transfer in Q.921-IUA mode................................................................14-15Figure 14-8 Index and interconnection mapping of the configuration command parameters of the SG over IUA...........................................................................................................................................................................14-16Figure 14-9 Networking diagram.....................................................................................................................14-20

FiguresHUAWEI UMG8900 Universal Media Gateway

Configuration Guide

vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)

Figure 14-10 Signaling adaptation and transfer in MTP3-M3UA mode.........................................................14-21Figure 14-11 Index mapping of the configuration commands of the signaling transfer based on M3UA.......14-22Figure 14-12 Networking diagram of the signaling transfer over M3UA........................................................14-28Figure 14-13 Signaling transparent transmission through the semi-permanent connection............................14-29Figure 14-14 Networking diagram...................................................................................................................14-31Figure 14-15 CAS configuration procedure.....................................................................................................14-40Figure 14-16 Index and interconnection mapping of the configuration command parameters of the SG over CAS...........................................................................................................................................................................14-41Figure 14-17 Networking diagram...................................................................................................................14-43Figure 15-1 Procedure for configuring basic services of the UAM...................................................................15-2Figure 15-2 UA frames and boards....................................................................................................................15-6Figure 15-3 Physical connections between the UAFM frame and the SSM frame..........................................15-11Figure 15-4 Physical connections between the HABD/HABL frame and the SSM frame..............................15-12Figure 15-5 Physical connections between the PV8 in the UAM frame and the SSM frame..........................15-14Figure 15-6 E1 port connection in sequence....................................................................................................15-15Figure 15-7 E1 port connection in a cross order..............................................................................................15-16Figure 15-8 Connection between the SSM frame and the main frame............................................................15-17Figure 15-9 Physical connections between the RSP in the UAM frame and the SSM frame..........................15-18Figure 15-10 Physical connections between the HWCB in the HABA_UP frame and the SSM frame..........15-19Figure 15-11 Connection between the SSM frame and the direct frame.........................................................15-20Figure 15-12 Connection between the RSP_10 main frame and the RSP_14 subframe..................................15-21Figure 15-13 Connection between the RSA main frame and the RSA subframe............................................15-24Figure 15-14 Connection between the main frame and the subframe..............................................................15-26Figure 15-15 DDI/AT0 trunk access service....................................................................................................15-32Figure 15-16 DDN dedicated line service........................................................................................................15-34Figure 15-17 Networking diagram...................................................................................................................15-36Figure 15-18 HW uplink mode for the V.35 interface.....................................................................................15-37Figure 15-19 E1 bypass mode for the V.35 interface.......................................................................................15-38Figure 15-20 HW uplink mode for the V.35 interface.....................................................................................15-41Figure 15-21 E1 bypass mode for the V.35 interface.......................................................................................15-41Figure 15-22 Audio dedicated line service networking...................................................................................15-45Figure 16-1 Takeover of call control function from the MGC to StandAlone...................................................16-2Figure 18-1 Index mapping of the configuration command parameters of the firewall....................................18-2Figure 18-2 Index mapping of the configuration command parameters of IPSec.............................................18-5Figure 18-3 Steps for configuring the SSH........................................................................................................18-8

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide Figures


vii

Tables

Table 1-1 Description of shortcut icons............................................................................................................... 1-3Table 2-1 Bearer data configuration when the UMG8900 serves as a TG...........................................................2-3Table 2-2 Bearer Data Configuration When the UMG8900 Serves as an AG.....................................................2-4Table 2-3 Bearer data configuration when the UMG8900 serves as a VIG.........................................................2-5Table 2-4 Bearer data configuration when the UMG8900 serves as the NGN-enabled switch...........................2-6Table 3-1 Equipment and resource management units.........................................................................................3-7Table 3-2 Service and protocol processing units..................................................................................................3-9Table 3-3 Switching and cascading units...........................................................................................................3-10Table 3-4 Interface units.....................................................................................................................................3-12Table 3-5 Media resource processing units........................................................................................................3-15Table 3-6 Clock units.........................................................................................................................................3-17Table 3-7 IP interfaces used by the UMG8900..................................................................................................3-35Table 3-8 Usage rules of IP interfaces when the HRB is configured.................................................................3-36Table 3-9 Usage rules for IP interfaces when no HRB is configured for single SSM-32 networking...............3-37Table 3-10 Usage rules for IP interfaces when the HRB is configured for the single SSM-32 networking......3-38Table 3-11 Usage rules for IP interfaces in case of SSM-256 self cascading....................................................3-38Table 3-12 Usage rules for IP interfaces in case of SSM-32 self cascading......................................................3-39Table 3-13 Usage rules for IP interfaces in case of SSM-256 and SSM-32 mixed cascading...........................3-39Table 3-14 Interface protection types supported by different interfaces............................................................3-42Table 3-15 Mapping between UA frame types and backplanes.........................................................................3-46Table 3-16 UA frame modes..............................................................................................................................3-48Table 5-1 Data planning.......................................................................................................................................5-1Table 5-2 Output parameter..................................................................................................................................5-2Table 6-1 Data planning.......................................................................................................................................6-2Table 7-1 Parameter configuration for the three types of interfaces....................................................................7-2Table 7-2 Input parameter.................................................................................................................................... 7-3Table 7-3 Data planning.......................................................................................................................................7-3Table 7-4 Data planning.....................................................................................................................................7-10Table 8-1 Considerations in adding a board.........................................................................................................8-2Table 8-2 Data planning.......................................................................................................................................8-4Table 8-3 Output parameter..................................................................................................................................8-5Table 9-1 SSM codes............................................................................................................................................9-2Table 9-2 Clock cable connection........................................................................................................................9-5

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide Tables


ix

Table 9-3 Input parameter.................................................................................................................................... 9-6Table 9-4 Data planning.......................................................................................................................................9-7Table 10-1 Usage rules of IP interfaces when the HRB is configured...............................................................10-2Table 10-2 Usage rules for IP interfaces when no HRB is configured for the single SSM-32 networking.......10-3Table 10-3 Usage rules for IP interfaces when the HRB is configured for the single SSM-32 networking......10-3Table 10-4 Input parameter................................................................................................................................10-4Table 10-5 Data planning...................................................................................................................................10-4Table 10-6 Data output.......................................................................................................................................10-6Table 10-7 Data planning.................................................................................................................................10-10Table 10-8 Data output.....................................................................................................................................10-11Table 10-9 Data planning.................................................................................................................................10-14Table 10-10 Data output...................................................................................................................................10-14Table 10-11 Data planning...............................................................................................................................10-17Table 10-12 Data output...................................................................................................................................10-18Table 10-13 Input parameter............................................................................................................................10-21Table 10-14 Data planning...............................................................................................................................10-21Table 11-1 Data planning...................................................................................................................................11-2Table 11-2 Data output.......................................................................................................................................11-3Table 11-3 Input parameter................................................................................................................................11-6Table 11-4 Data planning...................................................................................................................................11-6Table 11-5 Input parameter................................................................................................................................11-9Table 11-6 Data planning.................................................................................................................................11-10Table 11-7 Input parameter..............................................................................................................................11-13Table 11-8 Data planning.................................................................................................................................11-13Table 11-9 Input parameter..............................................................................................................................11-15Table 12-1 Input parameter................................................................................................................................12-2Table 12-2 Data planning...................................................................................................................................12-3Table 12-3 Input parameter................................................................................................................................12-4Table 12-4 Data planning...................................................................................................................................12-4Table 12-5 Input parameter................................................................................................................................12-6Table 12-6 Data planning...................................................................................................................................12-6Table 12-7 Data output.......................................................................................................................................12-7Table 12-8 Input parameter................................................................................................................................12-9Table 12-9 Data planning...................................................................................................................................12-9Table 12-10 Data output.....................................................................................................................................12-9Table 12-11 Input parameter............................................................................................................................12-11Table 12-12 Data planning...............................................................................................................................12-12Table 12-13 Data output...................................................................................................................................12-12Table 12-14 Data planning...............................................................................................................................12-14Table 12-15 Input parameter............................................................................................................................12-15Table 12-16 Data planning...............................................................................................................................12-16Table 13-1 Input parameter................................................................................................................................13-3

TablesHUAWEI UMG8900 Universal Media Gateway

Configuration Guide

x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)

Table 13-2 Data planning...................................................................................................................................13-3Table 13-3 Input parameter................................................................................................................................13-5Table 13-4 Data planning...................................................................................................................................13-5Table 13-5 Input parameter................................................................................................................................13-7Table 13-6 Data planning...................................................................................................................................13-7Table 13-7 Input parameter..............................................................................................................................13-10Table 13-8 Data planning.................................................................................................................................13-10Table 13-9 Input parameter..............................................................................................................................13-13Table 13-10 Data planning...............................................................................................................................13-13Table 13-11 Data output...................................................................................................................................13-13Table 13-12 Input parameter............................................................................................................................13-16Table 13-13 Data planning...............................................................................................................................13-16Table 13-14 Input parameter............................................................................................................................13-19Table 13-15 Data planning...............................................................................................................................13-19Table 14-1 Input parameter................................................................................................................................14-4Table 14-2 Data planning...................................................................................................................................14-5Table 14-3 Input parameter..............................................................................................................................14-10Table 14-4 Data planning.................................................................................................................................14-11Table 14-5 Input parameter..............................................................................................................................14-16Table 14-6 Data planning.................................................................................................................................14-17Table 14-7 Input parameter..............................................................................................................................14-23Table 14-8 Data planning.................................................................................................................................14-24Table 14-9 Input parameter..............................................................................................................................14-30Table 14-10 Data planning...............................................................................................................................14-30Table 14-11 CSN1 line signaling conversion index.........................................................................................14-32Table 14-12 CSN1 line command conversion index........................................................................................14-33Table 14-13 CSN1 register signaling conversion index...................................................................................14-33Table 14-14 CSN1 register command conversion index..................................................................................14-34Table 14-15 CAS conversion index in different countries...............................................................................14-34Table 14-16 Brazil R2 metering pulse index....................................................................................................14-37Table 14-17 CAS configuration in different countries.....................................................................................14-38Table 14-18 Input parameter............................................................................................................................14-41Table 14-19 Data planning...............................................................................................................................14-42Table 15-1 Preparations......................................................................................................................................15-1Table 15-2 Input parameter................................................................................................................................15-4Table 15-3 Data planning...................................................................................................................................15-4Table 15-4 Data output.......................................................................................................................................15-5Table 15-5 Input parameter................................................................................................................................15-9Table 15-6 Data planning...................................................................................................................................15-9Table 15-7 Descriptions of the HWC interface................................................................................................15-21Table 15-8 Descriptions of the HW interface in the RSP_14 frame................................................................15-22Table 15-9 Input parameter..............................................................................................................................15-22



xi

Table 15-10 Data planning...............................................................................................................................15-22Table 15-11 Input parameter............................................................................................................................15-24Table 15-12 Data planning...............................................................................................................................15-25Table 15-13 Input parameter............................................................................................................................15-26Table 15-14 Data planning...............................................................................................................................15-26Table 15-15 Input parameter............................................................................................................................15-27Table 15-16 Data planning...............................................................................................................................15-27Table 15-17 Input parameter............................................................................................................................15-29Table 15-18 Data planning...............................................................................................................................15-29Table 15-19 Input parameter............................................................................................................................15-31Table 15-20 Data planning...............................................................................................................................15-31Table 15-21 Input parameter............................................................................................................................15-33Table 15-22 Data planning...............................................................................................................................15-33Table 15-23 Input parameter............................................................................................................................15-35Table 15-24 Data planning...............................................................................................................................15-35Table 15-25 Input parameter............................................................................................................................15-38Table 15-26 Data planning...............................................................................................................................15-38Table 15-27 Input parameter............................................................................................................................15-42Table 15-28 Data planning...............................................................................................................................15-42Table 15-29 Input parameter............................................................................................................................15-45Table 15-30 Data planning...............................................................................................................................15-45Table 16-1 Input parameter................................................................................................................................16-2Table 16-2 Data planning...................................................................................................................................16-2Table 17-1 Board configuration of the VPU......................................................................................................17-2Table 17-2 Input parameter................................................................................................................................17-4Table 17-3 Data planning...................................................................................................................................17-4Table 17-4 Input parameter................................................................................................................................17-6Table 17-5 Data planning...................................................................................................................................17-7Table 17-6 Input parameter................................................................................................................................17-9Table 17-7 Data planning...................................................................................................................................17-9Table 18-1 Input parameter................................................................................................................................18-2Table 18-2 Data planning...................................................................................................................................18-3Table 18-3 Input parameter................................................................................................................................18-5Table 18-4 Data planning...................................................................................................................................18-6Table 18-5 Data planning...................................................................................................................................18-9Table A-1 Data planning.....................................................................................................................................A-1Table A-2 Data planning.....................................................................................................................................A-2Table A-3 Data planning.....................................................................................................................................A-3Table A-4 Data planning.....................................................................................................................................A-4Table A-5 Data planning.....................................................................................................................................A-4Table A-6 Data planning.....................................................................................................................................A-5Table A-7 Data planning.....................................................................................................................................A-6


Configuration Guide

xii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)

Table A-8 Data planning.....................................................................................................................................A-7Table A-9 Data planning.....................................................................................................................................A-8Table A-10 Data planning...................................................................................................................................A-9Table A-11 Data planning.................................................................................................................................A-10Table A-12 Data planning.................................................................................................................................A-11Table A-13 Data planning.................................................................................................................................A-12Table A-14 Data planning.................................................................................................................................A-12Table A-15 Data planning.................................................................................................................................A-13Table A-16 Data planning.................................................................................................................................A-13Table A-17 Data planning.................................................................................................................................A-14Table A-18 Data planning.................................................................................................................................A-14Table A-19 Data planning.................................................................................................................................A-15Table A-20 Data planning.................................................................................................................................A-15Table A-21 Data planning.................................................................................................................................A-16Table A-22 Data planning.................................................................................................................................A-16Table A-23 Data planning.................................................................................................................................A-17Table A-24 Data planning.................................................................................................................................A-18Table A-25 Data planning.................................................................................................................................A-18Table A-26 Data planning.................................................................................................................................A-19Table A-27 Data planning.................................................................................................................................A-19Table A-28 Data planning.................................................................................................................................A-21Table A-29 Data planning.................................................................................................................................A-22Table A-30 Data planning.................................................................................................................................A-24Table A-31 Data planning.................................................................................................................................A-26Table A-32 Data planning.................................................................................................................................A-26Table A-33 Data planning.................................................................................................................................A-27Table A-34 Data planning.................................................................................................................................A-28Table A-35 Data planning.................................................................................................................................A-29Table A-36 Data planning.................................................................................................................................A-29Table A-37 Data planning.................................................................................................................................A-29Table A-38 Data planning.................................................................................................................................A-30Table A-39 Data planning.................................................................................................................................A-30Table A-40 Data planning.................................................................................................................................A-31Table A-41 Data planning.................................................................................................................................A-31Table A-42 Data planning.................................................................................................................................A-31Table A-43 Data planning.................................................................................................................................A-32Table A-44 Data planning.................................................................................................................................A-32Table A-45 Data planning.................................................................................................................................A-33Table A-46 Data planning.................................................................................................................................A-34Table A-47 Data planning.................................................................................................................................A-35Table A-48 Data planning.................................................................................................................................A-36Table A-49 Data planning.................................................................................................................................A-37



xiii

Table A-50 Data planning.................................................................................................................................A-38Table A-51 Data planning.................................................................................................................................A-38Table A-52 Data planning.................................................................................................................................A-40


Configuration Guide

xiv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)

About This Document

Purpose

The data configuration corresponding to different networking requirements are required for theUMG8900 after hardware and software installation to provide service bearer and processingfunctions. This document describes the data configuration on the UMG8900 and the contentscover related concepts, configuration procedures, and configuration notes.

Related Versions

The following table lists the product versions related to this document.

Product Name Version

HUAWEI UMG8900 V100R007

Intended Audience

The intended audiences of this document are:

l Network administrator

l System engineer

l Commissioning engineer

l Operation and maintenance engineer

Update History

Updates between document versions are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Updates in Issue 02 (2008-05-07)

Initial commercial release

Updates in Issue 01 (2007-11-28)

Initial field trial release

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide About This Document


1

OrganizationThis document describes the data configuration procedures and methods on the UMG8900 andprovides the configuration index.

1 Introduction

This describes the data configuration methods and cautions of the UMG8900.

2 General Description of Data Configuration

This describes the general procedure for configuring data, and helps you have a generalknowledge of data configuration.

3 Preliminary Knowledge

This describes the necessary knowledge of the UMG8900.

4 General Planning of Examples

This describes the general planning of examples in each part of the document.

5 Configuring System Parameters

This describes how to configure the system parameters, including the system name, version loadserver information, local information, and environmental monitoring parameters.

6 Configuring System Time

This describes how to configure the system time including how to set the time synchronizationmode and how to manually set the time, time zone, Network Time Protocol (NTP) server, anddaylight saving time (DST).

7 Configuring NMS Data

This describes how to configure the interconnection data between the UMG8900 and the networkmanagement system (NMS), including the configurations of the NMS interface and SimpleNetwork Management Protocol (SNMP).

8 Configuring Frames and Boards

This describes how to add frames and boards.

9 Configuring the Clock

This describes how to configure the clock data including the reference source, CLK, and lineclock source.

10 Configuring the MGW Control Interface and SIGTRAN Interface

This describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface.

11 Configuring MGW Control Data

This describes how to configure the media gateway (MGW) control data. The standard MGWcontrol protocol H.248 is used between the UMG8900 and the media gateway controller (MGC)to control and manage the MGC on the UMG8900 and achieve the switching and processing ofthe voice service and data service.

12 Configuring TDM Bearer

About This DocumentHUAWEI UMG8900 Universal Media Gateway

Configuration Guide

2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)

This describes how to configure the time division multiplexing (TDM) bearer data including theTDM interface, TDM timeslot, TDM trunk group management, and office direction information.In the actual networking application, the service exchange between the UMG8900 and and publicswitching telephone network (PSTN) switch is based on the TDM bearer. The connectionbetween the UMG8900 and other media gateways (MGWs) can also be based on the TDMbearer.

13 Configuring IP Bearer

This describes how to configure the Internet Protocol (IP) bearer data including the IP interface,IP interface address, IP interface protection, and gateway IP address. Configure the IP bearerdata when the UMG8900 acts as a media gateway (MGW) in the core network and theconnections with other MGWs in the core network are based on the IP bearer.

14 Configuring Signaling Transfer

This describes how to configure the signaling transfer data. The UMG8900 is embedded with asignaling gateway (SG) and supports the signaling transfer function. In some networkingapplications, to reduce connections between network elements, no physical connection existsbetween the media gateway controller (MGC) and the remote devices. The signaling databetween the two connected devices are transferred by the UMG8900. In this case, you need toset signaling transfer on the UMG8900.

15 Configuring UAM Data

This describes how to configure the user access module (UAM) data.

16 Configuring StandAlone

This describes how to configure the StandAlone data, including the StandAlone data of the ESLsubscribers and that of the V5 subscribers.

17 Configuring Service Resource Parameters

This describes how to configure the service resource parameters, including the media resourceparameters, service parameters, and quality of service (QoS) parameters.

18 Configuring IP Network Security Data

This describes how to configure the Internet Protocol (IP) network security data, including howto configure the firewall, IP Security Protocol (IPSec), and Security Shell (SSH). TheUMG8900 can enable the firewall and the IPSec function on the media gateway (MGW) controlinterface, network management interface, and signaling transport (SIGTRAN) interface toachieve security protection on these types of control packets. Based on the SSH protocol, youcan log in to and manage the UMG8900 to implement the security of the remote login.

A Data Planning

This describes the data planning of the UMG8900.

B Glossary

Conventions

1. Symbol Conventions

The following symbols may be found in this document. They are defined as follows



3

Symbol Description

DANGERIndicates a hazard with a high level of risk that, if not avoided,will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk which, ifnot avoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation that, if not avoided,could cause equipment damage, data loss, and performancedegradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or save yourtime.

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

2. General Conventions

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files,directories,folders,and users are in boldface. Forexample,log in as user root .

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

3. Command Conventions


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[ ] Items (keywords or arguments) in square brackets [ ] are optional.

{x | y | ...} Alternative items are grouped in braces and separated by verticalbars.One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets andseparated by vertical bars.One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by verticalbars.A minimum of one or a maximum of all can be selected.

About This DocumentHUAWEI UMG8900 Universal Media Gateway

Configuration Guide

4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)


[ x | y | ... ] * Alternative items are grouped in braces and separated by verticalbars.A minimum of zero or a maximum of all can be selected.

4. GUI Conventions


Boldface Buttons,menus,parameters,tabs,window,and dialog titles are inboldface. For example,click OK.

> Multi-level menus are in boldface and separated by the ">" signs.For example,choose File > Create > Folder .

5. Keyboard Operation


Key Press the key.For example,press Enter and press Tab.

Key1+Key2 Press the keys concurrently.For example,pressing Ctrl+Alt+Ameans the three keys should be pressed concurrently.

Key1,Key2 Press the keys in turn.For example,pressing Alt,A means the twokeys should be pressed in turn.

6. Mouse Operation

Action Description

Click Select and release the primary mouse button without moving thepointer.

Double-click Press the primary mouse button twice continuously and quicklywithout moving the pointer.

Drag Press and hold the primary mouse button and move the pointerto a certain position.



5

1 Introduction

About This Chapter

This describes the data configuration methods and cautions of the UMG8900.

1.1 Data Configuration MethodsThis describes the data configuration methods, including configurations through man-machinelanguage (MML) commands, device panel, and data configuration scripts.

1.2 Cautions for Data ConfigurationThis describes the cautions for data configuration of the UMG8900.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 1 Introduction


1-1

1.1 Data Configuration MethodsThis describes the data configuration methods, including configurations through man-machinelanguage (MML) commands, device panel, and data configuration scripts.

You can adopt the above methods through Huawei local maintenance terminal (LMT). Beforeconfiguration, you need to start the LMT and log in to the OMC port (the first FE port on theNET in the main control frame).

NOTE

The Internet Protocol (IP) address of the OMC network port is often defined in the MML.txt file. Whenlogging in for the first time, you need to add an office and set the office address as specified in theMML.txt file. Then you can log in to the host through the office address and set data online.

For how to add an office, see the online help (press F1).You can change the IP address of theOMC network port by running MOD OMCIP after logging in to the office. For moreinformation, see the MML online help.

1.1.1 MML Using MethodsThis describes how to use the man-machine language (MML) commands to configure data. TheMML command is the commonly-used configuration method, and it can complete all theconfigurations.

1.1.2 Methods of Using Device PanelThis describes how to use the device panel to configure data. Using the device panel can completethe configuration of hardware such as the frame and board. Its advantage is direct view, but usingthe device panel can only complete the configuration of some data.

1.1.3 Methods of Using Data ScriptsThis describes how to use the script to configure data. Huawei compiles the configuration datainto script files. Using the script files, users can complete the data configuration.

1.1.1 MML Using MethodsThis describes how to use the man-machine language (MML) commands to configure data. TheMML command is the commonly-used configuration method, and it can complete all theconfigurations.

The MML command is a common configuration method provided by telecommunication devicesuppliers at present. The local maintenance terminal (LMT) supports the MML command linemode. Refer to Figure 1-1.

1 IntroductionHUAWEI UMG8900 Universal Media Gateway

Configuration Guide

1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)

Figure 1-1 MML command line

Table 1-1 lists the four shortcut icons and their description.

Table 1-1 Description of shortcut icons

Shortcut Icons Description

Display the input box of parameters.You can also press Enter after entering a command.

Execute a command.You can also press F9.

Select the next command.You can also press F8.

Select the last command.You can also press F7.

When using MML commands for data configuration, pay attention to the following:

l The parameters in red are crucial for a command, such as Frame No., Frame Ver, FrameType, Cabinet No., and Location in Cabinet in Figure 1-1. You must type theseparameters; otherwise, execution of a command fails.

l The parameters in black are often not crucial for a command (a few are key parameters),such as Frame Name and Frame description in Figure 1-1. These parameters are optionaland do not affect the execution of a command.

l To reduce workload for data configuration, the system presets some parameters that arefixed and need no frequent change to default values. You can decide whether to changethese parameters based on actual conditions.



1-3

l If you are not aware of the default value or value range of a parameter, you can point thearrow of the mouse to the input box of the parameter and in about one second, the systemdisplays the default value or value range of the parameter in a small pane.

l For functions, notes, parameter description, and examples of MML commands, see theMML online help.

1.1.2 Methods of Using Device PanelThis describes how to use the device panel to configure data. Using the device panel can completethe configuration of hardware such as the frame and board. Its advantage is direct view, but usingthe device panel can only complete the configuration of some data.

The device panel is used for:

l Data configuration of hardware (frames and boards)

l Routine query

Its advantage is direct view. For example, you can directly see the types and states of boardsdeployed in the system.

The LMT provides the device panel. For usage of the device panel, see the man-machinelanguage (MML) online help.

1.1.3 Methods of Using Data ScriptsThis describes how to use the script to configure data. Huawei compiles the configuration datainto script files. Using the script files, users can complete the data configuration.

CAUTIONAs the data scripts are compiled under lab environment, they may not be fully suitable fordeployment. Thus, you may need to change the data based on actual needs for the deployment.

The data script file is mainly applicable for data configuration (usually batch operation) in:

l Deployment

l System expansion

l Software upgrade

l Routine maintenance

Huawei compiles a data script file under lab environment to:

l Improve efficiency of data configuration

l Reduce errors of data configuration

The data configuration script file is a *.txt file consisting of man-machine language (MML)commands and notes. In the local maintenance terminal (LMT), choose System > Execute BatchCommand, set the batch execution parameters, and select the prepared data script (the *.txt file).The system executes the scripts one by one at once or at a specified time point based on thesetting.

1 IntroductionHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

1.2 Cautions for Data ConfigurationThis describes the cautions for data configuration of the UMG8900.

Back up the current configuration script before modifying the data configuration to avoid dataloss.

After the configuration is complete, run SAVE CFG to save the data so that the configurationdata is not lost when the system is restarted. Otherwise, you need to configure the data againafter the system is restarted.



1-5

2 General Description of Data Configuration

About This Chapter

This describes the general procedure for configuring data, and helps you have a generalknowledge of data configuration.

2.1 General Procedures for Data ConfigurationThis describes the general procedure for data configuration.

2.2 Configuration IndexThis describes the configuration index and reference of the UMG8900 in different positions ofa network.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 2 General Description of Data Configuration


2-1

2.1 General Procedures for Data ConfigurationThis describes the general procedure for data configuration.

Figure 2-1 shows the steps for data configuration of the UMG8900.

Figure 2-1 Steps for data configuration of the UMG8900

Start

Configure the clock

Configure MGW control data

Configure IP bearer

Configure TDM bearer

Configure signaling transfer

Configure IP network security data

End

Configure the NMS

Configure frames and boards

Configure the system time

Configure system parameters

Configure MGW control interfaces and physicalinterfaces of SIGTRAN interfaces

Configure service source parameters

Configure the UAM

Configure StandAlone

2 General Description of Data ConfigurationHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

Since the index relationship exists between different configuration commands, dataconfiguration of the UMG8900 must follow certain order.

2.2 Configuration IndexThis describes the configuration index and reference of the UMG8900 in different positions ofa network.

2.2.1 TG Configuration IndexThis describes the configuration procedure and reference when the UMG8900 serves as a trunkgateway (TG).

2.2.2 AG Configuration IndexThis describes the configuration procedure and reference when the UMG8900 serves as an accessgateway (AG).

2.2.3 VIG Configuration IndexThis describes the configuration procedure and reference when the UMG8900 serves as a videointerworking gateway (VIG).

2.2.4 Configuration Index of NGN-Enabled SwitchThis describes the configuration procedure and reference when the UMG8900 serves as an NGN-enabled switch.

2.2.1 TG Configuration IndexThis describes the configuration procedure and reference when the UMG8900 serves as a trunkgateway (TG).

Table 2-1 lists the index table of configuring the TG service.

Table 2-1 Bearer data configuration when the UMG8900 serves as a TG

Bearer Data Interconnected Device

ConfigurationDescription

Reference

MGW control data MGC Configure the data ofphysical interfacesbetween the UMG8900and the MGC.

10 Configuring theMGW ControlInterface andSIGTRAN Interface

Configure the MGWcontrol data between theUMG8900 and theMGC.

11 Configuring MGWControl Data

TDM bearer data PSTN switch Configure the TDMbearer for bearingservice data between theUMG8900 and PSTNswitch.

12 Configuring TDMBearer



2-3



Reference

IP bearer data MGW Configure IP bearer databetween the UMG8900and other MGWs.

13 Configuring IPBearer

Signaling transferdata

MGC If signaling packetsneed to be transferred,configure signalingtransfer for theUMG8900.

14 ConfiguringSignaling Transfer

2.2.2 AG Configuration IndexThis describes the configuration procedure and reference when the UMG8900 serves as an accessgateway (AG).

Table 2-2 lists the index table of configuring the AG service.

Table 2-2 Bearer Data Configuration When the UMG8900 Serves as an AG

Bearer Data InterconnectedDevice


Reference

MGW control data MGC Data of physicalinterfaces between theUMG8900 and theMGC


Configure the MGWcontrol data betweenthe UMG8900 and theMGC.

11 ConfiguringMGW Control Data

TDM bearer data V5 access network TDM connection to theV5 access network


PBX TDM connection to thePBX

UAM data UAM When the UMG8900 isdirectly connectedwith users through thesubscribe frame,configure the UAMdata.

15 Configuring UAMData


Configuration Guide


Issue 02 (2008-05-07)

Bearer Data InterconnectedDevice


Reference

IP bearer data MGW The connectionbetween theUMG8900 and otherMGWs in the corenetwork is based on IPbearer, and thusconfigure the IP bearerdata.



MGC If signaling packets ofIUA/V5UA arerequired to betransferred, configuresignaling transfer forthe UMG8900.


StandAlone MGC ConfigureStandAlone, which canconnect calls betweenusers when thecommunicationbetween theUMG8900 and theMGW fails.

16 ConfiguringStandAlone

2.2.3 VIG Configuration IndexThis describes the configuration procedure and reference when the UMG8900 serves as a videointerworking gateway (VIG).

Table 2-3 shows the index table of configuring the VIG service.

Table 2-3 Bearer data configuration when the UMG8900 serves as a VIG



Reference

MGW controldata

MGC Configure the data ofphysical interfacesbetween the UMG8900and the MGC.






2-5



Reference

TDM bearer data GMSC Configure the TDMbearer for bearingservice data between theUMG8900 and GMSC.


IP bearer data H.323/SIPterminal

When the UMG8900serves as a VIG, it isconnected with the H.323 and SIP terminalsbased on IP bearer.



MGC If signaling packets arerequired to betransferred, configuresignaling transfer for theUMG8900.


2.2.4 Configuration Index of NGN-Enabled SwitchThis describes the configuration procedure and reference when the UMG8900 serves as an NGN-enabled switch.

Table 2-4 shows the index table of configuring the NGN-enabled switch service.

Table 2-4 Bearer data configuration when the UMG8900 serves as the NGN-enabled switch



Reference

MGW control data MGC Configure the data ofphysical interfacesbetween the UMG8900and the MGC.




TDM bearer data PSTN switch Configure the TDMconnection to the PSTNlocal office.


Configure the TDMconnection to the PSTNtrunk office.


Configuration Guide


Issue 02 (2008-05-07)



Reference

UAM data UAM When the UMG8900directly accesses usersthrough the subscriberframe, configure theUAM data.

15 Configuring UAMData


MGC If signaling packets ofV5UA/IUA are requiredto be transferred,configure signalingtransfer for theUMG8900.


StandAlone MGC Configure StandAlone,which can connect callsbetween users when thecommunication betweenthe UMG8900 and theMGW fails.

16 ConfiguringStandAlone



2-7

3 Preliminary Knowledge

About This Chapter

This describes the necessary knowledge of the UMG8900.

3.1 Frames and BoardsThis describes the hardware of the UMG8900.

3.2 Frame CascadingThis describes the cascading relationship of the SSM-256 self-cascading, SSM-32 self-cascading, and SSM-32 and SSM-256 mixed-cascading.

3.3 Centralized ForwardingThis describes the concept and configuration principles of centralized forwarding.

3.4 Dual HomingThis describes the concept and configuration principles of dual homing.

3.5 SCTP Multi-HomingThis describes the concept and configuration principles of Stream Control Transmission Protocol(SCTP) multi-homing.

3.6 Virtual Media GatewayThis describes the concept and configuration principles of the virtual media gateway (VMGW).

3.7 Interface ProtectionThis describes the concept and configuration principle of synchronous digital hierarchy (SDH)/synchronous optical network (SONET), and Internet Protocol (IP) interface protection.

3.8 UAM Background InformationThis describes the background information of the user access module (UAM).

3.9 Route BackupThis describes the concept and cautions of route backup.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 3 Preliminary Knowledge


3-1

3.1 Frames and BoardsThis describes the hardware of the UMG8900.

3.1.1 Introduction to the SSM-256 FrameThis describes the SSM-256 frame of the UMG8900.3.1.2 Introduction to the SSM-32 FrameThis describes the SSM-32 frame of the UMG8900.3.1.3 Numbering Cabinets and FramesThis describes the numbering order and configuration principle of the SSM-256 and SSM-32frames.3.1.4 Introduction to BoardsThis describes the boards of the UMG8900. Based on functions, boards are classified into thetypes, including the equipment and resource management unit, service and protocol processingunit, switching and cascading unit, interface unit, media resource processing unit, and CLK.

3.1.1 Introduction to the SSM-256 FrameThis describes the SSM-256 frame of the UMG8900.

The SSM-256 frame provides the 256 K time division multiplexing (TDM) service switchingplatform.

SSM-256 frames can be divided into four types:

l Main control framel Central switching framel Service framel Control frame

The main control frame is considered as an example, and Figure 3-1 shows the board positionof the SSM-256 frame. SSM-256 frames of other types differ from the main control frame inthat their front slots 7 and 8 are inserted with the MPUs rather than OMUs. The CLK is notconfigured in other types of frames.

Figure 3-1 Board position of the SSM-256 frame

Common

0 1 2 3 4 5 6

MOMU

7

MOMU

8 9 10

11

12

13

14

15

MTNB

MNET

MTNB

MNET

Backplane

Frontboard

Backboard

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

MCLK

MCLK

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

0 1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

3 Preliminary KnowledgeHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

3.1.2 Introduction to the SSM-32 FrameThis describes the SSM-32 frame of the UMG8900.

The SSM-32 frame provides the 32 K time division multiplexing (TDM) service switchingplatform.

SSM-32 frames can be divided into two types:

l Main control frame

l Service frame

Figure 3-2 shows the board position of the SSM-32 frame. In the case of SSM-32 frames, aservice frame differs from the main control frame in that their front slots 7 and 8 are insertedwith MPB boards rather than OMB boards.

Figure 3-2 Board position of the SSM-32 frame

Common

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

MTNB

MTNB

Backplane

Frontboard

Backboard

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

Common

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

MTNB

MTNB

The distinct difference between the SSM-256 frame and the SSM-32 frame is that the maincontrol board in an SSM-256 frame is the OMU and occupies only one slot, while that in theSSM-32 is the MOMB and occupies two slots.

3.1.3 Numbering Cabinets and FramesThis describes the numbering order and configuration principle of the SSM-256 and SSM-32frames.

Numbering Principles

The SSM-256 frame supports the cascading of up to nine frames, while the SSM-32 framesupports the cascading of up to three frames. A mixed networking with both SSM-256 andSSM-32 frames supports the cascading of up to 29 frames. The frame numbering order varieswith different frames or different cascading modes.

The numbering rules of cabinets and frames are as follows:

l The Nos. of cabinets start from 0. Frames are numbered according to their locations in acabinet, from bottom to top.



3-3

l SSM-256 self-cascading: The No. of the main control frame is 1, the Nos. of service framesare 2 to 7, and the No. of the control frame is 8. To satisfy the networking requirements,you can configure a dedicated central switching frame with the No. as 0. Otherwise, themain control frame can be directly inserted with the BLU or FLU cascading boards to serveas the central switching frame concurrently.

l SSM-32 self-cascading: The No. of the main control frame is 1. The Nos. of service framesare 2 and 3.

l SSM-256 and SSM-32 mixed cascading: The No. of the main control frame is 1. The Nos.of service frames are 2 to 7 and 9 to 29. The frame No., 8, is reserved as the extended controlframe. Though no extended control is configured in the mixed cascading, the frame No. isreserved. If needed, you can configure an independent central switching frame with theframe No. as 0. The main control frame can also be directly inserted with the BLU or FLUcascading boards to serve as the central switching frame concurrently.

l If the cabinet can only hold two frames due to dense E1 cables leaded out from the frame,it is recommended to reserve the unused frame No. for later expansion.

Numbering Frames in SSM-256 Self-Cascading ModeFigure 3-3 shows the numbering order of cabinets and frames in the SSM-256 self-cascadingmode.

Figure 3-3 Numbering order of cabinets and frames in the SSM-256 self-cascading mode

cabinet 0 cabinet 1 cabinet 2

Service frameFrame No.: 2

Central switchingframe

Frame No.: 0

Main contro frameFrame No.: 1






Extended controlframe

Frame No.: 8

Numbering Frames in SSM-32 Self-Cascading ModeFigure 3-4 shows the numbering order of cabinets and frames in the SSM-32 self-cascadingmode.


Configuration Guide


Issue 02 (2008-05-07)

Figure 3-4 Numbering order of cabinets and frames in the SSM-32 self-cascading mode

cabinet 0




Numbering in SSM-256 and SSM-32 Mixed Cascading modeAfter the configuration expansion from the SSM-32 self-cascading mode to the mixed cascadingmode. Figure 3-5 shows the numbering order of frames.

Figure 3-5 Numbering order of frames after configuration expansion of SSM-32 self-cascading

...

cabinet 0 cabinet 1





Frame No.: 0



The central switching frame must be an SSM-256 frame.

Figure 3-6 shows the numbering order of cabinets and frames in the SSM-256 and SSM-32mixed cascading mode.



3-5

Figure 3-6 Numbering order of cabinets and frame in the SSM-256 and SSM-32 mixedcascading mode

...

cabinet 0 cabinet 1 cabinet 9



Frame No.: 0







The central switching frame must be an SSM-256 frame, and other frames are SSM-32 frames.

In Figure 3-6, it is supposed that cabinet 1 holds only two frames because the frames lead outdense E1 cables. That is, it is inserted with service frames 3 and 4. The space for service frame5 is empty. It is recommended that you reserve frame No. 5 and number frames in cabinet 2 from6.

Rules for Configuring Frames in CabinetsIn actual networking of the UMG8900, some factors must be considered, such as:

l Cooperation with an SIWF device

l E1 interface applications

l SSM-256 self-cascading

l SSM-32 self-cascading

l SSM-32 and SSM-256 mixed cascading

Thus, the rules for configuring frames and cabinets are as follows:

l Each cabinet can hold three frames at most. If all the time division multiplexing (TDM)interface boards in frames use E1 or T1 interfaces, each cabinet can hold two service framesat most for the convenience of installation and cabling.

l The central switching frame and control frame have no TDM service interface. Thus, thecabinet where the central switching frame or control frame is located can hold three frames,which does not affect the installation and cabling.

l The frames in the cabinet are placed from bottom to top.

l The main control frame is configured by default. It manages and maintains the wholeUMG8900 while providing services. The main control frame is always numbered 1 andcannot be assigned with any other No.


Configuration Guide


Issue 02 (2008-05-07)

3.1.4 Introduction to BoardsThis describes the boards of the UMG8900. Based on functions, boards are classified into thetypes, including the equipment and resource management unit, service and protocol processingunit, switching and cascading unit, interface unit, media resource processing unit, and CLK.

Equipment and Resource Management Units

Table 3-1 Equipment and resource management units

Board Name BackupMode

Board Position Function

LogicalBoard

PhysicalBoard

OperationMaintenanceUnit (OMU)

Media gatewayOperationMaintenanceUnit (MOMU)

Master/slave It is inserted in frontslot 7 or 8 of theSSM-256 maincontrol frame.A correspondingNET back board isrequired.

The OMUmanages all theframes of theUMG8900when multipleframes areconfigured.The MOMB canconvert thebroadbandservice data.The boardprovides theexternalinterfacesincluding theConsoleinterface.

Media gatewayOperationMaintenanceUnit B(MOMB)

Master/slave It is inserted in frontslots 6, 7, 8 and 9 ofthe SSM-32 maincontrol frame.Each board occupiestwo slots.A correspondingTNC back board isrequired.

Mainprocessingunit (MPU)

Media gatewayMainProcessing Unit(MMPU)

Master/slave It is inserted in frontslot 7 or 8 of theSSM-256 frameexcept the maincontrol frame.A correspondingNET back board isrequired.

The MPUmanages theboards in theframe where theMPU is located.The MMPB canconvert thebroadbandservice data.

Media gatewayMainProcessing UnitB (MMPB)

Master/slave It is inserted in frontslots 6, 7, 8 and 9 of aSSM-32 serviceframe.Each board occupiestwo slots.A correspondingTNC back board isrequired.



3-7



LogicalBoard

PhysicalBoard

ConnectionMaintenanceUnit (CMU)

Media gatewayConnectionMaintenanceFront Unit(MCMF)

Master/slave It is inserted in acommon front slot ofthe SSM-256 frameor the SSM-32 frame.No correspondingback board isrequired.

The CMUprocessesmessages of themedia resourcecontrol protocoland operates thecorrespondingresources.

Media gatewayConnectionMaintenanceBack unit(MCMB)

Master/slave It is inserted in acommon back slot ofthe SSM-256 frameor SSM-32 frame.No correspondingfront board isrequired.

ConnectionMaintenanceUnit (CMU)

Sub-card ofConnection &ManagementUnit (SCMU)

Load sharingor master/slave

It is inserted in thesubboard slot of theUG02MOMB or theUG02MMPB of theSSM-32 frame.

The CMUprocessesmessages of themedia resourcecontrol protocoland operates thecorrespondingresources.

ProtocolProcessingUnit (PPU)

Media gatewayBack ProtocolProcessing Unit(MPPB)

Load sharing It is inserted in acommon back slot ofthe SSM-256 frame.No correspondingfront board isrequired.

The PPUprocesses the H.248/SCTP/UDP/TCP/IPprotocols.The externalinterfacesinclude the FEinterface.

Media gatewayConnectionMaintenanceFront Unit(MCMF)

Load sharing It is inserted in acommon front slot ofthe SSM-256 frameor the SSM-32 frame.No correspondingback board isrequired.

Media gatewayConnectionMaintenanceBack unit(MCMB)

Load sharing It is inserted in acommon back slot ofthe SSM-256 frameor the SSM-32 frame.No correspondingfront board isrequired.


Configuration Guide


Issue 02 (2008-05-07)

Service and Protocol Processing Units

Table 3-2 Service and protocol processing units



LogicalBoard

Physical Board

High-speedRouting Unit(HRB)

Media gatewayHigh-speedRouting Unit(MHRU)

Master/slave It is inserted in acommon front slot ofthe SSM-256 frameor the SSM-32 frame.A correspondingE8T/E1G/P4L/ P1Hback board isrequired.

The MHRUtransfers theRTP/RTCP andIP bearerservices.


Media gatewayRTP ProcessingUnit (MRPU)

Master/slave The MRPUprocesses theIP routes,converges anddistributes IPservices.


Media gatewayHigh-speedRouting Unit D(MHRD)

Master/slave It is inserted in acommon back slot ofthe SSM-256 frameor the SSM-32 frame.A correspondingD8FT/D1GOsubboard is required.

The MHRDprocessed theIP routes, and itconverges, anddistributes theIP services.The MHRDprovides theservice accessfunction.


Media gateway IPover E1 Unit(MIOE)

Master/slave It is inserted in acommon front slot ofthe SSM-256 frameor the SSM-32 frame.

The MIOEimplement IPover E1.When the boardis used in theSSM-256frame, theframe must beconfiguredwith theMTNB.



3-9



LogicalBoard

Physical Board

FrontSignallingProcessingunit (SPF)

Media gatewayFront SignallingProcessing unit(MSPF)

Load sharing It is inserted in acommon front slot ofthe SSM-256 frameor the SSM-32 frame.No correspondingback board isrequired.

The SPFperformssignalingadaptation andtransfers thesignaling.

Switching and Cascading Units

Table 3-3 Switching and cascading units



LogicalBoard

Physical Board

Packetswitch Unit(NET)

Media gatewayPacket switchUnit (MNET)

Master/slave It is inserted in backslot 7 or 8 of theSSM-256 frame.A correspondingMPU or OMU frontboard is required.

The NETimplementsswitching ofpacket servicesand datacascadingbetween frames.The externalinterfacesincludes the2xGE, 4xFE,Clock, MIR,OMCinterfaces.

Front LinkUnit (FLU)

Media gatewayFront Link Unit(MFLU)

Nullbackup It is inserted in a frontslot of the SSM-256central switchingframe except slots 6,7, 8 and 9.A correspondingBLU back board isrequired.

The FLU andBLU provide 32K or 24 Ksubscribercascadingcapacity,interfacing andswitchingfunctions ontime divisionmultiplexing(TDM)narrowbanddata plane, and 2


Configuration Guide


Issue 02 (2008-05-07)



LogicalBoard

Physical Board

Back LinkUnit (BLU)

Media gatewayBack Link Unit(MBLU)

Master/slave It is inserted in a backslot of the SSM-256central switchingframe except slots 6,7, 8 and 9.A correspondingFLU front board isrequired.

x 1.25 Gbit/scascadingcapacity andinterfacingfunction on thebroadband dataplane.Providing FEcontrol datachannels todirectly connectframesThe BLUprovides thecascadinginterface.

Net LinkUnit (NLU)

Media gatewayNet Link Unit(MNLU)

Load sharing It is in back slots 4, 5,10 and 11 of theSSM-32 frame.

The NLUprovides 2 x1.25G/1 x1.25Gcascadingcapacity andinterfacingfunction on thebroadband dataplane.

TDM centralswitchingNet Unit(TNU)

Media gatewayTDM switchingNet Unit(MTNU)

Master/slave It is inserted in backslot 6 or 9 of theSSM-256 frame.No correspondingfront board isrequired.

The TNUimplementsTDM serviceswitching.The MTNUprovides 24 Kcascadingcapacity.The TCLUprovides 24 Kcascadingcapacity.The MTNBprovides 32 Kcascadingcapacity.The MTNCprovides 3 x 8K

TDMConvergence &Link Unit(TCLU)

Master/slave It is inserted in backslot 6 or 9 of theSSM-256 maincontrol frame or theservice frame.No correspondingfront board isrequired.



3-11



LogicalBoard

Physical Board

Media gatewayTDM switchingNet Unit B(MTNB)

Master/slave It is inserted in backslot 6 or 9 of theSSM-256 frame.No correspondingfront board isrequired.

cascadingcapacity.The MTNCprovides the FEswitchingfunction for thecontrol plane.The MTNCprovides multi-frame cascadingchannels for theFE plane and theTDM plane.The MTNCmanages theboards in theframe where theMTNC islocated.The MTNCprovides level 3clock signal forthe systemthrough theclock subboard.

Media gatewayTDM switchingNet Unit C(MTNC)

Master/slave It is in back slots 6, 7,8 and 9 of the SSM-32frame.Each board occupiestwo slots.A correspondingMOMB/MMPB frontboard is required.

Interface Units

Table 3-4 Interface units



LogicalBoard

Physical Board

1-port GEOpticalinterface card(E1G)

Media gatewayone-port GEOptical interfacecard (MG1O)

Nullbackup It is inserted in acommon back slot ofthe SSM-256 frameor the SSM-32frame.A correspondingHRB front board isrequired.

The E1Gprovides oneGE interface.


Configuration Guide


Issue 02 (2008-05-07)



LogicalBoard

Physical Board

1-portSTM-4 POSopticalInterfaceboard (P1H)

Media gateway 1Port STM-4 POSOptical InterfaceBoard (MP1H)


The P1Hprovides one622 Mbit/sPOS interface.

2*155MSDH/SONETopticalinterface card(S2L)

Media gateway2*155M SDH/SONET opticalinterface card(MS2L)

Master/slave or loadsharing

The UG01MS2L andUG01MS2E can beonly inserted in acommon back slot ofthe SSM-256 frame.The UG02MS2L andUG02MS2E can beinserted in a commonback slot of theSSM-256 frame orthe SSM-32 frame.No correspondingfront board isrequired.

The MS2Lprovides two155 Mbit/sSDH opticalinterfaces.The MS2Eprovides two155 Mbit/sSDH electricalinterfaces.

Media gateway2*155M SDH/SONETElectronicalinterface card(MS2E)


1*155MSDH/SONETopticalinterface card(S1L)

Media gateway1*155M SDH/SONET opticalinterface card(MS1L)


It is inserted in acommon back slot ofthe SSM-32 frame.No correspondingfront board isrequired.

The MS1Lprovides one155 Mbit/sSDH opticalinterface.The MS1Eprovides one155 Mbit/sSDH electricalinterface.

Media gateway2*155M SDH/SONETElectronicalinterface card(MS1E)


4 PortsSTM-1 ATMOpticalInterfaceBoard (A4L)

Media gateway 4Ports STM-1 ATMOptical InterfaceBoard (MA4L)

Nullbackup It is inserted in acommon back slot ofthe SSM-256 frameor the SSM-32frame.A correspondingASU front board isrequired.

The A4Lprovides four155 M ATMopticalinterfaces.



3-13



LogicalBoard

Physical Board

4 Port STM-1POS OpticalInterfaceBoard (P4L)

Media gateway 4Port STM-1 POSOptical InterfaceBoard (MP4L)


The P4Lprovides four155 Mbit/sPOSinterfaces.

8-port10/100MEthernetinterfaceboard (E8T)

Media gateway 8-port 10/100MEthernet InterfaceBoard (ME8T)


The E8Tprovides eightFE interfaces.

32*E1 portTDMinterfaceboard (E32)

Media gateway32*E1 ports TDMinterface board(ME32)

Loadsharing

It is inserted in acommon back slot ofthe SSM-256 frameor the SSM-32frame.No correspondingfront board isrequired.

The ME32provides 32 E1interfaces toextract linesignaling fromCAS such asR2 and CNo.1or insert linesignaling intothem.The MESUprovides 32 E1interfaces toreceive andsend NO.5 linesignaling andregistersignaling.

Media gateway32*E1 interfacecard with Signalingfunction Unit(MESU)

Loadsharing

32*T1 portTDMinterfaceboard (T32)

Media gateway32*T1 ports TDMinterface board(MT32)

Loadsharing


The MT32provides 32 T1interfaces toextract linesignaling fromCAS such asR2 and CNo.1or insert linesignaling intothem.


Configuration Guide


Issue 02 (2008-05-07)



LogicalBoard

Physical Board

32*T1 portTDMinterfaceboard (T32)

Media gateway32*T1 interfacecard with Signalingfunction Unit(MTSU)

Loadsharing


The MTSUprovides 32 T1interfaces toreceive andsend NO.5 linesignaling andregistersignaling.

PDHInterfaceElectronicalUnit (PIE)

Media gatewayPDH InterfaceElectronical Unit(MPIE)



The PIEprovides threeE3/T3 PDHelectricalinterfaces.

Media Resource Processing Units

Table 3-5 Media resource processing units



LogicalBoard

Physical Board

VoiceProcessingUnit (VPU)

Media gatewayVoice ProcessingUnit B (MVPB)

Loadsharing

It is inserted in acommon front slot ofthe SSM-256 frame.No correspondingback board isrequired.

The VPUprovides thetranscoding andEC functionsfor voiceservice streams.The VPUprovidesannouncementplayingresources toimplement thedigit-collectingandannouncement-playingservices.

Media gatewayVoice ProcessingUnit D (MVPD)

Loadsharing

It is inserted in acommon front slot ofthe SSM-256 frame orthe SSM-32 frame.No correspondingback board isrequired.



3-15



LogicalBoard

Physical Board

Media gatewayTransCode Unit B(MTCB)

Loadsharing

It is inserted in acommon front slot ofthe SSM-256 frame.No correspondingback board isrequired.

When the VPUis used in theSSM-256frame, theframe must beconfigured withthe MTNB.

Media gatewayTransCode Unit D(MTCD)

Loadsharing

It is inserted in acommon front slot ofthe SSM-256 frame orthe SSM-32 frame.No correspondingback board isrequired.

EchoCancellationUnit (ECU)

Media gatewayEcho CancellationUnit (MECU)

Loadsharing

The UG01MECU canbe inserted in acommon front slot ofthe SSM-256 frame.The UG02MECU canbe inserted in acommon front slot ofthe SSM-256 frame orthe SSM-32 frame.No correspondingfront board isrequired.

The ECUimplements theEC function forvoice signals.


Configuration Guide


Issue 02 (2008-05-07)

CLK

Table 3-6 Clock units



LogicalBoard

Physical Board

Clock Unit(CLK)

Media gatewayClock Unit (MCLK)

Master/slave

It is inserted in backslot 0 or 1 of theSSM-256 frame or theSSM-32 frame.No correspondingfront board isrequired.

The CLKprovides clocksignals forservices.The externalinterfacesincludes theclock input/outputinterfaces.

3.2 Frame CascadingThis describes the cascading relationship of the SSM-256 self-cascading, SSM-32 self-cascading, and SSM-32 and SSM-256 mixed-cascading.

3.2.1 SSM-256 Self-CascadingThis describes the SSM-256 self-cascading.


3.2.3 SSM-256 and SSM-32 Mixed Cascading (UG01NET and BLU.A Configured)This describes the SSM-256 and SSM-32 mixed cascading when the UG01NET works with theBLU.A.

3.2.4 SSM-256 and SSM-32 Mixed Cascading (UG02NET and BLU.C Configured)This describes the SSM-256 and SSM-32 mixed cascading when the UG02NET works with theBLU.C.


Both the main control frame and service frames can connect with the central switching framethrough 1 FE + 2 GE + 3 TDM or 1 FE + 2 GE + 4 TDM cascading channels. The control frameconnects with the central switching frame through one fast Ethernet (FE) cascading channel.The central switching frame can be independently configured, and the main control frame canperform the functions of the central switching frame. Insert the BLU/FLU cascading boards inthe main control frame to implement the multi-frame cascading.

Figure 3-7 shows the nine-frame self-cascading of SSM-256 frames.



3-17

Figure 3-7 SSM-256 nine-frame cascading

2# 3# 4# 6# 7#

0#

1#

8#

4*8 K TDM 1*FE

NET

NET

TNB

TNB

NET

NET

TNB

TNB

BLU

BLU

BLU

BLU

BLU

BLU

BLU

BLU

BLU

BLU

BLU

BLU

NET

NET

5#

2*GE

0#: central switching frame 1#: main control frame 2# to 7#: service frames 8#: control frame

The NET is of two versions: UG01NET and UG02NET. In term of the packet switchingcapability, the UG01NET provides 16 gigabit Ethernet (GE) packet switching capability, andthe UG02NET provides 24 GE packet switching capability. In term of the cascading cableconnection, the UG01NET uses interface FE1 to perform FE cascading, and the UG02NET usesinterfaces FE1&FE2 and FE3&FE4 to perform FE cascading.

The BLU is of three versions: UG01BLU, UG02BLU.A, and UG02BLU.C. The UG01BLUprovides 3 x 8K time division multiplexing (TDM) cascading channels, and the UG02BLUprovides 4 x 8K TDM cascading channels. The UG02BLU.A uses interface FE0 to perform FEcascading, and the UG02BLU.C uses FE1&FE2 or FE3&FE4 to perform FE cascading, whichis the difference between the UG02BLU.A and UG02BLU.C.

For details about boards, refer to 3.1.4 Introduction to Boards.


l The TNC in the main control frame is the UG02TNC providing two time divisionmultiplexing (TDM) channels or the UG01TNC.The TNC in the service frame is the UG02TNC providing one TDM cascading channel orthe UG01TNC.In the case of SSM-32 self-cascading, up to three frames can be cascaded. The centralswitching frame and main control frame are combined. Each service frame connects withthe central switching frame through one fast Ethernet (FE) and one TDM cascading channel.


Configuration Guide


Issue 02 (2008-05-07)

Service frames must connect with the main control frame through the TDM cascadingoptical interface 0 on its TNC.TDM cascading optical interfaces 0 and 1 of the central switching frame or main controlframe are respectively connected to TDM cascading interface 0 in other two frames.Four FE interfaces exist on the TNC. FE interfaces 1 and 2 are connected to FE interface3 on the TNCs of the other two frames to implement the FE cascading of service frames.If the GE cascading exists, insert the NLU into slots 4 and 5 or slots 10 and 11 of frame 1to implement the GE cascading between two service frames.Figure 3-8 shows the three-frame self-cascading of SSM-32 frames.

Figure 3-8 Three-frame self-cascading of SSM-32 frames

TNC TNC

TNC TNC

TNC TNC1#

1*8KTDM 1*FE

2#

3#

NLU

NLU

NLU

NLU

1*GE

NLU

NLU

NLU

NLU

1#: central switching frame 2#: service frame 3#: service frame

l The TNC in the main control frame is the UG02TNC providing four time divisionmultiplexing (TDM) channels. The TNC in the service frame is the UG02TNC providingtwo TDM cascading channels.The UMG8900 supports up to three frames in SSM-32 self-cascading. The centralswitching frame and the main control frame are integrated. The UMG8900 provides fourTDM cascading optical interfaces. The service frame connects to the main control framethrough the 1 FE + 2 TDM cascading channel to implement the 2 x 8 K TDM cascading.The service frame must connect with the main control frame through TDM cascadingoptical interfaces 0 and 1 on the TNC. The TNC provides two TDM cascading opticalinterfaces.Cascading optical interfaces 0 and 1 on the TNC in the central switching and main controlintegrated frame connect to TDM cascading optical interfaces 0 and 1 on the TNC in serviceframe 1. For service frame 1, refer to 2# in Figure 3-9. Cascading optical interfaces 2 and3 on the TNC in the central switching and main control integrated frame connect to TDMcascading optical interfaces 0 and 1 on the TNC in service frame 2. For service frame 2,refer to 3# in Figure 3-9.



3-19

The TNC provides four FE interfaces. FE interfaces 1 and 2 connect to FE interfaces 3 onthe TNCs in the other two frames to implement the FE cascading with service frames.If the GE cascading exists, insert the NLU into slots 4 and 5 or slots 10 and 11 of frame 1to implement the GE cascading with two service frames.Figure 3-9 shows the three-frame self-cascading of SSM-32 frames.

Figure 3-9 Three-frame self-cascading of SSM-32 frames

TNC TNC

TNC TNC

TNC TNC

1#

2#

3#

NLU

NLU

NLU

NLU

NLU

NLU

NLU

NLU

1*8KTDM 1*FE1*GE

1#: central switching frame 2#: service frame 3#: service frame

3.2.3 SSM-256 and SSM-32 Mixed Cascading (UG01NET and BLU.AConfigured)

This describes the SSM-256 and SSM-32 mixed cascading when the UG01NET works with theBLU.A.

SSM-256 and SSM-32 frames support mixed cascading. That is, an SSM-256 central switchingframe, served by a dedicated frame or the main control frame, can cascade with SSM-256 orSSM-32 frames. Thus, two mixed networking modes with different capacities can be adoptedto satisfy actual needs.

Each TNB or BLU in the SSM-256 central switching frame can cascade with one SSM-256frame or four SSM-32 frames. Thus, the number of service frames that can be attached is n xSSM-256 + (7 - n) x 4 x SSM-32, where n refers to the number of SSM-256 frames except thecentral switching frame. When only SSM-32 frames are attached, up to 28 service frames canbe cascaded.


Configuration Guide


Issue 02 (2008-05-07)

The cascading of the SSM-256 central switching frame and SSM-256 service frames is describedin 3.2.1 SSM-256 Self-Cascading. Thus, only the cascading of the SSM-256 central switchingframe and SSM-32 service frames is shown here.

When the UG01NET and BLU.A are configured in the SSM-256 frame, the SSM-256 frame iscascaded with the SSM-32 frame in two modes:

l TNB and NET used

l BLU used

TNB and NET Usedl If the TNC in the SSM-32 frame provides one TDM cascading optical interface, the

SSM-256 frame can cascade with four SSM-32 frames, that is, one SSM-32 main controlframe and three SSM-32 service frames.Each SSM-32 service frame connects with the central switching frame through one fastEthernet (FE) and one time division multiplexing (TDM) cascading channel. SSM-32service frames must connect with the central switching frame through TDM cascadingoptical port 0 on the TNC.Figure 3-10 shows the mixed cascading of one SSM-256 frame and four SSM-32 framesthrough the TNB.



3-21

Figure 3-10 Mixed cascading of one SSM-256 frame and four SSM-32 frames through theTNB

TNC TNC

TNC TNC

TNC TNC1#

1*8KTDM 1*FE

2#

3#

0# TNB

TNB

NET

NET

TNC TNC

4#

NLU

NLU

1*GE

0#: central switching frame 1#: main control frame 2# to 4#: service frames

In this mode, the main control frame and the central switching frame are cascaded throughthe TNB to implement the TDM service cascading. The cascading of the control plane isimplemented through the FE cascading interface of the NET.

For the cascading of the GE plane, only one service frame is cascaded. Connect the opticalinterface on the NLU of the service frame to the GE interfaces of the master and slave NETsto implement the GE cascading. The NLU can be configured in slots 4 and 5 or slots 10and 11 of the SSM-32 service frame.

On the FE plane, main control frame 1 connects to the FE interface on the NET in centralswitching frame 0 through the FE3 interface on the TNC. Service frames 2, 3, and 4respectively connect to the FE2, FE1, and FE0 interface in main control frame 1 throughthe FE3 interfaces. Main control frame 1 can be considered as a level-2 cascading frame.


Configuration Guide


Issue 02 (2008-05-07)

l If the TNC in the SSM-32 frame provides two TDM cascading optical interfaces, theSSM-256 frame can cascade with two SSM-32 frames, that is, one SSM-32 main controlframe and one SSM-32 service frame.Each SSM-32 frame connects to the SSM-256 central switching frame through the 1 FE +2 TDM cascading channel. The SSM-32 frame must connect to the SSM-256 centralswitching frame through TDM cascading optical interfaces 0 and 1 on the TNC.Figure 3-11 shows the mixed cascading of one SSM-256 frame and two SSM-32 framesthrough the TNB.

Figure 3-11 Mixed cascading of one SSM-256 frame and two SSM-32 frames through theTNB

TNC TNC

TNC TNC

1#

1*8KTDM 1*FE

2#

0#

TNB

TNB

NET

NET

NLU

NLU

1*GE

0#: central switching frame 1#: main control frame 2#: service frame

NOTE

The cascading on the FE and GE planes is the same as the cascading of four SSM-32 frames throughthe TNB.

l If the TNC in the SSM-32 frame provides four TDM cascading optical interfaces, theSSM-256 frame can cascade with one SSM-32 frame.Each SSM-32 frame connects to the SSM-256 central switching frame through the 1 FE +4 TDM cascading channel. The SSM-32 frame connects to optical interfaces 0, 1, 2, and 3on the TNB in the SSM-256 central switching frame through TDM cascading opticalinterfaces 0, 1, 2, and 3 on the TNC.Figure 3-12 shows the mixed cascading of one SSM-256 frame and one SSM-32 framethrough the TNB.



3-23

Figure 3-12 Mixed cascading of one SSM-256 frame and one SSM-32 frame through theTNB

TNC TNC1#

1*8KTDM 1*FE

0# TNB

TNB

NET

NET

NLU

NLU

1*GE

0#: central switching frame 1#: main control frame

NOTE

The cascading on the FE and GE planes is the same as the cascading of four SSM-32 frames throughthe TNB.

BLU Usedl The BLU in the central switching frame supports four TDM cascading optical interfaces.

If the TNC in the SSM-32 frame provides one TDM cascading optical interface, theSSM-256 frame can cascade with four SSM-32 frames, that is, one SSM-32 main controlframe and three SSM-32 service frames.The SSM-256 central switching frame can be cascaded with four SSM-32 frames throughthe BLU. Figure 3-13 shows the mixed cascading of one SSM-256 frame and four SSM-32frames through the BLU.


Configuration Guide


Issue 02 (2008-05-07)

Figure 3-13 Mixed cascading of one SSM-256 frame and four SSM-32 frames through theBLU

TNC TNC

TNC TNC

TNC TNC1#

1*8KTDM 1*FE

2#

3#

0# TNB

TNB

NET

NET

TNC TNC

4#

NLU

NLU

1*GE

BLUBLU


In this mode, one FE cascading interface of the MBLU in the central switching frame iscascaded with one FE cascading interface of the MTNC in one SSM-32 service frame, andthe other three FE interfaces of the MBLU in the central switching frame are cascaded withthe other three SSM-32 service frames to implement the four-frame FE cascading. The fourTDM cascading interfaces of the MBLU in the central switching frame are cascaded withthe TDM cascading interfaces of the four SSM-32 service frames to implement the four-frame TDM cascading.The GE optical interfaces on the master and slave MBLUs are cascaded with the opticalinterface on the MNLU in one SSM-32 frame to implement the GE cascading of one serviceframe. The MNLU in the service frame can be only inserted in slots 4 and 5, or slots 10and 11.



3-25

l If the TNC in the SSM-32 frame provides two TDM cascading optical interfaces, theSSM-256 frame can cascade with two SSM-32 frames, that is, one SSM-32 main controlframe and one SSM-32 service frame.On the TDM plane, the first SSM-32 frame, main control frame, connects to opticalinterfaces 0 and 1 on the BLU through TDM optical interfaces 0 and 1 on the UG02TNC.The second SSM-32 frame, service frame, connects to optical interfaces 2 and 3 on theBLU through TDM optical interfaces 0 and 1 on the UG02TNC. Refer to Figure 3-11.

NOTE

The cascading on the FE and GE planes is the same as the cascading of four SSM-32 frames throughthe BLU.

l If the TNC in the SSM-32 frame provides four TDM cascading optical interfaces, theSSM-256 frame can cascade with one SSM-32 frame.The SSM-32 frame connects to optical interfaces 0, 1, 2, and 3 on the BLU in the SSM-256central switching frame through TDM cascading optical interfaces 0, 1, 2, and 3 on theTNC. Refer to Figure 3-12.

NOTE

The cascading on the FE and GE planes is the same as the cascading of four SSM-32 frames throughthe BLU.

3.2.4 SSM-256 and SSM-32 Mixed Cascading (UG02NET and BLU.CConfigured)

This describes the SSM-256 and SSM-32 mixed cascading when the UG02NET works with theBLU.C.

SSM-256 and SSM-32 frames support mixed cascading. That is, an SSM-256 central switchingframe, served by a dedicated frame or the main control frame, can cascade with SSM-256 orSSM-32 frames. Thus, two mixed networking modes with different capacities can be adoptedto satisfy actual needs.

Each TNB or BLU in the SSM-256 central switching frame can cascade with one SSM-256frame or four SSM-32 frames. Thus, the number of service frames that can be attached is n xSSM-256 + (7 - n) x 4 x SSM-32, where n refers to the number of SSM-256 frames except thecentral switching frame. When only SSM-32 frames are attached, up to 28 service frames canbe cascaded.

When the UG02NET and the BLU.C are configured in the SSM-256 frame, the SSM-256 framecan be cascaded with the SSM-32 frame in the following modes:

l TNB used and GE cascading not supported

l TNB used and GE cascading supported

l BLU used and GE cascading not supported

l BLU used and GE cascading supported

TNB and NET Usedl The GE cascading is not supported.

– If the UG01TNC or the UG02TNC in the SSM-32 frame provides one TDM cascadingoptical interface, the SSM-256 frame can cascade with four SSM-32 frames, that is, oneSSM-32 main control frame and three SSM-32 service frames.


Configuration Guide


Issue 02 (2008-05-07)

Figure 3-14 shows the mixed cascading of one SSM-256 frame and four SSM-32 framesthrough the TNB without gigabit Ethernet (GE) cascading.

Figure 3-14 Mixed cascading of one SSM-256 frame and four SSM-32 frames throughthe TNB (without GE cascading)

TNC TNC

TNC TNC

TNC TNC1#

1*8KTDM 1*FE

2#

3#

0# TNB

TNB

NET

NET

TNC TNC

4#


In this mode, the SSM-256 frame and SSM-32 frames are cascaded through the TNBand TNC to implement the time division multiplexing (TDM) cascading; and they arecascaded through the fast Ethernet (FE) cascading interface of the UG02NET toimplement the fast Ethernet (FE) cascading.The TNB provides four TDM cascading optical interfaces, and they can be cascadedwith four SSM-32 frames. For the cascading on the control plane, the FE1 and FE2interfaces on the UG02NET are connected to the FE3 interfaces in main control frame1 and service frame 2, and the FE3 and FE4 interfaces on the UG02NET are connectedto the FE3 interfaces in service frames 3 and 4.



3-27

– If the UG02TNC in the SSM-32 frame provides two TDM cascading optical interfaces,the SSM-256 frame can cascade with two SSM-32 frames, that is, one SSM-32 maincontrol frame and one SSM-32 service frame.Figure 3-15 shows the mixed cascading of one SSM-256 frame and two SSM-32 framesthrough the TNB.

Figure 3-15 Mixed cascading of one SSM-256 frame and two SSM-32 frames throughthe TNB (without GE cascading)

TNC TNC

TNC TNC1#

1*8KTDM 1*FE

2#

0# TNB

TNB

NET

NET


The SSM-256 frame and the SSM-32 frames are cascaded through the TNB and theTNC to implement the TDM service cascading and cascaded through the FE cascadinginterface on the UG02NET to implement the cascading on the control plane.The TNB supports four TDM cascading optical interfaces and can cascade with twoSSM-32 frames. The cascading on the control plane is the same as the cascading withfour SSM-32 frames after new FE cascading interfaces on the UG02NET are added.

– If the UG02TNC in the SSM-32 frame provides four TDM cascading optical interfaces,the SSM-256 frame can cascade with one SSM-32 frame.Figure 3-16 shows the mixed cascading of one SSM-256 frame and one SSM-32 framethrough the TNB.


Configuration Guide


Issue 02 (2008-05-07)

Figure 3-16 Mixed cascading of one SSM-256 frame and one SSM-32 through the TNB(without GE cascading)

TNC TNC1#

1*8KTDM 1*FE

0# TNB

TNB

NET

NET

0#: central switching frame 1#: main control frame

The SSM-256 frame and the SSM-32 frames are cascaded through the TNB and theTNC to implement the TDM service cascading and cascaded through the FE cascadinginterface on the UG02NET to implement the cascading on the control plane.The TNB supports four TDM cascading optical interfaces and can cascade with oneSSM-32 frame. The cascading on the control plane is the same as the cascading withfour SSM-32 frames after new FE cascading interfaces on the UG02NET are added.

l The GE cascading is supported.– If the UG01TNC or the UG02TNC in the SSM-32 frame provides one TDM cascading

optical interface, the SSM-256 frame can cascade with two SSM-32 frames, that is, oneSSM-32 main control frame and one SSM-32 service frame.Figure 3-17 shows the mixed cascading of one SSM-256 frame and two SSM-32 framesthrough the TNB with GE cascading.



3-29

Figure 3-17 Mixed cascading of one SSM-256 frame and two SSM-32 frames throughthe TNB (with GE cascading)

TNC TNC

TNC TNC

2#

1#

0# TNB

TNB

NET

NET

NLU

NLU

NLU

NLU

1*8KTDM 1*FE1*GE


In this mode, the GE cascading is supported, and one SSM-256 frame can be cascadedwith up to two SSM-32 frames. The cascading of the TDM service is implementedthrough the TNB and TNC, and the cascading of the control plane and packet plane isimplemented through the FE cascading interfaces and GE cascading interfaces on theUG02NET.The TNB provides four TDM cascading optical interfaces, and two of them are cascadedwith two SSM-32 frames. The FE cascading interfaces on the UG02NET are cascadedwith FE3 interfaces on the TNCs in two SSM-32 frames through expansion.In this mode, two GE interfaces on the UG02NET are cascaded with the opticalinterfaces of the NLUs in two SSM-32 frames to implement the cascading of the GEplane. The NLUs can be inserted in slots 4 and 5 or slots 10 and 11 in SSM-32 frames.In this manner, the NLUs can work only in the master and slave mode.

– If the UG02TNC in the SSM-32 frame provides two TDM cascading optical interfaces,the SSM-256 frame can cascade with two SSM-32 frames, that is, one SSM-32 maincontrol frame and one SSM-32 service frame.On the TDM plane, the first SSM-32 frame, main control frame, connects to opticalinterfaces 0 and 1 on the BLU through TDM optical interfaces 0 and 1 on the UG02TNC.The second SSM-32 frame, service frame, connects to optical interfaces 2 and 3 on theBLU through TDM optical interfaces 0 and 1 on the UG02TNC. Refer to Figure3-15.

NOTE

The cascading on the FE and GE planes is the same as the cascading of four SSM-32 framesthrough the TNB.

– If the UG02TNC in the SSM-32 frame provides four TDM cascading optical interfaces,the SSM-256 frame can cascade with one SSM-32 frame.


Configuration Guide


Issue 02 (2008-05-07)

The SSM-32 frame connects to optical interfaces 0, 1, 2, and 3 on the BLU in theSSM-256 central switching frame through TDM cascading optical interfaces 0, 1, 2,and 3 on the UG02TNC. Refer to Figure 3-16.

NOTE


BLU Usedl The GE cascading is not supported.

– If the UG01TNC or the UG02TNC in the SSM-32 frame provides one TDM cascadingoptical interface, the SSM-256 frame can cascade with four SSM-32 frames, that is, oneSSM-32 main control frame and three SSM-32 service frames.The SSM-256 central switching frame can cascade with the SSM-32 frame through theUG02BLU.C. If the GE cascading is not supported, the SSM-256 central switchingframe can cascade with four SSM-32 frames through the BLU. Refer to Figure 3-18.



3-31

Figure 3-18 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the BLU(without GE cascading)

TNC TNC

TNC TNC

TNC TNC1#

1*8KTDM 1*FE

2#

3#

0# TNB

TNB

NET

NET

TNC TNC4#

BLUBLU


In this mode, the SSM-256 frame and SSM-32 frames are cascaded through the BLUand TNC to implement the TDM cascading; they are cascaded through the FE interfaceson the BLUs to implement the FE cascading.The BLU provides four TDM cascading optical interfaces, and they can be cascadedwith four SSM-32 frames. The FE cascading interfaces on the UG02BLU.C arecascaded with FE3 interfaces on the TNCs in four SSM-32 frames through expansion.


Configuration Guide


Issue 02 (2008-05-07)

– If the UG02TNC in the SSM-32 frame provides two TDM cascading optical interfaces,the SSM-256 frame can cascade with two SSM-32 frames, that is, one SSM-32 maincontrol frame and one SSM-32 service frame.On the TDM plane, the first SSM-32 frame, main control frame, connects to opticalinterfaces 0 and 1 on the BLU through TDM optical interfaces 0 and 1 on the UG02TNC.The second SSM-32 frame, service frame, connects to optical interfaces 2 and 3 on theBLU through TDM optical interfaces 0 and 1 on the UG02TNC. Refer to Figure3-15.

NOTE

The cascading on the FE and GE planes is the same as the cascading of four SSM-32 framesthrough the BLU.

– If the UG02TNC in the SSM-32 frame provides four TDM cascading optical interfaces,the SSM-256 frame can cascade with one SSM-32 frame.The SSM-32 frame connects to optical interfaces 0, 1, 2, and 3 on the BLU in theSSM-256 central switching frame through TDM cascading optical interfaces 0, 1, 2,and 3 on the UG02TNC. Refer to Figure 3-16.

NOTE


l The GE cascading is supported.– If the UG01TNC or the UG02TNC in the SSM-32 frame provides one TDM cascading

optical interface, the SSM-256 frame can cascade with two SSM-32 frames, that is, oneSSM-32 main control frame and one SSM-32 service frame.If the UG02BLU.C is configured in the SSM-256 frame and the GE cascading issupported, the SSM-256 frame can cascaed with two SSM-32 frames through theUG02BLU.C. Refer to Figure 3-19.



3-33

Figure 3-19 Mixed cascading of one SSM-256 frame and two SSM-32 frames throughthe BLU (with GE cascading)

1*GE 1*FE1*8KTDM

TNC TNC

TNC TNC1#

2#

0# TNB

TNB

NET

NET

BLUBLU

NLU

NLU

NLU

NLU


In this mode, the GE cascading is supported, and one SSM-256 frame can be cascadedwith up to two SSM-32 frames. The cascading of the TDM service is implementedthrough the BLU and TNC, and the cascading of the control plane and packet plane isimplemented through the FE cascading interfaces and GE cascading interfaces on theBLU.

The BLU provides four TDM cascading optical interfaces, and two of them are cascadedwith two SSM-32 frames. The FE cascading interfaces on the BLU are cascaded withFE3 interfaces on the TNCs in two SSM-32 frames through expansion.

In this mode, two GE interfaces on the BLU are cascaded with the optical interfaces ofthe NLUs in two SSM-32 frames to implement the cascading of the GE plane. TheNLUs can be inserted in slots 4 and 5 or slots 10 and 11 in SSM-32 frames. In thismanner, the NLUs can work only in the master and slave mode.

The UG02NET and the BLU.C support the original configuration mode, and they canreplace the UG01NET and BLU.A.

– If the UG02TNC in the SSM-32 frame provides two TDM cascading optical interfaces,the SSM-256 frame can cascade with two SSM-32 frames, that is, one SSM-32 maincontrol frame and one SSM-32 service frame.

On the TDM plane, the first SSM-32 frame, main control frame, connects to opticalinterfaces 0 and 1 on the BLU through TDM optical interfaces 0 and 1 on the UG02TNC.The second SSM-32 frame, service frame, connects to optical interfaces 2 and 3 on theBLU through TDM optical interfaces 0 and 1 on the UG02TNC. Refer to Figure3-15.


Configuration Guide


Issue 02 (2008-05-07)

NOTE

The cascading on the FE and GE planes is the same as the cascading of four SSM-32 framesthrough the BLU.

– If the UG02TNC in the SSM-32 frame provides four TDM cascading optical interfaces,the SSM-256 frame can cascade with one SSM-32 frame.The SSM-32 frame connects to optical interfaces 0, 1, 2, and 3 on the BLU in theSSM-256 central switching frame through TDM cascading optical interfaces 0, 1, 2,and 3 on the UG02TNC. Refer to Figure 3-16.

NOTE


3.3 Centralized ForwardingThis describes the concept and configuration principles of centralized forwarding.

The UMG8900 in complete configuration has at least four logical interfaces based on InternetProtocol (IP) bearer. The four logical interfaces are:

l Operation, administration and maintenance (OAM) interface

l H.248 interface

l SIGTRAN interface

l Bearer interface

If the four interfaces use their own physical interfaces and IP addresses, complex networkingand waste of IP address resources are caused.

The UMG8900 supports centralized forwarding of the following messages through an IPinterface:

l Operation and maintenance center (OMC) messages

l H.248 messages

l SIGTRAN messages

In this way, IP interfaces and addresses are saved. Installation and configuration are alsosimplified.

In case of multiple-frame networking, the H.248 and signaling transport (SIGTRAN) interfacesmust be set to the centralized forwarding mode if no special requirement exists.

Table 3-7 lists the IP interfaces used by the UMG8900.

Table 3-7 IP interfaces used by the UMG8900

LogicalPosition

Physical Position in theSSM-256 Physical Position in the SSM-32

OMU/MPU OMC interface numbered 0 on theNET

OMC interface numbered 0 on theTNCMc interface numbered 1 on theTNC



3-35

LogicalPosition

Physical Position in theSSM-256 Physical Position in the SSM-32

PPU FE0 port numbered 0 on the PPU FE0 port numbered 0 on the PPU

SPF MIR interface numbered 0 on theNET in the same frame

The SPF in frame SSM-32 does notprovide interfaces.

HRBFE ports numbered 0 to 7 on the E8TGE port numbered 0 on the E1G

FE ports numbered 0 to 7 on the E8TGE port numbered 0 on the E1G

In Table 3-7, the logical position refers to the board needed when you configure the interface,and the physical position refers to the actual cabling position of the interface.

Configuration Principles for Single-frame Networking

If the frame types are different, the configuration rules differ too. The frames of theUMG8900 fall into SSM-256 and SSM-32.

The configuration principles of these two types of frames are as follows.

Single SSM-256 networking falls into the following cases:

l No HRB is configured.

l The E8T (back board of the HRB) is configured.

l The E1G (back board of the HRB) is configured.

Through the OMC interface on the NET, the SSM-256 frame provides OAM, H.248 andSIGTRAN interfaces at the same time, if the HRB is not configured. The IP address of the OAMinterface is set as the slave one, and that of the H.248 and SIGTRAN interfaces is set as themaster one. In this case, if the H.248 and SIGTRAN messages are transmitted through the sameprotocol, different protocol interface numbers must be used.

Table 3-8 shows the usage rules of IP interfaces when the HRB is configured in the SSM-256frame.

Table 3-8 Usage rules of IP interfaces when the HRB is configured

LogicalPosition

Physical Position and FunctionWhen the E8T Is Configured

Physical Position and FunctionWhen Only the E1G IsConfigured

OMU OMC interface on the back NET,which can serve as an OAM interface

OMC interface on the back NET,which can serve as an OAMinterface

HRBThe first FE port on the back E8T,which can serve as an H.248 orSIGTRAN interface

GE port on the back E1G, which canserve as an H.248 or SIGTRANinterface through the master IPaddress


Configuration Guide


Issue 02 (2008-05-07)

LogicalPosition



HRBOther FE ports on the back E8T,which can serve as an IP servicebearer interface

GE port on the back E1G, which canserve as an IP service bearerinterface through the slave IPaddress

NOTE

If both the E8T and the E1G are configured in the frame, the E8T is used for centralized forwarding.

As shown in Table 3-8, the first FE port on the E8T or the GE port on the E1G needs to serveas H.248 and SIGTRAN interfaces at the same time. In this case, if the same transmissionprotocol is used for the H.248 and SIGTRAN messages, different protocol interface numbersmust be used.

NOTE

If the HRB is configured in the signal-frame networking, it is recommend to use the centralized forwardingfunction of the HRB.

Single SSM-32 networking falls into the following cases:

l No HRB is configured.

l The back E8T of the HRB is configured.

l The back E1G of the HRB is configured.

In case of single SSM-32 networking, if no HRB is configured, the SSM-32 uses the Mc interfaceon the OMU for centralized forwarding.

Table 3-9 shows the usage rules for IP interfaces.

Table 3-9 Usage rules for IP interfaces when no HRB is configured for single SSM-32networking

LogicalPosition Physical Position and Function

OMU OMC interface on the TNC, which can serve as an OAM interface

OMU Mc interface on the back TNC, which can serve as an H.248 or SIGTRANinterface

As shown in Table 3-9, the Mc interface on the OMU provides H.248 and SIGTRAN interfacesat the same time. In this case, if the same transmission protocol is used for H.248 and SIGTRANmessages, different protocol port numbers must be used.

If the HRB is configured for single SSM-32 networking, the usage rules are similar to those ofthe SSM-256 frame. See Table 3-10.



3-37

Table 3-10 Usage rules for IP interfaces when the HRB is configured for the single SSM-32networking

LogicalPosition



OMU OMC interface on the back TNC,which can also serve as an OAMinterface

OMC interface on the back TNC,which can serve as an OAMinterface

HRB The first FE port on the back E8T,which can serve as an H.248 orSIGTRAN interface

GE port on the back E1G, which canserve as an H.248 or SIGTRANinterface through the master IPaddress

HRB Other FE ports on the back E8T,which can serve as an IP servicebearer interface

GE port on the back E1G, which canserve as an IP service bearerinterface through the slave IPaddress

NOTE

If both the E8T and the E1G are configured in the frame, the E8T board is used for centralized forwarding.

As shown in Table 3-10, the first FE port on the E8T or the GE port on the E1G needs to provideH.248 and SIGTRAN interfaces at the same time. In this case, if the same transmission protocolis used for H.248 and SIGTRAN messages, different protocol port numbers must be adopted.

Configuration Principles for Multi-Frame Networking

In multi-frame cascading, both the H.248 and SIGTRAN interfaces must be set to centralizedforwarding mode unless otherwise noted.

The configuration principles are different for different cascading modes.

The UMG8900 supports the following cascading modes:

l SSM-256 self cascading

l SSM-32 self cascading

l SSM-256 and SSM-32 mixed cascading

The usage rules for IP interfaces in the three cascading modes are as follows.

Table 3-11 shows the usage rules for IP interfaces in case of SSM-256 self cascading.

Table 3-11 Usage rules for IP interfaces in case of SSM-256 self cascading

Logical Position Physical Position and Function

OMU in the main controlframe

OMC interface on the back NET, which can serve as anOAM OMC interface on the back NET, which can serve asan H.248 or SIGTRAN interface


Configuration Guide


Issue 02 (2008-05-07)


MPU in the central switchingframe

OMC interface on the back NET, which can serve as an H.248 or SIGTRAN interface

HRB Interface of the back E8T or E1G, which can serve as an IPservice bearer interface

As shown in Table 3-11, the OMC interface on the MPU in the central switching frame needsto provide both H.248 and SIGTRAN interfaces at the same time. In this case, if the sametransmission protocol is used for H.248 and SIGTRAN messages, different protocol portnumbers must be adopted.

Table 3-12 shows the usage rules for IP interfaces in case of SSM-32 self cascading.

Table 3-12 Usage rules for IP interfaces in case of SSM-32 self cascading

Logical position Physical position and function

OMB in the main controlframe

OMC interface on the back TNC, which can serve as anOAM interface

MPU in the first service frame OMC interface on the back TNC, which can serve as an H.248 or SIGTRAN interface

HRB interface of the back E8T or E1G, which can serve as an IPservice bearer interface

As shown in Table 3-12, the Mc interface on the MPU in the first service frame needs to provideboth H.248 and SIGTRAN interfaces at the same time. In this case, if the same transmissionprotocol is used for H.248 and SIGTRAN messages, different protocol port numbers must beadopted.

Table 3-13 shows the usage rules for IP interfaces in case of SSM-256 and SSM-32 mixedcascading.

Table 3-13 Usage rules for IP interfaces in case of SSM-256 and SSM-32 mixed cascading


OMU in the main controlframe

OMC interface on the back TNC, which can serve as anOAM interface

MPU in the central switchingframe

OMC interface of the back NET, which can serve as an H.248 interface or SIGTRAN interface

HRB interface of the back E8T or E1G, which can serve as an IPservice bearer interface

As shown in Table 3-13, the OMC interface on the MPU in the central switching frame needsto provide both H.248 and SIGTRAN interfaces at the same time. In this case, if the same



3-39

transmission protocol is used for H.248 and SIGTRAN messages, different protocol portnumbers must be adopted.

3.4 Dual HomingThis describes the concept and configuration principles of dual homing.

Dual homing is a disaster tolerance plan, which enables remote disaster recovery for the mediagateway (MGC) system. For the two dual homing MGCs, when one MGC fails to provideservices, the other MGC takes over its services. When the original master MGC recovers, theservices are switched back to the original MGC.

Figure 3-20 shows the dual homing plan.

Figure 3-20 Dual homing

MGC(Master)

H.248

UMG8900

SIGTRAN

MGC(Slave)

H.248

BICC/SIP

As shown in Figure 3-20, the UMG8900 is under the control of the master MGC in normalcases. When the master MGC fails, the UMG8900 switches the H.248 and SIGTRAN(M3UA/M2UA) links connected with the master MGC to the slave MGC.

On the UMG8900 side, this procedure involves configuration of dual homing of H.248 andSIGTRAN links.

NOTE

You need to configure data of dual homing on both the UMG8900 and the MGC.

3.5 SCTP Multi-HomingThis describes the concept and configuration principles of Stream Control Transmission Protocol(SCTP) multi-homing.

SCTP multi-homing means to support multiple IP addresses configured on the two sides of anSCTP link to provide a reliable end-to-end multi-path transmission mechanism and enhance thesystem reliability. If an SCTP link fails, media gateway (MGW) control messages and signalingmessages are switched to other links. Two local IP addresses and two peer IP addresses can beconfigured on the UMG8900. Refer to Figure 3-21.


Configuration Guide


Issue 02 (2008-05-07)

Figure 3-21 SCTP multi-homing

MGC

UMG8900

H.248/SIGTRAN

IP3 IP4

IP1 IP2

In Figure 3-21, the UMG8900 supports two modes: two paths and four paths. The two pathsare IP 1 to IP 3 and IP 2 to IP 4. The four paths are IP 1 to IP 3, IP 2 to IP 4, IP 2 to IP 3, and IP1 to IP 4. After receiving a link establishment request, the SCTP client starts establishing a linkto the SCTP server by carrying the local IP address list. The SCTP client selects peer IP addressesfirst and then local IP addresses in turn, until the link is established. If a link fails, services onH.248 links and Signaling Transport (SIGTRAN) links are automatically switched to other links.

Whether the two-path or four-path mode is adopted relies on the actual conditions.

For SCTP multi-homing, messages must be forwarded through the centralized forwardinginterface on the OMU/OMB/MPU. Therefore, the centralized forwarding module must work inload-sharing mode, and the master and slave boards must be capable of centralized forwarding.

3.6 Virtual Media GatewayThis describes the concept and configuration principles of the virtual media gateway (VMGW).

The VMGW function divides a physical MGW into multiple different logical MGWs. EachVMGW is identified by the VMGW ID, and it is managed by one or multiple media gateways(MGCs) of the same type or different types to meet the requirements of different networkingand carriers.

The system can allocate bearer resources of the MGW to different virtual MGWs in exclusiveor resource sharing mode to improve the flexibility of the device. The VMGW function canreduce the network construction cost of carriers and provide the operating of virtual carriers.

3.7 Interface ProtectionThis describes the concept and configuration principle of synchronous digital hierarchy (SDH)/synchronous optical network (SONET), and Internet Protocol (IP) interface protection.

The SDH/SONET and IP interface protection varies with the interface type. Refer to Table3-14.



3-41

Table 3-14 Interface protection types supported by different interfaces

LogicalInterfaceType

PhysicalInterfaceType

Non 1+1APSProtection

Non 1:NAPSProtection

1+1 APSProtection

1:N APSProtection

IP interface FE interface Auto support - - -

GE interface Support - - -

SDH/SONETinterface

SDH/SONETinterface

- - Support Support

NOTE

l The gigabit Ethernet (GE) interface supports only non 1+1 APS protection.

l The FE interface automatically support non 1+1 APS protection, and the FE interface does not supportthe interface protection function.

l The IP interface does not support the non 1:N APS protection or 1:N APS protection.

l The SDH/SONET interface supports 1+1 APS protection and 1:N APS protection.

As shown in Table 3-14, the UMG8900 supports four interface protection types. The supportedinterface protection types vary with the interface types, which is described as follows.

l Non 1+1 APS protection: is also called 1+1 breakthrough protection. One protection grouphas two interfaces, one master and the other slave. Services are switched based on the UP/DOWN status of the interfaces. In the normal state, the master interface is working. If themaster interface becomes DOWN, services on it are switched to the slave interface. Thismode can be automatically supported by hardware for some interfaces, and is not requiredto be configured. This mode applies when the FE/GE interface of the UMG8900 is used tointerconnect with the router.

l Non 1:N APS protection: is also called 1:N breakthrough protection. One protection grouphas N+1 interfaces, and services are switched based on the UP/DOWN status of theinterface. In the normal state, N interfaces are working. When one interface becomesDOWN, services on it are switched to the slave interface. This mode applies when the FE/GE interface of the UMG8900 is used to interconnect with the router.

l 1+1 APS protection: One protection group has one work channel and one protectionchannel. The switchover is performed based on the APS protocol. In the normal state, thework channel is working. If an APS switchover event is detected by the work channel, theservices are switched to the protection channel. In this mode, the interconnected devicemust also support the APS protocol. This mode applies when the SDH/SONET interfaceis used to interconnected with the SDH device.

l 1:N APS protection: One protection group has N work channels and one protection channel.The switchover is performed based on the APS protocol. In the normal state, N workchannels are working. If an APS switchover event is detected by one work channel, theservices are switched to the protection channel. The APS protection requires theinterconnected device to support the APS protocol. This mode applies when the SDH/SONET interface are used to interconnect with the SDH device.

Interface protection uses the linear multiplex section protection mode. The working principlesof 1+1 backup and 1:N backup are described as follows.


Configuration Guide


Issue 02 (2008-05-07)

Figure 3-22 shows SDH/SONET interface protection in 1+1 backup mode.

Figure 3-22 1+1 backup

A B

Work channel

Protection channel

Work channel

Protection channel

In 1+1 backup mode, each work channel has a corresponding protection channel. The sendersends signals through both work and protection channels, and the receiver receives the signalswith good quality irrespective of whether they are from work or protection channels.

According to switch mode, 1+1 backup falls into the following categories, namely, unidirectionalnon-recover, unidirectional recover, bidirectional non-recover, and bidirectional recover.

l Unidirectional means the switchover is initiated by one end only, according to the linequality, without negotiation with the peer end.

l Bidirectional means the switchover starts at the two ends simultaneously after negotiationbetween them.

l Recover means the original work channel will be enabled again when recovered from failedstate.

l Non-recover means the protection channel still work even when the original work channelis recovered.

In unidirectional 1+1 backup mode, the receiver chooses to receive signals through work orprotection channels according to line quality. In bidirectional 1+1 backup mode, based on theautomatic protect switch (APS) protocol, the two ends exchange K bytes that carry statusinformation of links between the receiver and sender, and decide whether to enable channelswitch. In this case, K bytes are transported through protection channels.

Figure 3-23 shows the work mode of 1:N linear multiplex section protection.



3-43

Figure 3-23 1:N linear multiplex section protection

A B

Birdge Selector BirdgeSelector

Protection channel (send)Protection channel (receive)

Work channel 1 (send)

Work channel 1 (receive)

Work channel 2 (send)Work channel 2 (receive)

Work channel N (send)

Work channel N (receive)

Different from 1+1 backup mode, multiple work channels share one dedicated protection channelin 1:N backup mode. In the normal state, work channels carry signals. In the event of workchannels failure, the sender will turn to the protection channel to send signals.

1:N backup protect functions only in bidirectional recover mode. It also works based on APSprotocol, and K bytes are transported through protection channels.

3.8 UAM Background InformationThis describes the background information of the user access module (UAM).

When the UMG8900 acts as an access gateway (AG) or a next generation network (NGN)-enabled switch to connect public switched telephone network (PSTN) and integrated servicesdigital network (ISDN) subscribers, the UAM must be configured. In this case, the UMG8900consists of the UAM and the service switching module (SSM). Figure 3-24 shows thenetworking application.


Configuration Guide


Issue 02 (2008-05-07)

Figure 3-24 UMG8900 connecting subscribers directly

SSM

Main frame Directframe

RSA mainframe

MGC

UMG8900

Subframe RSAsubframeUAM

PSTN/ISDN User

3.8.1 UA Frame TypesThis describes the types of user access (UA) frames.

3.8.2 UA Frame ModesThis describes the modes that the user access (UA) frames can be configured in.

3.8.3 Conversion Between the TID and the Subscriber Line PortThis describes the conversion between the termination identifier (TID) and the subscriber lineport.

3.8.4 Method to Number E1 Interfaces on the PV8/RSU by Mapping Them to E1 Cables on theSSM SideThis describes the method to number E1 interfaces on the PV8/RSU by mapping them to E1cables on the service switching module (SSM) side.

3.8.5 Method to Number E1 Interfaces on the RSP by Mapping Them to E1 Cables on the SSMSideThis describes the method to number E1 interfaces on the RSP by mapping them to E1 cableson the service switching module (SSM) side.

3.8.1 UA Frame TypesThis describes the types of user access (UA) frames.

UA Frame Types

The frame type determines the frame dimensions, supported boards, and slot positions. The useraccess module (UAM) supports frames such as RSP_10, RSP_12, RSP_14, RSP_15, RSP_19,



3-45

UAM, UAS, UAFM, UAFS, HABA_UP, HABB_UP, HABD, HABE, HABF, HABL,RSP_160B, RSA_22, RSA_26, RSB, RSB_HK, USR_16, and USR_19.

You can distinguish the UA frames of different types based on the backplanes. Refer to Table3-15.

Table 3-15 Mapping between UA frame types and backplanes

No. Frame Type Backplane Remarks

1 UAFM HUBE For the two frame types, the backplane modelis often invisible. The two types of frames,however, differ from other types of frames inthat the cabling area is at the top rather thanat the back. The E1 interface of the UAFMframe is identified as PV8 E1, and the E1interface of the UAFS frame is identified asRSP E1.

2 UAFS HUBF

3 UAM HUBM -

4 UAS HUBS -

5 HABA_UP HABA The HABA_UP and HABA_DOWN framesshare one backplane. The HABA_UP frameis on the upper half, and the HABA_DOWNis on the lower half.

6 HABB_UP HABB The HABB_UP and HABB_DOWN framesshare one backplane. The HABB_UP frameis on the upper half, and the HABB_DOWNis on the lower half.

7 HABD HABD The backplane models of these four types offrames are often invisible. The four types offrames, however, differ from other types offrames in that the cabling area is at the bottomrather than at the back. The HABD frame canprovide up to 12 subscriber boards, theHABE frame can provide up to 14 subscriberboards, the HABF frame can provide up to18 subscriber boards, and the HABL canprovide up to 6 subscriber boards.

8 HABE HABE

9 HABF HABF

10 HABL HABL

11 RSP160B HLB -

12 RSP_10 HGB -

13 RSP_12 HFB -

14 RSP_14 HIB -

15 RSP_15 HDB -

16 RSP_19 HCB -


Configuration Guide


Issue 02 (2008-05-07)

No. Frame Type Backplane Remarks

17 RSA_22/RSA_26

RUB The two types of RSA frames providedifferent numbers of slots. The RSA_22frame provides 22 slots, and the RSA_26frame provides 26 slots.

18 RSB RSB -

19 RSB_HK RMB -

20 USR_16 SLB The backplane of the two types of subscriberframes is the SLB. You can distinguish thetwo subscriber frames based on the numberof slots on the ASL. The USR_16 frameprovides 16 ASL slots, and the USR_19frame provides 19 ASL slots.

21 USR_19 SLB

22 RSP_60A - This type of frame adopts the front cablingmode. It provides three slots with one for theRSP and the other two for the subscriberboards.

Frames such as the RSP_10 and the RSP_12 support two types of main control boards: PV8 andRSP. If the PV8 is installed, the subframe can be configured. If the RSP is installed, no subframecan be configured. In actual applications, a frame inserted with the PV8 is called a PV8 frame,and that inserted with the RSP is called an RSP frame.

The HABA, HABB, HABD, HABE, HABF, and HABL frames are called high-density frames.Other frames are called low-density frames.

3.8.2 UA Frame ModesThis describes the modes that the user access (UA) frames can be configured in.

UA Frame ModesThe frame mode determines the connections between the UA frames and the service switching(SSM) frames, and between the UA frames. Setting correct frame modes is important in addingUA frames.

Table 3-16 lists the five modes of the UA frames.



3-47

Table 3-16 UA frame modes

No. Frame Mode Description

1 Main frame The main frame connects directly with the SSM frame andcan attach subframes. Its main control board is the PV8, PV4,RSU8, or RSU4.The frames that can be configured as main frames include theUAFM, UAM, HABA_UP, HABD, HABL, RSP_10, andRSP_12.

2 Subframe The subframe connects directly with a main frame and cannotattach subframes. The main control board in the subframe ofa low-density UA frame is the RSP. No main control boardis installed in the subframe of a high-density UA frame.The frames that can be configured as subframes include theUAFS, UAS, HABA_UP, HABA_DOWN, HABB_UP,HABB_DOWN, HABE, HABF, RSP_10, RSP_12, RSP_14,RSP_15, and RSP_19.

3 Direct frame The direct frame connects directly with the SSM frame andcannot attach subframes. Its main control board is the RSP orRSA. The main control board of the RSB and RSB_HKframes is the RSA.The frames that can be configured as direct frames includethe UAFM, UAFS, UAM, UAS, RSP_10, RSP_12, RSP_14,RSP_15, RSP_19, RSP_60A, RSP_160B, RSB, andRSB_HK.

4 RSA main frame The RSA main frame connects directly with the SSM frameand can attach RSA subframes. Its main control board is theRSA.Only the RSA_22 and RSA_26 frames can be configured asthe RSA main frame.

5 RSA subframe The RSA subframe connects directly with the RSA mainframe and cannot attach subframe. Its main control board isthe DRV.Only the USR_16 and USR_19 frames can be configured asthe RSA subframe.

NOTE

As described previously, certain frames such as the RSP_10 and the RSP_12 can be configured as eithermain frames or subframes. When being configured as a main frame, the frame is inserted with the PV8/PV4. When being configured as a subframe, the frame is inserted with the RSP.

3.8.3 Conversion Between the TID and the Subscriber Line PortThis describes the conversion between the termination identifier (TID) and the subscriber lineport.

When the UMG8900 connects subscribers directly, it allocates a TID for each subscriber line.This TID is calculated based on the UA frame No., slot No., and port No. It is unchangeable.


Configuration Guide


Issue 02 (2008-05-07)

The TID of each subscriber line maps a telephone number. These telephone numbers areoperation resources, and are allocated and controlled by the media gateway controller (MGC).

The UMG8900 provides the following man-machine language (MML) commands for theconversion:

l LST UAPOS to query information about the subscriber line port based on a TID

l LST UATID to query the TID through based on the information of a subscriber line port

If the subscriber number on the MGC is configured with ADD VSBR or ADB VSBR, the TIDof the subscriber line port must be specified. You can run LST UATID on the UMG8900 toquery the TID of the subscriber line port.

%%LST UATID:;%%RETCODE = 0 accomplished

UA terminal TID--------------- Frame No. Slot No. TID(Hex) TID(Dec) TID_low23bit(Hex) TID_low23bit(Dec)

0 3 <40800060H-4080007FH> <1082130528-1082130559> <00000060H-0000007FH> <0000000096-0000000127> 0 4 <40800080H-4080009FH> <1082130560-1082130591> <00000080H-0000009FH> <0000000128-0000000159> 0 5 <408000A0H-408000BFH> <1082130592-1082130623> <000000A0H-000000BFH> <0000000160-0000000191> 0 6 <408000C0H-408000DFH> <1082130624-1082130655> <000000C0H-000000DFH> <0000000192-0000000223> 0 7 <408000E0H-408000FFH> <1082130656-1082130687> <000000E0H-000000FFH> <0000000224-0000000255> 0 11 <40800160H-4080017FH> <1082130784-1082130815> <00000160H-0000017FH> <0000000352-0000000383> 0 12 <40800180H-4080019FH> <1082130816-1082130847> <00000180H-0000019FH> <0000000384-0000000415> 0 13 <408001A0H-408001BFH> <1082130848-1082130879> <000001A0H-000001BFH> <0000000416-0000000447> 0 14 <408001C0H-408001DFH> <1082130880-1082130911> <000001C0H-000001DFH> <0000000448-0000000479> 0 15 <408001E0H-408001FFH> <1082130912-1082130943> <000001E0H-000001FFH> <0000000480-0000000511>(Number of results = 10)

--- END

In the query result, you need to pay attention to only TID_low23bit(Dec). Set TerminationID in ADD VSBR or Start MG termination ID in ADB VSBR of the MGC to the TID inTID_low23bit(Dec). Do not fill in 0 on the left of the query result. For example, for a queryresult of 0000000511, only 511 needs to be typed on the MGC.

Take the A32 in slot 3 of UA frame 0 as an example. Based on the preceding querying result,the TIDs of the 32 subscriber line ports range from 96 to 127. If the number of the subscriberline ports on the A32 is configured on the MGC, Termination ID ranges from 96 to 127.

3.8.4 Method to Number E1 Interfaces on the PV8/RSU by MappingThem to E1 Cables on the SSM Side

This describes the method to number E1 interfaces on the PV8/RSU by mapping them to E1cables on the service switching module (SSM) side.

1. Signaling between the user access module (UAM) and the SSM is transmitted throughtimeslot 16 on E1 interface 1. Thus, you must confirm the pair of E1 cables on the SSM



3-49

side that maps E1 interface 1 on the PV8/RSU. The PV8/RSU can run properly only afteryou run ADD UACFG to set the parameters including First trunk board No. and Firstport No. correctly.The procedure for confirming the mapping is as follows. Disconnect the connectionbetween the digital distribution frame (DDF) on the SSM side and the UAM, loop eachpair of E1 cables on the UAM side, and check the state of E1S indicator on the panel of thePV8/RSU. The E1 cable pair that lightens the E1S indicator maps E1 interface 1 on thePV8/RSU. Write down the board No. and the port No. of the E32 connected with this E1pair on the SSM side.

2. After confirming the pair of E1 cables that maps E1 interface 1 on the PV8/RSU, run ADDUACFG to configure the trunk connections between the SSM and the UAM.Set First trunk board No. and First port No. in ADD UACFG to the board No. and theport No. of the E32 noted in 1. Do not set the parameters Second trunk board No. toEighth trunk board No.. Then, you can see from Device Panel on the local maintenanceterminal (LMT) that the PV8/RSU runs properly.

3. After confirming that the PV8/RSU runs properly, confirm the mapping between other E1cables on the SSM side and E1 ports on the PV8/RSU. For the 4-bit dual-in-line package(DIP) switch on the panel of the PV8/RSU, bits are numbered 1 to 4 from the bottom upby the front view. Bits 1, 2, and 3 identify the E1 cable that the E1S indicator indicates thestatus for.The meaning of combinations of bits 3, 2, and 1 is as follows. The value 0 indicates OFF,and 1 indicates ON. The ON status is marked on the DIP switch.000: indicates E1 interface 1. It is the default value of DIP switches. That is why E1 interface1 is identified through the E1S indicator in 1.001: indicates E1 interface 2.010: indicates E1 interface 3.011: indicates E1 interface 4.100: indicates E1 interface 5.101: indicates E1 interface 6.110: indicates E1 interface 7.111: indicates E1 interface 8.Set the DIP switch on the PV8/RSU to related combinations, and perform loopback testson E1 cable pairs on the SSM side based on the method described in 1. Check the status ofE1S indicator to confirm the E1 cable pairs related to each of E1 interfaces 2 to 8 on thePV8/RSU. Write down the board Nos. and the port Nos. of the E32s connected with eachE1 cable pair.

4. Run RMV UACFG to delete the trunk connections between the SSM and the UAM.5. Run ADD UACFG to configure the trunk connections between the SSM and the UAM.

Set First trunk board No. through Eighth trunk board No. to the board Nos. of the E32sand First port No. through Eighth port No. to the port Nos. of the E32s noted in 1 and3.Then, you can see from Device Panel that the PV8/RSU runs properly. By now, configuringtrunk connections between the SSM and the UAM is complete.


Configuration Guide


Issue 02 (2008-05-07)

3.8.5 Method to Number E1 Interfaces on the RSP by MappingThem to E1 Cables on the SSM Side

This describes the method to number E1 interfaces on the RSP by mapping them to E1 cableson the service switching module (SSM) side.

1. Indicators E11 to E14 on the panel of the RSP respectively indicate the status of E1interfaces 1 to 4. On the digital distribution frame (DDF) on the SSM side, disconnect theconnection to the user access module (UAM), perform loopback tests on E1 cable pairs tothe UAM side one by one, and check whether indicators E11 to E14 on the panel of theRSP are on. If an indicator is on after loopback, the related E1 cable pair maps thecorresponding E1 interface on the RSP. Write down the board Nos. and the port Nos. ofthe E32s connected with E1 cable pairs on the SSM side.

2. Run ADD UACFG to configure the trunk connections between the SSM and the UAM.Set First trunk board No. through Fourth trunk board No. to the board Nos. of the E32sand First port No. through Fourth port No. to the port Nos. of the E32s noted in 1. Then,you can see from Device Panel that the RSP runs properly. Be now, configuring trunkconnections between the RSP and the SSM is complete.

3.9 Route BackupThis describes the concept and cautions of route backup.

When the route backup relationship is configured for the two Internet Protocol (IP) interfaces,if the interface or link where the master IP address is located is faulty, IP packets that take thismaster IP address as their source IP address can be sent through the interface where the slave IPaddress is located. These IP packets include service packets and control packets. Route backupin different networking is described as follows.

As shown in Figure 3-25, supposing IP addresses of IP0 and IP1 are in different networksegments and route backup is configured, when the master link is normal, packets with IP0 asthe source IP address are sent by the master interface IP0, and the master IP0 interface andbackup interface IP1 can receive the packets with IP0 as the destination address; when the masterlinks are faulty, packets with IP0 as the source IP address are sent by the backup interface, andthose with IP0 as the destination address are received by the backup interface IP1.

Figure 3-25 Route backup of IP addresses in different network segments

GW0HRB

GW1

IP0 IP2

IP3IP1

HRBIP0 IP2

IP3IP1

The master link is normal.

The master link is faulty.

Master

Slave

Master

Slave

GW0

GW1



3-51

When IP0 and IP1 are in the same network segment, there are two networking modes. Refer toFigure 3-26. In this networking mode, normally, packets with IP0 as the source IP address aresent by IP0; when IP0 is faulty, they are sent by backup interface IP1. When receiving packets,based on the received ARP response packets, the MGW resolves the MAC addresscorresponding to the main IP address of the UMG8900, and then decides to send the IP packetswith IP0 as the destination address to the master interface or the backup interface. When themaster and slave interfaces are in the same LAN, only the links between the UMG8900 andswitch can be protected. Thus, the master and slave interfaces are often configured in differentLANs.

Figure 3-26 Route backup of IP addresses in the same network segment

LSW

IP0 IP2

IP3IP1

IP0 IP2

IP3IP1

Master

Slave

Master

Slave

The master and slave interfaces are not inthe same LAN.

The master and slave interfacesare in the same LAN.

HRB

HRB

GW

GW0

GW1

Note the following when configuring the route backup:

l Only IP interfaces supporting independent interface numbering support the route backup,for example, the gigabit Ethernet (GE) interface of the HRU.

l The master and slave IP addresses must be configured on different interfaces of the sameHRB (that is, the master and slave HRBs with the same board No.), and belong to the sameIP domain.

l If the IP addresses of the master and slave interfaces belong to different network segments,the MGW interconnected with the slave interface must have a route to the segment that themaster interface is located in.

l The route backup relationship of IP addresses is unidirectional. If you want to back up theroute reversely, you must configure another backup relationship.

l It is recommended to configure route backup for all or none of the IP addresses of aninterface.

Note that both the master IP interface and the slave IP interface support the virtual local areanetwork (VLAN), or neither of them supports the VLAN. When both the master and slave IPinterfaces support the VLAN, VLAN IDs can be different. However, the interfaces of the peerdevice connected with these two IP interfaces must support the VLAN mixed mode. That is, theinterfaces of the peer device can receive and send packets of two VLANs at the same time.


Configuration Guide


Issue 02 (2008-05-07)

4 General Planning of Examples

This describes the general planning of examples in each part of the document.

For the data planning, see Figure 4-1. All the combined examples constitutes an entireconfiguration example.

Figure 4-1 Networking example

IP network

MasterMGC

SlaveMGC

R2SPC: aaaaaa

SPC: dddddd

DNS server IP address: 10.1.200.1

NMS IP address: 100.10.1.1/24

TDM

SPC: aaaaaa

PSTN switch

PBX userUA

V5 accessdevice

TDM

PBX

PRA

SCTP port No. to the master MGC: 3333

SCTP port No. to the master MGC(M2UA): 2000

SCTP port No. to the slave MGC: 2222

SCTP port No. to the slave MGC(M2UA): 3000

SCTP port No. to the master MGC(IUA): 2010

SCTP port No. to the slave MGC(IUA): 3010

SCTP port No. to the master MGC(M3UA): 4000

SCTP port No. to the slave MGC(M3UA): 5000E8T IP address: 10.1.1.10~10.1.1.14E1G IP address: 10.1.1.50~10.1.1.51

SPF(MIR) IP address: 10.1.1.2PPU board IP address: 10.1.1.3

OMC interface in the main control frame IPaddress: 10.1.1.1

Mc interface IP address: 10.1.1.4OMC interface in the central switchingframe IP address: 10.1.1.5OMC interface in the first service frame IPaddress: 10.1.1.6

SPC: bbbbbb SPC: bbbbbbIP address: 192.168.0.1/24

Router IP address: 10.1.1.254/24

H.248 SCTP Port No.: 3333 H248 SCTP Port No.: 2222L2UA SCTP Port No.: 2000

MTP3-M3UA SCTP Port No.: 4000L2UA SCTP Port No.: 3000MTP3-M3UA SCTP Port No.: 5000

MGW IP address: 10.1.1.200

IP address: 172.16.0.1/24

V5UA SCTP Port No.: 2020 V5UA SCTP Port No.: 3020

SCTP port No. to the master MGC(V5UA): 2020

SCTP port No. to the slave MGC(V5UA):3020

IUA SCTP Port No.: 2010 IUA SCTP Port No.: 3010

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 4 General Planning of Examples


4-1

5 Configuring System Parameters

This describes how to configure the system parameters, including the system name, version loadserver information, local information, and environmental monitoring parameters.

Prerequisitel Hardware installation is complete.

l Software installation is complete.

Data Planningl Table 5-1 lists the data needed in this step. The interconnected device column in the table

indicates whether the parameter needs to negotiate with the interconnected parameter. Ifnot, "-" is filled in.

Table 5-1 Data planning

Parameter Name UMG8900

IP address of the version server <IP Address of Version Server>

User name of the version server <User Name of Version Server>

Password of the version server <Password of Version Server>

System Node No. <System Node No.>

National signaling point code 1 <National network code>_1

Coding length <National network structure>

Local signaling point index <OPC index>


Upper limit of the input voltagealarm (V)

<Upper Limit of the Input Voltage Alarm (V)>

Lower limit of the input voltagealarm (V)

<Lower Limit of the Input Voltage Alarm (V)>

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 5 Configuring System Parameters


5-1


Upper limit of the environmenttemperature alarm (C)

<Upper Limit of the Environment TemperatureAlarm (C)>

Lower limit of the environmenttemperature alarm (C)

<Lower Limit of the Environment TemperatureAlarm (C)>

Upper limit of the environmenttemperature alarm (F)

<Upper Limit of the Environment TemperatureAlarm (F)>

Lower limit of the environmenttemperature alarm (F)

<Lower Limit of the Environment TemperatureAlarm (F)>

Cabinet No. <Cabinet No.>

Buzzer switch <Switch>

Frame No. <Frame No.>

Port No. of the environmentalalarm chest

<Port No.>

Alarm ID <Alarm ID>

Digital port alarm voltage <Digital Port Alarm Voltage>

Alarm name <Alarm Name>

Alarm level <Alarm Level>

Net management type <Net Management Type>

l Table 5-2 lists the parameters output to other steps.

Table 5-2 Output parameter

Parameter Name Data

Local signaling point code 1 <National network code>_1

Local signaling point code 2 <National network code>_2


NOTE

l If the local office provides one signaling point, local signaling point code 1 is provided.

l If the local office provides multiple signaling points, local signaling point code 2 is provided.

Procedure

Step 1 Run MOD SYSINFO to modify the configuration information of the system.

5 Configuring System ParametersHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

MOD SYSINFO: SYSN="AUMG89001", FTPIP=<IP Address of Version Server>,FTPUN=<User Name of Version Server>, PWD=<Password of Version Server>,SNN=<System Node No.>, SNM="AUMG89001";

NOTE

Name systems according the naming specifications. A system name can be composed of the area namefollowed by equipment name and equipment serial No. Consider the name AUMG89001 as an example,where, A stands for the area, 1 stands for the equipment serial No., and UMG8900 stands for the equipmentUMG8900.

Step 2 Run SET OFI to configure the local information. Set National network valid to YES, Firstsearch network to National, and STP function to YES.SET OFI: NAME="AUMG89001", INTVLD=NO, INTRESVLD=NO, NATVLD=YES,NATRESVLD=NO, SERACH0=NAT, NATOPC=<National network code>_1,NATLEN=<National network structure>, STPFLAG=YES;

The UMG8900 provides the function of multiple signaling points. After setting the localinformation, if multiple signaling points are required, run ADD OFI to add the information ofthe original signaling point. The index of the local signaling points range from 1 to 15. The localsignaling point whose index is 0 is configured with the SET OFI command.

ADD OFI: INDEX=<OPC index>, NATOPC=<National network code>_2;

Step 3 Run SET ENVTHD to set the environmental configuration parameter of the power distributionframe.l Set Metrology to Metric.

SET ENVTHD: VOLTH=<Upper Limit of the Input Voltage Alarm (V)>,VOLTL=<Lower Limit of the Input Voltage Alarm (V)>, MTRLGY=MET,MTEMH=<Upper Limit of the Environment Temperature Alarm (C)>,MTEML=<Lower Limit of the Environment Temperature Alarm (C)>;

l Set Metrology to Imperial.SET ENVTHD: VOLTH=<Upper Limit of the Input Voltage Alarm (V)>,VOLTL=<Lower Limit of the Input Voltage Alarm (V)>, MTRLGY=IMP,ITEMH=<Upper Limit of the Environment Temperature Alarm (F)>, ITEML=<LowerLimit of the Environment Temperature Alarm (F)>;

Step 4 Run SET BUZZER to enable or disable the buzzer of the power distribution frame.SET BUZZER: SHF=<Cabinet No.>, SWITCH=<Switch>;

Step 5 Run SET ALMPORT to set the input port of the environmental signaling of the environmentalalarm chest. Set Port Switch to On and Port Type to Digital.SET ALMPORT: FN=<Frame No.>, PN=<Port No.>, SW=ON, AID=<Alarm ID>,PT=BOOL, AVOL=<Digital Port Alarm Voltage>;

Step 6 Run SET ENVALMPARA to set the environmental alarm parameter of the environmentalalarm chest.SET ENVALMPARA: ALMID=<Alarm ID>, ANM=<Alarm Name>, ALVL=<AlarmLevel>, ASS=<Net Management Type>;

----End

ExampleExample script//Configure the system information. MOD SYSINFO: SYSN="ABUMG89001", FTPIP="user", FTPUN="UMG8900W";

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 5 Configuring System Parameters


5-3

//Configure the local information. SET OFI: NAME="AUMG89001", INTVLD=NO, INTRESVLD=NO, NATVLD=YES, NATRESVLD=NO, SERACH0=NAT, NATOPC=H'aaaaaa, NATLEN=LABEL24, STPFLAG=YES;//Set the environmental configuration parameter of the 48V power distribution frame. Set the upper limit of the input voltage to -59V, the lower limit of the input voltage to -40V, the metrology to the metric, the upper limit of the environmental temperature to 40℃, and the lower limit of the environmental temperature to 10 ℃.SET ENVTHD: VOLTH=-59, VOLTL=-40, MTRLGY=MET, MTEMH=40, MTEML=10;//Enable the buzzer switch of cabinet 0.SET BUZZER: SHF=0, SWITCH=ON;

//Set the input port of the environmental signal. SET ALMPORT: FN=0, PN=2, SW=ON, AID=65400, PT=BOOL, AVOL=LOW;

//Set the configuration parameter of the environmental alarm. SET ENVALMPARA: ALMID=65400, ANM="New alarm name", ALVL=Critical, ASS=env;

PostrequisiteAfter configuring the system parameter, proceed with other configurations.

Configuring System Time

5 Configuring System ParametersHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

6 Configuring System Time

This describes how to configure the system time including how to set the time synchronizationmode and how to manually set the time, time zone, Network Time Protocol (NTP) server, anddaylight saving time (DST).

Prerequisitel The hardware installation is complete.

l The software installation is complete.

ContextThis contains the configuration and correction of the UMG8900 host time. Logs, alarms,performance and trace information contain time parameters. Correct time information helps youto specify the time when an error occurs.

When starting, the UMG8900 obtains the current system time from the RTC (the hard clock thatkeeps timing on the battery power after the system shuts down). This time is not accurate. Youcan adjust it in the following three methods:

l Setting the system time manuallyIn this manner, the accuracy of time can only reach the scale of second and cannot meethigher requirements.

l Adjusting time according to the global positioning system (GPS) reference sourceThe CLK adjusts the local time to the satellite time signals from the GPS. In this manner,the system can keep accurate time but it is expensive.

l Adjusting the time according to the NTP server through the NTP protocol

Configuration ProceduresIn the preceding three methods, steps for configuring the system time are different. Refer toFigure 6-1.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 6 Configuring System Time


6-1

Figure 6-1 Steps for configuring the host time

Configure the system time

Configure the systemtime manually Configure the time zone Configure the time zone

Configure the NTP server

End

RTC

NTP

GPSConfigure the timesynchronization mode?




Parameter Name UMG8900 InterconnectedDevice (NTP Server)

Date <Date> -

Time <Time> -

Adjust value (s) <Adjust value(s)> -

Daylight saving time <Daylight saving time> -

Time zone <Time zone> -

Start date mode <Start date mod> -

Start month <Start month> -

Start date <Start date> -

Start week <Start week> -

Start time <Start time> -

End date mode <End date mode> -

End month <End month> -

End date <End date> -

6 Configuring System TimeHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

Parameter Name UMG8900 InterconnectedDevice (NTP Server)

End week <End week> -

End time <End time> -

Time offset (minute) <Time offset(minute)> -

IP address of the NTPserver

The same as that of the peerdevice

<NTP IP Address>

Whether to authenticatethe ID

<Authentication> -

Authentication key ID <Authentication key ID> -

Authentication key <Authentication key> -

Version The same as that of the peerdevice

<NTP Version>

Prefer <Prefer> -

Procedure

Step 1 Run SET TIMESYC to set the synchronization mode of the local system time. The timesynchronization mode can be GPS, NTP, or RTC.l RTC mode: The system time does not synchronize with an external source but fully depends

on the RTC clock. Then, perform Step 2.SET TIMESYC: INFO=RTC;

l Global positioning system (GPS) mode: GPS satellite signals are obtained to synchronizethe local system time, and perform Step 3.SET TIMESYC: INFO=GPS;

l Network Time Protocol (NTP) mode: The NTP is used to synchronize the time with theNTP server through the network. Then, perform Step 3 to Step 4.SET TIMESYC: INFO=NTP;

Step 2 When the standard time cannot be obtained from the GPS, you can manually set the system time.Run SET TIME to set the host time. Dates are expressed in yyyy&mm&dd and time is expressedin hh&mm&ss.l Set Set Type to Set Time.

SET TIME: ST=SETTIME, DATE=<Date>, TIME=<Time>, DST=<Daylight savingtime>;

l Set Set Type to Adjust Time.SET TIME: ST=ADJUST, SEC=<Adjust value(s)>;

Step 3 Run SET TZ to set the time zone and the daylight saving time.l Set Daylight saving time flag to NO.

SET TZ: ZONET=<Time zone>, DST=NO;

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 6 Configuring System Time


6-3

l Set Daylight saving time flag to YES.SET TZ: ZONET=<Time zone>, DST=YES, SM=<Start date mod>, SMONTH=<Startmonth>, SDAY=<Start date>, SWEEK=<Start week>, ST=<Start time>, EM=<Enddate mode>, EMONTH=<End month>, EDAY=<End date>, EWEEK=<End week>,ET=<End time>, TO=<Time offset(minute)>;

Step 4 Run ADD NTPSRV to add the NTP server.ADD NTPSRV: IPADDR=<NTP IP Address>, AUTH=<Authentication>KID=<Authentication key ID> KEY=<Authentication key>, VER=<NTP Version>PREFER=<Prefer>;

----End

ExampleExample script//Configure the system time. Synchronize the host time with the NTP Server.SET TIMESYC: INFO=NTP;SET TZ: ZONET=GMT_0800, DST=NO;ADD NTPSRV: IPADDR="10.1.1.3", AUTH=NO, VER=3, PREFER=NO;

PostrequisiteAfter configuring the system time, configure NMS data.

Configuring NMS Data

6 Configuring System TimeHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

7 Configuring NMS Data

About This Chapter

This describes how to configure the interconnection data between the UMG8900 and the networkmanagement system (NMS), including the configurations of the NMS interface and SimpleNetwork Management Protocol (SNMP).

7.1 Configuring the NMS InterfaceThis describes how to configure the interface and route of the UMG8900 to the networkmanagement system (NMS).

7.2 Configuring SNMPThis describes the Simple Network Management Protocol (SNMP) data of the UMG8900 to thenetwork management system (NMS).

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 7 Configuring NMS Data


7-1

7.1 Configuring the NMS InterfaceThis describes how to configure the interface and route of the UMG8900 to the networkmanagement system (NMS).

Prerequisitel The system parameter and time information are correctly set.

l The hardware information is correctly set.

Background Information

Based on different networking plans, the NMS interface can be the following:

l the OMU interface: The OMC interface on the NET in the SSM-256 main control frame,or the OMC interface on the TNC in the main control frame.

l The MPU interface: the OMC interface on the NET in an SSM-256 frame other than themain control frame, or the OMC interface on the TNC in an SSM-32 service frame.

NOTE

In the software loading scripts, the OMU interfaces, that is, the OMC interfaces, in the main control frameare configured with IP addresses for software loading. Thus, if the OMU interface is used to receive andsend NMS packets, no more configurations are needed.

Table 7-1 lists the parameter configuration for the three types of interfaces when ADDIPADDR is used to set the IP address.

Table 7-1 Parameter configuration for the three types of interfaces

Parameter OMU Interface MPU Interface

Board type OMU MPU

Board No. 0The board No. of the MPU in frame 0 is 1. TheNos. of MPU boards in other frames are the sameas the Nos. of the frames they are located.

Interface type ETH ETH

Interface No. 0 0

NOTE

Run MOD IPIF to modify the auto negotiation parameters of the OMC interface such as the rate and duplexmode.

Index mapping of the configuration command parameters

Figure 7-1 shows the index mapping of the configuration command parameters.

7 Configuring NMS DataHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

Figure 7-1 Index Mapping of Configuration Command Parameters

ADD IPADDR

IPADDRMASK

ADD ROUTE

DSTIP

ADD IPFWD

DSTMASK

BTBN

BTBN

BTBN

IPADDR

Data Planningl Table 7-2 lists the parameter output to this step, and you need to fill in the parameter values

according to the output parameters of the input source.

Table 7-2 Input parameter

Parameter Name Data Input Source

Board type <Board type> 8 Configuring Frames andBoards

Board No. <Board No.> 8 Configuring Frames andBoards

l Table 7-3 lists the data needed in this step. The interconnected device column in the tableindicates whether the parameter needs to negotiate with the interconnected parameter. Ifnot, "-" is filled in.


Parameter Name UMG8900 InterconnectedDevice 1 (NMS)

InterconnectedDevice 2 (Router)

IP address of theNMS interface

<Interface IPaddress>

The same as that ofthe peer device

-

IP address and maskof the NMSinterface

<Interface IPaddress mask>


-

Master or slave flag <Master or slaveflag>

- -

In VLAN <In VLAN> - -



7-3



IP address of theNMS


<Destinationaddress>

-

IP address and maskof the NMS


<Destinationaddress mask>

-

IP address of therouter directlyconnected with theUMG8900


- <Next hopaddress>

Protocol type The same as that ofthe peer device

<Protocol type> -

Procedure

Step 1 Run ADD IPADDR to add the IP address to the NMS interface. Set Interface type to ETHbecause the OMC interface on the OMU/MPU serves as the NMS interface.ADD IPADDR: BT=<Board type>, BN=<Board No.>, IFT=ETH, IFN=0,IPADDR=<Interface IP address>, MASK=<Interface IP address mask>, FLAG=<Masteror slave flag>, INVLAN=<In VLAN>;

Step 2 Run ADD ROUTE to configure the static route to the LMT. Set Route type to NEXTHOP(Next hop).ADD ROUTE: BT=<Board type>, BN=<Board No.>, DSTIP=<Destination address>,DSTMASK=<Destination address mask>, RTTYPE=NEXTHOP, NEXTHOP=<Next hopaddress>;

Step 3 The OMU processes the NMS packets, and thus when the NMS interface is the MPU interface,configure the packet forwarding relationship between the OMU and the MPU interface. RunADD IPFWD to configure the packet forwarding relationship. The NMS packets are forwarded,and thus set Forwarded board type to OMU and Forwarded board No. to 0.ADD IPFWD: BT=OMU, BN=0, IP=<Interface IP address>, PROT=<Protocol type>;

----End

ExampleNetworking diagram

Figure 7-2 shows the typical networking.


Configuration Guide


Issue 02 (2008-05-07)

Figure 7-2 Networking diagram

NMS clientUMG8900

LMT

Local maintenance

NMS server

LAN

IP：10.1.1.1/24

IP：10.1.1.254/24

IP:100.10.1.1/24

Example script

//Configure the IP address of the NMS interface. ADD IPADDR: BT=OMU, BN=0, IFT=ETH, IFN=0, IPADDR="10.1.1.1", MASK="255.255.255.0", FLAG=SLAVE, INVLAN=NO;

//Add routes. ADD ROUTE: BT=OMU, BN=0, DSTIP="100.10.1.1", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";

PostrequisiteAfter configuring the NMS interface, configure the Simple Network Management Protocol(SNMP) data.

7.2 Configuring SNMP

7.2 Configuring SNMPThis describes the Simple Network Management Protocol (SNMP) data of the UMG8900 to thenetwork management system (NMS).

Prerequisitel The hardware data is correctly set.

l The NMS interface data is correctly set.

Background InformationSimple Network Management Protocol (SNMP), a proven industry standard, is widely used innetworks. Its purpose is to guarantee the transmission of management information between anytwo points. In this case, the network administrator can retrieve information at any node on thenetwork to achieve:

l Fault diagnosis



7-5

l Capacity planning

l Report generation

SNMP adopts a polling mechanism and offers a fundamental functional set. In addition, SNMPonly requires the unacknowledged transport layer protocol UDP; so it is widely supported by avariety of products.

Structurally, SNMP can be divided into NMS and Agent. In SNMPv3, NMS and Agent areuniformly called SNMP entity. Network management station (NMS) is a workstation runningthe client program, while Agent is the server software running on the network device.

To manage a network through SNMP, you must run the SNMP Agent on the managed device.The specific process is as follows:

1. The NMS sends a serial packet to the Agent.2. The Agent receives the serial packet through the UDP port 161.3. The Agent decodes, authenticates, and analyzes the packet to obtain the corresponding node

of the management variable in the MIB tree.4. The Agent obtains the value of the management variable from the relevant module to

generate a response packet.5. The Agent codes the response packet and sends it back to the NMS.6. The NMS outputs the result through the same processing.

In addition, if the device running the Agent is restarted (warm or cold), the Agent also sendsTrap messages to the NMS for reporting the events.

To uniquely identify a management variable in SNMP packets, SNMP uses a hierarchicalnaming convention to distinguish different managed objects. The hierarchical structure is like atree. Each node on the tree represents a managed object, which can be identified by a path fromthe root to the node. For example, the managed object B can be uniquely identified by a seriesof numbers {1.3.6.1}, as shown in Figure 7-3.

The numbers are Object Identifier of the managed object. Management Information Base (MIB)is a collection of standard variable definitions of the monitored network device. Its function isto describe the hierarchical structure of the managed object tree.

Figure 7-3 Structure of MIB tree

1

1 36 4

1 25 6

B

In the UMG8900, the SNMP Agent supports three SNMP versions:

l SNMPv1

l SNMPv2c

l SNMPv3

In the SNMP architecture, access control is to allow different users to have different accessauthorities to management information. The view-based access control model implements accesscontrol through associating users and a MIB view.


Configuration Guide


Issue 02 (2008-05-07)

NOTE

View-based access control is a component of SNMPv3. However, the UMG8900 provides the same accesscontrol method for SNMPv1/v2c users.

Figure 7-4 shows the access control mode based on view.

Figure 7-4 Access control based on view

MIB view MIB object 1User groupUser

Security mode

Securitu level

MIB object 2

MIB object n

include/exclude

v1/v2c/usm

v1/v2c/usm/any

auth/noauth/priv

In view-based access control mode, you first need to define a MIB view, and then define MIBobjects included and excluded by the MIB view. To avoid mapping a large number of users tothe MIB view, the mode adopts two-level mapping methods: It maps a user group to the MIBview, and then maps users to the user group. To guarantee the security, you can set the securitymode and security level for the above two mapping processes.

SNMP v1/v2c does not support the robust authentication and encryption and only uses acommunity name as the identity of a visitor. In this case, the Agent determines whether to allowthe access through identifying the community name.

Figure 7-5 shows the access control of SNMP v1/v2c.

Figure 7-5 Access control of SNMP v1/v2c

MIB view MIB object 1Community

MIB object 2

MIB object n

Access mode

RO/RWinclude/exclude

Consequently, for SNMP v1/v2c, you can set SNMP with users and a user group, or only witha community name.

In the UMG8900, the SNMP Agent supports three types of security modes: v1, v2c and usm.The three modes correspond to SNMPv1, SNMPv2c, and SNMPv3 respectively. That is, v1/v2c/usm security mode is adopted when v1/v2c/v3 users map to a user group. Similarly, v1/v2c/usm security mode is adopted when the v1/v2c/v3 user group maps to the MIB view. If a usergroup contains multiple types of users (such as both v1 and v3), the any security mode is adoptedwhen the user group maps to the MIB view.

The SNMP Agent supports three types of security levels: auth, noauth, and priv. The three levelsrepresent authentication without encryption, no authentication and encryption, and



7-7

authentication with encryption. For the v1, v2c or any security mode, its security level can onlybe noauth. To select auth or priv, you must set the security mode as usm.

Configuration ProcedureFigure 7-6 shows the steps for the SNMP configuration.

Figure 7-6 Steps for the SNMP configuration

Start

Configure the supported SNMP version

Add SNMP view information

Add SMNP views?

Add SNMP groups

Add SNMP users

Configure the host for receiving Trapmessages

Configure the type of Trap messages tobe reported

End

No

No

Yes

Yes

Visiting protocol is SNMPV3?

If SNMPv1 or SNMPv2c is used for communication between the NMS and the agent, theconfiguration steps can be simplified.

Figure 7-7 shows the simplified steps for the SNMPv1 and SNMPv2c configuration.


Configuration Guide


Issue 02 (2008-05-07)

Figure 7-7 Simplified steps for the SNMPv1/v2c configuration

Start

Configure the supported SNMPversion

Add SNMP view information

Add SNMP views?

Add an access community name

Configure the host for receiving Trapmessages

Configure the type of Trap messagesto be reported

End

No

Yes

Index Mapping of Configuration Command ParametersFigure 7-8 shows the index mapping of the configuration command parameters of the SNMP.



7-9

Figure 7-8 Index mapping of configuration command parameters

ADD SNMPVIEW

ADD SNMPGRPREADVIEW

NAMEOIDTREE

NAME

ADD SNMPCOMM

VIEWNAMECOMMNAME

ADD TRAPHOST

COMMNAME

IPADDRWRITEVIEWNOTIFYVIEW

ADD SNMPUSER

GRPNAME

USERNAME

v1/v2c

v3

SECMDL

SECMDL




Parameter Name UMG8900 Interconnected Device(NMS)

NMS version <Version No.> The same as that of the peerdevice

SNMP view name <View name> -

Mib object subtreeOID

<Mib object subtree OID> -

Operate type <Operate type> -

SNMP group name <Group Name> The same as that of the peerdevice

Security level <Security level> The same as that of the peerdevice

Read view name <Read View Name> -

Write view name <Write View Name> -

Notify view name <Notify View Name> -


Configuration Guide


Issue 02 (2008-05-07)

Parameter Name UMG8900 Interconnected Device(NMS)

SNMP user name <User Name> The same as that of the peerdevice

Authenticationprotocol

<Authentication Protocol> The same as that of the peerdevice

Authenticationpassword

<Authentication Password> The same as that of the peerdevice

Encryption protocol <Privacy Protocol> The same as that of the peerdevice

Encryptionpassword

<Privacy Password> The same as that of the peerdevice

SNMP group name <Community Name> The same as that of the peerdevice

Access mode <Access Mode> -

IP address of thehost receiving theSNMP notification


<Host Address>

Port No. <UDP Port No.> The same as that of the peerdevice

Trap type <Trap type> -

ProcedureStep 1 Run SET SNMPVER to set the supported SNMP version, including v1, v2c, and v3.

SET SNMPVER: VER=<Version No.>;

Step 2 Run ADD SNMPVIEW to add the SNMP view information.ADD SNMPVIEW: NAME =<View name>, OIDTREE =<Mib object subtree OID>,OPTYPE =<Operate type>;

Step 3 Run ADD SNMPGRP to add the SNMP user group. The configuration varies with SecurityModel. Security Model must be the same as that on the NMS.l Set Security Model to USM.

ADD SNMPGRP: NAME=<Group Name>, SECMDL=USM, SECLVL=<Securitylevel>, READVIEW=<Read View Name>, WRITEVIEW=<Write View Name>,NOTIFYVIEW=<Notify View Name>;

l Set Security Model to other values. For example, set Security Model to ANY.ADD SNMPGRP: NAME=<Group Name>, SECMDL=ANY, READVIEW=<ReadView Name>, WRITEVIEW=<Write View Name>, NOTIFYVIEW=<Notify ViewName>;

Step 4 Run ADD SNMPGRP to add the SNMP user. Security Model must be the same as that on theNMS.



7-11

l Set Security Model to USM.ADD SNMPUSER: USERNAME=<User Name>, GRPNAME=<Group Name>,SECMDL=USM, AUTHPRTL=<Authentication Protocol>,AUTHWORD=<Authentication Password>, PRIVPRTL=<Privacy Protocol>,PRIVWORD=<Privacy Password>;

l Set Security Model to other values. For example, set Security Model to V1.ADD SNMPUSER: USERNAME=<User Name>, GRPNAME=<Group Name>,SECMDL=V1;

Step 5 (Optional) Run ADD SNMPCOMM to add the access group name.ADD SNMPCOMM: COMMNAME=<Community Name>, VIEWNAME=<View name>,ACCESSMOD=<Access Mode>;

Step 6 Run ADD TRAPHOST to add the host receiving the SNMP notice.l When TRAP Packet Version is set to V3, Community name is user name in ADD

SNMPUSER.ADD TRAPHOST: IPADDR=<Host Address>, USERNAME=<User Name>,UDPPORT=<UDP Port No.>, VER=V3, SECLVL=<Security level>;

l When TRAP Packet Version is set to V1 or V2C, Community name is user name inADD SNMPUSER.ADD TRAPHOST: IPADDR=<Host Address>, COMMNAME=<CommunityName>, UDPPORT=<UDP Port No.>, VER=V1;

Step 7 Run SET SNMPTRAP to set the TRAP-related parameters.SET SNMPTRAP: TYPE=<Trap type>;

----End

ExampleExample script//Set the SNMP to support V3. SET SNMPVER: VER=V3-1;

//Add one piece of SNMP view public including 1.3.6.1 view information. ADD SNMPVIEW: NAME = "public", OIDTREE = "1.3.6.1", OPTYPE = Include;

//Add an SMNP group. ADD SNMPGRP: NAME="mgw" , SECMDL=USM, SECLVL=priv, READVIEW="View1";

//Add a new SNMP user. ADD SNMPUSER: USERNAME="public",GRPNAME="g1",SECMDL=V1;

//Add the community name as private. The community name has the write and read right, and the accessed MIB view is UMG8900view. ADD SNMPCOMM: COMMNAME="private", VIEWNAME="UMG8900view", ACCESSMOD=RO;

//Add the host receiving the SNMP notification. ADD TRAPHOST: IPADDR="10.110.10.10", COMMNAME="public", VER=V1;

//Set the TRAP packet type that the SNMP proxy reports. SET SNMPTRAP: TYPE=AUTHENTICATIONFAILURE-1;

PostrequisiteAfter the SNMP data is configured, configuring the MGW data is complete. Then, configureother data.


Configuration Guide


Issue 02 (2008-05-07)


This describes how to add frames and boards.

Prerequisite

The hardware installation and software installation are complete.

Context

You do not need to configure cabinets of the UMG8900 separately. By default, the system hasadded a cabinet (cabinet 0) and the main control frame in the middle of cabinet 0.

Pay attention to the following points in frame configuration:

l Service switching module (SSM) frame No. ranges from 0 to 29. It is decided by the 8-bitdial in-line package (DIP) switch on the transfer board on the back of the frame. Theconfigured frame No. must be the same with the No. decided by the DIP switch. Otherwise,loading software and data to the frame will fail.

l The main control frame is configured by default and its No. is fixed as 1. You cannot addor delete it.

l If the networking requires an independent central switching frame, its frame No. is 0. If noindependent central switching frame is configured, the main control frame serves as thecentral switching frame.

l The control frame is needed only for large capacity configuration. Its frame No. is 8.

l In SSM-256 self-cascading mode, each GE and TDM cascading optical port connects withthe corresponding one. That is, cascading optical ports 0, 1, 2, and 3 in the central switchingframe connect with cascading ports 0, 1, 2, and 3 in cascaded frames respectively.

l In SSM-32 self-cascading mode, service frames must be cascaded with the main controlframe through TDM optical port 0. TDM Port0 must be set to the same No. with the actualoptical port on the MTNC through which the service frame connects to the main controlframe.

l In SSM-256 and SSM-32 mixed cascading mode, SSM-32 frames must be cascaded withthe SSM-256 central switching frame through TDM optical port 0, and TDM Port0 mustbe set to the same No. with the actual optical port on the TNB/BLU through which theservice frame connects to the central switching frame.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 8 Configuring Frames and Boards


8-1

l In SSM-256 and SSM-32 mixed cascading mode, SSM-32 frames cascaded to one pair ofthe BLUs or the TNUs in the central switching frame must be numbered in an ascendingorder. The SSM-32 frame with the smallest frame No. is called a level-2 cascading frame.

l The FE cascading cable of the level-2 cascading frame is cascaded to the BLU/NET throughinterface FE3 on the MTNC, and then is cascaded to other SSM-32 frames throughinterfaces FE2, FE1, and FE0 in order.

l When the UG02MNET and the UG02MBLU.C are configured in the SSM-256 frame, thecentral switching frame is directly connected to service frames through interfacesFE1&FE2(UG02MNET)/FE1&FE2(UG02MBLU.C), and the level-2 cascading frame isnot used. When the central switching frame is cascaded with only one service frame,interface FE1 is used.

l For the GE cascading, if the SSM-32 frame is directly cascaded to the SSM-256 frame, theGE cascading slot No. of the central switching frame is not required to be configured.

Pay attention to the following when adding a board:

Table 8-1 Considerations in adding a board

Item Description

Limitation onfront and backboards

SSM-256

Front boards include the OMU, MPU, HRB, FLU, VPU,ECU, SPF, and MCMF in the CMU.Back boards include the NET, CLK, TNU, PPU, E8T,E1G, BLU, E32, T32, S2L, and MCMB in the CMU.

SSM-32

Front boards include the OMU, MPU, VPU, SPF andMCMF in the CMU.Back boards include the TNU, CLK, PPU, E32, HRB,T32, PIE, S1L, and MCMB in the CMU.

Limitation onoppositepositions

SSM-256FLU--BLUOMU/MPU--NETHRB--E8T/E1G/E32

SSM-32 OMU/MPU--TNU

Limitation onfixed positions SSM-256

The OMU can only be in front slots 7 and 8 in the maincontrol frame.The MPU can only be in front slots 7 and 8 in a frameexcept the main control frame.The NET can only be in back slots 7 and 8.The TNU can only be in back slots 6 and 9.The CLK can only be in back slots 0 and 1 in the mainframe.The FLU and BLU can only be in the central switchingframe.

8 Configuring Frames and BoardsHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

Item Description

SSM-32

The OMU (MOMB) can only be in front slots 6, 7, 8, and9 in the main control frame.The MPU (MMPB) can only be in front slots 6, 7, 8, and9 in a service frame.The TNU (MTNC) can only be in back slots 6, 7, 8, and9.The NLU (MNLU) can only be in back slots 4, 5, 10, and11.The CLK, if needed, can only be in back slots 0 and 1 inthe main control frame.

Limitation onconfiguration

SSM-256

When the MTNU/TCLU is installed in the SSM-256frame, the following boards can be used: UG01E32,UG01T32, UG01BLU, UG01FLU, UG02BLU,UG02FLU, and UG01SPF.When the MTNB is installed in the SSM-256 frame, thefollowing boards can be used: UG02E32, UG02T32,UG01ESU, UG01TSU, UG02BLU, UG02FLU, andUG02SPF.

SSM-32

Boards including the UG02E32, UG02T32, UG01ESU,and UG02SPF can be used in the SSM-32 frame.NOTE

Board matching limitation refers to the matching relationship ofboard types. Only configuration of some boards is involved. Fordetails, refer to Boards.

l Difference on appearance of UG01 and UG02 boards is thatsubscript a exists or no subscript exists on the name silkscreenof the front panel of the UG01 board, and subscript b exists onthat of the UG02 board.

l You can query board file information with LST BRDARCand obtain the board version information.

Defaultconfiguration

SSM-256

The OMU and NET in the main control frame and theMPU and NET in other frames are configured by default.You do not need to configure these boards and cannotdelete them.

SSM-32

The OMU and TNU in the main control frame and theTNU in service frames are configured by default.You do not need to configure these boards and cannotdelete them.



8-3

Item Description

Limitation onboard Nos.

All OMU, MPU, and CMU boards are numbered uniformly. Nos. for allOMU and MPU boards are generated automatically. The OMU board No.is 0. The MPU board in frame 0 is numbered 1. The board Nos. for otherMPUs are the same with the Nos. of the frames where they are located,ranging from 2 to 29. CMU boards are numbered from 30 to 61.The MTNB board No. must be the same with the No. of the frame where itis located.For a board in 1+1 backup mode, its board type and No. must be the samewith those of the board in the paired slot. For example, if an FLU board in1+1 backup mode is in slot 12, the board in slot 13 must also be FLU andthe Nos. of the two boards must be the same.NOTE

l Paired slots refer to slots 0 and 1, slots 2 and 3, slots 4 and 5, slots 6 and 9, slots 7and 8, slots 10 and 11, slots 12 and 13, as well as slots 14 and 15.

l You do not need to specify the master board in the two boards working in 1+1backup mode. When the system starts up, the master is determined through thecontention mechanism. The board that is often started first is the master and theother one the slave.

Work modes

The boards that can work in 1+1 backup mode only include the OMU, MPU,NET, CLK, TNU, CMU, HRB and BLU.The boards that can work in load-sharing mode only include the PPU, VPU,ECU, SPF, E32, T32, and NLU.The S1L, S2L, and PIE can work in either 1+1 backup or load-sharing mode.






Frame version <Frame Ver>

Cascading mode <FE Cascading Mode>

Cascading board No. <Cascading Board No.>

Configure GE cascade <Configure GE Cascade>

Local frame GE cascade slot No. <Local Frame GE Cascade Slot No.>

Up frame GE cascade slot No. <Up Frame GE Cascade Slot No.>

Up frame GE port No. <Up Frame GE Port No.>


Configuration Guide


Issue 02 (2008-05-07)


Configure TDM cascade <Configure TDM Cascade>

TDM cascadeport0 <TDM CascadePort0>



Frame position <Frame Position>

Frame name <Frame Name>

Frame description <Frame Description>

Slot No. <Slot No.>

Board position <Board Position>

Board type <Board type>

Backup type <Backup type>

Hardware type <Hardware type>

Board No. <Board No.>


Table 8-3 Output parameter

Parameter Name Data




Slot No. <Slot No.>


Procedure

Step 1 Run ADD FRM to add the frame. You can set Frame Type to Service Frame, CentralSwitching Frame, or Control Frame. By default, the main control frame is configured and theframe No. is 1.

l Set Frame Type to Central Switching Frame. The frame No. is always 0. In SSM-256and SSM-32 mixed cascading, the central switching frame must be an SSM-256 frame.

ADD FRM: FN=<Frame No.>, FV=<Frame Ver>, FT=SWITCH, SHF=<CabinetNo.>, LOC=<Frame Position>, FNM=<Frame Name>, FD=<Frame Description>;

l Set Frame Type to Control Frame. The frame No. is always 8.



8-5

ADD FRM: FN=<Frame No.>, FV=<Frame Ver>, FT=CONTROL, SHF=<CabinetNo.>, LOC=<Frame Position>, FNM=<Frame Name>, FD=<Frame Description>;

l Set Frame Type to Service Frame. If the UG01NET is configured in the central switchingframe, set FE Cascading Mode to Second Cascading Mode. If the UG02NET isconfigured in the central switching frame, set FE Cascading Mode to Direct CascadingModeSet Configure GE Cascadee to YES.ADD FRM: FN=<Frame No.>, FV=<Frame Ver>, FT=SERVICE, CM=<FECascading Mode>, CN=<Cascading Board No.>, GECAS=<Configure GE Cascade>,GELSN=<Local Frame GE Cascade Slot No.>, GESN=<Up Frame GE Cascade SlotNo.>, GEPN=<Up Frame GE Port No.>, TDMCAS=<Configure TDM Cascade>,TDMPORT0=<TDM CascadePort0>, TDMPORT1=<TDM CascadePort1>,SHF=<Cabinet No.>, LOC=<Frame Position>, FNM=<Frame Name>, FD=<FrameDescription>;

Step 2 Run ADD BRD to add boards. For precautions, refer to Table 8-1.ADD BRD: FN=<Frame No.>, SN=<Slot No.>, BP=<Board Position>, BT=<Board type>,BS=<Backup type>, HBT=<Hardware type>, BN=<Board No.>;

Step 3 If the main control board is the UG02OMB, run ADD OMUSUBRD to add the SCMU subboard.l If Board Type is CMU and Sub-Board No. is Sub-Board 0, run the following command:

ADD OMUSUBRD: FN=<Frame No.>, SN=<Slot No.>, SUBBN=SBRD0, BT=CMU,BN=<Board No.>;

l If Board Type is PPU and Sub-Board No. is Sub-Board 1, run the following command:ADD OMUSUBRD: FN=<Frame No.>, SN=<Slot No.>, SUBBN=SBRD1, BT=PPU,BN=<Board No.>;

----End

ExampleBoard layout

This example uses the SSM-256 and SSM-32 mixed cascading mode. Figure 8-1 shows theboard layout.


Configuration Guide


Issue 02 (2008-05-07)

Figure 8-1 Board layout of the UMG8900

00

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

SlotNo.

MNET

MNET

MTNB

MTNB

MainControlFrame

FrontBoard

BackBoard

MOMB

MOMB

MTNC

MTNC

MCMB

MCMB

MVPD

MVPD

MVPD

MVPD

MCMF

MCMF

FrontBoard

BackBoard

CentralSwitching

Frame

MCLK

MCLK

MMPU

MMPU

ME8T

ME8T

MHRU

MHRU

ME8T

ME8T

MHRU

MHRU

MMPB

MMPB

MTNC

MTNC

FrontBoard

BackBoard

ME32

ME32

MSPF

MSPF

MBLU

MBLU

MFLU

MFLU

ME32

ME32

ServiceFrame

Example script//The SSM-32 main control frame is configured by default. You do not need to configure it, and cannot add or delete it. //Add service frame and central switching frame: ADD FRM: FN=0, FV=SSM256, FT=SWITCH, SHF=0, LOC=MIDDLE, FNM="Central Switch", FD="Central Switch"; MOD FRM: FN=1, CM=SLAVECAS, CN=DIRECT, GECAS=NO, TDMCAS=YES, TDMPORT0=0, FNM="Main control frame", FD="Main control frame";ADD FRM: FN=2, FV=SSM32, FT=SERVICE, CM=SLAVECAS, CN=BLU0, GECAS=NO, TDMCAS=YES, TDMPORT0=0, SHF=0, LOC=TOP, FNM="Service Frame";//Add boards to the main control frame.ADD BRD: FN=1, SN=0, BP=FRONT, BT=VPU, ADS=ACTIVE, CPUB=90, CPUM=80, BS=LOADSHARE, HBT=VPD, BN=0;ADD BRD: FN=1, SN=1, BP=FRONT, BT=VPU, ADS=ACTIVE, CPUB=90, CPUM=80, BS=LOADSHARE, HBT=VPD, BN=1;ADD BRD: FN=1, SN=2, BP=FRONT, BT=VPU, ADS=ACTIVE, CPUB=90, CPUM=80, BS=LOADSHARE, HBT=VPD, BN=2;ADD BRD: FN=1, SN=3, BP=FRONT, BT=VPU, ADS=ACTIVE, CPUB=90, CPUM=80, BS=LOADSHARE, HBT=VPD, BN=3;ADD BRD: FN=1, SN=0, BP=BACK, BT=CLK, CPUB=90, CPUM=80, BS=ONEBACKUP, HBT=CLK, BN=0;ADD BRD: FN=1, SN=4, BP=BACK, BT=PPU, HBT=CMB, BS=LOADSHARE, BN=0, ADS=ACTIVE;ADD BRD: FN=1, SN=5, BP=BACK, BT=PPU, HBT=CMB, BS=LOADSHARE, BN=1, ADS=ACTIVE;



8-7

ADD BRD: FN=1, SN=4, BP=FRONT, BT=CMU, CPUB=90, CPUM=80, BS=ONEBACKUP, HBT=CMF, BN=30;ADD BRD: FN=1, SN=5, BP=FRONT, BT=CMU, CPUB=90, CPUM=80, BS=ONEBACKUP, HBT=CMF, BN=30;ADD BRD: FN=1, SN=12, BP=FRONT, BT=HRB, ADS=ACTIVE, CPUB=90, CPUM=80, BS=ONEBACKUP, HBT=HRU, BN=0;ADD BRD: FN=1, SN=14, BP=FRONT, BT=HRB, ADS=ACTIVE, CPUB=90, CPUM=80, BS=ONEBACKUP, HBT=HRU, BN=1;ADD BRD: FN=1, SN=12, BP=BACK, BT=E8T, ADS=ACTIVE, CPUB=90, CPUM=80, BS=NULLBACKUP, HBT=E8T, BN=0;ADD BRD: FN=1, SN=13, BP=BACK, BT=E8T, ADS=ACTIVE, CPUB=90, CPUM=80, BS=NULLBACKUP, HBT=E8T, BN=1;ADD BRD: FN=1, SN=14, BP=BACK, BT=E8T, ADS=ACTIVE, CPUB=90, CPUM=80, BS=NULLBACKUP, HBT=E8T, BN=2;ADD BRD: FN=1, SN=15, BP=BACK, BT=E8T, ADS=ACTIVE, CPUB=90, CPUM=80, BS=NULLBACKUP, HBT=E8T, BN=3;//Add the SCMU subboard.ADD OMUSUBRD: FN=1, SN=7, SUBBN=SBRD0, BT=CMU, BS=ONEBACKUP, BN=30; ADD OMUSUBRD: FN=1, SN=7, SUBBN=SBRD1, BT=PPU, BS=LOADSHARE, BN=1; ADD OMUSUBRD: FN=1, SN=8, SUBBN=SBRD1, BT=PPU, BS=LOADSHARE, BN=2;//Configure the board of central switching frame.ADD BRD: FN=0, SN=6, BP=BACK, BT=TNU, CPUB=90, CPUM=80, BS=ONEBACKUP, HBT=TNB, BN=0;ADD BRD: FN=0, SN=0, BP=FRONT, BT=FLU, CPUB=90, CPUM=80, BS=NULLBACKUP, HBT=FLU, BN=0;ADD BRD: FN=0, SN=1, BP=FRONT, BT=FLU, CPUB=90, CPUM=80, BS=NULLBACKUP, HBT=FLU, BN=1;ADD BRD: FN=0, SN=0, BP=BACK, BT=BLU, CPUB=90, CPUM=80, BS=ONEBACKUP, HBT=BLU, BN=0;

//Configure boards of the service frame.ADD BRD: FN=2, SN=7, BP=FRONT, BT=MPU, BS=ONEBACKUP, HBT=MPB, BN=1;ADD BRD: FN=2, SN=8, BP=FRONT, BT=MPU, BS=ONEBACKUP, HBT=MPB, BN=1;ADD BRD: FN=2, SN=0, BP=BACK, BT=E32, ADS=ACTIVE, CPUB=90, CPUM=80, BS=LOADSHARE, HBT=E32, BN=0;ADD BRD: FN=2, SN=1, BP=BACK, BT=E32, ADS=ACTIVE, CPUB=90, CPUM=80, BS=LOADSHARE, HBT=E32, BN=1;ADD BRD: FN=2, SN=2, BP=BACK, BT=E32, ADS=ACTIVE, CPUB=90, CPUM=80, BS=LOADSHARE, HBT=E32, BN=2;ADD BRD: FN=2, SN=3, BP=BACK, BT=E32, ADS=ACTIVE, CPUB=90, CPUM=80, BS=LOADSHARE, HBT=E32, BN=3;ADD BRD: FN=2, SN=2, BP=FRONT, BT=SPF, CPUB=90, CPUM=80, BS=LOADSHARE, HBT=SPF, BN=0;ADD BRD: FN=2, SN=3, BP=FRONT, BT=SPF, CPUB=90, CPUM=80, BS=LOADSHARE, HBT=SPF, BN=1;

PostrequisiteAfter configuring frames and boards, configure the clock.

Configuring the Clock


Configuration Guide


Issue 02 (2008-05-07)

9 Configuring the Clock

This describes how to configure the clock data including the reference source, CLK, and lineclock source.

PrerequisiteThe frames and boards data is correctly set.

UMG8900 Clock System

The UMG8900 clock system provides clock signals to meet the requirements of theUMG8900. It accesses external reference clock signals of different standards to provide thestratum-2 and stratum-3 precision clocks for telecom devices.

The core processing unit of the clock system is the independent clock boards CLK or the clocksubboard on the TNC board. When independent CLK boards are adopted, the system can provideboth the stratum-2 and stratum-3 precision clocks. When the clock subboard is adopted, onlythe stratum-3 precision clock can be provided.

Depending on such schemes as tracing of external reference signals and filtering of externalreference jitter and float, the CLK boards or clock subboard on the TNC board outputs clocksignals with high frequency, accuracy and stability, ensuring preciseness of clock source.

The MCLK boards support the following clock reference sources:

l 2-MHz line clock

l 2-Mbit/s line clock

l 1.5-Mbit/s line clock

l 64-kHz line clock

l 8-kHz line clock

l Global positioning system (GPS)

l Global navigation satellite system (GLONASS)

The clock subboard supports the following clock reference sources:

l 2-MHz line clock

l 2-Mbit/s line clock

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 9 Configuring the Clock


9-1

l 8-kHz line clock

The clock system also provides building integrated timing supply (BITS) clock output interfacesto connect with devices at the upper layer and provides BITS clock signal reference source fordevices at the lower layer.

In addition, the clock system can be configured through software to choose the external clockreference source and output clock level flexibly.

Introduction to the SSMSynchronization status message (SSM) is a synchronization status message and indicates thelevel of synchronous timing signals in synchronous timing transmission links. For E1 signals,Sa4 to Sa8 of timeslot 0 of the odd frame are defined to transmit SSM in G.704. For T1 signals,the 4-kbit/s data link composed of the first bit of the odd frame in the multiframe is defined totransmit SSM in G.704.

Figure 9-1 shows the position that SSM is transmitted in E1 signals.

Figure 9-1 Position that SSM is transmitted in E1 signals

Multiframe

Oddframe

8 bitsTimeslot

0

32 timeslots

16 frames

As shown in Figure 9-1, timeslot 0 of the odd frame in the multiframe is used to transmit SSM.Each timeslot consists of eight bits. SSM can be inserted to anyone of Sa4 to Sa8.

NOTE

You can use MOD CLKSRC and SET LINECLK to select the bit for inserting SSM for the BITS clockand the line clock.

The SSM code is composed of four bits. A multiframe consists of eight odd frames and eight even frames.Each odd frame provides a bit to transmit the SSM code. Thus, a multiframe can transmit two completeSSM codes, with the last four odd frames repeatedly transmitting codes of the first four odd frames.

See Table 9-1 for SSM codes.

Table 9-1 SSM codes

SSM Code Meaning Level

10 Primary reference clock (PRC) Stratum-1 clock

100 Transit network clock (TNC) Stratum-2 clock

1000 Local network clock (LNC) Stratum-3 clock

9 Configuring the ClockHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

SSM Code Meaning Level

1011 SDH device timing source (SETS) Transfer node clock

1111 Don't use for sync (DNU) Not used for synchronization

0 Sync status unknown (UNKNOWN) Unknown synchronization status

In Table 9-1, the priority is PRC > TNC > LNC > SETS > UNKNOWN > DNU. The priorityof PRC is the highest.

NOTE

You can use MOD CLKSRC to define the SSM level of a clock reference source.

The SSM level of the GPS/GLONASS reference source can only be PRC.

Clock Phase-Lock StatusThe value of phase-lock status can be:

l Free running: Indicates that the CLK board outputs free running clock generated by itscrystal.

l Fast tracking: Indicates that the CLK board or the clock subboard on the MTNC is trackingreference source clock fast and is an instantaneous status usually when the system justconnects the reference source.

l Locked: Indicates that the CLK board or the clock subboard on the MTNC has lockedprimary reference source and outputs clock signals aligned with reference source.

l Holdover: Indicates that the CLK board or the clock subboard on the MTNC outputs clocksignals based on the locked status when reference source is missing.

After configuring clock reference source, the phase-lock status of the CLK board or the clocksubboard on the MTNC is Locked when the system is in normal operation. Otherwise, the clockis in error. You need to examine clock cable connections and clock alarms to find out the causeof error.

If no reference source is set and the CLK board or the clock subboard on the MTNC adopts clockgenerated by its constant-temperature crystal, the phase-lock status is Free running.

Clock Reference Source SelectionThe UMG8900 supports four options of clock reference source, namely GPS/GLONASS, one-channel 2-MHz, 2-Mbit/s, 1.5-Mbit/s or 64-kHz BITS clocks and two-channel 8-kHz line clock.

Figure 9-2 shows the procedures for selecting clock reference source.



9-3

Figure 9-2 Procedures for choosing clock reference source

Start

Manual selection?

Under SSM control

Select a reference source basedon the configured priority

End

Specify the primaryreference source without

switching reference sources

Select the reference sourcebased on SSM level

Yes

YesNo

No

First, the system supports two modes of reference source selection, automatic selection andmanual selection. In manual selection mode, the CLK board only traces primary reference sourcethat is manually specified, without auto switching between reference sources.

Second, automatic selection falls into two cases, namely, under SSM control and without SSMcontrol.

Under SSM control, first the reference source with higher SSM level is preferred. If with thesame SSM level, the reference source with higher priority is preferred. If available referencesource with the highest level is missing, the CLK board will auto switch to the reference sourcewith secondary highest level. When the original reference source recovers, the CLK board canauto switch back to it.

Without SSM control, first the reference source with higher priority is preferred. If availablereference source with the highest level is missing, the CLK board will auto switch to the referencesource with secondary highest level. When the original reference source recovers, the CLK boardcan auto switch back to it.

You can configure priorities for reference sources manually. By default, priorities are arrangedin the following high-to-low order: GPS/GLONASS (level 1), external synchronous referencesource (level 2), line clock 1 (level 3) and line clock 2 (level 4). It is recommended to select theexternal synchronous reference source.

NOTE

In automatic selection mode, the primary reference source specified in manual selection mode does nottake effect.

Clock Distribution and OutputWhen independent CLK boards are adopted, they provide clock signals to the NET. Then theNET distributes the clock signals to other boards within the frame. The CLK provides clock


Configuration Guide


Issue 02 (2008-05-07)

signals to the NET in its own frame through the backplane. It provides clock signals to the NETin other frames through clock distribution cables.

When the subboard on the TNC is adopted, it sends clock signals to the boards in its own framethrough the backplane. For boards in other frames, it first sends clock signals to the TNC throughTDM cascading cables between frames, and the TNC then distributes the clock signals to theboards in its frame.

Both the CLK and the subboard on the TNC can output one-channel 2-Mbit/s, 1.5-Mbit/s, 2-MHz or 16-kHz external synchronous clock signals to other equipment within the network oraccess network equipment. You can configure the type of output clock signal by the MMLcommand MOD CLK.

Physical Cable Connection

Before configuring clock, you need to connect physical cables based on actual clock networkingmode.

The connection of physical clock cables is shown in Table 9-2.

Table 9-2 Clock cable connection

Application Cable Connection

Extract the line clockreference source 1 from theTDM interface board.

Connect the 8K_OUT interface of the TDM interface board(including E32/T32/S2L/P4L/P1H) with the 8K-IN1 interfaceof the master and slave MCLK boards through the 8K clockcable. The X1 plug of the 8K clock cable connects the TDMinterface board side and the X2/X3 plug connects the MCLKboard side.

Extract the line clockreference source 2 from theTDM interface board.

The same as above.

Extract the externalsynchronous referencesource from the BITSdevice.

Connect the 2M_IN interface of the CLK board with the clockoutput interface of the BITS device through the 2M clockcable.Connect the 1.5M/64k interface of the CLK board with theclock output interface of the BITS device through the 1.5M/64k clock cable.

Extract the reference sourcefrom GPS/GLONASS.

Connect the ANT interface of the MCLK board with the GPSsatellite antenna through the GPS/GLONASS clock cable.The satellite card must be inserted in the MCLK board.

Clock distribution to framesexcept the main controlframe.

Connect the CLK-OUT interface of the MCLK board with theCLK-IN interface of the NET board through the clockdistribution cable. CLK0_IN and CLK1_IN interfaces of theNET board correspond the CLK_OUT interfaces of the masterand slave MCLK boards respectively. The X1 plug of theclock distribution cable connects the MCLK board side andthe X2-X7 plugs connect the NET board side.



9-5

Application Cable Connection

Clock distribution to thecurrent frame.

Distributed through the backplane, without manualconnection.

Clock output.Connect the 2M_OUT interface of the MCLK board with theclock input interface of the clock receiving device through the2M clock cable.

Configuration Procedure

Figure 9-3 shows the recommended steps for configuring the clock.

Figure 9-3 Steps for clock configuration

Configure the clock

Configure CLK data

Configure clockreference sources

Configure line clocksources

Extract line clocks?

Output clock signals?

End

No

No

NoYes

Yes

Yes

Configure referencesources?

Clock configuration varies with different modes of the clock synchronization networking. Referto Figure 9-3.

Data Planningl Table 9-3 lists the parameter output to this step, and you need to fill in the parameter values

according to the output parameters of the input source.



Board type <Board type> Configuring Frames and Boards

Board No. <Board No.> Configuring Frames and Boards


Configuration Guide


Issue 02 (2008-05-07)

l Table 9-4 lists the data needed in this step. The interconnected device column in the table




Priority of GPS reference source <Priority of GPS reference source>

Priority of line clock 1 <Priority of line clock 1>


Priority of external synchronous1

<Priority of external synchronous 1>

Priority of external synchronous2

<Priority of external synchronous 2>

Type of external synchronous <Type of external synchronous>

Select mode of reference source <Select Mode of Reference Source>

Clock level <Clock Level>

Type of clock signal of externalsynchronous output

<Type of Clock Signal of External SynchronousOutput>

Whether SSM control <Whether SSM Control>

External reference source workmode

<External Reference Source Work Mode>

Line clock <Line Clock>

Interface type <Interface Type>

Port No. <Port No.>

Channel No. <Channel No.>

SSM timeslot <SSM Time Slot>

Procedure

Step 1 If the clock reference source is required, run MOD CLKSRC to configure the clock referencesource. Set Board Type to CLK or TNC. If no clock reference source is required, perform Step2 and configure the CLK data.l Set Board Type to CLK.

MOD CLKSRC: BRDTYPE=CLK, GPSPRI=<Priority of GPS reference source>,LINE1PRI=<Priority of line clock 1>, LINE2PRI=<Priority of line clock 2>,EXT1PRI=<Priority of external synchronous 1>;

l Set Board Type to TNC, and the GPS reference source is not supported.



9-7

MOD CLKSRC: BRDTYPE=TNC, LINE1PRI=<Priority of line clock 1>,LINE2PRI=<Priority of line clock 2>, EXT1PRI=<Priority of external synchronous1>, EXT2PRI=<Priority of external synchronous 2>;

Step 2 Run MOD CLK to configure the CLK data.l Set Board Type to CLK.

MOD CLK: BRDTYPE=CLK, MODE=<Select Mode of Reference Source>,GRADE=<Clock Level>, TYPE=<Type of Clock Signal of External SynchronousOutput>, CTRL=<Whether SSM Control>, CLKMODE=<External Reference SourceWork Mode>;

l Set Board Type to TNC, and only the stratum-3 clock is provided.MOD CLK: BRDTYPE=CLK, MODE=<Select Mode of Reference Source>,TYPE=<Type of Clock Signal of External Synchronous Output>, CTRL=<WhetherSSM Control>, CLKMODE=<External Reference Source Work Mode>;

Step 3 If the line clock is required, run SET LINECLK to set the port of extracting the line clockreference source.SET LINECLK: LINE=<Line Clock>, BT=<Board type>, BN=<Board No.>,PT=<Interface Type>, PN=<Port No.>, CN=<Channel No.>, SLOT=<SSM Time Slot>;

----End

ExampleExample script//Configure the clock. MOD CLKSRC: BRDTYPE=CLK, GPSPRI=SECOND, LINE1PRI=THIRD, LINE2PRI=FOURTH, EXT1PRI=FIRST, GPSTYPE=GPS, SRCTYPE=EXT2MHz;MOD CLK: BRDTYPE=CLK, MODE=AUTO, GRADE=TWO, CTRL=NO, CLKMODE=SOURCE;

//Configure the clock. Extract the line clock from port 0 on E32 boards 0 and 1.SET LINECLK: LINE=LINE1, BT=E32, BN=0, PN=0, SLOT=SA4;SET LINECLK: LINE=LINE2, BT=E32, BN=1, PN=0, SLOT=SA4;

PostrequisiteAfter configuring the system clock data, configure the MGW control interface and SIGTRANinterface.

Configuring the MGW Control Interface and SIGTRAN Interface


Configuration Guide


Issue 02 (2008-05-07)

10 Configuring the MGW Control Interfaceand SIGTRAN Interface

About This Chapter

This describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface.

10.1 Configuring the Physical Interface in Single-Frame Networking ModeThis describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface in single-frame networking mode.

10.2 Configuring the Physical Interface in SSM-256 Self-Cascading ModeThis describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface in SSM-256 self-cascading mode.

10.3 Configuring the Physical Interface in SSM-32 Self-Cascading ModeThis describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface in SSM-32 self-cascading mode.

10.4 Configuring the Physical Interface in Mixed Cascading ModeThis describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface in SSM-256 and SSM-32 mixed cascading mode.

10.5 Configuring the E1 Physical Interface Carrying IP Signaling PacketsThis describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface when the E1 physical interface is used to carry Internet Protocol(IP) signaling packets.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide

10 Configuring the MGW Control Interface and SIGTRANInterface


10-1

10.1 Configuring the Physical Interface in Single-FrameNetworking Mode

This describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface in single-frame networking mode.

Prerequisitel The frames and board data is correctly set.

l The clock data is correctly set.

ContextIn single-frame networking mode, the configurations of the physical interface of the MGWcontrol interface and SIGTRAN interface in the SSM-256 frame are different from those in theSSM-32 frame. The configuration rules of the two types of frames are as follows:

l Single SSM-256 networking falls into the following cases:– No HRB is configured.

– The E8T (back board of the HRB) is configured.

– The E1G (back board of the HRB) is configured.

– Through the OMC interface on the NET, the SSM-256 frame provides OAM, H.248and SIGTRAN interfaces at the same time, if the HRB is not configured. The IP addressof the OAM interface is set as the slave one, and that of the H.248 and SIGTRANinterfaces is set as the master one. In this case, if the H.248 and SIGTRAN messagesare transmitted through the same protocol, different protocol interface numbers mustbe used.

– Table 10-1 shows the usage rules of IP interfaces when the HRB board is configuredin the SSM-256 frame.

Table 10-1 Usage rules of IP interfaces when the HRB is configured

LogicalPosition

Physical Position andFunction When the E8T IsConfigured

Physical Position andFunction When Only theE1G Is Configured

OMUOMC interface on the back NET,which can serve as an OAMinterface

OMC interface on the back NET,which can serve as an OAMinterface

HRBThe first FE port on the backE8T, which can serve as an H.248 or SIGTRAN interface

GE port on the back E1G, whichcan serve as an H.248 orSIGTRAN interface through themaster IP address


GE port on the back E1G, whichcan serve as an IP service bearerinterface through the slave IPaddress




Issue 02 (2008-05-07)

NOTE

If both the E8T and E1G boards are configured in the frame, the E8T board is used for centralizedforwarding.

As shown in Table 10-1, the first FE port on the E8T board or the GE port on the E1Gboard needs to serve as H.248 and SIGTRAN interfaces at the same time. In this case,if the same transmission protocol is used for the H.248 and SIGTRAN messages,different protocol interface numbers must be used.

NOTE

If the HRB is configured in the signal-frame networking, it is recommend to use the centralizedforwarding function of the HRB.

l Single SSM-32 networking falls into the following cases:– No HRB is configured.

– The back E8T of the HRB is configured.

– The back E1G of the HRB is configured.

– In case of single SSM-32 networking, if no HRB is configured, the SSM-32 uses theMc interface on the OMU board for centralized forwarding.Table 10-2 shows the usage rules for IP interfaces.

Table 10-2 Usage rules for IP interfaces when no HRB is configured for the singleSSM-32 networking

LogicalPosition Physical Position and Function

OMU OMC interface on the TNC, which can serve as an OAM interface

OMU Mc interface on the back TNC, which can serve as an H.248 orSIGTRAN interface

As shown in Table 10-2, the Mc interface on the OMU provides both H.248 andSIGTRAN interfaces. In this case, if the same transmission protocol is used for H.248and SIGTRAN messages, different protocol port numbers must be used.

– If the HRB is configured for single SSM-32 networking, the usage rules are similar tothose of the SSM-256 frame. Refer to Table 10-3.

Table 10-3 Usage rules for IP interfaces when the HRB is configured for the singleSSM-32 networking

LogicalPosition



OMUOMC interface on the backTNC, which can also serve as anOAM interface

OMC interface on the back TNC,which can serve as an OAMinterface




10-3

LogicalPosition



HRBThe first FE port on the backE8T, which can serve as an H.248 or SIGTRAN interface

GE port on the back E1G, whichcan serve as an H.248 orSIGTRAN interface through themaster IP address


GE port on the back E1G, whichcan serve as an IP service bearerinterface through the slave IPaddress

NOTE

If both the E8T and E1G are configured in the frame, the E8T is used for centralized forwarding.

As shown in Table 10-3, the first FE port on the E8T or the GE port on the E1G needsto provide H.248 and SIGTRAN interfaces at the same time. In this case, if the sametransmission protocol is used for H.248 and SIGTRAN messages, different protocolport numbers must be adopted.

Data Planningl Table 10-4 lists the parameter output to this step, and you need to fill in the parameter

values according to the output parameters of the input source.



Board type <Board type> 8 Configuring Frames andBoards

Board No. <Board No.> 8 Configuring Frames andBoards



ParameterName

UMG8900 Interconnected Device 1(MGC)

Interconnected Device 2(DirectRouter)

Interconnected Device 3(MGW)

Work mode <Work Mode> - - -




Issue 02 (2008-05-07)

ParameterName




Interface type <Interfacetype>

- - -

Interface ID <InterfaceNo.>

- - -

IP addresses 1of gatewaycontrolinterfaces andSIGTRANinterfaces

<Interface IPaddress>_1

The same asthat of the peerdevice

- -

IP addresses 2of gatewaycontrolinterfaces andSIGTRANinterfaces



- -

IP address andmask ofgatewaycontrolinterfaces andSIGTRANinterfaces



- -

Master or slaveflag

<Master orslave flag>

- - -

Slot No. <Slot No.> - - -

IP address 1 ofthe MGC


<Destinationaddress>_1

- -




- -

IP address andmask of theMGC



- -

IP address ofthe routerconnected withthe UMG8900


- <Next hopaddress>

-




10-5

ParameterName




IP address ofthe gateway


- - <Gateway IP>

If aging or not <If aging ornot>

- - -


Table 10-6 Data output

Parameter Name Data

IP address 1 of MGW control interfacesand SIGTRAN interfaces

<Interface IP address>_1

IP address 2 of MGW control interfacesand SIGTRAN interfaces


NOTE

If Stream Control Transmission Protocol (SCTP) multi-homing is supported, two IP addresses ofMGW control interfaces and SIGTRAN interfaces are exported.

Procedure

Step 1 Run SET IPWORKMODE to set the IP work mode of boards. SET IPWORKMODE is validfor the OMB, MPB, and MPU only. In single-frame networking mode, SETIPWORKMODE is valid for the OMB only. WORK MODE can be STANDBY orLOADSHARE. By default, it is STANDBY. WORK MODE is set to LOADSHARE onlywhen SCTP multi-homing is configured.SET IPWORKMODE: BT=OMU, BN=0, WM=<Work Mode>;

Step 2 Run ADD IPADDR to add the IP address of the interface. Parameter settings vary with Boardtype.l If the IP interface on the OMU or the OMB is adopted, set Board type to OMU.

ADD IPADDR: BT=OMU, BN=0, IFT=ETH, IFN=<Interface No.>,IPADDR=<Interface IP address>_1, MASK=<Interface IP address mask>,FLAG=<Master or slave flag>, SN=<Slot No.>;

NOTE

If WORK MODE is set to LOADSHARE, you must specify Slot No.. If WORK MODE is set toSTANDBY, you do not need to specify Slot No..

If WORK MODE of the OMB is set to LOADSHARE, only the Mc interface works in load-sharingmode. The OMC interface still serves as the system maintenance interface and works in master/slavemode.




Issue 02 (2008-05-07)

l If the IP interface on the PPU or the HRB is adopted, set Board type to a value rather thanOMU.

ADD IPADDR: BT=<Board type>, BN=<Board No.>, IFT=ETH, IFN=<InterfaceNo.>, IPADDR=<Interface IP address>_1, MASK=<Interface IP address mask>,FLAG=<Master or slave flag>;

If... Then...

The interface on the OMU/OMB/PPU is adopted and the IP address of the MGCand that of the gateway are not in the same network segment

Step 4

The back interface board of the HRB works as the MGW control interface andSIGTRAN interface

Step 6

Step 3 If SCTP multi-homing is configured on the OMB, if the Mc interface works in load-sharingmode, and if IP addresses need to be configured for two OMBs respectively, run ADDIPADDR to add the IP address of the Mc interface on the slave board. Otherwise, do not performthis step but perform the related step based on the preceding table.ADD IPADDR: BT=OMU, BN=0, IFT=ETH, IFN=1, IPADDR=<Interface IPaddress>_2, MASK=<Interface IP address mask>, FLAG=<Master or slave flag>, SN=<SlotNo.>;

Step 4 Run ADD ROUTE to add routes. Set Route type to Next hop. Configuration commands varywith Board type.

l If the IP interface on the OMU or the OMB is adopted, set Board type to OMU.

ADD ROUTE: BT=OMU, BN=0, DSTIP=<Destination address>_1,DSTMASK=<Destination address mask>, RTTYPE=NEXTHOP, NEXTHOP=<Nexthop address>, SN=<Slot No.>;

NOTE

In SCTP multi-homing mode, the MGC provides two IP addresses. If WORK MODE is set toLOADSHARE, you must specify Slot No.. If WORK MODE is set to STANDBY, you do not needto specify Slot No..

l If the IP interface on the PPU is adopted, set Board type to a value rather than OMU.

ADD ROUTE: BT=PPU, BN=<Board No.>, DSTIP=<Destination address>_1,DSTMASK=<Destination address mask>, RTTYPE=NEXTHOP, NEXTHOP=<Nexthop address>;

Step 5 If SCTP multi-homing is configured on the OMB, you must configure routes to the MGC fortwo IP addresses. Run ADD ROUTE to add the route to IP address 2 of the MGC. Otherwise,you do not need to perform this step, and the configuration is complete.ADD ROUTE: BT=OMU, BN=0, DSTIP=<Destination address>_2,DSTMASK=<Destination address mask>, RTTYPE=NEXTHOP, NEXTHOP=<Next hopaddress>, SN=<Slot No.>;

Step 6 Run ADD GWADDR to add the IP address of the MGW. Set Board type to HRB.ADD GWADDR: BT=HRB, BN=<Board No.>, IPADDR=, GWIP=<Gateway IP>,TIMEOUT=NoAging;

----End




10-7

SSM-256 FrameNetworking diagram

Figure 10-1 shows the networking diagram of a single SSM-256 frame.

Figure 10-1 Networking diagram of a single SSM-256 frame

IP Network

MGC

IP address: 192.168.0.1/24

IP address of the router: 10.1.1.254/24

IP address of the OMC interface: 10.1.1.1IP address of the first interface on the E8T: 10.1.1.10IP address of the Mc interface: 10.1.1.50

IP address of the Gateway: 10.1.1.200/24

UMG8900

Example script

l When the HRB is not configured, use the OMC interface on the NET as the OAM, H.248,and SIGTRAN interfaces.ADD IPADDR: BT=OMU, BN=0, IFT=ETH, IFN=0, IPADDR="10.1.1.1", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO;

NOTE

If the OMC interface serves as the OAM interface, set Master or slave flag to SLAVE whenconfiguring the IP address.

ADD ROUTE: BT=OMU, BN=0, DSTIP="192.168.0.1", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";

l Configure the first interface on the back E8T of the HRB as the centralized forwardinginterface.ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=0, IPADDR="10.1.1.10", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO; ADD GWADDR: BT=HRB, BN=0, IPADDR="10.1.1.10", GWIP="10.1.1.200", TIMEOUT=NoAging;

l Configure the GE interface on the back E1G of the HRB as the centralized forwardinginterface.ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=0, IPADDR="10.1.1.50", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO; ADD GWADDR: BT=HRB, BN=0, IPADDR="10.1.1.50", GWIP="10.1.1.200", TIMEOUT=NoAging;

SSM-32 FrameNetworking diagram

Figure 10-2 shows the networking diagram of a single SSM-32 frame.




Issue 02 (2008-05-07)

Figure 10-2 Networking diagram of a single SSM-32 frame

IP Network

MGC

IP address 1: 192.168.0.1/24


7 slot IP address of the Mc interface: 10.1.1.4IP address of the OMC interface: 10.1.1.1

IP address of the first interface on the E8T: 10.1.1.10IP address of the Mc interface: 10.1.1.50

IP address of the Gateway: 10.1.1.200/24

IP address 2: 192.168.0.2/24

8 slot IP address of the Mc interface: 10.1.1.14

UMG8900

Example script

l If the HRB is not configured, use the Mc interface on the OMB as the centralized forwardinginterface. WORK MODE is STANDBY.//Set WORK MODE of the OMB to STANDBY. SET IPWORKMODE: BT=OMU, BN=0, WM=STANDBY;ADD IPADDR: BT=OMU, BN=0, IFT=ETH, IFN=1, IPADDR="10.1.1.4", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO; ADD ROUTE: BT=OMU, BN=0, DSTIP="192.168.0.1", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";

l If the HRB is not configured, use the Mc interface on the OMB as the centralized forwardinginterface. WORK MODE is LOADSHARE. Enabling the centralized forwarding functionof the slave board can help to implement SCTP multi-homing.//Set WORK MODE of the OMB to LOADSHARE. SET IPWORKMODE: BT=OMU, BN=0, WM=LOADSHARE;

//You can set WORK MODE of the Mc interface only on the OMB to LOADSHARE. You must set IP addresses for the OMBs in slots 7 and 8. ADD IPADDR: BT=OMU, BN=0, IFT=ETH, IFN=1, IPADDR="10.1.1.4", MASK="255.255.255.0", FLAG=MASTER, SN=7; ADD IPADDR: BT=OMU, BN=0, IFT=ETH, IFN=1, IPADDR="10.1.1.8", MASK="255.255.255.0", FLAG=MASTER, SN=8;

//The MGC provides two IP addresses. You must configure routes to IP addresses 1 and 2 of the MGC. ADD ROUTE: BT=OMU, BN=0, DSTIP="192.168.0.1", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254"; ADD ROUTE: BT=OMU, BN=0, DSTIP="192.168.0.2", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";

l Configure the first interface on the back E8T of the HRB as the centralized forwardinginterface.ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=0, IPADDR="10.1.1.10", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO; ADD GWADDR: BT=HRB, BN=0, IPADDR="10.1.1.10", GWIP="10.1.1.200", TIMEOUT=NoAging;

l Configure the GE interface on the back E1G of the HRB as the centralized forwardinginterface.ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=0, IPADDR="10.1.1.50", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO;




10-9

ADD GWADDR: BT=HRB, BN=0, IPADDR="10.1.1.50", GWIP="10.1.1.200", TIMEOUT=NoAging;

PostrequisiteAfter configuring the physical interface of the MGW control interface and SIGTRAN interface,configure the MGW control data.


10.2 Configuring the Physical Interface in SSM-256 Self-Cascading Mode

This describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface in SSM-256 self-cascading mode.



ContextIn SSM-256 self-cascading mode, the centralized forwarding mode is used. The OMC interfaceon the back NET of the MPU in the centralized switching provides the H.248 interface andSIGTRAN interface.




Parameter Name UMG8900 InterconnectedDevice 1 (MGC)

InterconnectedDevice 2 (DirectRouter)

Work mode <Work Mode> - -

IP address 1 of theOMC interface onthe MPU



-




-

IP address and maskof the OMCinterface on theMPU



-




Issue 02 (2008-05-07)




- -

Slot No. <Slot No.> - -

IP address of therouter connectedwith the UMG8900


- <Next hopaddress>

IP address 1 of theMGC



-




-

IP address and maskof the MGC



-



Parameter Name Data

IP addresses 1 of MGW controlinterfaces and SIGTRAN interfaces


IP addresses 2 of MGW controlinterfaces and SIGTRAN interfaces


NOTE


Procedure

Step 1 Run SET IPWORKMODE to set the IP work mode. SET IPWORKMODE is valid for theOMB, MPB, and MPU only. In SSM-256 self-cascading mode, LOADSHARE is valid for theMPU only. WORK MODE can be STANDBY or LOADSHARE. By default, it isSTANDBY. WORK MODE is set to LOADSHARE only when SCTP multi-homing isconfigured.SET IPWORKMODE: BT=MPU, BN=1, WM=<Work Mode>;

Step 2 Run ADD IPADDR to add the IP address of the interface. If the OMC interface on the MPU inthe central switching frame serves as the centralized forwarding interface, set Board type toMPU and Interface No. to 0. Board No. of the MPU in the central switching frame can onlybe 1.




10-11

ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR=<Interface IP address>_1,MASK=<Interface IP address mask>, FLAG=<Master or slave flag>, SN=<Slot No.>;

NOTE

If WORK MODE of the MPU is set to LOADSHARE, you must specify Slot No.. If WORK MODE isset to STANDBY, you do not need to specify Slot No..

Step 3 If SCTP multi-homing is configured on the MPU and IP addresses need to be configured fortwo MPUs respectively, run ADD IPADDR to add the IP address of the OMC interface on theslave board.ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR=<Interface IP address>_2,MASK=<Interface IP address mask>, FLAG=<Master or slave flag>, SN=<Slot No.>;

Step 4 If the MGC and the UMG8900 are not in the same network segment, run ADD ROUTE to adda route. Otherwise, do not configure the route.

ADD ROUTE: BT=MPU, BN=1, DSTIP=<Destination address>_1,DSTMASK=<Destination address mask>, RTTYPE=NEXTHOP, NEXTHOP=<Next hopaddress>, SN=<Slot No.>;

NOTE


Step 5 If SCTP multi-homing is configured on the MPU, you must configure routes to the MGC fortwo IP addresses. Run ADD ROUTE to add the route to IP address 2 of the MGC.ADD ROUTE: BT=MPU, BN=1, DSTIP=<Destination address>_2,DSTMASK=<Destination address mask>, RTTYPE=NEXTHOP, NEXTHOP=<Next hopaddress>, SN=<Slot No.>;

----End


Figure 10-3 shows the networking diagram of the SSM-256 self-cascading mode.

Figure 10-3 Networking diagram of the SSM-256 self-cascading

IP Network

MGC

IP address 1: 192.168.0.1/24


7 slot IP address of the OMC interface on the MPUin the central switching frame: 10.1.1.5

IP address 2: 192.168.0.2/24


UMG8900




Issue 02 (2008-05-07)

Example script

l To set WORK MODE of the MPU to STANDBY, run the following command:SET IPWORKMODE: BT=MPU, BN=1, WM=STANDBY; //To set WORK MODE to STANDBY, you need to set one IP address only.ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR="10.1.1.5", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO; ADD ROUTE: BT=MPU, BN=1, DSTIP="192.168.0.1", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";

l To set WORK MODE of the MPU to LOADSHARE, run the following command:SET IPWORKMODE: BT=MPU, BN=1, WM=LOADSHARE; //To set WORK MODE to LOADSHARE, you must set IP addresses for the MPUs in slots 7 and 8. Set the IP address of the MPU in slot 7 as the master IP address and that of the MPU in slot 8 as the slave IP address. ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR="10.1.1.5", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO, SN=7; ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR="10.1.1.15", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO, SN=8;

//The MGC provides two IP addresses. You must configure routes to IP addresses 1 and 2 of the MGC. ADD ROUTE: BT=MPU, BN=1, DSTIP="192.168.0.1", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";ADD ROUTE: BT=MPU, BN=1, DSTIP="192.168.0.2", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";



10.3 Configuring the Physical Interface in SSM-32 Self-Cascading Mode

This describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface in SSM-32 self-cascading mode.



Context

In SSM-32 self-cascading mode, the centralized forwarding mode is used, and the OMC interfaceon the back TNC of the MPB in the first service frame is used as the H.248 interface andSIGTRAN interface.






10-13





IP address 1 of theOMC interface onthe MPB



-

IP address 2 of theOMC interface onthe MPB



IP address and maskof the OMCinterface on theMPB



-


- -




- <Next hopaddress>




-







-



Parameter Name Data

IP address 1 of MGW controlinterfaces and SIGTRAN interfaces







Issue 02 (2008-05-07)

NOTE


Procedure

Step 1 Run SET IPWORKMODE to set the IP work mode. SET IPWORKMODE is valid for theOMB, MPB, and MPU only. In SSM-32 self-cascading mode, LOADSHARE is valid for theMPB only. WORK MODE can be STANDBY or LOADSHARE. By default, it isSTANDBY. WORK MODE is set to LOADSHARE only when SCTP multi-homing isconfigured.SET IPWORKMODE: BT=MPU, BN=1, WM=<Work Mode>;

Step 2 Run ADD IPADDR to add the IP address of the interface. If the OMC interface on the MPB inthe first service frame serves as the centralized forwarding interface, set Board type to MPUand Interface No. to 0. Board No. of the MPU in the central switching frame can only be 1.


NOTE

If WORK MODE of the MPB is set to LOADSHARE, you must specify Slot No.. If WORK MODE isset to STANDBY, you do not need to specify Slot No..

Step 3 If SCTP multi-homing is configured on the MPB and IP addresses need to be configured for twoMPBs respectively, run ADD IPADDR to add the IP address of the OMC interface on the slaveboard.ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR=<Interface IP address>_2,MASK=<Interface IP address mask>, FLAG=<Master or slave flag>, SN=<Slot No.>;

Step 4 If the MGC and the UMG8900 are not in the same network segment, run ADD ROUTE to adda route. Otherwise, do not configure the route.


NOTE


Step 5 If SCTP multi-homing is configured on the MPB, you must configure routes to the MGC fortwo IP addresses. Run ADD ROUTE to add the route to IP address 2 of the MGC. Set Routetype to Next hop.ADD ROUTE: BT=MPU, BN=1, DSTIP=<Destination address>_2,DSTMASK=<Destination address mask>, RTTYPE=NEXTHOP, NEXTHOP=<Next hopaddress>, SN=<Slot No.>;

----End


Figure 10-4 shows the networking diagram of the SSM-32 self-cascading mode.




10-15

Figure 10-4 Networking diagram of the SSM-32 self-cascading

IP Network

MGC

IP address 1 : 192.168.0.1/24


7 slot IP address of the OMC interface on theMPB in the first service frame: 10.1.1.6

IP address 2: 192.168.0.2/24

8 slot IP address of the OMC interface on theMPB in the first service frame: 10.1.1.16UMG8900

Example scriptl To set WORK MODE of the MPB to STANDBY, run the following command:

SET IPWORKMODE: BT=MPU, BN=1, WM=STANDBY;

//To set WORK MODE to STANDBY, you need to set one IP address only. ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR="10.1.1.5", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO; ADD ROUTE: BT=MPU, BN=1, DSTIP="192.168.0.1", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";

l To set WORK MODE of the MPB to LOADSHARE, run the following command:SET IPWORKMODE: BT=MPU, BN=1, WM=LOADSHARE;

//To set WORK MODE to LOADSHARE, you must set IP addresses for the MPUs in slots 7 and 8. Set the master IP address for the MPU in slot 7 and the slave IP address for the MPU in slot 8. ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR="10.1.1.5", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO, SN=7; ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR="10.1.1.15", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO, SN=8;

//The MGC provides two IP addresses. You must configure routes to IP addresses 1 and 2 of the MGC. ADD ROUTE: BT=MPU, BN=1, DSTIP="192.168.0.1", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254"; ADD ROUTE: BT=MPU, BN=1, DSTIP="192.168.0.2", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";






Issue 02 (2008-05-07)

10.4 Configuring the Physical Interface in Mixed CascadingMode

This describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface in SSM-256 and SSM-32 mixed cascading mode.



ContextIn SSM-256 and SSM-32 mixed cascading mode, the SSM-256 frame is used as the centralswitching frame, and the centralized forwarding mode is used. The OMC interface on the backNET of the MPU in the central switching frame is used as the H.248 interface and SIGTRANinterface.

Data Planningl Table 10-11 lists the data needed in this step. The interconnected device column in the

table indicates whether the parameter needs to negotiate with the interconnected parameter.If not, "-" is filled in.








-




-

IP address and maskof the OMCinterface on theMPU



-


- -





10-17





- <Next hopaddress>




-




-




-



Parameter Name Data





NOTE

If Stream Control Transmission Protocol (SCTP) multi-homing is supported, two IP addresses of theMGW control interface and SIGTRAN interface are exported.

Procedure

Step 1 Run SET IPWORKMODE to set the IP work mode. SET IPWORKMODE is valid for theOMB, MPB, and MPU only. In SSM-256 and SSM-32 mixed cascading mode,LOADSHARE is valid for the MPU only. WORK MODE can be STANDBY orLOADSHARE. By default, it is STANDBY. WORK MODE is set to LOADSHARE onlywhen SCTP multi-homing is configured.SET IPWORKMODE: BT=MPU, BN=1, WM=<Work Mode>;

Step 2 Run ADD IPADDR to add the IP address of the interface. If the OMC interface on the MPU inthe central switching frame serves as the centralized forwarding interface, set Board type toMPU and Interface No. to 0. Board No. of the MPU in the central switching frame can onlybe 1.





Issue 02 (2008-05-07)

NOTE

If WORK MODE of the MPU is set to LOADSHARE, you must specify Slot No.. If WORK MODE isset to STANDBY, you do not need to specify Slot No..

Step 3 If SCTP multi-homing is configured on the MPU and IP addresses need to be configured fortwo MPUs respectively, run ADD IPADDR to add the IP address of the OMC interface on theslave board.ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR=<Interface IP address>_2,MASK=<Interface IP address mask>, FLAG=<Master or slave flag>, SN=<Slot No.>;

Step 4 If the MGC and the UMG8900 are not in the same network segment, run ADD ROUTE to addthe route. Otherwise, do not configure the route.


NOTE


Step 5 If SCTP multi-homing is configured on the MPU, you must configure routes to the MGC fortwo IP addresses. Run ADD ROUTE to add the route to IP address 2 of the MGC. Set Routetype to Next hop.ADD ROUTE: BT=MPU, BN=1, DSTIP=<Destination address>_2,DSTMASK=<Destination address mask>, RTTYPE=NEXTHOP, NEXTHOP=<Next hopaddress>, SN=<Slot No.>;

----End


Figure 10-5 shows the networking diagram of the SSM-256 and SSM-32 mixed cascading.

Figure 10-5 Networking diagram of the SSM-256 and SSM-32 mixed cascading

IP Network

MGC

IP address 1: 192.168.0.1/24



IP address 2: 192.168.0.2/24


UMG8900




10-19

Example scriptl To set WORK MODE of the MPU to STANDBY, run the following command:

SET IPWORKMODE: BT=MPU, BN=1, WM=STANDBY; //To set WORK MODE to STANDBY, you need to set one IP address only.ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR="10.1.1.5", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO; ADD ROUTE: BT=MPU, BN=1, DSTIP="192.168.0.1", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";

l To set WORK MODE of the MPU to LOADSHARE, run the following command:SET IPWORKMODE: BT=MPU, BN=1, WM=LOADSHARE; //To set WORK MODE to LOADSHARE, you must set IP addresses for the MPUs in slots 7 and 8. Set the IP address of the MPU in slot 7 as the master IP address and that of the MPU in slot 8 as the slave IP address. ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR="10.1.1.5", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO, SN=7; ADD IPADDR: BT=MPU, BN=1, IFT=ETH, IFN=0, IPADDR="10.1.1.15", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO, SN=8;

//The MGC provides two IP addresses. You must configure routes to IP addresses 1 and 2 of the MGC. ADD ROUTE: BT=MPU, BN=1, DSTIP="192.168.0.1", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";ADD ROUTE: BT=MPU, BN=1, DSTIP="192.168.0.2", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.254";



10.5 Configuring the E1 Physical Interface Carrying IPSignaling Packets

This describes how to configure the media gateway (MGW) control interface and signalingtransport (SIGTRAN) interface when the E1 physical interface is used to carry Internet Protocol(IP) signaling packets.



ContextWhen the media gateway controller (MGC) is placed far away from the UMG8900 and has onlythe time division multiplexing (TDM) bearer, the UMG8900 communicates with the MGCthrough the E1 physical interface carrying IP packets.

In this case, use the IOE to bind with the E1 port of the E32 to provide the H.248 interface andSIGTRAN interface.






Issue 02 (2008-05-07)



TDM interface board type <Board type>_1 Configuring Frames andBoards

TDM board No. <Board No.> Configuring Frames andBoards

IOE board No. <Board No.>_2 Configuring Frames andBoards

Virtual media gateway ID <Virtual media gatewayid>

Configuring MGW Data

NOTE

The board Nos. of various types of boards are represented with <Board No.>.

l Table 10-14 lists the data needed in this step. The interconnected device column in thetable indicates whether the parameter needs to negotiate with the interconnected parameter.If not, "-" is filled in.



TDM optical port No. <TDM opt port No.> -

TDM port No. <TDM port No.> -

IOE internal TDM portNo.

<IOE internal TDM port No.> -

Port description <Port description> -

Start TID <Start TID> -

End TID <End TID> -

CMU module No. <CMU Module No.> -

TDM start timeslot <Start timeslot> -

TDM end timeslot <End timeslot> -

Serial interface ID <Interface No.> -

Interface type <Interface type> -

Serial interfacedescription

<Interface description> -

MP enable <MP enable> -




10-21


VT interface ID <VT Interface No.> -

IP address of the MGC The same as that of the peer device <Destination address>

IP address and mask ofthe MGC

The same as that of the peer device <Destination addressmask>

Procedure

Step 1 Run ADD BIND to configure the binding relationship of the TDM port.

l Set TDM board type to E32 and T32. The setting of E32 is considered as an example.

ADD BIND: TDMBT=E32, TDMBN=<Board No.>_1, TDMPORT=<TDM portNo.>, IOEBN=<Board No.>_2, IOEPORT=<IOE internal TDM port No.>,DESP=<Port description>;

l Set TDM board type to S1L, S2L, and PIE. The setting of S2L is considered as anexample.

ADD BIND: TDMBT=S2L, TDMBN=<Board No.>_1, OPTPORT=<TDM opt portNo.>, TDMPORT=<TDM port No.>, IOEBN=<Board No.>_2, IOEPORT=<IOEinternal TDM port No.>, DESP=<Port description>;

Step 2 Run ADD TDMIU to configure the binding relationship of the TDM port. Set Relay type toInside.ADD TDMIU: BT=<Board type>, BN=<Board No.>_1, TIDFV=<Start TID>,TIDLV=<End TID>, VMGWID=<Virtual media gateway id>, HOSTID=<CMU ModuleNo.>, RT=INSIDE;

Step 3 Run ADD CHANNEL to configure the binding relationship of the TDM port.ADD CHANNEL: BN=<Board No.>_2, PORT=<IOE internal TDM port No.>,STARTTS=<Start timeslot>, ENDTS=<End timeslot>, IFN=<Interface No.>;

Step 4 Run MOD IPIF to modify the configuration of the IP interface. Set Board type to HRB.MOD IPIF: IFT=<Interface type>, BT=HRB, BN=<Board No.>_2, IFN=<Interface No.>,DESP=<Interface description>, IFMP=<MP enable>, VT=<VT Interface No.>;

Step 5 Run ADD IPADDR to add the IP address of the interface. Set Board type to HRB.ADD IPADDR: BT=HRB, BN=<Board No.>_2, IFT=<Interface type>, IFN=<VT InterfaceNo.>, IPADDR=<Destination address>, MASK=<Destination address mask>;

----End


Figure 10-6 shows the networking diagram of using the E1 physical interface to carry IP packets.




Issue 02 (2008-05-07)

Figure 10-6 Networking diagram of using the E1 physical interface to carry IP packets

MGC

IP address: 192.168.0.1/24

IP address of VT0 interface: 10.1.1.7

E1

IP address of VT1 interface: 10.1.1.8

UMG8900

E1 ports 0 and 1 on E32 boards 0 and 1 constitute two VT interfaces to connect with the bearernetwork.

Example scriptADD BIND: TDMBT=E32, TDMBN=0, TDMPORT=0, IOEBN=0, IOEPORT=0, DESP="MSC0-0";ADD BIND: TDMBT=E32, TDMBN=0, TDMPORT=1, IOEBN=0, IOEPORT=1, DESP=" MSC0-1";ADD BIND: TDMBT=E32, TDMBN=1, TDMPORT=0, IOEBN=0, IOEPORT=2, DESP=" MSC0-2";ADD BIND: TDMBT=E32, TDMBN=1, TDMPORT=1, IOEBN=0, IOEPORT=3, DESP=" MSC0-3";ADD TDMIU: BT=E32, BN=0, TIDFV=0, TIDLV=63, VMGWID=0, HOSTID=30, RT=INSIDE;ADD TDMIU: BT=E32, BN=1, TIDFV=1024, TIDLV=1087, VMGWID=0, HOSTID=30, RT=INSIDE;ADD CHANNEL: BN=0, PORT=0, STARTTS=1, ENDTS=31, IFN=0;ADD CHANNEL: BN=0, PORT=1, STARTTS=1, ENDTS=31, IFN=1;ADD CHANNEL: BN=0, PORT=2, STARTTS=1, ENDTS=31, IFN=2;ADD CHANNEL: BN=0, PORT=3, STARTTS=1, ENDTS=31, IFN=3;MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=0, DESP="VT0-0", IFMP=YES, VT=0;MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=1, DESP="VT0-1", IFMP=YES, VT=0;MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=2, DESP="VT1-0", IFMP=YES, VT=1;MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=3, DESP="VT1-1", IFMP=YES, VT=1;MOD IPIF: IFT=VT, BT=HRB, BN=0, IFN=0, DESP="VT0", BEARBW=0, RPTROUTE=YES;MOD IPIF: IFT=VT, BT=HRB, BN=0, IFN=1, DESP="VT1", BEARBW=0, RPTROUTE=YES;

NOTE

When the bearer bandwidth is configured, the maximum bearer bandwidth of a channel is 64 kbit/s. Theinterface in the example is used to transmit control packets, and thus the bearer bandwidth is set to 0.

ADD IPADDR: BT=HRB, BN=0, IFT=VT, IFN=0, IPADDR="10.1.1.7", MASK="255.255.255.0";ADD IPADDR: BT=HRB, BN=0, IFT=VT, IFN=1, IPADDR="10.1.1.8", MASK="255.255.255.0";


Configuring MGW Control Data




10-23


About This Chapter

This describes how to configure the media gateway (MGW) control data. The standard MGWcontrol protocol H.248 is used between the UMG8900 and the media gateway controller (MGC)to control and manage the MGC on the UMG8900 and achieve the switching and processing ofthe voice service and data service.

11.1 Configuring MGW dataThis describes how to configure the virtual media gateway (VMGW) ID, media gatewaycontroller (MGC) ID, and media gateway (MGW) control data.

11.2 Configuring the LinkThis describes how to configure the H.248 link in different bearer modes.

11.3 Activating the VMGWThis describes how to activate the virtual media gateway (VMGW) on which the H.248 link isconfigured.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 11 Configuring MGW Control Data


11-1

11.1 Configuring MGW dataThis describes how to configure the virtual media gateway (VMGW) ID, media gatewaycontroller (MGC) ID, and media gateway (MGW) control data.

Prerequisitel The network management system (NMS) interface is correctly configured.

l The MGW control interface is correctly configured.

Index Mapping of Configuration Command ParametersFigure 11-1 shows the index mapping of the configuration command parameters.

Figure 11-1 Index mapping of the configuration command parameters of the MGW Data

SET VMGW

VMGWID

ADD MGC

VMGWID




ParameterName

UMG8900 InterconnectedDevice 1 (MGC)

InterconnectedDevice 2 (DNSServer)

Virtualmediagateway ID

<Virtual mediagateway id>

- -

Virtualmediagateway ID

l In domainmode:<Virtualmedia gatewayMID>_1

l In IP mode:<Virtual mediagateway MID>_2

l In device mode:<Virtual mediagateway MID>_3

- -

11 Configuring MGW Control DataHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

ParameterName



MasterMGC ID

<Media gatewaycontroller No.>_1

- -

Slave MGCID


- -

MasterMGC IDtype

The same as that of thepeer device

<Media gatewaycontroller MIDtype>_1

-

Slave MGCID type



-

MasterMGC ID


<Media gatewaycontroller MID>_1

-

Slave MGCID



-

IP address ofthe masterDNS server


- <DNS IP address>_1

IP address ofthe slaveDNS server





Parameter Name Data

Virtual media gatewayID

<Virtual media gateway id>

Master MGC ID <Media gateway controller No.>_1

Slave MGC ID <Media gateway controller No.>_2

Procedure

Step 1 Run SET VMGW to set the virtual media gateway (VMGW). The VMGW ID can be in thefollowing formats: domain name, IP address, and device name.

l Domain name:

SET VMGW: VMGWID=<Virtual media gateway id>, MIDTYPE=DOMAIN,MID=<Virtual media gateway MID>_1;



11-3

l IP address:SET VMGW: VMGWID=<Virtual media gateway id>, MIDTYPE=IP, MID=<Virtualmedia gateway MID>_2;

l Device name:SET VMGW: VMGWID=<Virtual media gateway id>, MIDTYPE=DEVICENAME,MID=<Virtual media gateway MID>_3;

Step 2 Run ADD MGC to add the master MGW controller.ADD MGC: VMGWID=<Virtual media gateway id>, MGCIDX=<Media gateway controllerNo.>_1, MIDTYPE=<Media gateway controller MID type>_1, MID=<Media gatewaycontroller MID>_1, MSS=MASTER;

Step 3 Run ADD MGC to add the slave MGW controller. If no dual homing is used in the networking,skip the step. The UMG8900 can support up to two slave MGCs.ADD MGC: VMGWID=<Virtual media gateway id>, MGCIDX=<Media gateway controllerNo.>_2, MIDTYPE=<Media gateway controller MID type>_2, MID=<Media gatewaycontroller MID>_2, MSS=SLAVE;

Step 4 When the MGW ID or MGW controller ID is in the format of domain name, run SETDNSSVR to set the DNS server. If the ID type of the MGW and MGW controller is in the formatof IP address or Device name, skip the step.1. Configure the master DNS server.

SET DNSSVR: FLAG=MASTER, IPADDR=<DNS IP address>_1;2. Configure the slave DNS server.

SET DNSSVR: FLAG=SLAVE, IPADDR=<DNS IP address>_2;

----End




IP Network

Master MGC Slave MGC

UMG8900

IP address: 192.168.0.1

Port No.: 3333

IP address: 172.16.0.1

Port No.: 2222


Port No.: 3333/2222

Example script


Configuration Guide


Issue 02 (2008-05-07)

SET VMGW: VMGWID=0, MIDTYPE=IP, MID="10.1.1.1:3333";ADD MGC: VMGWID=0, MGCIDX=0, MIDTYPE=IP, MID="192.168.0.1:3333", MSS=MASTER;ADD MGC: VMGWID=0, MGCIDX=1, MIDTYPE=IP, MID="172.16.0.1:2222", MSS=SLAVE;

PostrequisiteAfter configuring the MGW control data, configure the link data based on the selected transportlayer protocol.l Configuring the Link over UDP

l Configuring the Link over SCTP

11.2 Configuring the LinkThis describes how to configure the H.248 link in different bearer modes.

11.2.1 Configuring the Link over UDPThis describes how to configure the H.248 control link over the User Datagram Protocol (UDP).

11.2.2 Configuring the H.248 Link over SCTPThis describes how to configure the H.248 control link over the Simple Control TransmissionProtocol (SCTP).

11.2.3 Configuring the H.245 LinkThis describes how to configure the control link over the H.245 protocol.

11.2.1 Configuring the Link over UDPThis describes how to configure the H.248 control link over the User Datagram Protocol (UDP).

Prerequisitel The MGW control interface is correctly configured.

l The MGW control data is correctly set.





11-5



IP address of MGWcontrol interfaces


l 10.1 Configuring the PhysicalInterface in Single-FrameNetworking Mode

l 10.2 Configuring the PhysicalInterface in SSM-256 Self-Cascading Mode


l 10.4 Configuring the PhysicalInterface in Mixed CascadingMode

l 10.5 Configuring the E1 PhysicalInterface Carrying IP SignalingPackets

Virtual mediagateway ID


11.1 Configuring MGW data

Master MGC ID <Media gatewaycontroller No.>_1


Slave MGC ID <Media gatewaycontroller No.>_2





ParameterName

UMG8900 Interconnected Device (MGC)

Coding codec type <Codec type> The same as that of the peer device

UDP port No. tothe master MGC

<Local UDP port No.>_1 The same as that of the peer device

UDP port No. tothe slave MGC


IP address of themaster MGC


<Peer Master address>_1

IP address of theslave MGC



UDP port No. tothe master MGC


<Peer UDP port No.>_1


Configuration Guide


Issue 02 (2008-05-07)

ParameterName


UDP port No. tothe slave MGC



H.248 signalinglink No. to themaster MGC

<H248 signaling linkNo.>_1

-

H.248 signalinglink No. to theslave MGC


-

Procedure

Step 1 Run SET H248PARA to set the H.248 parameter. Set Transfer protocol type to UDP.SET H248PARA: VMGWID=<Virtual media gateway id>,CT=<Codec type>, TT=UDP;

Step 2 Run ADD H248LNK to add the H.248 links to the master MGC. To facilitate management,configure H.248 links over UDP.ADD H248LNK: LINKID=<H248 signaling link No.>_1, VMGWID=<Virtual mediagateway id>, MGCIDX=<Media gateway controller No.>_1, TT=UDP,LOCALIP=<Interface IP address>_1, LOCALPORT=<Local UDP port No.>_1,PEERIP=<Peer Master address>_1, PEERPORT=<Peer UDP portNo.>_1,LNKNAME=AH248_1;

Step 3 Run ADD H248LNK to add the H.248 links to the slave MGC. The H.248 signaling link No.cannot conflict with the No. of the signaling link to the master MGC.ADD H248LNK: LINKID=<H248 signaling link No.>_2, VMGWID=<Virtual mediagateway id>, MGCIDX=<Media gateway controller No.>_2, TT=UDP,LOCALIP=<Interface IP address>_1, LOCALPORT=<Local UDP port No.>_2,PEERIP=<Peer Master address>_2, PEERPORT=<Peer UDP port No.>_2,LNKNAME=AH248_1;

----End





11-7


IP Network


UMG8900

IP address: 192.168.0.1

UDP port No.: 2944


UDP port No.: 2944


UDP port No.: 2945

Example script

SET H248PARA: VMGWID=0, TT=UDP;

ADD H248LNK: LINKID=0, VMGWID=0, MGCIDX=0, TT=UDP, LOCALIP="10.1.1.1", LOCALPORT=2945, PEERIP="192.168.0.1", PEERPORT=2944, LNKNAME="Master MGC Lnk1";ADD H248LNK: LINKID=1, VMGWID=0, MGCIDX=1, TT=UDP,LOCALIP="10.1.1.1", LOCALPORT=2945, PEERIP="172.16.0.1", PEERPORT=2944, LNKNAME="Slave MGC Lnk1";

PostrequisiteAfter configuring the H.248 links, activate the VMGW.

Activating the VMGW

11.2.2 Configuring the H.248 Link over SCTPThis describes how to configure the H.248 control link over the Simple Control TransmissionProtocol (SCTP).

Prerequisitel The MGW control interface is correctly configured.

l The MGW data is correctly set.




Configuration Guide


Issue 02 (2008-05-07)



IP address 1 ofMGW controlinterfaces


l 10.1 Configuring the Physical Interfacein Single-Frame Networking Mode

l 10.2 Configuring the Physical Interfacein SSM-256 Self-Cascading Mode


l 10.4 Configuring the Physical Interfacein Mixed Cascading Mode


IP address 2 ofMGW controlinterfaces


l 10.1 Configuring the Physical Interfacein Single-Frame Networking Mode



l 10.4 Configuring the Physical Interfacein Mixed Cascading Mode




Master MGC ID <Media gatewaycontroller No.>_1


Slave MGC ID <Media gatewaycontroller No.>_2


Board type <Board type> 8 Configuring Frames and Boards

Board No. <Board No.> 8 Configuring Frames and Boards

Frame No. <Frame No.> 8 Configuring Frames and Boards

Slot No. <Slot No.> 8 Configuring Frames and Boards

Board position <BoardPosition>






11-9


ParameterName



Checksumalgorithm

<Checksum algorithm> The same as that of the peer device

Path mode <path mode> -

SCTP port No. tothe master MGC

<Local SCTP port No.>_1 The same as that of the peer device

SCTP port No. tothe slave MGC


IP address 1 of themaster MGC





<Peer Slave address>_1

IP address 1 of theslave MGC








<Peer SCTP port No.>_1






-



-

SubBoard No. <SubBoard No.> -

Procedure

Step 1 Run SET H248PARA to set the H.248 parameter. Set Transfer protocol type to SCTP.SET H248PARA: VMGWID=<Virtual media gateway id>, CT=<Codec type>, TT=SCTP;

Step 2 Run SET SCTPINIT to set the SCTP initialization parameter.SET SCTPINIT: BT=<Board type>, BN=<Board No.>, CHKSUM=<Checksumalgorithm>;

Step 3 Check whether the SCTP multi-homing networking is adopted.


Configuration Guide


Issue 02 (2008-05-07)

l If the SCTP multi-homing networking is not adopted, perform Step 4 and Step 5.l If the SCTP multi-homing networking is adopted, perform Step 6 and Step 7.

Step 4 Run ADD H248LNK to add the H.248 links to the master MGC. To facilitate management,configure H.248 links over SCTP with the link No. greater than 47. Set path mode toUnsupported.ADD H248LNK: LINKID=<H248 signaling link No.>_1, VMGWID=<Virtual mediagateway id>, MGCIDX=<Media gateway controller No.>_1, TT=SCTP,PTHMODE=UNSUPP, LOCALIP=<Interface IP address>_1, LOCALPORT=<LocalSCTP port No.>_1, PEERIP=<Peer Master address>_1, PEERPORT=<Peer SCTP portNo.>_1, LINKNAME=AH248_1, FN=<Frame No.>, SN=<Slot No.>, BP=<BoardPosition>, SBN=<SubBoard No.>;

NOTE

By default, SubBoard No. is Mother Board. SubBoard No. is set to No. 0 SubBoard or No. 1SubBoard only during configuration of the UG02OMB.

Step 5 If dual homing is configured, run ADD H248LNK to add the H.248 links to the slave MGC.The H.248 signaling link No. cannot conflict with the number of the signaling link to the masterMGC. Set path mode to Unsupported.If no dual-homing is configured, do not perform thisstep.ADD H248LNK: LINKID=<H248 signaling link No.>_2, VMGWID=<Virtual mediagateway id>, MGCIDX=<Media gateway controller No.>_2, TT=SCTP,PTHMODE=UNSUPP, LOCALIP=<Interface IP address>_1, LOCALPORT=<LocalSCTP port No.>_2, PEERIP=<Peer Master address>_2, PEERPORT=<Peer SCTP portNo.>_2, LINKNAME=AH248_3, FN=<Frame No.>, SN=<Slot No.>, BP=<BoardPosition>, SBN=<SubBoard No.>;

Step 6 Run ADD H248LNK to add the H.248 links to the master MGC. To facilitate management,configure H.248 links over SCTP with the link No. greater than 47. Set path mode to twopath or four path based on the actual conditions. By default, path mode is two path. If no dualhoming is configured, the configuration is complete.ADD H248LNK: LINKID=<H248 signaling link No.>_1, VMGWID=<Virtual mediagateway id>, MGCIDX=<Media gateway controller No.>_1, TT=SCTP, PTHMODE=<pathmode>, LOCALIP=<Interface IP address>_1, LOCALPORT=<Local SCTP port No.>_1,PEERIP=<Peer Master address>_1, PEERPORT=<Peer SCTP port No.>_1,SLIP=<Interface IP address>_2, SRIP=<Peer Slave address>_1, LINKNAME=AH248_2,FN=<Frame No.>, SN=<Slot No.>, BP=<Board Position>, SBN=<SubBoard No.>;

Step 7 If dual homing is configured, run ADD H248LNK to add the H.248 links to the slave MGC.The H.248 signaling link No. cannot conflict with the number of the signaling link to the masterMGC. Set path mode to two path or four path based on the actual conditions. By default, pathmode is two path.ADD H248LNK: LINKID=<H248 signaling link No.>_2, VMGWID=<Virtual mediagateway id>, MGCIDX=<Media gateway controller No.>_2, TT=SCTP, PTHMODE=<pathmode>, LOCALIP=<Interface IP address>_2, LOCALPORT=<Local SCTP port No.>_2,PEERIP=<Peer Master address>_2, PEERPORT=<Peer SCTP port No.>_2,SLIP=<Interface IP address>_2, SRIP=<Peer Slave address>_1, LINKNAME=AH248_4,FN=<Frame No.>, SN=<Slot No.>, BP=<Board Position>, SBN=<SubBoard No.>;

----End




11-11



IP Network


UMG8900

IP address 1: 192.168.0.1

SCTP port No.: 3333

IP address 1: 172.16.0.1

SCTP port No.: 2222

IP address 1: 10.1.1.1

SCTP port No.: 3333/2222

IP address 2: 192.168.0.2 IP address 2: 172.16.0.2

IP address 2: 10.1.1.11

Example script

SET H248PARA: VMGWID=0, TT=SCTP; SET SCTPINIT: BT=PPU, BN=0, CHKSUM=CRC32;//Configure an H.248 link to the master MGC and set SCTP multi-homing. ADD H248LNK: LINKID=50, VMGWID=0, MGCIDX=0, TT=SCTP, PTHMODE=TWOPATH, LOCALIP="10.1.1.1", LOCALPORT=3333, PEERIP="192.168.0.1", PEERPORT=3333, SLIP="10.1.1.11", SRIP="192.168.0.2", LINKNAME="AH248_1", FN=0, SN=4, BP=BACK, SBN=MTHBRD;

//Configure an H.248 link to the slave MGC and set SCTP multi-homing. ADD H248LNK: LINKID=51, VMGWID=0, MGCIDX=1, TT=SCTP, PTHMODE=TWOPATH, LOCALIP="10.1.1.1", LOCALPORT=2222, PEERIP="172.16.0.1", PEERPORT=2222, SLIP="10.1.1.11", SRIP="172.16.0.2", LINKNAME="AH248_2", FN=0, SN=4, BP=BACK, SBN=MTHBRD;

PostrequisiteAfter configuring the H.248 links, go to activate the VMGW.

11.3 Activating the VMGW

11.2.3 Configuring the H.245 LinkThis describes how to configure the control link over the H.245 protocol.

Prerequisitel The media gateway (MGW) control interface is correctly configured.


l The H.248 link is correctly configured.




Configuration Guide


Issue 02 (2008-05-07)



IP address of gatewaycontrol interfaces


l Configuring Signaling Interfaces inSingle-Frame Networking Mode

l Configuring Signaling Interfaces inSSM-256 Self-Cascading Mode

l Configuring Signaling Interfaces inSSM-32 Self-Cascading Mode

l Configuring Signaling Interfaces inSSM-256 and SSM-32 Mixed CascadingMode

l Configuring Signaling Interfaces WhenE1 Physical Interfaces Carry IPSignaling Packets


<Virtualmedia gatewayid>


Master MGC ID <MediagatewaycontrollerNo.>_1


Slave MGC ID <MediagatewaycontrollerNo.>_2


Frame No. <Frame No.> Configuring Frames and Boards

Slot No. <Slot No.> Configuring Frames and Boards

Board position <BoardPosition>

Configuring Frames and Boards




ParameterName

UMG8900 Interconnected Device(MGC)









11-13

ParameterName

UMG8900 Interconnected Device(MGC)

Port No. to themaster MGC


<Peer port No.>_1

Port No. to theslave MGC


<Peer port No.>_2

Port No. of H.245signaling links tothe master MGC

<Local port No.>_1 The same as that of the peerdevice

Port No. of H.245signaling links tothe slave MGC



<H245 signaling link No.>_1 -



Procedure

Step 1 Run ADD H245LNK to add the H.245 signaling link to the master MGC.ADD H245LNK: LINKID=<H245 signaling link No.>_1, VMGWID=<Virtual mediagateway id>, MGCIDX=<Media gateway controller No.>_1, LOCALIP=<Interface IPaddress>_1, LOCALPORT=<Local port No.>_1, PEERIP=<Peer Master address>_1,PEERPORT=<Peer port No.>_1, FN=<Frame No.>, SN=<Slot No.>, BP=<BoardPosition>;

Step 2 Run ADD H245LNK to add the H.245 signaling link to the slave MGC.ADD H245LNK: LINKID=<H245 signaling link No.>_2, VMGWID=<Virtual mediagateway id>, MGCIDX=<Media gateway controller No.>_2, LOCALIP=<Interface IPaddress>_1, LOCALPORT=<Local UDP port No.>_1, PEERIP=<Peer Masteraddress>_2, PEERPORT=<Peer port No.>_2, FN=<Frame No.>, SN=<Slot No.>,BP=<Board Position>;

----End




Configuration Guide


Issue 02 (2008-05-07)

Figure 11-5 Networking Examples

IP Network


UMG8900

IP address: 192.168.0.1 IP address: 172.16.0.1

IP address: 10.1.1.1Port No. of H.245 links: 5000/5001

Port No. of H.245 links: 5001Port No. of H.245 links: 5000

Example script

ADD H245LNK: LINKID=0, VMGWID=0, MGCIDX=0, TT=SCTP, LOCALIP="192.168.1.1", LOCALPORT=2944, PEERIP="192.168.10.1", PEERPORT=2945, FN=1, SN=4, BP=BACK;ADD H245LNK: LINKID=1, VMGWID=0, MGCIDX=0, LOCALIP="10.1.1.1", LOCALPORT=5002, PEERIP="172.16.0.1", PEERPORT=5003, FN=1, SN=3, BP=FRONT;

PostrequisiteAfter configuring the H.245 links, go to activate the VMGW.

Activating the VMGW

11.3 Activating the VMGWThis describes how to activate the virtual media gateway (VMGW) on which the H.248 link isconfigured.

Prerequisitel The media gateway (MGW) control interface is correctly configured.


l The H.248 link is correctly configured.





Virtual media gateway ID <Virtualmediagateway id>




11-15

ProcedureRun ACT VMGW to activate the VMGW.ACT VMGW: VMGWID=<Virtual media gateway id>;

----End

ExampleExample scriptACT VMGW: VMGWID=0;

PostrequisiteAfter configuring the MGW control data, configure the bearer data.


Configuration Guide


Issue 02 (2008-05-07)

12 Configuring TDM Bearer

About This Chapter

This describes how to configure the time division multiplexing (TDM) bearer data including theTDM interface, TDM timeslot, TDM trunk group management, and office direction information.In the actual networking application, the service exchange between the UMG8900 and and publicswitching telephone network (PSTN) switch is based on the TDM bearer. The connectionbetween the UMG8900 and other media gateways (MGWs) can also be based on the TDMbearer.

12.1 Configuring the TDM InterfaceThis describes how to configure the time division multiplexing (TDM) interface including howto configure the E1/T1 interface, E3/T3 interface, synchronous digital hierarchy (SDH) interface,and SDH interface protection.

12.2 Configuring the TDM TimeslotThis describes how to configure the time division multiplexing (TDM) timeslot.

12.3 Configuring Trunk Group ManagementThis describes how to configure the time division multiplexing (TDM) trunk group management.

12.4 Configuring Office Direction InformationThis describes how to configure the office direction information.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 12 Configuring TDM Bearer


12-1

12.1 Configuring the TDM InterfaceThis describes how to configure the time division multiplexing (TDM) interface including howto configure the E1/T1 interface, E3/T3 interface, synchronous digital hierarchy (SDH) interface,and SDH interface protection.

12.1.1 Configuring the E1/T1 InterfaceThis describes how to configure the E1/T1 interface.


12.1.3 Configuring the SDH Interface on the S2L/S1LThis describes how to configure the synchronous digital hierarchy (SDH) interface data. Youneed to configure the physical interface based on the actual physical connection. If you use theSDH interface of the S2L/S1L to access services, configure the SDH/synchronous opticalnetwork (SONET) optical interface.

12.1.4 Configuring SDH Interface ProtectionThis describes how to configure the synchronous digital hierarchy (SDH) interface protectiondata.







ParameterName

Data Input Source

Frame ID <Frame No.> 8 Configuring Frames and Boards




12 Configuring TDM BearerHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)


Parameter Name UMG8900 Interconnected Device

Start port No. <Start Port No.> -

End port No. <End Port No.> -

Frame format <Frame Structure> The same as that of the peerdevice

Tx line code structure <Tx line Code Structure> The same as that of the peerdevice

Rx line code structure <Rx line Code Structure> The same as that of the peerdevice

Distance Mode <Distance Mode> -

Procedure

Run SET E1PORT to set the E1/T1 interface.SET E1PORT: FN=<Board No.>, SN=<Slot No.>, SPN=<Start Port No.>, EPN=<End PortNo.>, FS=<Frame Structure>, TXCS=<Tx line Code Structure>, RXCS=<Rx line CodeStructure>, DISTANCE=<Distance Mode>;

----End

ExampleExample script//Set the attributes of ports 0 through 31 in slot 3 of frame 2. SET E1PORT: FN=2, SN=3, SPN=0, EPN=31, FS=DOUBLE_FRAME, TXCS=HDB3, RXCS=HDB3, DISTANCE=SHORT;

PostrequisiteAfter configuring the E1/T1 interface, configure other time division multiplexing (TDM)interfaces based on the requirements.

12.1.2 Configuring the E3/T3 Interface

12.1.3 Configuring the SDH Interface on the S2L/S1L






12-3




ParameterName

Data Input Source









Distance Mode <CommunicationDistance>

-

frame type <Frame type> The same as that of the peerdevice

Start channel No. <Start Chan No.> -

End channel No. <End Chan No.> -

Frame format <Frame mode> The same as that of the peerdevice

ProcedureStep 1 Run SET E3PORT to set the E3/T3 interface. For WorkMode, you can select E3, T3 or G.

747. The parameters vary based on the WorkMode.l Set WorkMode to E3

SET E3PORT:FN=<Frame No.>,SN=<Slot No.>,SPN=<Start Port No.>,EPN=<EndPort No.>,LN=E3;

l Set WorkMode to T3 or G747, The T3 is considered as an example.SET E3PORT:FN=<Frame No.>,SN=<Slot No.>,SPN=<Start Port No.>,EPN=<EndPort No.>,LN=T3,MODE=<Communication Distance>,TYPE=<Frame type>;

Step 2 Run SET E3FRM to set the E3/T3 channel attribute.SET E3FRM: FN=<Frame No.>, SN=<Slot No.>, SPN=<Start Port No.>, EPN=<End PortNo.>, SCN=<Start Chan No.>, ECN=<End Chan No.>, FRM=<Frame mode>;


Configuration Guide


Issue 02 (2008-05-07)

NOTE

l For E1 load type, that is in the G.747 or E3 mode, the parameters Double-Frame and CRC4-Multiframe are optional.

l For T1 load type, that is in the T3 mode, the parameters SuperFrame and Extended-SuperFrame areoptional.

----End

ExampleExample script//Set the work mode of ports 0 and 1 on the PIE in slot 2 of frame 1 to G.747, communication distance to the long mode, and frame type to M23. SET E3PORT:FN=1,SN=2,SPN=0,EPN=1,LN=G747,MODE=Long,TYPE=M23;

//Set the frame type of all the channels of ports 0 and 1 on the PIE in slot 2 of frame 1 to the super frame mode. SET E3FRM:FN=1, SN=2, SPN=0,EPN=1, SCN=0, ECN=27, FRM=DOUBLE_FRAME;

PostrequisiteAfter configuring the E3/T3 interface, configure other time division multiplexing (TDM)interfaces based on the requirements.

12.1.3 Configuring the SDH Interface on the S2L/S1L

12.1.3 Configuring the SDH Interface on the S2L/S1LThis describes how to configure the synchronous digital hierarchy (SDH) interface data. Youneed to configure the physical interface based on the actual physical connection. If you use theSDH interface of the S2L/S1L to access services, configure the SDH/synchronous opticalnetwork (SONET) optical interface.



Context

To ensure normal running of SDH/SONET transport channels, the UMG8900 has to keepconsistent with the interconnected device (probably an optical transport device) in terms of SDH/SONET overhead bytes. SDH/SONET overhead bytes of the S2L/S1L include C2, J2, J1 andJ0 bytes.

l The C2 byte specifies the multiplexing structure and payload status of a VC frame, suchas whether channels being loaded, bearer service type and mapping mode.

l The J2 byte is used to send lower order path access point identifier repeatedly to convincethe receiver that the connection to the sender end is normal.

l The J1 byte is used to send higher order path access point identifier repeatedly to convincethe receiver that the connection to the sender is normal.

l The J0 byte is used to send the access point identifier of the sending section repeatedly toconvince the receiver that the connection to the sender is normal.



12-5











SDH port No. <SDH port No.> -

E1/T1 channel No. <Channel No.> -

Receiving C2 byte <Receiving C2 byte> The same as that of the peerdevice

Transmitting C2 byte <Transmitting C2 byte> The same as that of the peerdevice

Receiving J0 byte <Receiving J0 byte> The same as that of the peerdevice

Transmitting J0 byte <Transmitting J0 byte> The same as that of the peerdevice





Frame type <Frame type> -

Frame mode 1 <Frame mode 1> The same as that of the peerdevice


Configuration Guide


Issue 02 (2008-05-07)


Load type <Load type> The same as that of the peerdevice

Start Channel No. <Start Channel No.> -

End Channel No. <End Channel No.> -

E1/T1 Frame format <Frame format> -

Period <Period> -

Status <Status> -



Parameter Name Data

SDH port No. <SDH port No.>

Procedure

Step 1 Run SET SDHFLAG to set the overhead bytes of the SDH interface. Configure the TDMinterface, and set Board Type to S1L or S2L. The S2L is considered as an example.

SET SDHFLAG: BT=S2L, BN=<Board No.>, PN=<SDH port No.>, CN=<Channel No.>,RxC2=<Receiving C2 byte>, TxC2=<Transmitting C2 byte>, RxJ0=<Receiving J0 byte>,TxJ0=<Transmitting J0 byte>, RxJ1=<Receiving J1 byte>, TxJ1=<Transmitting J1 byte>,RxJ2=<Receiving J2 byte>, TxJ2=<Transmitting J2 byte>;

Step 2 Run SET S2LPORT to set S2L/S1L interface attribute.

SET S2LPORT: BT=S2L, BN=<Board No.>, FT=<Frame type>, MODE=<Frame mode1>, TYPE=<Load type>;

Step 3 Run SET S2LFRM to set the frame format on the S2L/S1L port.

SET S2LFRM: BT=S2L, BN=<Board No.>, PN=<SDH port No.>, SRTCN=<Start ChannelNo.>, ENDCN=<End Channel No.>, FRAME=<Frame format>;

Step 4 Run SET PERMON to set the performance monitoring state to 15 minutes or 24 hours basedon actual requirements.

SET PERMON: BT=S2L, BN=<Board No.>, PN=<SDH port No.>, PERD=<Period>,STAT=<Status>;

Step 5 If the performance monitoring function is enabled, run SET PERTIME to set the start time forperformance monitoring. Otherwise, this step needs not be performed. Generally, the detectionis performed immediately.



12-7

SET PERTIME: BT=S2L, BN=<Board No.>, PN=<SDH port No.>, SD15=2007&07&13,ST15=15&29&34, SD24=2007&07&13, ST24=15&29&34;

----End

ExampleSET SDHFLAG: BT=S2L, BN=0, PN=0, RxC2=2, TxC2=2, RxJ1="1111", TxJ1="1111";SET S2LPORT: BT=S2L, BN=0, FT=SDH, MODE=HUAWEI, TYPE=E1;SET S2LFRM: BT=S2L, BN=0, PN=PORT0, SRTCN=0, ENDCN=0, FRAME=CEPT_BASIC_MODE;SET PERMON: BT=S2L, BN=0, PN=PORT0, PERD=P15MIN, STAT=DISABLE;

PostrequisiteAfter configuring the SDH interface, configure the SDH interface protection.

Configuring SDH Interface Protection

12.1.4 Configuring SDH Interface ProtectionThis describes how to configure the synchronous digital hierarchy (SDH) interface protectiondata.



l The SDH interface data is correctly set.

Index Mapping of Configuration Command Parameters

Figure 12-1 shows the index mapping of the configuration command parameters.

Figure 12-1 Index mapping of the configuration command parameters of the MGW data

ADD PG

ADD PGIF

SET WRTIME

SET SIGDEFECT

SET PG

PGIDTYPE

FN/SN/IFNPGID

PGIDCMD

PGIDWRTIME

PGIDSDFLAG


Configuration Guide


Issue 02 (2008-05-07)







SDH port No. <SDH port No.> Configuring SDH Interface on the S2L/S1L




Protection group No. <Protect group ID>

Interface type <Interface type>

Recover mode <Recover mode>

Operate mode <Operate mode>

Optical splitter mode <Optical Splitter mode>

Channel number <Channel number>

Recover time length (s) <Recover time length(s)>

SD flag <SD flag>

Interface ID <Interface No.>

Channel ID <Work/Protect Channel ID>

Operate mode <Command type>



Parameter Name Data




12-9

Procedure

Step 1 Run ADD PG to configure the protection group. For Protect type, you can selectAPS1PLUS1, APS1VSN, NONAPS1PLUS1 or NONAPS1VSN.

CAUTIONWhen APS1PLUS1 is selected, configure the boards to work in master/slave mode. If workchannels fail, switch over boards directly to start the protect channel. Therefore, all interfacesof boards configured with interface protection must be configured with protect groups.

l Set Protect type to APS1PLUS1. In APS1PLUS1 mode, configure the boards to work inmaster/slave mode. The work channel is configured on the master board and the protectchannel is configured on the slave board.ADD PG: PGID=<Protect group ID>, IFT=<Interface type>, TYPE=APS1PLUS1,RTVM=<Recover mode>, OPM=<Operate mode>, OPTSM=<Optical Splitter mode>;

l Set Protect type to APS1VSN. In APS1VSN mode, configure the boards to work in load-sharing mode.ADD PG: PGID=<Protect group ID>, IFT=<Interface type>, TYPE=APS1VSN,CHNNUM=<Channel number>;

l Set Protect type to NONAPS1PLUS1.ADD PG: PGID=<Protect group ID>, IFT=<Interface type>,TYPE=NONAPS1PLUS1;

l Set Protect type to NONAPS1VSN.ADD PG: PGID=<Protect group ID>, IFT=<Interface type>, TYPE=NONAPS1VSN,CHNNUM=<Channel number>;

Step 2 When Recover mode is set to Recover, run SET WRTIME to configure the recover time length.SET WRTIME: PGID=<Protect group ID>, WTIME=<Recover time length(s)>;

Step 3 If signaling degrade is required, run SET SIGDEFECT to set the signal degrade flag. Set SDflag to SD enable.SET SIGDEFECT: PGID=<Protect group ID>, SDFLAG=<SD flag>;

Step 4 Run ADD PGIF to configure the protection group to which the optical interface belongs to.Before adding work channels, add the protection channels of the protection group. The protectionchannel No. in the protection group is always 0.ADD PGIF: FN=<Frame No.>, SN=<Slot No.>, IFN=<SDH port No.>, PGID=<Protectgroup ID>, CHN=<Work/Protect Channel ID>;

Step 5 Run SET PG to enable the protection controller.SET PG: PGID=<Protect group ID>, CMDT=<Command type>;

----End

ExampleExample scriptl Configure interface protection in APS 1+1 mode


Configuration Guide


Issue 02 (2008-05-07)

//Configure interfaces on two S2L boards to be in the APS 1+1 backup protection mode. Configure the boards to work in master/slave mode. Configure protect groups for both the two interfaces of the S2L.ADD PG: PGID=0, IFT=SDH/SONET, TYPE=APS1PLUS1, RTVM=RECOVER, OPM=BIDIRECTIONAL, OPTSM=DISABLE;ADD PG: PGID=1, IFT=SDH/SONET, TYPE=APS1PLUS1, RTVM=RECOVER, OPM=BIDIRECTIONAL, OPTSM=DISABLE;ADD PGIF: FN=2, SN=3, IFN=0, PGID=0, CHN=0;ADD PGIF: FN=2, SN=3, IFN=1, PGID=1, CHN=0;ADD PGIF: FN=2, SN=2, IFN=0, PGID=0, CHN=1;ADD PGIF: FN=2, SN=2, IFN=1, PGID=1, CHN=1;

//Start the protection group protocol controller. SET PG: PGID=0, CMDT=START_CONTROLLER;SET PG: PGID=1, CMDT=START_CONTROLLER;

l Configure interface protection in APS 1:N mode//Configure interfaces on four S2L boards to be in the 1:3 backup protection mode. Configure the boards to work in load sharing mode.ADD PG: PGID=0, IFT=SDH/SONET, TYPE=APS1VSN, CHNNUM=3;SET WRTIME: PGID=0, WTIME=6;SET SIGDEFECT: PGID=0, SDFLAG=SD_ENABLE;ADD PGIF: FN=2, SN=13, IFN=0, PGID=0, CHN=0;ADD PGIF: FN=2, SN=10, IFN=0, PGID=0, CHN=1;ADD PGIF: FN=2, SN=11, IFN=0, PGID=0, CHN=2;ADD PGIF: FN=2, SN=12, IFN=0, PGID=0, CHN=3;

//Start the protection group protocol controller. SET PG: PGID=0, CMDT=START_CONTROLLER;

l Configure interface protection in non APS 1+1 mode//Configure interfaces on two E1G boards to be in the 1+1 backup protection mode.ADD PG: PGID=0, IFT=GE, TYPE=NONAPS1PLUS1;ADD PGIF: FN=2, SN=15, IFN=0, PGID=0, CHN=0;ADD PGIF: FN=2, SN=14, IFN=0, PGID=0, CHN=1;

//Start the protection group protocol controller. SET PG: PGID=0, CMDT=START_CONTROLLER;

12.2 Configuring the TDM TimeslotThis describes how to configure the time division multiplexing (TDM) timeslot.

PrerequisiteThe TDM interface data is correctly set.












12-11

l Table 12-12 lists the data needed in this step. The interconnected device column in the




Start TID <Start TID>

End TID <End TID>

CASATTR No. <CASATTR No.>



Parameter Name Data


End TID <End TID>

ProcedureRun ADD TDMIU to configure the TDM timeslot.l When the UMG8900 interconnects with the public switched telephone network (PSTN)

switch, public branch switch (PBX), and other media gateways (MGWs), set Relay typeto Extern.ADD TDMIU: BT=<Board type>, BN=<Board No.>, TIDFV=<Start TID>,TIDLV=<End TID>, VMGWID=<Virtual media gateway id>, RT=EXTERN;

l When the UMG8900 interconnects with the remote switching module (RSM)/user accessmode (UAM) and you configure the protection channels in the 1:N backup protection group,set Relay type to Inside.ADD TDMIU: BT=<Board type>, BN=<Board No.>, TIDFV=<Start TID>,TIDLV=<End TID>, VMGWID=<Virtual media gateway id>, RT=INSIDE;

l When the UMG8900 interconnects with the V5 access network (AN), set Relay type toV5.ADD TDMIU: BT=<Board type>, BN=<Board No.>, TIDFV=<Start TID>,TIDLV=<End TID>, VMGWID=<Virtual media gateway id>, RT=V5;

l When the UMG8900 interconnects with the PBX or PSTN switch that runs the R2 channelassociated signaling (CAS), set Relay type to R2.ADD TDMIU: BT=<Board type>, BN=<Board No.>, TIDFV=<Start TID>,TIDLV=<End TID>, VMGWID=<Virtual media gateway id>, RT=R2,CASNO=<CASATTR No.>;

l When the UMG8900 interconnects with the PBX or PSTN switch that runs the No.5 CAS,set Relay type to No5.


Configuration Guide


Issue 02 (2008-05-07)

ADD TDMIU: BT=<Board type>, BN=<Board No.>, TIDFV=<Start TID>,TIDLV=<End TID>, VMGWID=<Virtual media gateway id>, RT=NO5;

l When the UMG8900 interconnects with the PBX or PSTN switch that runs the R1 CAS,set Relay type to R1.ADD TDMIU: BT=<Board type>, BN=<Board No.>, TIDFV=<Start TID>,TIDLV=<End TID>, VMGWID=<Virtual media gateway id>, RT=R1;

l When the UMG8900 interconnects with the PBX or PSTN switch that runs the R15 CAS,set Relay type to R15.ADD TDMIU: BT=<Board type>, BN=<Board No.>, TIDFV=<Start TID>,TIDLV=<End TID>, VMGWID=<Virtual media gateway id>, RT=R15;

----End

ExampleExample script//Set the TDM timeslot of the E32 in slot 1 of frame 2. ADD TDMIU: BT=E32, BN=1, TIDFV=0, TIDLV=1023, VMGWID=0, RT=EXTERN;

PostrequisiteAfter configuring the TDM timeslot, configure the TDM trunk group management and officedirection information based on the requirements.

l 12.3 Configuring Trunk Group Management

l 12.4 Configuring Office Direction Information

If not required, configure the TDM bearer and then configure other bearer data.

l 13 Configuring IP Bearer

l 14 Configuring Signaling Transfer

12.3 Configuring Trunk Group ManagementThis describes how to configure the time division multiplexing (TDM) trunk group management.

Prerequisitel The TDM interface data is correctly set.

l The TDM timeslot is correctly configured.

Context

CAUTIONFor the trunk group configuration, the UMG8900 and the interconnected media gatewaycontroller (MGC) must support the function of circuit wild routing; otherwise, the service isinterrupted.



12-13

The trunk group indicates the TID resource pool configured on the UMG8900. The trunk groupmanagement function enables the UMG8900 to choose the TID function in the specific rangeon the MGC. At the same time, the TID resources between the VMGWs can be shared.

In general, the MGC sends the command that distributes available TID resource to a specificcall to the VMGW. In this case, the TID resource is set to belong to the VMGW by runningADD TDMIU in advance. In other words, the TID resource is static and fixed.

After the trunk group management is configured, the MGC does not require the specific TIDresource when the MGC applies for TID resource with a VMGW. In this case, one TID rangeor a trunk group is required to send the messages to the VMGW. Then the VMGW allocates theavailable TID resources to calls according to certain rules within the specific range and finishesthe connection of calls with the TID resources. In other words, the TID belongs to the VMGWbefore the call is over. After the call, the TID resource can be released for availability of otherVMGWs.

Data Planningl Table 12-14 lists the data needed in this step. The interconnected device column in the




Trunk group No. <TG No.>

Trunk group information <TG No. Info>


End TID <End TID>

Procedure

Step 1 Run ADD TG to add the trunk group.ADD TG: TGNO=<TG No.>, TGINFO=<TG No. Info>;

Step 2 Run ADD TGTID to add the TID termination of the specified trunk group. Different trunk typesof TIDs can be configured in a trunk group. The TID can be the external timeslot, No.5 timeslot,or R2 timeslot; however, the V5 timeslot and internal timeslot cannot be added to the trunkgroup. The number of TIDs in the trunk group is unlimited. The TIDs can assigned to multipleports.ADD TGTID: TGNO=<TG No.>, TIDB=<Start TID>, TIDE=<End TID>;

NOTE

l When a TID termination is added to a trunk group, the VMGW No. to which it belongs is invalid. TheVMGW to which it belongs is determined when the CMU sends the networking message.

l The MGC can specify the range in multiple ways when allocating timeslots, including by trunk groupNo., by frame No./slot No./optical port No./port No. in hierarchy or by TID range. The MGC can alsospecify a specific TID.

----End


Configuration Guide


Issue 02 (2008-05-07)

ExampleExample script//Add TIDs to a trunk group. Set TG No. to 54, Start TID to 72, and End TID to 95. ADD TG: TGNO=54, TGINFO="aaaa"; ADD TGTID: TGNO=54, TIDB=72, TIDE=95;

PostrequisiteAfter configuring the TDM trunk group management data, configure the office directioninformation based on the requirements.

12.4 Configuring Office Direction Information

If not required, configure IP bearer data.


12.4 Configuring Office Direction InformationThis describes how to configure the office direction information.

Prerequisitel The TDM interface data is correctly set.

l The TDM timeslot is correctly configured.

ContextIf a straight voice circuit exists between a switching office and the UMG8900, the switchingoffice is an office direction of the UMG8900.

The configuration in this step does not affect service provisioning; however, it is recommendedthat you configure this information so that office names can be displayed in related alarms, thusfacilitating management.

Configuring office direction information on the UMG8900 is to identify the office to which theport on the TDM interface board is connected. In this way, maintenance staff can know the officedirection that the trunk circuit belongs to by checking the configuration information.










12-15



Office No. <Office No.>

Port No. <Port No.>

Start port No. <Start Port No.>

End port No. <End Port No.>

Procedure

Step 1 Run ADD OFCTKC to add the trunk group. Set Board type to E32, T32, S2L, S1L, or PIE.l When Board type is set to E32 or T32, the setting of E32 is considered as an example.

ADD OFCTKC: OFC=<Office No.>, BT=E32, BN=<Board No.>, PNSV=<Start PortNo.>, PNEV=<End Port No.>;

l If Board type is set to PIE, S2L, or S1L, take PIE as an example.ADD OFCTKC: OFC=<Office No.>, BT=PIE, BN=<Board No.>, PN=<Port No.>;

Step 2 Run ADD OFCNAME to add the office name. The office to MGW 1 of city A is considered asan example.ADD OFCNAME: OFCNO=<Office No.>, OFCINFO="AMGW1";

----End

ExampleExample script//Set the office information of the E32 in slot 1 of frame 2. ADD OFCTKC: OFC=0, BT=E32, BN=1, PNSV=0, PNEV=31; ADD OFCNAME: OFCNO=0, OFCINFO="AMGW1";

PostrequisiteAfter configuring the office direction information, configuring the time division multiplexing(TDM) bearer is complete. Then, configure IP bearer data.



Configuration Guide


Issue 02 (2008-05-07)


About This Chapter

This describes how to configure the Internet Protocol (IP) bearer data including the IP interface,IP interface address, IP interface protection, and gateway IP address. Configure the IP bearerdata when the UMG8900 acts as a media gateway (MGW) in the core network and theconnections with other MGWs in the core network are based on the IP bearer.

13.1 Configuring IP InterfaceThis describes how to configure the Internet Protocol (IP) interface including the fast Ethernet(FE) interface, gigabit Ethernet (GE) interface, asynchronous transfer mode (ATM)interface,and IP over E1 (IPoE1) interface.

13.2 Configuring the IP Interface AddressThis describes how to configure the Internet Protocol (IP) interface address.

13.3 Configuring IP Interface ProtectionThis describes how to configure the Internet Protocol (IP) interface protection.

13.4 Configuring the Gateway AddressThis describes how to configure the gateway address.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 13 Configuring IP Bearer


13-1

13.1 Configuring IP InterfaceThis describes how to configure the Internet Protocol (IP) interface including the fast Ethernet(FE) interface, gigabit Ethernet (GE) interface, asynchronous transfer mode (ATM)interface,and IP over E1 (IPoE1) interface.

13.1.1 Configuring the FE InterfaceThis describes how to configure the fast Ethernet (FE) interface.

13.1.2 Configuring the GE InterfaceThis describes how to configure the gigabit Ethernet (GE) interface.

13.1.3 Configuring the ATM InterfaceThis describes how to configure the asynchronous transfer mode (ATM) interface.

13.1.4 Configuring the IP over E1 InterfaceThis describes how to configure the IP over E1 (IPoE1) interface.

13.1.1 Configuring the FE InterfaceThis describes how to configure the fast Ethernet (FE) interface.



Context

The Local Area Network (LAN) includes networks such as the Ethernet and the token ringnetwork. As an important LAN networking technology, the Ethernet is flexible and easy to berealized.

At present, the UMG8900 supports Ethernet interfaces including FE and gigabit Ethernet (GE)interfaces. It also supports the interface convergence and VLAN.

Figure 13-1 shows the protocol stacks of the Ethernet interface that is supported by theUMG8900.

Figure 13-1 Ethernet interface protocol stack

IP

IEEE802.3/802.3u/802.3q/802.3z

100Base-TX1000Base-SX/LX/LX-GL/ZX

13 Configuring IP BearerHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)




ParameterName

Data Input Source







VLAN ID <VLAN ID>

MAC address <MAC address>

IP address <IP address>

VLAN domain ID <VLAN domain ID>

Bearer bandwidth <VLAN bear bandwidth(Kbps)>

Max transmissionunit

<The max. transmission unit>

Duplex mode <Duplex mode>

Domain <Domain>

Procedure

Step 1 Run ADD IFVLAN to add the VLAN configuration of the Ethernet interface. Set Interfacetype to ETH, Board type to HRB.ADD IFVLAN: IFT=ETH,BT=HRB,BN=<Board No.>,IFN=<InterfaceNo.>,VID=<VLAN ID>,VDOMAIN=<VLAN domain ID>,VBEARBW=<VLAN bearbandwidth(Kbps)>;

Step 2 Run ADD VMAC to add the virtual MAC address. Set Interface type to ETH, Board type toHRB.ADD VMAC: IFT=ETH,BT=HRB,BN=<Board No.>,IFN=<Interface No.>,MACADDR=<MAC address>;

Step 3 Run ADD ARP to add the static address resolution protocol (ARP) mapping. Set Board typeto HRB.



13-3

ADD ARP: BT=HRB,BN=<Board No.>, IPADDR=<IP address>, MACADDR=<MACaddress>;

Step 4 Run MOD IPIF to modify the configuration of the IP interface. Set Interface type to ETH,Board type to HRB.MOD IPIF: IFT=ETH,BT=HRB,BN=<Board No.>,IFN=<Interface No.>, MTU=<Themax. transmission unit>, BEARBW=<VLAN bear bandwidth(Kbps)>, DUPLEX=<Duplexmode>, DOMAIN=<Domain>;

----End

ExampleExample scriptADD IFVLAN: IFT=ETH,BT=HRB,BN=0,IFN=0,VID=6,VDOMAIN=0,VBEARBW=100,CLPRI=2,VOPRI=2, VIPRI=2;ADD VMAC: IFT=ETH, BT=HRB, BN=0, IFN=0, MACADDR="00E0.FC2A.6B56";ADD ARP: BT=HRB, BN=1, IPADDR="10.110.33.167", MACADDR="00aa.bbcc.ddee";MOD IPIF: IFT=ETH, BT=HRB, BN=0, IFN=0, MTU=1500, DESP="Ethernet Interface", BEARBW=102400, DUPLEX=FULL, DOMAIN=0;

Postrequisite

After configuring the FE interface, configure other types of Internet Protocol (IP) interfacesbased on the requirements.

Configuring the GE Interface

Configuring the ATM Interfac

Configuring the IP over E1 Interfac

If not required, configure the IP interface address.

Configuring the IP Interface Address

13.1.2 Configuring the GE InterfaceThis describes how to configure the gigabit Ethernet (GE) interface.



Context

The local area network (LAN) includes the types including the Ethernet and token ring network.Featuring the flexibility, simplicity, and easy implementation, the Ethernet becomes animportant LAN networking technology.

At present, the UMG8900 supports the Ethernet interface including the fast Ethernet (FE)interface and gigabit Ethernet (GE) interface and supports the port convergence and virtual LAN(VLAN).

Figure 13-2 shows the protocol stack supported by the Ethernet interface of the UMG8900.


Configuration Guide


Issue 02 (2008-05-07)

Figure 13-2 Protocol stack of the Ethernet interface

IP

IEEE802.3/802.3u/802.3q/802.3z

100Base-TX1000Base-SX/LX/LX-GL/ZX




ParameterName

Data Input Source







VLAN ID <VLAN ID>








Domain <Domain>

Auto negotiation <Auto negotiation>



13-5

Procedure

Step 1 Run ADD IFVLAN to add the VLAN configuration of the Ethernet interface. Set InterfaceType to GE, Board Type to HRB.ADD IFVLAN: IFT=GE,BT=HRB,BN=<Board No.>,IFN=<Interface No.>,VID=<VLANID>,VDOMAIN=<VLAN domain ID>,VBEARBW=<VLAN bear bandwidth(Kbps)>;

Step 2 Run ADD VMAC to add the virtual MAC address. Set Interface Type to GE, Board Type toHRB.ADD VMAC: IFT=GE,BT=HRB,BN=<Board No.>,IFN=<Interface No.>,MACADDR=<MAC address>;

Step 3 Run ADD ARP to add the static address resolution protocol (ARP) mapping. Set InterfaceType to GE, Board Type to HRB.ADD ARP: BT=HRB,BN=<Board No.>, IPADDR=<IP address>, MACADDR=<MACaddress>;

Step 4 Run MOD IPIF to modify the configuration of the IP interface. Set Interface Type to GE,Board Type to HRB.MOD IPIF: IFT=GE,BT=HRB,BN=<Board No.>,IFN=<Interface No.>, MTU=<The max.transmission unit>, AUTONEGO=<Auto negotiation>, BEARBW=<VLAN bear bandwidth(Kbps)>, DUPLEX=<Duplex mode>, DOMAIN=<Domain>;

----End

ExampleExample scriptADD IFVLAN: IFT=GE,BT=HRB,BN=0,IFN=0,VID=6,VDOMAIN=0,VBEARBW=100,CLPRI=2,VOPRI=2, VIPRI=2;ADD VMAC: IFT=GE, BT=HRB, BN=0, IFN=0, MACADDR="00E0.FC2A.6B56";ADD ARP: BT=HRB, BN=1, IPADDR="10.110.33.167", MACADDR="00aa.bbcc.ddee";MOD IPIF: IFT=GE, BT=HRB, BN=0, IFN=0, MTU=1500, DESP="GE Interface, AUTONEGO=NO, BEARBW=1024000, DUPLEX=FULL, DOMAIN=0;

PostrequisiteAfter configuring the GE interface, configure other types of IP interfaces based on therequirements.

Configuring the ATM Interfac

Configuring the IP over E1 Interfac



13.1.3 Configuring the ATM InterfaceThis describes how to configure the asynchronous transfer mode (ATM) interface.




Configuration Guide


Issue 02 (2008-05-07)

Context

IP over ATM (IPoA) is configured only when IP packets are transmitted over the ATM network.

IPoA inherits the basic concept of the TCP/IP protocol. It regards the ATM network as a differentsubnetwork, and IP protocol packets are carried over ATM Adaptation Layer 5 (AAL5). IPoAhelps you to carry out the application of the IP-based network protocols and networks over theATM network. By using IPoA, you can directly run the IP-based network protocol and networkapplication over the ATM network.

Figure 13-3 shows the protocol stack supported by the ATM interface of the UMG8900.

Figure 13-3 Protocol stack of the ATM interface

IP

ATM

SONET/SDH

The UMG8900 supports IPoA, and the back interface board of the HRB is the A4L.











C2 byte <C2 byte>

J0 byte <J0 byte>

J1 byte <J1 byte>

K1 byte <K1 byte>



13-7


K2 byte <K2 byte>

VPI <VPI>

VCI <VCI>

Default static MAP <Default static MAP>

Source IP address <Source IP address>

Encapsulation protocol <Enc protocol>

Destination IP address <Destination IP address>

ATM interface No. <Interface No.>

Maximum transmission unit ofthe ATM interface


Enable ATM interface <Interface enable>

CRC length <Length of CRC>

Procedure

Step 1 Run SET SDHFLAG to set the overhead bytes of the SDH interface. Set Board Type toHRB.

SET SDHFLAG: BT=HRB, BN=<Board No.>, PN=, S1=, C2=, J0=, J1=, K1=, K2=;

Step 2 Run ADD IPPVC to add the IP permanent virtual channel (PVC). Set Board Type to HRB.ADD IPPVC: BT=HRB, BN=<Board No.>, IFN=<Interface No.>, VPI=<VPI>,VCI=<VCI>, ENC=<Enc protocol>;

Step 3 Run ADD IPMAP to add the IP map. Set Board Type to HRB.ADD IPMAP: BT=HRB, BN=<Board No.>, IFN=<Interface No.>, VPI=<VPI>,VCI=<VCI>, DEF=YES, SRCIP=<Source IP address>;

Step 4 Run MOD IPIF to modify the configuration of the IP interface. Set Interface Type to ATM,Board Type to HRB.MOD IPIF: IFT=ATM, BT=HRB, BN=<Board No.>, IFN=<Interface No.>, MTU=<Themax. transmission unit>, ENABLE=<Interface enable>, CRCLEN=<Length of CRC>;

----End

ExampleExample scriptSET SDHFLAG: BT=HRB, BN=0, PN=0, C2=0, J0="1111", J1="111111", K1=0, K2=2, SCR=NO;ADD IPPVC: BT=HRB, BN=0, IFN=0, VPI=0, VCI=8, ENC=SNAP;ADD IPMAP: BT=HRB, BN=0, IFN=0, VPI=0, VCI=8, DEF=YES, SRCIP="10.1.1.80";MOD IPIF: IFT=ATM, BT=HRB, BN=0, IFN=0, MTU=1500, ENABLE=YES, DESP="ATM Interface", CRCLEN=BITS32;


Configuration Guide


Issue 02 (2008-05-07)

PostrequisiteAfter configuring the IPoA interface, configure other types of IP interfaces based on therequirements.

13.1.4 Configuring the IP over E1 Interface


13.2 Configuring the IP Interface Address

13.1.4 Configuring the IP over E1 InterfaceThis describes how to configure the IP over E1 (IPoE1) interface.



ContextThe communication network evolves towards the whole IP of the network. The whole IPimplementation of the whole network can provide rich services based on IP, and greatly improvethe voice quality.

Some networking environments have only the time division multiplexing (TDM) transportnetwork, but no IP bearer network, and carriers hope to construct a network of the whole IP. Inthis case, IP packets need to be transmitted over the TDM transmission network. IP over E1indicates that IP packets are carried over E1 on the current TDM network.

Figure 13-4 shows the protocol stack supported by the IPoE1 interface of the UMG8900.

Figure 13-4 Protocol stack supported by the IPoE1 interface

IP

PPP/MP

E1





13-9



Board type <Board type> Configuring Frames andBoards

Board No. <Board No.> Configuring Frames andBoards

Virtual media gatewayID

<Virtual media gatewayid>

Configuring MGW data

Start TID <Start TID> Configuring the TDM Timeslot

End TID <End TID> Configuring the TDM Timeslot

Interface IP address <Interface IP address> Configuring the IP InterfaceAddress

Interface IP addressmask

<Interface IP addressmask>

Configuring the IP InterfaceAddress




TDM optical port No. <TDM opt port No.>

TDM port No. <TDM port No.>

IOE internal port No. <IOE internal TDM port No.>

TDM start timeslot <Start timeslot>

TDM end timeslot <End timeslot>

Serial interface ID <Serial Interface No.>

Route type <Routing Type>

Destination IP address <Remote IP address>

Route No. <Routing No.>

Transmitting board type <Transmitting board type>

Transmitting board No. <Transmitting board No.>

Transmitting IP address <Transmitting IP address>

VPI <VPI>

VCI <VCI>


Configuration Guide


Issue 02 (2008-05-07)



MP enable <MP enable>

VT Interface No. <VT Interface No.>

ProcedureStep 1 Run ADD BIND to configure the binding relationship of the TDM port.

ADD BIND: TDMBT=<Board type>_1, TDMBN=<Board No.>_1, TDMPORT=<TDM portNo.>, IOEBN=<Board No.>, IOEPORT=<IOE internal TDM port No.>;

Step 2 Run ADD TDMIU to configure the binding relationship of the TDM port. Set Relay type toInside.ADD TDMIU: BT=<Board type>_1, BN=<Board No.>_1, TIDFV=<Start TID>,TIDLV=<End TID>, VMGWID=<Virtual media gateway id>, RT=INSIDE;

Step 3 Run ADD CHANNEL to configure the binding relationship of the TDM port. Here is IOE boardNo..ADD CHANNEL: BN=<Board No.>_2, PORT=<IOE internal TDM port No.>,STARTTS=<Start timeslot>, ENDTS=<End timeslot>, IFN=<Serial Interface No.>;

Step 4 When multiple Serial interfaces support the MP binding, the VT interface comes into being. RunMOD IPIF to modify the attributes of the IP interface. Set Interface Type to SRL, BoardType to HRB.MOD IPIF: IFT=SRL, BT=HRB, BN=<Board No.>_2, IFN=<Interface No.>, IFMP=<MPenable>, VT=<VT Interface No.>;

Step 5 Run ADD IPADDR to add the IP address of the VT interface. Set Interface Type to VT, BoardType to HRB.ADD IPADDR: BT=HRB, BN=<Board No.>_2, IFT=VT, IFN=<Interface No.>,IPADDR=<Interface IP address>, MASK=<Interface IP address mask>;

Step 6 Run ADD REMOTEIP to configure the destination IP address. Set Transmitting boardtype to HRB.ADD REMOTEIP: RTTP=<Routing Type>, RMTIP=<Remote IP address>,IDX=<Transmitting board type>, BT=HRB, BN=<Board No.>_2,LOCALIP=<Transmitting IP address>;

----End


Figure 13-5 Networking diagram of IP over E1

E1192.168.0.1

IP

MGC MGW10.10.1.310.10.1.4

10.10.1.110.10.1.2

10.10.0.110.10.0.2

10.10.0.310.10.0.4

MGW



13-11

Example script//Configure the binding relationship of the TDM port so that each of E32 board 0 and E32 board 1 in frame 2 provides two ports bound to the internal TDM port on IOE 0.ADD BIND: TDMBT=E32, TDMBN=0, TDMPORT=4, IOEBN=0, IOEPORT=0, DESP="Bearer-0";ADD BIND: TDMBT=E32, TDMBN=0, TDMPORT=5, IOEBN=0, IOEPORT=1, DESP="Bearer-0";ADD BIND: TDMBT=E32, TDMBN=1, TDMPORT=1, IOEBN=0, IOEPORT=2, DESP="BSC-Sig-0";ADD BIND: TDMBT=E32, TDMBN=1, TDMPORT=2, IOEBN=0, IOEPORT=3, DESP="BSC-Sig-0";

//Configure the TDM timeslot. ADD TDMIU: BT=E32, BN=0, TIDFV=96, TIDLV=159, VMGWID=0, HOSTID=30, RT=INSIDE, CASNO=0, DCMESUP=NO;ADD TDMIU: BT=E32, BN=1, TIDFV=1120, TIDLV=1183, VMGWID=0, HOSTID=30, RT=INSIDE, CASNO=0, DCMESUP=NO;ADD TDMIU: BT=E32, BN=2, TIDFV=2080, TIDLV=2143, VMGWID=0, HOSTID=30, RT=INSIDE, CASNO=0, DCMESUP=NO;ADD TDMIU: BT=E32, BN=3, TIDFV=3104, TIDLV=3167, VMGWID=0, HOSTID=30, RT=INSIDE, CASNO=0, DCMESUP=NO;

//Configure the binding relationship of the TDM timeslot. Configure the timeslot binding relationship based on the port binding relationship. There are 31 timeslots on each serial interface.ADD CHANNEL: BN=0, PORT=0, STARTTS=1, ENDTS=31, IFN=0;ADD CHANNEL: BN=0, PORT=1, STARTTS=1, ENDTS=31, IFN=1;ADD CHANNEL: BN=0, PORT=2, STARTTS=1, ENDTS=31, IFN=2;ADD CHANNEL: BN=0, PORT=3, STARTTS=1, ENDTS=31, IFN=3;ADD CHANNEL: BN=0, PORT=4, STARTTS=1, ENDTS=31, IFN=4;ADD CHANNEL: BN=0, PORT=5, STARTTS=1, ENDTS=31, IFN=5;ADD CHANNEL: BN=0, PORT=6, STARTTS=1, ENDTS=31, IFN=6;ADD CHANNEL: BN=0, PORT=7, STARTTS=1, ENDTS=31, IFN=7;

//Configure the port attributes, and set the serial interface to the VT interface.MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=0, DESP="VT0-0", IFMP=YES, VT=0;MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=1, DESP="VT0-1", IFMP=YES, VT=0;MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=2, DESP="VT1-0", IFMP=YES, VT=1;MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=3, DESP="VT1-1", IFMP=YES, VT=1;MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=4, DESP="VT2-0", IFMP=YES, VT=2;MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=5, DESP="VT2-1", IFMP=YES, VT=2;MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=6, DESP="VT3-0", IFMP=YES, VT=3;MOD IPIF: IFT=SRL, BT=HRB, BN=0, IFN=7, DESP="VT3-1", IFMP=YES, VT=3;//Configure the port attribute and configure the bearer bandwidth of the VT interface.MOD IPIF: IFT=VT, BT=HRB, BN=0, IFN=0, DESP="BSC-VT0", BEARBW=3968, IFCRTP=YES, RPTROUTE=YES;MOD IPIF: IFT=VT, BT=HRB, BN=0, IFN=1, DESP="BSC-VT1", BEARBW=3968, IFCRTP=YES, RPTROUTE=YES;MOD IPIF: IFT=VT, BT=HRB, BN=0, IFN=2, DESP="BSC-VT2", BEARBW=3968, IFCRTP=NO, RPTROUTE=YES;MOD IPIF: IFT=VT, BT=HRB, BN=0, IFN=3, DESP="BSC-VT3", BEARBW=3968, IFCRTP=NO, RPTROUTE=YES;

NOTE

When the bearer bandwidth is configured, the maximum bearer bandwidth of a channel is 64 kbit/s. In thisexample, one VT interface has two Serial interfaces, and one Serial interface has 31 channels. Themaximum bearer bandwidth of one VT interface is 2 x 31 x 64 kbit/s, that is, 3968 kbit/s.

The bearer bandwidth of the interface transmitting the signaling packets is set to 0.

If supporting CRTP, the UMG8900 compresses the Real-time Transport Protocol (RTP) packets andreduces the bandwidth occupied by the RTP packets to improve the transmission efficiency. After theCompressed Real-Time Protocol (CRTP) function is enabled, the route backup function of the interface isunavailable.

//Configure the IP address. ADD IPADDR: BT=HRB, BN=0, IFT=VT, IFN=0, IPADDR="10.10.0.1", MASK="255.255.255.0";ADD IPADDR: BT=HRB, BN=0, IFT=VT, IFN=1, IPADDR="10.10.0.2", MASK="255.255.255.0";ADD IPADDR: BT=HRB, BN=0, IFT=VT, IFN=2, IPADDR="10.1.1.1", MASK="255.255.255.0";ADD IPADDR: BT=HRB, BN=0, IFT=VT, IFN=3, IPADDR="10.1.1.2", MASK="255.255.255.0";


Configuration Guide


Issue 02 (2008-05-07)

//Set the destination IP address to forward packets from the UMG8900 to the MGC.ADD REMOTEIP: RMTIP="192.168.0.1", BT=MPU, BN=0, DESP="MGC";

PostrequisiteAfter configuring the IP over E1 interface, configure other types of Internet Protocol (IP)interfaces based on the requirements. If not required, configure the IP interface address.


13.2 Configuring the IP Interface AddressThis describes how to configure the Internet Protocol (IP) interface address.

PrerequisiteThe IP interface is correctly configured.











Interface IP address <Interface IP address>

Interface IP address mask <Interface IP address mask>

Master or slave flag <Master or slave flag>

In VLAN <In VLAN>




Parameter Name Data




13-13

ProcedureRun ADD IPADDR to configure the IP interface address. Configure the bearer IP interfaceaddress, and set Board Type to HRB.ADD IPADDR: BT=HRB, BN=<Board No.>, IFT=<Interface type>, IFN=<InterfaceNo.>, IPADDR=<Interface IP address>, MASK=<Interface IP address mask>,FLAG=<Master or slave flag>, INVLAN=<In VLAN>;

----End

ExampleExample scriptADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=0, IPADDR="10.1.1.1", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO;

PostrequisiteAfter configuring the IP interface, decide whether to configurr IP interface protection based onthe requirements.

13.3 Configuring IP Interface Protection

If not required, go to Configuring Gateway Address.

13.4 Configuring the Gateway Address

13.3 Configuring IP Interface ProtectionThis describes how to configure the Internet Protocol (IP) interface protection.

Prerequisitel The IP interface is correctly configured.

l The IP interface address is correctly set.

ContextAfter codec transformation of the service data at the TDM side, the UMG8900 puts the data intoIP packets and sends them to the packet core network through the HRB. The security of IPinterfaces on the HRB is very important. Thus, backup protection must be configured on the IPinterfaces and links.

Figure 13-6 shows the access of the UMG8900 to a core network.


Configuration Guide


Issue 02 (2008-05-07)

Figure 13-6 Access of the UMG8900 to a core network

IP Core Net

Local UMG8900

Remote UMG8900

Master

Slave

Master

E8T/E1GE8T/E1G

MHRUMHRU

SlaveFE/GE

FE/GE POS

MHRU+E8T/E1GMHRU+E8T/E1G

The local UMG8900 is often connected with one router or layer 3 switches in the core networkthrough the master and slave FE/GE interfaces respectively. The local UMG8900 interworkswith the remote UMG8900. The reliability of the local links must be considered for theUMG8900. That is, if a link or interface between the UMG8900 and the router fails, theUMG8900 can quickly detect the failure and switch services from the master faulty link orinterface to the slave link or interface.

Configuration ProcedureFigure 13-7 shows the configuration procedure for IP interface protection of the UMG8900.

Figure 13-7 Configuration procedure for IP interface protection

Configure BFD (optional)

Configure route backup Configure protectiongroups

Start

End





13-15





Interface IP address <Interface IP address> 13.2 Configuring the IP InterfaceAddress









BFD configuration name <BFD configuration name>

Detect type <Detect type>



Domain <Domain>







SD flag <SD flag>




Configuration Guide


Issue 02 (2008-05-07)

ProcedureStep 1 If the Bidirectional Forwarding Detection (BFD) function, run ADD BFD to add the BFD

configuration.ADD BFD: BT=<Board type>, BN=<Board No.>, IFT=<Interface type>, IFN=<InterfaceNo.>, BFDNM=<BFD configuration name>, TYPE=<Detect type>, SRCIP=<Source IPaddress>, DSTIP=<Destination IP address>;

If... Then...

The route backup protection mode is used Step 2

The protection group mode of the IP interface is used Step 3 to Step 7

Step 2 Run ADD RTBAK to configure the route backup.ADD RTBAK: BT=<Board type>, BN=<Board No.>, IFT=<Interface type>,IFN=<Interface No.>, DOMAIN=<Domain>, IPADDR=<Interface IP address>,IPADDRBAK=<Interface IP address>;

Step 3 Run ADD PG to configure the protection group. The IP interface does not support the 1:Nprotection mode. Thus, Protect type must be set to NONAPS1PLUS1 or APS1PLUS1.l Set Protect type to APS1PLUS1.

ADD PG: PGID=<Protect group ID> , IFT=<Interface type>, TYPE=APS1PLUS1,RTVM=<Recover mode>, OPM=<Operate mode>, OPTSM=<Optical Splitter mode>;

l Set Protect type to NONAPS1PLUS1.ADD PG: PGID=<Protect group ID>, IFT=<Interface type>,TYPE=NONAPS1PLUS1;

Step 4 When Recover mode is set to Recover, run SET WRTIME to configure the recover time length.SET WRTIME: PGID=<Protect group ID>, WTIME=<Recover time length(s)> ;

Step 5 If signaling degrade is required, run SET SIGDEFECT to set the signal degrade flag. Set SDflag to SD enable.SET SIGDEFECT: PGID=<Protect group ID>, SDFLAG=<SD flag>;

Step 6 Run ADD PGIF to configure the protection group to which the optical interface belongs to.Before adding work channels, add the protection channels of the protection group. The protectionchannel No. in the protection group is always 0.ADD PGIF: FN=<Frame No.>, SN=<Interface No.>, IFN=<Interface No.>, PGID=<Protectgroup ID>, CHN=<Interface No.>;

Step 7 Run SET PG to enable the protection controller.SET PG: PGID=<Protect group ID>, CMDT=<Work/Protect Channel ID>;

----End

Task InstancesExample script

NOTE

Nos. and IP addresses of interfaces in the same positions on the master and slave boards are the same, andthe 1+1 non-APS protection is supported automatically.



13-17

l FE Interface Protection//Configure the route backup protection mode. ADD BFD: BT=HRB, BN=0, IFT=ETH, IFN=0, BFDNM="BFD-1", TYPE=IP, SRCIP="10.10.1.1", DSTIP="10.10.10.1"; ADD RTBAK: BT=HRB, BN=0, IFT=ETH, IFN=0, IPADDR="10.10.1.1", IPADDRBAK="10.10.1.2";

l ATM Interface ProtectionADD PG: PGID=0, IFT=ATM, TYPE=NONAPS1VSN, CHNNUM=1; SET WRTIME: PGID=0, WTIME=6; SET SIGDEFECT: PGID=0, SDFLAG=SD_ENABLE; ADD PGIF: FN=2, SN=12, IFN=0, PGID=0, CHN=0; ADD PGIF: FN=2, SN=11, IFN=0, PGID=0, CHN=1; ADD PGIF: FN=2, SN=10, IFN=0, PGID=0, CHN=2; ADD PGIF: FN=2, SN=9, IFN=0, PGID=0, CHN=3; SET PG: PGID=0, CMDT=START_CONTROLLER;

l GE Interface Protection

NOTE

The GE interface on the MHRU supports only the independent backup mode. The interfaces providedby the master and slave MHRUs are uniformly numbered. The interfaces in the even slots arenumbered first and then the interfaces in the odd slots are numbered. For example, the GE interfaceof the HRB in slot 4 is numbered 0, and the FE interface of the HRB in slot 5 is numbered 1.

The GE interface on the MHRU supports the 1+1 non-APS protection mode. The interfaces arenumbered separately, no one-to-one relationship exists between the master and slave interfaces.When configuring the interface protection relationship, you need to specify the work channel andprotection channel by using configuration commands. The configuration of the 1+1 non-APSprotection is similar to that of the 1+1 APS protection.

ADD PG: PGID=0, IFT=GE, TYPE=NONAPS1PLUS1; //The GE interface in slot 11 acts as the protection channel. ADD PGIF: FN=2, SN=11, IFN=1, PGID=0, CHN=0;

//The GE interface in slot 10 acts as the working channel. ADD PGIF: FN=2, SN=11, IFN=0, PGID=0, CHN=1; SET PG: PGID=0, CMDT=START_CONTROLLER;

Postrequisite

After configuring the IP interface, configure the gateway IP address.

13.4 Configuring the Gateway Address

13.4 Configuring the Gateway AddressThis describes how to configure the gateway address.

Prerequisitel The IP interface is correctly configured.

l The IP interface address is correctly set.




Configuration Guide


Issue 02 (2008-05-07)




Local IP address <Interface IPaddress>






IP address of the gateway <Gateway IP>

If aging or not <If aging or not>

ProcedureRun ADD GWADDR to configure the gateway address. Set Board Type to HRB.ADD GWADDR: BT=HRB, BN=<Board No.>, IPADDR=<Interface IP address>,GWIP=<Gateway IP>, TIMEOUT=<If aging or not>;

----End

ExampleExample scriptADD GWADDR: BT=HRB, BN=0, IPADDR="10.1.10.1", GWIP="10.1.10.254", TIMEOUT=NoAging;

PostrequisiteAfter configuring the gateway interface address, configure the internet protocol (IP) bearer iscomplete. After configuring the bearer data, configure the signaling transfer.

Configuring Signaling Transfer



13-19

14 Configuring Signaling Transfer

About This Chapter

This describes how to configure the signaling transfer data. The UMG8900 is embedded with asignaling gateway (SG) and supports the signaling transfer function. In some networkingapplications, to reduce connections between network elements, no physical connection existsbetween the media gateway controller (MGC) and the remote devices. The signaling databetween the two connected devices are transferred by the UMG8900. In this case, you need toset signaling transfer on the UMG8900.

14.1 Configuring SIGTRAN over L2UAThis describes how to configure the signaling transfer data over Layer 2 User Adaptation (L2UA)including MTP2 User Adaptation Layer (M2UA) , V5 User Adaptation (V5UA), and ISDN Q.921-User Adaptation Layer (IUA).

14.2 Configuring SIGTRAN over M3UA (MTP3-M3UA)This describes how to configure the signaling transfer data between Message Transfer Part Layer3 (MTP3) and MTP3 User Adaptation Layer (M3UA).

14.3 Configuring Semi-Permanent ConnectionThis describes how to configure the semi-permanent connection to transfer signaling.

14.4 Configuring CASThis describes how to configure the channel associated signaling (CAS).

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 14 Configuring Signaling Transfer


14-1

14.1 Configuring SIGTRAN over L2UAThis describes how to configure the signaling transfer data over Layer 2 User Adaptation (L2UA)including MTP2 User Adaptation Layer (M2UA) , V5 User Adaptation (V5UA), and ISDN Q.921-User Adaptation Layer (IUA).

14.1.1 Configuring SIGTRAN over MTP2-M2UAThis describes how to configure the signaling transfer between message transfer part layer 2(MTP2) and MTP2 user adaptation (M2UA).

14.1.2 Configuring SIGTRAN over LAPV5-V5UAThis describes how to configure the signaling transfer between V5 Signaling Processing Board(LAPV5) and V5 User Adaptation (V5UA).

14.1.3 Configuring SIGTRAN over Q.921-IUAThis describes how to configure the signaling transfer between Q.921 and ISDN Q.921-UserAdaptation Layer (IUA).

14.1.1 Configuring SIGTRAN over MTP2-M2UAThis describes how to configure the signaling transfer between message transfer part layer 2(MTP2) and MTP2 user adaptation (M2UA).

PrerequisiteThe signaling transport (SIGTRAN) interface is correctly configured.

ContextThe M2UA networking mode is applicable to networks with small signaling capacity. It has thefeatures like scatter access and centralized control; however, centralized monitoring on signalingis hard to implement, which affects maintenance and management of the network. Thisnetworking mode is suitable for interworking between broadband and narrowband signaling ofcircuit-related services, especially for interworking between different carriers.

Figure 14-1 shows the embedded SG for signaling adaptation and transfer of the UMG8900 inMTP2-M2UA mode.

14 Configuring Signaling TransferHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

Figure 14-1 Signaling adaptation and transfer in MTP2-M2UA mode

MSC/PSTNSwitch

UMG8900 MGC

S7UP

MTP3

S7UP

MTP3

MTP2

MTP1 MTP1

MTP2M2UASCTP

IP

M2UASCTP

IPMAC MAC

SS7 IP

M2UA-NIF

TDM IP

M2UA: MTP2 User Adaptation Layer MTP: Message Transfer Part S7UP: SS7 User PartSCTP: Stream Control TransmissionProtocol

NIF: nodal interworking function MGC: media gateway controller

MAC: media access control

The SIGTRAN configuration of the UMG8900 based on the M2UA link includes the followingtwo parts:

l Configuration of the M2UA link to the MGCl Configuration of the MTP2 link to the PSTN switch

Index Mapping of Configuration Command ParametersFigure 14-2 shows the index mapping of the configuration command parameters of the signalinggateway (SG) over M2UA.

Figure 14-2 Index mapping of the configuration command parameters over M2UAADD L2UALKS

LKSPROTYPE

LNKNOLOCALIP1LOCALPN

REMOTEIP1REMOTERN

ADD L2UALNK

LKSPROTYPE

LKS

LNKTYPESTRTTSENDTS

ADD MTP2LNK

BINIFIDTEXTIFID



14-3





IP address 1 ofSIGTRANinterfaces



l 10.2 Configuring the PhysicalInterface in SSM-256 Self-CascadingMode


l 10.4 Configuring the PhysicalInterface in Mixed Cascading Mode


IP address 2 ofSIGTRANinterfaces





l 10.4 Configuring the PhysicalInterface in Mixed Cascading Mode

Board type <Board type>_1 8 Configuring Frames and Boards

Transmitting boardNo.

<Board No.>_1 8 Configuring Frames and Boards

SPF board No. <Board No.>_2 8 Configuring Frames and Boards

MTP2 interfaceboard type

<Board type>_2 8 Configuring Frames and Boards

MTP2 interfaceboard No.




Configuration Guide


Issue 02 (2008-05-07)


ParameterName


Interconnected Device 2(DNS)

Interconnected Device 3(BSC/PSTNSwitch)

Checksum andalgorithm

<Checksumalgorithm>


- -

Link group No. <Link set No.> - - -

Use text-typeinterface ID

<Use text-typeinterface ID>


- -

Work mode <Traffic mode> The same asthat of the peerdevice

- -

Link No. to themaster MGC

<Link No.>_1 - - -

Link No. to theslave MGC

<Link No.>_2 - - -

SCTP port No.to the masterMGC

<Local portNo.>_1

- - -

SCTP port No.to the slaveMGC

<Local portNo.>_2

- - -

SCTP port No.to the masterMGC

The same as thatof the peerdevice

<Remote portNo.>_1

- -

SCTP port No.to the slaveMGC


<Remote portNo.>_2

- -

IP address 1 ofthe master MGC


<Remoteaddress1>_1

- -



<Remoteaddress2>_1

IP address 1 ofthe slave MGC


<Remoteaddress1>_2

- -



14-5

ParameterName






<Remoteaddress2>_2

Priority of theM2UA link tothe master MGC

<Priority>_1 - - -

Priority of theM2UA link tothe slave MGC

<Priority>_2 - - -

IP address of theDNS server


- <DNS IPaddress>

-

Path Mode <Path Mode> - - -

MTP2 link No. <Link No.> - - -

E1/T1 No. <E1T1 No.> - - -

Start timeslotNo.

<Start timeslot>

- - The same asthat of the peerdevice

End timeslotNo.

<End time slot> - - The same asthat of the peerdevice

Subboard No. <SPF sub-board No.>

- - -

Integer interfaceID

<Int-typeinterface ID>


- -

Procedurel Configuring the data to the MGC

1. Run SET SCTPINIT to set the SCTP protocol parameters.SET SCTPINIT: BT=<Board type>_1, BN=<Board No.>_1,CHKSUM=<Checksum algorithm>;

2. Run ADD L2UALKS to add an L2UA link set. Use only one link set to the masterand slave MGCs respectively. Set Protocol type to M2UA.ADD L2UALKS: PROTYPE=M2UA, LKSNAME="AMGC1_1", LKS=<Linkset No.>, TRANSTXTID=<Use text-type interface ID>, TM=<Traffic mode>;

3. Check whether the SCTP multi-homing networking is adopted.


Configuration Guide


Issue 02 (2008-05-07)

– If the SCTP multi-homing networking is not adopted, perform Step 4 and Step5.

– If the SCTP multi-homing networking is adopted, perform Step 6 and Step 7.4. Run ADD L2UALNK to add an L2UA link to the master MGC. Set Protocol type

to M2UA.ADD L2UALNK: PROTYPE=M2UA, BN=<Board No.>_2, LNKNO=<LinkNo.>_1, LNKNAME=AMGC1_1, LKS=<Link set No.>, LOCALPN=<Local portNo.>_1, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote portNo.>_1, REMOTEIP1=<Remote address1>_1, PRIO=<Priority>_1;

5. If dual homing is configured, run ADD L2UALNK to add an L2UA link to the slaveMGC. Set Protocol type to M2UA.If no dual homing is configured, do not performthis step but perform Step 8.ADD L2UALNK: PROTYPE=M2UA, BN=<Board No.>_2, LNKNO=<LinkNo.>_2, LNKNAME=AMGC1_2, LKS=<Link set No.>, LOCALPN=<Local portNo.>_2, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote portNo.>_2, REMOTEIP1=<Remote address1>_2, PRIO=<Priority>_2;

6. Run ADD L2UALNK to add an L2UA link to the master MGC. Set Protocol typeto M2UA. Set Path Mode to TWO-PATH or FOUR-PATH based on the actualconditions. By default, Path Mode is TWO-PATH.ADD L2UALNK: PROTYPE=M2UA, BN=<Board No.>_2, LNKNO=<LinkNo.>_1, LNKNAME=AMGC1_1, LKS=<Link set No.>, LOCALPN=<Local portNo.>_1, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IPaddress>_2, REMOTEPN=<Remote port No.>_1, REMOTEIP1=<Remoteaddress1>_1, REMOTEIP2=<Remote address2>_1, PRIO=<Priority>_1,PTHMODE=<Path Mode>;

7. If dual homing is configured, run ADD L2UALNK to add an L2UA link to the slaveMGC. Set Protocol type to M2UA. Set Path Mode to TWO-PATH or FOUR-PATH based on the actual conditions. By default, Path Mode is TWO-PATH. If nodual homing is configured, do not perform this step but perform Step 8.ADD L2UALNK: PROTYPE=M2UA, BN=<Board No.>_2, LNKNO=<LinkNo.>_2, LNKNAME=AMGC1_2, LKS=<Link set No.>, LOCALPN=<Local portNo.>_2, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IPaddress>_2, REMOTEPN=<Remote port No.>_2, REMOTEIP1=<Remoteaddress1>_2, REMOTEIP2=<Remote address2>_2, PRIO=<Priority>_2,PTHMODE=<Path Mode>;

8. When the remote address is expressed in the domain name, run SET DNSSVR toconfigure the DNS server.SET DNSSVR: FLAG=MASTER, IPADDR=<DNS IP address>;

l Configuring the data to the PSTN switch1. Run ADD MTP2LNK to add the MTP2 link. Set Link type to M2UA 64K LINK.

ADD MTP2LNK: LNKNO=<Link No.>, LNKNAME=ABSC1_1, IFBT=<Boardtype>_2, IFBN=<Board No.>_3, E1T1N=<E1T1 No.>, STRTTS=<Start timeslot>, ENDTS=<End time slot>,SPFBN=<Board No.>_2, SUBBN=<SPF sub-board No.>, LNKTYPE=M2UA64K, LKS=<Link set No.>, BINIFID=<Int-typeinterface ID>;

----End




14-7



IP Network


UMG8900

PSTN switch

TDM

IP address: 192.168.0.1

SCTP port No.: 2000


SCTP port No.: 3000



SCTP port No. to the slave MGC: 3000

Example scriptl Configure the data to the MGC.

SET SCTPINIT: BT=SPF, BN=1, CHKSUM=CRC32;ADD L2UALKS: PROTYPE=M2UA, TRANSTXTID=NOUSE, TM=LOADSHARE;//Add an M2UA link to the master MGC.ADD L2UALNK: PROTYPE=M2UA, BN=1, LNKNO=0, LNKNAME="M2UALINK-1", LKS=0, LOCALPN=2000, LOCALIP1="10.1.1.1", REMOTEPN=2000, REMOTEIP1="192.168.0.1", PRIO=0;//Add an M2UA link to the slave MGC, and ensure that the priority of this link is lower than that of the link to the master MGC. ADD L2UALNK: PROTYPE=M2UA, BN=1, LNKNO=0, LNKNAME="M2UALINK-1", LKS=0, LOCALPN=3000, LOCALIP1="10.1.1.1", REMOTEPN=3000, REMOTEIP1="172.16.0.1", PRIO=1;

l Configure the data to the PSTN switch.ADD MTP2LNK: LNKNO=0, LNKNAME="MTP2-1", IFBT=E32, IFBN=0, E1T1N=0, STRTTS=16, SPFBN=0, SUBBN=0, LNKTYPE=M2UA64K, LKS=0, BINIFID=0;

PostrequisiteAfter configuring the M2UA signaling transfer, configure other types of signaling transfer basedon the requirements. If no signaling transfer is required, configuring the signaling transfer iscomplete.l 14.1.2 Configuring SIGTRAN over LAPV5-V5UA

l 14.1.3 Configuring SIGTRAN over Q.921-IUA

l 14.2 Configuring SIGTRAN over M3UA (MTP3-M3UA)

l 14.3 Configuring Semi-Permanent Connection

l 14.4 Configuring CAS

14.1.2 Configuring SIGTRAN over LAPV5-V5UAThis describes how to configure the signaling transfer between V5 Signaling Processing Board(LAPV5) and V5 User Adaptation (V5UA).

PrerequisiteThe SIGTRAN interface is correctly configured.


Configuration Guide


Issue 02 (2008-05-07)

ContextWhen the UMG8900 is connected with the V5 access network, they communicate through theV5.2 signaling. The UMG8900 needs an embedded SG and uses the LAPV5-V5UA mode toadapt and transfer the V5.2 signaling. Refer to Figure 14-4.

Figure 14-4 Signaling adaptation and transfer in LAPV5-V5UA mode

AN UMG8900 MGC

V5.2 V5.2

LAPV5 LAPV5

V5UASCTP

IP

V5UASCTP

IPMAC MAC

V5.2 IP

V5UA-NIF

TDM IP

V5UA: V5.2 User Adaptation Layer LAPV5: LAPV5 Data Link LayerProtocol


NIF: nodal interworking function AN: access network MGC: media gateway controllerSCTP: Stream Control TransmissionProtocol

The SIGTRAN configuration of the UMG8900 based on the V5UA link includes the followingtwo parts:

l Configuration of the V5UA link to the MGC

l Configuration of the LAPV5 link to the V5 access network

Index Mapping of Configuration Command ParametersFigure 14-5 shows the index mapping of the configuration command parameters of the SG overV5UA.



14-9

Figure 14-5 Index and interconnection mapping of the configuration command parameters ofthe SG over V5UA

ADD L2UALKS

LKSPROTYPE


REMOTEIP1REMOTERN

ADD L2UALNK

LKSPROTYPE

LKS

ADD V5E1

E1 IDE1 LNK ID

ADD V5LNK

E1 ID

TSLNK NO





IP address 1 ofSIGTRAN interfaces






l 10.5 Configuring the E1Physical Interface Carrying IPSignaling Packets


Configuration Guide


Issue 02 (2008-05-07)












V5 interface board type <Board type>_2 8 Configuring Frames and Boards

V5 interface board No. <Board No.>_3 8 Configuring Frames and Boards





InterconnectedDevice 2 (V5AN)


<Checksumalgorithm>


-

Link group No. <Link set No.> - -




-

Work mode <Traffic mode> The same as that ofthe peer device

-


<Link No.>_1 - -


<Link No.>_2 - -



14-11




<Local port No.>_1 The same as that ofthe peer device

-



-



<Remote portNo.>_1

-



<Remote portNo.>_2

-



<Remoteaddress1>_1

-



<Remoteaddress2>_1

-



<Remoteaddress1>_2

-



<Remoteaddress2>_2

-

Priority of theV5UA link to themaster MGC

<Priority>_1 - -

Priority of theV5UA link to theslave MGC

<Priority>_2 - -



- <DNS-IPaddress>

Path Mode <Path Mode> - -

E1ID <E1 ID> - -

E1 link ID <E1 link ID> The same as that ofthe peer device

-

E1 No. <E1 No.> - -

V5UA link No. <Link No.> - -

Timeslot No. <Time slot> - The same as thatof the peer device

Subboard No. <SPF sub-boardNo.>

- -


Configuration Guide


Issue 02 (2008-05-07)


1. Run SET SCTPINIT to set the SCTP protocol parameter.SET SCTPINIT: BT=<Board type>_1, BN=<Board No.>_1,CHKSUM=<Checksum algorithm>;

2. Run ADD L2UALKS to add an L2UA link set. Use only one link set to the masterand slave MGCs respectively. Set Protocol type to V5UA.ADD L2UALKS: PROTYPE=V5UA, LKSNAME="AMGC1_1", LKS=<Linkset No.>, TRANSTXTID=<Use text-type interface ID>, TM=<Traffic mode>;



– If the SCTP multi-homing networking is adopted, perform Step 6 and Step 7.

4. Run ADD L2UALNK to add an L2UA link to the master MGC. Set Protocol typeto V5UA.ADD L2UALNK: PROTYPE=V5UA, BN=<Board No.>_2, LNKNO=<LinkNo.>_1, LNKNAME="AMGC1_1", LKS=<Link set No.>, LOCALPN=<Localport No.>_1, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote portNo.>_1, REMOTEIP1=<Remote address1>_1, PRIO=<Priority>_1;

5. If dual homing is configured, run ADD L2UALNK to add an L2UA link to the slaveMGC. Set Protocol type to V5UA. If no dual homing is configured, do not performthis step but perform Step 8.ADD L2UALNK: PROTYPE=V5UA, BN=<Board No.>_2, LNKNO=<LinkNo.>_2, LNKNAME="AMGC1_2", LKS=<Link set No.>, LOCALPN=<Localport No.>_2, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote portNo.>_2, REMOTEIP1=<Remote address1>_2, PRIO=<Priority>_2;

6. Run ADD L2UALNK to add an L2UA link to the master MGC. Set Protocol typeto V5UA. Set Path Mode to TWO-PATH or FOUR-PATH based on the actualconditions. By default, Path Mode is TWO-PATH.ADD L2UALNK: PROTYPE=V5UA, BN=<Board No.>_2, LNKNO=<LinkNo.>_1, LNKNAME="AMGC1_1", LKS=<Link set No.>, LOCALPN=<Localport No.>_1, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IPaddress>_2, REMOTEPN=<Remote port No.>_1, REMOTEIP1=<Remoteaddress1>_1, REMOTEIP2=<Remote address2>_1, PRIO=<Priority>_1,PTHMODE=<Path Mode>;

7. If dual homing is configured, run ADD L2UALNK to add an L2UA link to the slaveMGC. Set Protocol type to V5UA. Set Path Mode to TWO-PATH or FOUR-PATH based on the actual conditions. By default, Path Mode is TWO-PATH. If nodual homing is configured, do not perform this step but perform Step 8.ADD L2UALNK: PROTYPE=V5UA, BN=<Board No.>_2, LNKNO=<LinkNo.>_2, LNKNAME="AMGC1_2", LKS=<Link set No.>, LOCALPN=<Localport No.>_2, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IPaddress>_2, REMOTEPN=<Remote port No.>_2, REMOTEIP1=<Remoteaddress1>_2, REMOTEIP2=<Remote address2>_2, PRIO=<Priority>_2,PTHMODE=<Path Mode>;

8. When the remote address is expressed in the domain name, run SET DNSSVR toconfigure the DNS server.



14-13

SET DNSSVR: FLAG=MASTER, IPADDR=<DNS-IP address>;l Configuring the data to the V5 access network device

1. Run ADD V5E1 to add the V5 E1 link.ADD V5E1: E1ID=<E1 ID>, LKS=<Link set No.>, E1LNKID=<E1 link ID>,IFBT=<Board type>_2, IFBN=<Board No.>_3, E1N=<E1 No.>;

2. Run ADD V5LNK to add the LAPV5 link.ADD V5LNK: LNKNO=<Link No.>, LNKNAME="AV5AN1_1", E1ID=<E1ID>, TS=<Time slot>, SPFBN=<Board No.>, SUBBN=<SPF sub-board No.>;

----End




IP Network


UMG8900

IP address: 192.168.0.1

SCTP port No.: 2020


SCTP port No.: 3020



SCTP port No. to the slave MGC: 3020V5 access device

TDM

Example scriptl Configuring the data to the MGC

SET SCTPINIT: BT=SPF, BN=1, CHKSUM=CRC32;//Add a L2UA link set. ADD L2UALKS: PROTYPE=V5UA, TRANSTXTID=NOUSE, TM=LOADSHARE;//Add a V5UA link to the master MGC. ADD L2UALNK: PROTYPE=V5UA, BN=1, LNKNO=0, LNKNAME="V5UALINK-1", LKS=0, LOCALPN=2020, LOCALIP1="10.1.1.1", REMOTEPN=2020, REMOTEIP1="192.168.0.1", PRIO=0;//Add a V5UA link to the slave MGC, and ensure that the priority of this link is lower than that of the link to the master MGC. ADD L2UALNK: PROTYPE=V5UA, BN=1, LNKNO=0, LNKNAME="V5UALINK-1", LKS=0, LOCALPN=3020, LOCALIP1="10.1.1.1", REMOTEPN=3020, REMOTEIP1="172.16.0.1", PRIO=1;

l Configuring the data to the V5 access network deviceADD V5E1: E1ID=0, LKS=0, E1LNKID=1, IFBT=E32, IFBN=0, E1N=0; ADD V5LNK: LNKNO=0, LNKNAME="V5LNK-1", E1ID=0, TS=16, SPFBN=0, SUBBN=0;

PostrequisiteAfter configuring the V5UA signaling transfer, configure other types of signaling transfer basedon the requirements. If no other signaling transfer is required, configuring the signaling transferis complete.


Configuration Guide


Issue 02 (2008-05-07)

l 14.1.3 Configuring SIGTRAN over Q.921-IUA




14.1.3 Configuring SIGTRAN over Q.921-IUAThis describes how to configure the signaling transfer between Q.921 and ISDN Q.921-UserAdaptation Layer (IUA).


ContextWhen the UMG8900 accesses the PBX, the Q.921-IUA mode is used to adapt and transfer thePRA signaling. Figure 14-7 shows the PRA signaling adaptation and transfer of theUMG8900 in Q.921-IUA mode.

Figure 14-7 Signaling adaptation and transfer in Q.921-IUA mode

PBX UMG8900 MGC

Q.931 Q.931

Q.921

L1 L1

Q.921IUA

SCTPIP

IUASCTP

IPMAC MAC

PRA IP

IUA-NIF

TDM IP

IUA: ISDN Q.921-User Adaptation Layer Q.921: ISDN User-Network Interface Data LinkProtocol

Q.931: ISDN User-Network Interface the Third LayerProtocol

PBX: private branch exchange

NIF: nodal interworking function SCTP: Stream Control Transmission Protocol

The SIGTRAN configuration of the UMG8900 based on the IUA link includes the followingtwo parts:

l Configuration of the IUA link to the MGC

l Configuration of the Q.921 link to the PBX

Index Mapping of Configuration Command ParametersFigure 14-8 shows the index mapping of the configuration command parameters of the signalinggateway (SG) over IUA.



14-15

Figure 14-8 Index and interconnection mapping of the configuration command parameters ofthe SG over IUA

ADD L2UALKS

LKSPROTYPE


REMOTEIP1REMOTERN

ADD L2UALNK

LKSPROTYPE

LKS

TS

ADD Q921LNK

BINIFIDTEXTIFID













Configuration Guide


Issue 02 (2008-05-07)












Q.921 interface boardtype

<Board type>_2 8 Configuring Frames and Boards

Q.921 interface boardNo.





Interconnected Device 2(PBX)


<Checksumalgorithm>


-





-


-


<Link No.>_1 - -


<Link No.>_2 - -



14-17





-



-



<Remote portNo.>_1

-



<Remote portNo.>_2

-



<Remoteaddress1>_1

-



<Remoteaddress2>_1

-



<Remoteaddress1>_2

-



<Remoteaddress2>_2

-

Priority of the IUAlink to the masterMGC

<Priority>_1 - -

Priority of the IUAlink to the slaveMGC

<Priority>_2 - -

Path mode <Path Mode> - -


<DNS-IP address> - -

Q.921 link No. <Q921 Link No.> - -

Integer interface ID <Int-type interface ID> The same as that ofthe peer device

-

E1/T1 No. <E1T1 No.> - -

Timeslot No. <Time slot> - The same asthat of thepeer device

SPF subboard No. <SPF sub-board No.> - -

Network side andsubscriber side

<Net/User side> - -


Configuration Guide


Issue 02 (2008-05-07)


1. Run SET SCTPINIT to set the SCTP protocol parameter.SET SCTPINIT: BT=<Board type>_1, BN=<Board No.>_1,CHKSUM=<Checksum algorithm>;

2. Run ADD L2UALKS to add an L2UA link set. Use only one link set to the masterand slave MGCs. Set Protocol type to IUA.ADD L2UALKS: PROTYPE=IUA, LKSNAME=AMGC1_1, LKS=<Link setNo.>, TRANSTXTID=<Use text-type interface ID>, TM=<Traffic mode>;



– If the SCTP multi-homing networking is adopted, perform Step 6 and Step 7.

4. Run ADD L2UALNK to add an IUA link to the master MGC. Set Protocol type toIUA.ADD L2UALNK: PROTYPE=IUA, BN=<Board No.>_2, LNKNO=<LinkNo.>_1, LNKNAME=AMGC1_1, LKS=<Link set No.>, LOCALPN=<Local portNo.>_1, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote portNo.>_1, REMOTEIP1=<Remote address1>_1, PRIO=<Priority>_1;

5. If dual homing is configured, Run ADD L2UALNK to add an IUA link to the slaveMGC. Set Protocol type to IUA.If no dual homing is configured, do not perform thisstep but perform Step 8.ADD L2UALNK: PROTYPE=IUA, BN=<Board No.>_2, LNKNO=<LinkNo.>_2, LNKNAME=AMGC1_2, LKS=<Link set No.>, LOCALPN=<Local portNo.>_2, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote portNo.>_2, REMOTEIP1=<Remote address1>_2, PRIO=<Priority>_2;

6. Run ADD L2UALNK to add an IUA link to the master MGC. Set Protocol type toIUA. Set Path Mode to TWO-PATH or FOUR-PATH based on the actualconditions. By default, Path Mode is TWO-PATH.ADD L2UALNK: PROTYPE=IUA, BN=<Board No.>_2, LNKNO=<LinkNo.>_1, LNKNAME=AMGC1_1, LKS=<Link set No.>, LOCALPN=<Local portNo.>_1, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IPaddress>_2, REMOTEPN=<Remote port No.>_1, REMOTEIP1=<Remoteaddress1>_1, REMOTEIP2=<Remote address2>_1, PRIO=<Priority>_1,PTHMODE=<Path Mode>;

7. If dual homing is configured, run ADD L2UALNK to add an IUA link to the slaveMGC. Set Protocol type to IUA. Set Path Mode to TWO-PATH or FOUR-PATH based on the actual conditions. By default, Path Mode is TWO-PATH. If nodual homing is configured, do not perform this step but perform Step 8.ADD L2UALNK: PROTYPE=IUA, BN=<Board No.>_2, LNKNO=<LinkNo.>_2, LNKNAME=AMGC1_2, LKS=<Link set No.>, LOCALPN=<Local portNo.>_2, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IPaddress>_2, REMOTEPN=<Remote port No.>_2, REMOTEIP1=<Remoteaddress1>_2, REMOTEIP2=<Remote address2>_2, PRIO=<Priority>_2,PTHMODE=<Path Mode>;

8. When the remote address is expressed in the domain name, run SET DNSSVR toconfigure the DNS server.



14-19

SET DNSSVR: FLAG=MASTER, IPADDR=<DNS-IP address>;l Configuring the data to the PBX

1. Run ADD Q921LNK to add the Q.921 link.ADD Q921LNK: LNKNO=<Q921 Link No.>, LNKNAME=APBX1_1,LKS=<Link set No.>, BINIFID=<Int-type interface ID>, IFBT=<Board type>_2,IFBN=<Board No.>_3, E1T1N=<E1T1 No.>, TS=<Time slot>, SPFBN=<BoardNo.>_2, SUBBN=<SPF sub-board No.>, NETUSER=<Net/User side>;

----End




IP Network


UMG8900

IP address 1: 192.168.0.1

SCTP port No.: 2010

IP address 1: 172.16.0.1

SCTP port No.: 3010



SCTP port No. to the slave MGC: 3010PBX


IP address 2: 172.16.0.2IP address 2: 192.168.0.2

Example scriptl Configuring the data to the MGC

SET SCTPINIT: BT=SPF, BN=0, CHKSUM=CRC32;//Add an L2UA link set. ADD L2UALKS: PROTYPE=IUA, TRANSTXTID=NOUSE, TM=LOADSHARE;//Add an IUA link to the master MGC, and configure SCTP multi-homing. ADD L2UALNK: PROTYPE=IUA, BN=0, LNKNO=0, LNKNAME="M2UALNK-1", LKS=0, LOCALPN=2010, LOCALIP1="10.1.1.1", LOCALIP2="10.1.1.11", REMOTEPN=2010, REMOTEIP1="192.168.0.1", REMOTEIP2="192.168.0.2", PRIO=0, PTHMODE=TWOPATH; //Add an IUA link to the slave MGC, and ensure that the priority of this link is lower than that of the link to the master MGC. ADD L2UALNK: PROTYPE=IUA, BN=0, LNKNO=0, LNKNAME="M2UALNK-2", LKS=0, LOCALPN=3010, LOCALIP1="10.1.1.1", LOCALIP2="10.1.1.11", REMOTEPN=3010, REMOTEIP1="172.16.0.1", REMOTEIP2="172.16.0.2", PRIO=1, PTHMODE=TWOPATH;

l Configuring the data to the PBXADD Q921LNK: LNKNO=0, LNKNAME="Q921-1", LKS=0, BINIFID=0, IFBT=E32, IFBN=0, E1T1N=0, TS=16, SPFBN=0, SUBBN=0, NETUSER=USER;

PostrequisiteAfter configuring the IUA signaling transfer, configure other types of signaling transfer basedon the requirements. If no other signaling transfer is required, configuring the signaling transferis complete.


Configuration Guide


Issue 02 (2008-05-07)




14.2 Configuring SIGTRAN over M3UA (MTP3-M3UA)This describes how to configure the signaling transfer data between Message Transfer Part Layer3 (MTP3) and MTP3 User Adaptation Layer (M3UA).

Prerequisite

The SIGTRAN interface is correctly configured.

Context

The UMG8900 uses the MTP3-M3UA mode to adapt the SS7 user part (S7UP) signaling. TheUMG8900 adapts the common channel signaling (CCS) over the time division multiplexing(TDM) bearer to the CCS over the IP bearer, and then transfers the adapted CCS to the mediagateway controller (MGC). In this case, configure the MTP3-M3UA signaling transfer on theUMG8900.

Figure 14-10 shows the signaling adaptation and transfer of the UMG8900 in MTP3-M3UAmode.

Figure 14-10 Signaling adaptation and transfer in MTP3-M3UA mode

BSC/PSTNSwitch UMG8900 MGCSS7 IP

TDM IP

S7UP

MTP3

MTP2

MTP1

S7UPM3UA-NIF

MTP3

MTP2

MTP1

M3UA

IP

MAC

SCTP

M3UA

IP

MAC

SCTP

M3UA: MTP3 User Adaptation Layer MTP: Message Transfer Part S7UP: SS7 User PartSCTP: Stream Control TransmissionProtocol

NIF: nodal interworking function MGC: media gateway controller


Index Mapping of Configuration Command Parametersl Figure 14-11 shows the index mapping of the major configuration command parameters

of the signaling transfer over M3UA.



14-21

Figure 14-11 Index mapping of the configuration commands of the signaling transfer basedon M3UA

ADD N7DSP

INDEX

DPCOSPINDEX

NI

ADD N7LKS

INDEX

DSPIDX

ADD N7RT

INDEXLKSIDXDSPIDX

ADD N7LNK

INDEXLKSIDX

SLCMTP2NO

ADD MTP2LNK

LNKNO

ADD M3LE

LEX

LET

NIOPC

RCADD M3DE

DEX

DET

NIDPCRC

LEX

ADD M3LKS

LSXADX

TM

ADD M3RTDEXLSX

ADD M3LNK

LIP1/LIP2LP

RIP1/RIP2RP

LSXBNBT




Configuration Guide


Issue 02 (2008-05-07)



Signaling interfaceaddress 1





l 10.4 Configuring the PhysicalInterface in MixedCascading Mode

l 10.5 Configuring the E1Physical Interface CarryingIP Signaling Packets

Signaling interfaceaddress 2





l 10.4 Configuring the PhysicalInterface in MixedCascading Mode

M3UA board type <Board type>_1 8 Configuring Frames andBoards

M3UA board No. <Board No.>_1 8 Configuring Frames andBoards

Local signaling pointcode

<OPC index> 5 Configuring SystemParameters

Local signaling pointindex

<Upper Limit of theInput Voltage Alarm (V)>

5 Configuring SystemParameters

MTP2 interface boardtype

<Board type>_2 8 Configuring Frames andBoards

MTP2 interface boardNo.

<Board No.>_2 8 Configuring Frames andBoards



14-23


SPF Board No. <Board No.>_3 8 Configuring Frames andBoards





InterconnectedDevice 2 (BSC)

Local entity index <Local EntityIndex>

- -

Local network ID <NetworkIndicator>


-

Local Entity Type <Local EntityType>

- -

M3UA Destinationentity index

<Destination EntityIndex>

- -

Network ID of theM3UA destinationentity


<Network Indicator> -

Destination EntityType

- <Destination EntityType>

-

Destinationsignaling PointCode


<Destinationsignaling PointCode>

-

A-interfaceprotocol number

<A-InterfaceProtocol Number>

- The same as thatof the peer device

M3UA link setindex

<Link Set Index> - -

Discard messagesfrom lower prioritylink

<Discard messagesfrom lower prioritylink>

- -

Working Mode <Working Mode> - -

M3UA signalinglink No. to themaster MGC

<M3UA LinkNo.>_1

- -


Configuration Guide


Issue 02 (2008-05-07)



M3UA signalinglink No. to the slaveMGC

<M3UA LinkNo.>_2

- -


<Local Port>_1 The same as that ofthe peer device

-


<Local Port>_2 The same as that ofthe peer device

-



<First Address ofRemote End>_1

-



<Second Address ofRemote End>_1

-



<Remote Port>_1 -




-




-



<Remote Port>_2 -


N7 destinationsignal point index


- <DSP index>

N7 destinationNetwork indicator


- <Networkindicator>

N7 DPC The same as that ofthe peer device

- <DSP>

OPC index <OPC index> - The same as thatof the peer device

N7 link set index <Linkset index> - -

N7 route index <Route index> - -

MTP2 link No. <Link No.> - -

E1/T1 No. <E1T1 No.> - -

Start timeslot No. <Start time slot> - The same as thatof the peer device


- -



14-25



N7 link index <Link index> - -

N7 link code <Signaling linkcode>

- The same as thatof the peer device

Procedurel Configuring data to the MGC

1. Run ADD M3LE to add the M3UA local entity. .ADD M3LE: LEX=<Local Entity Index>, LEN="AUMG89001_1", LET=<LocalEntity Type>, NI=<Network Indicator>, OPC=<National network code>_1;

2. Run ADD M3DE to add the M3UA destination entity. The master and slave MGCsshare one signaling point.ADD M3DE: DEX=<Destination Entity Index>, DEN="AMGC1_1",DET=<Destination Entity Type>, NI=<Network Indicator>, DPC=<Destinationsignaling Point Code>, LEX=<Local Entity Index>;– In M3UA proxy mode, set Network Mode to Nonengross_Mode and Route

Context destined to different entities to different values.

– In M3UA forwarding mode, retain the default values of Network Mode and RouteContext.

3. Run ADD M3LKS to add the M3UA link set. If dual homing is configured, setDiscard messages from lower priority link to DISCARD (YES). Otherwise, usethe default value of Discard messages from lower priority link.ADD M3LKS: LSX=<Link Set Index>, LSN="AMGC1_1", ADX=<DestinationEntity Index>, WM=<Working Mode>, DLP=<Discard messages from lowerpriority link>;

4. Run ADD M3RT to add the M3UA route.ADD M3RT: RN="AMGC1_1", DEX=<Destination Entity Index>, LSX=<LinkSet Index>;

5. Check whether the SCTP multi-homing networking is adopted.– If the SCTP multi-homing networking is not adopted, perform Step 6 and Step

7.– If the SCTP multi-homing networking is adopted, perform Step 8 and Step 9.

6. Run ADD M3LNK to add a M3UA link destined to the master MGC. Set CSMode to Server, Active Standby Flag to Active, and Priority to 0.ADD M3LNK: LNK=<M3UA Link No.>_1, BT=<Board type>_1, BN=<BoardNo.>_1, LKN="AMGC1_1", LIP1=<Interface IP address>_1, LP=<LocalPort>_1, RIP1=<First Address of Remote End>_1, RP=<Remote Port>_1,CS=SERVER,LSX=<Link Set Index>, ASF=ACTIVE, PR=0;

7. If dual homing is configured, run ADD M3LNK to add the M3UA link destined tothe slave MGC. Set CS Mode to Server and Active Standby Flag to Active. Thepriority level of the M3UA link destined to the slave MGC must be lower than that ofthe M3UA link destined to the master MGC, and thus set Priority to 1.If no dualhoming is configured, do not perform this step but perform next step.


Configuration Guide


Issue 02 (2008-05-07)

ADD M3LNK: LNK=<M3UA Link No.>_2, BT=<Board type>_1, BN=<BoardNo.>_1, LKN="AMGC1_2", LIP1=<Interface IP address>_1, LP=<LocalPort>_2, RIP1=<First Address of Remote End>_2, RP=<Remote Port>_2,CS=SERVER,LSX=<Link Set Index>, ASF=ACTIVE, PR=1;

8. Run ADD M3LNK to add the M3UA link destined to the master MGC. Set CSMode to Server and Active Standby Flag to Active, and Priority to 0. Set PathMode to TWO-PATH or FOUR-PATH based on the actual conditions. By default,Path Mode is TWO-PATH.ADD M3LNK: LNK=<M3UA Link No.>_1, BT=<Board type>_1, BN=<BoardNo.>_1, LKN="AMGC1_1", LIP1=<Interface IP address>_1, LIP2=<InterfaceIP address>_2, LP=<Local Port>_1, RIP1=<First Address of Remote End>_1,RIP2=<Second Address of Remote End>_1, RP=<Remote Port>_1, CS=SERVER,LSX=<Link Set Index>, ASF=ACTIVE, PR=0, PTHMODE=<Path Mode>;

9. If dual homing is configured, run ADD M3LNK to add M3UA link destined to slaveMGC. Set CS Mode to Server and Active Standby Flag to Active. The priority levelof the M3UA link destined to the slave MGC must be lower than that of the M3UAlink destined to the master MGC, and thus set Priority to 1. Set Path Mode to TWO-PATH or FOUR-PATH based on the actual conditions. By default, Path Mode isTWO-PATH. If no dual homing is configured, do not perform this step but performnext step.ADD M3LNK: LNK=<M3UA Link No.>_2, BT=<Board type>_1, BN=<BoardNo.>_1, LKN="AMGC1_2", LIP1=<Interface IP address>_1, LIP2=<InterfaceIP address>_2, LP=<Local Port>_2, RIP1=<First Address of Remote End>_2,RIP2=<Second Address of Remote End>_2, RP=<Remote Port>_2, CS=SERVER,LSX=<Link Set Index>, ASF=ACTIVE, PR=1, PTHMODE=<Path Mode>;

l Configuring data to the interconnected device1. Run ADD N7DSP to add the destination signaling point. Set Network indicator to

National Reserved.ADD N7DSP: INDEX=<DSP index>, NAME="ABSC1", NI=NATB,DPC=<DSP>, OSPINDEX=<OPC index>;

2. Run ADD N7LKS to add the N7 link set.ADD N7LKS: INDEX=<Linkset index>, NAME="ABSC1", DSPIDX=<DSPindex>;

3. Run ADD N7RT to add the N7 route.ADD N7RT: INDEX=<Route index>, NAME="ABSC1_1", LKSIDX=<Linksetindex>, DSPIDX=<DSP index>;

4. Run ADD MTP2LNK to add the MTP2 link.– Set Link type to M2UA 64K LINK.

ADD MTP2LNK: LNKNO=<Link No.>, LNKNAME="ABSC1_1",IFBT=<Board type>_2, IFBN=<Board No.>_2, E1T1N=<E1T1 No.>,STRTTS=<Start time slot>, SPFBN=<Board No.>_3, SUBBN=<SPF sub-board No.>, LNKTYPE=MTP364K;

– Set Link type to MTP3 2M LINK.ADD MTP2LNK: LNKNO=<Link No.>, LNKNAME="ABSC1_1",IFBT=<Board type>_2, IFBN=<Board No.>_2, E1T1N=<E1T1 No.>,STRTTS=<Start time slot>, SPFBN=<Board No.>_3, SUBBN=<SPF sub-board No.>, LNKTYPE=MTP32M;

5. Run ADD N7LNK to add the N7 link.



14-27

ADD N7LNK: INDEX=<Link index>, NAME="ABSC1_1", LKSIDX=<Linksetindex>, SLC=<Signaling link code>, MTP2NO=<Link No.>;

----End

Examplel Signaling transfer example over M3UA

Networking diagramFigure 14-12 shows the typical networking of the signaling transfer over M3UA.

Figure 14-12 Networking diagram of the signaling transfer over M3UA

IP Network


UMG8900

IP address: 192.168.0.1SCTP port No.: 4000

IP address: 172.16.0.1SCTP port No.: 5000

IP address: 10.1.1.5SCTP port No. to the master MGC: 4000SCTP port No. to the slave MGC: 5000

PSTN switch

SPC: bbbbbb SPC: bbbbbb

SPC: aaaaaa

SPC: cccccc

Example script– Configuring data to the MGC

ADD M3LE: LEX=0, LEN="AUMG89001", LET=SG, NI=NAT, OPC=H'aaaaaa; ADD M3DE: DEX=0, DEN="AMGC1", DET=AS, NI=NAT, DPC=H'bbbbbb, LEX=0;

//Configure dual homing, and set Discard messages from lower priority link to YES. ADD M3LKS: LSX=0, LSN="AMGC1", ADX=0, DLP=DISCARD; ADD M3RT: RN="AMGC1_1", DEX=0, LSX=0;

//Add the M3UA link destined to the master MGC. ADD M3LNK: LNK=0, BT=SPF, BN=0, LKN="AMGC_1", LIP1="10.1.1.5", LP=4000, RIP1="192.168.0.1", RP=4000, CS=SERVER, PR=0, LSX=0, ASF=ACTIVE;

//Add the M3UA link destined to the slave MGC. The priority level of the M3UA link destined to the slave MGC must be lower than that of the M3UA link destined to the master MGC. ADD M3LNK: LNK=1, BT=SPF, BN=0, LKN="AMGC1_2", LIP1="10.1.1.1", LP=5000, RIP1="172.16.0.1", RP=5000, CS=SERVER, PR=1, LSX=0, ASF=ACTIVE;

– Configuring data to the PSTN switchADD N7DSP: INDEX=0, NAME="APSTN1", NI=NAT, DPC=H'cccccc, OSPINDEX=0; ADD N7LKS: INDEX=0, NAME="APSTN1", DSPIDX=0;

//Use timeslot 16 of port 16 on E32 board 0. ADD MTP2LNK: LNKNO=0, LNKNAME="APSTN1_1", IFBT=E32, IFBN=0, E1T1N=16, STRTTS=16, SPFBN=0, SUBBN=0, LNKTYPE=MTP364K, LKS=0; ADD N7LNK: INDEX=0, NAME="APSTN1_1", LKSIDX=0, SLC=0, MTP2NO=0;


Configuration Guide


Issue 02 (2008-05-07)

PostrequisiteAfter configuring the MTP3-M3UA signaling transfer, configure other types of signalingtransfer based on the requirements. If no signaling transfer is required, configuring the signalingtransfer is complete.l 14.3 Configuring Semi-Permanent Connection


14.3 Configuring Semi-Permanent ConnectionThis describes how to configure the semi-permanent connection to transfer signaling.


Context

When the UMG8900 and the MGC are connected by the time division multiplexing (TDM)connection, a semi-permanent connection can extract the signaling system No.7 (SS7) signalingfrom a certain timeslot in the E1/synchronous digital hierarchy (SDH) trunk and thentransparently transfer the SS7 signaling to the media gateway controller (MGC) through this E1connection. Thus, the transparent transmission of the SS7 signaling is accomplished.

E1 cables need to be deployed between the UMG8900 and the MGC to transfer SS7 signalingthrough semi-permanent connections. The semi-permanent connections greatly expand thenetworking capability of the UMG8900.

Figure 14-13 shows the signaling transparent transmission through the semi-permanentconnection.

Figure 14-13 Signaling transparent transmission through the semi-permanent connection

BSC/MSC/PSTN Switch UMG8900 MGC

S7UP

MTP3

MTP2

MTP1

SS7 SS7

semi-connectionTDM TDM

S7UP

MTP3

MTP2

MTP1

MGC: media gateway controller MTP: Message Transfer Part S7UP: SS7 User Part





14-29












InterconnectedDevice 2 (BSC/MSC/PSTNSwitch)

Start TID <Start TID> - -

End TID <End TID> - -

Semi-permanentconnection ID

<ID> The same as that ofthe peer device

The same as thatof the peer device

Semi-permanentconnection name

<Name> - -

Interworking type <Link type> - -

Direction <Direction> - -

Source frame No. <Src frame No.> The same as that ofthe peer device


Source slot No. <Src slot No.> The same as that ofthe peer device


Source port No. <Src port No.> The same as that ofthe peer device


Source timeslot No. <Src timeslot No.> The same as that ofthe peer device


Destination frameNo.

<Dst frame No.> The same as that ofthe peer device


Destination slot No. <Dst slot No.> The same as that ofthe peer device


Destinationtimeslot No.

<Dst port No.> The same as that ofthe peer device



Configuration Guide


Issue 02 (2008-05-07)



Destinationtimeslot No.

<Dst timeslot No.> The same as that ofthe peer device


Procedure

Step 1 Run ADD TDMIU to configure the TDM timeslot, set Relay type to Extern.ADD TDMIU: BT=<Board type>, BN=<Board No.>, TIDFV=<Start TID>, TIDLV=<EndTID>, VMGWID=<Virtual media gateway id>, RT=EXTERN;

Step 2 Run ADD SPC to configure the semi-permanent connection.ADD SPC: ID=<ID>, CT=<Link type>, CD=<Direction>, STFN=<Src frame No.>,STSN=<Src slot No.>, SPN=<Src port No.>, STS=<Src timeslot No.>, DTFN=<Dst frameNo.>, DTSN=<Dst slot No.>, DPN=<Dst port No.>, DTS=<Dst timeslot No.>;

----End




UMG8900

Timeslot 1-port 0-slot 12-frame 1

PSTN switch

MGC

Timeslot 1-port 1-slot 12-frame 1

TDM

Example scriptADD TDMIU: BT=E32, BN=0, TIDFV=0, TIDLV=31, VMGWID=0, RT=EXTERN;ADD SPC: ID=1, CT=TDM_TDM, CD=DDIR, STFN=1, STSN=12, SPN=0, STS=1, DTFN=1, DTSN=12, DPN=1, DTS=1;

PostrequisiteAfter configuring the semi-permanent connection signaling transfer, configure other types ofsignaling transfer based on the requirements. If no other signaling transfer is required,configuring the signaling transfer is complete.



14-31

Configuring CAS

14.4 Configuring CASThis describes how to configure the channel associated signaling (CAS).

PrerequisiteThe bearer data is correctly set.

CAS AdaptationThe application of CAS signaling varies with countries, and the great difference lies in thedifference between physical signals and logical signals. For example, in the standard R2signaling, a seizing signal corresponds to 0001, but, in Iranian signaling, it may be a 130ms pulsein bit A; in Indonesian signaling, the signal to request the calling number is A6, but, in Iraqisignaling, it is A5. The UMG8900 defines a semantic adaptation layer, carries out the mappingbetween different physical and logical signals through data configuration, and processes onlythe logical signals in the host software. By this means, the R2 CAS difference in term of signalmeanings between different countries is shielded.

At present, the UMG8900 supports the multinational adaptation of the R2 line signaling, R1 linesignaling, and the register signaling, and the multinational adaptation of the R1.5 registersignaling.

l Signaling Conversion IndexThe key to carry out the multinational adaptation of signaling is to configure the mappingtable between physical signals and logical signals. The mapping table is called signalingconversion index, and it includes the following four subindexes:

1. Line signaling conversion indexWhen an outgoing or incoming trunk receives physical line signaling from the peeroffice, index query and judgment based on the state machine is required. The outgoingor incoming trunk converts physical line signaling codes to logical line signals (logicalevents).For example, Table 14-11 lists part of CSN1 line signaling conversion index.

Table 14-11 CSN1 line signaling conversion index

IndexPhysicalSignalingType

PhysicalSignal Call State Logical Event

2 LINE_SIG 1 IDCR (clear requeststate)

SZ (seizingsignal)

2 LINE_SIG 3ODCR (outgoing-trunk clear requeststate)

RANSR (re-answer signal)

2 LINE_SIG 5 IDL (idle state) FR (free signal)

... ... ... ... ...


Configuration Guide


Issue 02 (2008-05-07)

In different call states, a physical signal parameter corresponds to different logicalevents. You must define all the physical line signals related to CSN1 one by onethrough ADD LRPT to set up a complete line signaling conversion index.

2. Line command conversion indexWhen an outgoing or incoming trunk sends line signaling to the peer office, indexquery is required for converting logical line signals to physical line signaling codes.For example, Table 14-12 lists part of the CSN1 line command conversion index.

Table 14-12 CSN1 line command conversion index

Index LogicalCommand

PhysicalSignalingType

PhysicalSignal

SendingLength ofSignal

2 SZ LINE_SIG 3 10

2 RANSR LINE_SIG 7 10

2 FR LINE_SIG 11 10

... ... ... ... ...

The same logical commands correspond to the same physical signal. You must defineall the logical line signals related to CSN1 one by one through ADD LSND to set upa complete line signaling command conversion index.

3. Register signaling conversion indexWhen an incoming trunk receives physical register signaling from the peer office,index query and judgment based on the state machine is required. The incoming trunkconverts physical register signaling codes to logical register signals.For example, Table 14-13 lists part of the CSN1 register signaling conversion index.

Table 14-13 CSN1 register signaling conversion index

Index RegisterSignaling Code Call State Logical Event Parameter

2 1 1 11 1

2 2 1 11 0

2 3 1 12 0

... ... ... ... ...

The value of a register signaling code ranges from 1 to 15. The relevant physicalregister signals are decided by the system. In different call states, a signaling codecorresponds to different logical events. You must define all the physical signalingcodes related to CSN1 MFC one by one through ADD REGRPT to set up a completeregister signaling conversion index.



14-33

4. Register signaling command conversion indexWhen an outgoing trunk sends register signaling to the peer office, index query isrequired for converting logical register signals to physical register signaling codes.For example, Table 14-14 lists part of CSN1 register signaling command conversionindex.

Table 14-14 CSN1 register command conversion index

Index Command Parameter Register SignalingCode

2 11 1 1

2 11 0 2

2 12 0 3

... ... ... ...

In the table, "Command" indicates the logical event in the conversion index. You mustdefine all the logical commands related to CSN1 MFC one by one through ADDREGSND to set up a complete register signaling command conversion index.All the MML commands for configuring signaling conversion index are grouped intoa script file based on the signaling standard in certain country. In the script file, R2,R1 and R1.5 signaling of each country corresponds to a unique index number. Youcan execute the script file on site for configuring the signaling conversion index, andrun ADD CASSIGNAL to reference the index No. in the signaling conversion indexfor defining the related CAS.For example, the script file of CSN1 signaling conversion index defines the followingindexes as 2:– Line signaling conversion index

– Line command conversion index

– Register signaling conversion index

– Register command conversion index

Therefore, the configuration command for CSN1 is:ADD CASSIGNAL: SIGNM="China CNO1", ST=CNO1, LSC=2, LCM=2, RSSC=2, RSCM=2; Table 14-15 lists the CAS conversion index in different countries.

Table 14-15 CAS conversion index in different countries

SignalingName

LineSignalingConversionIndex

LineCommandConversionIndex

RegisterSignalingConversionIndex

RegisterCommandConversionIndex

StandardR2 0 0 0 0

CSN1 2 2 2 2


Configuration Guide


Issue 02 (2008-05-07)

SignalingName





AustraliaR2 0 0 3 3

ThailandR2 4 4 4 4

Brunei R2 0 0 1 1

Brazil 5BR2 3 3 3 (5B) 3 (5B)

Brazil 5CR2 3 3 4 (5C) 4 (5C)

Chile R2 2 2 2 2

IndonesiaR2

5 (E&M longand shortpulses)2 (Ericssonrespondingmetering pulse- incoming)6 (Ericssonrespondingmetering pulse- outgoing)7 (Ericssonclear-backwardmetering pulse- outgoing)1 (Ericssonclear-backwardmetering pulse- incoming)

5 (E&M longand shortpulses)2 (Ericssonrespondingmetering pulse- incoming)6 (Ericssonrespondingmetering pulse- outgoing)7 (Ericssonclear-backwardmetering pulse- outgoing)1 (Ericssonclear-backwardmetering pulse- incoming)

5 5

Mexico R2 0 0 6 6

ArgentinaR2 0 0 1 1

Peru R2 0 0 5 5

Sri LankaR2 0 0 7 7

VenezuelaR2 3 3 3 3



14-35

SignalingName





Tunisia R2 0 0 3 3

India R2 0 0 6 6

SingaporeR2 5 5 5 5

Czechoslovakia R2

6 (Meteringpulse is notsupported.)

6 (Meteringpulse is notsupported.)

7 77 (Meteringpulse issupported.)

7 (Meteringpulse issupported.)

Iran andPakistan R1

0 (FAS is theshort pulse andthe linesignaling typeis one bit.)1 (FAS is thelong pulse andthe linesignaling typeis one bit.)2 (FAS is theshort pulse andthe linesignaling typeis three bits.)3 (FAS is thelong pulse andthe linesignaling typeis three bits.)

0 (FAS is theshort pulse andthe linesignaling typeis one bit.)1 (FAS is thelong pulse andthe linesignaling typeis one bit.)2 (FAS is theshort pulse andthe linesignaling typeis three bits.)3 (FAS is thelong pulse andthe linesignaling typeis three bits.)

2 2

AmericanCAS

1 (The SeizeACK messageis sent.)2 (The SeizeACK messageis not sent.)

1 (The SeizeACK messageis sent.)2 (The SeizeACK messageis not sent.)

1 1


Configuration Guide


Issue 02 (2008-05-07)

SignalingName





RussianR1.5 - -

1 (The registersignaling typeis the MFGP orMFS.)2 (The registersignaling typeis the MFP1.)3 (The registersignaling typeis the MFP2.)

1 (The registersignaling typeis the MFGP orMFS.)2 (The registersignaling typeis the MFP1.)3 (The registersignaling typeis the MFP2.)

l Configuring Pulse Data

Pulse data must be configured in the CAS data. Generally, three types of pulse exist inCAS, described as follows.

– Line pulse: Is used when the line signaling is LINE_PULSE.

– Dial pulse (DP): Is used when the register signaling is DP.

– Metering pulse: Is used for charging, which belongs to line signaling.

Pulse data configuration differs in different countries, especially in offices that need digit-analog conversion. Based on the diversification of pulses, feature parameters of a pulseshould be configured in CAS.

The same as the signaling conversion index, pulse parameter configuration is made into ascript file based on signaling standards in different countries. The script file is containedin the line signaling script file. On site, the script file can be executed for configuring thepulse data. No on-site configuration is required.

For example, Brazil R2 supports A-bit and 1-polarity metering pulse, and Table 14-16 liststhe pulse properties of Brazil R2.

Table 14-16 Brazil R2 metering pulse index

PulseIndex Pulse Bit Pulse

PolarityHigh LevelWidth

Low LevelWidth

PulseInterval(ms)

3 A 1 15 (12-18) 15 (12-18) 15

The pulse composite index of Brazil R2 is defined as 3, and the metering pulse is added inthe pulse composite to complete the pulse configuration for Brazil R2. Configuration scriptis as follows.ADD PULSE: PID=3, BIT=A_BIT, PP=valid_1, HT=15, HMIN=12, HMAX=18, LT=15, LMIN=12, LMAX=18, GAPTIM=15; ADD PCMPLS: ID=3, CPM=3;

Table 14-15 lists the pulse composite index configuration in other countries.



14-37

When the CAS and pulse data is configured, you should assign TDM timeslots fortransmitting CAS between offices.

NOTE

Pulse data configuration is not required for all the CAS.

Different pulse data configuration is required in the following conditions.

l When the line signaling that is used contains line pulse, line pulse data configuration is required.

l When the called number is sent in the DP mode, DP data configuration is required.

l When the metering pulse is used, metering pulse data configuration is required.

Russia line signaling is complex. Therefore, Line signaling conversion index and Line commandconversion index of Russian CAS supported by the UMG8900 are of the default settings, and youdo not need to configure them. The ANI pulse and the inductive pulse are peculiar to Russian linesignaling. You must run ADD ANIPULSE and ADD INDPULSE to configure the ANI pulse andthe inductive pulse.

CAS TypeThe CAS with specific common features can be grouped into one CAS type for use in the CASattribute table. The features based on which CAS type is defined include signaling type, linesignaling type, register signaling type and mapping table index defined in Table 14-15.

Table 14-17 lists the different signaling types in different countries.

Table 14-17 CAS configuration in different countries

CAS nameSignalingtype Line signaling

Registersignaling Remarks

R2 R2 L2B DTMF None

Hong KongIDAM

R2 L2B DTMF None

Australia R2 R2 L2B DTMF None

Thailand R2 THAILAND_R2

THAILAND_R2orTHAILAND_PBX

MFC There are two types ofR2 used in Thailand.THAILAND_R2 ismore applicable, andTHAILAND_PBX ismainly used toconnecting with PBX.

Brunei R2 R2 L2B MFC None

Brazil 5B R2 BRAZIL_R2 L2B MFC None

Brazil 5C R2 BRAZIL_R2 L2B MFC None

Chile R2 CHILE_R2 L2B MFC None

Indonesia R2 R2 L2B MFC None

Mexico R2 MEXICO_R2 L2B MFC None

Argentina R2 R2 L2B MFC None


Configuration Guide


Issue 02 (2008-05-07)

CAS nameSignalingtype Line signaling

Registersignaling Remarks

Peru R2 R2 L2B MFC None

Sri Lanka R2 R2 L2B MFC None

VenezuelaR2

R2 L2B DTMF None

India R2 INDIA_R2 L2B MFC None

Singapore R2 R2 L2B MFC None

CzechRepublic R2

CZECHOSLOVAK_R2

L2B MFC None

United StatesR1

AMERICA_CAS

L1B DTMF orMFP

None

Iran andPakistan R1

IRAN_R1 L1B or L3B DPMFP None

R1.5 R15 TL_CAS2,TCL_CAS2,OCL_CAS2,CL_CAS2,TL_1VF,TCL_1VF,OCL_1VF,TL_CAS1,TCL_CAS1 orOCL_CAS1

DP, MFGP,MFP1,MFP2,MFS,MFS_DP orMFS_MFP1

None

Configuration ProcedureTo configure the CAS, learn the signaling standards of a nation, such as the type of the used linesignaling pulse, register signaling type, line signaling pulse parameter, sending power level whenthe MFC register signaling is used, backward pulse length, supported address sending andreceiving sequence, and requirements for the length of various types of timers. Based on theinformation, the CAS can be smoothly configured.

In addition, during the signaling configuration, Huawei technologies Co., Ltd (hereinafterreferred to as Huawei) makes the scripts for some configuration data such as the pulse data andsignaling conversion table. You can obtain the configuration script applicable to your owncountry from the software version before configuration. The software version includes multipleconfiguration scripts based on the signaling specifications of different countries, and thus youcan select the configuration scripts applicable to your own country.

Figure 14-15 shows the procedure for configuring the CAS.



14-39

Figure 14-15 CAS configuration procedure

Start

Configure pulse data(optional)

Configure CAS mappingtable

Configure CAS types

Configure CAS attributes

Configure CAS timeslots

Configure CAS attributes ofthe UMG8900 (optional)

Add country codes andregion codes (optional)

End

Huawei scripts

Add tariff codes (only for theCzechoslovakia R2n

Index Mapping of Configuration Command ParametersFigure 14-16 shows the index mapping of the configuration command parameters of thesignaling gateway (SG) over CAS.


Configuration Guide


Issue 02 (2008-05-07)

Figure 14-16 Index and interconnection mapping of the configuration command parameters ofthe SG over CAS

ADD PULSE

PIDBIT

IDLMP1-LMP8

DMPCMP

RT=R1 / R2CASNOPLSID

ADD PCMPLS

ADD TDMIU

ADD REGRPT

IDLEVD

IDCMD

IDPEVT

IDLCMD

SIGNMST

LCMLSC

RSCMRSSC

IDSIGNM

ADD REGSND

ADD LSND

ADD LRPT

ADD CASSIGNAL

ADD CASATTR














14-41



Signaling name <CAS name>

Signaling type <signaling type>

Line signaling type <Line signaling>

Register signaling type <Register signaling>

CAS attribute index <Index>

Address send list <Address send list>

Address receive list <Address receive list>

Pulse No. <Pulse No.>

Line signaling conversion index <Line signaling conversion index>

Line command conversion index <Line command conversion index>

Register signaling conversion index <Register signaling conversion index>

Register command conversion index <Register command conversion index>


End TID <End TID>

Procedure

Step 1 Run ADD CASSIGNAL to add the CAS type.ADD CASSIGNAL: SIGNM=<CAS name>, ST=<signaling type>, LS=<Line signaling>,RS=<Register signaling>, LSC=<Line signaling conversion index>, LCM=<Line commandconversion index>, RSSC=<Register signaling conversion index>, RSCM=<Registercommand conversion index>;

Step 2 Run ADD CASATTR to configure the CAS attributes.ADD CASATTR: ID=<Index>, SIGNM=<CAS name>, SNDLST=<Address send list>,RCVLST=<Address receive list>;

Step 3 Run ADD TDMIU to add the CAS timeslot, and set Relay type to R2.ADD TDMIU: BT=<Board type>, BN=<Board No.>, TIDFV=<Start TID>, TIDLV=<EndTID>, VMGWID=<Virtual media gateway id>, RT=R2, CASNO=<Index>, PLSID=<PulseNo.>;

----End




Configuration Guide


Issue 02 (2008-05-07)


UMG8900PBX

MGC

R2

Example script

ADD PULSE: PID=0, BIT=A_BIT, PP=valid_1;ADD PCMPLS: ID=1, CPM=0;ADD LRPT: ID=1, PEVT=LINE_SIG, PARA=0, CRS=IDL, LEVT=SZ;ADD LSND: ID=1, LCMD=SZ, PCMD=LINE_SIG, PARA=1, SNDTIM=10;ADD REGRPT: ID=1, RSD=1, CRS=2, LEVT=11, PARA=1;ADD REGSND: ID=1, CMD=0, PARA=1, RSD=1;ADD CASSIGNAL: SIGNM="R2MFC", ST=R2, LS=L2B, RS=MFC, LSC=1, LCM=1, RSSC=1, RSCM=1;ADD CASATTR: ID=1, SIGNM="R2MFC", SNDLST=DI-1&SI-1&SC-1&ES-0&CC-0&DISC-0&NAC-0, RCVLST=DI-1&SI-1&SC-1&ES-0&CC-0&DISC-0&NAC-0, RCPS=3, RCCP=2;ADD TDMIU: BN=0, BT=E32, TIDFV=0, TIDLV=31, VMGWID=0, HOSTID=1, RT=R2,CASNO=1, PLSID=1;

PostrequisiteAfter the CAS is configured, configuring the signaling transfer is complete.



14-43

15 Configuring UAM Data

About This Chapter

This describes how to configure the user access module (UAM) data.

PreparationsBefore configuring the UAM data, you must complete preparations listed in Table 15-1.

Table 15-1 Preparations

No. Item Remarks

1 Confirm the physical cableconnection.

The UA main frame, UA direct frame, or RSAmain frame is connected to the TDM interfaceboard in the SSM frame through E1 cables.The UA main frame and subframe are connectedthrough highway cables.The RSA main frame and the attached subframeare connected through cascading cables.

2 Confirm that the VPU runsproperly.

The VPU functions to provide asynchronoustones.

3

Confirm that the SPF andthe TDM interface boardsare configured and theywork normally.

The SPF and the TDM interface boards processnarrowband access services.

Configuration ProcedureFigure 15-1 shows the procedure for configuring basic services of the UAM.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 15 Configuring UAM Data


15-1

Figure 15-1 Procedure for configuring basic services of the UAM

Start

Configure asynchronous tones

Configure TDM timeslots

Configure UAM frames

Configure UAM boards

Configure trunks of the PV8/RSU/RSP/RSA/DRV

End

Configure mutual-aid on the SPF

15.1 Configuring UA Frames and BoardsThis describes how to configure the user access (UA) frames, boards, and connections, and howto deploy the plain old telephone service (POTS).

15.2 Configuring the Connection to the UA FrameThis describes how to configure the connection between the UMG8900 and the user access (UA)frame.

15.3 Configuring Synchronous TonesThis describes how to configure the synchronous tones.

15.4 Configuring UAM Environment Monitoring DataThis describes how to configure the user access module (UAM) environment monitoring data.

15.5 Configuring the DDI/AT0 Trunk Access ServiceThis describes how to configure the direct-dialing-in (DDI) or AT0 trunk access service.

15.6 Configuring the Hotline ServiceThis describes how to configure the hotline service.

15.7 Configuring the DDN Dedicated Line Service of the DSLThis describes how to configure the digital data network (DDN) dedicated line service of theDSL.

15.8 Configuring the DDN Dedicated Line Service of the HSLThis describes how to configure the digital data network (DDN) dedicated line service of theHSL.

15 Configuring UAM DataHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

15.9 Configuring the DDN Dedicated Line Service of the SDLThis describes how to configure the digital data network (DDN) dedicated line service of theSDL.

15.10 Configuring the Audio Dedicated Line ServiceThis describes how to configure the audio dedicated line service.



15-3

15.1 Configuring UA Frames and BoardsThis describes how to configure the user access (UA) frames, boards, and connections, and howto deploy the plain old telephone service (POTS).

Prerequisite

Hardware and software of the UMG8900 are installed.

Context

For types and modes of UA frames, see 3.8 UAM Background Information.





Frame ID <Board type> 8 Configuring Frames and Boards


Virtual media gateway ID <Virtual mediagateway id>






End TID <End TID>

Trunk type <Relay type>

Frame ID <Frame No.>

Field ID <Place No.>


Frame No. in cabinet <Frame No. in cabinet>

Frame type <Frame type>


Configuration Guide


Issue 02 (2008-05-07)


Mode <Frame mode>

CMU module No. <CMU module No.>

Slot No. <Slot No.>


Link group No. <Link set No.>

Integer interface ID <Int interface ID>



Parameter Name Data


Slot No. <Slot No.>


Procedure

Step 1 Run ADD TDMIU to add timeslots to the time division multiplexing (TDM) interface board.ADD TDMIU: BT=<Board type>, BN=<Board No.>, TIDFV=<Start TID>, TIDLV=<EndTID>, VMGWID=<Virtual media gateway id>, RT=<Relay type>;

Step 2 Run ADD UAFRM to add UA frames and set Add default board to No.

For types of UA frames, see 3.8.1 UA Frame Types.

ADD UAFRM: FN=<Frame No.>, PN=<Place No.>, RN=<Cabinet No.>, RFN=<Frame No.in cabinet>, FT=<Frame type>, FM=<Frame mode>, BN=<CMU module No.>,VMGWNO=<Virtual media gateway id>, FLG=NO;

UA frames are classified into main frame, subframe, direct frame, RSA main frame, RSAsubframe. For details, see 3.8.2 UA Frame Modes.

Step 3 Run ADD UABRD to add boards in the UA frame.

CAUTIONFor details about boards in the UA frame, refer to Chapter 3 "Introduction to Boards" in the U-SYS UMG8900 Universal Media Gateway UAM Hardware Description.

l If Board type is set to DSL, run the following command:



15-5

ADD UABRD: FN=<Frame No.>, SN=<Slot No.>, BT=<Board type>, LKS=<Link setNo.>, BINIFID=<Int interface ID>;

l If Board type is set to another value, run the following command:ADD UABRD: FN=<Frame No.>, SN=<Slot No.>, BT=<Board type>;

----End

ExampleIn this example, an RSP_10 frame acts as the main frame, an RSP_14 frame acts as the subframe,and another RSP_14 frame acts as the direct frame. The configurations of frames and boards aredescribed. For configurations of RSA main frames, RSA subframes, RSA direct frames, high-density UA frames, and boards, refer to HUAWEI UMG8900 Universal Media GatewayConfiguration Examples Configuring Interconnection Data Between the UMG8900 and theHigh-Density UA Frame.

UA frames and boards

Figure 15-2 shows the UA frames and boards.

Figure 15-2 UA frames and boards

PV8

A32

ASL

ASL

A32

A32

A32

HWC

PV8

A32

A32

A32

DSL

00

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

TSS

PWX

ESC

16

RSP

A32

ASL

ASL

A32

A32

A32

A32

RSP

A32

A32

A32

DSL

DSL

00

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

PWX

ESC

16

17

PWX

DSL

17

RSP_10(main frame)

RSP_14(subframe)

UAM

RSP

A32

ASL

ASL

A32

A32

A32

RSP

A32

A32

A32

A32

00

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

PWX

ESC

16

17

PWX

RSP_14(direct frame)

Example script//Configure the TDM bearer.ADD TDMIU: BT=E32, BN=0, TIDFV=0, TIDLV=1023, VMGWID=0, HOSTID=30, RT=INSIDE, CASNO=0, DCMESUP=NO; ADD TDMIU: BT=E32, BN=1, TIDFV=1024, TIDLV=2047, VMGWID=0, HOSTID=30, RT=INSIDE, CASNO=0, DCMESUP=NO;//Configure the hardware data of the UA frame.//Add the UA frame.ADD UAFRM: FN=1, PN=0, RN=0, RFN=1, FT=RSP10, FM=MAIN, BN=30, VMGWNO=0, FLG=NO; ADD UAFRM: FN=2, PN=0, RN=0, RFN=2, FT=RSP14, FM=SUB, BN=30, VMGWNO=0, FLG=NO; ADD UAFRM: FN=3, PN=0, RN=0, RFN=3, FT=RSP10, FM=DIRECT, BN=30, VMGWNO=0, FLG=NO;


Configuration Guide


Issue 02 (2008-05-07)

//Configure boards in the main frame. ADD UABRD: FN=1, SN=0, BT=ESC, ET=ESC303; ADD UABRD: FN=1, SN=1, BT=PWX04; ADD UABRD: FN=1, SN=2, BT=TSS; ADD UABRD: FN=1, SN=3, BT=ASL; ADD UABRD: FN=1, SN=4, BT=ASL; ADD UABRD: FN=1, SN=5, BT=A32; ADD UABRD: FN=1, SN=6, BT=A32; ADD UABRD: FN=1, SN=7, BT=A32; ADD UABRD: FN=1, SN=8, BT=HWC; ADD UABRD: FN=1, SN=9, BT=PV8; ADD UABRD: FN=1, SN=10, BT=PV8; ADD UABRD: FN=1, SN=11, BT=A32; ADD UABRD: FN=1, SN=12, BT=A32; ADD UABRD: FN=1, SN=13, BT=A32; ADD UABRD: FN=1, SN=14, BT=A32; ADD UABRD: FN=1, SN=15, BT=DSL, LKS=0, BINIFID=8000; ADD UABRD: FN=1, SN=17, BT=PWX04;

NOTE

If Board type is set to DSL, at least one of Int interface ID and Text interface ID must be set. Intinterface ID specifies the integer interface ID of the ISDN Q.921-User Adaptation Layer (IUA) link wherethe DSL subscriber is located. Int interface ID is valid only when Board type is set to DSL, and must bea multiple of eight.

//Configure boards in the subframe.ADD UABRD: FN=2, SN=0, BT=ESC, ET=ESC303; ADD UABRD: FN=2, SN=1, BT=PWX04; ADD UABRD: FN=2, SN=3, BT=ASL; ADD UABRD: FN=2, SN=4, BT=ASL; ADD UABRD: FN=2, SN=5, BT=A32; ADD UABRD: FN=2, SN=6, BT=A32; ADD UABRD: FN=2, SN=7, BT=A32; ADD UABRD: FN=1, SN=8, BT=A32; ADD UABRD: FN=2, SN=9, BT=RSP; ADD UABRD: FN=2, SN=10, BT=RSP; ADD UABRD: FN=2, SN=11, BT=A32; ADD UABRD: FN=2, SN=12, BT=A32; ADD UABRD: FN=2, SN=13, BT=A32; ADD UABRD: FN=2, SN=14, BT=A32; ADD UABRD: FN=2, SN=15, BT=DSL, LKS=0, BINIFID=8008; ADD UABRD: FN=2, SN=16, BT=DSL, LKS=0, BINIFID=8016; ADD UABRD: FN=2, SN=17, BT=DSL, LKS=0, BINIFID=8024;

//Configure boards in the direct frame. ADD UABRD: FN=3, SN=0, BT=ESC, ET=ESC303; ADD UABRD: FN=3, SN=1, BT=PWX04; ADD UABRD: FN=3, SN=3, BT=ASL; ADD UABRD: FN=3, SN=4, BT=ASL; ADD UABRD: FN=3, SN=5, BT=A32; ADD UABRD: FN=3, SN=6, BT=A32; ADD UABRD: FN=3, SN=7, BT=A32; ADD UABRD: FN=3, SN=9, BT=RSP; ADD UABRD: FN=3, SN=10, BT=RSP; ADD UABRD: FN=3, SN=11, BT=A32; ADD UABRD: FN=3, SN=12, BT=A32; ADD UABRD: FN=3, SN=13, BT=A32; ADD UABRD: FN=3, SN=14, BT=A32; ADD UABRD: FN=3, SN=15, BT=A32; ADD UABRD: FN=3, SN=17, BT=PWX04;

PostrequisiteAfter configuring the hardware data, you can configure the connection between theUMG8900 and the user access module (UAM).

15.2 Configuring the Connection to the UA FrameThis describes how to configure the connection between the UMG8900 and the user access (UA)frame.



15-7

Context

Configure the data of the time division multiplexing (TDM) trunk connection between the useraccess module (UAM) frame and the service switching module (SSM) frame, between the UAmain frame and subframe, and between the RSA main frame and subframe. The TDM trunkconnection data is used to carry UAM signaling links and voice services. Connections to beconfigured vary with network applications.

l If the networking mode is SSM + main frame + subframe, you must configure E1connections between the PV8/RSU in the master frame and the TDM interface boards suchas the E32/T32/S2L/S1L in the SSM frame. You must also configure the highway (HW)connection between the main frame and the subframe. It is recommended to configure theHW connection after the E1 connections are configured. In this manner, you can check ifconfigurations are correct through the PV8/RSU/RSP board status.

l If the networking mode is SSM + direct frame, you must configure E1 connections betweenthe RSP in the direct frame and the TDM interface boards such as the E32/T32/S2L/S1Lin the SSM frame. If the direct frame is an RSB frame, configure E1 connections betweenthe RSA in the direct frame and the TDM interface boards in the SSM frame.

l If the networking mode is SSM + RSA main frame + RSA subframe, you must configureE1 connections between the RSA in the RSA main frame and the TDM interface boardssuch as the E32/T32/S2L in the SSM frame. You must also configure the cascading betweenthe DRV in the RSA subframe and the RSA in the RSA main frame.

Check whether the trunk connections are correctly configured through the status of the PV8/RSP/RSA/DRV/RSU. If the board status is normal, it indicates that the trunk connections arecorrectly configured. If the board status is faulty, it indicates that the trunk connections are notcorrectly configured.

The following conventions are determined for the two sides of the TDM connections:

l For configuration of connections between the main frame, RSA main frame, direct frame,and SSM frame, the SSM frame is called the upper-level frame; the main frame, RSA mainframe, and direct frame are called the lower-level frames.

l Similarly, for configuration of connections between the main frame and the subframe, andbetween the RSA main frame and the RSA subframe, the main frame and the RSA mainframe are called the upper-level frames; the subframe and the RSA subframe are called thelower-level frames.

15.2.1 Configuring the Connection Between the SSM Frame and the Main Frame as Well as theDirect FrameThis describes the connection between the service switching module (SSM) frame and the mainframe, as well as the direct frame, and how to configure the connection.

15.2.2 Configuring the Connection Between the RSP Main Frame and the RSP SubframeThis describes the connection between the RSP main frame and the RSP subframe, and how toconfigure the connection.

15.2.3 Configuring the Connection Between the RSA Main Frame and the RSA SubframeThis describes the connection between the RSA main frame and the RSA subframe, and how toconfigure the connection.

15.2.4 Configuring the Connection Between the High-Density Main Frame and the High-Density SubframeThis describes the connection between the high-density main frame and the high-densitysubframe, and how to configure the connection.


Configuration Guide


Issue 02 (2008-05-07)

15.2.1 Configuring the Connection Between the SSM Frame and theMain Frame as Well as the Direct Frame

This describes the connection between the service switching module (SSM) frame and the mainframe, as well as the direct frame, and how to configure the connection.

PrerequisiteThe frames, boards, and time division multiplexing (TDM) timeslots of the user access module(UAM) are correctly configured.

Connection Between the UAM Frame and the SSM Frame

CAUTIONParameter settings must match the physical cable connections. The timeslot 16 of the first E1on the PV8/RSU/RSP/RSA is used to carry signaling, and thus the PV8/RSU/RSP/RSA cannotstart normally if the parameters such as First board No. are configured wrongly. On the devicepanel, the board status is displayed as faulty. The second to the eighth E1s are used to carry voicechannels, and thus call loss occurs if the parameters Second board No. to Eighth board No.are configured wrongly. Calls can sometimes are connected and sometimes are not connected.

To connect the UAM frame and the SSM frame correctly, the No. of the E1 of the PV8/RSU/RSP/RSA and the No. of the TDM interface board connected to the E1 must be determined.





Frame ID <Frame No.> 15.1 Configuring UA Frames andBoards

Slot No. <Slot No.> 15.1 Configuring UA Frames andBoards





Trunk interface board type <Trunk interface board type>



15-9


SPF board No. <SPF board No.>

SPF subboard No. <SPF subboard No.>

First board No. <First trunk board No.>

First port No. <First port No.>

Second board No. <Second trunk board No.>

Second port No. <Second port No.>

Third board No. <Third trunk board No.>

Third port No. <Third port No.>

Fourth board No. <Fourth trunk board No.>

Fourth port No. <Fourth port No.>

Fifth board No. <Fifth trunk board No.>

Fifth port No. <Fifth port No.>

Sixth board No. <Sixth trunk board No.>

Sixth port No. <Sixth port No.>

Seventh board No. <Seventh trunk board No.>

Seventh port No. <Seventh port No.>

Eighth board No. <Eighth trunk board No.>

Eighth port No. <Eighth port No.>

ProcedureRun ADD UACFG to add connections between the SSM frame and the main frame and directframe.ADD UACFG: FN=<Frame No.>, SN=<Slot No.>, E1SRC=<Trunk interface board type>,BN=<SPF board No.>, SBN=<SPF subboard No.>, BN0=<First trunk board No.>,PN0=<First port No.>, BN1=<Second trunk board No.>, PN1=<Second port No.>,BN2=<Third trunk board No.>, PN2=<Third port No.>, BN3=<Fourth trunk board No.>,PN3=<Fourth port No.>, BN4=<Fifth trunk board No.>, PN4=<Fifth port No.>, BN5=<Sixthtrunk board No.>, PN5=<Sixth port No.>, BN6=<Seventh trunk board No.>, PN6=<Seventhport No.>, BN7=<Eighth trunk board No.>, PN7=<Eighth port No.>;

----End

ExampleThe following describes five different connection examples of the E1.

l For the front access frame (PV8-SSM), the physical connections between the UAFM frameand the SSM frame are shown in the following figure.


Configuration Guide


Issue 02 (2008-05-07)

The D-50PIN connector of the trunk cable connects with the PV8 E1 or PV4 E1 interfacesof the UAFM frame. The other end is a coaxial cable that connects with the TDM interfaceboard of the SSM frame. In other words, it connects with the physical DDF frame.– The trunk cables inserted in the PV4 E1 interfaces of the UAFM frame use E1 1 to 4

on the PV8. Among them, the coaxial cable labeled W1-Left PV8/PV4 (1 to 4) E1connects the PV8 in slot 5 with the SSM frame, and that labeled W2-Right PV8/PV4(1 to 4) E1 connects the PV8 in slot 6 with the SSM frame.

– The trunk cables inserted in the PV8 E1 interfaces of the UAFM frame use E1 5 to 8on the PV8. Among them, the coaxial cable labeled W1-Left PV8/PV4 (5 to 8) E1connects the PV8 in slot 5 with the SSM frame, and that labeled W2-Right PV8/PV4(5 to 8) E1 connects the PV8 in slot 6 with the SSM frame.

NOTE

If the main control is the PV4, it only need be connected with the PV4 E1 interface in the cablingarea of the frame, but need not be connected with the PV8 E1 interface.

Figure 15-3 Physical connections between the UAFM frame and the SSM frame

PV8 E1

W2-Right PV8/PV4(1~4)E1

PV4 E1

UAFM

W1-Left PV8/PV4(1~4)E1

1

2

3

4

5

6

7

8

。。。

0# E32

1

2

3

4

5

6

7

8

。。。

1# E32

1

2

3

4

5

6

7

8

。。。

2# E32

。。。

3# E32 1

2

3

4

5

6

7

8

port 0 port 1

port 7

port 1 port 3port 0

W1-Left PV8/PV4(5~8)E1

W2-Right PV8/PV4(5~8)E1

E1 Nos. on the naked wires. Two cables need to be inserted in an E1interface, one for sending and the other for receiving. For example,

cables 1 and 2 are connected to the same E1 port.

//Configure the trunk connections between the PV8 in slot 5 of UAFM frame 1 and the SSM frame. The connection details are: The first four E1 trunks on the PV8 in slot 5 connect to ports 0, 1, 6 and 7 on E32 0 respectively. The last four E1 trunks on the PV8 in slot 5 connect to ports 1, 3, 5 and 7 on E32 2 respectively.ADD UACFG: FN=1, SN=5, E1SRC=E32, BN=0, SBN=0, BN0=0, PN0=0, BN1=0, PN1=1, BN2=0, PN2=6, BN3=0, PN3=7, BN4=2, PN4=1, BN5=2, PN5=3, BN6=2, PN6=5, BN7=2, PN7=7;

//Configure the trunk connections between the PV8 in slot 6 of UAFM frame 1 and the SSM frame. The connection details are: The first four E1 trunks on the PV8 in slot 6 connect to ports 0, 1, 6 and 7 on E32 1 respectively. The last four E1 trunks on the PV8 in slot 6 connect to ports 1, 3, 5 and 7 on E32 3 respectively.



15-11

ADD UACFG: FN=1, SN=6, E1SRC=E32, BN=0, SBN=0, BN0=1, PN0=0, BN1=1, PN1=1, BN2=1, PN2=6, BN3=1, PN3=7, BN4=3, PN4=1, BN5=3, PN5=3, BN6=3, PN6=5, BN7=3, PN7=7;

l For the front access frame (RSU-SSM), the physical connections between the HABD/HABL frame and the SSM frame are shown in the following figure.The D-68PIN connector of the trunk cable connects with the E1TF interface of the HABDor the HABL frame. The other end is a four-wire coaxial cable that connects with the TDMinterface board of the SSM frame. In other words, it connects with the physical DDF.– The four E1s of the W1 cable correspond to the first four E1s of the RSU in slot 4 in

sequence.– The four E1s of the W2 cable correspond to the last four E1s of the RSU in slot 4 in

sequence.– The four E1s of the W3 cable correspond to the first E1s of the RSU in slot 5 in sequence.– The four E1s of the W4 cable correspond to the last four E1s of the RSU in slot 5 in

sequence.

Figure 15-4 Physical connections between the HABD/HABL frame and the SSM frame

W4-Right RSU(5~8)E1

E1TF

HABD/HABL

W2-Left RSU(5~8)E1

1

2

3

4

5

6

7

8

0# E32

1

2

3

4

5

6

7

8

1

2

3

4

5

6

7

8

2# E32

1

2

3

4

5

6

7

8

port 0 port 1

port 7

port 1 port 3port 0

W1-Left RSU(1~4)E1

W3-Right RSU(1~4)E1

... ...

... ...

1# E323# E32

E1 Nos. on the naked wires. Two cables need to be inserted in anE1 interface, one for sending and the other for receiving. Forexample, cables 1 and 2 are connected to the same E1 port.

//Configure the trunk connections between the RSU in slot 4 of HABD frame 1 and the SSM frame. The connection details are: The first four E1 trunks on the RSU in slot 4 connect to ports 1, 3, 5 and 7 on No.2 E32 respectively. The last four E1 trunks on the RSU in slot 4 connect to ports 0, 1, 6 and 7 on No.0 E32 respectively.ADD UACFG: FN=1, SN=4, E1SRC=E32, BN=0, SBN=0, BN0=2, PN0=1, BN1=2, PN1=3, BN2=2, PN2=5, BN3=2, PN3=7, BN4=0, PN4=0, BN5=0, PN5=1, BN6=0, PN6=6, BN7=0, PN7=7;

//Configure the trunk connections between the RSU in slot 5 of HABD frame 1 and the SSM frame. The connection details are: The first four E1 trunks on the RSU in slot 5 connect to ports 1, 3, 5 and 7 on No.3 E32 respectively. The last four E1 trunks on the RSU in slot 5 connect to ports 0, 1, 6 and 7 on No.1 E32


Configuration Guide


Issue 02 (2008-05-07)

respectively.ADD UACFG: FN=1, SN=5, E1SRC=E32, BN=0, SBN=0, BN0=3, PN0=1, BN1=3, PN1=3, BN2=3, PN2=5, BN3=3, PN3=7, BN4=1, PN4=0, BN5=1, PN5=1, BN6=1, PN6=6, BN7=1, PN7=7;

l For the rear access frame (PV8-SSM), the physical connections between the PV8 in theUAM frame and the SSM frame are shown in the following figure.The 4x8-PIN AMP interface end of the trunk cable connects with pins 17 to 24 and 25 to32 in the upper HEADER on the PV8. The other end is a coaxial cable that connects withthe TDM interface board of the SSM frame. In other words, it connects with the physicalDDF frame.For trunk cables with one end connecting the 4x8-PIN AMP socket and the other endleading out four E1s (eight sending and receiving cables in total):– The trunk cables inserted with pins 17 to 24 on the PV8 use E1s 1, 2, 5 and 6 on the

PV8. That is, No. 1 and 2 naked wires use E1 1, No. 3 and 4 naked wires use E1 2, No.5 and 6 naked wires use E1 5f, and No. 7 and 8 naked wires use E1 6.

– The trunk cables inserted with pins 25 to 32 on the PV8 use E1s 3, 4, 7 and 8 on thePV8. That is, No. 1 and 2 naked wires use E1 3, No. 3 and 4 naked wires use E1 4, No.5 and 6 naked wires use E1 7, and No. 7 and 8 naked wires use E1 8.

For trunk cables with one connecting the 4x8-PIN AMP socket and the other end leadingout two E1s (four sending and receiving cables in total):– The trunk cables inserted with pins 17 to 24 on the PV8 use E1 1 and 2 on the PV8.

That is, the No. 1 and 2 naked wires use E1 1, and the No. 3 and 4 naked wires use E12.

– The trunk cables inserted with pins 25 to 32 on the PV8 use E1 3 and 4 on the PV8.That is, the No. 1 and 2 naked wires use E1 3, and the No. 3 and 4 naked wires use E14.

For trunk cables with one end connecting the 4x8-PIN AMP socket and the other endleading out one E1 (two sending and receiving cables in total):– The trunk cables inserted with pins 17 to 24 on the PV8 use E1 1 on the PV8. That is,

the No. 1 and 2 naked wires use E1 1.– The trunk cables inserted with pins 25 to 32 on the PV8 use E1 2 on the PV8. That is,

the No. 1 and 2 naked wires use E1 2.

NOTE

If the main control board is the PV4, a cable with one connecting the 4x8-PIN AMP socket and theother end leading out four E1s cannot be used. The cables are connected in the same way as those ofthe PV8.

Take the trunk cable with one end connecting the 4x8-PIN AMP socket and the other endproviding four E1s as an example to describe the trunk configuration.



15-13

Figure 15-5 Physical connections between the PV8 in the UAM frame and the SSM frame

PV8R PV8L 1

2

3

4

5

6

7

8

。。。

1# E32

1

2

3

4

5

6

7

8

1

2

3

4

5

6

7

8

。。。

2#E32

1

2

3

4

5

6

7

8

port 0 port 1

port 7

port 1port 0

1

16

32

24

port 6

1#E1

2#E1

5#E1

6#E1

3#E1

7#E1

8#E1

4#E1

1#E1

2#E1

5#E1

6#E1

3#E1

7#E1

8#E1

4#E1

E1 Nos. on the naked wires. Two cables need to be inserted in anE1 interface, one for sending and the other for receving. For

example, cables 1 and 2 connected to the same E1 port.

– For the rear access frame, if E1 cables provided by the PV8 in the UAM frame areconnected to E1 ports in sequence, configure the E1 ports in a cross order whenconfiguring E1 trunks. Refer to Figure 15-6.


Configuration Guide


Issue 02 (2008-05-07)

Figure 15-6 E1 port connection in sequence

W1 to W8: E1 cable labels1#E1 to 8#E1: E1 cable Nos. on the PV8, corresponding to trunks PN0 to PN7

Example script//Configure the connection between the SSM frame and the main frame. Configure the connections between the PV8s in slots 4 and 5 of the PV8 main frame and ports 0 to 7 on E32s 0 and 1 of the UMG8900. Note that the trunk cables inserted in pins in rows 17 to 24 correspond to E1 cables 1, 2, 5, and 6 of the PV8, and the related parameters are PN0, PN1, PN4, and PN5. The trunk cables inserted in pins in rows 25 to 32 correspond to E1 cables 3, 4, 7, and 8 of the PV8, and the related parameters are PN2, PN3, PN6, and PN7. ADD UACFG: FN=1, SN=9, E1SRC=E32, BN=0, SBN=0, BN0=1, PN0=0, BN1=1, PN1=1, BN2=1, PN2=4, BN3=1, PN3=5, BN4=1, PN4=2, BN5=1, PN5=3, BN6=1, PN6=6, BN7=1, PN7=7;ADD UACFG: FN=1, SN=10, E1SRC=E32, BN=1, SBN=0, BN0=2, PN0=0, BN1=2, PN1=1, BN2=2, PN2=4, BN3=2, PN3=5, BN4=2, PN4=2, BN5=2, PN5=3, BN6=2, PN6=6, BN7=2, PN7=7;

– For the rear access frame, if E1 cables provided by the PV8 in the UAM frame areconnected to E1 ports in a cross order, configure the E1 ports in sequence whenconfiguring E1 trunks. Refer to Figure 15-7.



15-15

Figure 15-7 E1 port connection in a cross order

W1 to W8: E1 cable labels1#E1 to 8#E1: E1 cable Nos. on the PV8, corresponding to trunks PN0 to PN7

Example script//Configure the connection between the SSM frame and the main frame.ADD UACFG: FN=1, SN=9, E1SRC=E32, BN=0, SBN=0, BN0=1, PN0=0, BN1=1, PN1=1, BN2=1, PN2=2, BN3=1, PN3=3, BN4=1, PN4=4, BN5=1, PN5=5, BN6=1, PN6=6, BN7=1, PN7=7;ADD UACFG: FN=1, SN=10, E1SRC=E32, BN=1, SBN=0, BN0=2, PN0=0, BN1=2, PN1=1, BN2=2, PN2=2, BN3=2, PN3=3, BN4=2, PN4=4, BN5=2, PN5=5, BN6=2, PN6=6, BN7=2, PN7=7;

For the rear access frame, the SSM frame and the UAM are connected through cables shownin Figure 15-8. Configure the E1 ports in sequence when configuring E1 trunks.


Configuration Guide


Issue 02 (2008-05-07)

Figure 15-8 Connection between the SSM frame and the main frame

Example script//Configure the connection between the SSM frame and the main frame. ADD UACFG: FN=1, SN=9, E1SRC=E32, BN=0, SBN=0, BN0=1, PN0=0, BN1=1, PN1=1, BN2=1, PN2=2, BN3=1, PN3=3, BN4=1, PN4=4, BN5=1, PN5=5, BN6=1, PN6=6, BN7=1, PN7=7;ADD UACFG: FN=1, SN=10, E1SRC=E32, BN=1, SBN=0, BN0=2, PN0=0, BN1=2, PN1=1, BN2=2, PN2=2, BN3=2, PN3=3, BN4=2, PN4=4, BN5=2, PN5=5, BN6=2, PN6=6, BN7=2, PN7=7;

l For the rear access frame, the physical connections between the RSP of the UAM frameand the SSM frame are shown in the following figure.The AMP interface end of the trunk cable connects with pins 17 to 24 and 25 to 32 in theupper HEADER on the RSP. The other end is a coaxial cable that connects with the TDMinterface board of the SSM frame. In other words, it connects with the physical DDF frame.For trunk cables with one end connecting the 4x8-PIN AMP socket and the other endleading out two E1s (four sending and receiving cables in total):– The trunk cables inserted with pins 17 to 24 on the RSP use E1 1 and 2 on the RSP.

That is, the No. 1 and 2 naked wires use E1 1, and the No. 3 and 4 naked wires use E12.

– The trunk cables inserted with pins 25 to 32 on the RSP use E1 3 and 4 on the RSP.That is, the No. 1 and 2 naked wires use E1 3, and the No. 3 and 4 naked wires use E14.

For trunk cables with one end connecting the 4x8-PIN socket and the other end leading outone E1 (two sending and receiving cables in total):– The trunk cables inserted with pins 17 to 24 on the RSP use E1 1. That is, the No. 1 and

2 naked wires use E1 1.– The trunk cables inserted with pins 25 to 32 on the RSP use E1 2 on the RSP. That is,

the No. 1 and 2 naked wires use E1 2.Take the trunk cable with one end connecting the 4x8-PIN AMP socket and the other endproviding two E1s as an example to describe the trunk configuration.



15-17

Figure 15-9 Physical connections between the RSP in the UAM frame and the SSM frame

RSPR RSPL 1

2

3

4

。。。

0# E32

1

2

3

4

。。。

1# E32

1

2

3

4

。。。

2# E32

。。。

3# E32 1

2

3

4

port 0 port 1

port 7

port 1 port 3port 0

1

16

32

24

E1 Nos. on the naked wires. Two cables need to beinserted in an E1 interface, one for sending and theother for receiving. For example, cables 1 and 2 are

connected to the same E1 port.

//Configure the trunk connections between the RSP in slot 9 of UAM frame 1 and the SSM frame. The connection details are: The trunk cables inserted with pins 17 to 24, which use E1s 1 and 2, connect to ports 8 and 9 on the E32 0 board respectively. The trunk cables inserted with pins 25 to 32, which use E1s 3 and 4, connect to ports 0 and 1 on the E32 3 board respectively.ADD UACFG: FN=1, SN=9, E1SRC=E32, BN=0, SBN=0, BN0=0, PN0=0, BN1=0, PN1=1, BN2=1, PN2=0, BN3=1, PN3=1;

//Configure the trunk connections between the RSP in slot 10 of UAM frame 1 and the SSM frame. The connection details are: The trunk cables inserted with pins 17 to 24, which use E1s 1 and 2, connect to ports 1 and 3 on the E32 2 board respectively. The trunk cables inserted with pins 25 to 32, which use E1s 3 and 4, connect to ports 1 and 3 on the E32 3 board respectively.ADD UACFG: FN=1, SN=10, E1SRC=E32, BN=0, SBN=0, BN0=2, PN0=1, BN1=2, PN1=3, BN2=3, PN2=1, BN3=3, PN3=3;

l For the rear access frame, the physical connections between the HWCB in the HABA_UPframe and the SSM frame are shown in the following figure.The D-44PIN connector of the trunk cable connects with the D-44PIN interface of the rearHWCB of the HABA frame. The other end is a two-wire coaxial cable that connects withthe TDM interface board of the SSM frame. In other words, it connects with the physicalDDF.The HWCB provides the upper and lower 44-PIN interfaces, each of which can connecteight E1s.– The first four E1s of the upper interface correspond to the first four E1s of the RSU in

slot 4 in sequence. The last four E1s correspond to the first four E1s in the RSU in slot5 in sequence.

– The first four E1s of the lower interface correspond to the last four E1s of the RSU inslot 4 in sequence. The last four E1s correspond to the last four E1s in the RSU in slot5 in sequence.


Configuration Guide


Issue 02 (2008-05-07)

Figure 15-10 Physical connections between the HWCB in the HABA_UP frame and theSSM frame

W2-Right RSU(1-4)E1

1

2

3

4

5

6

7

8

。。。

0# E32

1

2

3

4

5

6

7

8

。。。

1# E32

1

2

3

4

5

6

7

8

。。。

2# E32

。。。

3# E32 1

2

3

4

5

6

7

8

port 0 port 1

port 7

port 1 port 3port 0

W1-Left RSU(1-4)E1

HWCB

W1-Left RSU(5-8)E1

W2-Right RSU(5-8)E1

E1 Nos. on the naked wires. Two cables need to be inserted in an E1interface, one for sending and the other for receiving. For example,

cables 1 and 2 are connected to the same E1 port.

//Configure the trunk connections between the RSU in slot 4 of HABA_UP frame 1 and the SSM frame. The connection details are: The trunk cables W1 inserted in E1 port A on the HWCB connect to ports 1, 3, 5 and 7 on the E32 2 board respectively. The trunk cables W1 inserted in E1 port B on the HWCB connect to ports 1, 3, 5 and 7 on the E32 3 board respectively.ADD UACFG: FN=1, SN=4, E1SRC=E32, BN=0, SBN=0, BN0=2, PN0=1, BN1=2, PN1=3, BN2=2, PN2=5, BN3=2, PN3=7, BN4=3, PN4=1, BN5=3, PN5=3, BN6=3, PN6=5, BN7=3, PN7=7;

//Configure the trunk connections between the RSU in slot 5 of HABA_UP frame 1 and the SSM frame. The connection details are: The trunk cables W2 inserted in E1 port A on the HWCB connect to ports 0, 1, 6 and 7 on the E32 0 board respectively. The trunk cables W2 inserted in E1 port B on the HWCB connect to ports 0, 1, 6 and 7 on the E32 1 board respectively.ADD UACFG: FN=1, SN=5, E1SRC=E32, BN=0, SBN=0, BN0=0, PN0=0, BN1=0, PN1=1, BN2=0, PN2=6, BN3=0, PN3=7, BN4=1, PN4=0, BN5=1, PN5=1, BN6=1, PN6=6, BN7=1, PN7=7;

If the UAM frame and the SSM frame are installed in different offices, SDH devices are requiredin between. Thus, the E1 Nos. matching the E1 cables of the PV8/RSU/RSP in the SSM frameare difficult to specify due to the various types of trunk cables. For determining the E1 Nos.through the loopback test, refer to 3.8.4 Method to Number E1 Interfaces on the PV8/RSUby Mapping Them to E1 Cables on the SSM Side and 3.8.5 Method to Number E1 Interfaceson the RSP by Mapping Them to E1 Cables on the SSM Side.

Figure 15-11 shows the connection between the SSM frame and the direct frame.



15-19

Figure 15-11 Connection between the SSM frame and the direct frame

Example script//Configure the connection between the SSM frame and the direct frame.ADD UACFG: FN=3, SN=9, E1SRC=E32, BN=0, SBN=0, BN0=0, PN0=8, BN1=0, PN1=9, BN2=0, PN2=10, BN3=0, PN3=11; ADD UACFG: FN=3, SN=10, E1SRC=E32, BN=1, SBN=0, BN0=1, PN0=8, BN1=1, PN1=9, BN2=1, PN2=10, BN3=1, PN3=11;

15.2.2 Configuring the Connection Between the RSP Main Frameand the RSP Subframe

This describes the connection between the RSP main frame and the RSP subframe, and how toconfigure the connection.

PrerequisiteThe connection between the user access (UA) main frame and the service switching module(SSM) frame is configured.

ContextThe UA main frame is connected to the subframe through internal highway (HW) cables. Figure15-12 shows the connection.


Configuration Guide


Issue 02 (2008-05-07)

Figure 15-12 Connection between the RSP_10 main frame and the RSP_14 subframe

HWC

A

B

C

D

H

E

F

G

c

d

a

b

RSPR RSPL

HGB

HIB

In Figure 15-12, the HGB is the backplane of the RSP_10 frame. The HGB provides the HWCinterface for cascading with the subframe. Table 15-7 lists the descriptions of the HWC interfacein the RSP_10 frame.

Table 15-7 Descriptions of the HWC interface

Interface ID HW No. Pin Position

A 16 to19 1 to 8

B 20 to 23 9 to 16

C 24 to 27 17 to 24

D 28 to 31 25 to 32

E 32 to 35 33 to 40



15-21

Interface ID HW No. Pin Position

F 36 to 39 41 to 48

G 40 to 43 49 to 56

H 44 to 47 57 to 64

The HIB is the backplane of the RSP_14 frame. The HIB provides the HW interface for cascadingwith the main frame. Table 15-8 lists the descriptions of the HW interface.

Table 15-8 Descriptions of the HW interface in the RSP_14 frame

Interface ID Slot No. of the RSP Board No. of the RSP Pin Position

a 10 1 to 4 17 to 24

b 10 5 to 8 25 to 32

c 9 1 to 4 17 to 24

d 9 5 to 8 25 to 32












PV8 frame No. <PV8 slot No.>

First HW No. <First HW No.>


Configuration Guide


Issue 02 (2008-05-07)


Second HW No. <Second HW No.>

Third HW No. <Third HW No.>

Fourth HW No. <Fourth HW No.>

Fifth HW No. <Fifth HW No.>

Sixth HW No. <Sixth HW No.>

Seventh HW No. <Seventh HW No.>

Eighth HW No. <Eighth HW No.>

Procedure

Run ADD UACFG to add the trunk between boards in the RSP main frame and the RSPsubframe.ADD UACFG: FN=<Frame No.>, SN=<Slot No.>, E1SRC=<Trunk interface board type>,PV8FN=<PV8 slot No.>, HW1=<First HW No.>, HW2=<Second HW No.>, HW3=<ThirdHW No.>, HW4=<Fourth HW No.>, HW5=<Fifth HW No.>, HW6=<Sixth HW No.>,HW7=<Seventh HW No.>, HW8=<Eighth HW No.>;

----End

ExampleExample script

//Configure the connection between the main frame and the subframe.ADD UACFG: FN=2, SN=9, E1SRC=PV8, PV8FN=1, HW1=16, HW2=17, HW3=18, HW4=19, HW5=20, HW6=21, HW7=22, HW8=23;ADD UACFG: FN=2, SN=10, E1SRC=PV8, PV8FN=1, HW1=24, HW2=25, HW3=26, HW4=27, HW5=28, HW6=29, HW7=30, HW8=31;

15.2.3 Configuring the Connection Between the RSA Main Frameand the RSA Subframe

This describes the connection between the RSA main frame and the RSA subframe, and how toconfigure the connection.

PrerequisiteBoards in the RSA main frame and the RSA subframe are configured, and the main frame andthe service switching module (SSM) frame are configured.

Context

The RSA main frame is connected to the RSA subframe through internal NOD and highway(HW) cables. Refer to Figure 15-13.



15-23

Figure 15-13 Connection between the RSA main frame and the RSA subframe

USRframe

DRV DRV

RSAframe

RSA RSA

2

1

2

1. HW cables 2. NOD cables

In Figure 15-13, the DRV in slot 10 of the USR frame is connected to the RSA in slot 5 of theRSA frame through NOD cables. The DRV in slot 11 of the USR frame is connected to the RSAin slot 6 of the RSA frame through NOD cables.








Configuration Guide


Issue 02 (2008-05-07)





RSA frame No. <RSA Frame No.>

Slot No. of the RSA <RSA slot No.>

Procedure

Run ADD UACFG to add the trunk between boards in the RSA main frame and the RSAsubframe.ADD UACFG: FN=<Frame No.>, E1SRC=<Trunk interface board type>, SN=<Slot No.>,RSAFN=<RSA Frame No.>, RSASN=<RSA slot No.>;

----End


//Configure the connection between the DRV in slot 10 of the USR subframe and the RSA in slot 5 of the RSA main frame.ADD UACFG: FN=2, E1SRC=RSA, SN=10, RSAFN=1, RSASN=5;

//Configure the connection between the DRV in slot 11 of the USR subframe and the RSA in slot 6 of the RSA main frame.ADD UACFG: FN=2, E1SRC=RSA, SN=11, RSAFN=1, RSASN=6;

15.2.4 Configuring the Connection Between the High-Density MainFrame and the High-Density Subframe

This describes the connection between the high-density main frame and the high-densitysubframe, and how to configure the connection.

PrerequisiteBoards in the high-density main frame and the high-density subframe are configured, and themain frame and the service switching module (SSM) frame are configured.

Context

In Figure 15-14, HABA_UP frame 7 is connected to HABB_UP frame 9 through the highway(HW) cable of the HWCB.

The UMG8900 automatically allocates the cascading interface PORT0 of the HABA_UP frameto the HABA_DOWN frame 8, PORT1 to the HABA_UP frame 9, and PORT2 to theHABA_DOWN frame 10.



15-25

Figure 15-14 Connection between the main frame and the subframe

HWCB

HWCB

#7HABA_UP

#8HABA_DOWN

#9HABB_UP

#10HABB_DOWN











RSU frame No. <RSU frame No.>

Cascading interface <Cascade>

ProcedureRun ADD UACFG to add the trunk between boards in the high-density main frame and thehigh-density subframe.ADD UACFG: FN=<Frame No.>, E1SRC=<Trunk interface board type>, RSUFN=<RSUframe No.>, RSUHW=<Cascade>;

----End



Configuration Guide


Issue 02 (2008-05-07)

//Configure the connection between the HABA_UP subframe 9 and the HABA_UP main frame 7.ADD UACFG: FN=8, E1SRC=RSU, RSUFN=7, RSUHW=PORT0;ADD UACFG: FN=9, E1SRC=RSU, RSUFN=7, RSUHW=PORT1;ADD UACFG: FN=10, E1SRC=RSU, RSUFN=7, RSUHW=PORT2;

15.3 Configuring Synchronous TonesThis describes how to configure the synchronous tones.

PrerequisiteThe VPU is configured.

ContextAsynchronous tones refer to digital tones that the UMG8900 does not need to play from thebeginning for an announcement playing request. The tone heard by the subscriber may be playedfrom the middle and repeatedly.

To configure the user access module (UAM), you must add the ringing tone, busy tone, andinitial ringing tone. The VPU provides the asynchronous tones.

Asynchronous tones of the same type can be configured on up to two boards.

NOTE

The ringing tone is an asynchronous tone. For example, the ringing tone used in China rings for one secondand keeps silent for four seconds periodically. A connected call may be mistaken as a call failed to beconnected if the ringing tone is in the four-second silent period. To avoid this, you can add the initial ringingtone on the VPU so that the UMG8900 plays the initial ringing tone before the ringing tone. Theconfiguration of the initial ringing tone is optional. It is recommended to configure the initial ringing tonetogether with the ringing tone.











Tone type <Tone type>



15-27

Procedure

Run ADD ATONE to add the synchronous tones.ADD ATONE: BT=<Board type>, BN=<Board No.>, TONEID=<Tone type>;

----End


//Configure synchronous tones.ADD ATONE: BT=VPU, BN=3, TONEID=RT; ADD ATONE: BT=VPU, BN=3, TONEID=BT; ADD ATONE: BT=VPU, BN=3, TONEID=INITRINGTONE;

15.4 Configuring UAM Environment Monitoring DataThis describes how to configure the user access module (UAM) environment monitoring data.

PrerequisiteThe physical cables are connected, including:

l Serial port connection between the ESC and the UAM

l Connection between the ESC and the monitored analog or digital sensor

l Connection between the ESC and the power supply

Context

Environment monitoring refers to monitoring on the status of environment parameters, includingtemperature, humidity, smoke, water penetration, fire alarm, and thief alarm of the cabledistribution frame, access control, inside of the cabinet, and outside of the cabinet, as well aspower parameters of the power supply and storage battery. If a monitored environment parameteris in abnormal state, the UMG8900 reports an alarm. Environment monitoring ensures that theUAM can run in a proper environment and the UMG8900 can run stably.

Environment monitoring on the UMG8900 requires functional modules for monitoring. Theenvironment monitoring module is classified into the following:

l Independent environment monitoring boards such as the ESC302 and the ESC303

l Monitoring modules embedded in the monitored device, such as power supply 4875 andpower supply 4845




Configuration Guide


Issue 02 (2008-05-07)





Board type <Board type> 15.1 Configuring UA Frames andBoards





EMU ID <EMU ID>

Switch value index <Switch value index>

Alarm mode <Alarm mode>

Analog value index <Analog value index>

Fan control mode <Fan control mode>

Power type <Power type>

Procedure

Step 1 Run ADD UABRD to configure the environment & power monitoring board (ESC). Set ESCtype to ESC303.ADD UABRD: FN=<Frame No.>, SN=<Slot No.>, BT=<Board type>, ET=ESC303;

Step 2 Run SET ESCSWITCH to configure the Boolean value output sensor for water penetration.Set Name to water.

NOTE

By default, the ESC is equipped with two Boolean value output sensors, that is, cable distribution framesensor and access control sensor. You do not need to configure these two sensors, and they use switch valueindexes 0 and 1 by default.

If you need to connect an external Boolean value output sensor of other types to the ESC, you must configurethe external Boolean value output sensor through this step.

SET ESCSWITCH: FN=<EMU ID>, IDX=<Switch value index>, FLG=<Alarm mode>,NAME="water";

Step 3 Run SET ESCANALOG to configure the analog sensor. Set Sensor type to Voltage, Unit tov, Name to Vol-A, Alarm upper limit to 100, Alarm lower limit to 50, Test upper limit to-27, and Test lower limit to 100.



15-29

SET ESCANALOG: FN=<EMU ID>, IDX=<Analog value index>, HLMT=100,LLMT=50, MHLMT=-27, MLMT=100, SENTYP=VOT, UNIT="V", NAME="Vol-A";

NOTE

By default, the ESC is equipped with two analog sensors, that is, temperature sensor and humidity sensor.You do not need to configure these two sensors, and they use analog value indexes 0 and 1 by default.

If you need to connect an external analog sensor of other types to the ESC, you must configure the externalanalog sensor through this step.

Step 4 Run SET UAFAN to configure ESC fan control parameters.SET UAFAN: FN=<EMU ID>, FMOD=<Fan control mode>;

Step 5 Run SET ESCPOWER to configure power supply control parameters.SET ESCPOWER: FN=<EMU ID>, TYP=<Power type>;

Step 6 After configuring environment monitoring, you can run DSP ESC to check the running statusof each monitored parameter.DSP ESC: FN=<EMU ID>;

----End

ExampleExample scriptADD UABRD: FN=1, SN=0, BT=ESC, ET=ESC303;//Configure monitoring parameters of an external water penetration sensor. SET ESCSWITCH: FN=1, IDX=5, FLG=LOW, NAME="water";//Configure monitoring parameters of an external voltage sensor. SET ESCANALOG: FN=0, IDX=N2, HLMT=100, LLMT=50, MHLMT=100, MLMT=-27, SENTYP=VOT, UNIT="V", NAME="Vol-A";//Configure monitoring on power supply 4810. SET ESCPOWER: FN=1, TYP=P4810;//Check monitored parameters. DSP ESC: FN=1;//Check whether the fan can be stopped. SET UAFAN: FN=0, FMOD=CLOSE; //If the fan can be stopped, it indicates that the control on the fan is realizable. Open the fan. SET UAFAN: FN=0, FMOD=OPEN;

15.5 Configuring the DDI/AT0 Trunk Access ServiceThis describes how to configure the direct-dialing-in (DDI) or AT0 trunk access service.

Context

The UMG8900 can connect private branch exchange (PBX) subscribers through analogsubscriber lines in DDI/AT0 trunk access mode.

The DDI/AT0 access solves the problem that an attendant console is required to transfer the callfrom a subscriber in the public network to a PBX subscriber. When calling a PBX subscriberwith the extension number, the subscriber directly dials the extension number without knowingthat the number is an extension number passing the switch.

The direct-dialing-in subscriber interface board (CDI) in the user access (UA) frame implementsthe DDI/AT0 service.


Configuration Guide


Issue 02 (2008-05-07)





Frame ID <FrameNo.>

15.1 Configuring UA Frames andBoards





Start port No. <Start port No.>


Port No. <Port No.>

Procedure

Step 1 Run SET CDIPRT to set attributes of ports on the CDI.

l If Call mode is set to HongKong telecom mode, run the following command:

SET CDIPRT: FN=<Frame No.>, SN=<Slot No.>, PN=<Start port No.>,CALLMODE=DID1;

l If Call mode is set to Singapore telecom mode, run the following command:

SET CDIPRT: FN=<Frame No.>, SN=<Slot No.>, PN=<Start port No.>,CALLMODE=DID2, CASNO=<CASATTR No.>;

Step 2 Run ADD PRTTS to add reserved timeslots.ADD PRTTS: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>;

----End


The UMG8900 connects to the PBX through two analog subscriber lines from ports 0 and 1 ofthe CDI. The Singapore telecom mode is adopted. Figure 15-15 shows the networking.



15-31

Figure 15-15 DDI/AT0 trunk access service

RSP14

CDI

PBX

UMG8900

Example script

//Configure the attributes of ports on the CDI. Set Call mode to Singapore telecom mode and CASATTR No. to 1.SET CDIPRT: FN=1, SN=3, PN=0, CALLMODE=DID2, CASNO=1; SET CDIPRT: FN=1, SN=3, PN=1, CALLMODE=DID2, CASNO=1;

//Reserve timeslots for ports 0 and 1 of the CDI.ADD PRTTS: FN=1, SN=3, PN=0; ADD PRTTS: FN=1, SN=3, PN=1;

15.6 Configuring the Hotline ServiceThis describes how to configure the hotline service.

PrerequisiteSubscriber boards in the user access (UA) frame are configured.

ContextThe hotline service is classified into the following:

l Hotline call service: If a subscriber does not dial a number within a specified time, such asfive seconds, after picking up the phone, the call is automatically connected to a fixednumber, also called hotline number.

l Immediate hotline service: After a subscriber picks up the phone, the call is automaticallyconnected to the called number specified in service subscription.




Configuration Guide


Issue 02 (2008-05-07)









Port No. <Port No.>

ProcedureRun ADD PRTTS to add reserved timeslots.

ADD PRTTS: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>;

The configuration of the hotline service is mainly on the media gateway controller (MGC). Youmust configure the hotline call authority for the subscriber and reserve the trunk. Refer to thedata configuration guide of the MGC. The configuration on the UMG8900 refers to reservingtimeslots for subscribers with the hotline call authority to ensure that subscribers can talk on thephone after off-hook.

NOTE

If no timeslot is reserved, hotline calls can also be completed in normal cases; however, hotline calls mayfail in busy hours because of failure to occupy timeslots.

----End

ExampleThe subscriber of port 0 on the A32 in the RSP_10 frame of the UMG8900 has the hotline callauthority and requires a reserved timeslot.

Example script

//Reserve a timeslot for port 0 on the A32. ADD PRTTS: FN=0, SN=5, PN=0;

15.7 Configuring the DDN Dedicated Line Service of theDSL

This describes how to configure the digital data network (DDN) dedicated line service of theDSL.



15-33

PrerequisiteThe related hardware of the UMG8900, E1 interface boards, and ISDN Q.921-User AdaptationLayer (IUA) links are configured.

Context

The DDN adopts digital channels to provide semi-permanent connection circuits to transmit datasignals. By using the time division multiplexing (TDM) mode and the circuit switchingtechnology, the DDN provides permanent or semi-permanent digital dedicated line connectionsto transparently transmit subscriber data.

The multifunctional terminal adapter (MTA) is a data service unit (DSU) positioned on thesubscriber side. The MTA is connected to the DSL through the 2B1Q interface. The accessdistance of the MTA is 4 to 5 kilometers, and the core diameter is 0.4 millimeter. The MTA canprovide one V.24/V.35 compatible interface, two V.24 interfaces, rate-synchronous port (64kbit/s or 128 kbit/s), and subrate-synchronous/asynchronous port (2.4 kbit/s, 4.8 kbit/s, 9.6 kbit/s, or 19.2 kbit/s). The subrate multiplexing protocol complies with the ITU-T X.50 Division3stipulations about twenty 8-bit envelope.

Networking Application

Through semi-permanent connections, the UMG8900 establishes digital dedicated lineconnections between the data terminal attached to the MTA and the DDN node machine, as wellas the data terminal attached to the MTA. Refer to Figure 15-16.

Figure 15-16 DDN dedicated line service

MTA MTA

V.35/V.24 V.24

DataTerminal

RouterData

Terminal

V.35

DDN node machine

DSL DSL

PV8/RSP

UMG8900 A

E1

E1

SPC(A)

SPC(B)




Configuration Guide


Issue 02 (2008-05-07)









MTA index <MTA index>

DSL frame No. <DSL frame No.>

DSL slot No. <DSL slot No.>

DSL port No. <DSL port No.>

Port0 rate <Port0 rate>

B channel of port 0 <Port0 B channel>

Semi-Permanent connection ID <ID>

Link type <Link type>

Direction <Direction>

Source frame No. <Src frame No.>

Source slot No. <Src slot No.>

Source port No. <Src port No.>

ProcedureStep 1 Run ADD MTA to add MTA configuration.

ADD MTA: MIDX=<MTA index>, FMN=<DSL frame No.>, SLTN=<DSL slot No.>,PRTN=<DSL port No.>, RATE0=<Port0 rate>, BCHANNEL0=<Port0 B channel>;

Step 2 Run ADD PRTTS to add reserved timeslots.ADD PRTTS: FN=<Frame No.>, SN=<Slot No.>, PN=<DSL port No.>;

Step 3 Run ADD SPC to add semi-permanent connections.ADD SPC: ID=<ID>, CT=<Link type>, CD=<Direction>, STFN=<Src frame No.>,STSN=<Src slot No.>, SPN=<Src port No.>,

----End



15-35




MTA

V.35

Router

DDN node machine

DSL

PV8/RSP

UMG8900

E1

E1

SPC

Example script//Configure the DDN dedicated line service on the DSL. //Configure an MTA on port 0 of the DSL on UMG8900. The rate for the first port of the MTA is configured as 64 kbit/s, and the B1 channel is used. ADD MTA: MIDX=0, FMN=1, SLTN=4, PRTN=0, Rate0=BAUD_RATE_64000, BChannel0=B1;

//Reserve timeslots for port 0 on the DSL. ADD PRTTS: FN=1, SN=4, PN=0;

//Add a semi-permanent connection between the B1 channel of port 0 on the DSL and timeslot 2 of port 0 on E32 0 on UMG8900.ADD SPC: ID=0, CT=TDM_UA, CD=DDIR, STFN=1, STSN=1, SPN=0, STS=2, DRFN=1, DRSN=4, DRPN=0;

15.8 Configuring the DDN Dedicated Line Service of theHSL

This describes how to configure the digital data network (DDN) dedicated line service of theHSL.

PrerequisiteThe HSL is in position, and data except the dedicated line service is configured.

ContextThe HSL is a high-speed line interface board of the UMG8900. The HSL can be inserted into aslot where the ASL or the A32 can be inserted. The HSL provides two FE1 and two V.35interfaces to implement the N x 64 kbit/s dedicated line service. Here, N ranges from 1 to 31.The V.35 interface connects to user devices such as routers.


Configuration Guide


Issue 02 (2008-05-07)

The V.35 interface can be connected in highway (HW) uplink mode or E1 bypass mode.

Networking ApplicationIn HW uplink mode, two V.35 terminals communicate with each other through the serviceswitching module (SSM). The maximum rate is 25 x 64 kbit/s. Figure 15-18 shows thenetworking in HW uplink mode.

Figure 15-18 HW uplink mode for the V.35 interface

UAM

SSM

HSL HSL

E1

Router Router

In E1 bypass mode, two HSLs are connected through E1 cables. Two V.35 terminals cancommunicate with each other through the user access module (UAM). The maximum rate is 31x 64 kbit/s. If the rate is equal to or greater than 6 x 64 kbit/s, the E1 bypass mode is recommended.Figure 15-19 shows the networking in E1 bypass mode.



15-37

Figure 15-19 E1 bypass mode for the V.35 interface

SSM

Router

UAM

HSL HSL

E1

E1

Router










Port No. <Port No.>

V35 rate <V35 rate>

V35 clock mode <V35 clock mode>

V35 work mode <V35 work mode>

E1 port <E1 port No.>

E1 timeslot No. <E1 timeslot No.>


Configuration Guide


Issue 02 (2008-05-07)


Clock source <Clock source>

E1 Frame <E1 Frame>



Source UA frame No. <Src frame No.>

Source UA slot No. <Src slot No.>

Source UA port No. <Src port No.>

Destination UA frame No. <Dst frame No.>

Destination UA slot No. <Dst slot No.>

Destination UA port No. <Dst port No.>

Procedure

Step 1 Run SET HSLPRT to set attributes of ports on the HSL.

l If Port type is set to V35 port, run the following commands:

– If V35 link is set to HW, run the following command:

SET HSLPRT: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>, PT=V35,MD=HW, RT=<V35 rate>, CLKMD=<V35 clock mode>, WM=<V35 work mode>;

– If V35 link is set to E1, run the following command:

SET HSLPRT: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>, PT=V35,MD=E1, E1N=<E1 port No.>, E1TS=<E1 timeslot No.>, RT=<V35 rate>,CLDMD=<V35 clock mode>, WM=<V35 work mode>;

l If Port type is set to FE1 port, run the following command:

SET HSLPRT: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>, PT=FE1,CLK=<Clock source> , FE=<E1 Frame>;

Step 2 If V35 link is set to HW, run ADD PRTTS to add reserved timeslots.ADD PRTTS: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>;

Step 3 If V35 link is set to HW, run ADD SPC to add semi-permanent connections. If Link type isset to UA_UA, run the following command:ADD SPC: ID=<ID>, CT=UA_UA, CD=<Direction>, SRFN=<Src frame No.>, SRSN=<Srcslot No.>, SRPN=<Src port No.>, DRFN=<Dst frame No.>, DRSN=<Dst slot No.>,DRPN=<Dst port No.>;

----End

Example

The configuration focuses on the V.35 connection modes.



15-39

l Networking diagram for the HW uplink mode


Example script

//Configure the N x 64 kbit/s dedicated line service of the HSL.//Configure V.35 port 1 on the HSL in slot 6 of the UMG8900.SET HSLPRT: FN=0, SN=6, PN=2, PT=V35, MD=HW, RT=25, CLKMD=INSIDE, WM=DCE;

//Configure V.35 port 1 on the HSL in slot 12 of the UMG8900. SET HSLPRT: FN=0, SN=12, PN=2, PT=V35, MD=HW, E1TS=1, RT=25, CLKMD=INSIDE, WM=DCE;

//Reserve timeslots for the HSL in slot 6.ADD PRTTS: FN=0, SN=6, PN=2;

//Reserve timeslots for the HSL in slot 12.ADD PRTTS: FN=0, SN=12, PN=2;

//Configure semi-permanent connections.ADD SPC: ID=4, CT=UA_UA, CD=DDIR, SRFN=0, SRSN=6, SRPN=2, DRFN=0, DRSN=12, DRPN=2;

l Networking diagram for the E1 bypass mode


Example script//Modify attributes of port 0 on the HSL in slot 4 of frame 2. Set Port type to V35 port, V35 link to E1, E1 port No. to 0, E1 timeslot No. to 2, V35 rate to 2, V35 clock mode to Inside mode, and V35 work mode to DCE.SET HSLPRT: FN=2, SN=4, PN=0, PT=V35, MD=E1, E1N=0, E1TS=2, RT=2, CLDMD= INSIDE, WM=DCE;

15.9 Configuring the DDN Dedicated Line Service of theSDL

This describes how to configure the digital data network (DDN) dedicated line service of theSDL.

PrerequisiteThe SDL and the hardware data are configured.

Context

The SDL is a high-speed line interface board of the UMG8900. The SDL can be inserted into aslot where the ASL or the A32 can be inserted. The SDL provides four FE1 and four SHDSLinterfaces to connect to the modem. The modem provides the V.35 interface to connect to therouter to implement the N x 64 kbit/s dedicated line service. Here, N ranges from 3 to 32.

The SHDSL interface can be connected in highway (HW) uplink mode or E1 bypass mode.

Networking Application

In HW uplink mode, two V.35 terminals communicate with each other through the serviceswitching module (SSM). The maximum rate is 25 x 64 kbit/s. Figure 15-20 shows thenetworking in HW uplink mode.


Configuration Guide


Issue 02 (2008-05-07)

Figure 15-20 HW uplink mode for the V.35 interface

UAM

SSM

SDL SDL

E1

Router Router

Modem Modem

In E1 bypass mode, two SDLs are connected through E1 cables. Two V.35 terminals cancommunicate with each other through the user access module (UAM). If Board mode is set toNormal and E1 frame is set to PCM31, the maximum rate is 31 x 64 kbit/s. If Board mode isset to Transfer, the maximum rate is 32 x 64 kbit/s.

If the rate is equal to or greater than 6 x 64 kbit/s, the E1 bypass mode is recommended. Figure15-21 shows the networking in E1 bypass mode.

Figure 15-21 E1 bypass mode for the V.35 interface

SSM

Router

UAM

SDL SDL

E1

E1

Router

Modem Modem



15-41










Port No. <Port No.>

Board mode <Board mode>


E1 Frame <E1 frame>



Max rate <Max rate>

Min rate <Min rate>

Trans-mode <Trans-mode>

SNR(dB) <SNR(dB>

Work mode <Work mode>

Frame switch <Frame switch>

Rx clock <Rx clock>

PLL lock <PLL lock>

Modem mode <Modem mode>





Configuration Guide


Issue 02 (2008-05-07)









Procedure

Step 1 Run SET SDLPRT to set attributes of ports on the SDL.l If Port type is set to FE1 port, run the following command:

SET SDLPRT: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>, PT=FE1,BRDMD=<Board mode>, CLK=<Clock source>, FE=<E1 frame>;

l If Port type is set to SHDSL port, run the following command:– If Link mode is set to HW, run the following command:

SET SDLPRT: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>, PT=SHDSL,BRDMD=<Board mode>, CLK=<Clock source>, MD=HW, MDM=<Modemmode>;

– If Link mode is set to E1, run the following command:SET SDLPRT: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>, PT=SHDSL,MD=E1, E1N=<E1 port No.>, E1TS=<E1 timeslot No.>, MAXR=<Max rate>,MINR=<Min rate>, TRNM=<Trans-mode>, SNRMG=<SNR(dB>, WD=<Workmode>, FW=<Frame switch>, RXCLK=<Rx clock>, PLOCK=<PLL lock>,MDM=<Modem mode>;

Step 2 If Link mode is set to HW, run ADD PRTTS to add reserved timeslots.ADD PRTTS: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>;

Step 3 If Link mode is set to HW, run ADD SPC to add semi-permanent connections. If Link type isset to UA_UA, run the following command:ADD SPC: ID=<ID>, CT=UA_UA, CD=<Direction>, SRFN=<Src frame No.>, SRSN=<Srcslot No.>, SRPN=<Src port No.>, DRFN=<Dst frame No.>, DRSN=<Dst slot No.>,DRPN=<Dst port No.>;

----End


In this example, the E1 bypass mode is adopted. Figure 15-21 shows the networking.

Example script



15-43

//Configure the N x 64 kbit/s dedicated line service of the SDL. //Configure E1 port 0 on the SDL in slot 6 of the UMG8900. SET SDLPRT: FN=1, SN=6, PN=0, PT=FE1, BRDMD=NORMAL, CLK=HW, FE=PCM31;

//Configure E1 port 0 on the SDL in slot 12 of the UMG8900. SET SDLPRT: FN=1, SN=12, PN=0, PT=FE1, BRDMD=NORMAL, CLK=HW, FE=PCM31;

//Configure SHDSL port 0 on the SDL in slot 6 of the UMG8900.SET SDLPRT: FN=1, SN=6, PN=4, PT=SHDSL, MD=E1, E1N=0, E1TS=1, MAXR=30, MINR=3, TRNM=G9912B, SNRMG=0, WD=CO, FW=OPENED, RXCLK=SLAVE, PLOCK=ENABLE, MDM=V35;

//Configure SHDSL port 0 on the SDL in slot 12 of the UMG8900. SET SDLPRT: FN=1, SN=12, PN=4, PT=SHDSL, MD=E1, E1N=0, E1TS=1, MAXR=30, MINR=3, TRNM=G9912B, SNRMG=0, WD=CO, FW=OPENED, RXCLK=SLAVE, PLOCK=ENABLE, MDM=V35;

15.10 Configuring the Audio Dedicated Line ServiceThis describes how to configure the audio dedicated line service.

PrerequisiteData except that of dedicated line services is configured.

ContextThe analog trunk interface (ATI) is a 2/4-wire E&M interface board of the UMG8900. The ATIcan be inserted into a slot where the ASL or the A32 can be inserted, and can provide six 2/4-wire E&M interfaces. The ATI functions as the analog trunk between offices. To transmit data,it may not use the E or M cables, but uses the 2/4-wire audio cable.

Networking ApplicationAt present, the UMG8900 connects different ATIs through semi-permanent connections toimplement dedicated line connections among 2/4-wire audio subscribers. Figure 15-22 showsthe networking.


Configuration Guide


Issue 02 (2008-05-07)

Figure 15-22 Audio dedicated line service networking

UMG8900A UMG8900B

IP

SPCIP

E1 E1

PV8/RSP PV8/RSP

ATI ATI ATI

AudioModem

AudioModem

AudioModem

DataTerminal

DataTerminal

DataTerminal

SPC(A)

SPC(B)










Port No. <Port No.>


IP domain ID <IP domain ID>



15-45


Local IP address <Local IP address>

Local UDP port No. <Local UDP port>

Remote IP address <Remote IP address>

Remote UDP port No. <Remote UDP port>

VPU board No. <VPU board No.>

Service type <Service type>

Codec type <Codec>

PTime(ms) <PTime(ms)>

Semi-permanent connection ID <ID>


Source IP address <Src IP address>

Source IP port <Src IP port>




ProcedureStep 1 Run SET ATIPRT to set attributes of ports on the ATI.

SET ATIPRT: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>, WORKMODE=<Workmode>;

Step 2 Run ADD PRTTS to add reserved timeslots.ADD PRTTS: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>;

Step 3 If the semi-permanent connection to be established, such as SPC (B) in Figure 15-22, is requiredto pass the IP network, you must add IP terminations of the semi-permanent connection inadvance. IP terminations of the semi-permanent connection must be added on UMG8900 A andUMG8900 B in advance. Local IP address and Local UDP port of the IP termination of thesemi-permanent connection of UMG8900 A must be the same as Remote IP address andRemote UDP port of that of UMG8900 B. Remote IP address and Remote UDP port of theIP termination of the semi-permanent connection of UMG8900 A must be the same as Local IPaddress and Local UDP port of that of UMG8900 B. Run ADD SPCIP to add IP terminationsof the semi-permanent connection.ADD SPCIP: IPDOMAIN=<IP domain ID>, LOCALIP=<Local IP address>,LOCALUDP=<Local UDP port>, REMOTEIP=<Remote IP address>,REMOTEUDP=<Remote UDP port>, VPUBRD=<VPU board No.>,SERVICETYPE=<Service type>, CODEC=<Codec>, PTIME=<PTime(ms)>;

Step 4 Run ADD SPC to add semi-permanent connections. If Link type is set to IP_UA, run thefollowing command:


Configuration Guide


Issue 02 (2008-05-07)

ADD SPC: ID=<ID>, CT=IP_UA, CD=<Direction>, SISA=<Src IP address>, SISP=<SrcIP port>, SIAD=<IP domain ID>, DRFN=<Dst frame No.>, DRSN=<Dst slot No.>,DRPN=<Dst port No.>;

----End



Example script

//Configure the audio dedicated line service inside UMG8900 A.//Set Work mode of port 0 on the ATIs in slots 3 and 4 to 4 line configure.SET ATIPRT: FN=0, SN=3, PN=0, WORKMODE=LINE4; SET ATIPRT: FN=0, SN=4, PN=0, WORKMODE=LINE4;

//Reserve timeslots for ports on the ATI.ADD PRTTS: FN=0, SN=3, PN=0; ADD PRTTS: FN=0, SN=4, PN=0;

//Configure the semi-permanent connection between port 0 on the ATI in slot 3 and port 0 on the ATI in slot 4. ADD SPC: ID=1, CT=UA_UA, CD=DDIR, SRFN=0, SRSN=3, SRPN=0, DRFN=0, DRSN=4, DRPN=0;

//Configure the audio dedicated line service between UMG8900 A and UMG8900 B.//Set Work mode of port 1 on the ATI in slot 4 of UMG8900 A to 4 line configure.SET ATIPRT: FN=0, SN=4, PN=1, WORKMODE=LINE4; //Set Work mode of port 1 on the ATI in slot 5 of UMG8900 B to 4 line configure.SET ATIPRT: FN=0, SN=5, PN=1, WORKMODE=LINE4;

//Reserve timeslots for port 1 on the ATI in slot 4 of UMG8900 A.ADD PRTTS: FN=0, SN=4, PN=1;

//Reserve timeslots for port 1 on the ATI in slot 5 of UMG8900 B.ADD PRTTS: FN=0, SN=5, PN=1;

//Configure the IP termination of the semi-permanent connection of UMG8900 A.ADD SPCIP: IPDOMAIN=0, LOCALIP="192.168.0.1", LOCALUDP=8000, REMOTEIP="172.16.0.1", REMOTEUDP=8000, VPUBRD=3, SERVICETYPE=BYPASS, CODEC=G711A, PTIME=PT20;

//Configure the IP termination of the semi-permanent connection of UMG8900 B. ADD SPCIP: IPDOMAIN=0, LOCALIP="172.16.0.1", LOCALUDP=8000, REMOTEIP="192.168.0.1", REMOTEUDP=8000, VPUBRD=3, SERVICETYPE=BYPASS, CODEC=G711A, PTIME=PT20;

//Configure the semi-permanent connection between port 1 on the ATI in slot 4 of UMG8900 A and the IP termination of the semi-permanent connection.ADD SPC: ID=2, CT=IP_UA, CD=DDIR, SISA="192.168.0.1", SISP=8000, SIAD=0, DRFN=0, DRSN=4, DRPN=1;

//Configure the semi-permanent connection between port 1 on the ATI in slot 5 of UMG8900 B and the IP termination of the semi-permanent connection.ADD SPC: ID=3, CT=IP_UA, CD=DDIR, SISA="172.16.0.1", SISP=8000, SIAD=0, DRFN=1, DRSN=5, DRPN=1;



15-47

16 Configuring StandAlone

This describes how to configure the StandAlone data, including the StandAlone data of the ESLsubscribers and that of the V5 subscribers.

Prerequisitel The TDM bearer is configured on the UMG8900.

l The V5E1 link is configured on the UMG8900.

l The LAPV5 link is configured on the UMG8900.

ContextStandAlone is a disaster tolerance solution of the UMG8900. If the media gateway controller(MGC) is faulty or the communication between the UMG8900 and the MGC fails, theUMG8900 is not controlled by the MGC; however, the UMG8900 can still implement basic callconnection between user access module (UAM) analog subscribers or subscribers accessedthrough devices in the V5 access network. That is, StandAlone imposes certain call controlfunctions of the MGC on the media gateway (MGW). Thus, StandAlone enhances the reliabilityof the MGW and enables networks to survive disasters.

After losing connection with the MGC, the UMG8900 enables StandAlone to control basic callsbetween analog subscribers, and the ongoing calls established by the MGC are not interrupted.When the connection between the UMG8900 and the MGC recovers, StandAlone automaticallyhands over the call control function to the MGC. Figure 16-1 shows the takeover of the callcontrol function from the MGC to StandAlone.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 16 Configuring StandAlone


16-1

Figure 16-1 Takeover of call control function from the MGC to StandAlone

MGC

UMG8900

H.248

StandAlone

MGC

UMG8900

H.248

StandAlone

A: Normally, the MGCcontrols calls.

B: When the UMG8900 loses contactwith the MGC, calls are connected in

StandAlone mode.

StandAlone supports only calls between analog subscribers in the same office rather thanoutgoing calls, and supports only the basic call control service rather than supplementary servicessuch as call forwarding.

In addition, StandAlone supports only calls between subscribers of the same virtual MGW(VMGW) rather than calls between subscribers of different VMGWs.





Virtual media gateway ID <Virtual media gatewayid>






Trunk group No. <V5 Group No.>

CMU module No. <CMU Module No.>

Start L3 E1 No. <Start L3 E1 ID>


Start AN E1 No. <Start AN E1 ID>

16 Configuring StandAloneHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)



V5 interface No. <V5 Interface No>

V5 interface ID <V5 Interface ID>

Master link <Main Link>

Logical C channel ID of the masterlink

<Main Logical C channel ID>

Slave link <Vice Link>

PSTN link <PSTN Link>

Logical C channel ID of the PSTNlink

<PSTN Logical C channel ID>

V5 start Phone Number <V5 Start Phone Number>

V5 end Phone Number <V5 End Phone Number>

Start L3 Address <Start L3 Address>

Add Type <Add Type>

Start phone number <Start Phone Number>

End phone number <End Phone Number>

DIGITMAP <DIGITMAP>

Local IP address <Local IP>

Local port No. <Locla Port>

iGWB IP <iGWB IP>

iGWB port <iGWB Port>

User type <User Type>

ProcedureStep 1 If the subscriber is a V5 subscriber, run ADD V5TG to add the V5 trunk group.

ADD V5TG: TKGNO=<V5 Group No.>, CMUBN=<CMU Module No.>,VMGWID=<Virtual media gateway id>, TKGNAME="V5 StandAlone";

Step 2 If the subscriber is a V5 subscriber, run ADD V5TKC to add the V5 trunk circuit.ADD V5TKC: TKGNO=<V5 Group No.>, L3SE1ID=<Start L3 E1 ID>, L2SE1ID=<StartL2 E1 ID>, ANSE1ID=<Start AN E1 ID>, STID=<Start TID>;

Step 3 If the subscriber is a V5 subscriber, run ADD V5I to add the V5 interface. Set Protect GroupType to Protect Group 2.ADD V5I: INFNO=<V5 Interface No>, TKGNO=<V5 Group No.>, INFID=<V5 InterfaceID>, MAINLNK=<Main Link>, MLNKID=<Main Logical C channel ID>, PROTTYP=P2,



16-3

VICELNK=<Vice Link>, PSTNLNK=<PSTN Link>, PSTNID=<PSTN Logical C channelID>, P2S1ID=1, P2S2ID=3, VARNO=0;

Step 4 Run ADD PHONENO to configure the telephone number table.l If the subscriber is a V5 subscriber and Phone Type is set to V5, run the following command:

ADD PHONENO: PHONETYPE=V5, V5SPHNNO=<V5 Start Phone Number>,V5EPHNNO=<V5 End Phone Number>, IID=<V5 Interface ID>, SL3ADDR=<Start L3Address>;

l If the subscriber is a UA subscriber and Phone Type is set to V5, run the following command:ADD PHONENO: PHONETYPE=ESL, MODE=<Add Type>, SPHNNO=<Start PhoneNumber>, EPHNNO=<End Phone Number>, STID=<Start TID>;

Step 5 Run SET CCDIGITMAP to configure the StandAlone digitmap.SET CCDIGITMAP: DIGITMAP=<DIGITMAP>

Step 6 Run SET IGWBINFO to configure the connection with the iGateway Bill (iGWB).SET IGWBINFO: SRCIP=<Local IP>, SRCPORT=<Locla Port>, DSTIP =<iGWB IP>,DSTPORT =<iGWB Port>;

CAUTIONAfter the UMG8900 is successfully connected with the iGWB, the UMG8900 registers theVMGW MID of the VMGW with the iGWB, and the related authentication information aboutthe VMGW MID need be added to the GatewayIDs.ini file of the iGWB. The UMG8900 sendsan authentication message of the VMGW MID of the VMGW before sending the bill to theiGWB. After the authentication succeeds, the iGWB can normally receive the correct bill fromthe UMG8900.

Step 7 Run SET CCSWT to enable StandAlone.SET CCSWT: VMGWID=<Virtual media gateway id>, USERTYPE=<User Type>,BILL=YES;

----End

ExampleExample scriptl For V5 subscribers

//Configure the V5 trunk.ADD V5TG: TKGNO=0, CMUBN=30, VMGWID=0, TKGNAME="V5 StandAlone";ADD V5TKC: TKGNO=0, L3SE1ID=0, L2SE1ID=0, ANSE1ID=0, STID=0; ADD V5TKC: TKGNO=0, L3SE1ID=1, L2SE1ID=1, ANSE1ID=1, STID=32; ADD V5TKC: TKGNO=0, L3SE1ID=2, L2SE1ID=2, ANSE1ID=2, STID=1024; ADD V5TKC: TKGNO=0, L3SE1ID=3, L2SE1ID=3, ANSE1ID=3, STID=1056;

//Configure the V5 interface. ADD V5I: INFNO=0, TKGNO=0, INFID=0, MAINLNK=0, MLNKID=0, PROTTYP=P2, VICELNK=2, PSTNLNK=4, PSTNID=1, P2S1ID=1, P2S2ID=3, VARNO=0;

//Configure the telephone number table. ADD PHONENO: PHONETYPE=V5, V5SPHNNO="6540080", V5EPHNNO="6540083", IID=0, SL3ADDR=0;

//Configure the StandAlone digitmap.

16 Configuring StandAloneHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

SET CCDIGITMAP: DIGITMAP="65400xx";

//Configure the connection with the iGWB. SET IGWBINFO: SRCIP="10.0.0.1", SRCPORT=1234, DSTIP="10.1.1.1", DSTPORT=1234;

CAUTIONThe iGWB can normally receive bills from the UMG8900 only when the authenticationinformation about the VMGW MID of the VMGW is added to the GatewayIDs.ini fileof the iGWB.

//If VMGW 0 whose ID is 10.1.1.1:3333 needs to send bills to the iGWB, you need to type the following 10.1.1.1:3333 262 in the GatewayIDs.ini file, where the number 262 is the module number without any practical meaning. The module number should range from 256 to 511.

//Enable StandAlone. SET CCSWT: VMGWID=0, USERTYPE=ESL-0&V5-1, BILL=YES;

l For ESL subscribers//Configure the phone number table. ADD PHONENO: PHONETYPE=ESL, MODE=BYTID, SPHNNO="6540070", EPHNNO="6540075", STID=64;

//Configure the StandAlone digitmap. SET CCDIGITMAP: DIGITMAP="65400xx";

//Configure the connection with the iGWB. SET IGWBINFO: SRCIP="10.0.0.1", SRCPORT=1234, DSTIP="10.1.1.1", DSTPORT=1234;

CAUTIONThe iGWB can normally receive bills from the UMG8900 only when the relatedauthentication information about the VMGW MID of the VMGW is added to theGatewayIDs.ini file of the iGWB.

//If VMGW 0 whose ID is 10.1.1.1:3333 needs to send bills to the iGWB, you need to type the following10.1.1.1:3333 262in the GatewayIDs.ini file, where the number 262 is the module number without any practical meaning. The module number should range from 256 to 511.

//Enable StandAlone. SET CCSWT: VMGWID=0, USERTYPE=ESL-1&V5-0, BILL=YES;



16-5

17 Configuring Service ResourceParameters

About This Chapter

This describes how to configure the service resource parameters, including the media resourceparameters, service parameters, and quality of service (QoS) parameters.

17.1 Configuring Media Resource ParametersThis describes how to configure the media resource parameters, including the voice codec, mediaprocessing parameters, transcoder (TC) work parameters, echo cancellation (EC) workparameters, MTC work parameters, voice enhancement work parameters, audio mixing state ofthe signal tones, alarm threshold of the resource utilization, common codec information, faxwork parameters, and RFC2833 parameters.

17.2 Configuring Service ParametersThis describes how to configure the service parameters.

17.3 Configuring QoS ParametersThis describes how to configure the quality of service (QoS) parameters.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 17 Configuring Service Resource Parameters


17-1

17.1 Configuring Media Resource ParametersThis describes how to configure the media resource parameters, including the voice codec, mediaprocessing parameters, transcoder (TC) work parameters, echo cancellation (EC) workparameters, MTC work parameters, voice enhancement work parameters, audio mixing state ofthe signal tones, alarm threshold of the resource utilization, common codec information, faxwork parameters, and RFC2833 parameters.

Prerequisitel The MGW control data is correctly set.

l The bearer data is correctly set.

l The signaling transfer data is correctly set.

Background Information

CAUTIONThe configuration of codec capability causes the reset of the VPU. In this case, all the sessionson the VPU are lost. It is recommended to use SET CODECCAP when a new office is set upor the UMG8900 is ready to restart.

The configuration in this step is not mandatory, and the configuration varies with the applicationscenarios. Configure the resource parameters based on the actual conditions.

In different application scenarios, different subboards are configured on the VPU and differentTC or EC resources are provided. Refer to Table 17-1.

Table 17-1 Board configuration of the VPU

Board No. Resource Function Restrictions

MVPD1 Two VDB subboards are configured toprovide 1024 channels of TCresources.

-

MVPD2 Two VDB subboards and one ECCsubboard are configured to provide1024 channels of TC and 64 ms ECresources.

The MVPD1 and the MVPD2 are notconfigured at the same time. Ifneeded, use the MVPD2 only.

MVPD3 One ECC subboard is configured toprovide 1024 channels of 64 ms ECresources.

In an SSM-256 frame, the MECU,rather than the VPD3, provides ECresources.

MVPD4 One VDB subboard is configured toprovide 512 channels of TDMannouncement playing resources.

-

17 Configuring Service Resource ParametersHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)

Board No. Resource Function Restrictions

MVPD6 Two VDB subboards and one ECEsubboard are configured to provide1024 channels of TC and 128 ms ECresources.

-

MVPD8 Two VDB subboards and one ECJsubboard are configured to provide1024 channels of TC and 64 ms ECresources.

-

MVPD9 One ECJ subboard is configured toprovide 1024 channels of 64 ms ECresources.

-

MVPD10 Two VDB subboards and one ECKsubboard are configured to provide1024 channels of TC and 128 ms ECresources.

-

MVPD11 Two VDB subboards and one VQEsubboard are configured to provide1024 channels of TC and VQEresources.

-

MVPD12 One VQE subboard is configured toprovide VQE resources.

-

MVPD13 Two VDB subboards and one ECFsubboard are configured to provide1024 channels of TC and 64 ms ECresources.

-

MVPD15 One ECF subboard is configured toprovide 1024 channels of 64 ms ECresources.

-

MVPD16 Two VDB subboards and one ECGsubboard are configured to provide1024 channels of TC and 128 ms ECresources.

-

You can run DSP MEDIARES to query media resources, such as TC, EC, conference channel(CC), multiplex transcode channel (MTC), voice quality enhancement (VQE), and channelassociated signaling (CAS), of the UMG8900.





17-3







Codec capability set <Codec>

MPTY channel number <MPTY channel num>

CAS channel number <MPTY channel num>

Support public codec <Support public codec>

Loading tone file type of the broadbandcodec capability set

<Tonefile Type in WideBand Codec set>

A/Mu law <A/MU law>

Start timer length(s) <Start timer length(s)>

VAD option <VAD option>

Packet Loss compensation <Packet Loss compensation>

G.711 PTime(ms) <G.711 PTime(ms)>

EEC tail length(ms) <EEC tail length(ms)>

Comfort noise generation mode <Comfort noise generation mode>

TFO switch <TFO SWITCH>

Noise reduction aggressiveness (dB) <Noise reduction aggressiveness (dB)>

Maximum gain for noise compensation(dB)

<Maximum gain for noise compensation (dB)>

Tone number <Tone number>

tone mix state <tone mix state>

Resource type <Resource type>

Threshold(%) <Alarm Threshold>

General codec No. <General Codec No.>

General codec name <General Codec Name>

T38 PTime(ms) <T38 Fax PTime(ms)>


Configuration Guide


Issue 02 (2008-05-07)


T38 Max transmit speed(bps) <T38 Max transmit speed(bps)>

T38 train mode <T38 Train mode>

IFP type <FAX TYPE>

Redundant number <Redundant number>

Redundant package payload type <Redundant Package Payload Type>

RFC2833 sending mode of DTMF <RFC2833 sending mode of DTMF>

Named packet payload type <Named packet payload type>

Send interval(ms) <Ipti>

Codec <Codec>

RFCI length <Rfci Length>

New RFCI No. <New RFCI No.>

ProcedureStep 1 Run SET CODECCAP to set the supported codec capability set.

SET CODECCAP: BN=<Board No.>, CODEC=<Codec>, MPTYCHN=<MPTY channelnum>, CASCHN=<MPTY channel num>;

Step 2 Run SET MRPARA to set the media processing parameter. The board media processingparameter is set by default, and the default value of the MGW is often used.SET MRPARA: AMU=<A/MU law>, STLEN=<Start timer length(s)>;

Step 3 Run SET TCPARA to set the TC resource parameter.SET TCPARA: VAD=<VAD option>, PLC=<Packet Loss compensation>, G711PT=<G.711PTime(ms)>;

Step 4 Run SET ECPARA to set the EC resource parameter.SET ECPARA: BT=<Board No.>, TL=<EEC tail length(ms)>, CNG=<Comfort noisegeneration mode>, TFOSW=<TFO SWITCH>;

Step 5 If the work parameter of the VIG feature needs to be modified, run SET MTCPARA to set theMTC work parameters.SET MTCPARA: VAD=<VAD option>;

Step 6 Run SET VQEPARA to set the voice enhancement work parameter.SET VQEPARA: NRGN=<Noise reduction aggressiveness (dB)>, NCMXGN=<Maximumgain for noise compensation (dB)>;

Step 7 If a tone needs to be set to a mixed audio, run SET TONEMIX to set the audio mixing state ofthe tone signal. Otherwise, skip the step.SET TONEMIX: TONENO=<Tone number>, MIXSTATE=<tone mix state>;

Step 8 If reporting the alarm of the utilization overload of the TC and EC resources is required, runSET RESTHD to set the alarm threshold of the resource utilization.



17-5

SET RESTHD: RESTP=<Resource type>, AT=<Alarm Threshold>;

Step 9 If the fax work parameter is required, run SET FAXPARA to set the fax work parameter.SET FAXPARA: FFI=<T38 Fax PTime(ms)>, MFS=<T38 Max transmit speed(bps)>,TM=<T38 Train mode>;

Step 10 When the network quality is poor, run SET FAXRDNT to set the quantity of the fax redundancypacket for the pack loss concealment.l Set FAX TYPE to T38 Over UDPTL.

SET FAXRDNT: TYPE=UDPTL_T38, FT=<FAX TYPE>, RN=<Redundantnumber>;

l Set FAX TYPE to T38 OverRTP.SET FAXRDNT: TYPE=RTP_T38, RN=<Redundant number>,RDNT_PT=<Redundant Package Payload Type>;

Step 11 Run SET RFC2833 to set the RFC2833 parameter.SET RFC2833: RM=<RFC2833 sending mode of DTMF>,NPT=<Named packet payloadtype>;

----End

ExampleExample scriptSET CODECCAP: BN=0, CODEC=NGN-1&MTPY-1, MPTYCHN=CHN256; SET CODECCAP: BN=1, CODEC=NGN-1&MTPY-1, MPTYCHN=CHN256; SET CODECCAP: BN=2, CODEC=NGN-1&MTPY-1, MPTYCHN=CHN256; SET CODECCAP: BN=3, CODEC=NGN-1&MTPY-1, MPTYCHN=CHN256; SET TCPARA: PLC=ENABLE, G711PT=PT20; SET ECPARA: TL=EC_TAIL_LENGTH_64; SET FAXPARA: FFI=FAX_FRAME_10MS, MFS=FAX_SPEED_14400, TM=LOCAL, ECM=NON_ECM_MODE, FV=-6, DS=V21-1, G711DS=CNG-0&CED-0;

17.2 Configuring Service ParametersThis describes how to configure the service parameters.











Configuration Guide


Issue 02 (2008-05-07)





Alarm high threshold of fraction lost(%)

<Alarm high threshold of fraction lost(%)>

Alarm low threshold of fraction lost(%) <Alarm low threshold of fraction lost(%)>

Lost rate of disconnection(%) <Lost rate of disconnection(%)>

Alarm high threshold of packet jitter(ms)

<Alarm high threshold of packet jitter (ms)>

Alarm low threshold of packet jitter(ms)

<Alarm low threshold of packet jitter (ms)>

Alarm high threshold of packet delay(ms)

<Alarm high threshold of packet delay (ms)>

Alarm low threshold of packet delay(ms)

<Alarm low threshold of packet delay (ms)>

Sending period of RTCP packet (s) <Sending period of RTCP packet (s)>

Switch to send RTCP packets or not <Switch to send RTCP packets or not>

Release unstable links automatically ornot

<Release unstable links automatically ornot>

RTCP transmission mode <RTCP transmission mode>

Send RTCP packets or not during IMSperiod

<Send RTCP packets or not during IMSperiod>

Gmin of RTCP XR <Gmin of RTCP XR>

RTCP XR support mode <RTCP XR support mode>

E1 Switch to open RTCP or not <E1 Switch to open RTCP or not>

None E1 Switch to open RTCP or not <None E1 Switch to open RTCP or not>

Release threshold for no RTCP packetreceived

<Release threshold for no RTCP packetreceived>

Average rate <Average rate (kbps)>

Peak rate <Peak rate (kbps)>

Dynamic adjust enable <Dynamic adjust enable>

JBU depth for 5-ms service <JBU depth for 5-ms service>



17-7



Host dynamic time <Host dynamic time>

Timeout(s) <Timeout(s)>

Launch time <Launch time>

Initialization frame resend times <Initialization frame resend times>

Initialization frame resend interval <Initialization frame resend interval(ms)>

Time align frame resend times <Time align frame resend times>

Time align frame resend interval <Time align frame resend interval(ms)>

Rate control frame resend times <Rate control frame resend times>

Rate control frame resend interval <Rate control frame resend interval(ms)>

ProcedureStep 1 Run SET RTCP to set the RTCP protocol parameter.

SET RTCP: WLOSSH=<Alarm high threshold of fraction lost(%)>, WLOSSL=<Alarm lowthreshold of fraction lost(%)>, CLOSS=<Lost rate of disconnection(%)>, JITBUFH=<Alarmhigh threshold of packet jitter (ms)>, JITBUFL=<Alarm low threshold of packet jitter (ms)>, PKGDLYH=<Alarm high threshold of packet delay (ms)>, PKGDLYL=<Alarm lowthreshold of packet delay (ms)>, TIMER=<Sending period of RTCP packet (s)>,SENDFLAG=<Switch to send RTCP packets or not>, LINKFLAG=<Release unstable linksautomatically or not>, SENDMODE=<RTCP transmission mode>, VADFLAG=<SendRTCP packets or not during IMS period>, GMIN=<Gmin of RTCP XR>,XRSUPPORT=<RTCP XR support mode>, E1OPENRTCP=<E1 Switch to open RTCP ornot>, NOE1OPENRTCP=<None E1 Switch to open RTCP or not>,NORTCPTIMES=<Release threshold for no RTCP packet received>;

Step 2 Run SET TOTALNPCAR to set the total traffic parameter of the control packet on the HRB.SET TOTALNPCAR: BN=<Board No.>, AVERAGERATE=<Average rate (kbps)>,PEAKRATE=<Peak rate (kbps)>;

Step 3 Run SET JBUPARA to configure the JBU attribute parameters.SET JBUPARA: BN=<Board No.>, DYNDIS=<Dynamic adjustenable>,JBUFOR5MS=<JBU depth for 5-ms service>, JBUFOR20MS=<JBU depth for 20-ms service>, HOSTDYNTIME=<Host dynamic time>;

Step 4 Run SET IPBCP to set the IPBCP protocol parameter.SET IPBCP: BN=<Board No.>, TIMEOUT=<Timeout(s)>, LAUTM=<Launch time>;

----End

ExampleExample scriptSET RTCP: WLOSSH=70, WLOSSL=60, CLOSS=90, JITBUFH=8, JITBUFL=6, PKGDLYH=1400, PKGDLYL=1200, TIMER=5, SENDFLAG=NOSEND, LINKFLAG=NO, SENDMODE=END, VADFLAG=YES,


Configuration Guide


Issue 02 (2008-05-07)

GMIN=20, XRSUPPORT=BOTHSUPPORT,E1OPENRTCP=CLOSE, NOE1OPENRTCP=OPEN, NORTCPTIMES=65535;SET TOTALNPCAR: BN=0, AVERAGERATE=3750, PEAKRATE=8000;SET JBUPARA: BN=0, DYNDIS=Enable,JBUFOR5MS=4, JBUFOR20MS=2, HOSTDYNTIME=4; SET IPBCP: BN=0, TIMEOUT=6, LAUTM=FAST;

17.3 Configuring QoS ParametersThis describes how to configure the quality of service (QoS) parameters.









Interface IP address <Interface IPaddress>






Domain <Domain>

Protocol type <Protocol type>

Dscp/TOS value <IPQOS Value>

Precedence field <Precedence>

Packet type <Packet type>

Priority <Priority>

DSCP value <DSCP value>

High priority call threshold <High Priority Call Threshold>

High rate occupied threshold <High Rate Occupied Threshold(%)>



17-9


Low rate occupied threshold <Low Rate Occupied Threshold(%)>

Procedure

Step 1 Run SET IPQOS to configure the DSCP/TOS parameters.SET IPQOS: DOMAIN=<Domain>, IPADDR=<Interface IP address>,ProTYPE=<Protocol type>, IpQosValue=<IPQOS Value>, PRE=<Precedence>,PT=<Packet type>;

Step 2 Run SET PRITODSCP to set the DSCP value corresponding to the call priority.SET PRITODSCP: PRIORITY=<Priority>,DSCP=<DSCP value>;

Step 3 Run SET CALLPRI to allocate resources to the call with a high priority level.SET CALLPRI:CALPRI=<High Priority Call Threshold>,HIRT=<High Rate OccupiedThreshold(%)>,LORT=<Low Rate Occupied Threshold(%)>

----End

ExampleExample scriptSET IPQOS: DOMAIN=0, IPADDR="1.1.1.1", ProTYPE=DSCP, IpQosValue=G_0-1&G_1-0&G_2-0&G_3-0&G_4-0&G_5-0, PRE=HIGH, PT=CONTROL;SET PRITODSCP: PRIORITY=Priority4,DSCP=AF11;SET CALLPRI:CALPRI=8,HIRT=80,LORT=75;


Configuration Guide


Issue 02 (2008-05-07)

18 Configuring IP Network Security Data

About This Chapter

This describes how to configure the Internet Protocol (IP) network security data, including howto configure the firewall, IP Security Protocol (IPSec), and Security Shell (SSH). TheUMG8900 can enable the firewall and the IPSec function on the media gateway (MGW) controlinterface, network management interface, and signaling transport (SIGTRAN) interface toachieve security protection on these types of control packets. Based on the SSH protocol, youcan log in to and manage the UMG8900 to implement the security of the remote login.

Context18.1 Configuration the FirewallThis describes how to configure the firewall.

18.2 Configuring IPSecThis describes how to configure the IP Security Protocol (IPSec) data.

18.3 Configuring SSHThis describes how to configure the security shell (SSH) data.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide 18 Configuring IP Network Security Data


18-1

18.1 Configuration the FirewallThis describes how to configure the firewall.

Index Mapping of Configuration Command Parameters

Figure 18-1 shows the index mapping of the major configuration command parameters of thefirewall.

Figure 18-1 Index mapping of the configuration command parameters of the firewall

ADD PRDCTM

SET ACL

NUM

ADD SACL(EACL)

NUMTIME

ADD TIMERANG

NAME

ADD ABSTM

NAME

NAME

SET FIREWALL

ACLBTBN

STR FIREWALL

BTBN








18 Configuring IP Network Security DataHUAWEI UMG8900 Universal Media Gateway

Configuration Guide


Issue 02 (2008-05-07)



ACL number <ACL number>

Match sequence of ACL sub-rule <Match sequence of ACL sub-rule>

Time range name <Time range name>

Start time of the absolute time range <Start time>

Start date of the absolute time range <Start date>

End time of the absolute time range <End time>

End date of the absolute time range <End date>

Start time of the period time range <Start time>

End time of the period time range <End time>

Week of the period time range <Week>

Filtering rule <Filtering rule>


Reverse wildcard bits <Reverse wildcard bits>

Whether to make log <Whether to make log>



Packet receiving and sending direction <Inbound/Outbound packets>

Default filtering rule <Default filtering rule>

Procedure

Step 1 Run SET ACL to set the match order of the ACL rule.SET ACL: NUM=<ACL number>, SORT=<Match sequence of ACL sub-rule>;

Step 2 Run ADD ABSTM to add the absolute time range.ADD ABSTM: NAME=<Time range name>, STIME=<Start time>, SDATE=<Start date>,ETIME=<End time>, EDATE=<End date>;

Step 3 Run ADD PRDCTM to add the period time range.ADD PRDCTM: NAME=<Time range name>, STIME=<Start time>, ETIME=<Endtime>, DAY=<Week>;

Step 4 Run ADD SACL to add the standard ACL rule.ADD SACL: NUM=<ACL number>, RULE=<Filtering rule>, IP=<IP address>,RMASK=<Reverse wildcard bits>, LOG=<Whether to make log>;



18-3

Step 5 Run SET FIREWALL to configure the ACL rules of the firewall.SET FIREWALL: BT=<Board type>, BN=<Board No.>, IFT=<Interface type>,IFN=<Interface No.>, DIRE=<Inbound/Outbound packets>, ACL=<ACL number>;

Step 6 Run STR FIREWALL to start the firewall.STR FIREWALL: BT=<Board type>, BN=<Board No.>, RULE=<Default filtering rule>;

----End

ExampleExample scriptSET ACL: NUM=1, SORT=CONFIG;ADD ABSTM: NAME="timerang1", STIME=17&07&23, SDATE=2007&09&23, ETIME=17&08&24, EDATE=2007&09&24;ADD PRDCTM: NAME="timerang1", STIME=08&00&00, ETIME=18&00&00, DAY=MON;ADD SACL: NUM=1, RULE=permit, IP="192.168.0.0", MASK="0.0.0.255", LOG=YES;SET FIREWALL: BT=HRB, BN=0, IFT=ETH, IFN=0, DIRE=IN, ACL=1;STR FIREWALL: BT=HRB, BN=0, RULE=permit;

PostrequisiteAfter configuring the firewall, configure the IP Security Protocol (IPSec) and security shell(SSH) based on the requirements.

l Configuring IPSec

l Configuring SSH

18.2 Configuring IPSecThis describes how to configure the IP Security Protocol (IPSec) data.

Index Mapping of Configuration Command ParametersFigure 18-2 shows the index mapping of the configuration command parameters of IPSec.


Configuration Guide


Issue 02 (2008-05-07)

Figure 18-2 Index mapping of the configuration command parameters of IPSec

ADD EACL

NUMRULE

ADD ISTM

ISTMNPROTAHA

ESPAESPE

ADD ISSP

ISSPGN

NUMISTMN

LIPPIPACL

SET IPIFSPG

ENABLEISSPGN

AIKF/AIHK/AISKAOKF/AOHK/AOSK

EIKF/EIHAK/EIHEK/EISK

EOKF/EOHAK/EOHEK/EOSK

AISAOS

EISEOS











18-5


Parameter Name UMG8900 InterconnectedDevice

ACL number <ACL number> -

Filtering rule <Filtering rule> -

Protocol No. <Protocol No.> -

Source IP address <Source IP address> The same as that of thepeer device

Source reverse wildcard bits <Source reverse wildcardbits>

-

Destination IP address The same as that of the peerdevice

<Destination IPaddress>

Destination reverse wildcardbits

<Destination reversewildcard bits>

-

Transform name <Transform name> -

Protocol <Protocol> The same as that of thepeer device

Encapsulation mode <Encapsulation mode> -

AH authentication <AH authentication> The same as that of thepeer device

ESP authentication <ESP authentication> The same as that of thepeer device

ESP encryption <ESP encryption> The same as that of thepeer device

SPG name <SPG name> -

SPG No. <Num> -

SPG mode <SPG MODE> -


AH input SPI <AH input SPI> The same as that of thepeer device

AH input hex key <AH input key format> The same as that of thepeer device

AH output SPI <AH output SPI> The same as that of thepeer device

AH output hex key <AH output key format> The same as that of thepeer device


Configuration Guide


Issue 02 (2008-05-07)

Parameter Name UMG8900 InterconnectedDevice

AH input string key <AH input string key> The same as that of thepeer device

AH output hex key <AH output hex key> The same as that of thepeer device

Local IP address <Local IP> The same as that of thepeer device

Remote IP address The same as that of the peerdevice

<Peer IP>

Interface ID <Interface index> -

Enable IPSec <Enable IPSec> -


Procedure

Step 1 Run ADD EACL to add the extended ACL rule.ADD EACL: NUM=<ACL number>, RULE=<Filtering rule>, PROT=<Protocol No.>,SIP=<Source IP address>, SRMSK=<Source reverse wildcard bits>, SOP=EQ, SP1=20,DIP=<Destination IP address>, DRMSK=<Destination reverse wildcard bits>, LOG=YES,TIME="TILL2003";

Step 2 Run ADD ISTM to add the IPSec conversion mode.ADD ISTM: ISTMN=<Transform name>, PROT=<Protocol>, AM=<Encapsulationmode>, ESPA=<ESP authentication>, ESPE=<ESP encryption>;

Step 3 Run ADD ISSP to add the IPSec security policy.ADD ISSP: ISSPGN=<SPG name>, NUM=<Num>, ISTMN=<Transform name>,LIP=<Local IP>, PIP=<Peer IP>, ACL=<ACL number>, TYPE=<SPG MODE>, AIS=<AHinput SPI>, AIKF=<AH input key format>, AISK=<AH input string key>, AOS=<AH outputSPI>, AOKF=<AH output key format>, AOHK=<AH output hex key>;

Step 4 Run SET IPIFSPG to set the IPSec security policy group of the interface.SET IPIFSPG: BT=<Board type>, BN=<Board No.>, IFT=<Interface type>,IFN=<Interface index>, ENABLE=<Enable IPSec>, ISSPGN=<SPG name>;

----End

ExampleExample scriptADD EACL: NUM=100, RULE=permit, PROT=TCP, SIP="192.168.0.0", SMSK="0.0.0.255", SOP=eq, SP1=20, DIP="202.118.0.0", DMSK="0.0.0.255", LOG=YES, TIME="TILL2003";ADD ISTM: ISTMN="mode1", PROT=ESP, AM=TRANSPORT, ESPA=SHA1, ESPE=TripleDES;ADD ISSP: ISSPGN="isspg1", NUM=1, ISTMN="istm1", LIP="1.1.1.1", PIP="2.2.2.2", ACL=100, TYPE=MANUAL, AIS=256, AIKF=STRING, AISK="KEY", AOS=256, AOKF=HEX, AOHK="00112233445566778899aabbccddeeff";SET IPIFSPG: BT=HRB, BN=0, IFT=ETH, IFN=0, ENABLE=YES, ISSPGN="d";



18-7

PostrequisiteAfter configuring the IPSec, configure security shell (SSH) based on the requirements.

Configuring SSH

18.3 Configuring SSHThis describes how to configure the security shell (SSH) data.

ContextSSH is a safe remote login protocol developed based on Telnet. The protocol number is 22. SSHsupports the password and revest-shamir-adleman algorithm (RSA) authentication. In addition,it performs the data encryption standard (DES) and 3DES encryption on data and thus protectsthe integrity and reliability of the data. When the SSH client communicates with the server, boththe username and password are encrypted so that interception on the password is prevented andsecure transfer of data is ensured. The RSA authentication supports the mixed application ofsymmetrical and asymmetrical encryptions and secure exchange of keys, and finally realizessecure sessions. The SSH offsets the disadvantage of Telnet and securely achieves the remotelogin and access.

Figure 18-3 shows the steps for configuring the SSH.

Figure 18-3 Steps for configuring the SSH

Configure the SSH client software andgenerate the client key

Start

Add new user accounts on theUMG8900(optional)

Configure the SSH user accountsand type the client key

Configure the SSH serverpatameters(optional)

Configure Telnet timeouttime(optional)

End


Configuration Guide


Issue 02 (2008-05-07)

NOTE

l If you do not add new user accounts on the UMG8900, you can set existing users to SSH users.

l The timeout time of the SSH connection is the same as that of Telnet. You can set it with SETTEOV.





SSH user name <Account>

Authentication type <Authentication Type>

RSA authentication public key file <RSA Authentication Pubilc Key File>

Server key update interval (hour) <Server Key Update Interval(Hour)>

SSH authentication timeout (minute) <SSH Authentication Timeout(Minute)>

SSH authentication retry times <SSH Authentication Retry Times>

Enable SSHV1.X <Enable SSHV1.X>

enhSession key exchange interval (hour) <SessionKey Exchange Interval(Hour)>

Procedure

Step 1 Run SET SSHOP to set the SSH user account. Set SSH User Link Type to SSH.SET SSHOP: OP=<Account>, ENSSH=SSH, AUTHTYPE=<Authentication Type>,RSAPUBKEY="<RSA Authentication Pubilc Key File>";

Step 2 Run SET SSHSRV to set the SSH server parameters.SET SSHSRV: REKEY=<Server Key Update Interval(Hour)>, TIMEOUT=<SSHAuthentication Timeout(Minute)>, RETRIES=<SSH Authentication Retry Times>,ENSSHV1X=<Enable SSHV1.X>,EXKEY=<SessionKey Exchange Interval(Hour)>;

----End

ExampleExample scriptSET SSHOP: OP="sshuser", ENSSH=SSH, AUTHTYPE=RSA_PASSWORD, RSAPUBKEY="c:/bam/id_rsa.pub";SET SSHSRV: REKEY=2,TIMEOUT=1,RETRIES=3,ENSSHV1X=1,EXKEY=1;

PostrequisiteAfter configuring the SSH, configure other data based on the requirements.



18-9

A Data Planning

This describes the data planning of the UMG8900.

Configuring System Parameters

Table A-1 Data planning


IP address of the version server <IP Address of Version Server>

User name of the version server <User Name of Version Server>

Password of the version server <Password of Version Server>

System Node No. <System Node No.>


Coding length <National network structure>



Upper limit of the input voltagealarm (V)

<Upper Limit of the Input Voltage Alarm (V)>

Lower limit of the input voltagealarm (V)

<Lower Limit of the Input Voltage Alarm (V)>

Upper limit of the environmenttemperature alarm (C)

<Upper Limit of the Environment Temperature Alarm(C)>

Lower limit of the environmenttemperature alarm (C)

<Lower Limit of the Environment Temperature Alarm(C)>

Upper limit of the environmenttemperature alarm (F)

<Upper Limit of the Environment Temperature Alarm(F)>

Lower limit of the environmenttemperature alarm (F)

<Lower Limit of the Environment Temperature Alarm(F)>

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide A Data Planning


A-1



Buzzer switch <Switch>


Port No. of the environmental alarmchest

<Port No.>

Alarm ID <Alarm ID>

Digital port alarm voltage <Digital Port Alarm Voltage>

Alarm name <Alarm Name>

Alarm level <Alarm Level>

Net management type <Net Management Type>

Configuring the System Time


Parameter Name UMG8900 Interconnected Device(NTP Server)

Date <Date> -

Time <Time> -

Adjust value (s) <Adjust value(s)> -

Daylight saving time <Daylight saving time> -

Time zone <Time zone> -

Start date mode <Start date mod> -

Start month <Start month> -

Start date <Start date> -

Start week <Start week> -

Start time <Start time> -

End date mode <End date mode> -

End month <End month> -

End date <End date> -

End week <End week> -

End time <End time> -

A Data PlanningHUAWEI UMG8900 Universal Media Gateway

Configuration Guide

A-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)

Parameter Name UMG8900 Interconnected Device(NTP Server)

Time offset (minute) <Time offset(minute)> -

IP address of the NTPserver

The same as that of the peer device <NTP IP Address>

Whether to authenticate theID

<Authentication> -

Authentication key ID <Authentication key ID> -

Authentication key <Authentication key> -

Version The same as that of the peer device <NTP Version>

Prefer <Prefer> -

Configuring the NMS Interface




IP address of theNMS interface

<Interface IPaddress>


-

IP address and maskof the NMS interface



-


- -

In VLAN <In VLAN> - -

IP address of theNMS


<Destinationaddress>

-

IP address and maskof the NMS



-

IP address of therouter directlyconnected with theUMG8900


- <Next hop address>

Protocol type The same as that ofthe peer device

<Protocol type> -



A-3

Configuring SNMP Data


Parameter Name UMG8900 Interconnected Device (NMS)

NMS version <Version No.> The same as that of the peer device

SNMP view name <View name> -

Mib object subtreeOID

<Mib object subtree OID> -

Operate type <Operate type> -

SNMP group name <Group Name> The same as that of the peer device

Security level <Security level> The same as that of the peer device

Read view name <Read View Name> -

Write view name <Write View Name> -

Notify view name <Notify View Name> -

SNMP user name <User Name> The same as that of the peer device

Authenticationprotocol

<Authentication Protocol> The same as that of the peer device

Authenticationpassword

<Authentication Password> The same as that of the peer device

Encryption protocol <Privacy Protocol> The same as that of the peer device

Encryption password <Privacy Password> The same as that of the peer device

SNMP group name <Community Name> The same as that of the peer device

Access mode <Access Mode> -

IP address of the hostreceiving the SNMPnotification


<Host Address>

Port No. <UDP Port No.> The same as that of the peer device

Trap type <Trap type> -

Configuring Frames and Boards





Configuration Guide


Issue 02 (2008-05-07)


Frame version <Frame Ver>

Cascading mode <FE Cascading Mode>

Cascading board No. <Cascading Board No.>

Configure GE cascade <Configure GE Cascade>

Local frame GE cascade slot No. <Local Frame GE Cascade Slot No.>

Up frame GE cascade slot No. <Up Frame GE Cascade Slot No.>

Up frame GE port No. <Up Frame GE Port No.>

Configure TDM cascade <Configure TDM Cascade>




Frame position <Frame Position>

Frame name <Frame Name>

Frame description <Frame Description>

Slot No. <Slot No.>



Backup type <Backup type>

Hardware type <Hardware type>


Configuring the Clock



Priority of GPS reference source <Priority of GPS reference source>



Priority of external synchronous 1 <Priority of external synchronous 1>

Priority of external synchronous 2 <Priority of external synchronous 2>



A-5


Type of external synchronous <Type of external synchronous>

Select mode of reference source <Select Mode of Reference Source>

Clock level <Clock Level>

Type of clock signal of externalsynchronous output

<Type of Clock Signal of External Synchronous Output>

Whether SSM control <Whether SSM Control>

External reference source workmode

<External Reference Source Work Mode>

Line clock <Line Clock>

Interface type <Interface Type>

Port No. <Port No.>

Channel No. <Channel No.>

SSM timeslot <SSM Time Slot>

Configuring Physical Interfaces of Gateway Control Interfaces and SIGTRANInterfaces


ParameterName




Work mode <Work Mode> - - -

Interface type <Interfacetype>

- - -

Interface ID <Interface No.> - - -

IP addresses 1 ofgateway controlinterfaces andSIGTRANinterfaces



- -

IP addresses 2 ofgateway controlinterfaces andSIGTRANinterfaces



- -


Configuration Guide


Issue 02 (2008-05-07)

ParameterName




IP address andmask ofgateway controlinterfaces andSIGTRANinterfaces



- -

Master or slaveflag

<Master orslave flag>

- - -

Slot No. <Slot No.> - - -




- -




- -

IP address andmask of theMGC



- -

IP address of therouterconnected withthe UMG8900


- <Next hopaddress>

-

IP address of thegateway


- - <Gateway IP>

If aging or not <If aging ornot>

- - -

Configuring E1 Physical Interfaces Carrying IP Signaling Packets



TDM optical port No. <TDM opt port No.> -

TDM port No. <TDM port No.> -



A-7


IOE internal TDM portNo.

<IOE internal TDM port No.> -

Port description <Port description> -

Start TID <Start TID> -

End TID <End TID> -

CMU module No. <CMU Module No.> -

TDM start timeslot <Start timeslot> -

TDM end timeslot <End timeslot> -

Serial interface ID <Interface No.> -


Serial interfacedescription

<Interface description> -

MP enable <MP enable> -

VT interface ID <VT Interface No.> -

IP address of the MGC The same as that of the peer device <Destination address>

IP address and mask ofthe MGC

The same as that of the peer device <Destination addressmask>



ParameterName





- -


Configuration Guide


Issue 02 (2008-05-07)

ParameterName




l In domainmode:<Virtualmedia gatewayMID>_1

l In IP mode: <Virtualmedia gatewayMID>_2

l In device mode:<Virtual mediagateway MID>_3

- -

Master MGCID


- -

Slave MGCID


- -

Master MGCID type



-

Slave MGCID type



-

Master MGCID



-

Slave MGCID



-

IP address ofthe masterDNS server



IP address ofthe slaveDNS server



Configuring Links over UDP


Parameter Name UMG8900 Interconnected Device (MGC)




A-9


UDP port No. to themaster MGC


UDP port No. to theslave MGC








UDP port No. to themaster MGC



UDP port No. to theslave MGC





-

H.248 signalinglink No. to the slaveMGC


-

Configuring H.248 Links over SCTP




Checksumalgorithm

<Checksum algorithm> The same as that of the peer device

Path mode <path mode> -















Configuration Guide


Issue 02 (2008-05-07)















SubBoard No. <SubBoard No.> -

Configuring H.245 Links


Parameter Name UMG8900 Interconnected Device(MGC)


The same as that of the peer device <Peer Master address>_1


The same as that of the peer device <Peer Master address>_2

Port No. to themaster MGC

The same as that of the peer device <Peer port No.>_1

Port No. to the slaveMGC

The same as that of the peer device <Peer port No.>_2

Port No. of H.245signaling links tothe master MGC


Port No. of H.245signaling links tothe slave MGC






A-11

Parameter Name UMG8900 Interconnected Device(MGC)



Configuring SDH Interface Protection










SD flag <SD flag>



Operate mode <Command type>

Configuring E1/T1 Interfaces





Frame format <Frame Structure> The same as that of the peerdevice

Tx line code structure <Tx line Code Structure> The same as that of the peerdevice


Configuration Guide


Issue 02 (2008-05-07)


Rx line code structure <Rx line Code Structure> The same as that of the peerdevice

Distance Mode <Distance Mode> -

Configuring E3/T3 Interfaces





Distance Mode <Communication Distance> -

frame type <Frame type> The same as that of the peerdevice

Start channel No. <Start Chan No.> -

End channel No. <End Chan No.> -

Frame format <Frame mode> The same as that of the peerdevice

Configuring the SDH Interface (S2L/S1L)



SDH port No. <SDH port No.> -

E1/T1 channel No. <Channel No.> -

Receiving C2 byte <Receiving C2 byte> The same as that of the peerdevice

Transmitting C2 byte <Transmitting C2 byte> The same as that of the peerdevice





A-13






Frame type <Frame type> -

Frame mode 1 <Frame mode 1> The same as that of the peerdevice

Load type <Load type> The same as that of the peerdevice

Start Channel No. <Start Channel No.> -

End Channel No. <End Channel No.> -

E1/T1 Frame format <Frame format> -

Period <Period> -

Status <Status> -

Configuring TDM Timeslots




End TID <End TID>


Configuring Trunk Group Management



Trunk group No. <TG No.>


Configuration Guide


Issue 02 (2008-05-07)


Trunk group information <TG No. Info>


End TID <End TID>

Configuring Office Direction



Office No. <Office No.>

Port No. <Port No.>

Start port No. <Start Port No.>

End port No. <End Port No.>

Configuring the FE Interface




VLAN ID <VLAN ID>








Domain <Domain>



A-15

Configuring the GE Interface




VLAN ID <VLAN ID>








Domain <Domain>

Auto negotiation <Auto negotiation>

Configuring the ATM Interface




C2 byte <C2 byte>

J0 byte <J0 byte>

J1 byte <J1 byte>

K1 byte <K1 byte>

K2 byte <K2 byte>

VPI <VPI>

VCI <VCI>

Default static MAP <Default static MAP>


Encapsulation protocol <Enc protocol>



Configuration Guide


Issue 02 (2008-05-07)


ATM interface No. <Interface No.>

Maximum transmission unit of theATM interface


Enable ATM interface <Interface enable>

CRC length <Length of CRC>

Configuring the IP over E1 Interface



TDM optical port No. <TDM opt port No.>

TDM port No. <TDM port No.>

IOE internal port No. <IOE internal TDM port No.>

TDM start timeslot <Start timeslot>

TDM end timeslot <End timeslot>

Serial interface ID <Serial Interface No.>

Route type <Routing Type>

Destination IP address <Remote IP address>

Route No. <Routing No.>

Transmitting board type <Transmitting board type>

Transmitting board No. <Transmitting board No.>

Transmitting IP address <Transmitting IP address>

VPI <VPI>

VCI <VCI>


MP enable <MP enable>

VT Interface No. <VT Interface No.>



A-17

Configuring the IP Address





Interface IP address mask <Interface IP address mask>

Master or slave flag <Master or slave flag>

In VLAN <In VLAN>


Configuring IP Interface Protection





BFD configuration name <BFD configuration name>

Detect type <Detect type>



Domain <Domain>







SD flag <SD flag>




Configuration Guide


Issue 02 (2008-05-07)

Configuring the Gateway IP Address



IP address of the gateway <Gateway IP>

If aging or not <If aging or not>

Configuring SIGTRAN of MTP2-M2UA


ParameterName





<Checksumalgorithm>


- -

Link group No. <Link set No.> - - -




- -

Work mode <Traffic mode> The same asthat of the peerdevice

- -


<Link No.>_1 - - -


<Link No.>_2 - - -


<Local portNo.>_1

- - -


<Local portNo.>_2

- - -



<Remote portNo.>_1

- -



<Remote portNo.>_2

- -



<Remoteaddress1>_1

- -



A-19

ParameterName






<Remoteaddress2>_1



<Remoteaddress1>_2

- -



<Remoteaddress2>_2

Priority of theM2UA link to themaster MGC

<Priority>_1 - - -

Priority of theM2UA link to theslave MGC

<Priority>_2 - - -



- <DNS IPaddress>

-

Path Mode <Path Mode> - - -

MTP2 link No. <Link No.> - - -

E1/T1 No. <E1T1 No.> - - -

Start timeslot No. <Start time slot> - - The same as thatof the peerdevice

End timeslot No. <End time slot> - - The same as thatof the peerdevice


- - -

Integer interfaceID

<Int-typeinterface ID>


- -


Configuration Guide


Issue 02 (2008-05-07)

Configuring SIGTRAN of LAPV5-V5UA





<Checksumalgorithm>


-





-


-


<Link No.>_1 - -

Link No. to the slaveMGC

<Link No.>_2 - -

SCTP port No. to themaster MGC


-

SCTP port No. to theslave MGC


-



<Remote portNo.>_1

-



<Remote portNo.>_2

-



<Remoteaddress1>_1

-



<Remoteaddress2>_1

-



<Remoteaddress1>_2

-



<Remoteaddress2>_2

-

Priority of the V5UAlink to the masterMGC

<Priority>_1 - -

Priority of the V5UAlink to the slaveMGC

<Priority>_2 - -



A-21





- <DNS-IPaddress>

Path Mode <Path Mode> - -

E1ID <E1 ID> - -

E1 link ID <E1 link ID> The same as that ofthe peer device

-

E1 No. <E1 No.> - -

V5UA link No. <Link No.> - -

Timeslot No. <Time slot> - The same as that ofthe peer device

Subboard No. <SPF sub-board No.> - -

Configuring SIGTRAN of Q.921-IUA





<Checksum algorithm> The same as that of thepeer device

-



<Use text-type interfaceID>


-

Work mode <Traffic mode> The same as that of thepeer device

-


<Link No.>_1 - -

Link No. to the slaveMGC

<Link No.>_2 - -


<Local port No.>_1 The same as that of thepeer device

-


<Local port No.>_2 The same as that of thepeer device

-


Configuration Guide


Issue 02 (2008-05-07)





<Remote port No.>_1 -



<Remote port No.>_2 -



<Remote address1>_1 -










Priority of the IUAlink to the masterMGC

<Priority>_1 - -

Priority of the IUAlink to the slaveMGC

<Priority>_2 - -



<DNS-IP address> - -

Q.921 link No. <Q921 Link No.> - -

Integer interface ID <Int-type interface ID> The same as that of thepeer device

-

E1/T1 No. <E1T1 No.> - -

Timeslot No. <Time slot> - The same asthat of the peerdevice

SPF subboard No. <SPF sub-board No.> - -

Network side andsubscriber side

<Net/User side> - -



A-23

Configuring SIGTRAN over M3UA (MTP3-M3UA)




Local entity index <Local Entity Index> - -

Local network ID <NetworkIndicator>


-

Local Entity Type <Local Entity Type> - -

M3UA Destinationentity index

<Destination EntityIndex>

- -

Network ID of theM3UA destinationentity


<Network Indicator> -

Destination EntityType

- <Destination EntityType>

-

Destinationsignaling Point Code


<Destinationsignaling Point Code>

-

A-interface protocolnumber

<A-InterfaceProtocol Number>

- The same as that ofthe peer device

M3UA link set index <Link Set Index> - -

Discard messagesfrom lower prioritylink

<Discard messagesfrom lower prioritylink>

- -

Working Mode <Working Mode> - -

M3UA signaling linkNo. to the masterMGC

<M3UA Link No.>_1 - -

M3UA signaling linkNo. to the slave MGC

<M3UA Link No.>_2 - -


<Local Port>_1 The same as that of thepeer device

-


<Local Port>_2 The same as that of thepeer device

-




-




-


Configuration Guide


Issue 02 (2008-05-07)





<Remote Port>_1 -




-




-



<Remote Port>_2 -


N7 destination signalpoint index


- <DSP index>

N7 destinationNetwork indicator


- <Networkindicator>

N7 DPC The same as that ofthe peer device

- <DSP>

OPC index <OPC index> - The same as that ofthe peer device

N7 link set index <Linkset index> - -

N7 route index <Route index> - -

MTP2 link No. <Link No.> - -

E1/T1 No. <E1T1 No.> - -

Start timeslot No. <Start time slot> - The same as that ofthe peer device


- -

N7 link index <Link index> - -

N7 link code <Signaling linkcode>

- The same as that ofthe peer device



A-25

Configuring Semi-permanent Connection




Start TID <Start TID> - -

End TID <End TID> - -

Semi-permanentconnection ID

<ID> The same as that of thepeer device


Semi-permanentconnection name

<Name> - -

Interworking type <Link type> - -

Direction <Direction> - -

Source frame No. <Src frame No.> The same as that of thepeer device


Source slot No. <Src slot No.> The same as that of thepeer device


Source port No. <Src port No.> The same as that of thepeer device


Source timeslot No. <Src timeslot No.> The same as that of thepeer device


Destination frameNo.

<Dst frame No.> The same as that of thepeer device


Destination slot No. <Dst slot No.> The same as that of thepeer device


Destination timeslotNo.

<Dst port No.> The same as that of thepeer device


Destination timeslotNo.

<Dst timeslot No.> The same as that of thepeer device


Configuring CAS



Signaling name <CAS name>


Configuration Guide


Issue 02 (2008-05-07)


Signaling type <signaling type>

Line signaling type <Line signaling>

Register signaling type <Register signaling>

CAS attribute index <Index>

Address send list <Address send list>

Address receive list <Address receive list>

Pulse No. <Pulse No.>

Line signaling conversion index <Line signaling conversion index>

Line command conversion index <Line command conversion index>

Register signaling conversion index <Register signaling conversion index>

Register command conversion index <Register command conversion index>


End TID <End TID>

Configuring Frames and Boards in the UAM




End TID <End TID>

Trunk type <Relay type>


Field ID <Place No.>


Frame No. in cabinet <Frame No. in cabinet>

Frame type <Frame type>

Mode <Frame mode>

CMU module No. <CMU module No.>

Slot No. <Slot No.>




A-27


Link group No. <Link set No.>

Integer interface ID <Int interface ID>

Configuring Connections to the Main Frame and Direct Frame




SPF board No. <SPF board No.>

SPF subboard No. <SPF subboard No.>

First board No. <First trunk board No.>

First port No. <First port No.>

Second board No. <Second trunk board No.>

Second port No. <Second port No.>

Third board No. <Third trunk board No.>

Third port No. <Third port No.>

Fourth board No. <Fourth trunk board No.>

Fourth port No. <Fourth port No.>

Fifth board No. <Fifth trunk board No.>

Fifth port No. <Fifth port No.>

Sixth board No. <Sixth trunk board No.>

Sixth port No. <Sixth port No.>

Seventh board No. <Seventh trunk board No.>

Seventh port No. <Seventh port No.>

Eighth board No. <Eighth trunk board No.>

Eighth port No. <Eighth port No.>


Configuration Guide


Issue 02 (2008-05-07)

Configuring Connections to the RSP Subframe




PV8 frame No. <PV8 slot No.>

First HW No. <First HW No.>

Second HW No. <Second HW No.>

Third HW No. <Third HW No.>

Fourth HW No. <Fourth HW No.>

Fifth HW No. <Fifth HW No.>

Sixth HW No. <Sixth HW No.>

Seventh HW No. <Seventh HW No.>

Eighth HW No. <Eighth HW No.>

Configuring Connections to the RSA Subframe




RSA frame No. <RSA Frame No.>

Slot No. of the RSA <RSA slot No.>

Configuring Connections From High-Density Subframe




RSU frame No. <RSU frame No.>

Cascading interface <Cascade>



A-29

Configuring Asynchronous Tone



Tone type <Tone type>

Configuring StandAlone



Trunk group No. <V5 Group No.>

CMU module No. <CMU Module No.>



Start AN E1 No. <Start AN E1 ID>


V5 interface No. <V5 Interface No>

V5 interface ID <V5 Interface ID>

Master link <Main Link>

Logical C channel ID of the master link <Main Logical C channel ID>

Slave link <Vice Link>

PSTN link <PSTN Link>

Logical C channel ID of the PSTN link <PSTN Logical C channel ID>

V5 start Phone Number <V5 Start Phone Number>

V5 end Phone Number <V5 End Phone Number>

Start L3 Address <Start L3 Address>

Add Type <Add Type>

Start phone number <Start Phone Number>

End phone number <End Phone Number>

DIGITMAP <DIGITMAP>

Local IP address <Local IP>

Local port No. <Locla Port>


Configuration Guide


Issue 02 (2008-05-07)


iGWB IP <iGWB IP>

iGWB port <iGWB Port>

User type <User Type>

Configuring UAM Environmental Monitoring



EMU ID <EMU ID>

Switch value index <Switch value index>

Alarm mode <Alarm mode>

Analog value index <Analog value index>

Fan control mode <Fan control mode>

Power type <Power type>

Configuring DDI/AT0 Trunk Access Services



Start port No. <Start port No.>


Port No. <Port No.>

Configuring Hotline Services



Port No. <Port No.>



A-31

Configuring DDN Services of the DSL



MTA index <MTA index>

DSL frame No. <DSL frame No.>

DSL slot No. <DSL slot No.>

DSL port No. <DSL port No.>

Port0 rate <Port0 rate>

B channel of port 0 <Port0 B channel>


Link type <Link type>


Source frame No. <Src frame No.>

Source slot No. <Src slot No.>

Source port No. <Src port No.>

Configuring DDN Services of the HSL



Port No. <Port No.>

V35 rate <V35 rate>

V35 clock mode <V35 clock mode>

V35 work mode <V35 work mode>




E1 Frame <E1 Frame>





Configuration Guide


Issue 02 (2008-05-07)







Configuring DDN Services of the SDL



Port No. <Port No.>



E1 Frame <E1 frame>



Max rate <Max rate>

Min rate <Min rate>

Trans-mode <Trans-mode>

SNR(dB) <SNR(dB>


Frame switch <Frame switch>

Rx clock <Rx clock>

PLL lock <PLL lock>

Modem mode <Modem mode>








A-33







Configuring Audio Dedicated Line Services



Port No. <Port No.>


IP domain ID <IP domain ID>

Local IP address <Local IP address>

Local UDP port No. <Local UDP port>

Remote IP address <Remote IP address>

Remote UDP port No. <Remote UDP port>

VPU board No. <VPU board No.>

Service type <Service type>

Codec type <Codec>

PTime(ms) <PTime(ms)>

Semi-permanent connection ID <ID>


Source IP address <Src IP address>

Source IP port <Src IP port>





Configuration Guide


Issue 02 (2008-05-07)

Configuring Media Resource Parameters



Codec capability set <Codec>

MPTY channel number <MPTY channel num>

CAS channel number <MPTY channel num>

Support public codec <Support public codec>

Loading tone file type of the broadbandcodec capability set

<Tonefile Type in WideBand Codec set>

A/Mu law <A/MU law>

Start timer length(s) <Start timer length(s)>

VAD option <VAD option>

Packet Loss compensation <Packet Loss compensation>

G.711 PTime(ms) <G.711 PTime(ms)>

EEC tail length(ms) <EEC tail length(ms)>

Comfort noise generation mode <Comfort noise generation mode>

TFO switch <TFO SWITCH>

Noise reduction aggressiveness (dB) <Noise reduction aggressiveness (dB)>

Maximum gain for noise compensation(dB)

<Maximum gain for noise compensation (dB)>

Tone number <Tone number>

tone mix state <tone mix state>

Resource type <Resource type>

Threshold(%) <Alarm Threshold>

General codec No. <General Codec No.>

General codec name <General Codec Name>

T38 PTime(ms) <T38 Fax PTime(ms)>

T38 Max transmit speed(bps) <T38 Max transmit speed(bps)>

T38 train mode <T38 Train mode>

IFP type <FAX TYPE>

Redundant number <Redundant number>

Redundant package payload type <Redundant Package Payload Type>



A-35


RFC2833 sending mode of DTMF <RFC2833 sending mode of DTMF>

Named packet payload type <Named packet payload type>

Send interval(ms) <Ipti>

Codec <Codec>

RFCI length <Rfci Length>

New RFCI No. <New RFCI No.>

Configuring Service Parameters



Alarm high threshold of fraction lost(%) <Alarm high threshold of fraction lost(%)>

Alarm low threshold of fraction lost(%) <Alarm low threshold of fraction lost(%)>

Lost rate of disconnection(%) <Lost rate of disconnection(%)>

Alarm high threshold of packet jitter (ms) <Alarm high threshold of packet jitter (ms)>

Alarm low threshold of packet jitter (ms) <Alarm low threshold of packet jitter (ms)>

Alarm high threshold of packet delay (ms) <Alarm high threshold of packet delay (ms)>

Alarm low threshold of packet delay (ms) <Alarm low threshold of packet delay (ms)>

Sending period of RTCP packet (s) <Sending period of RTCP packet (s)>

Switch to send RTCP packets or not <Switch to send RTCP packets or not>

Release unstable links automatically ornot

<Release unstable links automatically or not>

RTCP transmission mode <RTCP transmission mode>

Send RTCP packets or not during IMSperiod

<Send RTCP packets or not during IMS period>

Gmin of RTCP XR <Gmin of RTCP XR>

RTCP XR support mode <RTCP XR support mode>

E1 Switch to open RTCP or not <E1 Switch to open RTCP or not>

None E1 Switch to open RTCP or not <None E1 Switch to open RTCP or not>

Release threshold for no RTCP packetreceived

<Release threshold for no RTCP packetreceived>


Configuration Guide


Issue 02 (2008-05-07)


Average rate <Average rate (kbps)>

Peak rate <Peak rate (kbps)>

Dynamic adjust enable <Dynamic adjust enable>



Host dynamic time <Host dynamic time>

Timeout(s) <Timeout(s)>

Launch time <Launch time>

Initialization frame resend times <Initialization frame resend times>

Initialization frame resend interval <Initialization frame resend interval(ms)>

Time align frame resend times <Time align frame resend times>

Time align frame resend interval <Time align frame resend interval(ms)>

Rate control frame resend times <Rate control frame resend times>

Rate control frame resend interval <Rate control frame resend interval(ms)>

Configuring QoS Parameters



Domain <Domain>

Protocol type <Protocol type>

Dscp/TOS value <IPQOS Value>

Precedence field <Precedence>

Packet type <Packet type>

Priority <Priority>

DSCP value <DSCP value>

High priority call threshold <High Priority Call Threshold>

High rate occupied threshold <High Rate Occupied Threshold(%)>

Low rate occupied threshold <Low Rate Occupied Threshold(%)>



A-37

Configuring Firewall



ACL number <ACL number>

Match sequence of ACL sub-rule <Match sequence of ACL sub-rule>

Time range name <Time range name>

Start time of the absolute time range <Start time>

Start date of the absolute time range <Start date>

End time of the absolute time range <End time>

End date of the absolute time range <End date>

Start time of the period time range <Start time>

End time of the period time range <End time>

Week of the period time range <Week>

Filtering rule <Filtering rule>


Reverse wildcard bits <Reverse wildcard bits>

Whether to make log <Whether to make log>



Packet receiving and sending direction <Inbound/Outbound packets>

Default filtering rule <Default filtering rule>

Configuring IPSec



ACL number <ACL number> -

Filtering rule <Filtering rule> -

Protocol No. <Protocol No.> -

Source IP address <Source IP address> The same as that of the peerdevice


Configuration Guide


Issue 02 (2008-05-07)


Source reverse wildcard bits <Source reverse wildcardbits>

-

Destination IP address The same as that of the peerdevice

<Destination IP address>

Destination reverse wildcardbits

<Destination reversewildcard bits>

-


Protocol <Protocol> The same as that of the peerdevice

Encapsulation mode <Encapsulation mode> -

AH authentication <AH authentication> The same as that of the peerdevice

ESP authentication <ESP authentication> The same as that of the peerdevice

ESP encryption <ESP encryption> The same as that of the peerdevice

SPG name <SPG name> -

SPG No. <Num> -

SPG mode <SPG MODE> -


AH input SPI <AH input SPI> The same as that of the peerdevice

AH input hex key <AH input key format> The same as that of the peerdevice

AH output SPI <AH output SPI> The same as that of the peerdevice

AH output hex key <AH output key format> The same as that of the peerdevice

AH input string key <AH input string key> The same as that of the peerdevice

AH output hex key <AH output hex key> The same as that of the peerdevice

Local IP address <Local IP> The same as that of the peerdevice

Remote IP address The same as that of the peerdevice

<Peer IP>



A-39


Interface ID <Interface index> -

Enable IPSec <Enable IPSec> -


Configuring SSH



SSH user name <Account>

Authentication type <Authentication Type>

RSA authentication public key file <RSA Authentication Pubilc Key File>

Server key update interval (hour) <Server Key Update Interval(Hour)>

SSH authentication timeout (minute) <SSH Authentication Timeout(Minute)>

SSH authentication retry times <SSH Authentication Retry Times>

Enable SSHV1.X <Enable SSHV1.X>

enhSession key exchange interval (hour) <SessionKey Exchange Interval(Hour)>


Configuration Guide


Issue 02 (2008-05-07)

B Glossary

Numerics

3GPP See 3rd generation partnership project

3rd generationpartnership project

Founded in 1998, a project which aims to expedite the development of open, globallyaccepted technical specifications for the Universal Mobile Telecommunications System(UMTS), including the WCDMA and TD-SCDMA specifications. The WCDMAspecifications developed by the 3GPP include 3GPP R99, R4, R5, R6, and R7.

A

A interface An interface between the BSS and MSC. It is a 2G interface. Its physical link adopts the2.048 Mbit/s PCM digital transmission link to transmit the information related to callprocessing, mobility management and BSS management. It adopts the BSSAP protocol.

AAL See ATM adaptation layer

access A link between the customer and the telecommunication network. Many technologies,such as the copper wire, optical fiber, mobile, microwave and satellite, are used foraccess.

access control list A series of sequential rules consisting of permit | deny statements. In firewall, after ACLis applied to an interface on the router, the router decides which packet can be forwardedand which packet should be denied. In QoS, ACL is used to classify traffic.

access network A local part of a telecommunication network. It is closest to the subscriber's home orenterprise and opposite to the core network.

ACL See access control list

add/drop multiplexer A digital multiplexing device that offers interfaces between different signals in anetwork.

address A number that identifies the location of a device in a network or the location on the harddisk or the memory, such as the IPv4 address or IPv6 address of a network entity.

address resolutionprotocol

A protocol used in the IP network to map an IP address to a MAC address and thus enablethe transmission of IP datagram across a LAN.

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide B Glossary


B-1

adjacency A portion of the local routing information which pertains to the reachability of a singleneighbour ES or IS over a single circuit. Adjacencies are used as input to the DecisionProcess for forming paths through the routing domain. A separate adjacency is createdfor each neighbouron a circuit, and for each level of routeing (i.e. level 1 and level 2) ona broadcast circuit.

ADM See add/drop multiplexer

AGC See automatic gain control

AH See authentication header

american nationalstandards institute

The American National Standards Institute is a voluntary membership organization (runwith private funding) that develops national consensus standards for a wide variety ofdevices and procedures.

AN See access network

analog signal A signal sent by an analog system without restriction specified on transmitted data.

ANSI See american national standards institute

application serviceprovider

A business that provides computer-based services to customers over a network.

APS See automatic protection switching

APS 1+1 Indicates that the protective group uses the master/slave interfaces mode. The APSprotective mode is supported.One protection group has one work channel and oneprotection channel. The switchover is performed based on the APS protocol. In thenormal state, the work channel is working. If an APS switchover event is detected bythe work channel, the services are switched to the protection channel.

APS 1:N Indicates that the protective group uses one protective channel and N pieces of workingchannels. The APS protective mode is supported. One protection group has N workchannels and one protection channel. The switchover is performed based on the APSprotocol. In the normal state, N work channels are working. If an APS switchover eventis detected by one work channel, the services are switched to the protection channel. TheAPS protection requires the interconnected device to support the APS protocol.

area A routing subdomain that maintains the detailed routing information about its owninternal composition and the routing information enabling it to reach the other routingsubdomains.In IS-IS and OSPF, it is a set of adjacent networks and hosts that have beenadministratively grouped together within an autonomous system. In IS-IS, an areacorresponds to a Level 1 subdomain.

ARP See address resolution protocol

ASP See application service provider

association Logical association or channels that are established between two SCTP terminationsaccording to the four-handshake system of the SCTP protocol.

asynchronousannouncement

A digital announcement not always played by the MGW from beginning when receivingan announcement request. This kind of digital announcement is the asynchronousannouncement. Therefore, a subscriber might hear a section of an announcement playedrepeatedly from beginning or middle. The MGW can play a broadcast announcement formultiple subscribers (no limit to the number of subscribers) at a time. The basic serviceannouncement is a common asynchronous announcement.

B GlossaryHUAWEI UMG8900 Universal Media Gateway

Configuration Guide

B-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)

asynchronous transfermode

A data transfer technology based on cell, in which packets allocation relies on channeldemand. It supports fast packet switching so that the network resources can be usedefficiently. The size of a cell is fixed, 53 bytes in total. Here, 48 bytes form the payloadand the other five bytes form the header.

ATM See asynchronous transfer mode

ATM adaptation layer A collection of protocols that enable the voice, data, image, and video traffic to run overan ATM network.

ATM switch A switch to transmit cells through an ATM network. It receives the incoming cell froman ATM endpoint or another ATM switch, analyzes and updates the cell headerinformation, and then switches the cell to an output interface towards the destination.

authentication header It is a type of IPv6 extension headers, and is also a kind of IPsec. It ensures data integrity,authenticates original identities, and provides some optional and limited anti-replayservices for IP.

auto negotiation A procedure defined in Fast Ethernet in which a device accords with another device ona transmission mode before transmitting data. The mode can be 100 Mbit/s or 10 Mbit/s and full or half duplex.

automatic gain control A process or means by which gain is automatically adjusted in a specified manner as afunction of a specified parameter, such as received signal level.

automatic protectionswitching

Automatic Protection Switching (APS) is the capability of a transmission system todetect a failure on a working facility and to switch to a standby facility to recover thetraffic.

available user capacity A capacity that specifies the number of new access users that the MSC server canaccommodate. For example, if the initial capacity of the MSC server is 2000000, theavailable user capacity is 1500000 on condition that 500000 users are currently on line.

B

backup flag It specifies whether the CN node is centralized backup MSC. The information of all theregistered mobile phones in the pool is backed up to the centralized backup MSC.

bandwidth A range of transmission frequencies that a transmission line or channel can carry in anetwork. In fact, it is the difference between the highest and lowest frequencies thetransmission line or channel. The greater the bandwidth, the faster the data transfer rate.

base station A fixed radio transmitter/receiver that relays signals from and to the mobile terminals orhandsets electronically within a specified range. It accommodates the devices that arenecessary to set up and complete calls on handsets, such as the antenna and computer.

base station controller Base Station Controller. A logical entity that connects the BTS with the MSC in a GSMnetwork. It interworks with the BTS through the Abis interface, the MSC through the Ainterface. It provides the following functions: Radio resource management Base stationmanagement Power control Handover control Traffic measurement One BSC controlsand manages one or more BTSs in an actual networking.

base station subsystem A physical device that gives radio coverage to a specific geographical zone called a cell.It consists of the BTS and BSC.



B-3

base station subsystemapplication part

The protocol employed across the A interface in the GSM system. It is used to transportMM (Mobility Management) and CM (Connection Management) information to andfrom the MSC (Mobile Switching Centre). The BSS Application Part (BSSAP) is splitinto two sub application parts, these are: the BSS Management Application Part(BSSMAP) and the Direct Transfer Application Part (DTAP).

base station subsystemmanagementapplication part

This protocol is also used to convey general BSS (Base Station System) controlinformation between the MSC (Mobile Switching Centre) and the BSS. An example isthe allocation of traffic channels between the MSC and the BSS.

BFD See bidirectional forwarding detection

bidirectionalforwarding detection

A simple hello mechanism to detect failures in a network and work with the routingprotocols to expedite failure detection.

bit The smallest unit of information that can be used by a computer. It is a binary digit thatcan be 0 or 1.

BITS See building integrated timing supply system

bits per second A rate at which the individual bits are transmitted through a communication link orcircuit. Its unit can be bit/s, kbit/s, and Mbit/s.

BPS See bits per second

broadband A term that indicates the capacity with enough bandwidth to transmit voice, data andvideo signals. It supports transmission of large amount of information.

broadcast An operation of sending electromagnetic signals to many receivers through the air or thepublic service network so that the information or programs can be transmitted at the sametime. It also refers to the telecommunication mode that information sent by a terminalcan be received by multiple receiving terminals in the computer network at the sametime.

BSC See base station controller

BSS See base station subsystem

BSSAP See base station subsystem application part

BSSMAP See base station subsystem management application part

BTS See base station

building integratedtiming supply system

In the situation of multiple synchronous nodes or communication devices, one can usea device to set up a clock system on the hinge of telecom network to connect thesynchronous network as a whole, and provide satisfactory synchronous base signals tothe building integrated device.

burst A process of forming data into a block of the proper size, uninterruptedly sending theblock in a fast operation, waiting for a long time, and preparing for the next fast sending.

busy tone A tone indicating that the called party is busy.

byte A unit of computer information equal to eight bits.

C

call loss A process during which a call cannot be set up or released owing to an error or failure.

CAS See channel associated signaling


Configuration Guide


Issue 02 (2008-05-07)

CAS multiframe A multiframe set up based on timeslot 16. Each CAS multiframe contains 16 E1 PCMframes. Among the eight bits of timeslot 16 in the first of the 16 frames, the first fourbits are used for multiframe synchronization. The multiframe alignment signal (MFAS)for synchronization is 0000. The last four bits are used as the not multiframe alignmentsignal (NMFAS). The NMFAS is XYXX. For the other 15 frames, timeslot 16 is usedto transmit the exchange and multiplexing (E&M) signaling corresponding to eachtimeslot.

CBR See constant bit rate

CCS See common channel signaling

CDMA See code division multiple access

CDMA2000 A 3G technology developed by Qualcomm of the US. Technology competitive withWCDMA, upgraded form CDMA1, and developed by the GSM community as aworldwide standard for 3G mobile.

cell A geographic area in a cellular mobile telephone system where a cell site controls allcellular transmission.

centralized backupMSC server

An MSC server in the MSC pool. This MSC server backs up the user data of each MSCserver/VLR in the MSC pool. In addition, the MSC server backs up the call services forsingle MSC servers in the MSC pool when they are faulty and restores the call servicesfor the faulty MSC servers after they are recovered. Different from other MSC servers,no NRI is available for the centralized backup MSC server, and the uplink SCCP CRmessages are not distributed to the centralized backup MSC server.

centralized forwarding Forwarding of OMC packets, H.248 packets and SIGTRAN packets through one IPinterface. It can save IP address resources and avoid the complexed networking.

challenge handshakeauthentication protocol

A method of authentication that you can use when connecting to an ISP that allows youto log on automatically.

channel A telecommunication path of a specific capacity and/or at a specific speed between twoor more locations in a network. The channel can be established through wire, radio(microwave), fiber or a combination of the three.

channel A channel refers to the CDR processing mode and storage directories that match a sortingcondition. A channel corresponds to a CDR storage path.

channel associatedsignaling

Channel Associated Signaling. A signaling system in which the signaling information istransmitted within the voice channel. China Signaling System No. 1 is a kind of CASsignaling.

CHAP See challenge handshake authentication protocol

circuit pool A group of trunk circuits that are identical in bearer capability.

CNG See comfort noise generation

code division multipleaccess

CDMA is a form of wireless multiplexing, in which data can be sent over multiplefrequencies simultaneously, optimizing the use of available bandwidth. In a CDMAsystem, data is broken into packets, each of which are given a unique identifier, so thatthey can be sent out over multiple frequencies and then re-built in the correct order bythe receiver.

comfort noisegeneration

The CNG is the algorithm that is used to generate comfort noise. The CNG expands thelower rate noise modeling data into a standard frame of G.729 data by filling in some ofthe less significant parameters. It then performs G.729 synthesis to generate the comfortnoise.



B-5

common channelsignaling

Common Channel Signaling. A signaling system used in telephone networks thatseparates signaling information from user data. A specified channel is exclusivelydesignated to carry signaling information for all other channels in the system. ChinaSignaling System No. 7 is a kind of CCS signaling.

congestion An extra intra-network or inter-network traffic resulting in decreasing network serviceefficiency.

constant bit rate An ATM service category supporting applications like voice and video that require aconstant bit rate.

CRC-4 multiframe A multiframe is recommended by ITU-T G.704 and set up based on the first bit of timeslot0. The CRC-4 multiframe is totally different from the CAS multiframe in principle andimplementation. Each CRC-4 multiframe contains 16 PCM frames. Each CRC-4multiframe consists of two CRC-4 sub-multiframes. Each CRC-4 sub-multiframe is aCRC-4 check block that contains 256 x 8 = 2048 bits. Bits C1 to C4 of a check blockcan check the previous check block.

D

differentiated servicescode point

Values for a 6-bit field defined for the IPv4 and IPv6 packet headers that enhance classof service (CoS) distinctions in routers.

digital network A telecommunication network where information is first converted into distinctelectronic pulses and then transmitted to a digital bit stream.

DNS See domain name service/server

domain name service/server

An Internet protocol to relate the service names or URLs to an IP address and conversely.

double wrapping A coding mode. In binary codec, parameters of the OCTET STRING type are coded withthe standard BER grammar, and then H.248 binary coding is performed. It is stipulatedin the H.248V2 protocol. For details, refer to the H.248V2 protocol.

DSCP See differentiated services code point

DTMF See dual tone multi-frequency

dual homing A solution in which signaling transfer points are configured in pairs, that is, eachsignaling point connects two signaling transfer points. Dual homing solutions can be 1+1 master/slave backup, 1+1 mutual aid, N+1 backup, and N+1 mutual aid. The dualhoming solution is a network security solution put forward by Huawei first. This solutionis used to ensure the security of MSC servers. Nowadays, the dual homing solution isapplied in multiple commercial networks.

dual tone multi-frequency

It is an analogue inband access signalling system.

DW See double wrapping

E

E-LABEL See electronic label

E1 A European standard for high-speed data transmission at 2.048 Mbit/s. It provides 32 x64 kbit/s channels.

EC See echo cancellation


Configuration Guide


Issue 02 (2008-05-07)

echo In the traditional PSTN network, an echo is caused by the 2/4 wire conversion. In acommon session, the end-to-end delay is small, an echo can be rapidly transmitted to theears of speakers, and thus it is not easily felt. In long-distance calls or international long-distance calls, however, the end-to-end delay is big, and the echo canceller must be usedto control echoes.

echo cancellation Echo cancellation indicates to configure an echo canceller (usually called EC) in thecommunication network with the echo problem to reduce or eliminate echoes.

EFR See enhanced full rate

electronic label The label that stores the codes for identifying objects in the format of electronic data.Withthe feature of large capacity, high confidentiality, read-write capability and working inhad condition, it is much better than other electronic label.

element managementsystem

An element management system (EMS) manages one or more of a specific type ofnetwork elements (NEs). An EMS allows the user to manage all the features of each NEindividually, but not the communication between NEs - this is done by the networkmanagement system (NMS).

EMS See element management system

encapsulating securitypayload

Encapsulating Security Payload is used in the transmission mode and tunnel mode. Itadopts the encryption and authentication mechanism and provides the services such asdata source authentication, data completeness, anti-replay, and secret security.

encapsulation A procedure of packetizing a protocol data unit in a group of protocol header and tail.

encryption A method used to guarantee the security and authenticity of data in end-to-endtransmission. Encryption can be implemented through technologies such as data pseudo-random alteration and data substitution.

end system A network entity that sends and receives packets in IS-IS.

enhanced full rate A technology that improves the quality of calls made on a digital mobile network. It isachieved through more efficient use of bandwidth.

error correction Technique for restoring integrity in data that is corrupted during transmission. It requiresadditional information to be sent with the original data and allows the data to bereconstructed from this information if the original data is corrupted.

ESP See encapsulating security payload

ethernet A local technology based on CSMA/CD, The speed of Ethernet can be 10 Mbit/s, 100Mbit/s, 1000 Mbit/ s or 10000 Mbit/s. It is easily maintained and of high reliability.

extend superframe The multiframe format of T1. Each multiframe comprises of 24 single frames.

F

file transfer protocol FTP is commonly used application. It is the Internet standard for file transfer. The filetransfer provided by FTP copies a complete file from one system to another system. Touse FTP we need an account to login to on the server, or we need to use it with a serverthat allows anonymous FTP (which we show an example of in this chapter).

firewall A security gateway that is positioned between two different networks, usually betweena trusted network and the Internet.

flow Data amount through a piece of equipment within a unit of time.



B-7

flow control A method used to control the data packets that traverse a device so that the device is notto be overloaded because of heavy traffic.

FR AMR codecalgorithm

A full rate AMR codec algorithm that can be used only in GSM networks. The bit ratecan be 4.75 kbit/s, 5.15 kbit/s, 5.90 kbit/s, 6.70 kbit/s, 7.40 kbit/s, 7.95 kbit/s, 10.2 kbit/s, or 12.2 kbit/s. The AMR algorithm is an adaptive rate-based codec algorithm, whichadopts the algebraic code excitation linear prediction (ACELP) mechanism.

frame Logical grouping of information sent as a data link layer unit over a transmissionmedium. Often refers to the header and the trailer, used for synchronization and errorcontrol, that surround the user data contained in the unit. The terms cell, datagram,message, packet, and segment also are used to describe logical information groupings atvarious layers of the OSI reference model and in various technology circles.

frequency The number of completing tasks per unit of time with Hz as its unit. 1 Hz = 1 cycle persecond.

frequency shift keying FSK is used in low speed modems to modulate data that uses two frequencies, one ofwhich is used to represent a binary one and the other a binary zero. In full-duplextransmission, two different frequencies are used in each direction, which leads to fourdifferent frequencies being used.

FSK See frequency shift keying

FTP See file transfer protocol

full duplex It is a mode to transmit signals along a bearer channel or carrier in both directions at thesame time.

full rate A rate for transmitting data services. The service bandwidth can be 9.6 kbit/s, 4.8 kbit/s, or 2.4 kbit/s.

G

gateway A device that implements protocol conversion between different devices or networks.

gateway GPRS supportnode

It is short for gateway GPRS support node. In the IMS, a UE can find the entry point ofthe IMS through the GPRS process. That is, it can obtain the IP address of the P-CSCFthrough the GGSN.

gCause An event type stipulated in the H.248 protocol.

global system formobilecommunications

Abbreviated GSM. The second-generation mobile networking standard defined by ETSI.

GSM See global system for mobile communications

GSM EFR codecalgorithm

The GSM enhanced full rate (EFR) algorithm, a compressed mixed codec algorithmbased on the GSM network. It adopts the code excited linear prediction (CELP)technology, and the compressed bit rate is 12.2 kbit/s. Fully considering the spectrumtransition characteristic of the voice, this codec mode improves the codec algorithm ofthe voice source to make the voice quality clear and sufficient, thus improving the voicequality greatly. When the bandwidth used in the EFR algorithm is the same as that in theFR algorithm, the EFR algorithm can improve the call quality under the condition ofweak signals through a more advanced algorithm. This codec mode is used in GSMnetworks.


Configuration Guide


Issue 02 (2008-05-07)

GSM FR codecalgorithm

The GSM full rate (FR) algorithm, a compressed mixed codec algorithm. It adopts theregular-pulse excitation-long term prediction (RPE-LTP) codec technology, and thecompressed bit rate is 13 kbit/s. The outstanding characteristic of this codec mode is itsstability, namely, it has relative stable voice quality under different mobile noisebackgrounds and unstable wireless transmission condition (different error modes). Thiscodec mode is used in GSM networks.

H

half rate A variant of GSM, Half-Rate doubles system capacity by more efficient speech coding.The conversion of the voice to digital packets can be done 3 ways, using Half Rate coding(HR), Full Rate coding (FR) or Enhanced Full Rate coding.

HR See half rate

HR AMR codecalgorithm

A half rate AMR codec algorithm that can be used only in GSM networks. The bit ratecan be 4.75 kbit/s, 5.15 kbit/s, 5.90 kbit/s, 6.70 kbit/s, 7.40 kbit/s, or 7.95 kbit/s. TheAMR algorithm is an adaptive rate-based codec algorithm, which adopts the algebraiccode excitation linear prediction (ACELP) mechanism.

HR codec algorithm A half rate GSM voice encoding algorithm.

I

ICMP See internet control message protocol

IETF See internet engineering task force

IKE See internet key exchange

integrated servicesdigital network

Integrated Services Digital Network (ISDN) is comprised of digital telephony and data-transport services offered by regional telephone carriers. ISDN involves the digitizationof the telephone network, which permits voice, data, text, graphics, music, video, andother source material to be transmitted over existing telephone wires.

intermediate system-to-intermediate system

Intermediate System-to-Intermediate System. OSI link-state hierarchical routingprotocol based on DECnet Phase V routing whereby ISs (routers) exchange routinginformation based on a single metric to determine network topology.

international standardsorganization

A United Nations agency, based in Geneva, Switzerland, responsible for worldwidestandards, including many networking standards. The OSI reference model, publishedas ISO standard 7498, was jointly developed by the ISO and the ITU.

internationaltelecommunicationunion

A United Nations agency, one of the most important and influential recommendationbodies, responsible for recommending standards for telecommunication (ITU-T) andradio networks (ITU-R).

internet A global network that uses IP to link various physical networks into a single network.

internet controlmessage protocol

An extension to the Internet Protocol. It allows for the generation of error messages, testpackets and informational messages related to IP.

internet engineeringtask force

An international community of network designers, operators, vendors, and researchers.IETF focuses on the evolution of the Internet architecture and the smooth operation ofthe Internet.



B-9

internet key exchange An optional function of the IPSec that provides ways for encryption. It is used to providethe function of sharing the internet key through negotiating whether the AH Header andthe ESP Header of the IPSec packet are consistent.

internet protocol A protocol that enables data to be sent from one point to another on the Internet.

internet securityassociation and keymanagement protocol

A protocol that allows the message receiver to get a public key and use digital certificatesto authenticate the sender's identity.

IP See internet protocol

IP address An exclusive address on the Internet for each interface, which is 32 bits long. An IPaddress indicates a connection to a network, not a host.

IP security protocol A general designation of a set of open protocols. With the IPSec, the encryption and datasource verification between specific communication parties can ensure theconfidentiality, intactness, and authenticity of data packets when they are transmittedover the Internet.

IPSec See IP security protocol

IS-IS See intermediate system-to-intermediate system

ISAKMP See internet security association and key management protocol

ISDN See integrated services digital network

ISO See international standards organization

ITU See international telecommunication union

J

jitter The variation in the time taken for packets to be delivered to an endpoint or networkentity.

L

LAN See local area network

LAPV5 signaling link A layer-2 link on the V5 interface. The V5 interface is the interface between the accessnetwork and switches, and it is a service node interface (SNI).

link It is the physical or logical connection for two pieces of equipment to communicate witheach other.

local area network A network intended to serve a small geographic area, (few square kilometers or less), asingle office or building, or a small defined group of users. It features high speed andlittle errors. Ethernet, FDDI and Toke Ring are three technologies implemented in LAN.

M

M3UA destinationentity

An M3UA logical entity that equals the MTP3 destination signaling point.

MAC See media access control


Configuration Guide


Issue 02 (2008-05-07)

maximum transmissionunit

The MTU (Maximum Transmission Unit) is the size of the largest datagram that can besent over a network.

MD5 See message digest 5

media access control Media Access Control is the lower of the two sublayers of the Data Link Layer. In generalterms, MAC handles access to a shared medium, and can be found within many differenttechnologies. For example, MAC methodologies are employed within Ethernet , GPRS ,and UMTS etc.

media gateway Media Gateway. A logical entity that converts the format of the media of a network tomeet the format requirement of another network. It can process audio services, videoservices and data services, and convert the media format in full duplex mode. In addition,it can play certain audio and video signals, and provide the IVR function and mediaconference.

media gatewaycontroller

The Media Gateway Controller (MGC), also known as Call Agents or Soft Switches,handles registration, management, and control functionality of resources in the MediaGateway (MG).

message digest 5 One-way hashing algorithm that generates a 128-bit hash for producing messageauthentication signatures.

message transfer part A part of the Signaling System 7 (SS7) used for communication in Public SwitchedTelephone Networks. MTP Level 3 provides routing functionality to transport signalingmessages through the SS7 network to the requested endpoint.

message transfer partlevel 3(broadband)

Message Transfer Part level 3 broadband provides message routing, discrimination anddistribution (for point to point link only). It also provides signalling link management,load sharing and changeover between links within one link-set. The protocol is abroadband ISDN based protocol used typically in ATM (Asynchronous Transfer Mode).

message type A descriptor that identify the function of a message. Stimulus call control has onemessage type, that is, information, while, the functional call control has several messagetypes concerning call connection, call disconnection, and call status.

MGC See media gateway controller

MGW See media gateway

MIN See mobile identification number

mobile identificationnumber

A number that identifies a mobile unit in wireless carrier's networks, and dials from othernetworks or fixed lines. In addition, it can be electronically checked to help prevent fraud.

mobile station A mobile device, such as cellular phones or mobile personal digital assistants (PDAs).

mobile switching center Mobile Switching Center. A logical entity that provides interfaces for interworking withthe function entities in a GSM/WCDMA system and the public network. It plays a corerole for switch in the GSM/WCDMA system. It provides mobile management and switchto mobile subscribers and sets up communications between mobile subscribers, orbetween a mobile subscriber and a fixed line subscriber.

modem A device that enables data to be exchanged by interpreting and converting both analoguesignals and digital signals.

MPLS See multiprotocol label switching

MS See mobile station

MSC See mobile switching center



B-11

MSC pool A pool formed by multiple MSC servers that serve a pool area. A device in the accessnetwork interconnects with multiple MSC servers in the pool.

MTP See message transfer part

MTP3b See message transfer part level 3(broadband)

MTU See maximum transmission unit

multiplexer An equipment which combines a number of tributary channels onto a fewer number ofaggregate bearer channels, the relationship between the tributary and aggregate channelsbeing fixed.

multiprotocol labelswitching

A technology that uses short tags of fixed length to encapsulate packets in different linklayers, and provides connection-oriented switching for the network layer on the basis ofIP routing and control protocols. It improves the cost performance and expandability ofnetworks, and is beneficial to routing.

MUX See multiplexer

N

narrowband A term used to depict the communication services that transmit over TDM timeslot. ThePSTN is normally a narrowband network. A communication channel whose transmissionrate is lower than 2 Mbit/s is usually considered to be narrowband.

network In communications, a system of interconnected communication facilities.

network service accesspoint

A connection to a network that is identified by a network address.

network time protocol The Network Time Protocol was developed to maintain a common sense of "time" amongInternet hosts around the world. Many systems on the Internet run NTP, and have thesame time (relative to Greenwich Mean Time), with a maximum difference of about onesecond.

non APS 1+1 Indicates that the protective group uses the master/slave interfaces mode. The APSprotective mode is not supported.One protection group has two interfaces, one masterand the other slave. Services are switched based on the UP/DOWN status of theinterfaces. In the normal state, the master interface is working. If the master interfacebecomes DOWN, services on it are switched to the slave interface. This mode can beautomatically supported by hardware for some interfaces, and is not required to beconfigured.

non APS 1:N Indicates that the protective group uses one protective channel and N pieces of workingchannels. The APS protective mode is not supported.One protection group has N+1interfaces, and services are switched based on the UP/DOWN status of the interface. Inthe normal state, N interfaces are working. When one interface becomes DOWN, serviceson it are switched to the slave interface.

NSAP See network service access point

NTP See network time protocol

number of ATMendpoints

The point in an ATM network where an ATM connection is initiated or terminated. ATMendpoints include ATM-attached workstations, ATM-attached servers, ATM-to-LANswitches, and ATM routers. ATM

number of IPterminations

The number of concurrently available IP terminations on a gateway.


Configuration Guide


Issue 02 (2008-05-07)

P

packet Data packets and local packets. Logical grouping of information that includes a headercontaining control information and (usually) user data. Packets are most often used torefer to network layer units of data.

packet forwarding When a router receives a datagram, it is found that the destination IP address of thedatagram do not match the IP address of the router, then the router queries the route listand forwards the datagram to another router or the destination host.

packet losscompensation

A technology of compensating packets according to an appropriate algorithm if packetsare lost in the transmission.

packet over SDH Packets transmitted over SDH.

PAP See password authentication protocol

parity A method for character level error detection. An extra bit added to a string of bits, usuallya 7-bit ASCII character, so that the total number of bits 1 is odd or even (odd or evenparity). Both ends of a data transmission must use the same parity. When the transmittingdevice frames a character, it counts the numbers of 1s in the frame and attaches theappropriate parity bit. The recipient counts the 1s and, if there is parity error, may askfor the data to be retransmitted.

passwordauthentication protocol

A method for verifying the identity of a user attempting to log on to a Point-to-PointProtocol (PPP) server. PAP is used if a more rigorous method, such as the ChallengeHandshake Authentication Protocol (CHAP), is not available or if the user name andpassword that the user submitted to PAP must be sent to another program withoutencryption.

PBX See private branch exchange

PCM See pulse code modulation

PCR See peak cell rate

PDH See plesiochronous digital hierarchy

peak A time period when calls are the busiest in terms of service traffic.

peak cell rate The maximum rate at which an ATM connection can accept cells.

pending transaction A transaction type stipulated in the H.248 protocol. For details, refer to the H.248protocol. When a transaction lasts for a long time and the gateway processes thetransaction, the gateway sends a Pending transaction to the MGC to inform the MGC ofthe processing to avoid retransmission.

performancemanagement

One of five categories of network management defined by ISO to manage the OSInetworks. Performance management subsystems are in charging of analyzing andcontrolling network performance, including network throughput and error rates.

ping A method of testing whether a device in the IP network is reachable according to sentICMP Echo messages and received the response messages.

PLC See packet loss compensation



B-13

plesiochronous digitalhierarchy

A technology used in telecommunications networks to transport large quantities of dataover digital transport equipment such as fibre optic and microwave radiosystems.Plesiochronous Digital Hierarchy is the first multiplexing hierarchy used indigital transmission systems. The base frequency was 64Kbit/s, multiplexed up to 2048,8448, 34,368 and 139,264Mbit/s. There was more than one standard system and it variedbetween Europe, the US and Japan.

PM See performance management

point-to-point protocol Point-to-Point Protocol. A widely used WAN protocol designed to provide router torouter and host to network connections over synchronous and asynchronous circuits. Inaddition, PPP has a built-in security mechanism.

pool A concept raised in 3GPP TS 23.236. It means that multiple serving CN nodes in thenetwork form a pool area. Within this area, an MS can roam at will without changingthe serving CN node.

port A physical or logical communication interface.

POS See packet over SDH

PPP See point-to-point protocol

private branchexchange

A telephone switch for use inside a corporation.

profile negotiation A parameter for interconnection between the MGW and the peer MGC. Each profile canbe considered as a subset of the H.248 standard. ETSI_GateControl/1 defines theServiceChange message in a more detailed manner. For details, refer to ETSI TS 102333 V1.1.2. ETSI_Tgw/1 defines partial subsystems in the NGN. For details, refer toETSI ES 283 024 V1.1.1. FT_Tgw/1 defines and expands partial subsystems in the NGN.For details, refer to ETSI ES 283 024 V<1.0.14>.

protocol On the Internet "protocol" usually refers to a set of rules that define an exact format forcommunication between systems.

PSTN See public switched telephone network

public switchedtelephone network

Network by which household and business phones are connected, typically byconventional fixed cables. It is the infrastructure providing a country's telephone systemand it is the original analog telephone network.

pulse A variation above or below a normal level and a given duration in electrical energy.

pulse code modulation A method of converting an analog voice signal to digital. It samples the signal 8,000times per second and encodes the signal amplitude as an 8 bit value. The produced digitaltransmission rate is 64 kbit/s.

Q

Q.921 signaling link An ISDN data link. The corresponding protocol is ITU-T Q.921.

QoS See quality of service

quality of service Short for Quality of Service, QoS refers to service capacity assessment of IP networkpackets. Typically, the capability of supporting service requirements such as delay, delayjitter, and packet loss is considered as the core assessment object. Certain supporttechnologies are required to meet the core requirements.


Configuration Guide


Issue 02 (2008-05-07)

R

radio networkcontroller

An entity that manages the radio part of the network in UMTS.

real time Pertaining to the processing of data by a computer in connection with another processoutside the computer according to time requirements imposed by the outside process.

real time variable bitrate

A rate that is intended for real-time applications. The rt-VBR services are connection-oriented with variable bit rates. The bandwidth used by a termination varies with theinformation sending rate of the termination. The ATM network guarantees thesustainable cell rate (SCR) for communication terminations, and requires that theterminations adopt rates equal to or lower than the peck cell rate (PCR) to sendinformation. rt-VBR is typically used in the services that require much on time sensitivitysuch as image services.

real-time controlprotocol

The statuses of sessions in the connection are contained in the packets to guarantee QoSof RTP.

real-Time transportprotocol

A host-to-host protocol that is used in real-time multimedia services such as Voice overIP (VoIP) and video.

RNC See radio network controller

route A route is a set of all sub-routes from local office to a destination office. A route containsmultiple sub-routes and different routes may contain the same sub-routes.

router It is a piece of equipment that can forward the data, which should not be routed to it. Inother words, a router can receive packets and forwards them to the right destination,because a router connects to more than one physical network.

rt-VBR See real time variable bit rate

RTCP See real-time control protocol

RTP See real-Time transport protocol

S

SCCP See signaling connection control part

SCTP association An association is the logic relationship, or channel, established between two SCTPendpoints for data transmission, through the four-way handshake mechanism prescribedin SCTP.

SCTP dual-homingnetworking mode

A networking of 3GPP R4 or later in which one MGW belongs to two MSC Servers.

SDH See synchronous digital hierarchy

security domain A set of elements, a security policy, a security authority and a set of security relevantactivities in which the set of elements are subject to the security policy, administered bythe security authority, for the specified activities. The Security Domain focuses on theidentification of industry standards related to cybersecurity and the creation of policiesto promote a more secure environment.

security parameterindex

A numeric identifier in IPsec, used with the destination address and security protocol toidentify a security association (SA).



B-15

segmentation A term used to set limits to collision domains, which allows Ethernet networks to achievehigher performance. It is also called network segmentation.

server A network device that provides services to network users by managing shared resources,often used in the context of a client-server architecture for a LAN.

serving GPRS supportnode

A device in the mobile network that requests PDP contexts with a GGSN.

session initiationprotocol

An application layer protocol used for creating, modifying, and terminating a multimediasession in IP networks. It is part of the multimedia protocol system that IETF standardizesconstantly. The SIP protocol is used to initiate the interactive user sessions containingthe multimedia elements of video, voice, chatting, game, and virtual reality.

SGSN See serving GPRS support node

signaling The instructions and the signals that are transmitted among different levels of exchangesto enable the network to run normally as an entire entity and thus implement callconnections. The instructions control connections, and the signals indicate the executionresults and running status.

signaling connectioncontrol part

Signaling Connection Control Part. A protocol used by the MSOFTX3000 to establishcircuit-independent signaling connections with the VLR, HLR, EIR, MSC, SMC,GMLC, and SCP through the SS7 signaling network.

signaling point Signaling Point. A node that sends or receives signaling messages in a signaling network.

signaling system 7 A protocol used in telecommunication for delivering calls and services.SS7 typicallyemploys a dedicated 64 kilobit data circuit to carry packetized machine languagemessages about each call connected between and among machines of a network toachieve connection control.

signaling transfer point Signaling Transfer Point. A node that transfers messages received from a signaling linkto another. Element of an SS7-based Intelligent Network that performs routing of theSS7 signaling.

SIP See session initiation protocol

softswitch A term that refers to a softswitch device in a narrow sense. A softswitch provides callcontrol and connection control for real-time services. As the control core of the NGN,softswitches separate the services from the call control and the call control from thebearer, and adopt the application program interface (API) and standard protocols. Thismakes it easy for network carriers to develop new services and realize new features.

SONET See synchronous optical network

SP See signaling point

SPI See security parameter index

SS7 See signaling system 7

standard SGnetworking

A networking mode relative to the MSC Pool networking. In standard SG networkingmode, the UMG8900 serves only as an SG in signaling processing. The signalingmessages are processed only to the MTP3 layer. The UMG8900 does not resolve theMTP3 user contents; instead, the UMG8900 forwards them according to the destinationpoint codes in the messages.


Configuration Guide


Issue 02 (2008-05-07)

static route A route that cannot adapt to the change of network topology. Operators must configureit manually. When a network topology is simple, the network can work in normal stateif only the static route is configured. It can improve network performance and ensurebandwidth for important applications. Its disadvantage is: When a network is faulty orthe topology changes, the static route does not change automatically. It must be changedby operators.

STM See synchronous transport module

STP See signaling transfer point

stream index An index that is used to uniquely identify a media stream. It is stipulated in the H.248protocol. For details, refer to the H.248 protocol.

stream mode A mode that identifies the direction of the media stream on a termination. It is stipulatedin the H.248 protocol. For details, refer to the H.248 protocol.

subboard A type of board used in the separated architecture for the UMG8900. The board with theseparated architecture consists of the baseboard and the subboard that work jointly toimplement certain functions. Take the SPF as an example. The SPF subboard mainlyprocesses layer-2 narrowband signaling such as signaling on the MTP2 links, Q.921links, and LAPV5 links. The SPF baseboard typically processes layer-3 signaling.

subnet mask The technique used by the IP protocol to determine which network segment packets aredestined for. The subnet mask is a binary pattern that is stored in the client machine,server or router and is matched with the IP address.

SX See softswitch

synchronous digitalhierarchy

The European counterpart to SONET. SONET is an intelligent system that providesadvanced network management and a standard optical interface. Specified in theBroadband ISDN (B-ISDN) standard, SONET backbones are widely used to aggregateT1 and T3 lines. The European counterpart to SONET is the Synchronous DigitalHierarchy, and the term "SONET/SDH" is widely used when referring to SONET.

synchronous opticalnetwork

A North American standard for Synchronous Data Transfer over Optical Networks.

synchronous transportmodule

An information structure supporting section layer connections.

T

T1 A basic physical layer protocol that is used by the digital signal level 1 (DS1)multiplexing method in North America.

TCP See transmission control protocol

temporary mobilesubscriber identity

A temporary mobile station identification assigned by the MSC. The TMSI is stored inthe VLR and the SIM card and used by the MS to originate and receive calls. One TMSImaps to only one IMSI in a VLR area. The TMSI is used to conceal the internationalmobile subscriber identity (IMSI) for sake of security.

time to live A period of time starting when resources such as sessions and terminations are allocatedand ended when the resources are released.

TMSI See temporary mobile subscriber identity

topology The topology of a network describes the way computers are connected together.Topology is a major design consideration for cost and reliability.



B-17

ToS See type of service

traffic The average number of calls made and received by call sources in a seizure duration.

transit Connection to and use of a telecommunication path that is provided by a vendor.

transmission controlprotocol

A connection oriented packet switching protocol that provides reliable data transmissionservice for applications on the Internet.

transmit mode The mode employed for transmission.

transparenttransmission

Transmission of signals over the network without any change of structures and data. Forsignals, the network is transparent.

tunnel One of the NAT traversal solutions. Configure the tunnel client in the private networkand the tunnel server on the proxy device. The client transmits packets to the serverthrough the UDP tunnel or HTTP tunnel.

tunnel mode An IPSec mode of operation in which the entire IP packet, including the header, isencrypted and authenticated and a new VPN header is added, which protects the entireoriginal packet.

type of service A field in an IP packet (IP datagram) that is used for quality of service (QoS). The TOSfield is 8 bits, broken into five subfields.

U

UBR See unspecified bit rate

UDP See user datagram protocol

UMTS See universal mobile telecommunication system

UMTS terrestrial radioaccess network

A WCDMA radio network in UMTS.

universal mobiletelecommunicationsystem

A system that is applied in the third-generation (3G) wireless networks. It transmits text,digitized voice and multimedia based on packet. The transmission rate of data can be upto 2 Mbit/s.

unspecified bit rate A transmission service that does not guarantee a fixed transmission capacity. Anyapplication that can tolerate delays is ideally satisfied by an UBR.

user datagram protocol A connectionless transport layer protocol, in TCP/IP, that exchanges datagram withoutacknowledgments or guaranteed delivery.

UTRAN See UMTS terrestrial radio access network

V

VAD See voice activity detection

variable bit rate QoS class defined by the ATM Forum for ATM networks. VBR is subdivided into a realtime (RT) class and non-real time (NRT) class. VBR (RT) is used for connections inwhich there is a fixed timing relationship between samples.

VBR See variable bit rate

VCI See virtual circuit identifier


Configuration Guide


Issue 02 (2008-05-07)

video gateway When the MGW serves as a VIG, audio, video and H.245 (multimedia communicationcontrol protocol) data is multiplexed in H.223 frames. The MGW needs to demultiplexH.223 frames and then transmits H.223 control protocol data transparently to the MGC.Thus, H.245 signaling links need to be set up between the MGW and the MGC. Thisconfiguration is unnecessary in other networking applications.

VIG See video gateway

virtual channel A term that enables queuing, packet scheduling, and accounting rules to be applied toone or more logical interfaces.

virtual circuit identifier A 16-bit field in the header of an ATM cell. The VCI, together with the VPI, identifiesthe next destination of a cell as it passes through a series of ATM switches on its way toits destination.

virtual local areanetwork

A LAN is divided into several logical LANs to suppress broadcast packets. Each virtualLAN is a broadcast area. Hosts in the same VLAN can directly communicate but hostsin different VLANs cannot. Thus, broadcast packets are restricted in a VLAN.

virtual path identifier 8-bit field in the header of an ATM cell. The VPI, together with the VCI, identifies thenext destination of a cell as it passes through a series of ATM switches on its way to itsdestination.

VLAN See virtual local area network

voice activity detection Voice activity detection or voice activity detector is an algorithm used in speechprocessing wherein, the presence or absence of human speech is detected from the audiosamples. The main uses of VAD are in speech coding and speech recognition. A VADmay not just indicate the presence or absence of speech, but also whether the speech isvoiced or unvoiced, sustained or early, etc.

VPI See virtual path identifier

W

W-CDMA See wideband code division multiple access

WB-AMR See wide band AMR

wide band AMR Full rate of broadband AMR codec algorithm, which is also called G.722.2 algorithm.Generally, it refers to a codec type.

wideband code divisionmultiple access

A radio interface technology used in most of the third-generation (3G) wireless systems.It is the third generation standard developed and supported by GSM proponents.



B-19

Index

Ccascading

mixed cascading(UG01NET and BLU.AConfigured), 3-20, 3-26mixed cascading(UG02NET and BLU.CConfigured), 3-26SSM-256 self-cascading, 3-17SSM-32 self-cascading, 3-19

cautions for data configuration, 1-5centralized forwarding, 3-35configuration index

access gateway(AG), 2-4NGN-enabled switch, 2-6trunk gateway(TG), 2-3video interworking gateway(VIG), 2-5

configuring ATM physical layerSDH interface protection, 12-8

configuring control interfaceIP over E1, 10-20mixed cascading, 10-17single-frame, 10-2SSM-256 self-cascading, 10-10SSM-32 self-cascading, 10-13

configuring gateway address, 13-18configuring hardware, 8-1configuring IP interface

FE interface, 13-2GE interface, 13-4IP over E1, 13-9

configuring IP interface address, 13-13configuring IP interface protection, 13-14configuring MGW control data

activate VMGW, 11-15H.245 link, 11-12H.248 link over SCTP, 11-8H.248 link over UDP, 11-5MGW data, 11-2

configuring NMSinterface, 7-2SNMP, 7-8

configuring office direction information, 12-15configuring QoS parameter, 17-9configuring service parameter, 17-6

configuring signaling transferbased on CAS, 14-32based on IUA, 14-15based on M2UA, 14-2based on M3UA, 14-21based on semi-permanent connection, 14-29based on V5UA, 14-8

configuring system parameter, 5-1configuring system time, 6-1configuring TDM interface

E1/T1, 12-2E3/T3, 12-3SDH interface, 12-5SDH interface protection, 12-8

configuring TDM timeslot, 12-11configuring the clock, 9-1configuring trunk group management, 12-13

Ddual homing, 3-40

Fframes and boards

board, 3-7numbering rules, 3-3SSM-256 frame, 3-2SSM-32 frame, 3-3

Ggeneral planning of examples, 4-1general procedures for data configuration, 2-2

Iinterface protection, 3-41

Mmethod for data configuration

using data script, 1-4using data scripts, 1-4

HUAWEI UMG8900 Universal Media GatewayConfiguration Guide Index


i-1

using equipment panel, 1-4using MML command, 1-2

Rroute backup, 3-51

Ssecurity control

configuration the firewall, 18-2configuring IPSec, 18-4configuring SSH, 18-8

Vvirtual media gateway(VMGW), 3-41

IndexHUAWEI UMG8900 Universal Media Gateway

Configuration Guide

i-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-05-07)

00385871 configuration guide (v100r007 02,ngn)

Documents

huawei trademarks

huawei proprietary

data configuration methods

huawei industrial basebantian

tg configuration index

ag configuration index

vig configuration index

ltdhuawei technologies