Configuration Guide (V100R007 02, NGN)

HUAWEI UMG8900 Universal Media Gateway V100R007
Configuration Guide
Issue Date Part Number
02 2008-05-07 00385871
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
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 written consent 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.
Notice
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
HUAWEI UMG8900 Universal Media Gateway Configuration Guide
Contents
Contents
About This Document.....................................................................................................................1 1 Introduction.................................................................................................................................1-1
1.1 Data Configuration Methods...........................................................................................................................1-2 1.1.1 MML Using Methods.............................................................................................................................1-2 1.1.2 Methods of Using Device Panel.............................................................................................................1-4 1.1.3 Methods of Using Data Scripts..............................................................................................................1-4 1.2 Cautions for Data Configuration.....................................................................................................................1-5
2 General Description of Data Configuration.........................................................................2-1

2.1 General Procedures for Data Configuration....................................................................................................2-2 2.2 Configuration Index........................................................................................................................................2-3 2.2.1 TG Configuration Index.........................................................................................................................2-3 2.2.2 AG Configuration Index.........................................................................................................................2-4 2.2.3 VIG Configuration Index.......................................................................................................................2-5 2.2.4 Configuration Index of NGN-Enabled Switch.......................................................................................2-6
3 Preliminary Knowledge............................................................................................................3-1
3.1 Frames and Boards..........................................................................................................................................3-2 3.1.1 Introduction to the SSM-256 Frame.......................................................................................................3-2 3.1.2 Introduction to the SSM-32 Frame.........................................................................................................3-3 3.1.3 Numbering Cabinets and Frames...........................................................................................................3-3 3.1.4 Introduction to Boards............................................................................................................................3-7 3.2 Frame Cascading...........................................................................................................................................3-17 3.2.1 SSM-256 Self-Cascading.....................................................................................................................3-17 3.2.2 SSM-32 Self-Cascading.......................................................................................................................3-18 3.2.3 SSM-256 and SSM-32 Mixed Cascading (UG01NET and BLU.A Configured)................................3-20 3.2.4 SSM-256 and SSM-32 Mixed Cascading (UG02NET and BLU.C Configured)................................3-26 3.3 Centralized Forwarding.................................................................................................................................3-35 3.4 Dual Homing.................................................................................................................................................3-40 3.5 SCTP Multi-Homing.....................................................................................................................................3-40 3.6 Virtual Media Gateway.................................................................................................................................3-41 3.7 Interface Protection.......................................................................................................................................3-41 3.8 UAM Background Information.....................................................................................................................3-44 3.8.1 UA Frame Types..................................................................................................................................3-45 Issue 02 (2008-05-07) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd i
Contents
HUAWEI UMG8900 Universal Media Gateway Configuration Guide 3.8.2 UA Frame Modes.................................................................................................................................3-47 3.8.3 Conversion Between the TID and the Subscriber Line Port................................................................3-48 3.8.4 Method to Number E1 Interfaces on the PV8/RSU by Mapping Them to E1 Cables on the SSM Side .......................................................................................................................................................................3-49 3.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-1
7.1 Configuring the NMS Interface.......................................................................................................................7-2 7.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-1
10.1 Configuring the Physical Interface in Single-Frame Networking Mode....................................................10-2 10.2 Configuring the Physical Interface in SSM-256 Self-Cascading Mode....................................................10-10 10.3 Configuring the Physical Interface in SSM-32 Self-Cascading Mode......................................................10-13 10.4 Configuring the Physical Interface in Mixed Cascading Mode................................................................10-17 10.5 Configuring the E1 Physical Interface Carrying IP Signaling Packets.....................................................10-20
11 Configuring MGW Control Data........................................................................................11-1

11.1 Configuring MGW data..............................................................................................................................11-2 11.2 Configuring the Link...................................................................................................................................11-5 11.2.1 Configuring the Link over UDP.........................................................................................................11-5 11.2.2 Configuring the H.248 Link over SCTP............................................................................................11-8 11.2.3 Configuring the H.245 Link.............................................................................................................11-12 11.3 Activating the VMGW..............................................................................................................................11-15
12 Configuring TDM Bearer.....................................................................................................12-1

12.1 Configuring the TDM Interface..................................................................................................................12-2 12.1.1 Configuring the E1/T1 Interface........................................................................................................12-2 12.1.2 Configuring the E3/T3 Interface........................................................................................................12-3 12.1.3 Configuring the SDH Interface on the S2L/S1L................................................................................12-5 12.1.4 Configuring SDH Interface Protection...............................................................................................12-8 12.2 Configuring the TDM Timeslot................................................................................................................12-11 12.3 Configuring Trunk Group Management...................................................................................................12-13 12.4 Configuring Office Direction Information................................................................................................12-15
13 Configuring IP Bearer...........................................................................................................13-1
13.1 Configuring IP Interface..............................................................................................................................13-2 13.1.1 Configuring the FE Interface..............................................................................................................13-2 ii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-05-07)
Contents
13.1.2 Configuring the GE Interface.............................................................................................................13-4 13.1.3 Configuring the ATM Interface.........................................................................................................13-6 13.1.4 Configuring the IP over E1 Interface.................................................................................................13-9 13.2 Configuring the IP Interface Address........................................................................................................13-13 13.3 Configuring IP Interface Protection..........................................................................................................13-14 13.4 Configuring the Gateway Address............................................................................................................13-18
14 Configuring Signaling Transfer..........................................................................................14-1

14.1 Configuring SIGTRAN over L2UA............................................................................................................14-2 14.1.1 Configuring SIGTRAN over MTP2-M2UA......................................................................................14-2 14.1.2 Configuring SIGTRAN over LAPV5-V5UA....................................................................................14-8 14.1.3 Configuring SIGTRAN over Q.921-IUA.........................................................................................14-15 14.2 Configuring SIGTRAN over M3UA (MTP3-M3UA)..............................................................................14-21 14.3 Configuring Semi-Permanent Connection................................................................................................14-29 14.4 Configuring CAS.......................................................................................................................................14-32
15 Configuring UAM Data........................................................................................................15-1

15.1 Configuring UA Frames and Boards...........................................................................................................15-4 15.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-9 15.2.2 Configuring the Connection Between the RSP Main Frame and the RSP Subframe......................15-20 15.2.3 Configuring the Connection Between the RSA Main Frame and the RSA Subframe.....................15-23 15.2.4 Configuring the Connection Between the High-Density Main Frame and the High-Density Subframe .....................................................................................................................................................................15-25 15.3 Configuring Synchronous Tones...............................................................................................................15-27 15.4 Configuring UAM Environment Monitoring Data...................................................................................15-28 15.5 Configuring the DDI/AT0 Trunk Access Service.....................................................................................15-30 15.6 Configuring the Hotline Service...............................................................................................................15-32 15.7 Configuring the DDN Dedicated Line Service of the DSL.......................................................................15-33 15.8 Configuring the DDN Dedicated Line Service of the HSL.......................................................................15-36 15.9 Configuring the DDN Dedicated Line Service of the SDL.......................................................................15-40 15.10 Configuring the Audio Dedicated Line Service......................................................................................15-44
16 Configuring StandAlone......................................................................................................16-1 17 Configuring Service Resource Parameters........................................................................17-1

17.1 Configuring Media Resource Parameters...................................................................................................17-2 17.2 Configuring Service Parameters..................................................................................................................17-6 17.3 Configuring QoS Parameters......................................................................................................................17-9
18 Configuring IP Network Security Data.............................................................................18-1

18.1 Configuration the Firewall..........................................................................................................................18-2 18.2 Configuring IPSec.......................................................................................................................................18-4 18.3 Configuring SSH.........................................................................................................................................18-8
A Data Planning...........................................................................................................................A-1
Issue 02 (2008-05-07) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd iii
Contents
B Glossary......................................................................................................................................B-1 Index.................................................................................................................................................i-1
iv
Issue 02 (2008-05-07)
Figures
Figures
Figure 1-1 MML command line...........................................................................................................................1-3 Figure 2-1 Steps for data configuration of the UMG8900...................................................................................2-2 Figure 3-1 Board position of the SSM-256 frame................................................................................................3-2 Figure 3-2 Board position of the SSM-32 frame..................................................................................................3-3 Figure 3-3 Numbering order of cabinets and frames in the SSM-256 self-cascading mode...............................3-4 Figure 3-4 Numbering order of cabinets and frames in the SSM-32 self-cascading mode.................................3-5 Figure 3-5 Numbering order of frames after configuration expansion of SSM-32 self-cascading......................3-5 Figure 3-6 Numbering order of cabinets and frame in the SSM-256 and SSM-32 mixed cascading mode........3-6 Figure 3-7 SSM-256 nine-frame cascading .......................................................................................................3-18 Figure 3-8 Three-frame self-cascading of SSM-32 frames................................................................................3-19 Figure 3-9 Three-frame self-cascading of SSM-32 frames................................................................................3-20 Figure 3-10 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the TNB..................3-22 Figure 3-11 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the TNB...................3-23 Figure 3-12 Mixed cascading of one SSM-256 frame and one SSM-32 frame through the TNB.....................3-24 Figure 3-13 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the BLU..................3-25 Figure 3-14 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the TNB (without GE cascading)............................................................................................................................................................3-27 Figure 3-15 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the TNB (without GE cascading)............................................................................................................................................................3-28 Figure 3-16 Mixed cascading of one SSM-256 frame and one SSM-32 through the TNB (without GE cascading) .............................................................................................................................................................................3-29 Figure 3-17 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the TNB (with GE cascading)............................................................................................................................................................3-30 Figure 3-18 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the BLU (without GE cascading) ...........................................................................................................................................................3-32 Figure 3-19 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the BLU (with GE cascading)............................................................................................................................................................3-34 Figure 3-20 Dual homing...................................................................................................................................3-40 Figure 3-21 SCTP multi-homing........................................................................................................................3-41 Figure 3-22 1+1 backup.....................................................................................................................................3-43 Figure 3-23 1:N linear multiplex section protection..........................................................................................3-44 Figure 3-24 UMG8900 connecting subscribers directly ...................................................................................3-45 Figure 3-25 Route backup of IP addresses in different network segments........................................................3-51 Figure 3-26 Route backup of IP addresses in the same network segment.........................................................3-52 Figure 4-1 Networking example...........................................................................................................................4-1 Issue 02 (2008-05-07) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd v
Figures
HUAWEI UMG8900 Universal Media Gateway Configuration Guide Figure 6-1 Steps for configuring the host time.....................................................................................................6-2 Figure 7-1 Index Mapping of Configuration Command Parameters....................................................................7-3 Figure 7-2 Networking diagram...........................................................................................................................7-5 Figure 7-3 Structure of MIB tree..........................................................................................................................7-6
Figure 7-4 Access control based on view.............................................................................................................7-7 Figure 7-5 Access control of SNMP v1/v2c........................................................................................................ 7-7 Figure 7-6 Steps for the SNMP configuration......................................................................................................7-8 Figure 7-7 Simplified steps for the SNMPv1/v2c configuration......................................................................... 7-9 Figure 7-8 Index mapping of configuration command parameters....................................................................7-10 Figure 8-1 Board layout of the UMG8900...........................................................................................................8-7 Figure 9-1 Position that SSM is transmitted in E1 signals...................................................................................9-2 Figure 9-2 Procedures for choosing clock reference source................................................................................ 9-4 Figure 9-3 Steps for clock configuration..............................................................................................................9-6 Figure 10-1 Networking diagram of a single SSM-256 frame...........................................................................10-8 Figure 10-2 Networking diagram of a single SSM-32 frame.............................................................................10-9 Figure 10-3 Networking diagram of the SSM-256 self-cascading...................................................................10-12 Figure 10-4 Networking diagram of the SSM-32 self-cascading.....................................................................10-16 Figure 10-5 Networking diagram of the SSM-256 and SSM-32 mixed cascading..........................................10-19 Figure 10-6 Networking diagram of using the E1 physical interface to carry IP packets................................10-23 Figure 11-1 Index mapping of the configuration command parameters of the MGW Data..............................11-2 Figure 11-2 Networking diagram.......................................................................................................................11-4 Figure 11-3 Networking diagram.......................................................................................................................11-8 Figure 11-4 Networking diagram.....................................................................................................................11-12 Figure 11-5 Networking Examples..................................................................................................................11-15 Figure 12-1 Index mapping of the configuration command parameters of the MGW data...............................12-8 Figure 13-1 Ethernet interface protocol stack....................................................................................................13-2 Figure 13-2 Protocol stack of the Ethernet interface..........................................................................................13-5 Figure 13-3 Protocol stack of the ATM interface..............................................................................................13-7 Figure 13-4 Protocol stack supported by the IPoE1 interface............................................................................13-9 Figure 13-5 Networking diagram of IP over E1...............................................................................................13-11 Figure 13-6 Access of the UMG8900 to a core network..................................................................................13-15 Figure 13-7 Configuration procedure for IP interface protection....................................................................13-15 Figure 14-1 Signaling adaptation and transfer in MTP2-M2UA mode.............................................................14-3 Figure 14-2 Index mapping of the configuration command parameters over M2UA........................................14-3 Figure 14-3 Networking diagram.......................................................................................................................14-8 Figure 14-4 Signaling adaptation and transfer in LAPV5-V5UA mode ...........................................................14-9 Figure 14-5 Index and interconnection mapping of the configuration command parameters of the SG over V5UA ...........................................................................................................................................................................14-10 Figure 14-6 Networking diagram.....................................................................................................................14-14 Figure 14-7 Signaling adaptation and transfer in Q.921-IUA mode................................................................14-15 Figure 14-8 Index and interconnection mapping of the configuration command parameters of the SG over IUA ...........................................................................................................................................................................14-16 Figure 14-9 Networking diagram.....................................................................................................................14-20 vi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-05-07)
Figures
Figure 14-10 Signaling adaptation and transfer in MTP3-M3UA mode.........................................................14-21 Figure 14-11 Index mapping of the configuration commands of the signaling transfer based on M3UA.......14-22 Figure 14-12 Networking diagram of the signaling transfer over M3UA........................................................14-28 Figure 14-13 Signaling transparent transmission through the semi-permanent connection............................14-29 Figure 14-14 Networking diagram...................................................................................................................14-31 Figure 14-15 CAS configuration procedure.....................................................................................................14-40 Figure 14-16 Index and interconnection mapping of the configuration command parameters of the SG over CAS ...........................................................................................................................................................................14-41 Figure 14-17 Networking diagram...................................................................................................................14-43 Figure 15-1 Procedure for configuring basic services of the UAM...................................................................15-2 Figure 15-2 UA frames and boards....................................................................................................................15-6 Figure 15-3 Physical connections between the UAFM frame and the SSM frame..........................................15-11 Figure 15-4 Physical connections between the HABD/HABL frame and the SSM frame..............................15-12 Figure 15-5 Physical connections between the PV8 in the UAM frame and the SSM frame..........................15-14 Figure 15-6 E1 port connection in sequence....................................................................................................15-15 Figure 15-7 E1 port connection in a cross order..............................................................................................15-16 Figure 15-8 Connection between the SSM frame and the main frame............................................................15-17 Figure 15-9 Physical connections between the RSP in the UAM frame and the SSM frame..........................15-18 Figure 15-10 Physical connections between the HWCB in the HABA_UP frame and the SSM frame..........15-19 Figure 15-11 Connection between the SSM frame and the direct frame.........................................................15-20 Figure 15-12 Connection between the RSP_10 main frame and the RSP_14 subframe..................................15-21 Figure 15-13 Connection between the RSA main frame and the RSA subframe............................................15-24 Figure 15-14 Connection between the main frame and the subframe..............................................................15-26 Figure 15-15 DDI/AT0 trunk access service....................................................................................................15-32 Figure 15-16 DDN dedicated line service........................................................................................................15-34 Figure 15-17 Networking diagram...................................................................................................................15-36 Figure 15-18 HW uplink mode for the V.35 interface.....................................................................................15-37 Figure 15-19 E1 bypass mode for the V.35 interface.......................................................................................15-38 Figure 15-20 HW uplink mode for the V.35 interface.....................................................................................15-41 Figure 15-21 E1 bypass mode for the V.35 interface.......................................................................................15-41 Figure 15-22 Audio dedicated line service networking...................................................................................15-45 Figure 16-1 Takeover of call control function from the MGC to StandAlone...................................................16-2 Figure 18-1 Index mapping of the configuration command parameters of the firewall....................................18-2 Figure 18-2 Index mapping of the configuration command parameters of IPSec.............................................18-5 Figure 18-3 Steps for configuring the SSH........................................................................................................18-8
Issue 02 (2008-05-07)
vii
Tables
Tables
Table 1-1 Description of shortcut icons............................................................................................................... 1-3 Table 2-1 Bearer data configuration when the UMG8900 serves as a TG...........................................................2-3 Table 2-2 Bearer Data Configuration When the UMG8900 Serves as an AG.....................................................2-4 Table 2-3 Bearer data configuration when the UMG8900 serves as a VIG.........................................................2-5 Table 2-4 Bearer data configuration when the UMG8900 serves as the NGN-enabled switch...........................2-6 Table 3-1 Equipment and resource management units.........................................................................................3-7 Table 3-2 Service and protocol processing units..................................................................................................3-9 Table 3-3 Switching and cascading units...........................................................................................................3-10 Table 3-4 Interface units.....................................................................................................................................3-12 Table 3-5 Media resource processing units........................................................................................................3-15 Table 3-6 Clock units.........................................................................................................................................3-17 Table 3-7 IP interfaces used by the UMG8900..................................................................................................3-35 Table 3-8 Usage rules of IP interfaces when the HRB is configured.................................................................3-36 Table 3-9 Usage rules for IP interfaces when no HRB is configured for single SSM-32 networking...............3-37 Table 3-10 Usage rules for IP interfaces when the HRB is configured for the single SSM-32 networking......3-38 Table 3-11 Usage rules for IP interfaces in case of SSM-256 self cascading....................................................3-38 Table 3-12 Usage rules for IP interfaces in case of SSM-32 self cascading......................................................3-39 Table 3-13 Usage rules for IP interfaces in case of SSM-256 and SSM-32 mixed cascading...........................3-39 Table 3-14 Interface protection types supported by different interfaces............................................................3-42 Table 3-15 Mapping between UA frame types and backplanes.........................................................................3-46 Table 3-16 UA frame modes..............................................................................................................................3-48 Table 5-1 Data planning.......................................................................................................................................5-1 Table 5-2 Output parameter..................................................................................................................................5-2 Table 6-1 Data planning.......................................................................................................................................6-2 Table 7-1 Parameter configuration for the three types of interfaces....................................................................7-2 Table 7-2 Input parameter.................................................................................................................................... 7-3 Table 7-3 Data planning.......................................................................................................................................7-3 Table 7-4 Data planning.....................................................................................................................................7-10 Table 8-1 Considerations in adding a board.........................................................................................................8-2 Table 8-2 Data planning.......................................................................................................................................8-4 Table 8-3 Output parameter..................................................................................................................................8-5 Table 9-1 SSM codes............................................................................................................................................9-2 Table 9-2 Clock cable connection........................................................................................................................9-5 Issue 02 (2008-05-07) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd ix
Tables
HUAWEI UMG8900 Universal Media Gateway Configuration Guide Table 9-3 Input parameter.................................................................................................................................... 9-6 Table 9-4 Data planning.......................................................................................................................................9-7 Table 10-1 Usage rules of IP interfaces when the HRB is configured...............................................................10-2 Table 10-2 Usage rules for IP interfaces when no HRB is configured for the single SSM-32 networking.......10-3 Table 10-3 Usage rules for IP interfaces when the HRB is configured for the single SSM-32 networking......10-3 Table 10-4 Input parameter................................................................................................................................10-4 Table 10-5 Data planning...................................................................................................................................10-4 Table 10-6 Data output.......................................................................................................................................10-6 Table 10-7 Data planning.................................................................................................................................10-10 Table 10-8 Data output.....................................................................................................................................10-11 Table 10-9 Data planning.................................................................................................................................10-14 Table 10-10 Data output...................................................................................................................................10-14 Table 10-11 Data planning...............................................................................................................................10-17 Table 10-12 Data output...................................................................................................................................10-18 Table 10-13 Input parameter............................................................................................................................10-21 Table 10-14 Data planning...............................................................................................................................10-21 Table 11-1 Data planning...................................................................................................................................11-2 Table 11-2 Data output.......................................................................................................................................11-3 Table 11-3 Input parameter................................................................................................................................11-6 Table 11-4 Data planning...................................................................................................................................11-6 Table 11-5 Input parameter................................................................................................................................11-9 Table 11-6 Data planning.................................................................................................................................11-10 Table 11-7 Input parameter..............................................................................................................................11-13 Table 11-8 Data planning.................................................................................................................................11-13 Table 11-9 Input parameter..............................................................................................................................11-15 Table 12-1 Input parameter................................................................................................................................12-2 Table 12-2 Data planning...................................................................................................................................12-3 Table 12-3 Input parameter................................................................................................................................12-4 Table 12-4 Data planning...................................................................................................................................12-4 Table 12-5 Input parameter................................................................................................................................12-6 Table 12-6 Data planning...................................................................................................................................12-6 Table 12-7 Data output.......................................................................................................................................12-7 Table 12-8 Input parameter................................................................................................................................12-9 Table 12-9 Data planning...................................................................................................................................12-9 Table 12-10 Data output.....................................................................................................................................12-9 Table 12-11 Input parameter............................................................................................................................12-11 Table 12-12 Data planning...............................................................................................................................12-12 Table 12-13 Data output...................................................................................................................................12-12 Table 12-14 Data planning...............................................................................................................................12-14 Table 12-15 Input parameter............................................................................................................................12-15 Table 12-16 Data planning...............................................................................................................................12-16 Table 13-1 Input parameter................................................................................................................................13-3
Issue 02 (2008-05-07)
Tables
Table 13-2 Data planning...................................................................................................................................13-3 Table 13-3 Input parameter................................................................................................................................13-5 Table 13-4 Data planning...................................................................................................................................13-5 Table 13-5 Input parameter................................................................................................................................13-7 Table 13-6 Data planning...................................................................................................................................13-7 Table 13-7 Input parameter..............................................................................................................................13-10 Table 13-8 Data planning.................................................................................................................................13-10 Table 13-9 Input parameter..............................................................................................................................13-13 Table 13-10 Data planning...............................................................................................................................13-13 Table 13-11 Data output...................................................................................................................................13-13 Table 13-12 Input parameter............................................................................................................................13-16 Table 13-13 Data planning...............................................................................................................................13-16 Table 13-14 Input parameter............................................................................................................................13-19 Table 13-15 Data planning...............................................................................................................................13-19 Table 14-1 Input parameter................................................................................................................................14-4 Table 14-2 Data planning...................................................................................................................................14-5 Table 14-3 Input parameter..............................................................................................................................14-10 Table 14-4 Data planning.................................................................................................................................14-11 Table 14-5 Input parameter..............................................................................................................................14-16 Table 14-6 Data planning.................................................................................................................................14-17 Table 14-7 Input parameter..............................................................................................................................14-23 Table 14-8 Data planning.................................................................................................................................14-24 Table 14-9 Input parameter..............................................................................................................................14-30 Table 14-10 Data planning...............................................................................................................................14-30 Table 14-11 CSN1 line signaling conversion index.........................................................................................14-32 Table 14-12 CSN1 line command conversion index........................................................................................14-33 Table 14-13 CSN1 register signaling conversion index...................................................................................14-33 Table 14-14 CSN1 register command conversion index..................................................................................14-34 Table 14-15 CAS conversion index in different countries...............................................................................14-34 Table 14-16 Brazil R2 metering pulse index....................................................................................................14-37 Table 14-17 CAS configuration in different countries.....................................................................................14-38 Table 14-18 Input parameter............................................................................................................................14-41 Table 14-19 Data planning...............................................................................................................................14-42 Table 15-1 Preparations......................................................................................................................................15-1 Table 15-2 Input parameter................................................................................................................................15-4 Table 15-3 Data planning...................................................................................................................................15-4 Table 15-4 Data output.......................................................................................................................................15-5 Table 15-5 Input parameter................................................................................................................................15-9 Table 15-6 Data planning...................................................................................................................................15-9 Table 15-7 Descriptions of the HWC interface................................................................................................15-21 Table 15-8 Descriptions of the HW interface in the RSP_14 frame................................................................15-22 Table 15-9 Input parameter..............................................................................................................................15-22 Issue 02 (2008-05-07) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xi
Tables
HUAWEI UMG8900 Universal Media Gateway Configuration Guide Table 15-10 Data planning...............................................................................................................................15-22 Table 15-11 Input parameter............................................................................................................................15-24 Table 15-12 Data planning...............................................................................................................................15-25 Table 15-13 Input parameter............................................................................................................................15-26 Table 15-14 Data planning...............................................................................................................................15-26 Table 15-15 Input parameter............................................................................................................................15-27 Table 15-16 Data planning...............................................................................................................................15-27 Table 15-17 Input parameter............................................................................................................................15-29 Table 15-18 Data planning...............................................................................................................................15-29 Table 15-19 Input parameter............................................................................................................................15-31 Table 15-20 Data planning...............................................................................................................................15-31 Table 15-21 Input parameter............................................................................................................................15-33 Table 15-22 Data planning...............................................................................................................................15-33 Table 15-23 Input parameter............................................................................................................................15-35 Table 15-24 Data planning...............................................................................................................................15-35 Table 15-25 Input parameter............................................................................................................................15-38 Table 15-26 Data planning...............................................................................................................................15-38 Table 15-27 Input parameter............................................................................................................................15-42 Table 15-28 Data planning...............................................................................................................................15-42 Table 15-29 Input parameter............................................................................................................................15-45 Table 15-30 Data planning...............................................................................................................................15-45 Table 16-1 Input parameter................................................................................................................................16-2 Table 16-2 Data planning...................................................................................................................................16-2 Table 17-1 Board configuration of the VPU......................................................................................................17-2 Table 17-2 Input parameter................................................................................................................................17-4 Table 17-3 Data planning...................................................................................................................................17-4 Table 17-4 Input parameter................................................................................................................................17-6 Table 17-5 Data planning...................................................................................................................................17-7 Table 17-6 Input parameter................................................................................................................................17-9 Table 17-7 Data planning...................................................................................................................................17-9 Table 18-1 Input parameter................................................................................................................................18-2 Table 18-2 Data planning...................................................................................................................................18-3 Table 18-3 Input parameter................................................................................................................................18-5 Table 18-4 Data planning...................................................................................................................................18-6 Table 18-5 Data planning...................................................................................................................................18-9 Table A-1 Data planning.....................................................................................................................................A-1 Table A-2 Data planning.....................................................................................................................................A-2 Table A-3 Data planning.....................................................................................................................................A-3 Table A-4 Data planning.....................................................................................................................................A-4 Table A-5 Data planning.....................................................................................................................................A-4 Table A-6 Data planning.....................................................................................................................................A-5 Table A-7 Data planning.....................................................................................................................................A-6
xii
Issue 02 (2008-05-07)
Tables
Table A-8 Data planning.....................................................................................................................................A-7 Table A-9 Data planning.....................................................................................................................................A-8 Table A-10 Data planning...................................................................................................................................A-9 Table A-11 Data planning.................................................................................................................................A-10 Table A-12 Data planning.................................................................................................................................A-11 Table A-13 Data planning.................................................................................................................................A-12 Table A-14 Data planning.................................................................................................................................A-12 Table A-15 Data planning.................................................................................................................................A-13 Table A-16 Data planning.................................................................................................................................A-13 Table A-17 Data planning.................................................................................................................................A-14 Table A-18 Data planning.................................................................................................................................A-14 Table A-19 Data planning.................................................................................................................................A-15 Table A-20 Data planning.................................................................................................................................A-15 Table A-21 Data planning.................................................................................................................................A-16 Table A-22 Data planning.................................................................................................................................A-16 Table A-23 Data planning.................................................................................................................................A-17 Table A-24 Data planning.................................................................................................................................A-18 Table A-25 Data planning.................................................................................................................................A-18 Table A-26 Data planning.................................................................................................................................A-19 Table A-27 Data planning.................................................................................................................................A-19 Table A-28 Data planning.................................................................................................................................A-21 Table A-29 Data planning.................................................................................................................................A-22 Table A-30 Data planning.................................................................................................................................A-24 Table A-31 Data planning.................................................................................................................................A-26 Table A-32 Data planning.................................................................................................................................A-26 Table A-33 Data planning.................................................................................................................................A-27 Table A-34 Data planning.................................................................................................................................A-28 Table A-35 Data planning.................................................................................................................................A-29 Table A-36 Data planning.................................................................................................................................A-29 Table A-37 Data planning.................................................................................................................................A-29 Table A-38 Data planning.................................................................................................................................A-30 Table A-39 Data planning.................................................................................................................................A-30 Table A-40 Data planning.................................................................................................................................A-31 Table A-41 Data planning.................................................................................................................................A-31 Table A-42 Data planning.................................................................................................................................A-31 Table A-43 Data planning.................................................................................................................................A-32 Table A-44 Data planning.................................................................................................................................A-32 Table A-45 Data planning.................................................................................................................................A-33 Table A-46 Data planning.................................................................................................................................A-34 Table A-47 Data planning.................................................................................................................................A-35 Table A-48 Data planning.................................................................................................................................A-36 Table A-49 Data planning.................................................................................................................................A-37 Issue 02 (2008-05-07) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xiii
Tables
HUAWEI UMG8900 Universal Media Gateway Configuration Guide Table A-50 Data planning.................................................................................................................................A-38 Table A-51 Data planning.................................................................................................................................A-38 Table A-52 Data planning.................................................................................................................................A-40
xiv
Issue 02 (2008-05-07)
About This Document
About This Document

Purpose
The data configuration corresponding to different networking requirements are required for the UMG8900 after hardware and software installation to provide service bearer and processing functions. This document describes the data configuration on the UMG8900 and the contents cover related concepts, configuration procedures, and configuration notes.
Related Versions
The following table lists the product versions related to this document. Product Name HUAWEI UMG8900 Version V100R007
Intended Audience
The intended audiences of this document are:
l l l l
Network administrator System engineer Commissioning engineer Operation and maintenance engineer
Update History
Updates between document versions are cumulative. Therefore, the latest document version contains 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
Issue 02 (2008-05-07)
About This Document
Organization
This document describes the data configuration procedures and methods on the UMG8900 and provides 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 general knowledge 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 load server 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 synchronization mode and how to manually set the time, time zone, Network Time Protocol (NTP) server, and daylight saving time (DST). 7 Configuring NMS Data This describes how to configure the interconnection data between the UMG8900 and the network management system (NMS), including the configurations of the NMS interface and Simple Network 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 line clock source. 10 Configuring the MGW Control Interface and SIGTRAN Interface This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface. 11 Configuring MGW Control Data This describes how to configure the media gateway (MGW) control data. The standard MGW control 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 of the voice service and data service. 12 Configuring TDM Bearer
2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-05-07)
About This Document
This describes how to configure the time division multiplexing (TDM) bearer data including the TDM interface, TDM timeslot, TDM trunk group management, and office direction information. In the actual networking application, the service exchange between the UMG8900 and and public switching telephone network (PSTN) switch is based on the TDM bearer. The connection between the UMG8900 and other media gateways (MGWs) can also be based on the TDM bearer. 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 bearer data when the UMG8900 acts as a media gateway (MGW) in the core network and the connections 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 a signaling gateway (SG) and supports the signaling transfer function. In some networking applications, to reduce connections between network elements, no physical connection exists between the media gateway controller (MGC) and the remote devices. The signaling data between the two connected devices are transferred by the UMG8900. In this case, you need to set 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 ESL subscribers and that of the V5 subscribers. 17 Configuring Service Resource Parameters This describes how to configure the service resource parameters, including the media resource parameters, 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 how to configure the firewall, IP Security Protocol (IPSec), and Security Shell (SSH). The UMG8900 can enable the firewall and the IPSec function on the media gateway (MGW) control interface, network management interface, and signaling transport (SIGTRAN) interface to achieve security protection on these types of control packets. Based on the SSH protocol, you can 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
Issue 02 (2008-05-07) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 3
About This Document
Symbol
Description Indicates a hazard with a high level of risk that, if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save your time. Provides additional information to emphasize or supplement important points of the main text.
DANGER
WARNING
CAUTION
TIP
NOTE
2. General Conventions Convention Times New Roman Boldface Italic Courier New 3. Command Conventions Convention Boldface Italic [] {x | y | ...} [ x | y | ... ] { x | y | ... } * Description The keywords of a command line are in boldface. Command arguments are in italic. Items (keywords or arguments) in square brackets [ ] are optional. Alternative items are grouped in braces and separated by vertical bars.One is selected. Optional alternative items are grouped in square brackets and separated by vertical bars.One or none is selected. Alternative items are grouped in braces and separated by vertical bars.A minimum of one or a maximum of all can be selected. Description Normal paragraphs are in Times New Roman. Names of files,directories,folders,and users are in boldface. For example,log in as user root . Book titles are in italics. Terminal display is in Courier New.
Issue 02 (2008-05-07)
About This Document
Convention [ x | y | ... ] *
Description Alternative items are grouped in braces and separated by vertical bars.A minimum of zero or a maximum of all can be selected.
4. GUI Conventions Convention Boldface > Description Buttons,menus,parameters,tabs,window,and dialog titles are in boldface. For example,click OK. Multi-level menus are in boldface and separated by the ">" signs. For example,choose File > Create > Folder .
5. Keyboard Operation Convention Key Key1+Key2 Key1,Key2 Description Press the key.For example,press Enter and press Tab. Press the keys concurrently.For example,pressing Ctrl+Alt+A means the three keys should be pressed concurrently. Press the keys in turn.For example,pressing Alt,A means the two keys should be pressed in turn.
6. Mouse Operation Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Issue 02 (2008-05-07)
1 Introduction
1
About This Chapter
Introduction
This describes the data configuration methods and cautions of the UMG8900. 1.1 Data Configuration Methods This describes the data configuration methods, including configurations through man-machine language (MML) commands, device panel, and data configuration scripts. 1.2 Cautions for Data Configuration This describes the cautions for data configuration of the UMG8900.
Issue 02 (2008-05-07)
1-1
1 Introduction
1.1 Data Configuration Methods

This describes the data configuration methods, including configurations through man-machine language (MML) commands, device panel, and data configuration scripts. You can adopt the above methods through Huawei local maintenance terminal (LMT). Before configuration, you need to start the LMT and log in to the OMC port (the first FE port on the NET in the main control frame).
NOTE
The Internet Protocol (IP) address of the OMC network port is often defined in the MML.txt file. When logging in for the first time, you need to add an office and set the office address as specified in the MML.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 the OMC network port by running MOD OMCIP after logging in to the office. For more information, see the MML online help. 1.1.1 MML Using Methods This describes how to use the man-machine language (MML) commands to configure data. The MML command is the commonly-used configuration method, and it can complete all the configurations. 1.1.2 Methods of Using Device Panel This describes how to use the device panel to configure data. Using the device panel can complete the configuration of hardware such as the frame and board. Its advantage is direct view, but using the device panel can only complete the configuration of some data. 1.1.3 Methods of Using Data Scripts This describes how to use the script to configure data. Huawei compiles the configuration data into script files. Using the script files, users can complete the data configuration.
1.1.1 MML Using Methods

This describes how to use the man-machine language (MML) commands to configure data. The MML command is the commonly-used configuration method, and it can complete all the configurations. The MML command is a common configuration method provided by telecommunication device suppliers at present. The local maintenance terminal (LMT) supports the MML command line mode. Refer to Figure 1-1.
1-2
Issue 02 (2008-05-07)
1 Introduction
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, Frame Type, Cabinet No., and Location in Cabinet in Figure 1-1. You must type these parameters; otherwise, execution of a command fails. 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 optional and do not affect the execution of a command. To reduce workload for data configuration, the system presets some parameters that are fixed and need no frequent change to default values. You can decide whether to change these parameters based on actual conditions.
Issue 02 (2008-05-07)
1-3
1 Introduction
l
If you are not aware of the default value or value range of a parameter, you can point the arrow of the mouse to the input box of the parameter and in about one second, the system displays the default value or value range of the parameter in a small pane. For functions, notes, parameter description, and examples of MML commands, see the MML online help.
1.1.2 Methods of Using Device Panel

This describes how to use the device panel to configure data. Using the device panel can complete the configuration of hardware such as the frame and board. Its advantage is direct view, but using the device panel can only complete the configuration of some data. The device panel is used for:
l l
Data configuration of hardware (frames and boards) Routine query
Its advantage is direct view. For example, you can directly see the types and states of boards deployed in the system. The LMT provides the device panel. For usage of the device panel, see the man-machine language (MML) online help.
1.1.3 Methods of Using Data Scripts

This describes how to use the script to configure data. Huawei compiles the configuration data into script files. Using the script files, users can complete the data configuration.
CAUTION
As the data scripts are compiled under lab environment, they may not be fully suitable for deployment. 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 l l l
Deployment System expansion Software upgrade Routine maintenance
Huawei compiles a data script file under lab environment to:

l l
Improve efficiency of data configuration 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 Batch Command, 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 the setting.
1-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-05-07)
1 Introduction
1.2 Cautions for Data Configuration

This describes the cautions for data configuration of the UMG8900. Back up the current configuration script before modifying the data configuration to avoid data loss. After the configuration is complete, run SAVE CFG to save the data so that the configuration data is not lost when the system is restarted. Otherwise, you need to configure the data again after the system is restarted.
Issue 02 (2008-05-07)
1-5
2 General Description of Data Configuration
General Description of Data Configuration
About This Chapter

This describes the general procedure for configuring data, and helps you have a general knowledge of data configuration. 2.1 General Procedures for Data Configuration This describes the general procedure for data configuration. 2.2 Configuration Index This describes the configuration index and reference of the UMG8900 in different positions of a network.
Issue 02 (2008-05-07)
2-1
2.1 General Procedures for Data Configuration

This 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 system parameters
Configure the system time
Configure the NMS
Configure frames and boards
Configure the clock Configure MGW control interfaces and physical interfaces of SIGTRAN interfaces Configure MGW control data
Configure TDM bearer
Configure IP bearer
Configure signaling transfer
Configure the UAM
Configure StandAlone
Configure service source parameters
Configure IP network security data
End
2-2
Issue 02 (2008-05-07)
Since the index relationship exists between different configuration commands, data configuration of the UMG8900 must follow certain order.
2.2 Configuration Index

This describes the configuration index and reference of the UMG8900 in different positions of a network. 2.2.1 TG Configuration Index This describes the configuration procedure and reference when the UMG8900 serves as a trunk gateway (TG). 2.2.2 AG Configuration Index This describes the configuration procedure and reference when the UMG8900 serves as an access gateway (AG). 2.2.3 VIG Configuration Index This describes the configuration procedure and reference when the UMG8900 serves as a video interworking gateway (VIG). 2.2.4 Configuration Index of NGN-Enabled Switch This describes the configuration procedure and reference when the UMG8900 serves as an NGNenabled switch.
2.2.1 TG Configuration Index

This describes the configuration procedure and reference when the UMG8900 serves as a trunk gateway (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 MGW control data Interconnecte d Device MGC Configuration Description Configure the data of physical interfaces between the UMG8900 and the MGC. Configure the MGW control data between the UMG8900 and the MGC. TDM bearer data PSTN switch Configure the TDM bearer for bearing service data between the UMG8900 and PSTN switch. Reference 10 Configuring the MGW Control Interface and SIGTRAN Interface 11 Configuring MGW Control Data
12 Configuring TDM Bearer
Issue 02 (2008-05-07)
2-3
Bearer Data IP bearer data
Interconnecte d Device MGW
Configuration Description Configure IP bearer data between the UMG8900 and other MGWs. If signaling packets need to be transferred, configure signaling transfer for the UMG8900.
Reference 13 Configuring IP Bearer 14 Configuring Signaling Transfer
Signaling transfer data
MGC
2.2.2 AG Configuration Index

This describes the configuration procedure and reference when the UMG8900 serves as an access gateway (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 MGW control data Interconnected Device MGC Configuration Description Data of physical interfaces between the UMG8900 and the MGC Configure the MGW control data between the UMG8900 and the MGC. TDM bearer data V5 access network PBX UAM data UAM TDM connection to the V5 access network TDM connection to the PBX When the UMG8900 is directly connected with users through the subscribe frame, configure the UAM data. 15 Configuring UAM Data Reference 10 Configuring the MGW Control Interface and SIGTRAN Interface 11 Configuring MGW Control Data
2-4
Issue 02 (2008-05-07)
Bearer Data IP bearer data
Interconnected Device MGW
Configuration Description The connection between the UMG8900 and other MGWs in the core network is based on IP bearer, and thus configure the IP bearer data. If signaling packets of IUA/V5UA are required to be transferred, configure signaling transfer for the UMG8900. Configure StandAlone, which can connect calls between users when the communication between the UMG8900 and the MGW fails.
Reference 13 Configuring IP Bearer
MGC
14 Configuring Signaling Transfer
StandAlone
MGC
16 Configuring StandAlone
2.2.3 VIG Configuration Index

This describes the configuration procedure and reference when the UMG8900 serves as a video interworking 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 Bearer Data MGW control data Interconnecte d Device MGC Configuration Description Configure the data of physical interfaces between the UMG8900 and the MGC. Configure the MGW control data between the UMG8900 and the MGC. Reference 10 Configuring the MGW Control Interface and SIGTRAN Interface 11 Configuring MGW Control Data
Issue 02 (2008-05-07)
2-5
Bearer Data TDM bearer data
Interconnecte d Device GMSC
Configuration Description Configure the TDM bearer for bearing service data between the UMG8900 and GMSC. When the UMG8900 serves as a VIG, it is connected with the H. 323 and SIP terminals based on IP bearer. If signaling packets are required to be transferred, configure signaling transfer for the UMG8900.
Reference 12 Configuring TDM Bearer
IP bearer data
H.323/SIP terminal
13 Configuring IP Bearer
MGC
2.2.4 Configuration Index of NGN-Enabled Switch

This describes the configuration procedure and reference when the UMG8900 serves as an NGNenabled 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 Bearer Data MGW control data Interconnecte d Device MGC Configuration Description Configure the data of physical interfaces between the UMG8900 and the MGC. Configure the MGW control data between the UMG8900 and the MGC. TDM bearer data PSTN switch Configure the TDM connection to the PSTN local office. Configure the TDM connection to the PSTN trunk office. Reference 10 Configuring the MGW Control Interface and SIGTRAN Interface 11 Configuring MGW Control Data
2-6
Issue 02 (2008-05-07)
Bearer Data UAM data
Interconnecte d Device UAM
Configuration Description When the UMG8900 directly accesses users through the subscriber frame, configure the UAM data. If signaling packets of V5UA/IUA are required to be transferred, configure signaling transfer for the UMG8900. Configure StandAlone, which can connect calls between users when the communication between the UMG8900 and the MGW fails.
Reference 15 Configuring UAM Data
MGC
StandAlone
MGC
Issue 02 (2008-05-07)
2-7
3 Preliminary Knowledge
3
About This Chapter
Preliminary Knowledge
This describes the necessary knowledge of the UMG8900. 3.1 Frames and Boards This describes the hardware of the UMG8900. 3.2 Frame Cascading This describes the cascading relationship of the SSM-256 self-cascading, SSM-32 selfcascading, and SSM-32 and SSM-256 mixed-cascading. 3.3 Centralized Forwarding This describes the concept and configuration principles of centralized forwarding. 3.4 Dual Homing This describes the concept and configuration principles of dual homing. 3.5 SCTP Multi-Homing This describes the concept and configuration principles of Stream Control Transmission Protocol (SCTP) multi-homing. 3.6 Virtual Media Gateway This describes the concept and configuration principles of the virtual media gateway (VMGW). 3.7 Interface Protection This 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 Information This describes the background information of the user access module (UAM). 3.9 Route Backup This describes the concept and cautions of route backup.
Issue 02 (2008-05-07)
3-1
3.1 Frames and Boards

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

This describes the SSM-256 frame of the UMG8900. The SSM-256 frame provides the 256 K time division multiplexing (TDM) service switching platform. SSM-256 frames can be divided into four types:
l l l l
Main control frame Central switching frame Service frame Control frame
The main control frame is considered as an example, and Figure 3-1 shows the board position of the SSM-256 frame. SSM-256 frames of other types differ from the main control frame in that their front slots 7 and 8 are inserted with the MPUs rather than OMUs. The CLK is not configured in other types of frames. Figure 3-1 Board position of the SSM-256 frame
0 Back board M C L K C o m m o n 0 1 M C L K C o m m o n 1 2 C o m m o n C o m m o n 2 3 C o m m o n C o m m o n 3 4 C o m m o n C o m m o n 4 5 C o m m o n C o m m o n 5 6 M T N B C o m m o n 6 7 M N E T 8 M N E T 9 M T N B C o m m o n 9 1 0 C o m m o n C o m m o n 1 0 1 1 C o m m o n C o m m o n 1 1 1 2 C o m m o n C o m m o n 1 2 1 3 C o m m o n C o m m o n 1 3 1 4 C o m m o n C o m m o n 1 4 1 5 C o m m o n C o m m o n 1 5
Backplane
Front board
M O M U 7
M O M U 8
3-2
Issue 02 (2008-05-07)
3.1.2 Introduction to the SSM-32 Frame

This describes the SSM-32 frame of the UMG8900. The SSM-32 frame provides the 32 K time division multiplexing (TDM) service switching platform. SSM-32 frames can be divided into two types:
l l
Main control frame Service frame
Figure 3-2 shows the board position of the SSM-32 frame. In the case of SSM-32 frames, a service frame differs from the main control frame in that their front slots 7 and 8 are inserted with MPB boards rather than OMB boards. Figure 3-2 Board position of the SSM-32 frame
0 Back board C o m m o n C o m m o n 0 1 C o m m o n C o m m o n 1 2 C o m m o n C o m m o n 2 3 C o m m o n C o m m o n 3 4 C o m m o n C o m m o n 4 5 C o m m o n C o m m o n 5 6 6 M T N B 7 8 M T N B 9 10 11 12 13 14 15 C o m m o n C o m m o n 9 C o m m o n C o m m o n C o m m o n C o m m o n C o m m o n C o m m o n C o m m o n C o m m o n C o m m o n C o m m o n
Backplane
Front board
M T N B 7 8
M T N B
10 11 12 13 14 15
The distinct difference between the SSM-256 frame and the SSM-32 frame is that the main control board in an SSM-256 frame is the OMU and occupies only one slot, while that in the SSM-32 is the MOMB and occupies two slots.
3.1.3 Numbering Cabinets and Frames

This describes the numbering order and configuration principle of the SSM-256 and SSM-32 frames.
Numbering Principles
The SSM-256 frame supports the cascading of up to nine frames, while the SSM-32 frame supports the cascading of up to three frames. A mixed networking with both SSM-256 and SSM-32 frames supports the cascading of up to 29 frames. The frame numbering order varies with 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 a cabinet, from bottom to top.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 3-3
Issue 02 (2008-05-07)
l
SSM-256 self-cascading: The No. of the main control frame is 1, the Nos. of service frames are 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, the main control frame can be directly inserted with the BLU or FLU cascading boards to serve as the central switching frame concurrently. SSM-32 self-cascading: The No. of the main control frame is 1. The Nos. of service frames are 2 and 3. 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 control frame. Though no extended control is configured in the mixed cascading, the frame No. is reserved. If needed, you can configure an independent central switching frame with the frame No. as 0. The main control frame can also be directly inserted with the BLU or FLU cascading boards to serve as the central switching frame concurrently. 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 Mode

Figure 3-3 shows the numbering order of cabinets and frames in the SSM-256 self-cascading mode. Figure 3-3 Numbering order of cabinets and frames in the SSM-256 self-cascading mode
cabinet 0 Service frame Frame No.: 2 cabinet 1 Service frame Frame No.: 5 cabinet 2 Extended control frame Frame No.: 8
Central switching frame Frame No.: 0
Service frame Frame No.: 4
Main contro frame Frame No.: 1
Numbering Frames in SSM-32 Self-Cascading Mode

Figure 3-4 shows the numbering order of cabinets and frames in the SSM-32 self-cascading mode.
3-4
Issue 02 (2008-05-07)
Figure 3-4 Numbering order of cabinets and frames in the SSM-32 self-cascading mode
cabinet 0 Service frame Frame No.: 3
Numbering in SSM-256 and SSM-32 Mixed Cascading mode

After the configuration expansion from the SSM-32 self-cascading mode to the mixed cascading mode. 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 Service frame Frame No.: 3 cabinet 1 Service frame Frame No.: 5
...
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-32 mixed cascading mode.
Issue 02 (2008-05-07)
3-5
Figure 3-6 Numbering order of cabinets and frame in the SSM-256 and SSM-32 mixed cascading mode
cabinet 0 Service frame Frame No.: 2 cabinet 1 Service frame Frame No.: 5 cabinet 9
...
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 out dense E1 cables. That is, it is inserted with service frames 3 and 4. The space for service frame 5 is empty. It is recommended that you reserve frame No. 5 and number frames in cabinet 2 from 6.
Rules for Configuring Frames in Cabinets

In actual networking of the UMG8900, some factors must be considered, such as:
l l l l l
Cooperation with an SIWF device E1 interface applications SSM-256 self-cascading SSM-32 self-cascading 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 frames at most for the convenience of installation and cabling. The central switching frame and control frame have no TDM service interface. Thus, the cabinet where the central switching frame or control frame is located can hold three frames, which does not affect the installation and cabling. The frames in the cabinet are placed from bottom to top. The main control frame is configured by default. It manages and maintains the whole UMG8900 while providing services. The main control frame is always numbered 1 and cannot be assigned with any other No.
l l
3-6
Issue 02 (2008-05-07)
3.1.4 Introduction to Boards

This describes the boards of the UMG8900. Based on functions, boards are classified into the types, including the equipment and resource management unit, service and protocol processing unit, 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 Logical Board Operation Maintenance Unit (OMU) Physical Board Media gateway Operation Maintenance Unit (MOMU) Backup Mode Board Position Function
Master/slave
It is inserted in front slot 7 or 8 of the SSM-256 main control frame. A corresponding NET back board is required.
The OMU manages all the frames of the UMG8900 when multiple frames are configured. The MOMB can convert the broadband service data. The board provides the external interfaces including the Console interface. The MPU manages the boards in the frame where the MPU is located. The MMPB can convert the broadband service data.
Media gateway Operation Maintenance Unit B (MOMB)
Master/slave
It is inserted in front slots 6, 7, 8 and 9 of the SSM-32 main control frame. Each board occupies two slots. A corresponding TNC back board is required.
Main processing unit (MPU)
Media gateway Main Processing Unit (MMPU)
Master/slave
It is inserted in front slot 7 or 8 of the SSM-256 frame except the main control frame. A corresponding NET back board is required.
Media gateway Main Processing Unit B (MMPB)
Master/slave
It is inserted in front slots 6, 7, 8 and 9 of a SSM-32 service frame. Each board occupies two slots. A corresponding TNC back board is required.
Issue 02 (2008-05-07)
3-7
Board Name Logical Board Connection Maintenance Unit (CMU) Physical Board Media gateway Connection Maintenance Front Unit (MCMF)
Backup Mode
Board Position
Function
Master/slave
It is inserted in a common front slot of the SSM-256 frame or the SSM-32 frame. No corresponding back board is required.
The CMU processes messages of the media resource control protocol and operates the corresponding resources.
Media gateway Connection Maintenance Back unit (MCMB)
Master/slave
It is inserted in a common back slot of the SSM-256 frame or SSM-32 frame. No corresponding front board is required.
Connection Maintenance Unit (CMU)
Sub-card of Connection & Management Unit (SCMU)
Load sharing or master/ slave
It is inserted in the subboard slot of the UG02MOMB or the UG02MMPB of the SSM-32 frame.
The CMU processes messages of the media resource control protocol and operates the corresponding resources. The PPU processes the H. 248/SCTP/ UDP/TCP/IP protocols. The external interfaces include the FE interface.
Protocol Processing Unit (PPU)
Media gateway Back Protocol Processing Unit (MPPB)
Load sharing
It is inserted in a common back slot of the SSM-256 frame. No corresponding front board is required.
Media gateway Connection Maintenance Front Unit (MCMF)
Load sharing
Media gateway Connection Maintenance Back unit (MCMB)
Load sharing
It is inserted in a common back slot of the SSM-256 frame or the SSM-32 frame. No corresponding front board is required.
3-8
Issue 02 (2008-05-07)
Service and Protocol Processing Units

Table 3-2 Service and protocol processing units Board Name Logical Board High-speed Routing Unit (HRB) Physical Board Media gateway High-speed Routing Unit (MHRU) Media gateway RTP Processing Unit (MRPU) Backup Mode Board Position Function
Master/slave
High-speed Routing Unit (HRB)
Master/slave
It is inserted in a common front slot of the SSM-256 frame or the SSM-32 frame. A corresponding E8T/E1G/P4L/ P1H back board is required.
The MHRU transfers the RTP/RTCP and IP bearer services. The MRPU processes the IP routes, converges and distributes IP services. The MHRD processed the IP routes, and it converges, and distributes the IP services. The MHRD provides the service access function. The MIOE implement IP over E1. When the board is used in the SSM-256 frame, the frame must be configured with the MTNB.
Media gateway High-speed Routing Unit D (MHRD)
Master/slave
It is inserted in a common back slot of the SSM-256 frame or the SSM-32 frame. A corresponding D8FT/D1GO subboard is required.
Media gateway IP over E1 Unit (MIOE)
Master/slave
It is inserted in a common front slot of the SSM-256 frame or the SSM-32 frame.
Issue 02 (2008-05-07)
3-9
Board Name Logical Board Front Signalling Processing unit (SPF) Physical Board Media gateway Front Signalling Processing unit (MSPF)
Backup Mode
Board Position
Function
Load sharing
The SPF performs signaling adaptation and transfers the signaling.
Switching and Cascading Units

Table 3-3 Switching and cascading units Board Name Logical Board Packet switch Unit (NET) Physical Board Media gateway Packet switch Unit (MNET) Backup Mode Board Position Function
Master/slave
It is inserted in back slot 7 or 8 of the SSM-256 frame. A corresponding MPU or OMU front board is required.
The NET implements switching of packet services and data cascading between frames. The external interfaces includes the 2xGE, 4xFE, Clock, MIR, OMC interfaces.
Front Link Unit (FLU)
Media gateway Front Link Unit (MFLU)
Nullbackup
It is inserted in a front slot of the SSM-256 central switching frame except slots 6, 7, 8 and 9. A corresponding BLU back board is required.
The FLU and BLU provide 32 K or 24 K subscriber cascading capacity, interfacing and switching functions on time division multiplexing (TDM) narrowband data plane, and 2
3-10
Issue 02 (2008-05-07)
Board Name Logical Board Back Link Unit (BLU) Physical Board Media gateway Back Link Unit (MBLU)
Backup Mode
Board Position
Function
Master/slave
It is inserted in a back slot of the SSM-256 central switching frame except slots 6, 7, 8 and 9. A corresponding FLU front board is required.
x 1.25 Gbit/s cascading capacity and interfacing function on the broadband data plane. Providing FE control data channels to directly connect frames The BLU provides the cascading interface. The NLU provides 2 x 1.25G/1 x 1.25G cascading capacity and interfacing function on the broadband data plane. The TNU implements TDM service switching. The MTNU provides 24 K cascading capacity. The TCLU provides 24 K cascading capacity. The MTNB provides 32 K cascading capacity. The MTNC provides 3 x 8K
Net Link Unit (NLU)
Media gateway Net Link Unit (MNLU)
Load sharing
It is in back slots 4, 5, 10 and 11 of the SSM-32 frame.
TDM central switching Net Unit (TNU)
Media gateway TDM switching Net Unit (MTNU)
Master/slave
It is inserted in back slot 6 or 9 of the SSM-256 frame. No corresponding front board is required.
TDM Convergence & Link Unit (TCLU)
Master/slave
It is inserted in back slot 6 or 9 of the SSM-256 main control frame or the service frame. No corresponding front board is required.
Issue 02 (2008-05-07)
3-11
Board Name Logical Board Physical Board Media gateway TDM switching Net Unit B (MTNB)
Backup Mode
Board Position
Function
Master/slave
It is inserted in back slot 6 or 9 of the SSM-256 frame. No corresponding front board is required.
cascading capacity. The MTNC provides the FE switching function for the control plane. The MTNC provides multiframe cascading channels for the FE plane and the TDM plane.
Media gateway TDM switching Net Unit C (MTNC)
Master/slave
It is in back slots 6, 7, 8 and 9 of the SSM-32 frame. Each board occupies two slots.
A corresponding MOMB/MMPB front The MTNC board is required. manages the boards in the frame where the MTNC is located. The MTNC provides level 3 clock signal for the system through the clock subboard.
Interface Units
Table 3-4 Interface units Board Name Logical Board 1-port GE Optical interface card (E1G) Physical Board Media gateway one-port GE Optical interface card (MG1O) Backup Mode Board Position Function
Nullbackup
It is inserted in a common back slot of the SSM-256 frame or the SSM-32 frame. A corresponding HRB front board is required.
The E1G provides one GE interface.
3-12
Issue 02 (2008-05-07)
Board Name Logical Board 1-port STM-4 POS optical Interface board (P1H) Physical Board Media gateway 1 Port STM-4 POS Optical Interface Board (MP1H)
Backup Mode
Board Position
Function
Nullbackup
The P1H provides one 622 Mbit/s POS interface.
2*155M SDH/ SONET optical interface card (S2L)
Media gateway 2*155M SDH/ SONET optical interface card (MS2L) Media gateway 2*155M SDH/ SONET Electronical interface card (MS2E)
Master/ slave or load sharing
The UG01MS2L and UG01MS2E can be only inserted in a common back slot of the SSM-256 frame. The UG02MS2L and UG02MS2E can be inserted in a common back slot of the SSM-256 frame or the SSM-32 frame. No corresponding front board is required. It is inserted in a common back slot of the SSM-32 frame. No corresponding front board is required.
The MS2L provides two 155 Mbit/s SDH optical interfaces. The MS2E provides two 155 Mbit/s SDH electrical interfaces.
1*155M SDH/ SONET optical interface card (S1L)
Media gateway 1*155M SDH/ SONET optical interface card (MS1L) Media gateway 2*155M SDH/ SONET Electronical interface card (MS1E) Media gateway 4 Ports STM-1 ATM Optical Interface Board (MA4L)
The MS1L provides one 155 Mbit/s SDH optical interface. The MS1E provides one 155 Mbit/s SDH electrical interface.
4 Ports STM-1 ATM Optical Interface Board (A4L)
Nullbackup
It is inserted in a common back slot of the SSM-256 frame or the SSM-32 frame. A corresponding ASU front board is required.
The A4L provides four 155 M ATM optical interfaces.
Issue 02 (2008-05-07)
3-13
Board Name Logical Board 4 Port STM-1 POS Optical Interface Board (P4L) Physical Board Media gateway 4 Port STM-1 POS Optical Interface Board (MP4L)
Backup Mode
Board Position
Function
Nullbackup
The P4L provides four 155 Mbit/s POS interfaces.
8-port 10/100M Ethernet interface board (E8T)
Media gateway 8port 10/100M Ethernet Interface Board (ME8T)
Nullbackup
The E8T provides eight FE interfaces.
32*E1 port TDM interface board (E32)
Media gateway 32*E1 ports TDM interface board (ME32) Media gateway 32*E1 interface card with Signaling function Unit (MESU)
Load sharing
Load sharing
The ME32 provides 32 E1 interfaces to extract line signaling from CAS such as R2 and CNo.1 or insert line signaling into them. The MESU provides 32 E1 interfaces to receive and send NO.5 line signaling and register signaling. The MT32 provides 32 T1 interfaces to extract line signaling from CAS such as R2 and CNo.1 or insert line signaling into them.
32*T1 port TDM interface board (T32)
Media gateway 32*T1 ports TDM interface board (MT32)
Load sharing
3-14
Issue 02 (2008-05-07)
Board Name Logical Board 32*T1 port TDM interface board (T32) Physical Board Media gateway 32*T1 interface card with Signaling function Unit (MTSU)
Backup Mode
Board Position
Function
Load sharing
The MTSU provides 32 T1 interfaces to receive and send NO.5 line signaling and register signaling. The PIE provides three E3/T3 PDH electrical interfaces.
PDH Interface Electronical Unit (PIE)
Media gateway PDH Interface Electronical Unit (MPIE)
Media Resource Processing Units

Table 3-5 Media resource processing units Board Name Logical Board Voice Processing Unit (VPU) Physical Board Media gateway Voice Processing Unit B (MVPB) Backup Mode Board Position Function
Load sharing
It is inserted in a common front slot of the SSM-256 frame. No corresponding back board is required.
Media gateway Voice Processing Unit D (MVPD)
Load sharing
The VPU provides the transcoding and EC functions for voice service streams. The VPU provides announcement playing resources to implement the digit-collecting and announcementplaying services.
Issue 02 (2008-05-07)
3-15
Board Name Logical Board Physical Board Media gateway TransCode Unit B (MTCB)
Backup Mode
Board Position
Function
Load sharing
It is inserted in a common front slot of the SSM-256 frame. No corresponding back board is required.
When the VPU is used in the SSM-256 frame, the frame must be configured with the MTNB.
Media gateway TransCode Unit D (MTCD)
Load sharing
Echo Cancellation Unit (ECU)
Media gateway Echo Cancellation Unit (MECU)
Load sharing
The UG01MECU can be inserted in a common front slot of the SSM-256 frame. The UG02MECU can be inserted in a common front slot of the SSM-256 frame or the SSM-32 frame. No corresponding front board is required.
The ECU implements the EC function for voice signals.
3-16
Issue 02 (2008-05-07)
CLK
Table 3-6 Clock units Board Name Logical Board Clock Unit (CLK) Physical Board Media gateway Clock Unit (MCLK) Backup Mode Board Position Function
Master/ slave
It is inserted in back slot 0 or 1 of the SSM-256 frame or the SSM-32 frame. No corresponding front board is required.
The CLK provides clock signals for services. The external interfaces includes the clock input/ output interfaces.
3.2 Frame Cascading

This describes the cascading relationship of the SSM-256 self-cascading, SSM-32 selfcascading, and SSM-32 and SSM-256 mixed-cascading. 3.2.1 SSM-256 Self-Cascading This describes the SSM-256 self-cascading. 3.2.2 SSM-32 Self-Cascading This describes the SSM-32 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 the BLU.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 the BLU.C.
3.2.1 SSM-256 Self-Cascading

This describes the SSM-256 self-cascading. Both the main control frame and service frames can connect with the central switching frame through 1 FE + 2 GE + 3 TDM or 1 FE + 2 GE + 4 TDM cascading channels. The control frame connects 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 can perform the functions of the central switching frame. Insert the BLU/FLU cascading boards in the main control frame to implement the multi-frame cascading. Figure 3-7 shows the nine-frame self-cascading of SSM-256 frames.
Issue 02 (2008-05-07) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 3-17
Figure 3-7 SSM-256 nine-frame cascading

T N B N E T N E T T N B
1#
0#
B L U
B L U
B L U
B L U
B B L L U U
T N B
N E T
N E T
T N B
B L U
B L U
B L U
B L U
B L U
B L U
2#
3#
4#
5#
6#
7#
8#
N E T
N E T
4*8 K TDM
2*GE
1*FE
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 switching capability, the UG01NET provides 16 gigabit Ethernet (GE) packet switching capability, and the UG02NET provides 24 GE packet switching capability. In term of the cascading cable connection, the UG01NET uses interface FE1 to perform FE cascading, and the UG02NET uses interfaces FE1&FE2 and FE3&FE4 to perform FE cascading. The BLU is of three versions: UG01BLU, UG02BLU.A, and UG02BLU.C. The UG01BLU provides 3 x 8K time division multiplexing (TDM) cascading channels, and the UG02BLU provides 4 x 8K TDM cascading channels. The UG02BLU.A uses interface FE0 to perform FE cascading, and the UG02BLU.C uses FE1&FE2 or FE3&FE4 to perform FE cascading, which is the difference between the UG02BLU.A and UG02BLU.C. For details about boards, refer to 3.1.4 Introduction to Boards.
3.2.2 SSM-32 Self-Cascading

This describes the SSM-32 self-cascading.
l
The TNC in the main control frame is the UG02TNC providing two time division multiplexing (TDM) channels or the UG01TNC. The TNC in the service frame is the UG02TNC providing one TDM cascading channel or the UG01TNC. In the case of SSM-32 self-cascading, up to three frames can be cascaded. The central switching frame and main control frame are combined. Each service frame connects with the central switching frame through one fast Ethernet (FE) and one TDM cascading channel.
3-18
Issue 02 (2008-05-07)
Service frames must connect with the main control frame through the TDM cascading optical interface 0 on its TNC. TDM cascading optical interfaces 0 and 1 of the central switching frame or main control frame 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 interface 3 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 1 to 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
1# N L U N L U TNC TNC N L U N L U
2#
N L U
N L U
TNC
TNC
TNC 3#
TNC
N L U
N L U
1*8KTDM
1*GE
1*FE

l
2#: service frame
3#: service frame
The TNC in the main control frame is the UG02TNC providing four time division multiplexing (TDM) channels. The TNC in the service frame is the UG02TNC providing two TDM cascading channels. The UMG8900 supports up to three frames in SSM-32 self-cascading. The central switching frame and the main control frame are integrated. The UMG8900 provides four TDM cascading optical interfaces. The service frame connects to the main control frame through 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 cascading optical interfaces 0 and 1 on the TNC. The TNC provides two TDM cascading optical interfaces. Cascading optical interfaces 0 and 1 on the TNC in the central switching and main control integrated frame connect to TDM cascading optical interfaces 0 and 1 on the TNC in service frame 1. For service frame 1, refer to 2# in Figure 3-9. Cascading optical interfaces 2 and 3 on the TNC in the central switching and main control integrated frame connect to TDM cascading optical interfaces 0 and 1 on the TNC in service frame 2. For service frame 2, refer to 3# in Figure 3-9.
Issue 02 (2008-05-07)
3-19
The TNC provides four FE interfaces. FE interfaces 1 and 2 connect to FE interfaces 3 on the 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 1 to 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 1# TNC
N L U
N L U
N L U
N L U
2#
N L U
N L U
TNC
TNC
TNC 3#
TNC N L U N L U
1*8KTDM
1*GE
1*FE
2#: service frame
3#: service frame
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 the BLU.A. SSM-256 and SSM-32 frames support mixed cascading. That is, an SSM-256 central switching frame, served by a dedicated frame or the main control frame, can cascade with SSM-256 or SSM-32 frames. Thus, two mixed networking modes with different capacities can be adopted to satisfy actual needs. Each TNB or BLU in the SSM-256 central switching frame can cascade with one SSM-256 frame or four SSM-32 frames. Thus, the number of service frames that can be attached is n x SSM-256 + (7 - n) x 4 x SSM-32, where n refers to the number of SSM-256 frames except the central switching frame. When only SSM-32 frames are attached, up to 28 service frames can be cascaded.
The cascading of the SSM-256 central switching frame and SSM-256 service frames is described in 3.2.1 SSM-256 Self-Cascading. Thus, only the cascading of the SSM-256 central switching frame 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 is cascaded with the SSM-32 frame in two modes:
l l
TNB and NET used BLU used
TNB and NET Used

l
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 control frame and three SSM-32 service frames. Each SSM-32 service frame connects with the central switching frame through one fast Ethernet (FE) and one time division multiplexing (TDM) cascading channel. SSM-32 service frames must connect with the central switching frame through TDM cascading optical port 0 on the TNC. Figure 3-10 shows the mixed cascading of one SSM-256 frame and four SSM-32 frames through the TNB.
Issue 02 (2008-05-07)
3-21
Figure 3-10 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the TNB
0# T N B N E T N E T T N B
1#
N L U
N L U
TNC
TNC
TNC 2#
TNC
TNC 3#
TNC
TNC 4#
TNC
1*8KTDM
1*GE
1*FE
In this mode, the main control frame and the central switching frame are cascaded through the TNB to implement the TDM service cascading. The cascading of the control plane is implemented through the FE cascading interface of the NET. For the cascading of the GE plane, only one service frame is cascaded. Connect the optical interface on the NLU of the service frame to the GE interfaces of the master and slave NETs to implement the GE cascading. The NLU can be configured in slots 4 and 5 or slots 10 and 11 of the SSM-32 service frame. On the FE plane, main control frame 1 connects to the FE interface on the NET in central switching frame 0 through the FE3 interface on the TNC. Service frames 2, 3, and 4 respectively connect to the FE2, FE1, and FE0 interface in main control frame 1 through the FE3 interfaces. Main control frame 1 can be considered as a level-2 cascading frame.

l
If the TNC 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 main control frame 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 central switching 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 frames through the TNB. Figure 3-11 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the TNB
T N B N E T N E T T N B
0#
1#
N L U
N L U
TNC
TNC
TNC 2#
TNC
1*8KTDM
1*GE
1*FE
2#: service frame
NOTE
The cascading on the FE and GE planes is the same as the cascading of four SSM-32 frames through the TNB.
l
If the TNC in the SSM-32 frame provides four TDM cascading optical interfaces, the SSM-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 3 on the TNB in the SSM-256 central switching frame through TDM cascading optical interfaces 0, 1, 2, and 3 on the TNC. Figure 3-12 shows the mixed cascading of one SSM-256 frame and one SSM-32 frame through the TNB.
Issue 02 (2008-05-07)
3-23
Figure 3-12 Mixed cascading of one SSM-256 frame and one SSM-32 frame through the TNB
1#
N L U
N L U
TNC
TNC
1*8KTDM
1*GE
1*FE
NOTE
BLU Used
l
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, the SSM-256 frame can cascade with four SSM-32 frames, that is, one SSM-32 main control frame and three SSM-32 service frames. The SSM-256 central switching frame can be cascaded with four SSM-32 frames through the BLU. Figure 3-13 shows the mixed cascading of one SSM-256 frame and four SSM-32 frames through the BLU.
3-24
Issue 02 (2008-05-07)
Figure 3-13 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the BLU
0# T N B N E T N E T T N B BLUBLU
1#
N L U
N L U
TNC
TNC
TNC 2#
TNC
TNC 3#
TNC
TNC 4#
TNC
1*8KTDM
1*GE
1*FE
In this mode, one FE cascading interface of the MBLU in the central switching frame is cascaded with one FE cascading interface of the MTNC in one SSM-32 service frame, and the other three FE interfaces of the MBLU in the central switching frame are cascaded with the other three SSM-32 service frames to implement the four-frame FE cascading. The four TDM cascading interfaces of the MBLU in the central switching frame are cascaded with the TDM cascading interfaces of the four SSM-32 service frames to implement the fourframe TDM cascading. The GE optical interfaces on the master and slave MBLUs are cascaded with the optical interface on the MNLU in one SSM-32 frame to implement the GE cascading of one service frame. The MNLU in the service frame can be only inserted in slots 4 and 5, or slots 10 and 11.
l
If the TNC 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 main control frame and one SSM-32 service frame. On the TDM plane, the first SSM-32 frame, main control frame, connects to optical interfaces 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 the BLU 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 through the BLU.
l
If the TNC 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 the SSM-256 central switching frame through TDM cascading optical interfaces 0, 1, 2, and 3 on the TNC. Refer to Figure 3-12.
NOTE
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 the BLU.C. SSM-256 and SSM-32 frames support mixed cascading. That is, an SSM-256 central switching frame, served by a dedicated frame or the main control frame, can cascade with SSM-256 or SSM-32 frames. Thus, two mixed networking modes with different capacities can be adopted to satisfy actual needs. Each TNB or BLU in the SSM-256 central switching frame can cascade with one SSM-256 frame or four SSM-32 frames. Thus, the number of service frames that can be attached is n x SSM-256 + (7 - n) x 4 x SSM-32, where n refers to the number of SSM-256 frames except the central switching frame. When only SSM-32 frames are attached, up to 28 service frames can be cascaded. When the UG02NET and the BLU.C are configured in the SSM-256 frame, the SSM-256 frame can be cascaded with the SSM-32 frame in the following modes:
l l l l
TNB used and GE cascading not supported TNB used and GE cascading supported BLU used and GE cascading not supported BLU used and GE cascading supported
TNB and NET Used

l
The GE cascading is not 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 four SSM-32 frames, that is, one SSM-32 main control frame and three SSM-32 service frames.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-05-07)
3-26
Figure 3-14 shows the mixed cascading of one SSM-256 frame and four SSM-32 frames through the TNB without gigabit Ethernet (GE) cascading. Figure 3-14 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the TNB (without GE cascading)
1#
TNC
TNC
TNC 2#
TNC
TNC 3#
TNC
TNC 4#
TNC
1*8KTDM
1*FE
In this mode, the SSM-256 frame and SSM-32 frames are cascaded through the TNB and TNC to implement the time division multiplexing (TDM) cascading; and they are cascaded through the fast Ethernet (FE) cascading interface of the UG02NET to implement the fast Ethernet (FE) cascading. The TNB provides four TDM cascading optical interfaces, and they can be cascaded with four SSM-32 frames. For the cascading on the control plane, the FE1 and FE2 interfaces on the UG02NET are connected to the FE3 interfaces in main control frame 1 and service frame 2, and the FE3 and FE4 interfaces on the UG02NET are connected to the FE3 interfaces in service frames 3 and 4.
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 main control frame and one SSM-32 service frame. Figure 3-15 shows the mixed cascading of one SSM-256 frame and two SSM-32 frames through the TNB. Figure 3-15 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the TNB (without GE cascading)
1#
TNC
TNC
TNC 2#
TNC
1*8KTDM
1*FE
2#: service frame
The SSM-256 frame and the SSM-32 frames are cascaded through the TNB and the TNC to implement the TDM service cascading and cascaded through the FE cascading interface on the UG02NET to implement the cascading on the control plane. The TNB supports four TDM cascading optical interfaces and can cascade with two SSM-32 frames. The cascading on the control plane is the same as the cascading with four 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 frame through the TNB.
3-28
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)
1#
TNC
TNC
1*8KTDM
1*FE
The SSM-256 frame and the SSM-32 frames are cascaded through the TNB and the TNC to implement the TDM service cascading and cascaded through the FE cascading interface on the UG02NET to implement the cascading on the control plane. The TNB supports four TDM cascading optical interfaces and can cascade with one SSM-32 frame. The cascading on the control plane is the same as the cascading with four 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, one SSM-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 frames through the TNB with GE cascading.
Issue 02 (2008-05-07)
3-29
Figure 3-17 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the TNB (with GE cascading)
1#
N L U
N L U
TNC
TNC
2#
TNC
TNC
N L U
N L U
1*8KTDM
1*GE
1*FE
2#: service frame
In this mode, the GE cascading is supported, and one SSM-256 frame can be cascaded with up to two SSM-32 frames. The cascading of the TDM service is implemented through the TNB and TNC, and the cascading of the control plane and packet plane is implemented through the FE cascading interfaces and GE cascading interfaces on the UG02NET. The TNB provides four TDM cascading optical interfaces, and two of them are cascaded with two SSM-32 frames. The FE cascading interfaces on the UG02NET are cascaded with 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 optical interfaces of the NLUs in two SSM-32 frames to implement the cascading of the GE plane. 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 main control frame and one SSM-32 service frame. On the TDM plane, the first SSM-32 frame, main control frame, connects to optical interfaces 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 the BLU through TDM optical interfaces 0 and 1 on the UG02TNC. Refer to Figure 3-15.
NOTE
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.
3-30
The SSM-32 frame connects to optical interfaces 0, 1, 2, and 3 on the BLU in the SSM-256 central switching frame through TDM cascading optical interfaces 0, 1, 2, and 3 on the UG02TNC. Refer to Figure 3-16.
NOTE
BLU Used
l
The GE cascading is not 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 four SSM-32 frames, that is, one SSM-32 main control frame and three SSM-32 service frames. The SSM-256 central switching frame can cascade with the SSM-32 frame through the UG02BLU.C. If the GE cascading is not supported, the SSM-256 central switching frame can cascade with four SSM-32 frames through the BLU. Refer to Figure 3-18.
Issue 02 (2008-05-07)
3-31
Figure 3-18 Mixed cascading of one SSM-256 frame and four SSM-32 frames through the BLU (without GE cascading)
0# T N B N E T N E T T N B BLUBLU
1#
TNC
TNC
2#
TNC
TNC
3#
TNC
TNC
4#
TNC
TNC
1*8KTDM
0#: central switching frame 1#: main control frame
1*FE
In this mode, the SSM-256 frame and SSM-32 frames are cascaded through the BLU and TNC to implement the TDM cascading; they are cascaded through the FE interfaces on the BLUs to implement the FE cascading. The BLU provides four TDM cascading optical interfaces, and they can be cascaded with four SSM-32 frames. The FE cascading interfaces on the UG02BLU.C are cascaded with FE3 interfaces on the TNCs in four SSM-32 frames through expansion.
3-32
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 main control frame and one SSM-32 service frame. On the TDM plane, the first SSM-32 frame, main control frame, connects to optical interfaces 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 the BLU through TDM optical interfaces 0 and 1 on the UG02TNC. Refer to Figure 3-15.
NOTE
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 the SSM-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, one SSM-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 is supported, the SSM-256 frame can cascaed with two SSM-32 frames through the UG02BLU.C. Refer to Figure 3-19.
Issue 02 (2008-05-07)
3-33
Figure 3-19 Mixed cascading of one SSM-256 frame and two SSM-32 frames through the BLU (with GE cascading)
0#
T N B
N E T
N E T
T N B
BLUBLU
1#
N L U
N L U
TNC
TNC
TNC 2#
TNC
N L U
N L U
1*8KTDM
1*GE
1*FE
2#: service frame
In this mode, the GE cascading is supported, and one SSM-256 frame can be cascaded with up to two SSM-32 frames. The cascading of the TDM service is implemented through the BLU and TNC, and the cascading of the control plane and packet plane is implemented through the FE cascading interfaces and GE cascading interfaces on the BLU. The BLU provides four TDM cascading optical interfaces, and two of them are cascaded with two SSM-32 frames. The FE cascading interfaces on the BLU are cascaded with FE3 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 of the NLUs in two SSM-32 frames to implement the cascading of the GE plane. 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. The UG02NET and the BLU.C support the original configuration mode, and they can replace 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 main control frame and one SSM-32 service frame. On the TDM plane, the first SSM-32 frame, main control frame, connects to optical interfaces 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 the BLU through TDM optical interfaces 0 and 1 on the UG02TNC. Refer to Figure 3-15.
3-34
Issue 02 (2008-05-07)

NOTE
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 the SSM-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 Forwarding

This describes the concept and configuration principles of centralized forwarding. The UMG8900 in complete configuration has at least four logical interfaces based on Internet Protocol (IP) bearer. The four logical interfaces are:
l l l l
Operation, administration and maintenance (OAM) interface H.248 interface SIGTRAN interface Bearer interface
If the four interfaces use their own physical interfaces and IP addresses, complex networking and waste of IP address resources are caused. The UMG8900 supports centralized forwarding of the following messages through an IP interface:
l l l
Operation and maintenance center (OMC) messages H.248 messages SIGTRAN messages
In this way, IP interfaces and addresses are saved. Installation and configuration are also simplified. In case of multiple-frame networking, the H.248 and signaling transport (SIGTRAN) interfaces must 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 Logical Position Physical Position in the SSM-256 OMC interface numbered 0 on the NET Physical Position in the SSM-32 OMC interface numbered 0 on the TNC Mc interface numbered 1 on the TNC
3-35
OMU/MPU
Issue 02 (2008-05-07)
Logical Position PPU SPF HRB
Physical Position in the SSM-256 FE0 port numbered 0 on the PPU MIR interface numbered 0 on the NET in the same frame FE ports numbered 0 to 7 on the E8T GE port numbered 0 on the E1G
Physical Position in the SSM-32 FE0 port numbered 0 on the PPU The SPF in frame SSM-32 does not provide interfaces. FE ports numbered 0 to 7 on the E8T GE 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 the UMG8900 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 l l
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.248 and SIGTRAN interfaces at the same time, if the HRB is not configured. The IP address of the OAM interface is set as the slave one, and that of the H.248 and SIGTRAN interfaces is set as the master one. In this case, if the H.248 and SIGTRAN messages are transmitted through the same protocol, 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-256 frame. Table 3-8 Usage rules of IP interfaces when the HRB is configured Logical Position Physical Position and Function When the E8T Is Configured OMC interface on the back NET, which can serve as an OAM interface The first FE port on the back E8T, which can serve as an H.248 or SIGTRAN interface Physical Position and Function When Only the E1G Is Configured OMC interface on the back NET, which can serve as an OAM interface GE port on the back E1G, which can serve as an H.248 or SIGTRAN interface through the master IP address
OMU
HRB
3-36
Issue 02 (2008-05-07)
Logical Position
Physical Position and Function When the E8T Is Configured Other FE ports on the back E8T, which can serve as an IP service bearer interface
Physical Position and Function When Only the E1G Is Configured GE port on the back E1G, which can serve as an IP service bearer interface through the slave IP address
HRB
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 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 centralized forwarding function of the HRB.
Single SSM-32 networking falls into the following cases:

l l l
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 the Mc interface on 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-32 networking Logical Position OMU OMU Physical Position and Function OMC interface on the TNC, which can serve as an OAM interface Mc interface on the back TNC, which can serve as an H.248 or SIGTRAN interface
As shown in Table 3-9, the Mc interface on the OMU provides H.248 and SIGTRAN interfaces at the same time. In this case, if the same transmission protocol is used for H.248 and SIGTRAN messages, different protocol port numbers must be used. If the HRB is configured for single SSM-32 networking, the usage rules are similar to those of the SSM-256 frame. See Table 3-10.
Table 3-10 Usage rules for IP interfaces when the HRB is configured for the single SSM-32 networking Logical Position OMU Physical Position and Function When the E8T Is Configured OMC interface on the back TNC, which can also serve as an OAM interface The first FE port on the back E8T, which can serve as an H.248 or SIGTRAN interface Other FE ports on the back E8T, which can serve as an IP service bearer interface Physical Position and Function When Only the E1G Is Configured OMC interface on the back TNC, which can serve as an OAM interface GE port on the back E1G, which can serve as an H.248 or SIGTRAN interface through the master IP address GE port on the back E1G, which can serve as an IP service bearer interface through the slave IP address
HRB
HRB
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 provide H.248 and SIGTRAN interfaces at the same time. In this case, if the same transmission protocol is 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 centralized forwarding mode unless otherwise noted. The configuration principles are different for different cascading modes. The UMG8900 supports the following cascading modes:
l l l
SSM-256 self cascading SSM-32 self cascading 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 OMU in the main control frame Physical Position and Function OMC interface on the back NET, which can serve as an OAM OMC interface on the back NET, which can serve as an H.248 or SIGTRAN interface
Issue 02 (2008-05-07)
3-38
Logical Position MPU in the central switching frame HRB
Physical Position and Function OMC interface on the back NET, which can serve as an H. 248 or SIGTRAN interface Interface of the back E8T or E1G, which can serve as an IP service bearer interface
As shown in Table 3-11, the OMC interface on the MPU in the central switching frame needs to provide both H.248 and SIGTRAN interfaces at the same time. In this case, if the same transmission protocol is used for H.248 and SIGTRAN messages, different protocol port numbers 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 OMB in the main control frame MPU in the first service frame HRB Physical position and function OMC interface on the back TNC, which can serve as an OAM interface OMC interface on the back TNC, which can serve as an H. 248 or SIGTRAN interface interface of the back E8T or E1G, which can serve as an IP service bearer interface
As shown in Table 3-12, the Mc interface on the MPU in the first service frame needs to provide both H.248 and SIGTRAN interfaces at the same time. In this case, if the same transmission protocol is used for H.248 and SIGTRAN messages, different protocol port numbers must be adopted. Table 3-13 shows the usage rules for IP interfaces in case of SSM-256 and SSM-32 mixed cascading. Table 3-13 Usage rules for IP interfaces in case of SSM-256 and SSM-32 mixed cascading Logical Position OMU in the main control frame MPU in the central switching frame HRB Physical Position and Function OMC interface on the back TNC, which can serve as an OAM interface OMC interface of the back NET, which can serve as an H. 248 interface or SIGTRAN interface interface of the back E8T or E1G, which can serve as an IP service bearer interface
As shown in Table 3-13, the OMC interface on the MPU in the central switching frame needs to provide both H.248 and SIGTRAN interfaces at the same time. In this case, if the same
transmission protocol is used for H.248 and SIGTRAN messages, different protocol port numbers must be adopted.
3.4 Dual Homing

This describes the concept and configuration principles of dual homing. Dual homing is a disaster tolerance plan, which enables remote disaster recovery for the media gateway (MGC) system. For the two dual homing MGCs, when one MGC fails to provide services, the other MGC takes over its services. When the original master MGC recovers, the services are switched back to the original MGC. Figure 3-20 shows the dual homing plan. Figure 3-20 Dual homing
MGC(Master) BICC/SIP H.248 SIGTRAN MGC(Slave)
H.248
UMG8900
As shown in Figure 3-20, the UMG8900 is under the control of the master MGC in normal cases. 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 and SIGTRAN links.
NOTE
You need to configure data of dual homing on both the UMG8900 and the MGC.
3.5 SCTP Multi-Homing

This 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 an SCTP link to provide a reliable end-to-end multi-path transmission mechanism and enhance the system reliability. If an SCTP link fails, media gateway (MGW) control messages and signaling messages are switched to other links. Two local IP addresses and two peer IP addresses can be configured on the UMG8900. Refer to Figure 3-21.
3-40
Issue 02 (2008-05-07)
Figure 3-21 SCTP multi-homing

MGC
IP3
IP4 H.248/SIGTRAN
IP1
IP2
UMG8900
In Figure 3-21, the UMG8900 supports two modes: two paths and four paths. The two paths are 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 IP 1 to IP 4. After receiving a link establishment request, the SCTP client starts establishing a link to the SCTP server by carrying the local IP address list. The SCTP client selects peer IP addresses first and then local IP addresses in turn, until the link is established. If a link fails, services on H.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 forwarding interface on the OMU/OMB/MPU. Therefore, the centralized forwarding module must work in load-sharing mode, and the master and slave boards must be capable of centralized forwarding.
3.6 Virtual Media Gateway

This describes the concept and configuration principles of the virtual media gateway (VMGW). The VMGW function divides a physical MGW into multiple different logical MGWs. Each VMGW 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 networking and carriers. The system can allocate bearer resources of the MGW to different virtual MGWs in exclusive or resource sharing mode to improve the flexibility of the device. The VMGW function can reduce the network construction cost of carriers and provide the operating of virtual carriers.
3.7 Interface Protection

This 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 Table 3-14.
Issue 02 (2008-05-07)
3-41
Table 3-14 Interface protection types supported by different interfaces Logical Interface Type IP interface Physical Interface Type FE interface GE interface SDH/ SONET interface SDH/ SONET interface Non 1+1 APS Protection Auto support Support Non 1:N APS Protection 1+1 APS Protection Support 1:N APS Protection Support
NOTE
l l l l
The gigabit Ethernet (GE) interface supports only non 1+1 APS protection. The FE interface automatically support non 1+1 APS protection, and the FE interface does not support the interface protection function. The IP interface does not support the non 1:N APS protection or 1:N APS protection. 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 supported interface 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 group has 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 the master interface becomes DOWN, services on it are switched to the slave interface. This mode can be automatically supported by hardware for some interfaces, and is not required to be configured. This mode applies when the FE/GE interface of the UMG8900 is used to interconnect with the router. Non 1:N APS protection: is also called 1:N breakthrough protection. One protection group has N+1 interfaces, and services are switched based on the UP/DOWN status of the interface. In the normal state, N interfaces are working. When one interface becomes DOWN, 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. 1+1 APS protection: One protection group has one work channel and one protection channel. The switchover is performed based on the APS protocol. In the normal state, the work channel is working. If an APS switchover event is detected by the work channel, the services are switched to the protection channel. In this mode, the interconnected device must also support the APS protocol. This mode applies when the SDH/SONET interface is used to interconnected with the SDH device. 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 work channels are working. If an APS switchover event is detected by one work channel, the services are switched to the protection channel. The APS protection requires the interconnected 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 principles of 1+1 backup and 1:N backup are described as follows.
Figure 3-22 shows SDH/SONET interface protection in 1+1 backup mode. Figure 3-22 1+1 backup
A
Work channel Protection channel
Work channel Protection channel
In 1+1 backup mode, each work channel has a corresponding protection channel. The sender sends signals through both work and protection channels, and the receiver receives the signals with 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, unidirectional non-recover, unidirectional recover, bidirectional non-recover, and bidirectional recover.
l
Unidirectional means the switchover is initiated by one end only, according to the line quality, without negotiation with the peer end. Bidirectional means the switchover starts at the two ends simultaneously after negotiation between them. Recover means the original work channel will be enabled again when recovered from failed state. Non-recover means the protection channel still work even when the original work channel is recovered.
In unidirectional 1+1 backup mode, the receiver chooses to receive signals through work or protection channels according to line quality. In bidirectional 1+1 backup mode, based on the automatic protect switch (APS) protocol, the two ends exchange K bytes that carry status information of links between the receiver and sender, and decide whether to enable channel switch. In this case, K bytes are transported through protection channels. Figure 3-23 shows the work mode of 1:N linear multiplex section protection.
Issue 02 (2008-05-07)
3-43
Figure 3-23 1:N linear multiplex section protection

A 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) Birdge Selector Selector Birdge B
Different from 1+1 backup mode, multiple work channels share one dedicated protection channel in 1:N backup mode. In the normal state, work channels carry signals. In the event of work channels 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 APS protocol, and K bytes are transported through protection channels.
3.8 UAM Background Information

This 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 services digital network (ISDN) subscribers, the UAM must be configured. In this case, the UMG8900 consists of the UAM and the service switching module (SSM). Figure 3-24 shows the networking application.
3-44
Issue 02 (2008-05-07)
Figure 3-24 UMG8900 connecting subscribers directly

MGC
UMG8900 SSM
Main frame
Direct frame
RSA main frame
Subframe UAM
RSA subframe
PSTN/ISDN User
3.8.1 UA Frame Types This describes the types of user access (UA) frames. 3.8.2 UA Frame Modes This describes the modes that the user access (UA) frames can be configured in. 3.8.3 Conversion Between the TID and the Subscriber Line Port This describes the conversion between the termination identifier (TID) and the subscriber line port. 3.8.4 Method to Number E1 Interfaces on the PV8/RSU by Mapping Them to E1 Cables on the SSM Side This describes the method to number E1 interfaces on the PV8/RSU by mapping them to E1 cables 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 SSM Side This describes the method to number E1 interfaces on the RSP by mapping them to E1 cables on the service switching module (SSM) side.
3.8.1 UA Frame Types

This describes the types of user access (UA) frames.
UA Frame Types
The frame type determines the frame dimensions, supported boards, and slot positions. The user access module (UAM) supports frames such as RSP_10, RSP_12, RSP_14, RSP_15, RSP_19,
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 Table 3-15. Table 3-15 Mapping between UA frame types and backplanes No. 1 2 Frame Type UAFM UAFS Backplane HUBE HUBF Remarks For the two frame types, the backplane model is often invisible. The two types of frames, however, differ from other types of frames in that the cabling area is at the top rather than at the back. The E1 interface of the UAFM frame is identified as PV8 E1, and the E1 interface of the UAFS frame is identified as RSP E1. The HABA_UP and HABA_DOWN frames share one backplane. The HABA_UP frame is on the upper half, and the HABA_DOWN is on the lower half. The HABB_UP and HABB_DOWN frames share one backplane. The HABB_UP frame is on the upper half, and the HABB_DOWN is on the lower half. The backplane models of these four types of frames are often invisible. The four types of frames, however, differ from other types of frames in that the cabling area is at the bottom rather than at the back. The HABD frame can provide up to 12 subscriber boards, the HABE frame can provide up to 14 subscriber boards, the HABF frame can provide up to 18 subscriber boards, and the HABL can provide up to 6 subscriber boards. -
3 4 5
UAM UAS HABA_UP
HUBM HUBS HABA
HABB_UP
HABB
7 8 9 10
HABD HABE HABF HABL
HABD HABE HABF HABL
11 12 13 14 15 16
RSP160B RSP_10 RSP_12 RSP_14 RSP_15 RSP_19
HLB HGB HFB HIB HDB HCB
3-46
Issue 02 (2008-05-07)
No. 17
Frame Type RSA_22/ RSA_26
Backplane RUB
Remarks The two types of RSA frames provide different numbers of slots. The RSA_22 frame provides 22 slots, and the RSA_26 frame provides 26 slots. The backplane of the two types of subscriber frames is the SLB. You can distinguish the two subscriber frames based on the number of slots on the ASL. The USR_16 frame provides 16 ASL slots, and the USR_19 frame provides 19 ASL slots. This type of frame adopts the front cabling mode. It provides three slots with one for the RSP and the other two for the subscriber boards.
18 19 20 21
RSB RSB_HK USR_16 USR_19
RSB RMB SLB SLB
22
RSP_60A
Frames such as the RSP_10 and the RSP_12 support two types of main control boards: PV8 and RSP. If the PV8 is installed, the subframe can be configured. If the RSP is installed, no subframe can 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 Modes

This describes the modes that the user access (UA) frames can be configured in.
UA Frame Modes
The 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 adding UA frames. Table 3-16 lists the five modes of the UA frames.
Issue 02 (2008-05-07)
3-47
Table 3-16 UA frame modes No. 1 Frame Mode Main frame Description The main frame connects directly with the SSM frame and can attach subframes. Its main control board is the PV8, PV4, RSU8, or RSU4. The frames that can be configured as main frames include the UAFM, UAM, HABA_UP, HABD, HABL, RSP_10, and RSP_12. 2 Subframe The subframe connects directly with a main frame and cannot attach subframes. The main control board in the subframe of a low-density UA frame is the RSP. No main control board is installed in the subframe of a high-density UA frame. The frames that can be configured as subframes include the UAFS, 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 and cannot attach subframes. Its main control board is the RSP or RSA. The main control board of the RSB and RSB_HK frames is the RSA. The frames that can be configured as direct frames include the UAFM, UAFS, UAM, UAS, RSP_10, RSP_12, RSP_14, RSP_15, RSP_19, RSP_60A, RSP_160B, RSB, and RSB_HK. 4 RSA main frame The RSA main frame connects directly with the SSM frame and can attach RSA subframes. Its main control board is the RSA. Only the RSA_22 and RSA_26 frames can be configured as the RSA main frame. 5 RSA subframe The RSA subframe connects directly with the RSA main frame and cannot attach subframe. Its main control board is the DRV. Only the USR_16 and USR_19 frames can be configured as the RSA subframe.
NOTE
As described previously, certain frames such as the RSP_10 and the RSP_12 can be configured as either main 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 Port
This describes the conversion between the termination identifier (TID) and the subscriber line port. 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.
The TID of each subscriber line maps a telephone number. These telephone numbers are operation resources, and are allocated and controlled by the media gateway controller (MGC). The UMG8900 provides the following man-machine language (MML) commands for the conversion:
l l
LST UAPOS to query information about the subscriber line port based on a TID 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 TID of the subscriber line port must be specified. You can run LST UATID on the UMG8900 to query the TID of the subscriber line port.
%%LST UATID:;%% RETCODE = 0 accomplished UA terminal TID --------------Frame No. Slot No. TID(Hex) (Hex) TID_low23bit(Dec)
TID(Dec)
TID_low23bit
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 Termination ID in ADD VSBR or Start MG termination ID in ADB VSBR of the MGC to the TID in TID_low23bit(Dec). Do not fill in 0 on the left of the query result. For example, for a query result 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 subscriber line 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 Mapping Them to E1 Cables on the SSM Side
This describes the method to number E1 interfaces on the PV8/RSU by mapping them to E1 cables on the service switching module (SSM) side. 1. Signaling between the user access module (UAM) and the SSM is transmitted through timeslot 16 on E1 interface 1. Thus, you must confirm the pair of E1 cables on the SSM
Issue 02 (2008-05-07)
side that maps E1 interface 1 on the PV8/RSU. The PV8/RSU can run properly only after you run ADD UACFG to set the parameters including First trunk board No. and First port No. correctly. The procedure for confirming the mapping is as follows. Disconnect the connection between the digital distribution frame (DDF) on the SSM side and the UAM, loop each pair of E1 cables on the UAM side, and check the state of E1S indicator on the panel of the PV8/RSU. The E1 cable pair that lightens the E1S indicator maps E1 interface 1 on the PV8/RSU. Write down the board No. and the port No. of the E32 connected with this E1 pair on the SSM side. 2. After confirming the pair of E1 cables that maps E1 interface 1 on the PV8/RSU, run ADD UACFG 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 the port No. of the E32 noted in 1. Do not set the parameters Second trunk board No. to Eighth trunk board No.. Then, you can see from Device Panel on the local maintenance terminal (LMT) that the PV8/RSU runs properly. 3. After confirming that the PV8/RSU runs properly, confirm the mapping between other E1 cables 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 up by the front view. Bits 1, 2, and 3 identify the E1 cable that the E1S indicator indicates the status 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 interface 1 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 tests on E1 cable pairs on the SSM side based on the method described in 1. Check the status of E1S indicator to confirm the E1 cable pairs related to each of E1 interfaces 2 to 8 on the PV8/RSU. Write down the board Nos. and the port Nos. of the E32s connected with each E1 cable pair. 4. 5. Run RMV UACFG to delete the trunk connections between the SSM and the UAM. 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 E32s and First port No. through Eighth port No. to the port Nos. of the E32s noted in 1 and 3. Then, you can see from Device Panel that the PV8/RSU runs properly. By now, configuring trunk connections between the SSM and the UAM is complete.
3-50
Issue 02 (2008-05-07)
3.8.5 Method to Number E1 Interfaces on the RSP by Mapping Them to E1 Cables on the SSM Side
This describes the method to number E1 interfaces on the RSP by mapping them to E1 cables on the service switching module (SSM) side. 1. Indicators E11 to E14 on the panel of the RSP respectively indicate the status of E1 interfaces 1 to 4. On the digital distribution frame (DDF) on the SSM side, disconnect the connection to the user access module (UAM), perform loopback tests on E1 cable pairs to the UAM side one by one, and check whether indicators E11 to E14 on the panel of the RSP are on. If an indicator is on after loopback, the related E1 cable pair maps the corresponding E1 interface on the RSP. Write down the board Nos. and the port Nos. of the E32s connected with E1 cable pairs on the SSM side. 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 E32s and 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 trunk connections between the RSP and the SSM is complete.
2.
3.9 Route Backup

This 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 this master IP address as their source IP address can be sent through the interface where the slave IP address is located. These IP packets include service packets and control packets. Route backup in different networking is described as follows. As shown in Figure 3-25, supposing IP addresses of IP0 and IP1 are in different network segments and route backup is configured, when the master link is normal, packets with IP0 as the source IP address are sent by the master interface IP0, and the master IP0 interface and backup interface IP1 can receive the packets with IP0 as the destination address; when the master links are faulty, packets with IP0 as the source IP address are sent by the backup interface, and those 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
HRB IP0 Master IP2 GW0 GW1
IP1
Slave
IP3
The master link is normal.
HRB
IP0 IP1
Master Slave
IP2 IP3
GW0 GW1
The master link is faulty.
Issue 02 (2008-05-07)
3-51
When IP0 and IP1 are in the same network segment, there are two networking modes. Refer to Figure 3-26. In this networking mode, normally, packets with IP0 as the source IP address are sent 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 address corresponding to the main IP address of the UMG8900, and then decides to send the IP packets with IP0 as the destination address to the master interface or the backup interface. When the master and slave interfaces are in the same LAN, only the links between the UMG8900 and switch can be protected. Thus, the master and slave interfaces are often configured in different LANs. Figure 3-26 Route backup of IP addresses in the same network segment
HRB IP0 IP1 Master IP2 Slave IP3 LSW GW
The master and slave interfaces are in the same LAN. IP0 IP1 Master Slave IP2 IP3
HRB
GW0 GW1
The master and slave interfaces are not in the same LAN.
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. The master and slave IP addresses must be configured on different interfaces of the same HRB (that is, the master and slave HRBs with the same board No.), and belong to the same IP domain. 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 the master interface is located in. The route backup relationship of IP addresses is unidirectional. If you want to back up the route reversely, you must configure another backup relationship. It is recommended to configure route backup for all or none of the IP addresses of an interface.
Note that both the master IP interface and the slave IP interface support the virtual local area network (VLAN), or neither of them supports the VLAN. When both the master and slave IP interfaces support the VLAN, VLAN IDs can be different. However, the interfaces of the peer device connected with these two IP interfaces must support the VLAN mixed mode. That is, the interfaces of the peer device can receive and send packets of two VLANs at the same time.
3-52
Issue 02 (2008-05-07)
4 General Planning of Examples
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 entire configuration example. Figure 4-1 Networking example
SPC: bbbbbb IP address: 192.168.0.1/24 H.248 SCTP Port No.: 3333 L2UA SCTP Port No.: 2000 MTP3-M3UA SCTP Port No.: 4000 IUA SCTP Port No.: 2010 V5UA SCTP Port No.: 2020 DNS server IP address: 10.1.200.1 IP network Router IP address: 10.1.1.254/24 MGW IP address: 10.1.1.200 NMS IP address: 100.10.1.1/24 PSTN switch TDM SPC: aaaaaa R2 PRA TDM UA PBX PBX user SPC: aaaaaa SPC: dddddd Master MGC Slave MGC SPC: bbbbbb IP address: 172.16.0.1/24 H248 SCTP Port No.: 2222 L2UA SCTP Port No.: 3000 MTP3-M3UA SCTP Port No.: 5000 IUA SCTP Port No.: 3010 V5UA SCTP Port No.: 3020
V5 access device
OMC interface in the main control frame IP address: 10.1.1.1 SPF(MIR) IP address: 10.1.1.2 PPU board IP address: 10.1.1.3 Mc interface IP address: 10.1.1.4 OMC interface in the central switching frame IP address: 10.1.1.5 OMC interface in the first service frame IP address: 10.1.1.6 E8T IP address: 10.1.1.10~10.1.1.14 E1G IP address: 10.1.1.50~10.1.1.51
SCTP port No. to the master MGC: 3333 SCTP port No. to the slave MGC: 2222 SCTP port No. to the master MGC(M2UA): 2000 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): 5000 SCTP port No. to the master MGC(V5UA): 2020 SCTP port No. to the slave MGC(V5UA):3020
Issue 02 (2008-05-07)
4-1
5 Configuring System Parameters
5
Prerequisite
l l
Configuring System Parameters
This describes how to configure the system parameters, including the system name, version load server information, local information, and environmental monitoring parameters.
Hardware installation is complete. Software installation is complete.
Data Planning
l
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. If not, "-" is filled in. Table 5-1 Data planning Parameter Name IP address of the version server User name of the version server Password of the version server System Node No. National signaling point code 1 Coding length Local signaling point index National signaling point code 2 Upper limit of the input voltage alarm (V) Lower limit of the input voltage alarm (V) UMG8900 <IP Address of Version Server> <User Name of Version Server> <Password of Version Server> <System Node No.> <National network code>_1 <National network structure> <OPC index> <National network code>_2 <Upper Limit of the Input Voltage Alarm (V)> <Lower Limit of the Input Voltage Alarm (V)>
Issue 02 (2008-05-07)
5-1
Parameter Name Upper limit of the environment temperature alarm (C) Lower limit of the environment temperature alarm (C) Upper limit of the environment temperature alarm (F) Lower limit of the environment temperature alarm (F) Cabinet No. Buzzer switch Frame No. Port No. of the environmental alarm chest Alarm ID Digital port alarm voltage Alarm name Alarm level Net management type
UMG8900 <Upper Limit of the Environment Temperature Alarm (C)> <Lower Limit of the Environment Temperature Alarm (C)> <Upper Limit of the Environment Temperature Alarm (F)> <Lower Limit of the Environment Temperature Alarm (F)> <Cabinet No.> <Switch> <Frame No.> <Port No.> <Alarm ID> <Digital Port Alarm Voltage> <Alarm Name> <Alarm Level> <Net Management Type>
Table 5-2 lists the parameters output to other steps. Table 5-2 Output parameter Parameter Name Local signaling point code 1 Local signaling point code 2 Local signaling point index Data <National network code>_1 <National network code>_2 <OPC index>
NOTE
l l
If the local office provides one signaling point, local signaling point code 1 is provided. 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.
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 name followed 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 equipment UMG8900.
Step 2 Run SET OFI to configure the local information. Set National network valid to YES, First search 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 local information, if multiple signaling points are required, run ADD OFI to add the information of the original signaling point. The index of the local signaling points range from 1 to 15. The local signaling 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 distribution frame. 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=<Lower Limit 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 environmental alarm 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 environmental alarm chest. SET ENVALMPARA: ALMID=<Alarm ID>, ANM=<Alarm Name>, ALVL=<Alarm Level>, ASS=<Net Management Type>; ----End
Example
Example script
//Configure the system information. MOD SYSINFO: SYSN="ABUMG89001", FTPIP="user", FTPUN="UMG8900W";
Issue 02 (2008-05-07)
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;
Postrequisite
After configuring the system parameter, proceed with other configurations. Configuring System Time
5-4
Issue 02 (2008-05-07)
6 Configuring System Time
6
Prerequisite
l l
Configuring System Time
This describes how to configure the system time including how to set the time synchronization mode and how to manually set the time, time zone, Network Time Protocol (NTP) server, and daylight saving time (DST).
The hardware installation is complete. The software installation is complete.
Context
This contains the configuration and correction of the UMG8900 host time. Logs, alarms, performance and trace information contain time parameters. Correct time information helps you to specify the time when an error occurs. When starting, the UMG8900 obtains the current system time from the RTC (the hard clock that keeps timing on the battery power after the system shuts down). This time is not accurate. You can adjust it in the following three methods:
l
Setting the system time manually In this manner, the accuracy of time can only reach the scale of second and cannot meet higher requirements.
Adjusting time according to the global positioning system (GPS) reference source The 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.
Adjusting the time according to the NTP server through the NTP protocol
Configuration Procedures
In the preceding three methods, steps for configuring the system time are different. Refer to Figure 6-1.
Issue 02 (2008-05-07)
6-1
Figure 6-1 Steps for configuring the host time

Configure the system time
RTC
Configure the time synchronization mode? NTP
GPS
Configure the system time manually
Configure the time zone
Configure the time zone
Configure the NTP server
End
Data Planning
l
Table 6-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. If not, "-" is filled in. Table 6-1 Data planning Parameter Name Date Time Adjust value (s) Daylight saving time Time zone Start date mode Start month Start date Start week Start time End date mode End month End date UMG8900 <Date> <Time> <Adjust value(s)> <Daylight saving time> <Time zone> <Start date mod> <Start month> <Start date> <Start week> <Start time> <End date mode> <End month> <End date> Interconnected Device (NTP Server) -
6-2
Issue 02 (2008-05-07)
Parameter Name End week End time Time offset (minute) IP address of the NTP server Whether to authenticate the ID Authentication key ID Authentication key Version Prefer
UMG8900 <End week> <End time> <Time offset(minute)> The same as that of the peer device <Authentication> <Authentication key ID> <Authentication key> The same as that of the peer device <Prefer>
Interconnected Device (NTP Server) <NTP IP Address> <NTP Version> -
Procedure
Step 1 Run SET TIMESYC to set the synchronization mode of the local system time. The time synchronization 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 synchronize the 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 the NTP 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 expressed in hh&mm&ss. l Set Set Type to Set Time. SET TIME: ST=SETTIME, DATE=<Date>, TIME=<Time>, DST=<Daylight saving time>; 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;
Set Daylight saving time flag to YES. SET TZ: ZONET=<Time zone>, DST=YES, SM=<Start date mod>, SMONTH=<Start month>, SDAY=<Start date>, SWEEK=<Start week>, ST=<Start time>, EM=<End date 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
Example
Example 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;
Postrequisite
After configuring the system time, configure NMS data. Configuring NMS Data
6-4
Issue 02 (2008-05-07)
7 Configuring NMS Data
7
About This Chapter
Configuring NMS Data
This describes how to configure the interconnection data between the UMG8900 and the network management system (NMS), including the configurations of the NMS interface and Simple Network Management Protocol (SNMP). 7.1 Configuring the NMS Interface This describes how to configure the interface and route of the UMG8900 to the network management system (NMS). 7.2 Configuring SNMP This describes the Simple Network Management Protocol (SNMP) data of the UMG8900 to the network management system (NMS).
Issue 02 (2008-05-07)
7-1
7.1 Configuring the NMS Interface

This describes how to configure the interface and route of the UMG8900 to the network management system (NMS).
Prerequisite
l l
The system parameter and time information are correctly set. 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. The MPU interface: the OMC interface on the NET in an SSM-256 frame other than the main 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 frame are configured with IP addresses for software loading. Thus, if the OMU interface is used to receive and send NMS packets, no more configurations are needed.
Table 7-1 lists the parameter configuration for the three types of interfaces when ADD IPADDR is used to set the IP address. Table 7-1 Parameter configuration for the three types of interfaces Parameter Board type Board No. Interface type Interface No. OMU Interface OMU 0 ETH 0 MPU Interface MPU The board No. of the MPU in frame 0 is 1. The Nos. of MPU boards in other frames are the same as the Nos. of the frames they are located. ETH 0
NOTE
Run MOD IPIF to modify the auto negotiation parameters of the OMC interface such as the rate and duplex mode.
Index mapping of the configuration command parameters

Figure 7-1 shows the index mapping of the configuration command parameters.
Figure 7-1 Index Mapping of Configuration Command Parameters

ADD IPADDR BT BN IPADDR MASK ADD ROUTE BT BN DSTIP DSTMASK ADD IPFWD BT BN IPADDR
Data Planning
l
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 Board type Board No. Data <Board type> <Board No.> Input Source 8 Configuring Frames and Boards 8 Configuring Frames and Boards
Table 7-3 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. Table 7-3 Data planning Parameter Name IP address of the NMS interface IP address and mask of the NMS interface Master or slave flag In VLAN UMG8900 <Interface IP address> <Interface IP address mask> <Master or slave flag> <In VLAN> Interconnected Device 1 (NMS) The same as that of the peer device The same as that of the peer device Interconnected Device 2 (Router) -
7-3
Issue 02 (2008-05-07)
Parameter Name IP address of the NMS IP address and mask of the NMS IP address of the router directly connected with the UMG8900 Protocol type
UMG8900 The same as that of the peer device The same as that of the peer device The same as that of the peer device
Interconnected Device 1 (NMS) <Destination address> <Destination address mask> -
Interconnected Device 2 (Router) <Next hop address>
The same as that of the peer device
<Protocol type>
Procedure
Step 1 Run ADD IPADDR to add the IP address to the NMS interface. Set Interface type to ETH because 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=<Master or 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 hop address>; 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. Run ADD 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
Example
Networking diagram Figure 7-2 shows the typical networking.
7-4
Issue 02 (2008-05-07)
Figure 7-2 Networking diagram

IP:100.10.1.1/24 NMS server UMG8900 IP10.1.1.254/24 NMS client
LAN
IP10.1.1.1/24 Local maintenance LMT
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";
Postrequisite
After configuring the NMS interface, configure the Simple Network Management Protocol (SNMP) data. 7.2 Configuring SNMP
7.2 Configuring SNMP

This describes the Simple Network Management Protocol (SNMP) data of the UMG8900 to the network management system (NMS).
Prerequisite
l l
The hardware data is correctly set. The NMS interface data is correctly set.
Simple Network Management Protocol (SNMP), a proven industry standard, is widely used in networks. Its purpose is to guarantee the transmission of management information between any two points. In this case, the network administrator can retrieve information at any node on the network to achieve:
l
Fault diagnosis
Issue 02 (2008-05-07)

l l
Capacity planning Report generation
SNMP adopts a polling mechanism and offers a fundamental functional set. In addition, SNMP only requires the unacknowledged transport layer protocol UDP; so it is widely supported by a variety of products. Structurally, SNMP can be divided into NMS and Agent. In SNMPv3, NMS and Agent are uniformly called SNMP entity. Network management station (NMS) is a workstation running the 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. 2. 3. 4. 5. 6. The NMS sends a serial packet to the Agent. The Agent receives the serial packet through the UDP port 161. The Agent decodes, authenticates, and analyzes the packet to obtain the corresponding node of the management variable in the MIB tree. The Agent obtains the value of the management variable from the relevant module to generate a response packet. The Agent codes the response packet and sends it back to the NMS. 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 sends Trap messages to the NMS for reporting the events. To uniquely identify a management variable in SNMP packets, SNMP uses a hierarchical naming convention to distinguish different managed objects. The hierarchical structure is like a tree. Each node on the tree represents a managed object, which can be identified by a path from the root to the node. For example, the managed object B can be uniquely identified by a series of 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 is to describe the hierarchical structure of the managed object tree. Figure 7-3 Structure of MIB tree
1 1 6 1 B 5 6 2 3 4
In the UMG8900, the SNMP Agent supports three SNMP versions:

l l l
SNMPv1 SNMPv2c SNMPv3
In the SNMP architecture, access control is to allow different users to have different access authorities to management information. The view-based access control model implements access control through associating users and a MIB view.

NOTE
View-based access control is a component of SNMPv3. However, the UMG8900 provides the same access control method for SNMPv1/v2c users.
Figure 7-4 shows the access control mode based on view. Figure 7-4 Access control based on view
include/ exclude User Security mode Securitu level User group v1/v2c/usm v1/v2c/usm/any auth/noauth/priv MIB view MIB object 1 MIB object 2
MIB object n
In view-based access control mode, you first need to define a MIB view, and then define MIB objects included and excluded by the MIB view. To avoid mapping a large number of users to the MIB view, the mode adopts two-level mapping methods: It maps a user group to the MIB view, and then maps users to the user group. To guarantee the security, you can set the security mode and security level for the above two mapping processes. SNMP v1/v2c does not support the robust authentication and encryption and only uses a community name as the identity of a visitor. In this case, the Agent determines whether to allow the 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
RO/RW Community MIB view include/ exclude MIB object 1 MIB object 2 Access mode MIB object n
Consequently, for SNMP v1/v2c, you can set SNMP with users and a user group, or only with a 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 user group contains multiple types of users (such as both v1 and v3), the any security mode is adopted when the user group maps to the MIB view. The SNMP Agent supports three types of security levels: auth, noauth, and priv. The three levels represent authentication without encryption, no authentication and encryption, and
authentication with encryption. For the v1, v2c or any security mode, its security level can only be noauth. To select auth or priv, you must set the security mode as usm.
Configuration Procedure
Figure 7-6 shows the steps for the SNMP configuration. Figure 7-6 Steps for the SNMP configuration
Start
No
Visiting protocol is SNMP V3? Yes Configure the supported SNMP version
Add SMNP views? Yes Add SNMP view information
No
Add SNMP groups
Add SNMP users
Configure the host for receiving Trap messages Configure the type of Trap messages to be reported
End
If SNMPv1 or SNMPv2c is used for communication between the NMS and the agent, the configuration steps can be simplified. Figure 7-7 shows the simplified steps for the SNMPv1 and SNMPv2c configuration.
7-8
Issue 02 (2008-05-07)
Figure 7-7 Simplified steps for the SNMPv1/v2c configuration

Start
Configure the supported SNMP version No
Add SNMP views? Yes Add SNMP view information
Add an access community name
Configure the host for receiving Trap messages Configure the type of Trap messages to be reported
End
Index Mapping of Configuration Command Parameters

Figure 7-8 shows the index mapping of the configuration command parameters of the SNMP.
Issue 02 (2008-05-07)
7-9
Figure 7-8 Index mapping of configuration command parameters

ADD SNMPVIEW NAME OIDTREE v1/v2c ADD SNMPGRP READVIEW WRITEVIEW NOTIFYVIEW NAME SECMDL v3 ADD SNMPCOMM VIEWNAME COMMNAME
ADD TRAPHOST COMMNAME IPADDR
ADD SNMPUSER GRPNAME SECMDL USERNAME
Data Planning
l
Table 7-4 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. Table 7-4 Data planning Parameter Name NMS version SNMP view name Mib object subtree OID Operate type SNMP group name Security level Read view name Write view name Notify view name UMG8900 <Version No.> <View name> <Mib object subtree OID> <Operate type> <Group Name> <Security level> <Read View Name> <Write View Name> <Notify View Name> Interconnected Device (NMS) The same as that of the peer device The same as that of the peer device The same as that of the peer device Issue 02 (2008-05-07)
7-10
Parameter Name SNMP user name Authentication protocol Authentication password Encryption protocol Encryption password SNMP group name Access mode IP address of the host receiving the SNMP notification Port No. Trap type
UMG8900 <User Name> <Authentication Protocol> <Authentication Password> <Privacy Protocol> <Privacy Password> <Community Name> <Access Mode> The same as that of the peer device <UDP Port No.> <Trap type>
Interconnected Device (NMS) The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Host Address>
The same as that of the peer device -
Procedure
Step 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 Security Model. 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=<Security level>, 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=<Read View Name>, WRITEVIEW=<Write View Name>, NOTIFYVIEW=<Notify View Name>; Step 4 Run ADD SNMPGRP to add the SNMP user. Security Model must be the same as that on the NMS.
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>;
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 in ADD SNMPUSER. ADD TRAPHOST: IPADDR=<Host Address>, COMMNAME=<Community Name>, UDPPORT=<UDP Port No.>, VER=V1; Step 7 Run SET SNMPTRAP to set the TRAP-related parameters. SET SNMPTRAP: TYPE=<Trap type>; ----End
Example
Example 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;
Postrequisite
After the SNMP data is configured, configuring the MGW data is complete. Then, configure other data.
8 Configuring Frames and Boards
8
Prerequisite Context
Configuring Frames and Boards
This describes how to add frames and boards.
The hardware installation and software installation are complete.
You do not need to configure cabinets of the UMG8900 separately. By default, the system has added 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-bit dial in-line package (DIP) switch on the transfer board on the back of the frame. The configured frame No. must be the same with the No. decided by the DIP switch. Otherwise, loading software and data to the frame will fail. The main control frame is configured by default and its No. is fixed as 1. You cannot add or delete it. If the networking requires an independent central switching frame, its frame No. is 0. If no independent central switching frame is configured, the main control frame serves as the central switching frame. The control frame is needed only for large capacity configuration. Its frame No. is 8. In SSM-256 self-cascading mode, each GE and TDM cascading optical port connects with the corresponding one. That is, cascading optical ports 0, 1, 2, and 3 in the central switching frame connect with cascading ports 0, 1, 2, and 3 in cascaded frames respectively. In SSM-32 self-cascading mode, service frames must be cascaded with the main control frame through TDM optical port 0. TDM Port0 must be set to the same No. with the actual optical port on the MTNC through which the service frame connects to the main control frame. In SSM-256 and SSM-32 mixed cascading mode, SSM-32 frames must be cascaded with the SSM-256 central switching frame through TDM optical port 0, and TDM Port0 must be set to the same No. with the actual optical port on the TNB/BLU through which the service frame connects to the central switching frame.
l l
Issue 02 (2008-05-07)
8-1

l
In SSM-256 and SSM-32 mixed cascading mode, SSM-32 frames cascaded to one pair of the BLUs or the TNUs in the central switching frame must be numbered in an ascending order. The SSM-32 frame with the smallest frame No. is called a level-2 cascading frame. The FE cascading cable of the level-2 cascading frame is cascaded to the BLU/NET through interface FE3 on the MTNC, and then is cascaded to other SSM-32 frames through interfaces FE2, FE1, and FE0 in order. When the UG02MNET and the UG02MBLU.C are configured in the SSM-256 frame, the central switching frame is directly connected to service frames through interfaces FE1&FE2(UG02MNET)/FE1&FE2(UG02MBLU.C), and the level-2 cascading frame is not used. When the central switching frame is cascaded with only one service frame, interface FE1 is used. For the GE cascading, if the SSM-32 frame is directly cascaded to the SSM-256 frame, the GE 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 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. Front boards include the OMU, MPU, VPU, SPF and MCMF in the CMU. Back boards include the TNU, CLK, PPU, E32, HRB, T32, PIE, S1L, and MCMB in the CMU. FLU--BLU Limitation on opposite positions SSM-256 OMU/MPU--NET HRB--E8T/E1G/E32 SSM-32 OMU/MPU--TNU The OMU can only be in front slots 7 and 8 in the main control frame. The MPU can only be in front slots 7 and 8 in a frame except the main control frame. Limitation on fixed positions SSM-256 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 main frame. The FLU and BLU can only be in the central switching frame.
SSM-256 Limitation on front and back boards SSM-32
8-2
Issue 02 (2008-05-07)
Item
Description The OMU (MOMB) can only be in front slots 6, 7, 8, and 9 in the main control frame. The MPU (MMPB) can only be in front slots 6, 7, 8, and 9 in a service frame. SSM-32 The TNU (MTNC) can only be in back slots 6, 7, 8, and 9. The NLU (MNLU) can only be in back slots 4, 5, 10, and 11. The CLK, if needed, can only be in back slots 0 and 1 in the main control frame. When the MTNU/TCLU is installed in the SSM-256 frame, the following boards can be used: UG01E32, UG01T32, UG01BLU, UG01FLU, UG02BLU, UG02FLU, and UG01SPF. When the MTNB is installed in the SSM-256 frame, the following boards can be used: UG02E32, UG02T32, UG01ESU, UG01TSU, UG02BLU, UG02FLU, and UG02SPF. 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 of board types. Only configuration of some boards is involved. For details, refer to Boards.
l Difference on appearance of UG01 and UG02 boards is that
SSM-256
Limitation on configuration
SSM-32
subscript a exists or no subscript exists on the name silkscreen of the front panel of the UG01 board, and subscript b exists on that of the UG02 board.
l You can query board file information with LST BRDARC
and obtain the board version information.
SSM-256 Default configuration SSM-32
The OMU and NET in the main control frame and the MPU and NET in other frames are configured by default. You do not need to configure these boards and cannot delete them. The OMU and TNU in the main control frame and the TNU in service frames are configured by default. You do not need to configure these boards and cannot delete them.
Issue 02 (2008-05-07)
8-3
Item
Description All OMU, MPU, and CMU boards are numbered uniformly. Nos. for all OMU 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 other MPUs 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 it is located.
Limitation on board Nos.
For a board in 1+1 backup mode, its board type and No. must be the same with those of the board in the paired slot. For example, if an FLU board in 1+1 backup mode is in slot 12, the board in slot 13 must also be FLU and the 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 7
and 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+1
backup mode. When the system starts up, the master is determined through the contention mechanism. The board that is often started first is the master and the other one the slave.
The boards that can work in 1+1 backup mode only include the OMU, MPU, NET, CLK, TNU, CMU, HRB and BLU. Work modes 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.
Data Planning
l
Table 8-2 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. Table 8-2 Data planning Parameter Name Frame No. Frame version Cascading mode Cascading board No. Configure GE cascade Local frame GE cascade slot No. Up frame GE cascade slot No. Up frame GE port No. UMG8900 <Frame No.> <Frame Ver> <FE Cascading Mode> <Cascading Board No.> <Configure GE Cascade> <Local Frame GE Cascade Slot No.> <Up Frame GE Cascade Slot No.> <Up Frame GE Port No.>
Issue 02 (2008-05-07)
8-4
Parameter Name Configure TDM cascade TDM cascadeport0 TDM cascadeport1 Cabinet No. Frame position Frame name Frame description Slot No. Board position Board type Backup type Hardware type Board No.
UMG8900 <Configure TDM Cascade> <TDM CascadePort0> <TDM CascadePort1> <Cabinet No.> <Frame Position> <Frame Name> <Frame Description> <Slot No.> <Board Position> <Board type> <Backup type> <Hardware type> <Board No.>
Table 8-3 lists the parameters output to other steps. Table 8-3 Output parameter Parameter Name Board type Board No. Frame No. Slot No. Board position Data <Board type> <Board No.> <Frame No.> <Slot No.> <Board Position>
Procedure
Step 1 Run ADD FRM to add the frame. You can set Frame Type to Service Frame, Central Switching Frame, or Control Frame. By default, the main control frame is configured and the frame No. is 1. l Set Frame Type to Central Switching Frame. The frame No. is always 0. In SSM-256 and 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=<Cabinet No.>, LOC=<Frame Position>, FNM=<Frame Name>, FD=<Frame Description>; l
Issue 02 (2008-05-07)
Set Frame Type to Control Frame. The frame No. is always 8.

ADD FRM: FN=<Frame No.>, FV=<Frame Ver>, FT=CONTROL, SHF=<Cabinet No.>, LOC=<Frame Position>, FNM=<Frame Name>, FD=<Frame Description>; l Set Frame Type to Service Frame. If the UG01NET is configured in the central switching frame, set FE Cascading Mode to Second Cascading Mode. If the UG02NET is configured in the central switching frame, set FE Cascading Mode to Direct Cascading ModeSet Configure GE Cascadee to YES. ADD FRM: FN=<Frame No.>, FV=<Frame Ver>, FT=SERVICE, CM=<FE Cascading Mode>, CN=<Cascading Board No.>, GECAS=<Configure GE Cascade>, GELSN=<Local Frame GE Cascade Slot No.>, GESN=<Up Frame GE Cascade Slot No.>, 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=<Frame Description>; 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
Example
Board layout This example uses the SSM-256 and SSM-32 mixed cascading mode. Figure 8-1 shows the board layout.
8-6
Issue 02 (2008-05-07)
Figure 8-1 Board layout of the UMG8900

0 0 0 1 0 2 0 3 0 4 0 5 0 6 0 7 0 8 0 9 1 0 1 1 1 2 1 3 1 4 1 5 Slot No.
M Back E Board 3 2 Front Board
M E 3 2
M E 3 2 M S P F
M E 3 2 M S P F
M T N C M M P B
M T N C M M P B
Service Frame
M Back C Board L K M Front V Board P D
M C L K M V P D M V P D M V P D
M C M B M C M F
M C M B M C M F
M T N C M O M B
M T N C M O M B
M E 8 T M H R U
M E 8 T M H R U
M E 8 T M H R U
M E 8 T M H R U
Main Control Frame
M Back B Board L U M Front F Board L U
M B L U M F L U
M T N B
M N E T M M P U
M N E T M M P U
M T N B
Central Switching Frame
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;
Issue 02 (2008-05-07)
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;
Postrequisite
After configuring frames and boards, configure the clock. Configuring the Clock
8-8
Issue 02 (2008-05-07)
9 Configuring the Clock
9
Prerequisite UMG8900 Clock System
Configuring the Clock
This describes how to configure the clock data including the reference source, CLK, and line clock source.
The frames and boards data is correctly set.
The UMG8900 clock system provides clock signals to meet the requirements of the UMG8900. It accesses external reference clock signals of different standards to provide the stratum-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 clock subboard on the TNC board. When independent CLK boards are adopted, the system can provide both the stratum-2 and stratum-3 precision clocks. When the clock subboard is adopted, only the stratum-3 precision clock can be provided. Depending on such schemes as tracing of external reference signals and filtering of external reference jitter and float, the CLK boards or clock subboard on the TNC board outputs clock signals with high frequency, accuracy and stability, ensuring preciseness of clock source. The MCLK boards support the following clock reference sources:
l l l l l l l
2-MHz line clock 2-Mbit/s line clock 1.5-Mbit/s line clock 64-kHz line clock 8-kHz line clock Global positioning system (GPS) Global navigation satellite system (GLONASS)
The clock subboard supports the following clock reference sources:

l l
2-MHz line clock 2-Mbit/s line clock

Issue 02 (2008-05-07)

l
8-kHz line clock
The clock system also provides building integrated timing supply (BITS) clock output interfaces to connect with devices at the upper layer and provides BITS clock signal reference source for devices at the lower layer. In addition, the clock system can be configured through software to choose the external clock reference source and output clock level flexibly.
Introduction to the SSM

Synchronization status message (SSM) is a synchronization status message and indicates the level 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 to transmit 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
Multi frame 16 frames
Odd frame
32 timeslots
Timeslot 0
8 bits
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 clock and 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 complete SSM 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 10 100 1000
9-2
Meaning Primary reference clock (PRC) Transit network clock (TNC) Local network clock (LNC)
Level Stratum-1 clock Stratum-2 clock Stratum-3 clock

Issue 02 (2008-05-07)
SSM Code 1011 1111 0
Meaning SDH device timing source (SETS) Don't use for sync (DNU) Sync status unknown (UNKNOWN)
Level Transfer node clock Not used for synchronization Unknown synchronization status
In Table 9-1, the priority is PRC > TNC > LNC > SETS > UNKNOWN > DNU. The priority of 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 Status

The value of phase-lock status can be:
l
Free running: Indicates that the CLK board outputs free running clock generated by its crystal. Fast tracking: Indicates that the CLK board or the clock subboard on the MTNC is tracking reference source clock fast and is an instantaneous status usually when the system just connects the reference source. Locked: Indicates that the CLK board or the clock subboard on the MTNC has locked primary reference source and outputs clock signals aligned with reference source. Holdover: Indicates that the CLK board or the clock subboard on the MTNC outputs clock signals 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 clock subboard on the MTNC is Locked when the system is in normal operation. Otherwise, the clock is in error. You need to examine clock cable connections and clock alarms to find out the cause of error. If no reference source is set and the CLK board or the clock subboard on the MTNC adopts clock generated by its constant-temperature crystal, the phase-lock status is Free running.
Clock Reference Source Selection

The UMG8900 supports four options of clock reference source, namely GPS/GLONASS, onechannel 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.
Issue 02 (2008-05-07)
9-3
Figure 9-2 Procedures for choosing clock reference source

Start
Yes Manual selection? No Yes Under SSM control No Select a reference source based on the configured priority
Specify the primary reference source without switching reference sources
Select the reference source based on SSM level
End
First, the system supports two modes of reference source selection, automatic selection and manual selection. In manual selection mode, the CLK board only traces primary reference source that is manually specified, without auto switching between reference sources. Second, automatic selection falls into two cases, namely, under SSM control and without SSM control. Under SSM control, first the reference source with higher SSM level is preferred. If with the same SSM level, the reference source with higher priority is preferred. If available reference source with the highest level is missing, the CLK board will auto switch to the reference source with secondary highest level. When the original reference source recovers, the CLK board can auto switch back to it. Without SSM control, first the reference source with higher priority is preferred. If available reference source with the highest level is missing, the CLK board will auto switch to the reference source with secondary highest level. When the original reference source recovers, the CLK board can auto switch back to it. You can configure priorities for reference sources manually. By default, priorities are arranged in the following high-to-low order: GPS/GLONASS (level 1), external synchronous reference source (level 2), line clock 1 (level 3) and line clock 2 (level 4). It is recommended to select the external synchronous reference source.
NOTE
In automatic selection mode, the primary reference source specified in manual selection mode does not take effect.
Clock Distribution and Output

When independent CLK boards are adopted, they provide clock signals to the NET. Then the NET distributes the clock signals to other boards within the frame. The CLK provides clock
signals to the NET in its own frame through the backplane. It provides clock signals to the NET in other frames through clock distribution cables. When the subboard on the TNC is adopted, it sends clock signals to the boards in its own frame through the backplane. For boards in other frames, it first sends clock signals to the TNC through TDM cascading cables between frames, and the TNC then distributes the clock signals to the boards in its frame. Both the CLK and the subboard on the TNC can output one-channel 2-Mbit/s, 1.5-Mbit/s, 2MHz or 16-kHz external synchronous clock signals to other equipment within the network or access network equipment. You can configure the type of output clock signal by the MML command MOD CLK.
Physical Cable Connection

Before configuring clock, you need to connect physical cables based on actual clock networking mode. The connection of physical clock cables is shown in Table 9-2. Table 9-2 Clock cable connection Application Cable Connection Connect the 8K_OUT interface of the TDM interface board (including E32/T32/S2L/P4L/P1H) with the 8K-IN1 interface of the master and slave MCLK boards through the 8K clock cable. The X1 plug of the 8K clock cable connects the TDM interface board side and the X2/X3 plug connects the MCLK board side. The same as above. Connect the 2M_IN interface of the CLK board with the clock output interface of the BITS device through the 2M clock cable. Connect the 1.5M/64k interface of the CLK board with the clock output interface of the BITS device through the 1.5M/ 64k clock cable. Connect the ANT interface of the MCLK board with the GPS satellite antenna through the GPS/GLONASS clock cable. The satellite card must be inserted in the MCLK board. Connect the CLK-OUT interface of the MCLK board with the CLK-IN interface of the NET board through the clock distribution cable. CLK0_IN and CLK1_IN interfaces of the NET board correspond the CLK_OUT interfaces of the master and slave MCLK boards respectively. The X1 plug of the clock distribution cable connects the MCLK board side and the X2-X7 plugs connect the NET board side.
Extract the line clock reference source 1 from the TDM interface board.
Extract the line clock reference source 2 from the TDM interface board. Extract the external synchronous reference source from the BITS device.
Extract the reference source from GPS/GLONASS.
Clock distribution to frames except the main control frame.
Issue 02 (2008-05-07)
9-5
Application Clock distribution to the current frame. Clock output.
Cable Connection Distributed through the backplane, without manual connection. Connect the 2M_OUT interface of the MCLK board with the clock input interface of the clock receiving device through the 2M clock cable.
Figure 9-3 shows the recommended steps for configuring the clock. Figure 9-3 Steps for clock configuration
Configure the clock
Configure reference sources? Yes Configure clock reference sources
No
Configure CLK data Yes
Output clock signals? No
Extract line clocks? No Yes Configure line clock sources
End
Clock configuration varies with different modes of the clock synchronization networking. Refer to Figure 9-3.
Data Planning
l
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. Table 9-3 Input parameter Parameter Name Board type Board No. Data <Board type> <Board No.> Input Source Configuring Frames and Boards Configuring Frames and Boards
Issue 02 (2008-05-07)
9-6
Table 9-4 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. Table 9-4 Data planning Parameter Name Priority of GPS reference source Priority of line clock 1 Priority of line clock 2 Priority of external synchronous 1 Priority of external synchronous 2 Type of external synchronous Select mode of reference source Clock level Type of clock signal of external synchronous output Whether SSM control External reference source work mode Line clock Interface type Port No. Channel No. SSM timeslot UMG8900 <Priority of GPS reference source> <Priority of line clock 1> <Priority of line clock 2> <Priority of external synchronous 1> <Priority of external synchronous 2> <Type of external synchronous> <Select Mode of Reference Source> <Clock Level> <Type of Clock Signal of External Synchronous Output> <Whether SSM Control> <External Reference Source Work Mode> <Line Clock> <Interface Type> <Port No.> <Channel No.> <SSM Time Slot>
Procedure
Step 1 If the clock reference source is required, run MOD CLKSRC to configure the clock reference source. Set Board Type to CLK or TNC. If no clock reference source is required, perform Step 2 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
Issue 02 (2008-05-07)
Set Board Type to TNC, and the GPS reference source is not supported.
MOD CLKSRC: BRDTYPE=TNC, LINE1PRI=<Priority of line clock 1>, LINE2PRI=<Priority of line clock 2>, EXT1PRI=<Priority of external synchronous 1>, 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 Synchronous Output>, CTRL=<Whether SSM Control>, CLKMODE=<External Reference Source Work 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=<Whether SSM 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 clock reference 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
Example
Example 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;
Postrequisite
After configuring the system clock data, configure the MGW control interface and SIGTRAN interface. Configuring the MGW Control Interface and SIGTRAN Interface
9-8
Issue 02 (2008-05-07)
10 Configuring the MGW Control Interface and SIGTRAN Interface
10
Configuring the MGW Control Interface and SIGTRAN Interface
About This Chapter

This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface. 10.1 Configuring the Physical Interface in Single-Frame Networking Mode This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface in single-frame networking mode. 10.2 Configuring the Physical Interface in SSM-256 Self-Cascading Mode This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface in SSM-256 self-cascading mode. 10.3 Configuring the Physical Interface in SSM-32 Self-Cascading Mode This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface in SSM-32 self-cascading mode. 10.4 Configuring the Physical Interface in Mixed Cascading Mode This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface in SSM-256 and SSM-32 mixed cascading mode. 10.5 Configuring the E1 Physical Interface Carrying IP Signaling Packets This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface when the E1 physical interface is used to carry Internet Protocol (IP) signaling packets.
Issue 02 (2008-05-07)
10-1
10.1 Configuring the Physical Interface in Single-Frame Networking Mode

This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface in single-frame networking mode.
Prerequisite
l l
The frames and board data is correctly set. The clock data is correctly set.
Context
In single-frame networking mode, the configurations of the physical interface of the MGW control interface and SIGTRAN interface in the SSM-256 frame are different from those in the SSM-32 frame. The configuration rules of the two types of frames are as follows:
l

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.248 and SIGTRAN interfaces at the same time, if the HRB is not configured. The IP address of the OAM interface is set as the slave one, and that of the H.248 and SIGTRAN interfaces is set as the master one. In this case, if the H.248 and SIGTRAN messages are transmitted through the same protocol, different protocol interface numbers must be used. Table 10-1 shows the usage rules of IP interfaces when the HRB board is configured in the SSM-256 frame. Table 10-1 Usage rules of IP interfaces when the HRB is configured Logical Position Physical Position and Function When the E8T Is Configured OMC interface on the back NET, which can serve as an OAM interface The first FE port on the back E8T, which can serve as an H. 248 or SIGTRAN interface Other FE ports on the back E8T, which can serve as an IP service bearer interface Physical Position and Function When Only the E1G Is Configured OMC interface on the back NET, which can serve as an OAM interface GE port on the back E1G, which can serve as an H.248 or SIGTRAN interface through the master IP address GE port on the back E1G, which can serve as an IP service bearer interface through the slave IP address
Issue 02 (2008-05-07)
OMU
HRB
HRB
10-2
NOTE
If both the E8T and E1G boards are configured in the frame, the E8T board is used for centralized forwarding.
As shown in Table 10-1, the first FE port on the E8T board or the GE port on the E1G board 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 centralized forwarding function of the HRB.
l

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 the Mc 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 single SSM-32 networking Logical Position OMU OMU Physical Position and Function OMC interface on the TNC, which can serve as an OAM interface Mc interface on the back TNC, which can serve as an H.248 or SIGTRAN interface
As shown in Table 10-2, the Mc interface on the OMU provides both H.248 and SIGTRAN interfaces. In this case, if the same transmission protocol is used for H.248 and SIGTRAN messages, different protocol port numbers must be used.
If the HRB is configured for single SSM-32 networking, the usage rules are similar to those 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 single SSM-32 networking Logical Position Physical Position and Function When the E8T Is Configured OMC interface on the back TNC, which can also serve as an OAM interface
Physical Position and Function When Only the E1G Is Configured OMC interface on the back TNC, which can serve as an OAM interface
10-3
OMU
Issue 02 (2008-05-07)
Logical Position
Physical Position and Function When the E8T Is Configured The first FE port on the back E8T, which can serve as an H. 248 or SIGTRAN interface Other FE ports on the back E8T, which can serve as an IP service bearer interface
Physical Position and Function When Only the E1G Is Configured GE port on the back E1G, which can serve as an H.248 or SIGTRAN interface through the master IP address GE port on the back E1G, which can serve as an IP service bearer interface through the slave IP address
HRB
HRB
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 needs to provide H.248 and SIGTRAN interfaces at the same time. In this case, if the same transmission protocol is used for H.248 and SIGTRAN messages, different protocol port numbers must be adopted.
Data Planning
l
Table 10-5 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. Table 10-5 Data planning Parameter Name UMG8900 Interconnect ed Device 1 (MGC) Interconnect ed Device 2 (Direct Router) Interconnect ed Device 3 (MGW) -
Work mode
<Work Mode>
10-4
Issue 02 (2008-05-07)
Parameter Name
UMG8900
Interconnect ed Device 1 (MGC) The same as that of the peer device
Interconnect ed Device 2 (Direct Router) -
Interconnect ed Device 3 (MGW) -
Interface type Interface ID IP addresses 1 of gateway control interfaces and SIGTRAN interfaces IP addresses 2 of gateway control interfaces and SIGTRAN interfaces IP address and mask of gateway control interfaces and SIGTRAN interfaces Master or slave flag Slot No. IP address 1 of the MGC IP address 2 of the MGC IP address and mask of the MGC IP address of the router connected with the UMG8900
<Interface type> <Interface No.> <Interface IP address>_1
<Interface IP address>_2
<Interface IP address mask>
<Master or slave flag> <Slot No.> The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device
<Destination address>_1 <Destination address>_2 <Destination address mask> -
<Next hop address>
Issue 02 (2008-05-07)
10-5
Parameter Name
UMG8900
Interconnect ed Device 1 (MGC) -
Interconnect ed Device 2 (Direct Router) -
Interconnect ed Device 3 (MGW) <Gateway IP>
IP address of the gateway If aging or not
The same as that of the peer device <If aging or not>
Table 10-6 lists the parameters output to other steps. Table 10-6 Data output Parameter Name IP address 1 of MGW control interfaces and SIGTRAN interfaces IP address 2 of MGW control interfaces and SIGTRAN interfaces Data <Interface IP address>_1 <Interface IP address>_2
NOTE
If Stream Control Transmission Protocol (SCTP) multi-homing is supported, two IP addresses of MGW control interfaces and SIGTRAN interfaces are exported.
Procedure
Step 1 Run SET IPWORKMODE to set the IP work mode of boards. SET IPWORKMODE is valid for the OMB, MPB, and MPU only. In single-frame networking mode, SET IPWORKMODE is valid for the OMB only. WORK MODE can be STANDBY or LOADSHARE. By default, it is STANDBY. WORK MODE is set to LOADSHARE only when 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 Board type. 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 to STANDBY, 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-sharing mode. The OMC interface still serves as the system maintenance interface and works in master/slave mode.
10-6
Issue 02 (2008-05-07)
If the IP interface on the PPU or the HRB is adopted, set Board type to a value rather than OMU. ADD IPADDR: BT=<Board type>, BN=<Board No.>, IFT=ETH, IFN=<Interface No.>, 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 MGC Step 4 and that of the gateway are not in the same network segment The back interface board of the HRB works as the MGW control interface and Step 6 SIGTRAN interface Step 3 If SCTP multi-homing is configured on the OMB, if the Mc interface works in load-sharing mode, and if IP addresses need to be configured for two OMBs respectively, run ADD IPADDR to add the IP address of the Mc interface on the slave board. Otherwise, do not perform this step but perform the related step based on the preceding table. ADD IPADDR: BT=OMU, BN=0, IFT=ETH, IFN=1, IPADDR=<Interface IP address>_2, MASK=<Interface IP address mask>, FLAG=<Master or slave flag>, SN=<Slot No.>; Step 4 Run ADD ROUTE to add routes. Set Route type to Next hop. Configuration commands vary with 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=<Next hop address>, SN=<Slot No.>;
NOTE
In SCTP multi-homing mode, the MGC provides two IP addresses. If WORK MODE is set to LOADSHARE, you must specify Slot No.. If WORK MODE is set to STANDBY, you do not need to specify Slot No..
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=<Next hop address>;
Step 5 If SCTP multi-homing is configured on the OMB, you must configure routes to the MGC for two 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 hop address>, 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
SSM-256 Frame
Networking 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
MGC IP address: 192.168.0.1/24
IP Network IP address of the router: 10.1.1.254/24 IP address of the Gateway: 10.1.1.200/24
IP address of the OMC interface: 10.1.1.1 IP address of the first interface on the E8T: 10.1.1.10 IP address of the Mc interface: 10.1.1.50 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 when configuring 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 forwarding interface.
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;
Configure the GE interface on the back E1G of the HRB as the centralized forwarding interface.
SSM-32 Frame
Networking diagram Figure 10-2 shows the networking diagram of a single SSM-32 frame.
Figure 10-2 Networking diagram of a single SSM-32 frame

MGC IP address 1: 192.168.0.1/24 IP address 2: 192.168.0.2/24
IP Network IP address of the router: 10.1.1.254/24 IP address of the Gateway: 10.1.1.200/24 IP address of the OMC interface: 10.1.1.1 7 slot IP address of the Mc interface: 10.1.1.4 8 slot IP address of the Mc interface: 10.1.1.14 IP address of the first interface on the E8T: 10.1.1.10 UMG8900 IP address of the Mc interface: 10.1.1.50
Example script
l
If the HRB is not configured, use the Mc interface on the OMB as the centralized forwarding interface. 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";
If the HRB is not configured, use the Mc interface on the OMB as the centralized forwarding interface. WORK MODE is LOADSHARE. Enabling the centralized forwarding function of 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";
Configure the first interface on the back E8T of the HRB as the centralized forwarding interface.
Configure the GE interface on the back E1G of the HRB as the centralized forwarding interface.
ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=0, IPADDR="10.1.1.50", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO;
Issue 02 (2008-05-07)
10-9
ADD GWADDR: BT=HRB, BN=0, IPADDR="10.1.1.50", GWIP="10.1.1.200", TIMEOUT=NoAging;
Postrequisite
After configuring the physical interface of the MGW control interface and SIGTRAN interface, configure the MGW control data. 11 Configuring MGW Control Data
10.2 Configuring the Physical Interface in SSM-256 SelfCascading Mode

This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface in SSM-256 self-cascading mode.
Prerequisite
l l
Context
In SSM-256 self-cascading mode, the centralized forwarding mode is used. The OMC interface on the back NET of the MPU in the centralized switching provides the H.248 interface and SIGTRAN interface.
Data Planning
l
Table 10-7 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. Table 10-7 Data planning Parameter Name UMG8900 Interconnected Device 1 (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device Interconnected Device 2 (Direct Router) -
Work mode IP address 1 of the OMC interface on the MPU IP address 2 of the OMC interface on the MPU IP address and mask of the OMC interface on the MPU
10-10
<Work Mode> <Interface IP address>_1 <Interface IP address>_2 <Interface IP address mask>
Issue 02 (2008-05-07)
Parameter Name
UMG8900
Interconnected Device 1 (MGC) -
Interconnected Device 2 (Direct Router) <Next hop address> -
Master or slave flag Slot No. IP address of the router connected with the UMG8900 IP address 1 of the MGC IP address 2 of the MGC IP address and mask of the MGC
<Destination address>_1 <Destination address>_2 <Destination address mask>
Table 10-8 lists the parameters output to other steps. Table 10-8 Data output Parameter Name IP addresses 1 of MGW control interfaces and SIGTRAN interfaces IP addresses 2 of MGW control interfaces and SIGTRAN interfaces Data <Interface IP address>_1 <Interface IP address>_2
NOTE
Procedure
Step 1 Run SET IPWORKMODE to set the IP work mode. SET IPWORKMODE is valid for the OMB, MPB, and MPU only. In SSM-256 self-cascading mode, LOADSHARE is valid for the MPU only. WORK MODE can be STANDBY or LOADSHARE. By default, it is STANDBY. WORK MODE is set to LOADSHARE only when 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 in the central switching frame serves as the centralized forwarding interface, set Board type to MPU and Interface No. to 0. Board No. of the MPU in the central switching frame can only be 1.
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 is set 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 for two MPUs respectively, run ADD IPADDR to add the IP address of the OMC interface on the slave 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 add a 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 hop address>, SN=<Slot No.>;
NOTE
If WORK MODE is set to LOADSHARE, you must specify Slot No.. If WORK MODE is set to STANDBY, you do not need to specify Slot No..
Step 5 If SCTP multi-homing is configured on the MPU, you must configure routes to the MGC for two 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 hop address>, SN=<Slot No.>; ----End
Example
Networking diagram 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 IP address of the router: 10.1.1.254/24
7 slot IP address of the OMC interface on the MPU in the central switching frame: 10.1.1.5 8 slot IP address of the OMC interface on the MPU in the central switching frame: 10.1.1.15 UMG8900
10-12
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";
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";
Postrequisite
10.3 Configuring the Physical Interface in SSM-32 SelfCascading Mode

This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface in SSM-32 self-cascading mode.
Prerequisite
l l
Context
In SSM-32 self-cascading mode, the centralized forwarding mode is used, and the OMC interface on the back TNC of the MPB in the first service frame is used as the H.248 interface and SIGTRAN interface.
Data Planning
l
Table 10-9 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.
Issue 02 (2008-05-07)
10-13
Table 10-9 Data planning Parameter Name UMG8900 Interconnected Device 1 (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device Interconnected Device 2 (Direct Router) -
Work mode IP address 1 of the OMC interface on the MPB IP address 2 of the OMC interface on the MPB IP address and mask of the OMC interface on the MPB Master or slave flag Slot No. IP address of the router connected with the UMG8900 IP address 1 of the MGC IP address 2 of the MGC IP address and mask of the MGC
<Next hop address> -
10-14
Issue 02 (2008-05-07)

NOTE
Procedure
Step 1 Run SET IPWORKMODE to set the IP work mode. SET IPWORKMODE is valid for the OMB, MPB, and MPU only. In SSM-32 self-cascading mode, LOADSHARE is valid for the MPB only. WORK MODE can be STANDBY or LOADSHARE. By default, it is STANDBY. WORK MODE is set to LOADSHARE only when 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 MPB in the first service frame serves as the centralized forwarding interface, set Board type to MPU and Interface No. to 0. Board No. of the MPU in the central switching frame can only be 1. 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 MPB is set to LOADSHARE, you must specify Slot No.. If WORK MODE is set 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 two MPBs respectively, run ADD IPADDR to add the IP address of the OMC interface on the slave 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 add a 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 hop address>, SN=<Slot No.>;
NOTE
Step 5 If SCTP multi-homing is configured on the MPB, you must configure routes to the MGC for two IP addresses. Run ADD ROUTE to add the route to IP address 2 of the MGC. Set Route type to Next hop. ADD ROUTE: BT=MPU, BN=1, DSTIP=<Destination address>_2, DSTMASK=<Destination address mask>, RTTYPE=NEXTHOP, NEXTHOP=<Next hop address>, SN=<Slot No.>; ----End
Example
Networking diagram Figure 10-4 shows the networking diagram of the SSM-32 self-cascading mode.
Figure 10-4 Networking diagram of the SSM-32 self-cascading

MGC IP address 1 : 192.168.0.1/24 IP address 2: 192.168.0.2/24
UMG8900
7 slot IP address of the OMC interface on the MPB in the first service frame: 10.1.1.6 8 slot IP address of the OMC interface on the MPB in the first service frame: 10.1.1.16
Example script
l
To set WORK MODE of the MPB to STANDBY, run the following command:
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";
Postrequisite
10-16
Issue 02 (2008-05-07)
10.4 Configuring the Physical Interface in Mixed Cascading Mode

This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface in SSM-256 and SSM-32 mixed cascading mode.
Prerequisite
l l
Context
In SSM-256 and SSM-32 mixed cascading mode, the SSM-256 frame is used as the central switching frame, and the centralized forwarding mode is used. The OMC interface on the back NET of the MPU in the central switching frame is used as the H.248 interface and SIGTRAN interface.
Data Planning
l
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. Table 10-11 Data planning Parameter Name UMG8900 Interconnected Device 1 (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device Interconnected Device 2 (Direct Router) -
Work mode IP address 1 of the OMC interface on the MPU IP address 2 of the OMC interface on the MPU IP address and mask of the OMC interface on the MPU Master or slave flag Slot No.
<Master or slave flag> <Slot No.>
Issue 02 (2008-05-07)
10-17
Parameter Name
UMG8900
Interconnected Device 2 (Direct Router) <Next hop address> -
IP address of the router connected with the UMG8900 IP address 1 of the MGC IP address 2 of the MGC IP address and mask of the MGC
The same as that of the peer device The same as that of the peer device The same as that of the peer device <Destination address mask>
NOTE
If Stream Control Transmission Protocol (SCTP) multi-homing is supported, two IP addresses of the MGW control interface and SIGTRAN interface are exported.
Procedure
Step 1 Run SET IPWORKMODE to set the IP work mode. SET IPWORKMODE is valid for the OMB, 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 or LOADSHARE. By default, it is STANDBY. WORK MODE is set to LOADSHARE only when 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 in the central switching frame serves as the centralized forwarding interface, set Board type to MPU and Interface No. to 0. Board No. of the MPU in the central switching frame can only be 1. 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.>;
10-18
Issue 02 (2008-05-07)

NOTE
If WORK MODE of the MPU is set to LOADSHARE, you must specify Slot No.. If WORK MODE is set 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 for two MPUs respectively, run ADD IPADDR to add the IP address of the OMC interface on the slave 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 add the 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 hop address>, SN=<Slot No.>;
NOTE
Step 5 If SCTP multi-homing is configured on the MPU, you must configure routes to the MGC for two IP addresses. Run ADD ROUTE to add the route to IP address 2 of the MGC. Set Route type to Next hop. ADD ROUTE: BT=MPU, BN=1, DSTIP=<Destination address>_2, DSTMASK=<Destination address mask>, RTTYPE=NEXTHOP, NEXTHOP=<Next hop address>, SN=<Slot No.>; ----End
Example
Networking diagram 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
7 slot IP address of the OMC interface on the MPU in the central switching frame: 10.1.1.5 8 slot IP address of the OMC interface on the MPU in the central switching frame: 10.1.1.15 UMG8900
Issue 02 (2008-05-07)
10-19
Example script
l
To set WORK MODE of the MPU to STANDBY, run the following command:
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";
Postrequisite
10.5 Configuring the E1 Physical Interface Carrying IP Signaling Packets

This describes how to configure the media gateway (MGW) control interface and signaling transport (SIGTRAN) interface when the E1 physical interface is used to carry Internet Protocol (IP) signaling packets.
Prerequisite
l l
Context
When the media gateway controller (MGC) is placed far away from the UMG8900 and has only the time division multiplexing (TDM) bearer, the UMG8900 communicates with the MGC through 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 and SIGTRAN interface.
Data Planning
l
Table 10-13 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.
10-20
Table 10-13 Input parameter Parameter Name TDM interface board type TDM board No. IOE board No. Virtual media gateway ID Data <Board type>_1 <Board No.> <Board No.>_2 <Virtual media gateway id> Input Source Configuring Frames and Boards Configuring Frames and Boards Configuring Frames and Boards 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 the table indicates whether the parameter needs to negotiate with the interconnected parameter. If not, "-" is filled in. Table 10-14 Data planning Parameter Name TDM optical port No. TDM port No. IOE internal TDM port No. Port description Start TID End TID CMU module No. TDM start timeslot TDM end timeslot Serial interface ID Interface type Serial interface description MP enable UMG8900 <TDM opt port No.> <TDM port No.> <IOE internal TDM port No.> <Port description> <Start TID> <End TID> <CMU Module No.> <Start timeslot> <End timeslot> <Interface No.> <Interface type> <Interface description> <MP enable> Interconnected Device 1 (MGC) -
Issue 02 (2008-05-07)
10-21
Parameter Name VT interface ID
UMG8900 <VT Interface No.>
Interconnected Device 1 (MGC) <Destination address> <Destination address mask>
IP address of the MGC The same as that of the peer device IP address and mask of the MGC The same as that of the peer device
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 port No.>, 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 an example. ADD BIND: TDMBT=S2L, TDMBN=<Board No.>_1, OPTPORT=<TDM opt port No.>, TDMPORT=<TDM port No.>, IOEBN=<Board No.>_2, IOEPORT=<IOE internal TDM port No.>, DESP=<Port description>; Step 2 Run ADD TDMIU to configure the binding relationship of the TDM port. Set Relay type to Inside. ADD TDMIU: BT=<Board type>, BN=<Board No.>_1, TIDFV=<Start TID>, TIDLV=<End TID>, VMGWID=<Virtual media gateway id>, HOSTID=<CMU Module No.>, 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 Interface No.>, IPADDR=<Destination address>, MASK=<Destination address mask>; ----End
Example
Networking diagram Figure 10-6 shows the networking diagram of using the E1 physical interface to carry IP packets.
10-22
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
E1
IP address of VT0 interface: 10.1.1.7 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 bearer network. Example script
ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD MOD MOD MOD MOD MOD MOD BIND: TDMBT=E32, TDMBN=0, TDMPORT=0, IOEBN=0, IOEPORT=0, DESP="MSC0-0"; BIND: TDMBT=E32, TDMBN=0, TDMPORT=1, IOEBN=0, IOEPORT=1, DESP=" MSC0-1"; BIND: TDMBT=E32, TDMBN=1, TDMPORT=0, IOEBN=0, IOEPORT=2, DESP=" MSC0-2"; BIND: TDMBT=E32, TDMBN=1, TDMPORT=1, IOEBN=0, IOEPORT=3, DESP=" MSC0-3"; TDMIU: BT=E32, BN=0, TIDFV=0, TIDLV=63, VMGWID=0, HOSTID=30, RT=INSIDE; TDMIU: BT=E32, BN=1, TIDFV=1024, TIDLV=1087, VMGWID=0, HOSTID=30, RT=INSIDE; CHANNEL: BN=0, PORT=0, STARTTS=1, ENDTS=31, IFN=0; CHANNEL: BN=0, PORT=1, STARTTS=1, ENDTS=31, IFN=1; CHANNEL: BN=0, PORT=2, STARTTS=1, ENDTS=31, IFN=2; CHANNEL: BN=0, PORT=3, STARTTS=1, ENDTS=31, IFN=3; IPIF: IFT=SRL, BT=HRB, BN=0, IFN=0, DESP="VT0-0", IFMP=YES, VT=0; IPIF: IFT=SRL, BT=HRB, BN=0, IFN=1, DESP="VT0-1", IFMP=YES, VT=0; IPIF: IFT=SRL, BT=HRB, BN=0, IFN=2, DESP="VT1-0", IFMP=YES, VT=1; IPIF: IFT=SRL, BT=HRB, BN=0, IFN=3, DESP="VT1-1", IFMP=YES, VT=1; IPIF: IFT=VT, BT=HRB, BN=0, IFN=0, DESP="VT0", BEARBW=0, RPTROUTE=YES; 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. The interface 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";
Postrequisite
After configuring the physical interface of the MGW control interface and SIGTRAN interface, configure the MGW control data. Configuring MGW Control Data
Issue 02 (2008-05-07)
10-23
11 Configuring MGW Control Data
11
Configuring MGW Control Data
About This Chapter

This describes how to configure the media gateway (MGW) control data. The standard MGW control 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 of the voice service and data service. 11.1 Configuring MGW data This describes how to configure the virtual media gateway (VMGW) ID, media gateway controller (MGC) ID, and media gateway (MGW) control data. 11.2 Configuring the Link This describes how to configure the H.248 link in different bearer modes. 11.3 Activating the VMGW This describes how to activate the virtual media gateway (VMGW) on which the H.248 link is configured.
Issue 02 (2008-05-07)
11-1
11.1 Configuring MGW data

This describes how to configure the virtual media gateway (VMGW) ID, media gateway controller (MGC) ID, and media gateway (MGW) control data.
Prerequisite
l l
The network management system (NMS) interface is correctly configured. The MGW control interface is correctly configured.

Figure 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
Data Planning
l
Table 11-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. If not, "-" is filled in. Table 11-1 Data planning Parameter Name Virtual media gateway ID Virtual media gateway ID UMG8900 Interconnected Device 1 (MGC) Interconnected Device 2 (DNS Server) -
<Virtual media gateway id>

l
In domain mode:<Virtual media gateway MID>_1 In IP mode: <Virtual media gateway MID>_2 In device mode: <Virtual media gateway MID>_3
11-2
Issue 02 (2008-05-07)
Parameter Name Master MGC ID Slave MGC ID Master MGC ID type Slave MGC ID type Master MGC ID Slave MGC ID IP address of the master DNS server IP address of the slave DNS server
UMG8900
Interconnected Device 1 (MGC) <Media gateway controller MID type>_1 <Media gateway controller MID type>_2 <Media gateway controller MID>_1 <Media gateway controller MID>_2 -
Interconnected Device 2 (DNS Server) -
<Media gateway controller No.>_1 <Media gateway controller No.>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device
<DNS IP address>_1
<DNS IP address>_2
Table 11-2 lists the parameters output to other steps. Table 11-2 Data output Parameter Name Virtual media gateway ID Master MGC ID Slave MGC ID Data <Virtual media gateway id> <Media gateway controller No.>_1 <Media gateway controller No.>_2
Procedure
Step 1 Run SET VMGW to set the virtual media gateway (VMGW). The VMGW ID can be in the following 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;
Issue 02 (2008-05-07)
11-3

l
IP address: SET VMGW: VMGWID=<Virtual media gateway id>, MIDTYPE=IP, MID=<Virtual media gateway MID>_2;
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 controller No.>_1, MIDTYPE=<Media gateway controller MID type>_1, MID=<Media gateway controller 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 controller No.>_2, MIDTYPE=<Media gateway controller MID type>_2, MID=<Media gateway controller MID>_2, MSS=SLAVE; Step 4 When the MGW ID or MGW controller ID is in the format of domain name, run SET DNSSVR to set the DNS server. If the ID type of the MGW and MGW controller is in the format of 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
Example
Networking diagram Figure 11-2 shows the typical networking. Figure 11-2 Networking diagram
Master MGC IP Network Slave MGC
IP address: 192.168.0.1 Port No.: 3333
IP address: 172.16.0.1 Port No.: 2222
IP address: 10.1.1.1 Port No.: 3333/2222 UMG8900
Example script
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;
Postrequisite
After configuring the MGW control data, configure the link data based on the selected transport layer protocol.
l l
Configuring the Link over UDP Configuring the Link over SCTP
11.2 Configuring the Link

This describes how to configure the H.248 link in different bearer modes. 11.2.1 Configuring the Link over UDP This describes how to configure the H.248 control link over the User Datagram Protocol (UDP). 11.2.2 Configuring the H.248 Link over SCTP This describes how to configure the H.248 control link over the Simple Control Transmission Protocol (SCTP). 11.2.3 Configuring the H.245 Link This describes how to configure the control link over the H.245 protocol.
11.2.1 Configuring the Link over UDP

This describes how to configure the H.248 control link over the User Datagram Protocol (UDP).
Prerequisite
l l
The MGW control interface is correctly configured. The MGW control data is correctly set.
Data Planning
l
Issue 02 (2008-05-07)
11-5
Table 11-3 Input parameter Parameter Name IP address of MGW control interfaces Data <Interface IP address>_1 Input Source
l
10.1 Configuring the Physical Interface in Single-Frame Networking Mode 10.2 Configuring the Physical Interface in SSM-256 SelfCascading Mode 10.3 Configuring the Physical Interface in SSM-32 SelfCascading Mode 10.4 Configuring the Physical Interface in Mixed Cascading Mode 10.5 Configuring the E1 Physical Interface Carrying IP Signaling Packets
Virtual media gateway ID Master MGC ID Slave MGC ID
<Virtual media gateway id> <Media gateway controller No.>_1 <Media gateway controller No.>_2
11.1 Configuring MGW data 11.1 Configuring MGW data 11.1 Configuring MGW data
Table 11-4 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. Table 11-4 Data planning Parameter Name Coding codec type UDP port No. to the master MGC UDP port No. to the slave MGC IP address of the master MGC IP address of the slave MGC UDP port No. to the master MGC UMG8900 <Codec type> <Local UDP port No.>_1 <Local UDP port No.>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device Interconnected Device (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device <Peer Master address>_1 <Peer Master address>_2 <Peer UDP port No.>_1
11-6
Issue 02 (2008-05-07)
Parameter Name UDP port No. to the slave MGC H.248 signaling link No. to the master MGC H.248 signaling link No. to the slave MGC
UMG8900 The same as that of the peer device <H248 signaling link No.>_1 <H248 signaling link No.>_2
Interconnected Device (MGC) <Peer UDP port No.>_2 -
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 media gateway 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 port No.>_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 media gateway 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
Example
Issue 02 (2008-05-07)
11-7

Master MGC IP Network Slave MGC
IP address: 192.168.0.1 UDP port No.: 2944
IP address: 172.16.0.1 UDP port No.: 2944
IP address: 10.1.1.1 UDP port No.: 2945 UMG8900
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";
Postrequisite
After configuring the H.248 links, activate the VMGW. Activating the VMGW
11.2.2 Configuring the H.248 Link over SCTP

This describes how to configure the H.248 control link over the Simple Control Transmission Protocol (SCTP).
Prerequisite
l l
The MGW control interface is correctly configured. The MGW data is correctly set.
Data Planning
l
11-8
Issue 02 (2008-05-07)
Table 11-5 Input parameter Parameter Name IP address 1 of MGW control interfaces Data <Interface IP address>_1 Input Source
l
10.1 Configuring the Physical Interface in Single-Frame Networking Mode 10.2 Configuring the Physical Interface in SSM-256 Self-Cascading Mode 10.3 Configuring the Physical Interface in SSM-32 Self-Cascading Mode 10.4 Configuring the Physical Interface in Mixed Cascading Mode 10.5 Configuring the E1 Physical Interface Carrying IP Signaling Packets 10.1 Configuring the Physical Interface in Single-Frame Networking Mode 10.2 Configuring the Physical Interface in SSM-256 Self-Cascading Mode 10.3 Configuring the Physical Interface in SSM-32 Self-Cascading Mode 10.4 Configuring the Physical Interface in Mixed Cascading Mode
IP address 2 of MGW control interfaces
Virtual media gateway ID Master MGC ID Slave MGC ID Board type Board No. Frame No. Slot No. Board position
<Virtual media gateway id> <Media gateway controller No.>_1 <Media gateway controller No.>_2 <Board type> <Board No.> <Frame No.> <Slot No.> <Board Position>
11.1 Configuring MGW data 11.1 Configuring MGW data 11.1 Configuring MGW data 8 Configuring Frames and Boards 8 Configuring Frames and Boards 8 Configuring Frames and Boards 8 Configuring Frames and Boards 8 Configuring Frames and Boards
Issue 02 (2008-05-07)
11-9
Table 11-6 Data planning Parameter Name Coding codec type Checksum algorithm Path mode SCTP port No. to the master MGC SCTP port No. to the slave MGC IP address 1 of the master MGC IP address 2 of the master MGC IP address 1 of the slave MGC IP address 2 of the slave MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC H.248 signaling link No. to the master MGC H.248 signaling link No. to the slave MGC SubBoard No. UMG8900 <Codec type> <Checksum algorithm> <path mode> <Local SCTP port No.>_1 <Local SCTP port No.>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <H248 signaling link No.>_1 <H248 signaling link No.>_2 <SubBoard No.> Interconnected Device (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Peer Master address>_1 <Peer Slave address>_1 <Peer Master address>_2 <Peer Slave address>_2 <Peer SCTP port No.>_1 <Peer SCTP port No.>_2 -
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=<Checksum algorithm>; Step 3 Check whether the SCTP multi-homing networking is adopted.
l l
If the SCTP multi-homing networking is not adopted, perform Step 4 and Step 5. 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 to Unsupported. ADD H248LNK: LINKID=<H248 signaling link No.>_1, VMGWID=<Virtual media gateway id>, MGCIDX=<Media gateway controller No.>_1, TT=SCTP, PTHMODE=UNSUPP, LOCALIP=<Interface IP address>_1, LOCALPORT=<Local SCTP port No.>_1, PEERIP=<Peer Master address>_1, PEERPORT=<Peer SCTP port No.>_1, LINKNAME=AH248_1, FN=<Frame No.>, SN=<Slot No.>, BP=<Board Position>, SBN=<SubBoard No.>;
NOTE
By default, SubBoard No. is Mother Board. SubBoard No. is set to No. 0 SubBoard or No. 1 SubBoard 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 master MGC. Set path mode to Unsupported.If no dual-homing is configured, do not perform this step. ADD H248LNK: LINKID=<H248 signaling link No.>_2, VMGWID=<Virtual media gateway id>, MGCIDX=<Media gateway controller No.>_2, TT=SCTP, PTHMODE=UNSUPP, LOCALIP=<Interface IP address>_1, LOCALPORT=<Local SCTP port No.>_2, PEERIP=<Peer Master address>_2, PEERPORT=<Peer SCTP port No.>_2, LINKNAME=AH248_3, FN=<Frame No.>, SN=<Slot No.>, BP=<Board Position>, 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 two path or four path based on the actual conditions. By default, path mode is two path. If no dual homing is configured, the configuration is complete. ADD H248LNK: LINKID=<H248 signaling link No.>_1, VMGWID=<Virtual media gateway id>, MGCIDX=<Media gateway controller No.>_1, TT=SCTP, PTHMODE=<path mode>, 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 master MGC. Set path mode to two path or four path based on the actual conditions. By default, path mode is two path. ADD H248LNK: LINKID=<H248 signaling link No.>_2, VMGWID=<Virtual media gateway id>, MGCIDX=<Media gateway controller No.>_2, TT=SCTP, PTHMODE=<path mode>, 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
Example
Networking diagram
Figure 11-4 shows the typical networking. Figure 11-4 Networking diagram
Master MGC IP Network IP address 1: 192.168.0.1 IP address 2: 192.168.0.2 SCTP port No.: 3333 IP address 1: 172.16.0.1 IP address 2: 172.16.0.2 SCTP port No.: 2222 IP address 1: 10.1.1.1 IP address 2: 10.1.1.11 SCTP port No.: 3333/2222 UMG8900 Slave MGC
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;
Postrequisite
After configuring the H.248 links, go to activate the VMGW. 11.3 Activating the VMGW
11.2.3 Configuring the H.245 Link

This describes how to configure the control link over the H.245 protocol.
Prerequisite
l l l
The media gateway (MGW) control interface is correctly configured. The MGW data is correctly set. The H.248 link is correctly configured.
Data Planning
l
11-12
Issue 02 (2008-05-07)
Table 11-7 Input parameter Parameter Name IP address of gateway control interfaces Data <Interface IP address>_1 Input Source
l
Configuring Signaling Interfaces in Single-Frame Networking Mode Configuring Signaling Interfaces in SSM-256 Self-Cascading Mode Configuring Signaling Interfaces in SSM-32 Self-Cascading Mode Configuring Signaling Interfaces in SSM-256 and SSM-32 Mixed Cascading Mode Configuring Signaling Interfaces When E1 Physical Interfaces Carry IP Signaling Packets
Virtual media gateway ID Master MGC ID
<Virtual media gateway id> <Media gateway controller No.>_1 <Media gateway controller No.>_2 <Frame No.> <Slot No.> <Board Position>
Configuring MGW Data
Slave MGC ID
Frame No. Slot No. Board position
Configuring Frames and Boards Configuring Frames and Boards Configuring Frames and Boards
Table 11-8 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. Table 11-8 Data planning Parameter Name IP address of the master MGC IP address of the slave MGC UMG8900 The same as that of the peer device The same as that of the peer device Interconnected Device (MGC) <Peer Master address>_1 <Peer Master address>_2
Issue 02 (2008-05-07)
11-13
Parameter Name Port No. to the master MGC Port No. to the slave MGC Port No. of H.245 signaling links to the master MGC Port No. of H.245 signaling links to the slave MGC H.245 signaling link No. to the master MGC H.245 signaling link No. to the slave MGC
UMG8900 The same as that of the peer device The same as that of the peer device <Local port No.>_1
Interconnected Device (MGC) <Peer port No.>_1 <Peer port No.>_2 The same as that of the peer device The same as that of the peer device -
<Local port No.>_2
<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 media gateway id>, MGCIDX=<Media gateway controller No.>_1, LOCALIP=<Interface IP address>_1, LOCALPORT=<Local port No.>_1, PEERIP=<Peer Master address>_1, PEERPORT=<Peer port No.>_1, FN=<Frame No.>, SN=<Slot No.>, BP=<Board Position>; 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 media gateway id>, MGCIDX=<Media gateway controller No.>_2, LOCALIP=<Interface IP address>_1, LOCALPORT=<Local UDP port No.>_1, PEERIP=<Peer Master address>_2, PEERPORT=<Peer port No.>_2, FN=<Frame No.>, SN=<Slot No.>, BP=<Board Position>; ----End
Example
11-14
Issue 02 (2008-05-07)
Figure 11-5 Networking Examples

Master MGC IP Network IP address: 192.168.0.1 Port No. of H.245 links: 5000 IP address: 172.16.0.1 Port No. of H.245 links: 5001 Slave MGC
IP address: 10.1.1.1 Port No. of H.245 links: 5000/5001 UMG8900
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;
Postrequisite
After configuring the H.245 links, go to activate the VMGW. Activating the VMGW
11.3 Activating the VMGW

This describes how to activate the virtual media gateway (VMGW) on which the H.248 link is configured.
Prerequisite
l l l
The media gateway (MGW) control interface is correctly configured. The MGW data is correctly set. The H.248 link is correctly configured.
Data Planning
l
Table 11-9 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 11-9 Input parameter Parameter Name Virtual media gateway ID Data <Virtual media gateway id> Input Source Configuring MGW Data
Issue 02 (2008-05-07)
11-15
Procedure
Run ACT VMGW to activate the VMGW. ACT VMGW: VMGWID=<Virtual media gateway id>; ----End
Example
Example script
ACT VMGW: VMGWID=0;
Postrequisite
After configuring the MGW control data, configure the bearer data.
11-16
Issue 02 (2008-05-07)
12
About This Chapter
Configuring TDM Bearer
This describes how to configure the time division multiplexing (TDM) bearer data including the TDM interface, TDM timeslot, TDM trunk group management, and office direction information. In the actual networking application, the service exchange between the UMG8900 and and public switching telephone network (PSTN) switch is based on the TDM bearer. The connection between the UMG8900 and other media gateways (MGWs) can also be based on the TDM bearer. 12.1 Configuring the TDM Interface This describes how to configure the time division multiplexing (TDM) interface including how to configure the E1/T1 interface, E3/T3 interface, synchronous digital hierarchy (SDH) interface, and SDH interface protection. 12.2 Configuring the TDM Timeslot This describes how to configure the time division multiplexing (TDM) timeslot. 12.3 Configuring Trunk Group Management This describes how to configure the time division multiplexing (TDM) trunk group management. 12.4 Configuring Office Direction Information This describes how to configure the office direction information.
Issue 02 (2008-05-07)
12-1
12.1 Configuring the TDM Interface

This describes how to configure the time division multiplexing (TDM) interface including how to configure the E1/T1 interface, E3/T3 interface, synchronous digital hierarchy (SDH) interface, and SDH interface protection. 12.1.1 Configuring the E1/T1 Interface This describes how to configure the E1/T1 interface. 12.1.2 Configuring the E3/T3 Interface This describes how to configure the E3/T3 interface. 12.1.3 Configuring the SDH Interface on the S2L/S1L This describes how to configure the synchronous digital hierarchy (SDH) interface data. You need to configure the physical interface based on the actual physical connection. If you use the SDH interface of the S2L/S1L to access services, configure the SDH/synchronous optical network (SONET) optical interface. 12.1.4 Configuring SDH Interface Protection This describes how to configure the synchronous digital hierarchy (SDH) interface protection data.
12.1.1 Configuring the E1/T1 Interface

This describes how to configure the E1/T1 interface.
Prerequisite
l l
The hardware data is correctly set. The MGW control data is correctly set.
Data Planning
l
Table 12-1 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 12-1 Input parameter Parameter Name Frame ID Slot No. Data <Frame No.> <Slot No.> Input Source 8 Configuring Frames and Boards 8 Configuring Frames and Boards
12-2
Issue 02 (2008-05-07)
Table 12-2 Data planning Parameter Name Start port No. End port No. Frame format Tx line code structure Rx line code structure Distance Mode UMG8900 <Start Port No.> <End Port No.> <Frame Structure> <Tx line Code Structure> <Rx line Code Structure> <Distance Mode> Interconnected Device The same as that of the peer device The same as that of the peer device The same as that of the peer device -
Procedure
Run SET E1PORT to set the E1/T1 interface. SET E1PORT: FN=<Board No.>, SN=<Slot No.>, SPN=<Start Port No.>, EPN=<End Port No.>, FS=<Frame Structure>, TXCS=<Tx line Code Structure>, RXCS=<Rx line Code Structure>, DISTANCE=<Distance Mode>; ----End
Example
Example 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;
Postrequisite
After 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.1.2 Configuring the E3/T3 Interface

This describes how to configure the E3/T3 interface.
Prerequisite
l l
Issue 02 (2008-05-07)
12-3
Data Planning
l
Table 12-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. Table 12-3 Input parameter Parameter Name Frame ID Slot No. Data <Frame No.> <Slot No.> Input Source 8 Configuring Frames and Boards 8 Configuring Frames and Boards
Table 12-4 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. Table 12-4 Data planning Parameter Name Start port No. End port No. Distance Mode frame type Start channel No. End channel No. Frame format UMG8900 <Start Port No.> <End Port No.> <Communication Distance> <Frame type> <Start Chan No.> <End Chan No.> <Frame mode> Interconnected Device The same as that of the peer device The same as that of the peer device
Procedure
Step 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=<End Port 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=<End Port 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 Port No.>, SCN=<Start Chan No.>, ECN=<End Chan No.>, FRM=<Frame mode>;

NOTE
l l
For E1 load type, that is in the G.747 or E3 mode, the parameters Double-Frame and CRC4Multiframe are optional. For T1 load type, that is in the T3 mode, the parameters SuperFrame and Extended-SuperFrame are optional.
----End
Example
Example 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;
Postrequisite
After 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/S1L

This describes how to configure the synchronous digital hierarchy (SDH) interface data. You need to configure the physical interface based on the actual physical connection. If you use the SDH interface of the S2L/S1L to access services, configure the SDH/synchronous optical network (SONET) optical interface.
Prerequisite
l l
Context
To ensure normal running of SDH/SONET transport channels, the UMG8900 has to keep consistent 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 and J0 bytes.
l
The C2 byte specifies the multiplexing structure and payload status of a VC frame, such as whether channels being loaded, bearer service type and mapping mode. The J2 byte is used to send lower order path access point identifier repeatedly to convince the receiver that the connection to the sender end is normal. The J1 byte is used to send higher order path access point identifier repeatedly to convince the receiver that the connection to the sender is normal. The J0 byte is used to send the access point identifier of the sending section repeatedly to convince the receiver that the connection to the sender is normal.
Issue 02 (2008-05-07)
Data Planning
l
Table 12-5 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 12-5 Input parameter Parameter Name Frame No. Board No. Slot No. Data <Frame No.> <Board No.> <Slot No.> Input Source Configuring Frames and Boards Configuring Frames and Boards Configuring Frames and Boards
Table 12-6 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. Table 12-6 Data planning Parameter Name SDH port No. E1/T1 channel No. Receiving C2 byte Transmitting C2 byte Receiving J0 byte Transmitting J0 byte Receiving J1 byte Transmitting J1 byte Receiving J2 byte Transmitting J2 byte Frame type Frame mode 1 UMG8900 <SDH port No.> <Channel No.> <Receiving C2 byte> <Transmitting C2 byte> <Receiving J0 byte> <Transmitting J0 byte> <Receiving J1 byte> <Transmitting J1 byte> <Receiving J2 byte> <Transmitting J2 byte> <Frame type> <Frame mode 1> Interconnected Device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device
12-6
Issue 02 (2008-05-07)
Parameter Name Load type Start Channel No. End Channel No. E1/T1 Frame format Period Status
UMG8900 <Load type> <Start Channel No.> <End Channel No.> <Frame format> <Period> <Status>
Interconnected Device The same as that of the peer device -
Table 12-7 lists the parameters output to other steps. Table 12-7 Data output Parameter Name SDH port No. Data <SDH port No.>
Procedure
Step 1 Run SET SDHFLAG to set the overhead bytes of the SDH interface. Configure the TDM interface, 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 mode 1>, 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 Channel No.>, ENDCN=<End Channel No.>, FRAME=<Frame format>; Step 4 Run SET PERMON to set the performance monitoring state to 15 minutes or 24 hours based on 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 for performance monitoring. Otherwise, this step needs not be performed. Generally, the detection is performed immediately.
Issue 02 (2008-05-07)
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
Example
SET SET SET SET SDHFLAG: BT=S2L, BN=0, PN=0, RxC2=2, TxC2=2, RxJ1="1111", TxJ1="1111"; S2LPORT: BT=S2L, BN=0, FT=SDH, MODE=HUAWEI, TYPE=E1; S2LFRM: BT=S2L, BN=0, PN=PORT0, SRTCN=0, ENDCN=0, FRAME=CEPT_BASIC_MODE; PERMON: BT=S2L, BN=0, PN=PORT0, PERD=P15MIN, STAT=DISABLE;
Postrequisite
After configuring the SDH interface, configure the SDH interface protection. Configuring SDH Interface Protection
12.1.4 Configuring SDH Interface Protection

This describes how to configure the synchronous digital hierarchy (SDH) interface protection data.
Prerequisite
l l l
The hardware data is correctly set. The MGW control data is correctly set. The SDH interface data is correctly set.

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 PGID TYPE SET WRTIME PGID WRTIME
ADD PGIF FN/SN/IFN PGID
SET SIGDEFECT PGID SDFLAG
SET PG PGID CMD
12-8
Issue 02 (2008-05-07)
Data Planning
l
Table 12-8 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 12-8 Input parameter Parameter Name Frame No. Slot No. SDH port No. Data <Frame No.> <Slot No.> <SDH port No.> Input Source Configuring Frames and Boards Configuring Frames and Boards Configuring SDH Interface on the S2L/ S1L
Table 12-9 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. Table 12-9 Data planning Parameter Name Protection group No. Interface type Recover mode Operate mode Optical splitter mode Channel number Recover time length (s) SD flag Interface ID Channel ID Operate mode UMG8900 <Protect group ID> <Interface type> <Recover mode> <Operate mode> <Optical Splitter mode> <Channel number> <Recover time length(s)> <SD flag> <Interface No.> <Work/Protect Channel ID> <Command type>
Table 12-10 lists the parameters output to other steps. Table 12-10 Data output Parameter Name Protection group No. Data <Protect group ID>
Issue 02 (2008-05-07)
12-9
Procedure
Step 1 Run ADD PG to configure the protection group. For Protect type, you can select APS1PLUS1, APS1VSN, NONAPS1PLUS1 or NONAPS1VSN.
CAUTION
When APS1PLUS1 is selected, configure the boards to work in master/slave mode. If work channels fail, switch over boards directly to start the protect channel. Therefore, all interfaces of 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 in master/slave mode. The work channel is configured on the master board and the protect channel 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 loadsharing 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 SD flag 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 protection channel No. in the protection group is always 0. ADD PGIF: FN=<Frame No.>, SN=<Slot No.>, IFN=<SDH port No.>, PGID=<Protect group 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
Example
Example script
l
Configure interface protection in APS 1+1 mode

12-10
//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;
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 Timeslot

This describes how to configure the time division multiplexing (TDM) timeslot.
Prerequisite
The TDM interface data is correctly set.
Data Planning
l
Table 12-11 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 12-11 Input parameter Parameter Name Board type Board No. Virtual media gateway ID Data <Board type> <Board No.> <Virtual media gateway id> Input Source 8 Configuring Frames and Boards 8 Configuring Frames and Boards 11.1 Configuring MGW data
Issue 02 (2008-05-07)
12-11
Table 12-12 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. Table 12-12 Data planning Parameter Name Start TID End TID CASATTR No. UMG8900 <Start TID> <End TID> <CASATTR No.>
Table 12-13 lists the parameters output to other steps. Table 12-13 Data output Parameter Name Start TID End TID Data <Start TID> <End TID>
Procedure
Run 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 type to 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 access mode (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 to V5. 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 channel associated 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.
12-12
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
Example
Example 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;
Postrequisite
After configuring the TDM timeslot, configure the TDM trunk group management and office direction information based on the requirements.
l l
12.3 Configuring Trunk Group Management 12.4 Configuring Office Direction Information
If not required, configure the TDM bearer and then configure other bearer data.
l l
13 Configuring IP Bearer 14 Configuring Signaling Transfer
12.3 Configuring Trunk Group Management

This describes how to configure the time division multiplexing (TDM) trunk group management.
Prerequisite
l l
The TDM interface data is correctly set. The TDM timeslot is correctly configured.
Context
CAUTION
For the trunk group configuration, the UMG8900 and the interconnected media gateway controller (MGC) must support the function of circuit wild routing; otherwise, the service is interrupted.
Issue 02 (2008-05-07)
12-13
The trunk group indicates the TID resource pool configured on the UMG8900. The trunk group management function enables the UMG8900 to choose the TID function in the specific range on 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 specific call to the VMGW. In this case, the TID resource is set to belong to the VMGW by running ADD 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 TID resource when the MGC applies for TID resource with a VMGW. In this case, one TID range or a trunk group is required to send the messages to the VMGW. Then the VMGW allocates the available TID resources to calls according to certain rules within the specific range and finishes the connection of calls with the TID resources. In other words, the TID belongs to the VMGW before the call is over. After the call, the TID resource can be released for availability of other VMGWs.
Data Planning
l
Table 12-14 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. Table 12-14 Data planning Parameter Name Trunk group No. Trunk group information Start TID End TID UMG8900 <TG No.> <TG No. Info> <Start 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 types of 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 trunk group. The number of TIDs in the trunk group is unlimited. The TIDs can assigned to multiple ports. ADD TGTID: TGNO=<TG No.>, TIDB=<Start TID>, TIDE=<End TID>;
NOTE
l l
When a TID termination is added to a trunk group, the VMGW No. to which it belongs is invalid. The VMGW to which it belongs is determined when the CMU sends the networking message. The MGC can specify the range in multiple ways when allocating timeslots, including by trunk group No., by frame No./slot No./optical port No./port No. in hierarchy or by TID range. The MGC can also specify a specific TID.
----End
Example
Example 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;
Postrequisite
After configuring the TDM trunk group management data, configure the office direction information based on the requirements. 12.4 Configuring Office Direction Information If not required, configure IP bearer data. 13 Configuring IP Bearer
12.4 Configuring Office Direction Information

This describes how to configure the office direction information.
Prerequisite
l l
The TDM interface data is correctly set. The TDM timeslot is correctly configured.
Context
If a straight voice circuit exists between a switching office and the UMG8900, the switching office is an office direction of the UMG8900. The configuration in this step does not affect service provisioning; however, it is recommended that you configure this information so that office names can be displayed in related alarms, thus facilitating management. Configuring office direction information on the UMG8900 is to identify the office to which the port on the TDM interface board is connected. In this way, maintenance staff can know the office direction that the trunk circuit belongs to by checking the configuration information.
Data Planning
l
Table 12-15 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 12-15 Input parameter Parameter Name Board No. Data <Board No.> Input Source 8 Configuring Frames and Boards
Issue 02 (2008-05-07)
Table 12-16 Data planning Parameter Name Office No. Port No. Start port No. End port No. UMG8900 <Office No.> <Port No.> <Start 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 Port No.>, 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 as an example. ADD OFCNAME: OFCNO=<Office No.>, OFCINFO="AMGW1"; ----End
Example
Example 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";
Postrequisite
After configuring the office direction information, configuring the time division multiplexing (TDM) bearer is complete. Then, configure IP bearer data. 13 Configuring IP Bearer
12-16
Issue 02 (2008-05-07)
13
About This Chapter
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 bearer data when the UMG8900 acts as a media gateway (MGW) in the core network and the connections with other MGWs in the core network are based on the IP bearer. 13.1 Configuring IP Interface This 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 Address This describes how to configure the Internet Protocol (IP) interface address. 13.3 Configuring IP Interface Protection This describes how to configure the Internet Protocol (IP) interface protection. 13.4 Configuring the Gateway Address This describes how to configure the gateway address.
Issue 02 (2008-05-07)
13-1
13.1 Configuring IP Interface

This 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 Interface This describes how to configure the fast Ethernet (FE) interface. 13.1.2 Configuring the GE Interface This describes how to configure the gigabit Ethernet (GE) interface. 13.1.3 Configuring the ATM Interface This describes how to configure the asynchronous transfer mode (ATM) interface. 13.1.4 Configuring the IP over E1 Interface This describes how to configure the IP over E1 (IPoE1) interface.
13.1.1 Configuring the FE Interface

This describes how to configure the fast Ethernet (FE) interface.
Prerequisite
l l
Context
The Local Area Network (LAN) includes networks such as the Ethernet and the token ring network. As an important LAN networking technology, the Ethernet is flexible and easy to be realized. 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 the UMG8900. Figure 13-1 Ethernet interface protocol stack
IP IEEE802.3/802.3u/802.3q/ 802.3z 100Base-TX 1000Base-SX/LX/LX-GL/ZX
13-2
Issue 02 (2008-05-07)
Data Planning
l
Table 13-1 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 13-1 Input parameter Parameter Name Board No. Data <Board No.> Input Source Configuring Frames and Boards
Table 13-2 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. Table 13-2 Data planning Parameter Name Interface ID VLAN ID MAC address IP address VLAN domain ID Bearer bandwidth Max transmission unit Duplex mode Domain UMG8900 <Interface No.> <VLAN ID> <MAC address> <IP address> <VLAN domain ID> <VLAN bear bandwidth(Kbps)> <The max. transmission unit> <Duplex mode> <Domain>
Procedure
Step 1 Run ADD IFVLAN to add the VLAN configuration of the Ethernet interface. Set Interface type to ETH, Board type to HRB. ADD IFVLAN: IFT=ETH,BT=HRB,BN=<Board No.>,IFN=<Interface No.>,VID=<VLAN ID>,VDOMAIN=<VLAN domain ID>,VBEARBW=<VLAN bear bandwidth(Kbps)>; Step 2 Run ADD VMAC to add the virtual MAC address. Set Interface type to ETH, Board type to HRB. 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 type to HRB.
ADD ARP: BT=HRB,BN=<Board No.>, IPADDR=<IP address>, MACADDR=<MAC address>; 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=<The max. transmission unit>, BEARBW=<VLAN bear bandwidth(Kbps)>, DUPLEX=<Duplex mode>, DOMAIN=<Domain>; ----End
Example
Example script
ADD 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) interfaces based 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 Interface

This describes how to configure the gigabit Ethernet (GE) interface.
Prerequisite
l l
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 an important 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.
Figure 13-2 Protocol stack of the Ethernet interface

IP IEEE802.3/802.3u/802.3q/ 802.3z 100Base-TX 1000Base-SX/LX/LX-GL/ZX
Data Planning
l
Table 13-4 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. Table 13-4 Data planning Parameter Name Interface ID VLAN ID MAC address IP address VLAN domain ID Bearer bandwidth Max transmission unit Duplex mode Domain Auto negotiation UMG8900 <Interface No.> <VLAN ID> <MAC address> <IP address> <VLAN domain ID> <VLAN bear bandwidth(Kbps)> <The max. transmission unit> <Duplex mode> <Domain> <Auto negotiation>
Issue 02 (2008-05-07)
13-5
Procedure
Step 1 Run ADD IFVLAN to add the VLAN configuration of the Ethernet interface. Set Interface Type to GE, Board Type to HRB. ADD IFVLAN: IFT=GE,BT=HRB,BN=<Board No.>,IFN=<Interface No.>,VID=<VLAN ID>,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 to HRB. 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 Interface Type to GE, Board Type to HRB. ADD ARP: BT=HRB,BN=<Board No.>, IPADDR=<IP address>, MACADDR=<MAC address>; 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
Example
Example script
ADD 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;
Postrequisite
After configuring the GE interface, configure other types of IP interfaces based on the requirements. 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.3 Configuring the ATM Interface

This describes how to configure the asynchronous transfer mode (ATM) interface.
Prerequisite
l l
13-6
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 different subnetwork, and IP protocol packets are carried over ATM Adaptation Layer 5 (AAL5). IPoA helps you to carry out the application of the IP-based network protocols and networks over the ATM network. By using IPoA, you can directly run the IP-based network protocol and network application 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.
Data Planning
l
Table 13-6 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. Table 13-6 Data planning Parameter Name SDH port No. C2 byte J0 byte J1 byte K1 byte UMG8900 <SDH port No.> <C2 byte> <J0 byte> <J1 byte> <K1 byte>
Issue 02 (2008-05-07)
Parameter Name K2 byte VPI VCI Default static MAP Source IP address Encapsulation protocol Destination IP address ATM interface No. Maximum transmission unit of the ATM interface Enable ATM interface CRC length
UMG8900 <K2 byte> <VPI> <VCI> <Default static MAP> <Source IP address> <Enc protocol> <Destination IP address> <Interface No.> <The max. transmission unit> <Interface enable> <Length of CRC>
Procedure
Step 1 Run SET SDHFLAG to set the overhead bytes of the SDH interface. Set Board Type to HRB. 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=<The max. transmission unit>, ENABLE=<Interface enable>, CRCLEN=<Length of CRC>; ----End
Example
Example script
SET SDHFLAG: BT=HRB, BN=0, PN=0, C2=0, ADD IPPVC: BT=HRB, BN=0, IFN=0, VPI=0, ADD IPMAP: BT=HRB, BN=0, IFN=0, VPI=0, MOD IPIF: IFT=ATM, BT=HRB, BN=0, IFN=0, CRCLEN=BITS32; J0="1111", J1="111111", K1=0, K2=2, SCR=NO; VCI=8, ENC=SNAP; VCI=8, DEF=YES, SRCIP="10.1.1.80"; MTU=1500, ENABLE=YES, DESP="ATM Interface",
13-8
Issue 02 (2008-05-07)
Postrequisite
After configuring the IPoA interface, configure other types of IP interfaces based on the requirements. 13.1.4 Configuring the IP over E1 Interface If not required, configure the IP interface address. 13.2 Configuring the IP Interface Address
13.1.4 Configuring the IP over E1 Interface

This describes how to configure the IP over E1 (IPoE1) interface.
Prerequisite
l l
Context
The communication network evolves towards the whole IP of the network. The whole IP implementation of the whole network can provide rich services based on IP, and greatly improve the voice quality. Some networking environments have only the time division multiplexing (TDM) transport network, but no IP bearer network, and carriers hope to construct a network of the whole IP. In this case, IP packets need to be transmitted over the TDM transmission network. IP over E1 indicates 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
Data Planning
l
Issue 02 (2008-05-07)
13-9
Table 13-7 Input parameter Parameter Name Board type Board No. Virtual media gateway ID Start TID End TID Interface IP address Interface IP address mask Data <Board type> <Board No.> <Virtual media gateway id> <Start TID> <End TID> <Interface IP address> <Interface IP address mask> Input Source Configuring Frames and Boards Configuring Frames and Boards Configuring MGW data Configuring the TDM Timeslot Configuring the TDM Timeslot Configuring the IP Interface Address Configuring the IP Interface Address
Table 13-8 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. Table 13-8 Data planning Parameter Name TDM optical port No. TDM port No. IOE internal port No. TDM start timeslot TDM end timeslot Serial interface ID Route type Destination IP address Route No. Transmitting board type Transmitting board No. Transmitting IP address VPI VCI UMG8900 <TDM opt port No.> <TDM port No.> <IOE internal TDM port No.> <Start timeslot> <End timeslot> <Serial Interface No.> <Routing Type> <Remote IP address> <Routing No.> <Transmitting board type> <Transmitting board No.> <Transmitting IP address> <VPI> <VCI>
13-10
Parameter Name Interface ID MP enable VT Interface No.
UMG8900 <Interface No.> <MP enable> <VT Interface No.>
Procedure
Step 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 port No.>, 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 to Inside. 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 board No.. 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. Run MOD IPIF to modify the attributes of the IP interface. Set Interface Type to SRL, Board Type to HRB. MOD IPIF: IFT=SRL, BT=HRB, BN=<Board No.>_2, IFN=<Interface No.>, IFMP=<MP enable>, VT=<VT Interface No.>; Step 5 Run ADD IPADDR to add the IP address of the VT interface. Set Interface Type to VT, Board Type 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 board type 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
Example
Networking diagram Figure 13-5 Networking diagram of IP over E1
192.168.0.1 IP 10.10.1.1 MGW 10.10.1.2 10.10.0.1 10.10.0.2 E1 10.10.1.3 10.10.1.4 10.10.0.3 10.10.0.4
MGC
MGW
Issue 02 (2008-05-07)
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 this example, one VT interface has two Serial interfaces, and one Serial interface has 31 channels. The maximum 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 and reduces the bandwidth occupied by the RTP packets to improve the transmission efficiency. After the Compressed Real-Time Protocol (CRTP) function is enabled, the route backup function of the interface is unavailable.
//Configure ADD IPADDR: ADD IPADDR: ADD IPADDR: ADD IPADDR: the IP address. BT=HRB, BN=0, IFT=VT, BT=HRB, BN=0, IFT=VT, BT=HRB, BN=0, IFT=VT, BT=HRB, BN=0, IFT=VT, IFN=0, IFN=1, IFN=2, IFN=3, IPADDR="10.10.0.1", MASK="255.255.255.0"; IPADDR="10.10.0.2", MASK="255.255.255.0"; IPADDR="10.1.1.1", MASK="255.255.255.0"; IPADDR="10.1.1.2", MASK="255.255.255.0";
13-12
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";
Postrequisite
After 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. Configuring the IP Interface Address
13.2 Configuring the IP Interface Address

This describes how to configure the Internet Protocol (IP) interface address.
Prerequisite
The IP interface is correctly configured.
Data Planning
l
Table 13-10 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. Table 13-10 Data planning Parameter Name Interface type Interface IP address Interface IP address mask Master or slave flag In VLAN Interface ID UMG8900 <Interface type> <Interface IP address> <Interface IP address mask> <Master or slave flag> <In VLAN> <Interface No.>
Table 13-11 lists the parameters output to other steps. Table 13-11 Data output Parameter Name Interface IP address Data <Interface IP address>
13-13
Issue 02 (2008-05-07)
Procedure
Run ADD IPADDR to configure the IP interface address. Configure the bearer IP interface address, and set Board Type to HRB. ADD IPADDR: BT=HRB, BN=<Board No.>, IFT=<Interface type>, IFN=<Interface No.>, IPADDR=<Interface IP address>, MASK=<Interface IP address mask>, FLAG=<Master or slave flag>, INVLAN=<In VLAN>; ----End
Example
Example script
ADD IPADDR: BT=HRB, BN=0, IFT=ETH, IFN=0, IPADDR="10.1.1.1", MASK="255.255.255.0", FLAG=MASTER, INVLAN=NO;
Postrequisite
After configuring the IP interface, decide whether to configurr IP interface protection based on the 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 Protection

This describes how to configure the Internet Protocol (IP) interface protection.
Prerequisite
l l
The IP interface is correctly configured. The IP interface address is correctly set.
Context
After codec transformation of the service data at the TDM side, the UMG8900 puts the data into IP packets and sends them to the packet core network through the HRB. The security of IP interfaces on the HRB is very important. Thus, backup protection must be configured on the IP interfaces and links. Figure 13-6 shows the access of the UMG8900 to a core network.
13-14
Issue 02 (2008-05-07)
Figure 13-6 Access of the UMG8900 to a core network

Remote UMG8900 Master Local UMG8900 MHRU MHRU E8T/E1G E8T/E1G IP Core Net Slave FE/GE POS FE/GE Master MHRU+E8T/E1G MHRU+E8T/E1G Slave
The local UMG8900 is often connected with one router or layer 3 switches in the core network through the master and slave FE/GE interfaces respectively. The local UMG8900 interworks with the remote UMG8900. The reliability of the local links must be considered for the UMG8900. That is, if a link or interface between the UMG8900 and the router fails, the UMG8900 can quickly detect the failure and switch services from the master faulty link or interface to the slave link or interface.
Figure 13-7 shows the configuration procedure for IP interface protection of the UMG8900. Figure 13-7 Configuration procedure for IP interface protection
Start
Configure BFD (optional)
Configure route backup
Configure protection groups
End
Data Planning
l
Issue 02 (2008-05-07)
13-15
Table 13-12 Input parameter Parameter Name Board type Board No. Interface IP address Frame ID Slot No. Data <Board type> <Board No.> <Interface IP address> <Frame No.> <Slot No.> Input Source 8 Configuring Frames and Boards 8 Configuring Frames and Boards 13.2 Configuring the IP Interface Address 8 Configuring Frames and Boards 8 Configuring Frames and Boards
Table 13-13 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. Table 13-13 Data planning Parameter Name Interface type Interface ID BFD configuration name Detect type Source IP address Destination IP address Domain Protection group No. Recover mode Operate mode Optical splitter mode Channel number Recover time length (s) SD flag Interface ID Channel ID UMG8900 <Interface type> <Interface No.> <BFD configuration name> <Detect type> <Source IP address> <Destination IP address> <Domain> <Protect group ID> <Recover mode> <Operate mode> <Optical Splitter mode> <Channel number> <Recover time length(s)> <SD flag> <Interface No.> <Work/Protect Channel ID>
13-16
Issue 02 (2008-05-07)
Procedure
Step 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=<Interface No.>, BFDNM=<BFD configuration name>, TYPE=<Detect type>, SRCIP=<Source IP address>, DSTIP=<Destination IP address>; If... The route backup protection mode is used The protection group mode of the IP interface is used Then... Step 2 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:N protection 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 SD flag 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 protection channel No. in the protection group is always 0. ADD PGIF: FN=<Frame No.>, SN=<Interface No.>, IFN=<Interface No.>, PGID=<Protect group 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 Instances
Example script
NOTE
Nos. and IP addresses of interfaces in the same positions on the master and slave boards are the same, and the 1+1 non-APS protection is supported automatically.
Issue 02 (2008-05-07)
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";
ATM Interface Protection

ADD SET SET ADD ADD ADD ADD SET PG: PGID=0, IFT=ATM, TYPE=NONAPS1VSN, CHNNUM=1; WRTIME: PGID=0, WTIME=6; SIGDEFECT: PGID=0, SDFLAG=SD_ENABLE; PGIF: FN=2, SN=12, IFN=0, PGID=0, CHN=0; PGIF: FN=2, SN=11, IFN=0, PGID=0, CHN=1; PGIF: FN=2, SN=10, IFN=0, PGID=0, CHN=2; PGIF: FN=2, SN=9, IFN=0, PGID=0, CHN=3; PG: PGID=0, CMDT=START_CONTROLLER;
GE Interface Protection
NOTE
The GE interface on the MHRU supports only the independent backup mode. The interfaces provided by the master and slave MHRUs are uniformly numbered. The interfaces in the even slots are numbered first and then the interfaces in the odd slots are numbered. For example, the GE interface of 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 are numbered 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 and protection channel by using configuration commands. The configuration of the 1+1 non-APS protection 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 Address

This describes how to configure the gateway address.
Prerequisite
l l
The IP interface is correctly configured. The IP interface address is correctly set.
Data Planning
l
13-18
Issue 02 (2008-05-07)
Table 13-14 Input parameter Parameter Name Board No. Local IP address Data <Board No.> <Interface IP address> Input Source Configuring Frames and Boards Configuring the IP Interface Address
Table 13-15 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. Table 13-15 Data planning Parameter Name IP address of the gateway If aging or not UMG8900 <Gateway IP> <If aging or not>
Procedure
Run 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
Example
Example script
ADD GWADDR: BT=HRB, BN=0, IPADDR="10.1.10.1", GWIP="10.1.10.254", TIMEOUT=NoAging;
Postrequisite
After configuring the gateway interface address, configure the internet protocol (IP) bearer is complete. After configuring the bearer data, configure the signaling transfer. Configuring Signaling Transfer
Issue 02 (2008-05-07)
13-19
14
Configuring Signaling Transfer
About This Chapter

This describes how to configure the signaling transfer data. The UMG8900 is embedded with a signaling gateway (SG) and supports the signaling transfer function. In some networking applications, to reduce connections between network elements, no physical connection exists between the media gateway controller (MGC) and the remote devices. The signaling data between the two connected devices are transferred by the UMG8900. In this case, you need to set signaling transfer on the UMG8900. 14.1 Configuring SIGTRAN over L2UA This 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 Layer 3 (MTP3) and MTP3 User Adaptation Layer (M3UA). 14.3 Configuring Semi-Permanent Connection This describes how to configure the semi-permanent connection to transfer signaling. 14.4 Configuring CAS This describes how to configure the channel associated signaling (CAS).
Issue 02 (2008-05-07)
14-1
14.1 Configuring SIGTRAN over L2UA

This 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-M2UA This 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-V5UA This 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-IUA This describes how to configure the signaling transfer between Q.921 and ISDN Q.921-User Adaptation Layer (IUA).
14.1.1 Configuring SIGTRAN over MTP2-M2UA

This describes how to configure the signaling transfer between message transfer part layer 2 (MTP2) and MTP2 user adaptation (M2UA).
Prerequisite
The signaling transport (SIGTRAN) interface is correctly configured.
Context
The M2UA networking mode is applicable to networks with small signaling capacity. It has the features like scatter access and centralized control; however, centralized monitoring on signaling is hard to implement, which affects maintenance and management of the network. This networking mode is suitable for interworking between broadband and narrowband signaling of circuit-related services, especially for interworking between different carriers. Figure 14-1 shows the embedded SG for signaling adaptation and transfer of the UMG8900 in MTP2-M2UA mode.
14-2
Issue 02 (2008-05-07)
Figure 14-1 Signaling adaptation and transfer in MTP2-M2UA mode

MSC/PSTN Switch S7UP MTP3 MTP2 MTP1 TDM M2UA-NIF MTP2 MTP1 M2UA SCTP IP MAC IP SS7 UMG8900 IP MGC
S7UP MTP3 M2UA SCTP IP MAC
M2UA: MTP2 User Adaptation Layer SCTP: Stream Control Transmission Protocol MAC: media access control
MTP: Message Transfer Part
S7UP: SS7 User Part
NIF: nodal interworking function MGC: media gateway controller
The SIGTRAN configuration of the UMG8900 based on the M2UA link includes the following two parts:
l l
Configuration of the M2UA link to the MGC Configuration of the MTP2 link to the PSTN switch

Figure 14-2 shows the index mapping of the configuration command parameters of the signaling gateway (SG) over M2UA. Figure 14-2 Index mapping of the configuration command parameters over M2UA
ADD L2UALKS LKS PROTYPE ADD L2UALNK LKS PROTYPE LNKNO LOCALIP1 LOCALPN REMOTEIP1 REMOTERN ADD MTP2LNK LKS BINIFID TEXTIFID LNKTYPE STRTTS ENDTS
Issue 02 (2008-05-07)
14-3
Data Planning
l
Table 14-1 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 14-1 Input parameter Parameter Name IP address 1 of SIGTRAN interfaces Data <Interface IP address>_1 Input Source
l
10.1 Configuring the Physical Interface in Single-Frame Networking Mode 10.2 Configuring the Physical Interface in SSM-256 Self-Cascading Mode 10.3 Configuring the Physical Interface in SSM-32 Self-Cascading Mode 10.4 Configuring the Physical Interface in Mixed Cascading Mode 10.5 Configuring the E1 Physical Interface Carrying IP Signaling Packets 10.1 Configuring the Physical Interface in Single-Frame Networking Mode 10.2 Configuring the Physical Interface in SSM-256 Self-Cascading Mode 10.3 Configuring the Physical Interface in SSM-32 Self-Cascading Mode 10.4 Configuring the Physical Interface in Mixed Cascading Mode
IP address 2 of SIGTRAN interfaces
Board type Transmitting board No. SPF board No. MTP2 interface board type MTP2 interface board No.
<Board type>_1 <Board No.>_1 <Board No.>_2 <Board type>_2 <Board No.>_3
8 Configuring Frames and Boards 8 Configuring Frames and Boards 8 Configuring Frames and Boards 8 Configuring Frames and Boards 8 Configuring Frames and Boards
14-4
Table 14-2 Data planning Parameter Name UMG8900 Interconnect ed Device 1 (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device Interconnect ed Device 2 (DNS) Interconnect ed Device 3 (BSC/PSTN Switch) -
Checksum and algorithm Link group No. Use text-type interface ID Work mode
<Checksum algorithm> <Link set No.> <Use text-type interface ID> <Traffic mode>
Link No. to the master MGC Link No. to the slave MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC IP address 1 of the master MGC IP address 2 of the master MGC IP address 1 of the slave MGC
<Link No.>_1 <Link No.>_2 <Local port No.>_1 <Local port No.>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device
<Remote port No.>_1 <Remote port No.>_2 <Remote address1>_1 <Remote address2>_1 <Remote address1>_2
Issue 02 (2008-05-07)
14-5
Parameter Name
UMG8900
Interconnect ed Device 1 (MGC) <Remote address2>_2 -
Interconnect ed Device 2 (DNS)
Interconnect ed Device 3 (BSC/PSTN Switch)
IP address 2 of the slave MGC Priority of the M2UA link to the master MGC Priority of the M2UA link to the slave MGC IP address of the DNS server Path Mode MTP2 link No. E1/T1 No. Start timeslot No. End timeslot No. Subboard No. Integer interface ID
The same as that of the peer device <Priority>_1
<Priority>_2
The same as that of the peer device <Path Mode> <Link No.> <E1T1 No.> <Start time slot> <End time slot>
<DNS IP address> -
The same as that of the peer device The same as that of the peer device -
<SPF subboard No.> <Int-type interface ID>
Procedure
l 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 master and slave MGCs respectively. Set Protocol type to M2UA. ADD L2UALKS: PROTYPE=M2UA, LKSNAME="AMGC1_1", LKS=<Link set No.>, TRANSTXTID=<Use text-type interface ID>, TM=<Traffic mode>; 3.
14-6
Check whether the SCTP multi-homing networking is adopted.

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=<Link No.>_1, LNKNAME=AMGC1_1, LKS=<Link set No.>, LOCALPN=<Local port No.>_1, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote port No.>_1, REMOTEIP1=<Remote address1>_1, PRIO=<Priority>_1; If dual homing is configured, run ADD L2UALNK to add an L2UA link to the slave MGC. Set Protocol type to M2UA.If no dual homing is configured, do not perform this step but perform Step 8. ADD L2UALNK: PROTYPE=M2UA, BN=<Board No.>_2, LNKNO=<Link No.>_2, LNKNAME=AMGC1_2, LKS=<Link set No.>, LOCALPN=<Local port No.>_2, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote port No.>_2, REMOTEIP1=<Remote address1>_2, PRIO=<Priority>_2; Run ADD L2UALNK to add an L2UA link to the master MGC. 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. ADD L2UALNK: PROTYPE=M2UA, BN=<Board No.>_2, LNKNO=<Link No.>_1, LNKNAME=AMGC1_1, LKS=<Link set No.>, LOCALPN=<Local port No.>_1, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IP address>_2, REMOTEPN=<Remote port No.>_1, REMOTEIP1=<Remote address1>_1, REMOTEIP2=<Remote address2>_1, PRIO=<Priority>_1, PTHMODE=<Path Mode>; If dual homing is configured, run ADD L2UALNK to add an L2UA link to the slave MGC. Set Protocol type to M2UA. Set Path Mode to TWO-PATH or FOURPATH based on the actual conditions. By default, Path Mode is TWO-PATH. If no dual homing is configured, do not perform this step but perform Step 8. ADD L2UALNK: PROTYPE=M2UA, BN=<Board No.>_2, LNKNO=<Link No.>_2, LNKNAME=AMGC1_2, LKS=<Link set No.>, LOCALPN=<Local port No.>_2, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IP address>_2, REMOTEPN=<Remote port No.>_2, REMOTEIP1=<Remote address1>_2, REMOTEIP2=<Remote address2>_2, PRIO=<Priority>_2, PTHMODE=<Path Mode>; When the remote address is expressed in the domain name, run SET DNSSVR to configure the DNS server. SET DNSSVR: FLAG=MASTER, IPADDR=<DNS IP address>; 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.>_3, E1T1N=<E1T1 No.>, STRTTS=<Start time slot>, ENDTS=<End time slot>,SPFBN=<Board No.>_2, SUBBN=<SPF subboard No.>, LNKTYPE=M2UA64K, LKS=<Link set No.>, BINIFID=<Int-type interface ID>;
5.
6.
7.
8.
Configuring the data to the PSTN switch 1.
----End
Example
Networking diagram
Figure 14-3 shows the typical networking. Figure 14-3 Networking diagram
Master MGC IP Network IP address: 192.168.0.1 SCTP port No.: 2000 PSTN switch TDM IP address: 10.1.1.1 SCTP port No. to the master MGC: 2000 UMG8900 SCTP port No. to the slave MGC: 3000 IP address: 172.16.0.1 SCTP port No.: 3000 Slave MGC
Example script
l
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;
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;
Postrequisite
After configuring the M2UA signaling transfer, configure other types of signaling transfer based on the requirements. If no signaling transfer is required, configuring the signaling transfer is complete.
l l l l l
14.1.2 Configuring SIGTRAN over LAPV5-V5UA 14.1.3 Configuring SIGTRAN over Q.921-IUA 14.2 Configuring SIGTRAN over M3UA (MTP3-M3UA) 14.3 Configuring Semi-Permanent Connection 14.4 Configuring CAS
14.1.2 Configuring SIGTRAN over LAPV5-V5UA

This describes how to configure the signaling transfer between V5 Signaling Processing Board (LAPV5) and V5 User Adaptation (V5UA).
Prerequisite
The SIGTRAN interface is correctly configured.
Context
When the UMG8900 is connected with the V5 access network, they communicate through the V5.2 signaling. The UMG8900 needs an embedded SG and uses the LAPV5-V5UA mode to adapt and transfer the V5.2 signaling. Refer to Figure 14-4. Figure 14-4 Signaling adaptation and transfer in LAPV5-V5UA mode
AN V5.2 UMG8900 IP MGC
V5.2
V5UA-NIF V5UA SCTP IP MAC IP
V5.2 V5UA SCTP IP MAC
LAPV5 TDM
LAPV5
V5UA: V5.2 User Adaptation Layer NIF: nodal interworking function SCTP: Stream Control Transmission Protocol
LAPV5: LAPV5 Data Link Layer MAC: media access control Protocol AN: access network MGC: media gateway controller
The SIGTRAN configuration of the UMG8900 based on the V5UA link includes the following two parts:
l l
Configuration of the V5UA link to the MGC Configuration of the LAPV5 link to the V5 access network

Figure 14-5 shows the index mapping of the configuration command parameters of the SG over V5UA.
Issue 02 (2008-05-07)
14-9
Figure 14-5 Index and interconnection mapping of the configuration command parameters of the SG over V5UA
ADD L2UALKS LKS PROTYPE ADD L2UALNK LKS PROTYPE LNKNO LOCALIP1 LOCALPN REMOTEIP1 REMOTERN ADD V5E1 LKS E1 ID E1 LNK ID ADD V5LNK E1 ID LNK NO TS
Data Planning
l
l
14-10
Issue 02 (2008-05-07)
Parameter Name IP address 2 of SIGTRAN interfaces
Data <Interface IP address>_2
Input Source
l
10.1 Configuring the Physical Interface in Single-Frame Networking Mode 10.2 Configuring the Physical Interface in SSM-256 SelfCascading Mode 10.3 Configuring the Physical Interface in SSM-32 SelfCascading Mode 10.4 Configuring the Physical Interface in Mixed Cascading Mode
Board type Transmitting board No. SPF board No. V5 interface board type V5 interface board No.
<Board type>_1 <Board No.>_1 <Board No.>_2 <Board type>_2 <Board No.>_3
Table 14-4 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. Table 14-4 Data planning Parameter Name UMG8900 Interconnected Device 1 (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device Interconnected Device 2 (V5 AN) -
Checksum and algorithm Link group No. Use text-type interface ID Work mode Link No. to the master MGC Link No. to the slave MGC
<Checksum algorithm> <Link set No.> <Use text-type interface ID> <Traffic mode> <Link No.>_1 <Link No.>_2
Issue 02 (2008-05-07)
14-11
Parameter Name
UMG8900
Interconnected Device 1 (MGC) The same as that of the peer device The same as that of the peer device <Remote port No.>_1 <Remote port No.>_2 <Remote address1>_1 <Remote address2>_1 <Remote address1>_2 <Remote address2>_2 -
Interconnected Device 2 (V5 AN) -
SCTP port No. to the master MGC SCTP port No. to the slave MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC IP address 1 of the master MGC IP address 2 of the master MGC IP address 1 of the slave MGC IP address 2 of the slave MGC Priority of the V5UA link to the master MGC Priority of the V5UA link to the slave MGC IP address of the DNS server Path Mode E1ID E1 link ID E1 No. V5UA link No. Timeslot No. Subboard No.
<Local port No.>_1 <Local port No.>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Priority>_1
<Priority>_2
The same as that of the peer device <Path Mode> <E1 ID> <E1 link ID> <E1 No.> <Link No.> <Time slot> <SPF sub-board No.>
<DNS-IP address> The same as that of the peer device -
14-12
Issue 02 (2008-05-07)
Procedure
l Configuring the data to the MGC 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 master and slave MGCs respectively. Set Protocol type to V5UA. ADD L2UALKS: PROTYPE=V5UA, LKSNAME="AMGC1_1", LKS=<Link set No.>, TRANSTXTID=<Use text-type interface ID>, TM=<Traffic mode>; 3. Check whether the SCTP multi-homing networking is adopted.
4.
Run ADD L2UALNK to add an L2UA link to the master MGC. Set Protocol type to V5UA. ADD L2UALNK: PROTYPE=V5UA, BN=<Board No.>_2, LNKNO=<Link No.>_1, LNKNAME="AMGC1_1", LKS=<Link set No.>, LOCALPN=<Local port No.>_1, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote port No.>_1, REMOTEIP1=<Remote address1>_1, PRIO=<Priority>_1;
5.
If dual homing is configured, run ADD L2UALNK to add an L2UA link to the slave MGC. Set Protocol type to V5UA. If no dual homing is configured, do not perform this step but perform Step 8. ADD L2UALNK: PROTYPE=V5UA, BN=<Board No.>_2, LNKNO=<Link No.>_2, LNKNAME="AMGC1_2", LKS=<Link set No.>, LOCALPN=<Local port No.>_2, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote port No.>_2, REMOTEIP1=<Remote address1>_2, PRIO=<Priority>_2;
6.
Run ADD L2UALNK to add an L2UA link to the master MGC. 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. ADD L2UALNK: PROTYPE=V5UA, BN=<Board No.>_2, LNKNO=<Link No.>_1, LNKNAME="AMGC1_1", LKS=<Link set No.>, LOCALPN=<Local port No.>_1, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IP address>_2, REMOTEPN=<Remote port No.>_1, REMOTEIP1=<Remote address1>_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 slave MGC. Set Protocol type to V5UA. Set Path Mode to TWO-PATH or FOURPATH based on the actual conditions. By default, Path Mode is TWO-PATH. If no dual homing is configured, do not perform this step but perform Step 8. ADD L2UALNK: PROTYPE=V5UA, BN=<Board No.>_2, LNKNO=<Link No.>_2, LNKNAME="AMGC1_2", LKS=<Link set No.>, LOCALPN=<Local port No.>_2, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IP address>_2, REMOTEPN=<Remote port No.>_2, REMOTEIP1=<Remote address1>_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 to configure the DNS server.
Issue 02 (2008-05-07)
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.>; Run ADD V5LNK to add the LAPV5 link. ADD V5LNK: LNKNO=<Link No.>, LNKNAME="AV5AN1_1", E1ID=<E1 ID>, TS=<Time slot>, SPFBN=<Board No.>, SUBBN=<SPF sub-board No.>;
2.
----End
Example
Master MGC IP Network IP address: 192.168.0.1 SCTP port No.: 2020 IP address: 172.16.0.1 SCTP port No.: 3020 Slave MGC
TDM
IP address: 10.1.1.1 SCTP port No. to the master MGC: 2020
V5 access device
UMG8900
SCTP port No. to the slave MGC: 3020
Example script
l
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;
Configuring the data to the V5 access network device

ADD 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;
Postrequisite
After configuring the V5UA signaling transfer, configure other types of signaling transfer based on the requirements. If no other signaling transfer is required, configuring the signaling transfer is complete.

l l l l
14.1.3 Configuring SIGTRAN over Q.921-IUA 14.2 Configuring SIGTRAN over M3UA (MTP3-M3UA) 14.3 Configuring Semi-Permanent Connection 14.4 Configuring CAS
14.1.3 Configuring SIGTRAN over Q.921-IUA

This describes how to configure the signaling transfer between Q.921 and ISDN Q.921-User Adaptation Layer (IUA).
Prerequisite
Context
When the UMG8900 accesses the PBX, the Q.921-IUA mode is used to adapt and transfer the PRA signaling. Figure 14-7 shows the PRA signaling adaptation and transfer of the UMG8900 in Q.921-IUA mode. Figure 14-7 Signaling adaptation and transfer in Q.921-IUA mode
PBX PRA UMG8900 IP MGC
Q.931 Q.921 L1 TDM
IUA-NIF Q.921 L1 IUA SCTP IP MAC IP
Q.931 IUA SCTP IP MAC
IUA: ISDN Q.921-User Adaptation Layer
Q.921: ISDN User-Network Interface Data Link Protocol
Q.931: ISDN User-Network Interface the Third Layer PBX: private branch exchange Protocol NIF: nodal interworking function SCTP: Stream Control Transmission Protocol
The SIGTRAN configuration of the UMG8900 based on the IUA link includes the following two parts:
l l
Configuration of the IUA link to the MGC Configuration of the Q.921 link to the PBX

Figure 14-8 shows the index mapping of the configuration command parameters of the signaling gateway (SG) over IUA.
Figure 14-8 Index and interconnection mapping of the configuration command parameters of the SG over IUA
ADD L2UALKS LKS PROTYPE ADD L2UALNK LKS PROTYPE LNKNO LOCALIP1 LOCALPN REMOTEIP1 REMOTERN ADD Q921LNK LKS BINIFID TEXTIFID TS
Data Planning
l
l
14-16
Issue 02 (2008-05-07)
Parameter Name IP address 2 of SIGTRAN interfaces
Data <Interface IP address>_2
Input Source
l
10.1 Configuring the Physical Interface in Single-Frame Networking Mode 10.2 Configuring the Physical Interface in SSM-256 SelfCascading Mode 10.3 Configuring the Physical Interface in SSM-32 SelfCascading Mode 10.4 Configuring the Physical Interface in Mixed Cascading Mode
Board type Transmitting board No. SPF board No.
<Board type>_1 <Board No.>_1 <Board No.>_2
Q.921 interface board <Board type>_2 type Q.921 interface board <Board No.>_3 No.
Table 14-6 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. Table 14-6 Data planning Parameter Name UMG8900 Interconnected Device 1 (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device Interconnec ted Device 2 (PBX) -
Issue 02 (2008-05-07)
14-17
Parameter Name
UMG8900
Interconnected Device 1 (MGC) The same as that of the peer device The same as that of the peer device <Remote port No.>_1 <Remote port No.>_2 <Remote address1>_1 <Remote address2>_1 <Remote address1>_2 <Remote address2>_2 -
Interconnec ted Device 2 (PBX) -
SCTP port No. to the master MGC SCTP port No. to the slave MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC IP address 1 of the master MGC IP address 2 of the master MGC IP address 1 of the slave MGC IP address 2 of the slave MGC Priority of the IUA link to the master MGC Priority of the IUA link to the slave MGC Path mode IP address of the DNS server Q.921 link No. Integer interface ID E1/T1 No. Timeslot No.
<Local port No.>_1 <Local port No.>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Priority>_1
<Priority>_2
<Path Mode> <DNS-IP address> <Q921 Link No.> <Int-type interface ID> <E1T1 No.> <Time slot>
SPF subboard No. Network side and subscriber side
<SPF sub-board No.> <Net/User side>
14-18
Issue 02 (2008-05-07)
Procedure
l Configuring the data to the MGC 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 master and slave MGCs. Set Protocol type to IUA. ADD L2UALKS: PROTYPE=IUA, LKSNAME=AMGC1_1, LKS=<Link set No.>, TRANSTXTID=<Use text-type interface ID>, TM=<Traffic mode>; 3. Check whether the SCTP multi-homing networking is adopted.
4.
Run ADD L2UALNK to add an IUA link to the master MGC. Set Protocol type to IUA. ADD L2UALNK: PROTYPE=IUA, BN=<Board No.>_2, LNKNO=<Link No.>_1, LNKNAME=AMGC1_1, LKS=<Link set No.>, LOCALPN=<Local port No.>_1, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote port No.>_1, REMOTEIP1=<Remote address1>_1, PRIO=<Priority>_1;
5.
If dual homing is configured, Run ADD L2UALNK to add an IUA link to the slave MGC. Set Protocol type to IUA.If no dual homing is configured, do not perform this step but perform Step 8. ADD L2UALNK: PROTYPE=IUA, BN=<Board No.>_2, LNKNO=<Link No.>_2, LNKNAME=AMGC1_2, LKS=<Link set No.>, LOCALPN=<Local port No.>_2, LOCALIP1=<Interface IP address>_1, REMOTEPN=<Remote port No.>_2, REMOTEIP1=<Remote address1>_2, PRIO=<Priority>_2;
6.
Run ADD L2UALNK to add an IUA link to the master MGC. 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. ADD L2UALNK: PROTYPE=IUA, BN=<Board No.>_2, LNKNO=<Link No.>_1, LNKNAME=AMGC1_1, LKS=<Link set No.>, LOCALPN=<Local port No.>_1, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IP address>_2, REMOTEPN=<Remote port No.>_1, REMOTEIP1=<Remote address1>_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 slave MGC. Set Protocol type to IUA. Set Path Mode to TWO-PATH or FOURPATH based on the actual conditions. By default, Path Mode is TWO-PATH. If no dual homing is configured, do not perform this step but perform Step 8. ADD L2UALNK: PROTYPE=IUA, BN=<Board No.>_2, LNKNO=<Link No.>_2, LNKNAME=AMGC1_2, LKS=<Link set No.>, LOCALPN=<Local port No.>_2, LOCALIP1=<Interface IP address>_1, LOCALIP2=<Interface IP address>_2, REMOTEPN=<Remote port No.>_2, REMOTEIP1=<Remote address1>_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 to configure the DNS server.
Issue 02 (2008-05-07)
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=<Board No.>_2, SUBBN=<SPF sub-board No.>, NETUSER=<Net/User side>; ----End
Example
Master MGC IP Network IP address 1: 192.168.0.1 IP address 2: 192.168.0.2 SCTP port No.: 2010 IP address 1: 172.16.0.1 IP address 2: 172.16.0.2 SCTP port No.: 3010 Slave MGC
IP address 1: 10.1.1.1 IP address 2: 10.1.1.1 PBX UMG8900 SCTP port No. to the master MGC: 2010 SCTP port No. to the slave MGC: 3010
Example script
l
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;
Configuring the data to the PBX

ADD Q921LNK: LNKNO=0, LNKNAME="Q921-1", LKS=0, BINIFID=0, IFBT=E32, IFBN=0, E1T1N=0, TS=16, SPFBN=0, SUBBN=0, NETUSER=USER;
Postrequisite
After configuring the IUA signaling transfer, configure other types of signaling transfer based on the requirements. If no other signaling transfer is required, configuring the signaling transfer is complete.

l l l
14.2 Configuring SIGTRAN over M3UA (MTP3-M3UA) 14.3 Configuring Semi-Permanent Connection 14.4 Configuring CAS
14.2 Configuring SIGTRAN over M3UA (MTP3-M3UA)

This describes how to configure the signaling transfer data between Message Transfer Part Layer 3 (MTP3) and MTP3 User Adaptation Layer (M3UA).
Prerequisite
Context
The UMG8900 uses the MTP3-M3UA mode to adapt the SS7 user part (S7UP) signaling. The UMG8900 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 media gateway controller (MGC). In this case, configure the MTP3-M3UA signaling transfer on the UMG8900. Figure 14-10 shows the signaling adaptation and transfer of the UMG8900 in MTP3-M3UA mode. Figure 14-10 Signaling adaptation and transfer in MTP3-M3UA mode
BSC/PSTN Switch SS7 UMG8900 IP MGC
S7UP MTP3 MTP2 MTP1 TDM
M3UA-NIF MTP3 MTP2 MTP1 M3UA SCTP IP MAC IP
S7UP M3UA SCTP IP MAC
M3UA: MTP3 User Adaptation Layer SCTP: Stream Control Transmission Protocol MAC: media access control
S7UP: SS7 User Part
NIF: nodal interworking function MGC: media gateway controller

l
Figure 14-11 shows the index mapping of the major configuration command parameters of the signaling transfer over M3UA.
Issue 02 (2008-05-07)
14-21
Figure 14-11 Index mapping of the configuration commands of the signaling transfer based on M3UA
ADD M3LE ADD N7DSP INDEX NI DPC OSPINDEX ADD N7LKS DSPIDX INDEX ADD N7RT INDEX LKSIDX DSPIDX ADD N7LNK INDEX LKSIDX SLC MTP2NO ADD MTP2LNK LNKNO LET OPC NI LEX RC ADD M3DE LEX DEX NI DPC RC DET ADD M3LKS ADX LSX TM ADD M3RT DEX LSX ADD M3LNK BT BN LSX LIP1/LIP2 LP RIP1/RIP2 RP
Data Planning
l
14-22
Issue 02 (2008-05-07)
Table 14-7 Input parameter Parameter Name Signaling interface address 1 Data <Interface IP address>_1 Input Source
l
10.1 Configuring the Physical Interface in Single-Frame Networking Mode 10.2 Configuring the Physical Interface in SSM-256 SelfCascading Mode 10.3 Configuring the Physical Interface in SSM-32 SelfCascading Mode 10.4 Configuring the Physical Interface in Mixed Cascading Mode 10.5 Configuring the E1 Physical Interface Carrying IP Signaling Packets 10.1 Configuring the Physical Interface in Single-Frame Networking Mode 10.2 Configuring the Physical Interface in SSM-256 SelfCascading Mode 10.3 Configuring the Physical Interface in SSM-32 SelfCascading Mode 10.4 Configuring the Physical Interface in Mixed Cascading Mode
Signaling interface address 2
M3UA board type M3UA board No. Local signaling point code Local signaling point index MTP2 interface board type MTP2 interface board No.
<Board type>_1 <Board No.>_1 <OPC index> <Upper Limit of the Input Voltage Alarm (V) > <Board type>_2 <Board No.>_2
8 Configuring Frames and Boards 8 Configuring Frames and Boards 5 Configuring System Parameters 5 Configuring System Parameters 8 Configuring Frames and Boards 8 Configuring Frames and Boards
Issue 02 (2008-05-07)
14-23
Parameter Name SPF Board No.
Data <Board No.>_3
Input Source 8 Configuring Frames and Boards
Table 14-8 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. Table 14-8 Data planning Parameter Name Local entity index Local network ID Local Entity Type M3UA Destination entity index Network ID of the M3UA destination entity Destination Entity Type Destination signaling Point Code A-interface protocol number M3UA link set index Discard messages from lower priority link Working Mode M3UA signaling link No. to the master MGC UMG8900 <Local Entity Index> <Network Indicator> <Local Entity Type> <Destination Entity Index> The same as that of the peer device The same as that of the peer device <A-Interface Protocol Number> <Link Set Index> <Discard messages from lower priority link> <Working Mode> <M3UA Link No.>_1 Interconnected Device 1 (MGC) The same as that of the peer device <Network Indicator> Interconnected Device 2 (BSC) -
<Destination Entity Type> <Destination signaling Point Code> -
14-24
Issue 02 (2008-05-07)
Parameter Name M3UA signaling link No. to the slave MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC IP address 1 of the master MGC IP address 2 of the master MGC SCTP port No. to the master MGC IP address 1 of the slave MGC IP address 2 of the slave MGC SCTP port No. to the slave MGC Path mode N7 destination signal point index N7 destination Network indicator N7 DPC OPC index N7 link set index N7 route index MTP2 link No. E1/T1 No. Start timeslot No. Subboard No.
UMG8900 <M3UA Link No.>_2 <Local Port>_1 <Local Port>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Path Mode> The same as that of the peer device The same as that of the peer device The same as that of the peer device <OPC index> <Linkset index> <Route index> <Link No.> <E1T1 No.> <Start time slot> <SPF sub-board No.>
Interconnected Device 2 (BSC) -
The same as that of the peer device The same as that of the peer device <First Address of Remote End>_1 <Second Address of Remote End>_1 <Remote Port>_1 <First Address of Remote End>_2 <Second Address of Remote End>_2 <Remote Port>_2 -
<DSP index> <Network indicator> <DSP> The same as that of the peer device The same as that of the peer device -
Issue 02 (2008-05-07)
14-25
Parameter Name N7 link index N7 link code
UMG8900 <Link index> <Signaling link code>
Interconnected Device 2 (BSC) The same as that of the peer device
Procedure
l 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=<Local Entity Type>, NI=<Network Indicator>, OPC=<National network code>_1; Run ADD M3DE to add the M3UA destination entity. The master and slave MGCs share one signaling point. ADD M3DE: DEX=<Destination Entity Index>, DEN="AMGC1_1", DET=<Destination Entity Type>, NI=<Network Indicator>, DPC=<Destination signaling Point Code>, LEX=<Local Entity Index>;
2.
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 Route Context.
3.
Run ADD M3LKS to add the M3UA link set. If dual homing is configured, set Discard messages from lower priority link to DISCARD (YES). Otherwise, use the default value of Discard messages from lower priority link. ADD M3LKS: LSX=<Link Set Index>, LSN="AMGC1_1", ADX=<Destination Entity Index>, WM=<Working Mode>, DLP=<Discard messages from lower priority link>; Run ADD M3RT to add the M3UA route. ADD M3RT: RN="AMGC1_1", DEX=<Destination Entity Index>, LSX=<Link Set Index>; Check whether the SCTP multi-homing networking is adopted.
4.
5.
6.
Run ADD M3LNK to add a M3UA link destined to the master MGC. Set CS Mode to Server, Active Standby Flag to Active, and Priority to 0. ADD M3LNK: LNK=<M3UA Link No.>_1, BT=<Board type>_1, BN=<Board No.>_1, LKN="AMGC1_1", LIP1=<Interface IP address>_1, LP=<Local Port>_1, RIP1=<First Address of Remote End>_1, RP=<Remote Port>_1, CS=SERVER,LSX=<Link Set Index>, ASF=ACTIVE, PR=0; If dual homing is configured, run ADD M3LNK to add the M3UA link destined to the slave MGC. Set CS Mode to Server and Active Standby Flag to Active. 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, and thus set Priority to 1.If no dual homing is configured, do not perform this step but perform next step.
7.
14-26
ADD M3LNK: LNK=<M3UA Link No.>_2, BT=<Board type>_1, BN=<Board No.>_1, LKN="AMGC1_2", LIP1=<Interface IP address>_1, LP=<Local Port>_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 CS Mode to Server and Active Standby Flag to Active, and Priority to 0. Set Path Mode 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=<Board No.>_1, LKN="AMGC1_1", LIP1=<Interface IP address>_1, LIP2=<Interface IP 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 slave MGC. Set CS Mode to Server and Active Standby Flag to Active. 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, and thus set Priority to 1. Set Path Mode to TWOPATH or FOUR-PATH based on the actual conditions. By default, Path Mode is TWO-PATH. If no dual homing is configured, do not perform this step but perform next step. ADD M3LNK: LNK=<M3UA Link No.>_2, BT=<Board type>_1, BN=<Board No.>_1, LKN="AMGC1_2", LIP1=<Interface IP address>_1, LIP2=<Interface IP 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 device 1. 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=<DSP index>; 3. Run ADD N7RT to add the N7 route. ADD N7RT: INDEX=<Route index>, NAME="ABSC1_1", LKSIDX=<Linkset index>, 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 subboard 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 subboard No.>, LNKTYPE=MTP32M;
5.
Issue 02 (2008-05-07)
Run ADD N7LNK to add the N7 link.

ADD N7LNK: INDEX=<Link index>, NAME="ABSC1_1", LKSIDX=<Linkset index>, SLC=<Signaling link code>, MTP2NO=<Link No.>; ----End
Example
l
Signaling transfer example over M3UA Networking diagram Figure 14-12 shows the typical networking of the signaling transfer over M3UA.
Figure 14-12 Networking diagram of the signaling transfer over M3UA

Master MGC IP address: 192.168.0.1 SCTP port No.: 4000 SPC: bbbbbb Slave MGC IP Network IP address: 172.16.0.1 SCTP port No.: 5000 SPC: bbbbbb
IP address: 10.1.1.5 SCTP port No. to the master MGC: 4000 SCTP port No. to the slave MGC: 5000 SPC: aaaaaa PSTN switch SPC: cccccc UMG8900
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 switch

ADD 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;
14-28
Issue 02 (2008-05-07)
Postrequisite
After configuring the MTP3-M3UA signaling transfer, configure other types of signaling transfer based on the requirements. If no signaling transfer is required, configuring the signaling transfer is complete.
l l
14.3 Configuring Semi-Permanent Connection 14.4 Configuring CAS
14.3 Configuring Semi-Permanent Connection

This describes how to configure the semi-permanent connection to transfer signaling.
Prerequisite
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) signaling from a certain timeslot in the E1/synchronous digital hierarchy (SDH) trunk and then transparently transfer the SS7 signaling to the media gateway controller (MGC) through this E1 connection. 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 signaling through semi-permanent connections. The semi-permanent connections greatly expand the networking capability of the UMG8900. Figure 14-13 shows the signaling transparent transmission through the semi-permanent connection. Figure 14-13 Signaling transparent transmission through the semi-permanent connection
BSC/MSC/ PSTN Switch S7UP MTP3 MTP2 MTP1 TDM semi-connection TDM SS7 UMG8900 SS7 MGC
S7UP MTP3 MTP2 MTP1
MGC: media gateway controller
S7UP: SS7 User Part
Data Planning
l
Issue 02 (2008-05-07)
Table 14-9 Input parameter Parameter Name Board type Board No. Virtual media gateway ID Data <Board type> <Board No.> <Virtual media gateway id> Input Source Configuring Frames and Boards Configuring Frames and Boards Configuring MGW Data
Table 14-10 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. Table 14-10 Data planning Parameter Name UMG8900 Interconnected Device 1 (MGC) Interconnected Device 2 (BSC/ MSC/PSTN Switch) The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device
Start TID End TID Semi-permanent connection ID Semi-permanent connection name Interworking type Direction Source frame No. Source slot No. Source port No. Source timeslot No. Destination frame No. Destination slot No. Destination timeslot No.
<Start TID> <End TID> <ID> <Name> <Link type> <Direction> <Src frame No.> <Src slot No.> <Src port No.> <Src timeslot No.> <Dst frame No.> <Dst slot No.> <Dst port No.>
The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device
14-30
Issue 02 (2008-05-07)
Parameter Name
UMG8900
Interconnected Device 1 (MGC)
Interconnected Device 2 (BSC/ MSC/PSTN Switch) The same as that of the peer device
Destination timeslot No.
<Dst timeslot No.>
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=<End TID>, 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 frame No.>, DTSN=<Dst slot No.>, DPN=<Dst port No.>, DTS=<Dst timeslot No.>; ----End
Example
MGC
TDM
Timeslot 1-port 0-slot 12-frame 1 Timeslot 1-port 1-slot 12-frame 1 PSTN switch UMG8900
Example script
ADD 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;
Postrequisite
After configuring the semi-permanent connection signaling transfer, configure other types of signaling transfer based on the requirements. If no other signaling transfer is required, configuring the signaling transfer is complete.
Configuring CAS
14.4 Configuring CAS

This describes how to configure the channel associated signaling (CAS).
Prerequisite
The bearer data is correctly set.
CAS Adaptation
The application of CAS signaling varies with countries, and the great difference lies in the difference between physical signals and logical signals. For example, in the standard R2 signaling, a seizing signal corresponds to 0001, but, in Iranian signaling, it may be a 130ms pulse in bit A; in Indonesian signaling, the signal to request the calling number is A6, but, in Iraqi signaling, it is A5. The UMG8900 defines a semantic adaptation layer, carries out the mapping between different physical and logical signals through data configuration, and processes only the logical signals in the host software. By this means, the R2 CAS difference in term of signal meanings between different countries is shielded. At present, the UMG8900 supports the multinational adaptation of the R2 line signaling, R1 line signaling, and the register signaling, and the multinational adaptation of the R1.5 register signaling.
l
Signaling Conversion Index The key to carry out the multinational adaptation of signaling is to configure the mapping table between physical signals and logical signals. The mapping table is called signaling conversion index, and it includes the following four subindexes: 1. Line signaling conversion index When an outgoing or incoming trunk receives physical line signaling from the peer office, index query and judgment based on the state machine is required. The outgoing or incoming trunk converts physical line signaling codes to logical line signals (logical events). For example, Table 14-11 lists part of CSN1 line signaling conversion index. Table 14-11 CSN1 line signaling conversion index Index Physical Signaling Type LINE_SIG Physical Signal 1 Call State IDCR (clear request state) ODCR (outgoingtrunk clear request state) IDL (idle state) ... Logical Event SZ (seizing signal) RANSR (reanswer signal) FR (free signal) ...
2 2 ...
LINE_SIG LINE_SIG ...
3 5 ...
14-32
Issue 02 (2008-05-07)
In different call states, a physical signal parameter corresponds to different logical events. You must define all the physical line signals related to CSN1 one by one through ADD LRPT to set up a complete line signaling conversion index. 2. Line command conversion index When an outgoing or incoming trunk sends line signaling to the peer office, index query 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 2 2 2 ... Logical Command SZ RANSR FR ... Physical Signaling Type LINE_SIG LINE_SIG LINE_SIG ... Physical Signal 3 7 11 ... Sending Length of Signal 10 10 10 ...
The same logical commands correspond to the same physical signal. You must define all the logical line signals related to CSN1 one by one through ADD LSND to set up a complete line signaling command conversion index. 3. Register signaling conversion index When an incoming trunk receives physical register signaling from the peer office, index query and judgment based on the state machine is required. The incoming trunk converts 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 2 2 2 ... Register Signaling Code 1 2 3 ... Call State 1 1 1 ... Logical Event 11 11 12 ... Parameter 1 0 0 ...
The value of a register signaling code ranges from 1 to 15. The relevant physical register signals are decided by the system. In different call states, a signaling code corresponds to different logical events. You must define all the physical signaling codes related to CSN1 MFC one by one through ADD REGRPT to set up a complete register signaling conversion index.
4.
Register signaling command conversion index When an outgoing trunk sends register signaling to the peer office, index query is required for converting logical register signals to physical register signaling codes. For example, Table 14-14 lists part of CSN1 register signaling command conversion index. Table 14-14 CSN1 register command conversion index Index 2 2 2 ... Command 11 11 12 ... Parameter 1 0 0 ... Register Signaling Code 1 2 3 ...
In the table, "Command" indicates the logical event in the conversion index. You must define all the logical commands related to CSN1 MFC one by one through ADD REGSND to set up a complete register signaling command conversion index. All the MML commands for configuring signaling conversion index are grouped into a 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. You can execute the script file on site for configuring the signaling conversion index, and run ADD CASSIGNAL to reference the index No. in the signaling conversion index for defining the related CAS. For example, the script file of CSN1 signaling conversion index defines the following indexes 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 Signaling Name Standard R2 CSN1
14-34
Line Signaling Conversion Index 0 2
Line Command Conversion Index 0 2
Register Signaling Conversion Index 0 2
Register Command Conversion Index 0 2
Issue 02 (2008-05-07)
Signaling Name Australia R2 Thailand R2 Brunei R2 Brazil 5B R2 Brazil 5C R2 Chile R2
Line Signaling Conversion Index 0 4 0 3 3 2 5 (E&M long and short pulses) 2 (Ericsson responding metering pulse - incoming) 6 (Ericsson responding metering pulse - outgoing) 7 (Ericsson clearbackward metering pulse - outgoing) 1 (Ericsson clearbackward metering pulse - incoming)
Line Command Conversion Index 0 4 0 3 3 2 5 (E&M long and short pulses) 2 (Ericsson responding metering pulse - incoming) 6 (Ericsson responding metering pulse - outgoing) 7 (Ericsson clearbackward metering pulse - outgoing) 1 (Ericsson clearbackward metering pulse - incoming) 0 0 0 0 3
Register Signaling Conversion Index 3 4 1 3 (5B) 4 (5C) 2
Register Command Conversion Index 3 4 1 3 (5B) 4 (5C) 2
Indonesia R2
Mexico R2 Argentina R2 Peru R2 Sri Lanka R2 Venezuela R2

Issue 02 (2008-05-07)
0 0 0 0 3
6 1 5 7 3
6 1 5 7 3
14-35
Signaling Name Tunisia R2 India R2 Singapore R2
Line Signaling Conversion Index 0 0 5 6 (Metering pulse is not supported.) 7 (Metering pulse is supported.) 0 (FAS is the short pulse and the line signaling type is one bit.) 1 (FAS is the long pulse and the line signaling type is one bit.) 2 (FAS is the short pulse and the line signaling type is three bits.) 3 (FAS is the long pulse and the line signaling type is three bits.) 1 (The Seize ACK message is sent.) 2 (The Seize ACK message is not sent.)
Line Command Conversion Index 0 0 5 6 (Metering pulse is not supported.) 7 (Metering pulse is supported.) 0 (FAS is the short pulse and the line signaling type is one bit.) 1 (FAS is the long pulse and the line signaling type is one bit.) 2 (FAS is the short pulse and the line signaling type is three bits.) 3 (FAS is the long pulse and the line signaling type is three bits.) 1 (The Seize ACK message is sent.) 2 (The Seize ACK message is not sent.)
Register Signaling Conversion Index 3 6 5
Register Command Conversion Index 3 6 5
Czechoslov akia R2
Iran and Pakistan R1
American CAS
14-36
Issue 02 (2008-05-07)
Signaling Name
Line Signaling Conversion Index
Line Command Conversion Index
Register Signaling Conversion Index 1 (The register signaling type is the MFGP or MFS.)
Register Command Conversion Index 1 (The register signaling type is the MFGP or MFS.) 2 (The register signaling type is the MFP1.) 3 (The register signaling type is the MFP2.)
Russian R1.5
2 (The register signaling type is the MFP1.) 3 (The register signaling type is the MFP2.)
Configuring Pulse Data Pulse data must be configured in the CAS data. Generally, three types of pulse exist in CAS, 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 digitanalog conversion. Based on the diversification of pulses, feature parameters of a pulse should be configured in CAS. The same as the signaling conversion index, pulse parameter configuration is made into a script file based on signaling standards in different countries. The script file is contained in the line signaling script file. On site, the script file can be executed for configuring the pulse data. No on-site configuration is required. For example, Brazil R2 supports A-bit and 1-polarity metering pulse, and Table 14-16 lists the pulse properties of Brazil R2. Table 14-16 Brazil R2 metering pulse index Pulse Index 3 Pulse Bit A Pulse Polarity 1 High Level Width 15 (12-18) Low Level Width 15 (12-18) Pulse Interval (ms) 15
The pulse composite index of Brazil R2 is defined as 3, and the metering pulse is added in the pulse composite to complete the pulse configuration for Brazil R2. Configuration script is 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.
When the CAS and pulse data is configured, you should assign TDM timeslots for transmitting 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 l l
When the line signaling that is used contains line pulse, line pulse data configuration is required. When the called number is sent in the DP mode, DP data configuration is required. When the metering pulse is used, metering pulse data configuration is required.
Russia line signaling is complex. Therefore, Line signaling conversion index and Line command conversion index of Russian CAS supported by the UMG8900 are of the default settings, and you do not need to configure them. The ANI pulse and the inductive pulse are peculiar to Russian line signaling. You must run ADD ANIPULSE and ADD INDPULSE to configure the ANI pulse and the inductive pulse.
CAS Type
The CAS with specific common features can be grouped into one CAS type for use in the CAS attribute table. The features based on which CAS type is defined include signaling type, line signaling 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 name R2 Hong Kong IDAM Australia R2 Thailand R2 Signaling type R2 R2 R2 THAILAND_ R2 Line signaling L2B L2B L2B THAILAND_R2 or THAILAND_PBX Register signaling DTMF DTMF DTMF MFC Remarks None None None There are two types of R2 used in Thailand. THAILAND_R2 is more applicable, and THAILAND_PBX is mainly used to connecting with PBX. None None None None None None None
Issue 02 (2008-05-07)
Brunei R2 Brazil 5B R2 Brazil 5C R2 Chile R2 Indonesia R2 Mexico R2 Argentina R2

14-38
R2 BRAZIL_R2 BRAZIL_R2 CHILE_R2 R2 MEXICO_R2 R2
L2B L2B L2B L2B L2B L2B L2B
MFC MFC MFC MFC MFC MFC MFC
CAS name Peru R2 Sri Lanka R2 Venezuela R2 India R2 Singapore R2 Czech Republic R2 United States R1 Iran and Pakistan R1 R1.5
Signaling type R2 R2 R2 INDIA_R2 R2 CZECHOSL OVAK_R2 AMERICA_C AS IRAN_R1 R15
Line signaling L2B L2B L2B L2B L2B L2B L1B L1B or L3B TL_CAS2, TCL_CAS2, OCL_CAS2, CL_CAS2, TL_1VF, TCL_1VF, OCL_1VF, TL_CAS1, TCL_CAS1 or OCL_CAS1
Register signaling MFC MFC DTMF MFC MFC MFC DTMF or MFP DPMFP DP, MFGP, MFP1, MFP2, MFS, MFS_DP or MFS_MFP1
Remarks None None None None None None None None None
To configure the CAS, learn the signaling standards of a nation, such as the type of the used line signaling pulse, register signaling type, line signaling pulse parameter, sending power level when the MFC register signaling is used, backward pulse length, supported address sending and receiving sequence, and requirements for the length of various types of timers. Based on the information, the CAS can be smoothly configured. In addition, during the signaling configuration, Huawei technologies Co., Ltd (hereinafter referred to as Huawei) makes the scripts for some configuration data such as the pulse data and signaling conversion table. You can obtain the configuration script applicable to your own country from the software version before configuration. The software version includes multiple configuration scripts based on the signaling specifications of different countries, and thus you can select the configuration scripts applicable to your own country. Figure 14-15 shows the procedure for configuring the CAS.
Issue 02 (2008-05-07)
14-39
Figure 14-15 CAS configuration procedure

Start
Configure pulse data (optional) Configure CAS mapping table
Huawei scripts
Configure CAS types
Configure CAS attributes
Configure CAS timeslots
Configure CAS attributes of the UMG8900 (optional) Add country codes and region codes (optional) Add tariff codes (only for the Czechoslovakia R2n
End

Figure 14-16 shows the index mapping of the configuration command parameters of the signaling gateway (SG) over CAS.
14-40
Issue 02 (2008-05-07)
Figure 14-16 Index and interconnection mapping of the configuration command parameters of the SG over CAS
ADD REGRPT ID LEVD ADD REGSND ID CMD ADD LRPT ID PEVT ADD LSND ID LCMD ADD CASSIGNAL SIGNM ST LCM LSC RSCM RSSC ADD CASATTR ID SIGNM
ADD PULSE PID BIT
ADD PCMPLS ID LMP1-LMP8 DMP CMP ADD TDMIU RT=R1 / R2 CASNO PLSID
Data Planning
l
Table 14-18 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 14-18 Input parameter Parameter Name Board type Board No. Virtual media gateway ID Data <Board type> <Board No.> <Virtual media gateway id> Input Source 8 Configuring Frames and Boards 8 Configuring Frames and Boards 11.1 Configuring MGW data
Issue 02 (2008-05-07)
14-41
Table 14-19 Data planning Parameter Name Signaling name Signaling type Line signaling type Register signaling type CAS attribute index Address send list Address receive list Pulse No. Line signaling conversion index Line command conversion index Register signaling conversion index Register command conversion index Start TID End TID UMG8900 <CAS name> <signaling type> <Line signaling> <Register signaling> <Index> <Address send list> <Address receive list> <Pulse No.> <Line signaling conversion index> <Line command conversion index> <Register signaling conversion index> <Register command conversion index> <Start 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 command conversion index>, RSSC=<Register signaling conversion index>, RSCM=<Register command 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=<End TID>, VMGWID=<Virtual media gateway id>, RT=R2, CASNO=<Index>, PLSID=<Pulse No.>; ----End
Example

MGC
R2
PBX
UMG8900
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;
Postrequisite
After the CAS is configured, configuring the signaling transfer is complete.
Issue 02 (2008-05-07)
14-43
15 Configuring UAM Data
15
About This Chapter
Preparations
Table 15-1 Preparations No. Item
Configuring UAM Data
This describes how to configure the user access module (UAM) data.
Before configuring the UAM data, you must complete preparations listed in Table 15-1.
Remarks The UA main frame, UA direct frame, or RSA main frame is connected to the TDM interface board in the SSM frame through E1 cables. The UA main frame and subframe are connected through highway cables. The RSA main frame and the attached subframe are connected through cascading cables.
Confirm the physical cable connection.
Confirm that the VPU runs properly. Confirm that the SPF and the TDM interface boards are configured and they work normally.
The VPU functions to provide asynchronous tones. The SPF and the TDM interface boards process narrowband access services.
Figure 15-1 shows the procedure for configuring basic services of the UAM.
Issue 02 (2008-05-07)
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 mutual-aid on the SPF
Configure trunks of the PV8/RSU/ RSP/RSA/DRV
End
15.1 Configuring UA Frames and Boards This describes how to configure the user access (UA) frames, boards, and connections, and how to deploy the plain old telephone service (POTS). 15.2 Configuring the Connection to the UA Frame This describes how to configure the connection between the UMG8900 and the user access (UA) frame. 15.3 Configuring Synchronous Tones This describes how to configure the synchronous tones. 15.4 Configuring UAM Environment Monitoring Data This describes how to configure the user access module (UAM) environment monitoring data. 15.5 Configuring the DDI/AT0 Trunk Access Service This describes how to configure the direct-dialing-in (DDI) or AT0 trunk access service. 15.6 Configuring the Hotline Service This describes how to configure the hotline service. 15.7 Configuring the DDN Dedicated Line Service of the DSL This describes how to configure the digital data network (DDN) dedicated line service of the DSL. 15.8 Configuring the DDN Dedicated Line Service of the HSL This describes how to configure the digital data network (DDN) dedicated line service of the HSL.
15.9 Configuring the DDN Dedicated Line Service of the SDL This describes how to configure the digital data network (DDN) dedicated line service of the SDL. 15.10 Configuring the Audio Dedicated Line Service This describes how to configure the audio dedicated line service.
Issue 02 (2008-05-07)
15-3
15.1 Configuring UA Frames and Boards

This describes how to configure the user access (UA) frames, boards, and connections, and how to 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.
Data Planning
l
Table 15-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 15-2 Input parameter Parameter Name Frame ID Board No. Virtual media gateway ID Data <Board type> <Board No.> <Virtual media gateway id> Input Source 8 Configuring Frames and Boards 8 Configuring Frames and Boards 11.1 Configuring MGW data
Table 15-3 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. Table 15-3 Data planning Parameter Name Start TID End TID Trunk type Frame ID Field ID Cabinet No. Frame No. in cabinet Frame type UMG8900 <Start TID> <End TID> <Relay type> <Frame No.> <Place No.> <Cabinet No.> <Frame No. in cabinet> <Frame type>
Issue 02 (2008-05-07)
15-4
Parameter Name Mode CMU module No. Slot No. Board type Link group No. Integer interface ID
UMG8900 <Frame mode> <CMU module No.> <Slot No.> <Board type> <Link set No.> <Int interface ID>
Table 15-4 lists the parameters output to other steps. Table 15-4 Data output Parameter Name Frame ID Slot No. Board type Data <Frame No.> <Slot No.> <Board type>
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=<End TID>, 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, RSA subframe. For details, see 3.8.2 UA Frame Modes. Step 3 Run ADD UABRD to add boards in the UA frame.
CAUTION
For details about boards in the UA frame, refer to Chapter 3 "Introduction to Boards" in the USYS UMG8900 Universal Media Gateway UAM Hardware Description.
l
If Board type is set to DSL, run the following command:

Issue 02 (2008-05-07)
ADD UABRD: FN=<Frame No.>, SN=<Slot No.>, BT=<Board type>, LKS=<Link set No.>, 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
Example
In 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 are described. For configurations of RSA main frames, RSA subframes, RSA direct frames, highdensity UA frames, and boards, refer to HUAWEI UMG8900 Universal Media Gateway Configuration Examples Configuring Interconnection Data Between the UMG8900 and the High-Density UA Frame. UA frames and boards Figure 15-2 shows the UA frames and boards. Figure 15-2 UA frames and boards
UAM 0 0 0 1 0 2 0 3 0 4 0 5 0 6 0 7 0 8 0 9 1 0 1 1 1 2 1 3 1 4 1 5 1 6 1 7 RSP_10 P (main frame) W X 1 1 6 7
E P T A A A A A H P P A A A A D S W S S S 3 3 3 W V V 3 3 3 3 S C X S L L 2 2 2 C 8 8 2 2 2 2 L 0 0 0 1 0 2 0 3 0 4 0 5 0 6 0 7 0 8 0 9 1 0 1 1 1 2 1 3 1 4 1 5
E P S W C X 0 0 0 1 0 2
A A A A A A R R A A A A D D D S S 3 3 3 3 S S 3 3 3 3 S S S L L 2 2 2 2 P P 2 2 2 2 L L L 0 3 0 4 0 5 0 6 0 7 0 8 0 9 1 0 1 1 1 2 1 3 1 4 1 5 1 6 1 7
RSP_14 (subframe)
E P S W C X
A A A A A S S 3 3 3 L L 2 2 2
R R A A A A A S S 3 3 3 3 3 P P 2 2 2 2 2
RSP_14 P (direct frame) W X
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;
15-6
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. Int interface ID specifies the integer interface ID of the ISDN Q.921-User Adaptation Layer (IUA) link where the DSL subscriber is located. Int interface ID is valid only when Board type is set to DSL, and must be a 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;
Postrequisite
After configuring the hardware data, you can configure the connection between the UMG8900 and the user access module (UAM).
15.2 Configuring the Connection to the UA Frame

This describes how to configure the connection between the UMG8900 and the user access (UA) frame.
Issue 02 (2008-05-07)
15-7
Context
Configure the data of the time division multiplexing (TDM) trunk connection between the user access module (UAM) frame and the service switching module (SSM) frame, between the UA main frame and subframe, and between the RSA main frame and subframe. The TDM trunk connection data is used to carry UAM signaling links and voice services. Connections to be configured vary with network applications.
l
If the networking mode is SSM + main frame + subframe, you must configure E1 connections between the PV8/RSU in the master frame and the TDM interface boards such as 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 the HW connection after the E1 connections are configured. In this manner, you can check if configurations are correct through the PV8/RSU/RSP board status. If the networking mode is SSM + direct frame, you must configure E1 connections between the RSP in the direct frame and the TDM interface boards such as the E32/T32/S2L/S1L in the SSM frame. If the direct frame is an RSB frame, configure E1 connections between the RSA in the direct frame and the TDM interface boards in the SSM frame. If the networking mode is SSM + RSA main frame + RSA subframe, you must configure E1 connections between the RSA in the RSA main frame and the TDM interface boards such as the E32/T32/S2L in the SSM frame. You must also configure the cascading between the 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 are correctly configured. If the board status is faulty, it indicates that the trunk connections are not correctly 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 main frame, and direct frame are called the lower-level frames. Similarly, for configuration of connections between the main frame and the subframe, and between the RSA main frame and the RSA subframe, the main frame and the RSA main frame are called the upper-level frames; the subframe and the RSA subframe are called the lower-level frames.
15.2.1 Configuring the Connection Between the SSM Frame and the Main Frame as Well as the Direct Frame This describes the connection between the service switching module (SSM) frame and the main frame, 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 Subframe This describes the connection between the RSP main frame and the RSP subframe, and how to configure the connection. 15.2.3 Configuring the Connection Between the RSA Main Frame and the RSA Subframe This describes the connection between the RSA main frame and the RSA subframe, and how to configure the connection. 15.2.4 Configuring the Connection Between the High-Density Main Frame and the HighDensity Subframe This describes the connection between the high-density main frame and the high-density subframe, and how to configure the connection.
15.2.1 Configuring the Connection Between the SSM Frame and the Main Frame as Well as the Direct Frame
This describes the connection between the service switching module (SSM) frame and the main frame, as well as the direct frame, and how to configure the connection.
Prerequisite
The 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
CAUTION
Parameter settings must match the physical cable connections. The timeslot 16 of the first E1 on the PV8/RSU/RSP/RSA is used to carry signaling, and thus the PV8/RSU/RSP/RSA cannot start normally if the parameters such as First board No. are configured wrongly. On the device panel, the board status is displayed as faulty. The second to the eighth E1s are used to carry voice channels, 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.
Data Planning
l
Table 15-5 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 15-5 Input parameter Parameter Name Frame ID Slot No. Data <Frame No.> <Slot No.> Input Source 15.1 Configuring UA Frames and Boards 15.1 Configuring UA Frames and Boards
Table 15-6 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. Table 15-6 Data planning Parameter Name Trunk interface board type UMG8900 <Trunk interface board type>
15-9
Issue 02 (2008-05-07)
Parameter Name SPF board No. SPF subboard No. First board No. First port No. Second board No. Second port No. Third board No. Third port No. Fourth board No. Fourth port No. Fifth board No. Fifth port No. Sixth board No. Sixth port No. Seventh board No. Seventh port No. Eighth board No. Eighth port No.
UMG8900 <SPF board No.> <SPF subboard No.> <First trunk board No.> <First port No.> <Second trunk board No.> <Second port No.> <Third trunk board No.> <Third port No.> <Fourth trunk board No.> <Fourth port No.> <Fifth trunk board No.> <Fifth port No.> <Sixth trunk board No.> <Sixth port No.> <Seventh trunk board No.> <Seventh port No.> <Eighth trunk board No.> <Eighth port No.>
Procedure
Run ADD UACFG to add connections between the SSM frame and the main frame and direct frame. 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=<Sixth trunk board No.>, PN5=<Sixth port No.>, BN6=<Seventh trunk board No.>, PN6=<Seventh port No.>, BN7=<Eighth trunk board No.>, PN7=<Eighth port No.>; ----End
Example
The following describes five different connection examples of the E1.
l
For the front access frame (PV8-SSM), the physical connections between the UAFM frame and the SSM frame are shown in the following figure.
15-10
The D-50PIN connector of the trunk cable connects with the PV8 E1 or PV4 E1 interfaces of the UAFM frame. The other end is a coaxial cable that connects with the TDM interface board 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) E1 connects 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 8 on the PV8. Among them, the coaxial cable labeled W1-Left PV8/PV4 (5 to 8) E1 connects 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 cabling area 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
port 0 port 1 2# E32 1 2 3 4 5 6 3# E32 7 8 1 2 3 4 5 6 7 8 W2-Right PV8/PV4 (1~4)E1 W2-Right PV8/PV4 (5~8)E1 port 3 UAFM W1-Left PV8/PV4 (5~8)E1 W1-Left PV8/PV4 (1~4)E1 port 0 port 1 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1# E32 port 7 0# E32
PV8 E1 PV4 E1
E1 Nos. on the naked wires. Two cables need to be inserted in an E1 interface, 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.
Issue 02 (2008-05-07)
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 HABD or the HABL frame. The other end is a four-wire coaxial cable that connects with the TDM interface 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
port 0 port 1 2# E32 1 2 3 4 5 port 3 HABD/HABL W1-Left RSU (1~4)E1 E1TF W2-Left RSU (5~8)E1 port 0 port 1 1 2 3 4 5 6 7 8 1 2 3 4 5 6 W3-Right RSU (1~4)E1 W4-Right RSU (5~8)E1 7 8 1# E32 0# E32
...
6 7 8
...
port 7
3# E32
1 2 3 4 5 6 7 8
...
...
//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
15-12
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 the UAM 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 to 32 in the upper HEADER on the PV8. The other end is a coaxial cable that connects with the TDM interface 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 end leading 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 the PV8. 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 leading out 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 E1 2. 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 E1 4.
For trunk cables with one end connecting the 4x8-PIN AMP socket and the other end leading 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 the other end leading out four E1s cannot be used. The cables are connected in the same way as those of the PV8.
Take the trunk cable with one end connecting the 4x8-PIN AMP socket and the other end providing four E1s as an example to describe the trunk configuration.
Issue 02 (2008-05-07)
15-13
Figure 15-5 Physical connections between the PV8 in the UAM frame and the SSM frame
port 0 port 1 2#E32 1 2 3 4 5 6 7 8 1 2 3 port 6 4 5 6 7 8 8#E1 8#E1 4#E1 7#E1 4#E1 7#E1 3#E1 6#E1 32 3#E1 5#E1 24 6#E1 2#E1 16 5#E1 2#E1 1#E1 1 PV8R PV8L 1#E1 port 0 port 1 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 port 7 1# E32
E1 Nos. on the naked wires. Two cables need to be inserted in an E1 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 are connected to E1 ports in sequence, configure the E1 ports in a cross order when configuring E1 trunks. Refer to Figure 15-6.
15-14
Issue 02 (2008-05-07)
Figure 15-6 E1 port connection in sequence
W1 to W8: E1 cable labels 1#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 are connected to E1 ports in a cross order, configure the E1 ports in sequence when configuring E1 trunks. Refer to Figure 15-7.
Issue 02 (2008-05-07)
15-15
Figure 15-7 E1 port connection in a cross order
W1 to W8: E1 cable labels 1#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 shown in Figure 15-8. Configure the E1 ports in sequence when configuring E1 trunks.
15-16
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 frame and 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 the upper HEADER on the RSP. The other end is a coaxial cable that connects with the TDM interface 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 end leading 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 E1 2. 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 E1 4.
For trunk cables with one end connecting the 4x8-PIN socket and the other end leading out one 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 end providing two E1s as an example to describe the trunk configuration.
Issue 02 (2008-05-07)
15-17
Figure 15-9 Physical connections between the RSP in the UAM frame and the SSM frame
port 0 port 1 2# E32 1 2 3 4 16 3# E32 24 32 1 2 3 4 port 7 1# E32 1 port 3 RSPR RSPL port 0 port 1 1 2 3 4 0# E32
1 2 3 4
//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_UP frame 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 rear HWCB of the HABA frame. The other end is a two-wire coaxial cable that connects with the TDM interface board of the SSM frame. In other words, it connects with the physical DDF. The HWCB provides the upper and lower 44-PIN interfaces, each of which can connect eight 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 slot 5 in sequence. The first four E1s of the lower interface correspond to the last four E1s of the RSU in slot 4 in sequence. The last four E1s correspond to the last four E1s in the RSU in slot 5 in sequence.
15-18
Issue 02 (2008-05-07)
Figure 15-10 Physical connections between the HWCB in the HABA_UP frame and the SSM frame
port 0 port 1 2# E32 1 2 3 4 5 6 3# E32 7 8 1 2 3 4 5 6 7 8 W1-Left RSU (5-8)E1 W2-Right RSU (5-8)E1 port 3 HWCB W1-Left RSU (1-4)E1 W2-Right RSU (1-4)E1 port 0 port 1 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1# E32 port 7 0# E32
//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 required in between. Thus, the E1 Nos. matching the E1 cables of the PV8/RSU/RSP in the SSM frame are 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/RSU by Mapping Them to E1 Cables on the SSM Side and 3.8.5 Method to Number E1 Interfaces on 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.
Issue 02 (2008-05-07)
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 Frame and the RSP Subframe
This describes the connection between the RSP main frame and the RSP subframe, and how to configure the connection.
Prerequisite
The connection between the user access (UA) main frame and the service switching module (SSM) frame is configured.
Context
The UA main frame is connected to the subframe through internal highway (HW) cables. Figure 15-12 shows the connection.
15-20
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 E F G H HGB
RSPR RSPL
HIB
c d
a b
In Figure 15-12, the HGB is the backplane of the RSP_10 frame. The HGB provides the HWC interface for cascading with the subframe. Table 15-7 lists the descriptions of the HWC interface in the RSP_10 frame. Table 15-7 Descriptions of the HWC interface Interface ID A B C D E
Issue 02 (2008-05-07)
HW No. 16 to19 20 to 23 24 to 27 28 to 31 32 to 35
Pin Position 1 to 8 9 to 16 17 to 24 25 to 32 33 to 40
15-21
Interface ID F G H
HW No. 36 to 39 40 to 43 44 to 47
Pin Position 41 to 48 49 to 56 57 to 64
The HIB is the backplane of the RSP_14 frame. The HIB provides the HW interface for cascading with 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 a b c d Slot No. of the RSP 10 10 9 9 Board No. of the RSP 1 to 4 5 to 8 1 to 4 5 to 8 Pin Position 17 to 24 25 to 32 17 to 24 25 to 32
Data Planning
l
Table 15-10 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. Table 15-10 Data planning Parameter Name Trunk interface board type PV8 frame No. First HW No. UMG8900 <Trunk interface board type> <PV8 slot No.> <First HW No.>
Issue 02 (2008-05-07)
15-22
Parameter Name Second HW No. Third HW No. Fourth HW No. Fifth HW No. Sixth HW No. Seventh HW No. Eighth HW No.
UMG8900 <Second HW No.> <Third HW No.> <Fourth HW No.> <Fifth HW No.> <Sixth HW No.> <Seventh HW No.> <Eighth HW No.>
Procedure
Run ADD UACFG to add the trunk between boards in the RSP main frame and the RSP subframe. 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=<Third HW No.>, HW4=<Fourth HW No.>, HW5=<Fifth HW No.>, HW6=<Sixth HW No.>, HW7=<Seventh HW No.>, HW8=<Eighth HW No.>; ----End
Example
Example 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 Frame and the RSA Subframe
This describes the connection between the RSA main frame and the RSA subframe, and how to configure the connection.
Prerequisite
Boards in the RSA main frame and the RSA subframe are configured, and the main frame and the 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.
Issue 02 (2008-05-07)
15-23
Figure 15-13 Connection between the RSA main frame and the RSA subframe
RSA frame RSA RSA
USR frame
DRV DRV
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 the RSA frame through NOD cables. The DRV in slot 11 of the USR frame is connected to the RSA in slot 6 of the RSA frame through NOD cables.
Data Planning
l
15-24
Issue 02 (2008-05-07)

l
Table 15-12 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. Table 15-12 Data planning Parameter Name Trunk interface board type RSA frame No. Slot No. of the RSA UMG8900 <Trunk interface board type> <RSA Frame No.> <RSA slot No.>
Procedure
Run ADD UACFG to add the trunk between boards in the RSA main frame and the RSA subframe. ADD UACFG: FN=<Frame No.>, E1SRC=<Trunk interface board type>, SN=<Slot No.>, RSAFN=<RSA Frame No.>, RSASN=<RSA slot No.>; ----End
Example
Example script
//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 Main Frame and the High-Density Subframe
This describes the connection between the high-density main frame and the high-density subframe, and how to configure the connection.
Prerequisite
Boards in the high-density main frame and the high-density subframe are configured, and the main 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 frame to the HABA_DOWN frame 8, PORT1 to the HABA_UP frame 9, and PORT2 to the HABA_DOWN frame 10.
Figure 15-14 Connection between the main frame and the subframe
#7HABA_UP
HWCB
#8HABA_DOWN
#9HABB_UP
HWCB
#10HABB_DOWN
Data Planning
l
Table 15-13 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 15-13 Input parameter Parameter Name Frame ID Data <Frame No.> Input Source 15.1 Configuring UA Frames and Boards
Table 15-14 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. Table 15-14 Data planning Parameter Name Trunk interface board type RSU frame No. Cascading interface UMG8900 <Trunk interface board type> <RSU frame No.> <Cascade>
Procedure
Run ADD UACFG to add the trunk between boards in the high-density main frame and the high-density subframe. ADD UACFG: FN=<Frame No.>, E1SRC=<Trunk interface board type>, RSUFN=<RSU frame No.>, RSUHW=<Cascade>; ----End
Example
Example script
//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 Tones

This describes how to configure the synchronous tones.
Prerequisite
The VPU is configured.
Context
Asynchronous tones refer to digital tones that the UMG8900 does not need to play from the beginning for an announcement playing request. The tone heard by the subscriber may be played from the middle and repeatedly. To configure the user access module (UAM), you must add the ringing tone, busy tone, and initial 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 second and keeps silent for four seconds periodically. A connected call may be mistaken as a call failed to be connected if the ringing tone is in the four-second silent period. To avoid this, you can add the initial ringing tone on the VPU so that the UMG8900 plays the initial ringing tone before the ringing tone. The configuration of the initial ringing tone is optional. It is recommended to configure the initial ringing tone together with the ringing tone.
Data Planning
l
Table 15-16 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. Table 15-16 Data planning Parameter Name Tone type UMG8900 <Tone type>
15-27
Issue 02 (2008-05-07)
Procedure
Run ADD ATONE to add the synchronous tones. ADD ATONE: BT=<Board type>, BN=<Board No.>, TONEID=<Tone type>; ----End
Example
Example script
//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 Data

This describes how to configure the user access module (UAM) environment monitoring data.
Prerequisite
The physical cables are connected, including:
l l l
Serial port connection between the ESC and the UAM Connection between the ESC and the monitored analog or digital sensor Connection between the ESC and the power supply
Context
Environment monitoring refers to monitoring on the status of environment parameters, including temperature, humidity, smoke, water penetration, fire alarm, and thief alarm of the cable distribution frame, access control, inside of the cabinet, and outside of the cabinet, as well as power parameters of the power supply and storage battery. If a monitored environment parameter is in abnormal state, the UMG8900 reports an alarm. Environment monitoring ensures that the UAM can run in a proper environment and the UMG8900 can run stably. Environment monitoring on the UMG8900 requires functional modules for monitoring. The environment monitoring module is classified into the following:
l l
Independent environment monitoring boards such as the ESC302 and the ESC303 Monitoring modules embedded in the monitored device, such as power supply 4875 and power supply 4845
Data Planning
l
15-28
Issue 02 (2008-05-07)
Table 15-17 Input parameter Parameter Name Frame ID Slot No. Board type Data <Frame No.> <Slot No.> <Board type> Input Source 15.1 Configuring UA Frames and Boards 15.1 Configuring UA Frames and Boards 15.1 Configuring UA Frames and Boards
Table 15-18 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. Table 15-18 Data planning Parameter Name EMU ID Switch value index Alarm mode Analog value index Fan control mode Power type UMG8900 <EMU ID> <Switch value index> <Alarm mode> <Analog value index> <Fan control mode> <Power type>
Procedure
Step 1 Run ADD UABRD to configure the environment & power monitoring board (ESC). Set ESC type 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 frame sensor and access control sensor. You do not need to configure these two sensors, and they use switch value indexes 0 and 1 by default. If you need to connect an external Boolean value output sensor of other types to the ESC, you must configure the 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 to v, 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.
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 external analog 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 status of each monitored parameter. DSP ESC: FN=<EMU ID>; ----End
Example
Example script
ADD 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 Service

This 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 analog subscriber lines in DDI/AT0 trunk access mode. The DDI/AT0 access solves the problem that an attendant console is required to transfer the call from a subscriber in the public network to a PBX subscriber. When calling a PBX subscriber with the extension number, the subscriber directly dials the extension number without knowing that the number is an extension number passing the switch. The direct-dialing-in subscriber interface board (CDI) in the user access (UA) frame implements the DDI/AT0 service.
Data Planning
l
Table 15-20 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. Table 15-20 Data planning Parameter Name Start port No. CASATTR No. Port No. UMG8900 <Start port No.> <CASATTR 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;
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
Example
Networking diagram The UMG8900 connects to the PBX through two analog subscriber lines from ports 0 and 1 of the CDI. The Singapore telecom mode is adopted. Figure 15-15 shows the networking.
Figure 15-15 DDI/AT0 trunk access service

UMG8900
RSP14 CDI
PBX
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 Service

This describes how to configure the hotline service.
Prerequisite
Subscriber boards in the user access (UA) frame are configured.
Context
The hotline service is classified into the following:
l
Hotline call service: If a subscriber does not dial a number within a specified time, such as five seconds, after picking up the phone, the call is automatically connected to a fixed number, also called hotline number. Immediate hotline service: After a subscriber picks up the phone, the call is automatically connected to the called number specified in service subscription.
Data Planning
l
15-32
Issue 02 (2008-05-07)
Table 15-21 Input parameter Parameter Name Frame ID Slot No. Data <Frame No.> <Slot No.> Input Source 15.1 Configuring UA Frames and Boards 15.1 Configuring UA Frames and Boards
Table 15-22 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. Table 15-22 Data planning Parameter Name Port No. UMG8900 <Port No.>
Procedure
Run 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). You must configure the hotline call authority for the subscriber and reserve the trunk. Refer to the data configuration guide of the MGC. The configuration on the UMG8900 refers to reserving timeslots for subscribers with the hotline call authority to ensure that subscribers can talk on the phone after off-hook.
NOTE
If no timeslot is reserved, hotline calls can also be completed in normal cases; however, hotline calls may fail in busy hours because of failure to occupy timeslots.
----End
Example
The subscriber of port 0 on the A32 in the RSP_10 frame of the UMG8900 has the hotline call authority 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 the DSL

This describes how to configure the digital data network (DDN) dedicated line service of the DSL.
Prerequisite
The related hardware of the UMG8900, E1 interface boards, and ISDN Q.921-User Adaptation Layer (IUA) links are configured.
Context
The DDN adopts digital channels to provide semi-permanent connection circuits to transmit data signals. By using the time division multiplexing (TDM) mode and the circuit switching technology, the DDN provides permanent or semi-permanent digital dedicated line connections to transparently transmit subscriber data. The multifunctional terminal adapter (MTA) is a data service unit (DSU) positioned on the subscriber side. The MTA is connected to the DSL through the 2B1Q interface. The access distance of the MTA is 4 to 5 kilometers, and the core diameter is 0.4 millimeter. The MTA can provide one V.24/V.35 compatible interface, two V.24 interfaces, rate-synchronous port (64 kbit/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 Division3 stipulations about twenty 8-bit envelope.
Networking Application
Through semi-permanent connections, the UMG8900 establishes digital dedicated line connections between the data terminal attached to the MTA and the DDN node machine, as well as the data terminal attached to the MTA. Refer to Figure 15-16. Figure 15-16 DDN dedicated line service
UMG8900 A DDN node machine E1 E1 SPC(B) PV8/RSP DSL MTA V.35/V.24 SPC(A) V.24 DSL MTA V.35
Router Data Terminal Data Terminal
Data Planning
l
15-34
Issue 02 (2008-05-07)
Table 15-23 Input parameter Parameter Name Frame ID Slot No. Data <Frame No.> <Slot No.> Input Source 15.1 Configuring UA Frames and Boards 15.1 Configuring UA Frames and Boards
Table 15-24 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. Table 15-24 Data planning Parameter Name MTA index DSL frame No. DSL slot No. DSL port No. Port0 rate B channel of port 0 Semi-Permanent connection ID Link type Direction Source frame No. Source slot No. Source port No. UMG8900 <MTA index> <DSL frame No.> <DSL slot No.> <DSL port No.> <Port0 rate> <Port0 B channel> <ID> <Link type> <Direction> <Src frame No.> <Src slot No.> <Src port No.>
Procedure
Step 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
Example
UMG8900 DDN node machine E1 E1 SPC PV8/RSP DSL MTA V.35
Router
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 the HSL

This describes how to configure the digital data network (DDN) dedicated line service of the HSL.
Prerequisite
The HSL is in position, and data except the dedicated line service is configured.
Context
The HSL is a high-speed line interface board of the UMG8900. The HSL can be inserted into a slot where the ASL or the A32 can be inserted. The HSL provides two FE1 and two V.35 interfaces 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.
The V.35 interface can be connected in highway (HW) uplink mode or E1 bypass mode.
In HW uplink mode, two V.35 terminals communicate with each other through the service switching module (SSM). The maximum rate is 25 x 64 kbit/s. Figure 15-18 shows the networking in HW uplink mode. Figure 15-18 HW uplink mode for the V.35 interface
SSM
E1 UAM HSL HSL
Router
Router
In E1 bypass mode, two HSLs are connected through E1 cables. Two V.35 terminals can communicate with each other through the user access module (UAM). The maximum rate is 31 x 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.
Issue 02 (2008-05-07)
15-37
Figure 15-19 E1 bypass mode for the V.35 interface

SSM
E1 UAM HSL E1 HSL
Router
Router
Data Planning
l
Table 15-26 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. Table 15-26 Data planning Parameter Name Port No. V35 rate V35 clock mode V35 work mode E1 port E1 timeslot No. UMG8900 <Port No.> <V35 rate> <V35 clock mode> <V35 work mode> <E1 port No.> <E1 timeslot No.>
Issue 02 (2008-05-07)
15-38
Parameter Name Clock source E1 Frame Semi-Permanent connection ID Direction Source UA frame No. Source UA slot No. Source UA port No. Destination UA frame No. Destination UA slot No. Destination UA port No.
UMG8900 <Clock source> <E1 Frame> <ID> <Direction> <Src frame No.> <Src slot No.> <Src port No.> <Dst frame No.> <Dst slot 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>;
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 is set to UA_UA, run the following command: ADD SPC: ID=<ID>, CT=UA_UA, CD=<Direction>, SRFN=<Src frame No.>, SRSN=<Src slot 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.

l
Networking diagram for the HW uplink mode Figure 15-18 shows the typical networking. 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;
Networking diagram for the E1 bypass mode Figure 15-19 shows the typical networking. 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 the SDL

This describes how to configure the digital data network (DDN) dedicated line service of the SDL.
Prerequisite
The 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 a slot where the ASL or the A32 can be inserted. The SDL provides four FE1 and four SHDSL interfaces to connect to the modem. The modem provides the V.35 interface to connect to the router 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.
In HW uplink mode, two V.35 terminals communicate with each other through the service switching module (SSM). The maximum rate is 25 x 64 kbit/s. Figure 15-20 shows the networking in HW uplink mode.
Figure 15-20 HW uplink mode for the V.35 interface
SSM
E1 UAM SDL SDL
Modem
Modem
Router
Router
In E1 bypass mode, two SDLs are connected through E1 cables. Two V.35 terminals can communicate with each other through the user access module (UAM). If Board mode is set to Normal and E1 frame is set to PCM31, the maximum rate is 31 x 64 kbit/s. If Board mode is set 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. Figure 15-21 shows the networking in E1 bypass mode. Figure 15-21 E1 bypass mode for the V.35 interface
SSM
E1 UAM SDL E1 Modem Modem SDL
Router
Router
Issue 02 (2008-05-07)
15-41
Data Planning
l
Table 15-28 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. Table 15-28 Data planning Parameter Name Port No. Board mode Clock source E1 Frame E1 port E1 timeslot No. Max rate Min rate Trans-mode SNR(dB) Work mode Frame switch Rx clock PLL lock Modem mode Board mode Clock source Semi-Permanent connection ID UMG8900 <Port No.> <Board mode> <Clock source> <E1 frame> <E1 port No.> <E1 timeslot No.> <Max rate> <Min rate> <Trans-mode> <SNR(dB> <Work mode> <Frame switch> <Rx clock> <PLL lock> <Modem mode> <Board mode> <Clock source> <ID>
Issue 02 (2008-05-07)
15-42
Parameter Name Direction Source UA frame No. Source UA slot No. Source UA port No. Destination UA frame No. Destination UA slot No. Destination UA port No.
UMG8900 <Direction> <Src frame No.> <Src slot No.> <Src port No.> <Dst frame No.> <Dst slot No.> <Dst port No.>
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>;
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=<Modem mode>;
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=<Work mode>, 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 is set to UA_UA, run the following command: ADD SPC: ID=<ID>, CT=UA_UA, CD=<Direction>, SRFN=<Src frame No.>, SRSN=<Src slot No.>, SRPN=<Src port No.>, DRFN=<Dst frame No.>, DRSN=<Dst slot No.>, DRPN=<Dst port No.>; ----End
Example
Networking diagram In this example, the E1 bypass mode is adopted. Figure 15-21 shows the networking. Example script
//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 Service

This describes how to configure the audio dedicated line service.
Prerequisite
Data except that of dedicated line services is configured.
Context
The analog trunk interface (ATI) is a 2/4-wire E&M interface board of the UMG8900. The ATI can be inserted into a slot where the ASL or the A32 can be inserted, and can provide six 2/4wire 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.
At present, the UMG8900 connects different ATIs through semi-permanent connections to implement dedicated line connections among 2/4-wire audio subscribers. Figure 15-22 shows the networking.
15-44
Issue 02 (2008-05-07)
Figure 15-22 Audio dedicated line service networking

UMG8900A IP SPCIP E1 SPC(B) PV8/RSP ATI Audio Modem SPC(A) ATI Audio Modem ATI Audio Modem PV8/RSP E1 UMG8900B
Data Terminal
Data Terminal
Data Terminal
Data Planning
l
Table 15-30 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. Table 15-30 Data planning Parameter Name Port No. Work mode IP domain ID UMG8900 <Port No.> <Work mode> <IP domain ID>
15-45
Issue 02 (2008-05-07)
Parameter Name Local IP address Local UDP port No. Remote IP address Remote UDP port No. VPU board No. Service type Codec type PTime(ms) Semi-permanent connection ID Direction Source IP address Source IP port Destination UA frame No. Destination UA slot No. Destination UA port No.
UMG8900 <Local IP address> <Local UDP port> <Remote IP address> <Remote UDP port> <VPU board No.> <Service type> <Codec> <PTime(ms)> <ID> <Direction> <Src IP address> <Src IP port> <Dst frame No.> <Dst slot No.> <Dst port No.>
Procedure
Step 1 Run SET ATIPRT to set attributes of ports on the ATI. SET ATIPRT: FN=<Frame No.>, SN=<Slot No.>, PN=<Port No.>, WORKMODE=<Work mode>; 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 required to pass the IP network, you must add IP terminations of the semi-permanent connection in advance. IP terminations of the semi-permanent connection must be added on UMG8900 A and UMG8900 B in advance. Local IP address and Local UDP port of the IP termination of the semi-permanent connection of UMG8900 A must be the same as Remote IP address and Remote UDP port of that of UMG8900 B. Remote IP address and Remote UDP port of the IP termination of the semi-permanent connection of UMG8900 A must be the same as Local IP address and Local UDP port of that of UMG8900 B. Run ADD SPCIP to add IP terminations of 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 the following command:
ADD SPC: ID=<ID>, CT=IP_UA, CD=<Direction>, SISA=<Src IP address>, SISP=<Src IP port>, SIAD=<IP domain ID>, DRFN=<Dst frame No.>, DRSN=<Dst slot No.>, DRPN=<Dst port No.>; ----End
Example
Networking diagram Figure 15-22 shows the typical networking. 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;
Issue 02 (2008-05-07)
15-47
16
Prerequisite
l l l
Configuring StandAlone
This describes how to configure the StandAlone data, including the StandAlone data of the ESL subscribers and that of the V5 subscribers.
The TDM bearer is configured on the UMG8900. The V5E1 link is configured on the UMG8900. The LAPV5 link is configured on the UMG8900.
Context
StandAlone 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, the UMG8900 is not controlled by the MGC; however, the UMG8900 can still implement basic call connection between user access module (UAM) analog subscribers or subscribers accessed through devices in the V5 access network. That is, StandAlone imposes certain call control functions of the MGC on the media gateway (MGW). Thus, StandAlone enhances the reliability of the MGW and enables networks to survive disasters. After losing connection with the MGC, the UMG8900 enables StandAlone to control basic calls between analog subscribers, and the ongoing calls established by the MGC are not interrupted. When the connection between the UMG8900 and the MGC recovers, StandAlone automatically hands over the call control function to the MGC. Figure 16-1 shows the takeover of the call control function from the MGC to StandAlone.
Issue 02 (2008-05-07)
16-1
Figure 16-1 Takeover of call control function from the MGC to StandAlone
MGC MGC
H.248
H.248
UMG8900
StandAlone
UMG8900
StandAlone
A: Normally, the MGC controls calls.
B: When the UMG8900 loses contact with the MGC, calls are connected in StandAlone mode.
StandAlone supports only calls between analog subscribers in the same office rather than outgoing calls, and supports only the basic call control service rather than supplementary services such 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.
Data Planning
l
Table 16-1 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 16-1 Input parameter Parameter Name Virtual media gateway ID Data <Virtual media gateway id> Input Source 11.1 Configuring MGW data
Table 16-2 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. Table 16-2 Data planning Parameter Name Trunk group No. CMU module No. Start L3 E1 No. Start L2 E1 No. Start AN E1 No. UMG8900 <V5 Group No.> <CMU Module No.> <Start L3 E1 ID> <Start L2 E1 ID> <Start AN E1 ID>
Issue 02 (2008-05-07)
16-2
Parameter Name Start TID V5 interface No. V5 interface ID Master link Logical C channel ID of the master link Slave link PSTN link Logical C channel ID of the PSTN link V5 start Phone Number V5 end Phone Number Start L3 Address Add Type Start phone number End phone number DIGITMAP Local IP address Local port No. iGWB IP iGWB port User type
UMG8900 <Start TID> <V5 Interface No> <V5 Interface ID> <Main Link> <Main Logical C channel ID> <Vice Link> <PSTN Link> <PSTN Logical C channel ID> <V5 Start Phone Number> <V5 End Phone Number> <Start L3 Address> <Add Type> <Start Phone Number> <End Phone Number> <DIGITMAP> <Local IP> <Locla Port> <iGWB IP> <iGWB Port> <User Type>
Procedure
Step 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=<Start L2 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 Group Type to Protect Group 2. ADD V5I: INFNO=<V5 Interface No>, TKGNO=<V5 Group No.>, INFID=<V5 Interface ID>, MAINLNK=<Main Link>, MLNKID=<Main Logical C channel ID>, PROTTYP=P2,
VICELNK=<Vice Link>, PSTNLNK=<PSTN Link>, PSTNID=<PSTN Logical C channel ID>, 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 L3 Address>;
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 Phone Number>, 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>;
CAUTION
After the UMG8900 is successfully connected with the iGWB, the UMG8900 registers the VMGW MID of the VMGW with the iGWB, and the related authentication information about the VMGW MID need be added to the GatewayIDs.ini file of the iGWB. The UMG8900 sends an authentication message of the VMGW MID of the VMGW before sending the bill to the iGWB. After the authentication succeeds, the iGWB can normally receive the correct bill from the UMG8900. Step 7 Run SET CCSWT to enable StandAlone. SET CCSWT: VMGWID=<Virtual media gateway id>, USERTYPE=<User Type>, BILL=YES; ----End
Example
Example script
l
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-4
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;
CAUTION
The iGWB can normally receive bills from the UMG8900 only when the authentication information about the VMGW MID of the VMGW is added to the GatewayIDs.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 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;
CAUTION
The iGWB can normally receive bills from the UMG8900 only when the related authentication information about the VMGW MID of the VMGW is added to the GatewayIDs.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 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-1&V5-0, BILL=YES;
Issue 02 (2008-05-07)
16-5
17 Configuring Service Resource Parameters
17
About This Chapter
Configuring Service Resource Parameters
This describes how to configure the service resource parameters, including the media resource parameters, service parameters, and quality of service (QoS) parameters. 17.1 Configuring Media Resource Parameters This describes how to configure the media resource parameters, including the voice codec, media processing parameters, transcoder (TC) work parameters, echo cancellation (EC) work parameters, MTC work parameters, voice enhancement work parameters, audio mixing state of the signal tones, alarm threshold of the resource utilization, common codec information, fax work parameters, and RFC2833 parameters. 17.2 Configuring Service Parameters This describes how to configure the service parameters. 17.3 Configuring QoS Parameters This describes how to configure the quality of service (QoS) parameters.
Issue 02 (2008-05-07)
17-1
17.1 Configuring Media Resource Parameters

This describes how to configure the media resource parameters, including the voice codec, media processing parameters, transcoder (TC) work parameters, echo cancellation (EC) work parameters, MTC work parameters, voice enhancement work parameters, audio mixing state of the signal tones, alarm threshold of the resource utilization, common codec information, fax work parameters, and RFC2833 parameters.
Prerequisite
l l l
The MGW control data is correctly set. The bearer data is correctly set. The signaling transfer data is correctly set.
CAUTION
The configuration of codec capability causes the reset of the VPU. In this case, all the sessions on the VPU are lost. It is recommended to use SET CODECCAP when a new office is set up or the UMG8900 is ready to restart. The configuration in this step is not mandatory, and the configuration varies with the application scenarios. Configure the resource parameters based on the actual conditions. In different application scenarios, different subboards are configured on the VPU and different TC or EC resources are provided. Refer to Table 17-1. Table 17-1 Board configuration of the VPU Board No. MVPD1 Resource Two VDB subboards are configured to provide 1024 channels of TC resources. Two VDB subboards and one ECC subboard are configured to provide 1024 channels of TC and 64 ms EC resources. One ECC subboard is configured to provide 1024 channels of 64 ms EC resources. One VDB subboard is configured to provide 512 channels of TDM announcement playing resources. Function Restrictions -
MVPD2
The MVPD1 and the MVPD2 are not configured at the same time. If needed, use the MVPD2 only. In an SSM-256 frame, the MECU, rather than the VPD3, provides EC resources. -
MVPD3
MVPD4
17-2
Issue 02 (2008-05-07)
Board No. MVPD6
Resource Two VDB subboards and one ECE subboard are configured to provide 1024 channels of TC and 128 ms EC resources. Two VDB subboards and one ECJ subboard are configured to provide 1024 channels of TC and 64 ms EC resources. One ECJ subboard is configured to provide 1024 channels of 64 ms EC resources. Two VDB subboards and one ECK subboard are configured to provide 1024 channels of TC and 128 ms EC resources. Two VDB subboards and one VQE subboard are configured to provide 1024 channels of TC and VQE resources. One VQE subboard is configured to provide VQE resources. Two VDB subboards and one ECF subboard are configured to provide 1024 channels of TC and 64 ms EC resources. One ECF subboard is configured to provide 1024 channels of 64 ms EC resources. Two VDB subboards and one ECG subboard are configured to provide 1024 channels of TC and 128 ms EC resources.
Function Restrictions -
MVPD8
MVPD9
MVPD10
MVPD11
MVPD12 MVPD13
MVPD15
MVPD16
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 channel associated signaling (CAS), of the UMG8900.
Data Planning
l
Issue 02 (2008-05-07)
17-3
Table 17-2 Input parameter Parameter Name Board No. Data <Board No.> Input Source 8 Configuring Frames and Boards
Table 17-3 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. Table 17-3 Data planning Parameter Name Codec capability set MPTY channel number CAS channel number Support public codec Loading tone file type of the broadband codec capability set A/Mu law Start timer length(s) VAD option Packet Loss compensation G.711 PTime(ms) EEC tail length(ms) Comfort noise generation mode TFO switch Noise reduction aggressiveness (dB) Maximum gain for noise compensation (dB) Tone number tone mix state Resource type Threshold(%) General codec No. General codec name T38 PTime(ms) UMG8900 <Codec> <MPTY channel num> <MPTY channel num> <Support public codec> <Tonefile Type in WideBand Codec set> <A/MU law> <Start timer length(s)> <VAD option> <Packet Loss compensation> <G.711 PTime(ms)> <EEC tail length(ms)> <Comfort noise generation mode> <TFO SWITCH> <Noise reduction aggressiveness (dB)> <Maximum gain for noise compensation (dB) > <Tone number> <tone mix state> <Resource type> <Alarm Threshold> <General Codec No.> <General Codec Name> <T38 Fax PTime(ms)>
Issue 02 (2008-05-07)
17-4
Parameter Name T38 Max transmit speed(bps) T38 train mode IFP type Redundant number Redundant package payload type RFC2833 sending mode of DTMF Named packet payload type Send interval(ms) Codec RFCI length New RFCI No.
UMG8900 <T38 Max transmit speed(bps)> <T38 Train mode> <FAX TYPE> <Redundant number> <Redundant Package Payload Type> <RFC2833 sending mode of DTMF> <Named packet payload type> <Ipti> <Codec> <Rfci Length> <New RFCI No.>
Procedure
Step 1 Run SET CODECCAP to set the supported codec capability set. SET CODECCAP: BN=<Board No.>, CODEC=<Codec>, MPTYCHN=<MPTY channel num>, CASCHN=<MPTY channel num>; Step 2 Run SET MRPARA to set the media processing parameter. The board media processing parameter 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.711 PTime(ms)>; Step 4 Run SET ECPARA to set the EC resource parameter. SET ECPARA: BT=<Board No.>, TL=<EEC tail length(ms)>, CNG=<Comfort noise generation mode>, TFOSW=<TFO SWITCH>; Step 5 If the work parameter of the VIG feature needs to be modified, run SET MTCPARA to set the MTC 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=<Maximum gain 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 of the 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, run SET RESTHD to set the alarm threshold of the resource utilization.
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 redundancy packet for the pack loss concealment. l Set FAX TYPE to T38 Over UDPTL. SET FAXRDNT: TYPE=UDPTL_T38, FT=<FAX TYPE>, RN=<Redundant number>; 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 payload type>; ----End
Example
Example script
SET 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 Parameters

This describes how to configure the service parameters.
Prerequisite
l l l l
The hardware data is correctly set. The MGW control data is correctly set. The bearer data is correctly set. The signaling transfer data is correctly set.
Data Planning
l
Issue 02 (2008-05-07)
17-6
Table 17-5 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. Table 17-5 Data planning Parameter Name Alarm high threshold of fraction lost (%) Alarm low threshold of fraction lost(%) Lost rate of disconnection(%) Alarm high threshold of packet jitter (ms) Alarm low threshold of packet jitter (ms) Alarm high threshold of packet delay (ms) Alarm low threshold of packet delay (ms) Sending period of RTCP packet (s) Switch to send RTCP packets or not Release unstable links automatically or not RTCP transmission mode Send RTCP packets or not during IMS period Gmin of RTCP XR RTCP XR support mode E1 Switch to open RTCP or not None E1 Switch to open RTCP or not Release threshold for no RTCP packet received Average rate Peak rate Dynamic adjust enable JBU depth for 5-ms service UMG8900 <Alarm high threshold of fraction lost(%)> <Alarm low threshold of fraction lost(%)> <Lost rate of disconnection(%)> <Alarm high threshold of packet jitter (ms)> <Alarm low threshold of packet jitter (ms)> <Alarm high threshold of packet delay (ms)> <Alarm low threshold of packet delay (ms)> <Sending period of RTCP packet (s)> <Switch to send RTCP packets or not> <Release unstable links automatically or not> <RTCP transmission mode> <Send RTCP packets or not during IMS period> <Gmin of RTCP XR> <RTCP XR support mode> <E1 Switch to open RTCP or not> <None E1 Switch to open RTCP or not> <Release threshold for no RTCP packet received> <Average rate (kbps)> <Peak rate (kbps)> <Dynamic adjust enable> <JBU depth for 5-ms service>
Issue 02 (2008-05-07)
17-7
Parameter Name JBU depth for 20-ms service Host dynamic time Timeout(s) Launch time Initialization frame resend times Initialization frame resend interval Time align frame resend times Time align frame resend interval Rate control frame resend times Rate control frame resend interval
UMG8900 <JBU depth for 20-ms service> <Host dynamic time> <Timeout(s)> <Launch time> <Initialization frame resend times> <Initialization frame resend interval(ms)> <Time align frame resend times> <Time align frame resend interval(ms)> <Rate control frame resend times> <Rate control frame resend interval(ms)>
Procedure
Step 1 Run SET RTCP to set the RTCP protocol parameter. SET RTCP: WLOSSH=<Alarm high threshold of fraction lost(%)>, WLOSSL=<Alarm low threshold of fraction lost(%)>, CLOSS=<Lost rate of disconnection(%)>, JITBUFH=<Alarm high threshold of packet jitter (ms)>, JITBUFL=<Alarm low threshold of packet jitter (ms) >, PKGDLYH=<Alarm high threshold of packet delay (ms)>, PKGDLYL=<Alarm low threshold of packet delay (ms)>, TIMER=<Sending period of RTCP packet (s)>, SENDFLAG=<Switch to send RTCP packets or not>, LINKFLAG=<Release unstable links automatically or not>, SENDMODE=<RTCP transmission mode>, VADFLAG=<Send RTCP packets or not during IMS period>, GMIN=<Gmin of RTCP XR>, XRSUPPORT=<RTCP XR support mode>, E1OPENRTCP=<E1 Switch to open RTCP or not>, 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 adjust enable>,JBUFOR5MS=<JBU depth for 5-ms service>, JBUFOR20MS=<JBU depth for 20ms 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
Example
Example script
SET 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,
17-8
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 Parameters

This describes how to configure the quality of service (QoS) parameters.
Prerequisite
l l l l
The hardware data is correctly set. The MGW control data is correctly set. The bearer data is correctly set. The signaling transfer data is correctly set.
Data Planning
l
Table 17-6 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 17-6 Input parameter Parameter Name Interface IP address Data <Interface IP address> Input Source Configuring the IP Interface Address
Table 17-7 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. Table 17-7 Data planning Parameter Name Domain Protocol type Dscp/TOS value Precedence field Packet type Priority DSCP value High priority call threshold High rate occupied threshold UMG8900 <Domain> <Protocol type> <IPQOS Value> <Precedence> <Packet type> <Priority> <DSCP value> <High Priority Call Threshold> <High Rate Occupied Threshold(%)>
17-9
Issue 02 (2008-05-07)
Parameter Name Low rate occupied threshold
UMG8900 <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 Occupied Threshold(%)>,LORT=<Low Rate Occupied Threshold(%)> ----End
Example
Example script
SET 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;
17-10
Issue 02 (2008-05-07)
18 Configuring IP Network Security Data
18
Context
Configuring IP Network Security Data
About This Chapter

This describes how to configure the Internet Protocol (IP) network security data, including how to configure the firewall, IP Security Protocol (IPSec), and Security Shell (SSH). The UMG8900 can enable the firewall and the IPSec function on the media gateway (MGW) control interface, network management interface, and signaling transport (SIGTRAN) interface to achieve security protection on these types of control packets. Based on the SSH protocol, you can log in to and manage the UMG8900 to implement the security of the remote login.
18.1 Configuration the Firewall This describes how to configure the firewall. 18.2 Configuring IPSec This describes how to configure the IP Security Protocol (IPSec) data. 18.3 Configuring SSH This describes how to configure the security shell (SSH) data.
Issue 02 (2008-05-07)
18-1
18.1 Configuration the Firewall

This describes how to configure the firewall.

Figure 18-1 shows the index mapping of the major configuration command parameters of the firewall. Figure 18-1 Index mapping of the configuration command parameters of the firewall
SET ACL NUM ADD SACL(EACL) NUM TIME SET FIREWALL ACL BT BN STR FIREWALL BT BN ADD PRDCTM NAME ADD TIMERANG NAME ADD ABSTM NAME
Data Planning
l
18-2
Issue 02 (2008-05-07)
Table 18-2 Data planning Parameter Name ACL number Match sequence of ACL sub-rule Time range name Start time of the absolute time range Start date of the absolute time range End time of the absolute time range End date of the absolute time range Start time of the period time range End time of the period time range Week of the period time range Filtering rule IP address Reverse wildcard bits Whether to make log Interface type Interface ID Packet receiving and sending direction Default filtering rule UMG8900 <ACL number> <Match sequence of ACL sub-rule> <Time range name> <Start time> <Start date> <End time> <End date> <Start time> <End time> <Week> <Filtering rule> <IP address> <Reverse wildcard bits> <Whether to make log> <Interface type> <Interface No.> <Inbound/Outbound packets> <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=<End time>, 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>;
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
Example
Example script
SET 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;
Postrequisite
After configuring the firewall, configure the IP Security Protocol (IPSec) and security shell (SSH) based on the requirements.
l l
Configuring IPSec Configuring SSH
18.2 Configuring IPSec

This describes how to configure the IP Security Protocol (IPSec) data.

Figure 18-2 shows the index mapping of the configuration command parameters of IPSec.
18-4
Issue 02 (2008-05-07)
Figure 18-2 Index mapping of the configuration command parameters of IPSec

ADD EACL NUM RULE ADD ISTM ISTMN PROT AHA ESPA ESPE ADD ISSP ISSPGN ISTMN NUM LIP PIP ACL AIS AOS AIKF/AIHK/AISK AOKF/AOHK/AOSK EIS EOS EIKF/EIHAK/ EIHEK/EISK EOKF/EOHAK/ EOHEK/EOSK SET IPIFSPG ENABLE ISSPGN
Data Planning
l
Issue 02 (2008-05-07)
18-5
Table 18-4 Data planning Parameter Name ACL number Filtering rule Protocol No. Source IP address Source reverse wildcard bits Destination IP address Destination reverse wildcard bits Transform name Protocol Encapsulation mode AH authentication ESP authentication ESP encryption SPG name SPG No. SPG mode Transform name AH input SPI AH input hex key AH output SPI AH output hex key UMG8900 <ACL number> <Filtering rule> <Protocol No.> <Source IP address> <Source reverse wildcard bits> The same as that of the peer device <Destination reverse wildcard bits> <Transform name> <Protocol> <Encapsulation mode> <AH authentication> <ESP authentication> <ESP encryption> <SPG name> <Num> <SPG MODE> <Transform name> <AH input SPI> <AH input key format> <AH output SPI> <AH output key format> Interconnected Device The same as that of the peer device <Destination IP address> The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device
18-6
Issue 02 (2008-05-07)
Parameter Name AH input string key AH output hex key Local IP address Remote IP address Interface ID Enable IPSec Interface type
UMG8900 <AH input string key> <AH output hex key> <Local IP> The same as that of the peer device <Interface index> <Enable IPSec> <Interface type>
Interconnected Device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Peer IP> -
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=<Encapsulation mode>, 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=<AH input SPI>, AIKF=<AH input key format>, AISK=<AH input string key>, AOS=<AH output SPI>, 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
Example
Example script
ADD 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";
Issue 02 (2008-05-07)
18-7
Postrequisite
After configuring the IPSec, configure security shell (SSH) based on the requirements. Configuring SSH
18.3 Configuring SSH

This describes how to configure the security shell (SSH) data.
Context
SSH is a safe remote login protocol developed based on Telnet. The protocol number is 22. SSH supports 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 protects the integrity and reliability of the data. When the SSH client communicates with the server, both the username and password are encrypted so that interception on the password is prevented and secure transfer of data is ensured. The RSA authentication supports the mixed application of symmetrical and asymmetrical encryptions and secure exchange of keys, and finally realizes secure sessions. The SSH offsets the disadvantage of Telnet and securely achieves the remote login and access. Figure 18-3 shows the steps for configuring the SSH. Figure 18-3 Steps for configuring the SSH
Start
Configure the SSH client software and generate the client key
Add new user accounts on the UMG8900(optional)
Configure the SSH user accounts and type the client key
Configure the SSH server patameters(optional)
Configure Telnet timeout time(optional)
End
18-8
Issue 02 (2008-05-07)

NOTE
l l
If you do not add new user accounts on the UMG8900, you can set existing users to SSH users. The timeout time of the SSH connection is the same as that of Telnet. You can set it with SET TEOV.
Data Planning
l
Table 18-5 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. Table 18-5 Data planning Parameter Name SSH user name Authentication type RSA authentication public key file Server key update interval (hour) SSH authentication timeout (minute) SSH authentication retry times Enable SSHV1.X enhSession key exchange interval (hour) UMG8900 <Account> <Authentication Type> <RSA Authentication Pubilc Key File> <Server Key Update Interval(Hour)> <SSH Authentication Timeout(Minute)> <SSH Authentication Retry Times> <Enable SSHV1.X> <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=<SSH Authentication Timeout(Minute)>, RETRIES=<SSH Authentication Retry Times>, ENSSHV1X=<Enable SSHV1.X>,EXKEY=<SessionKey Exchange Interval(Hour)>; ----End
Example
Example script
SET 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;
Postrequisite
After configuring the SSH, configure other data based on the requirements.
A Data Planning
A
This describes the data planning of the UMG8900.
Data Planning
Configuring System Parameters

Table A-1 Data planning Parameter Name IP address of the version server User name of the version server Password of the version server System Node No. National signaling point code 1 Coding length Local signaling point index National signaling point code 2 Upper limit of the input voltage alarm (V) Lower limit of the input voltage alarm (V) Upper limit of the environment temperature alarm (C) Lower limit of the environment temperature alarm (C) Upper limit of the environment temperature alarm (F) Lower limit of the environment temperature alarm (F)
Issue 02 (2008-05-07)
UMG8900 <IP Address of Version Server> <User Name of Version Server> <Password of Version Server> <System Node No.> <National network code>_1 <National network structure> <OPC index> <National network code>_2 <Upper Limit of the Input Voltage Alarm (V)> <Lower Limit of the Input Voltage Alarm (V)> <Upper Limit of the Environment Temperature Alarm (C)> <Lower Limit of the Environment Temperature Alarm (C)> <Upper Limit of the Environment Temperature Alarm (F)> <Lower Limit of the Environment Temperature Alarm (F)>
A-1
A Data Planning
Parameter Name Cabinet No. Buzzer switch Frame No. Port No. of the environmental alarm chest Alarm ID Digital port alarm voltage Alarm name Alarm level Net management type
UMG8900 <Cabinet No.> <Switch> <Frame No.> <Port No.> <Alarm ID> <Digital Port Alarm Voltage> <Alarm Name> <Alarm Level> <Net Management Type>
Configuring the System Time

Table A-2 Data planning Parameter Name Date Time Adjust value (s) Daylight saving time Time zone Start date mode Start month Start date Start week Start time End date mode End month End date End week End time
A-2
UMG8900 <Date> <Time> <Adjust value(s)> <Daylight saving time> <Time zone> <Start date mod> <Start month> <Start date> <Start week> <Start time> <End date mode> <End month> <End date> <End week> <End time>
Interconnected Device (NTP Server) Issue 02 (2008-05-07)
A Data Planning
Parameter Name Time offset (minute) IP address of the NTP server Whether to authenticate the ID Authentication key ID Authentication key Version Prefer
UMG8900 <Time offset(minute)> The same as that of the peer device <Authentication> <Authentication key ID> <Authentication key> The same as that of the peer device <Prefer>
Interconnected Device (NTP Server) <NTP IP Address> <NTP Version> -
Configuring the NMS Interface

Table A-3 Data planning Parameter Name IP address of the NMS interface IP address and mask of the NMS interface Master or slave flag In VLAN IP address of the NMS IP address and mask of the NMS IP address of the router directly connected with the UMG8900 Protocol type UMG8900 <Interface IP address> <Interface IP address mask> <Master or slave flag> <In VLAN> The same as that of the peer device The same as that of the peer device The same as that of the peer device Interconnected Device 1 (NMS) The same as that of the peer device The same as that of the peer device <Destination address> <Destination address mask> Interconnected Device 2 (Router) <Next hop address>
<Protocol type>
Issue 02 (2008-05-07)
A-3
A Data Planning
Configuring SNMP Data

Table A-4 Data planning Parameter Name NMS version SNMP view name Mib object subtree OID Operate type SNMP group name Security level Read view name Write view name Notify view name SNMP user name Authentication protocol Authentication password Encryption protocol Encryption password SNMP group name Access mode IP address of the host receiving the SNMP notification Port No. Trap type UMG8900 <Version No.> <View name> <Mib object subtree OID> <Operate type> <Group Name> <Security level> <Read View Name> <Write View Name> <Notify View Name> <User Name> <Authentication Protocol> <Authentication Password> <Privacy Protocol> <Privacy Password> <Community Name> <Access Mode> The same as that of the peer device <UDP Port No.> <Trap type> Interconnected Device (NMS) The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Host Address>
Configuring Frames and Boards

Table A-5 Data planning Parameter Name Frame No.
A-4
UMG8900 <Frame No.>
Issue 02 (2008-05-07)
A Data Planning
Parameter Name Frame version Cascading mode Cascading board No. Configure GE cascade Local frame GE cascade slot No. Up frame GE cascade slot No. Up frame GE port No. Configure TDM cascade TDM cascadeport0 TDM cascadeport1 Cabinet No. Frame position Frame name Frame description Slot No. Board position Board type Backup type Hardware type Board No.
UMG8900 <Frame Ver> <FE Cascading Mode> <Cascading Board No.> <Configure GE Cascade> <Local Frame GE Cascade Slot No.> <Up Frame GE Cascade Slot No.> <Up Frame GE Port No.> <Configure TDM Cascade> <TDM CascadePort0> <TDM CascadePort1> <Cabinet No.> <Frame Position> <Frame Name> <Frame Description> <Slot No.> <Board Position> <Board type> <Backup type> <Hardware type> <Board No.>
Configuring the Clock

Table A-6 Data planning Parameter Name Priority of GPS reference source Priority of line clock 1 Priority of line clock 2 Priority of external synchronous 1 Priority of external synchronous 2 UMG8900 <Priority of GPS reference source> <Priority of line clock 1> <Priority of line clock 2> <Priority of external synchronous 1> <Priority of external synchronous 2>
Issue 02 (2008-05-07)
A-5
A Data Planning
Parameter Name Type of external synchronous Select mode of reference source Clock level Type of clock signal of external synchronous output Whether SSM control External reference source work mode Line clock Interface type Port No. Channel No. SSM timeslot
UMG8900 <Type of external synchronous> <Select Mode of Reference Source> <Clock Level> <Type of Clock Signal of External Synchronous Output> <Whether SSM Control> <External Reference Source Work Mode> <Line Clock> <Interface Type> <Port No.> <Channel No.> <SSM Time Slot>
Configuring Physical Interfaces of Gateway Control Interfaces and SIGTRAN Interfaces

Table A-7 Data planning Parameter Name UMG8900 Interconnecte d Device 1 (MGC) The same as that of the peer device Interconnecte d Device 2 (Direct Router) Interconnecte d Device 3 (MGW) -
Work mode Interface type Interface ID IP addresses 1 of gateway control interfaces and SIGTRAN interfaces IP addresses 2 of gateway control interfaces and SIGTRAN interfaces
<Work Mode> <Interface type> <Interface No.> <Interface IP address>_1
A-6
Issue 02 (2008-05-07)
A Data Planning
Parameter Name
UMG8900
Interconnecte d Device 1 (MGC) The same as that of the peer device
Interconnecte d Device 2 (Direct Router) -
Interconnecte d Device 3 (MGW) -
IP address and mask of gateway control interfaces and SIGTRAN interfaces Master or slave flag Slot No. IP address 1 of the MGC IP address 2 of the MGC IP address and mask of the MGC IP address of the router connected with the UMG8900 IP address of the gateway If aging or not
<Interface IP address mask>
<Master or slave flag> <Slot No.> The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <If aging or not>
<Destination address>_1 <Destination address>_2 <Destination address mask> -
<Next hop address>
<Gateway IP>
Configuring E1 Physical Interfaces Carrying IP Signaling Packets

Table A-8 Data planning Parameter Name TDM optical port No. TDM port No. UMG8900 <TDM opt port No.> <TDM port No.> Interconnected Device 1 (MGC) -
Issue 02 (2008-05-07)
A-7
A Data Planning
Parameter Name IOE internal TDM port No. Port description Start TID End TID CMU module No. TDM start timeslot TDM end timeslot Serial interface ID Interface type Serial interface description MP enable VT interface ID IP address of the MGC IP address and mask of the MGC
UMG8900 <IOE internal TDM port No.> <Port description> <Start TID> <End TID> <CMU Module No.> <Start timeslot> <End timeslot> <Interface No.> <Interface type> <Interface description> <MP enable> <VT Interface No.> The same as that of the peer device The same as that of the peer device
Interconnected Device 1 (MGC) <Destination address> <Destination address mask>

Table A-9 Data planning Parameter Name Virtual media gateway ID UMG8900 Interconnected Device 1 (MGC) Interconnected Device 2 (DNS Server) -
<Virtual media gateway id>
A-8
Issue 02 (2008-05-07)
A Data Planning
Parameter Name Virtual media gateway ID
UMG8900
Interconnected Device 2 (DNS Server) -
In domain mode:<Virtual media gateway MID>_1 In IP mode: <Virtual media gateway MID>_2 In device mode: <Virtual media gateway MID>_3
Master MGC ID Slave MGC ID Master MGC ID type Slave MGC ID type Master MGC ID Slave MGC ID IP address of the master DNS server IP address of the slave DNS server
<Media gateway controller No.>_1 <Media gateway controller No.>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device
<Media gateway controller MID type>_1 <Media gateway controller MID type>_2 <Media gateway controller MID>_1 <Media gateway controller MID>_2 -
<DNS IP address>_1
<DNS IP address>_2
Configuring Links over UDP

Table A-10 Data planning Parameter Name Coding codec type UMG8900 <Codec type> Interconnected Device (MGC) The same as that of the peer device
Issue 02 (2008-05-07)
A-9
A Data Planning
Parameter Name UDP port No. to the master MGC UDP port No. to the slave MGC IP address of the master MGC IP address of the slave MGC UDP port No. to the master MGC UDP port No. to the slave MGC H.248 signaling link No. to the master MGC H.248 signaling link No. to the slave MGC
UMG8900 <Local UDP port No.>_1 <Local UDP port No.>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <H248 signaling link No.>_1 <H248 signaling link No.>_2
Interconnected Device (MGC) The same as that of the peer device The same as that of the peer device <Peer Master address>_1 <Peer Master address>_2 <Peer UDP port No.>_1 <Peer UDP port No.>_2 -
Configuring H.248 Links over SCTP

Table A-11 Data planning Parameter Name Coding codec type Checksum algorithm Path mode SCTP port No. to the master MGC SCTP port No. to the slave MGC IP address 1 of the master MGC IP address 2 of the master MGC IP address 1 of the slave MGC
A-10
UMG8900 <Codec type> <Checksum algorithm> <path mode> <Local SCTP port No.>_1 <Local SCTP port No.>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device
Interconnected Device (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Peer Master address>_1 <Peer Slave address>_1 <Peer Master address>_2
Issue 02 (2008-05-07)
A Data Planning
Parameter Name IP address 2 of the slave MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC H.248 signaling link No. to the master MGC H.248 signaling link No. to the slave MGC SubBoard No.
UMG8900 The same as that of the peer device The same as that of the peer device The same as that of the peer device <H248 signaling link No.>_1
Interconnected Device (MGC) <Peer Slave address>_2 <Peer SCTP port No.>_1 <Peer SCTP port No.>_2 -
<SubBoard No.>
Configuring H.245 Links

Table A-12 Data planning Parameter Name IP address of the master MGC IP address of the slave MGC Port No. to the master MGC Port No. to the slave MGC Port No. of H.245 signaling links to the master MGC Port No. of H.245 signaling links to the slave MGC H.245 signaling link No. to the master MGC UMG8900 The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Local port No.>_1 Interconnected Device (MGC) <Peer Master address>_1 <Peer Master address>_2 <Peer port No.>_1 <Peer port No.>_2 The same as that of the peer device The same as that of the peer device -
<Local port No.>_2
Issue 02 (2008-05-07)
A-11
A Data Planning
Parameter Name H.245 signaling link No. to the slave MGC
UMG8900 <H245 signaling link No.>_2
Interconnected Device (MGC) -
Configuring SDH Interface Protection

Table A-13 Data planning Parameter Name Protection group No. Interface type Recover mode Operate mode Optical splitter mode Channel number Recover time length (s) SD flag Interface ID Channel ID Operate mode UMG8900 <Protect group ID> <Interface type> <Recover mode> <Operate mode> <Optical Splitter mode> <Channel number> <Recover time length(s)> <SD flag> <Interface No.> <Work/Protect Channel ID> <Command type>
Configuring E1/T1 Interfaces

Table A-14 Data planning Parameter Name Start port No. End port No. Frame format Tx line code structure UMG8900 <Start Port No.> <End Port No.> <Frame Structure> <Tx line Code Structure> Interconnected Device The same as that of the peer device The same as that of the peer device
A-12
Issue 02 (2008-05-07)
A Data Planning
Parameter Name Rx line code structure Distance Mode
UMG8900 <Rx line Code Structure> <Distance Mode>
Interconnected Device The same as that of the peer device -
Configuring E3/T3 Interfaces

Table A-15 Data planning Parameter Name Start port No. End port No. Distance Mode frame type Start channel No. End channel No. Frame format UMG8900 <Start Port No.> <End Port No.> <Communication Distance> <Frame type> <Start Chan No.> <End Chan No.> <Frame mode> Interconnected Device The same as that of the peer device The same as that of the peer device
Configuring the SDH Interface (S2L/S1L)

Table A-16 Data planning Parameter Name SDH port No. E1/T1 channel No. Receiving C2 byte Transmitting C2 byte Receiving J0 byte Transmitting J0 byte UMG8900 <SDH port No.> <Channel No.> <Receiving C2 byte> <Transmitting C2 byte> <Receiving J0 byte> <Transmitting J0 byte> Interconnected Device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device
Issue 02 (2008-05-07)
A-13
A Data Planning
Parameter Name Receiving J1 byte Transmitting J1 byte Receiving J2 byte Transmitting J2 byte Frame type Frame mode 1 Load type Start Channel No. End Channel No. E1/T1 Frame format Period Status
UMG8900 <Receiving J1 byte> <Transmitting J1 byte> <Receiving J2 byte> <Transmitting J2 byte> <Frame type> <Frame mode 1> <Load type> <Start Channel No.> <End Channel No.> <Frame format> <Period> <Status>
Interconnected Device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device -
Configuring TDM Timeslots

Table A-17 Data planning Parameter Name Start TID End TID CASATTR No. UMG8900 <Start TID> <End TID> <CASATTR No.>
Configuring Trunk Group Management

Table A-18 Data planning Parameter Name Trunk group No. UMG8900 <TG No.>
A-14
Issue 02 (2008-05-07)
A Data Planning
Parameter Name Trunk group information Start TID End TID
UMG8900 <TG No. Info> <Start TID> <End TID>
Configuring Office Direction

Table A-19 Data planning Parameter Name Office No. Port No. Start port No. End port No. UMG8900 <Office No.> <Port No.> <Start Port No.> <End Port No.>
Configuring the FE Interface

Table A-20 Data planning Parameter Name Interface ID VLAN ID MAC address IP address VLAN domain ID Bearer bandwidth Max transmission unit Duplex mode Domain UMG8900 <Interface No.> <VLAN ID> <MAC address> <IP address> <VLAN domain ID> <VLAN bear bandwidth(Kbps)> <The max. transmission unit> <Duplex mode> <Domain>
Issue 02 (2008-05-07)
A-15
A Data Planning
Configuring the GE Interface

Table A-21 Data planning Parameter Name Interface ID VLAN ID MAC address IP address VLAN domain ID Bearer bandwidth Max transmission unit Duplex mode Domain Auto negotiation UMG8900 <Interface No.> <VLAN ID> <MAC address> <IP address> <VLAN domain ID> <VLAN bear bandwidth(Kbps)> <The max. transmission unit> <Duplex mode> <Domain> <Auto negotiation>
Configuring the ATM Interface

Table A-22 Data planning Parameter Name SDH port No. C2 byte J0 byte J1 byte K1 byte K2 byte VPI VCI Default static MAP Source IP address Encapsulation protocol Destination IP address UMG8900 <SDH port No.> <C2 byte> <J0 byte> <J1 byte> <K1 byte> <K2 byte> <VPI> <VCI> <Default static MAP> <Source IP address> <Enc protocol> <Destination IP address>
A-16
Issue 02 (2008-05-07)
A Data Planning
Parameter Name ATM interface No. Maximum transmission unit of the ATM interface Enable ATM interface CRC length
UMG8900 <Interface No.> <The max. transmission unit> <Interface enable> <Length of CRC>
Configuring the IP over E1 Interface

Table A-23 Data planning Parameter Name TDM optical port No. TDM port No. IOE internal port No. TDM start timeslot TDM end timeslot Serial interface ID Route type Destination IP address Route No. Transmitting board type Transmitting board No. Transmitting IP address VPI VCI Interface ID MP enable VT Interface No. UMG8900 <TDM opt port No.> <TDM port No.> <IOE internal TDM port No.> <Start timeslot> <End timeslot> <Serial Interface No.> <Routing Type> <Remote IP address> <Routing No.> <Transmitting board type> <Transmitting board No.> <Transmitting IP address> <VPI> <VCI> <Interface No.> <MP enable> <VT Interface No.>
Issue 02 (2008-05-07)
A-17
A Data Planning
Configuring the IP Address

Table A-24 Data planning Parameter Name Interface type Interface IP address Interface IP address mask Master or slave flag In VLAN Interface ID UMG8900 <Interface type> <Interface IP address> <Interface IP address mask> <Master or slave flag> <In VLAN> <Interface No.>
Configuring IP Interface Protection

Table A-25 Data planning Parameter Name Interface type Interface ID BFD configuration name Detect type Source IP address Destination IP address Domain Protection group No. Recover mode Operate mode Optical splitter mode Channel number Recover time length (s) SD flag Interface ID Channel ID UMG8900 <Interface type> <Interface No.> <BFD configuration name> <Detect type> <Source IP address> <Destination IP address> <Domain> <Protect group ID> <Recover mode> <Operate mode> <Optical Splitter mode> <Channel number> <Recover time length(s)> <SD flag> <Interface No.> <Work/Protect Channel ID>
A-18
Issue 02 (2008-05-07)
A Data Planning
Configuring the Gateway IP Address

Table A-26 Data planning Parameter Name IP address of the gateway If aging or not UMG8900 <Gateway IP> <If aging or not>
Configuring SIGTRAN of MTP2-M2UA

Table A-27 Data planning Parameter Name UMG8900 Interconnect ed Device 1 (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device <Remote port No.>_1 <Remote port No.>_2 <Remote address1>_1 Interconnecte d Device 2 (DNS) Interconnecte d Device 3 (BSC/PSTN Switch) -
Checksum and algorithm Link group No. Use text-type interface ID Work mode
<Checksum algorithm> <Link set No.> <Use text-type interface ID> <Traffic mode>
Link No. to the master MGC Link No. to the slave MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC IP address 1 of the master MGC
<Link No.>_1 <Link No.>_2 <Local port No.>_1 <Local port No.>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device
Issue 02 (2008-05-07)
A-19
A Data Planning
Parameter Name
UMG8900
Interconnect ed Device 1 (MGC) <Remote address2>_1 <Remote address1>_2 <Remote address2>_2 -
Interconnecte d Device 2 (DNS)
Interconnecte d Device 3 (BSC/PSTN Switch)
IP address 2 of the master MGC IP address 1 of the slave MGC IP address 2 of the slave MGC Priority of the M2UA link to the master MGC Priority of the M2UA link to the slave MGC IP address of the DNS server Path Mode MTP2 link No. E1/T1 No. Start timeslot No.
The same as that of the peer device The same as that of the peer device The same as that of the peer device <Priority>_1
<Priority>_2
The same as that of the peer device <Path Mode> <Link No.> <E1T1 No.> <Start time slot>
<DNS IP address> -
The same as that of the peer device The same as that of the peer device -
End timeslot No.
<End time slot>
Subboard No. Integer interface ID
<SPF sub-board No.> <Int-type interface ID>
A-20
Issue 02 (2008-05-07)
A Data Planning
Configuring SIGTRAN of LAPV5-V5UA

Table A-28 Data planning Parameter Name UMG8900 Interconnected Device 1 (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Remote port No.>_1 <Remote port No.>_2 <Remote address1>_1 <Remote address2>_1 <Remote address1>_2 <Remote address2>_2 Interconnected Device 2 (V5 AN) -
Checksum and algorithm Link group No. Use text-type interface ID Work mode Link No. to the master MGC
<Checksum algorithm> <Link set No.> <Use text-type interface ID> <Traffic mode> <Link No.>_1
Link No. to the slave <Link No.>_2 MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC IP address 1 of the master MGC IP address 2 of the master MGC IP address 1 of the slave MGC IP address 2 of the slave MGC Priority of the V5UA link to the master MGC Priority of the V5UA link to the slave MGC <Local port No.>_1 <Local port No.>_2 The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Priority>_1
<Priority>_2
Issue 02 (2008-05-07)
A-21
A Data Planning
Parameter Name
UMG8900
Interconnected Device 1 (MGC) The same as that of the peer device -
Interconnected Device 2 (V5 AN) <DNS-IP address> The same as that of the peer device -
IP address of the DNS server Path Mode E1ID E1 link ID E1 No. V5UA link No. Timeslot No. Subboard No.
The same as that of the peer device <Path Mode> <E1 ID> <E1 link ID> <E1 No.> <Link No.> <Time slot> <SPF sub-board No.>
Configuring SIGTRAN of Q.921-IUA

Table A-29 Data planning Parameter Name UMG8900 Interconnected Device 1 (MGC) The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device Interconnect ed Device 2 (PBX) -
SCTP port No. to the <Local port No.>_1 master MGC SCTP port No. to the <Local port No.>_2 slave MGC
A-22
Issue 02 (2008-05-07)
A Data Planning
Parameter Name
UMG8900
Interconnected Device 1 (MGC) <Remote port No.>_1 <Remote port No.>_2 <Remote address1>_1 <Remote address2>_1 <Remote address1>_2 <Remote address2>_2 -
Interconnect ed Device 2 (PBX) -
SCTP port No. to the The same as that of the master MGC peer device SCTP port No. to the The same as that of the slave MGC peer device IP address 1 of the master MGC IP address 2 of the master MGC IP address 1 of the slave MGC IP address 2 of the slave MGC Priority of the IUA link to the master MGC Priority of the IUA link to the slave MGC Path mode IP address of the DNS server Q.921 link No. Integer interface ID E1/T1 No. Timeslot No. The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Priority>_1
<Priority>_2
<Path Mode> <DNS-IP address> <Q921 Link No.> <Int-type interface ID> <E1T1 No.> <Time slot>
SPF subboard No. Network side and subscriber side
<SPF sub-board No.> <Net/User side>
Issue 02 (2008-05-07)
A-23
A Data Planning
Configuring SIGTRAN over M3UA (MTP3-M3UA)

Table A-30 Data planning Parameter Name Local entity index Local network ID Local Entity Type M3UA Destination entity index Network ID of the M3UA destination entity Destination Entity Type Destination signaling Point Code A-interface protocol number M3UA link set index Discard messages from lower priority link Working Mode M3UA signaling link No. to the master MGC M3UA signaling link No. to the slave MGC SCTP port No. to the master MGC SCTP port No. to the slave MGC IP address 1 of the master MGC IP address 2 of the master MGC UMG8900 <Local Entity Index> <Network Indicator> <Local Entity Type> <Destination Entity Index> The same as that of the peer device The same as that of the peer device <A-Interface Protocol Number> <Link Set Index> <Discard messages from lower priority link> <Working Mode> <M3UA Link No.>_1 Interconnected Device 1 (MGC) The same as that of the peer device <Network Indicator> Interconnected Device 2 (BSC) -
<Destination Entity Type> <Destination signaling Point Code> -
<M3UA Link No.>_2 <Local Port>_1 <Local Port>_2 The same as that of the peer device The same as that of the peer device
The same as that of the peer device The same as that of the peer device <First Address of Remote End>_1 <Second Address of Remote End>_1
A-24
Issue 02 (2008-05-07)
A Data Planning
Parameter Name SCTP port No. to the master MGC IP address 1 of the slave MGC IP address 2 of the slave MGC SCTP port No. to the slave MGC Path mode N7 destination signal point index N7 destination Network indicator N7 DPC OPC index N7 link set index N7 route index MTP2 link No. E1/T1 No. Start timeslot No. Subboard No. N7 link index N7 link code
UMG8900 The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Path Mode> The same as that of the peer device The same as that of the peer device The same as that of the peer device <OPC index> <Linkset index> <Route index> <Link No.> <E1T1 No.> <Start time slot> <SPF sub-board No.> <Link index> <Signaling link code>
Interconnected Device 1 (MGC) <Remote Port>_1 <First Address of Remote End>_2 <Second Address of Remote End>_2 <Remote Port>_2 -
Interconnected Device 2 (BSC) <DSP index> <Network indicator> <DSP> The same as that of the peer device The same as that of the peer device The same as that of the peer device
Issue 02 (2008-05-07)
A-25
A Data Planning
Configuring Semi-permanent Connection

Table A-31 Data planning Parameter Name UMG8900 Interconnected Device 1 (MGC) Interconnected Device 2 (BSC/ MSC/PSTN Switch) The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device
Start TID End TID Semi-permanent connection ID Semi-permanent connection name Interworking type Direction Source frame No. Source slot No. Source port No. Source timeslot No. Destination frame No. Destination slot No. Destination timeslot No. Destination timeslot No.
<Start TID> <End TID> <ID> <Name> <Link type> <Direction> <Src frame No.> <Src slot No.> <Src port No.> <Src timeslot No.> <Dst frame No.> <Dst slot No.> <Dst port No.> <Dst timeslot No.>
The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device
Configuring CAS
Table A-32 Data planning Parameter Name Signaling name
A-26
UMG8900 <CAS name>

Issue 02 (2008-05-07)
A Data Planning
Parameter Name Signaling type Line signaling type Register signaling type CAS attribute index Address send list Address receive list Pulse No. Line signaling conversion index Line command conversion index Register signaling conversion index Register command conversion index Start TID End TID
UMG8900 <signaling type> <Line signaling> <Register signaling> <Index> <Address send list> <Address receive list> <Pulse No.> <Line signaling conversion index> <Line command conversion index> <Register signaling conversion index> <Register command conversion index> <Start TID> <End TID>
Configuring Frames and Boards in the UAM

Table A-33 Data planning Parameter Name Start TID End TID Trunk type Frame ID Field ID Cabinet No. Frame No. in cabinet Frame type Mode CMU module No. Slot No. Board type UMG8900 <Start TID> <End TID> <Relay type> <Frame No.> <Place No.> <Cabinet No.> <Frame No. in cabinet> <Frame type> <Frame mode> <CMU module No.> <Slot No.> <Board type>
Issue 02 (2008-05-07)
A-27
A Data Planning
Parameter Name Link group No. Integer interface ID
UMG8900 <Link set No.> <Int interface ID>
Configuring Connections to the Main Frame and Direct Frame

Table A-34 Data planning Parameter Name Trunk interface board type SPF board No. SPF subboard No. First board No. First port No. Second board No. Second port No. Third board No. Third port No. Fourth board No. Fourth port No. Fifth board No. Fifth port No. Sixth board No. Sixth port No. Seventh board No. Seventh port No. Eighth board No. Eighth port No. UMG8900 <Trunk interface board type> <SPF board No.> <SPF subboard No.> <First trunk board No.> <First port No.> <Second trunk board No.> <Second port No.> <Third trunk board No.> <Third port No.> <Fourth trunk board No.> <Fourth port No.> <Fifth trunk board No.> <Fifth port No.> <Sixth trunk board No.> <Sixth port No.> <Seventh trunk board No.> <Seventh port No.> <Eighth trunk board No.> <Eighth port No.>
A-28
Issue 02 (2008-05-07)
A Data Planning
Configuring Connections to the RSP Subframe

Table A-35 Data planning Parameter Name Trunk interface board type PV8 frame No. First HW No. Second HW No. Third HW No. Fourth HW No. Fifth HW No. Sixth HW No. Seventh HW No. Eighth HW No. UMG8900 <Trunk interface board type> <PV8 slot No.> <First HW No.> <Second HW No.> <Third HW No.> <Fourth HW No.> <Fifth HW No.> <Sixth HW No.> <Seventh HW No.> <Eighth HW No.>
Configuring Connections to the RSA Subframe

Table A-36 Data planning Parameter Name Trunk interface board type RSA frame No. Slot No. of the RSA UMG8900 <Trunk interface board type> <RSA Frame No.> <RSA slot No.>
Configuring Connections From High-Density Subframe

Table A-37 Data planning Parameter Name Trunk interface board type RSU frame No. Cascading interface UMG8900 <Trunk interface board type> <RSU frame No.> <Cascade>
Issue 02 (2008-05-07)
A-29
A Data Planning
Configuring Asynchronous Tone

Table A-38 Data planning Parameter Name Tone type UMG8900 <Tone type>
Configuring StandAlone
Table A-39 Data planning Parameter Name Trunk group No. CMU module No. Start L3 E1 No. Start L2 E1 No. Start AN E1 No. Start TID V5 interface No. V5 interface ID Master link Logical C channel ID of the master link Slave link PSTN link Logical C channel ID of the PSTN link V5 start Phone Number V5 end Phone Number Start L3 Address Add Type Start phone number End phone number DIGITMAP Local IP address Local port No.
A-30
UMG8900 <V5 Group No.> <CMU Module No.> <Start L3 E1 ID> <Start L2 E1 ID> <Start AN E1 ID> <Start TID> <V5 Interface No> <V5 Interface ID> <Main Link> <Main Logical C channel ID> <Vice Link> <PSTN Link> <PSTN Logical C channel ID> <V5 Start Phone Number> <V5 End Phone Number> <Start L3 Address> <Add Type> <Start Phone Number> <End Phone Number> <DIGITMAP> <Local IP> <Locla Port>
Issue 02 (2008-05-07)
A Data Planning
Parameter Name iGWB IP iGWB port User type
UMG8900 <iGWB IP> <iGWB Port> <User Type>
Configuring UAM Environmental Monitoring

Table A-40 Data planning Parameter Name EMU ID Switch value index Alarm mode Analog value index Fan control mode Power type UMG8900 <EMU ID> <Switch value index> <Alarm mode> <Analog value index> <Fan control mode> <Power type>
Configuring DDI/AT0 Trunk Access Services

Table A-41 Data planning Parameter Name Start port No. CASATTR No. Port No. UMG8900 <Start port No.> <CASATTR No.> <Port No.>
Configuring Hotline Services

Table A-42 Data planning Parameter Name Port No. UMG8900 <Port No.>
Issue 02 (2008-05-07)
A-31
A Data Planning
Configuring DDN Services of the DSL

Table A-43 Data planning Parameter Name MTA index DSL frame No. DSL slot No. DSL port No. Port0 rate B channel of port 0 Semi-Permanent connection ID Link type Direction Source frame No. Source slot No. Source port No. UMG8900 <MTA index> <DSL frame No.> <DSL slot No.> <DSL port No.> <Port0 rate> <Port0 B channel> <ID> <Link type> <Direction> <Src frame No.> <Src slot No.> <Src port No.>
Configuring DDN Services of the HSL

Table A-44 Data planning Parameter Name Port No. V35 rate V35 clock mode V35 work mode E1 port E1 timeslot No. Clock source E1 Frame Semi-Permanent connection ID Direction Source UA frame No.
A-32
UMG8900 <Port No.> <V35 rate> <V35 clock mode> <V35 work mode> <E1 port No.> <E1 timeslot No.> <Clock source> <E1 Frame> <ID> <Direction> <Src frame No.>
Issue 02 (2008-05-07)
A Data Planning
Parameter Name Source UA slot No. Source UA port No. Destination UA frame No. Destination UA slot No. Destination UA port No.
UMG8900 <Src slot No.> <Src port No.> <Dst frame No.> <Dst slot No.> <Dst port No.>
Configuring DDN Services of the SDL

Table A-45 Data planning Parameter Name Port No. Board mode Clock source E1 Frame E1 port E1 timeslot No. Max rate Min rate Trans-mode SNR(dB) Work mode Frame switch Rx clock PLL lock Modem mode Board mode Clock source Semi-Permanent connection ID Direction Source UA frame No. UMG8900 <Port No.> <Board mode> <Clock source> <E1 frame> <E1 port No.> <E1 timeslot No.> <Max rate> <Min rate> <Trans-mode> <SNR(dB> <Work mode> <Frame switch> <Rx clock> <PLL lock> <Modem mode> <Board mode> <Clock source> <ID> <Direction> <Src frame No.>
Issue 02 (2008-05-07)
A-33
A Data Planning
Parameter Name Source UA slot No. Source UA port No. Destination UA frame No. Destination UA slot No. Destination UA port No.
UMG8900 <Src slot No.> <Src port No.> <Dst frame No.> <Dst slot No.> <Dst port No.>
Configuring Audio Dedicated Line Services

Table A-46 Data planning Parameter Name Port No. Work mode IP domain ID Local IP address Local UDP port No. Remote IP address Remote UDP port No. VPU board No. Service type Codec type PTime(ms) Semi-permanent connection ID Direction Source IP address Source IP port Destination UA frame No. Destination UA slot No. Destination UA port No. UMG8900 <Port No.> <Work mode> <IP domain ID> <Local IP address> <Local UDP port> <Remote IP address> <Remote UDP port> <VPU board No.> <Service type> <Codec> <PTime(ms)> <ID> <Direction> <Src IP address> <Src IP port> <Dst frame No.> <Dst slot No.> <Dst port No.>
A-34
Issue 02 (2008-05-07)
A Data Planning
Configuring Media Resource Parameters

Table A-47 Data planning Parameter Name Codec capability set MPTY channel number CAS channel number Support public codec Loading tone file type of the broadband codec capability set A/Mu law Start timer length(s) VAD option Packet Loss compensation G.711 PTime(ms) EEC tail length(ms) Comfort noise generation mode TFO switch Noise reduction aggressiveness (dB) Maximum gain for noise compensation (dB) Tone number tone mix state Resource type Threshold(%) General codec No. General codec name T38 PTime(ms) T38 Max transmit speed(bps) T38 train mode IFP type Redundant number Redundant package payload type
Issue 02 (2008-05-07)
UMG8900 <Codec> <MPTY channel num> <MPTY channel num> <Support public codec> <Tonefile Type in WideBand Codec set> <A/MU law> <Start timer length(s)> <VAD option> <Packet Loss compensation> <G.711 PTime(ms)> <EEC tail length(ms)> <Comfort noise generation mode> <TFO SWITCH> <Noise reduction aggressiveness (dB)> <Maximum gain for noise compensation (dB)> <Tone number> <tone mix state> <Resource type> <Alarm Threshold> <General Codec No.> <General Codec Name> <T38 Fax PTime(ms)> <T38 Max transmit speed(bps)> <T38 Train mode> <FAX TYPE> <Redundant number> <Redundant Package Payload Type>
A-35
A Data Planning
Parameter Name RFC2833 sending mode of DTMF Named packet payload type Send interval(ms) Codec RFCI length New RFCI No.
UMG8900 <RFC2833 sending mode of DTMF> <Named packet payload type> <Ipti> <Codec> <Rfci Length> <New RFCI No.>
Configuring Service Parameters

Table A-48 Data planning Parameter Name Alarm high threshold of fraction lost(%) Alarm low threshold of fraction lost(%) Lost rate of disconnection(%) Alarm high threshold of packet jitter (ms) Alarm low threshold of packet jitter (ms) Alarm high threshold of packet delay (ms) Alarm low threshold of packet delay (ms) Sending period of RTCP packet (s) Switch to send RTCP packets or not Release unstable links automatically or not RTCP transmission mode Send RTCP packets or not during IMS period Gmin of RTCP XR RTCP XR support mode E1 Switch to open RTCP or not None E1 Switch to open RTCP or not Release threshold for no RTCP packet received UMG8900 <Alarm high threshold of fraction lost(%)> <Alarm low threshold of fraction lost(%)> <Lost rate of disconnection(%)> <Alarm high threshold of packet jitter (ms)> <Alarm low threshold of packet jitter (ms)> <Alarm high threshold of packet delay (ms)> <Alarm low threshold of packet delay (ms)> <Sending period of RTCP packet (s)> <Switch to send RTCP packets or not> <Release unstable links automatically or not> <RTCP transmission mode> <Send RTCP packets or not during IMS period> <Gmin of RTCP XR> <RTCP XR support mode> <E1 Switch to open RTCP or not> <None E1 Switch to open RTCP or not> <Release threshold for no RTCP packet received>
A-36
Issue 02 (2008-05-07)
A Data Planning
Parameter Name Average rate Peak rate Dynamic adjust enable JBU depth for 5-ms service JBU depth for 20-ms service Host dynamic time Timeout(s) Launch time Initialization frame resend times Initialization frame resend interval Time align frame resend times Time align frame resend interval Rate control frame resend times Rate control frame resend interval
UMG8900 <Average rate (kbps)> <Peak rate (kbps)> <Dynamic adjust enable> <JBU depth for 5-ms service> <JBU depth for 20-ms service> <Host dynamic time> <Timeout(s)> <Launch time> <Initialization frame resend times> <Initialization frame resend interval(ms)> <Time align frame resend times> <Time align frame resend interval(ms)> <Rate control frame resend times> <Rate control frame resend interval(ms)>
Configuring QoS Parameters

Table A-49 Data planning Parameter Name Domain Protocol type Dscp/TOS value Precedence field Packet type Priority DSCP value High priority call threshold High rate occupied threshold Low rate occupied threshold UMG8900 <Domain> <Protocol type> <IPQOS Value> <Precedence> <Packet type> <Priority> <DSCP value> <High Priority Call Threshold> <High Rate Occupied Threshold(%)> <Low Rate Occupied Threshold(%)>
Issue 02 (2008-05-07)
A-37
A Data Planning
Configuring Firewall
Table A-50 Data planning Parameter Name ACL number Match sequence of ACL sub-rule Time range name Start time of the absolute time range Start date of the absolute time range End time of the absolute time range End date of the absolute time range Start time of the period time range End time of the period time range Week of the period time range Filtering rule IP address Reverse wildcard bits Whether to make log Interface type Interface ID Packet receiving and sending direction Default filtering rule UMG8900 <ACL number> <Match sequence of ACL sub-rule> <Time range name> <Start time> <Start date> <End time> <End date> <Start time> <End time> <Week> <Filtering rule> <IP address> <Reverse wildcard bits> <Whether to make log> <Interface type> <Interface No.> <Inbound/Outbound packets> <Default filtering rule>
Configuring IPSec
Table A-51 Data planning Parameter Name ACL number Filtering rule Protocol No. Source IP address UMG8900 <ACL number> <Filtering rule> <Protocol No.> <Source IP address> Interconnected Device The same as that of the peer device
A-38
Issue 02 (2008-05-07)
A Data Planning
Parameter Name Source reverse wildcard bits Destination IP address Destination reverse wildcard bits Transform name Protocol Encapsulation mode AH authentication ESP authentication ESP encryption SPG name SPG No. SPG mode Transform name AH input SPI AH input hex key AH output SPI AH output hex key AH input string key AH output hex key Local IP address Remote IP address
UMG8900 <Source reverse wildcard bits> The same as that of the peer device <Destination reverse wildcard bits> <Transform name> <Protocol> <Encapsulation mode> <AH authentication> <ESP authentication> <ESP encryption> <SPG name> <Num> <SPG MODE> <Transform name> <AH input SPI> <AH input key format> <AH output SPI> <AH output key format> <AH input string key> <AH output hex key> <Local IP> The same as that of the peer device
Interconnected Device <Destination IP address> The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device The same as that of the peer device <Peer IP>
Issue 02 (2008-05-07)
A-39
A Data Planning
Parameter Name Interface ID Enable IPSec Interface type
UMG8900 <Interface index> <Enable IPSec> <Interface type>
Interconnected Device -
Configuring SSH
Table A-52 Data planning Parameter Name SSH user name Authentication type RSA authentication public key file Server key update interval (hour) SSH authentication timeout (minute) SSH authentication retry times Enable SSHV1.X enhSession key exchange interval (hour) UMG8900 <Account> <Authentication Type> <RSA Authentication Pubilc Key File> <Server Key Update Interval(Hour)> <SSH Authentication Timeout(Minute)> <SSH Authentication Retry Times> <Enable SSHV1.X> <SessionKey Exchange Interval(Hour)>
A-40
Issue 02 (2008-05-07)
B Glossary
B
Numerics
3GPP 3rd generation partnership project See 3rd generation partnership project
Glossary
Founded in 1998, a project which aims to expedite the development of open, globally accepted technical specifications for the Universal Mobile Telecommunications System (UMTS), including the WCDMA and TD-SCDMA specifications. The WCDMA specifications 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 the 2.048 Mbit/s PCM digital transmission link to transmit the information related to call processing, mobility management and BSS management. It adopts the BSSAP protocol. See ATM adaptation layer A link between the customer and the telecommunication network. Many technologies, such as the copper wire, optical fiber, mobile, microwave and satellite, are used for access. A series of sequential rules consisting of permit | deny statements. In firewall, after ACL is applied to an interface on the router, the router decides which packet can be forwarded and which packet should be denied. In QoS, ACL is used to classify traffic. A local part of a telecommunication network. It is closest to the subscriber's home or enterprise and opposite to the core network. See access control list A digital multiplexing device that offers interfaces between different signals in a network. A number that identifies the location of a device in a network or the location on the hard disk or the memory, such as the IPv4 address or IPv6 address of a network entity. A protocol used in the IP network to map an IP address to a MAC address and thus enable the transmission of IP datagram across a LAN.
AAL access
access control list
access network ACL add/drop multiplexer address address resolution protocol
Issue 02 (2008-05-07)
B-1
B Glossary
adjacency
A portion of the local routing information which pertains to the reachability of a single neighbour ES or IS over a single circuit. Adjacencies are used as input to the Decision Process for forming paths through the routing domain. A separate adjacency is created for each neighbouron a circuit, and for each level of routeing (i.e. level 1 and level 2) on a broadcast circuit. See add/drop multiplexer See automatic gain control See authentication header The American National Standards Institute is a voluntary membership organization (run with private funding) that develops national consensus standards for a wide variety of devices and procedures. See access network A signal sent by an analog system without restriction specified on transmitted data. See american national standards institute A business that provides computer-based services to customers over a network. See automatic protection switching Indicates that the protective group uses the master/slave interfaces mode. The APS protective mode is supported.One protection group has one work channel and one protection channel. The switchover is performed based on the APS protocol. In the normal state, the work channel is working. If an APS switchover event is detected by the work channel, the services are switched to the protection channel. Indicates that the protective group uses one protective channel and N pieces of working channels. The APS protective mode is supported. 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 work channels are working. If an APS switchover event is detected by one work channel, the services are switched to the protection channel. The APS protection requires the interconnected device to support the APS protocol. A routing subdomain that maintains the detailed routing information about its own internal composition and the routing information enabling it to reach the other routing subdomains.In IS-IS and OSPF, it is a set of adjacent networks and hosts that have been administratively grouped together within an autonomous system. In IS-IS, an area corresponds to a Level 1 subdomain. See address resolution protocol See application service provider Logical association or channels that are established between two SCTP terminations according to the four-handshake system of the SCTP protocol. A digital announcement not always played by the MGW from beginning when receiving an announcement request. This kind of digital announcement is the asynchronous announcement. Therefore, a subscriber might hear a section of an announcement played repeatedly from beginning or middle. The MGW can play a broadcast announcement for multiple subscribers (no limit to the number of subscribers) at a time. The basic service announcement is a common asynchronous announcement.
ADM AGC AH american national standards institute AN analog signal ANSI application service provider APS APS 1+1
APS 1:N
area
ARP ASP association asynchronous announcement
B-2
Issue 02 (2008-05-07)
B Glossary
asynchronous transfer A data transfer technology based on cell, in which packets allocation relies on channel mode demand. It supports fast packet switching so that the network resources can be used efficiently. The size of a cell is fixed, 53 bytes in total. Here, 48 bytes form the payload and 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 over an ATM network. ATM switch A switch to transmit cells through an ATM network. It receives the incoming cell from an ATM endpoint or another ATM switch, analyzes and updates the cell header information, and then switches the cell to an output interface towards the destination. 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-replay services for IP. A procedure defined in Fast Ethernet in which a device accords with another device on a transmission mode before transmitting data. The mode can be 100 Mbit/s or 10 Mbit/ s and full or half duplex.
authentication header
auto negotiation
automatic gain control A process or means by which gain is automatically adjusted in a specified manner as a function of a specified parameter, such as received signal level. automatic protection switching Automatic Protection Switching (APS) is the capability of a transmission system to detect a failure on a working facility and to switch to a standby facility to recover the traffic.
available user capacity A capacity that specifies the number of new access users that the MSC server can accommodate. For example, if the initial capacity of the MSC server is 2000000, the available user capacity is 1500000 on condition that 500000 users are currently on line.
B
backup flag bandwidth It specifies whether the CN node is centralized backup MSC. The information of all the registered mobile phones in the pool is backed up to the centralized backup MSC. A range of transmission frequencies that a transmission line or channel can carry in a network. In fact, it is the difference between the highest and lowest frequencies the transmission line or channel. The greater the bandwidth, the faster the data transfer rate. A fixed radio transmitter/receiver that relays signals from and to the mobile terminals or handsets electronically within a specified range. It accommodates the devices that are necessary to set up and complete calls on handsets, such as the antenna and computer. Base Station Controller. A logical entity that connects the BTS with the MSC in a GSM network. It interworks with the BTS through the Abis interface, the MSC through the A interface. It provides the following functions: Radio resource management Base station management Power control Handover control Traffic measurement One BSC controls and manages one or more BTSs in an actual networking.
base station
base station controller
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.
Issue 02 (2008-05-07)
B-3
B Glossary
base station subsystem The protocol employed across the A interface in the GSM system. It is used to transport application part MM (Mobility Management) and CM (Connection Management) information to and from the MSC (Mobile Switching Centre). The BSS Application Part (BSSAP) is split into two sub application parts, these are: the BSS Management Application Part (BSSMAP) and the Direct Transfer Application Part (DTAP). base station subsystem This protocol is also used to convey general BSS (Base Station System) control management information between the MSC (Mobile Switching Centre) and the BSS. An example is application part the allocation of traffic channels between the MSC and the BSS. BFD bidirectional forwarding detection bit BITS bits per second BPS broadband broadcast See bidirectional forwarding detection A simple hello mechanism to detect failures in a network and work with the routing protocols to expedite failure detection. The smallest unit of information that can be used by a computer. It is a binary digit that can be 0 or 1. See building integrated timing supply system A rate at which the individual bits are transmitted through a communication link or circuit. Its unit can be bit/s, kbit/s, and Mbit/s. See bits per second A term that indicates the capacity with enough bandwidth to transmit voice, data and video signals. It supports transmission of large amount of information. An operation of sending electromagnetic signals to many receivers through the air or the public service network so that the information or programs can be transmitted at the same time. It also refers to the telecommunication mode that information sent by a terminal can be received by multiple receiving terminals in the computer network at the same time. See base station controller See base station subsystem See base station subsystem application part See base station subsystem management application part See base station In the situation of multiple synchronous nodes or communication devices, one can use a device to set up a clock system on the hinge of telecom network to connect the synchronous network as a whole, and provide satisfactory synchronous base signals to the building integrated device. A process of forming data into a block of the proper size, uninterruptedly sending the block in a fast operation, waiting for a long time, and preparing for the next fast sending. A tone indicating that the called party is busy. A unit of computer information equal to eight bits.
BSC BSS BSSAP BSSMAP BTS building integrated timing supply system
burst busy tone byte
C
call loss CAS A process during which a call cannot be set up or released owing to an error or failure. See channel associated signaling
B-4
Issue 02 (2008-05-07)
B Glossary
CAS multiframe
A multiframe set up based on timeslot 16. Each CAS multiframe contains 16 E1 PCM frames. Among the eight bits of timeslot 16 in the first of the 16 frames, the first four bits are used for multiframe synchronization. The multiframe alignment signal (MFAS) for synchronization is 0000. The last four bits are used as the not multiframe alignment signal (NMFAS). The NMFAS is XYXX. For the other 15 frames, timeslot 16 is used to transmit the exchange and multiplexing (E&M) signaling corresponding to each timeslot. See constant bit rate See common channel signaling See code division multiple access A 3G technology developed by Qualcomm of the US. Technology competitive with WCDMA, upgraded form CDMA1, and developed by the GSM community as a worldwide standard for 3G mobile. A geographic area in a cellular mobile telephone system where a cell site controls all cellular transmission. An MSC server in the MSC pool. This MSC server backs up the user data of each MSC server/VLR in the MSC pool. In addition, the MSC server backs up the call services for single MSC servers in the MSC pool when they are faulty and restores the call services for 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 CR messages are not distributed to the centralized backup MSC server.
CBR CCS CDMA CDMA2000
cell centralized backup MSC server
centralized forwarding Forwarding of OMC packets, H.248 packets and SIGTRAN packets through one IP interface. It can save IP address resources and avoid the complexed networking. challenge handshake A method of authentication that you can use when connecting to an ISP that allows you authentication protocol to log on automatically. channel A telecommunication path of a specific capacity and/or at a specific speed between two or more locations in a network. The channel can be established through wire, radio (microwave), fiber or a combination of the three. A channel refers to the CDR processing mode and storage directories that match a sorting condition. A channel corresponds to a CDR storage path. Channel Associated Signaling. A signaling system in which the signaling information is transmitted within the voice channel. China Signaling System No. 1 is a kind of CAS signaling. See challenge handshake authentication protocol A group of trunk circuits that are identical in bearer capability. See comfort noise generation CDMA is a form of wireless multiplexing, in which data can be sent over multiple frequencies simultaneously, optimizing the use of available bandwidth. In a CDMA system, data is broken into packets, each of which are given a unique identifier, so that they can be sent out over multiple frequencies and then re-built in the correct order by the receiver. The CNG is the algorithm that is used to generate comfort noise. The CNG expands the lower rate noise modeling data into a standard frame of G.729 data by filling in some of the less significant parameters. It then performs G.729 synthesis to generate the comfort noise.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd B-5
channel channel associated signaling CHAP circuit pool CNG code division multiple access
comfort noise generation
Issue 02 (2008-05-07)
B Glossary
common channel signaling
Common Channel Signaling. A signaling system used in telephone networks that separates signaling information from user data. A specified channel is exclusively designated to carry signaling information for all other channels in the system. China Signaling System No. 7 is a kind of CCS signaling. An extra intra-network or inter-network traffic resulting in decreasing network service efficiency. An ATM service category supporting applications like voice and video that require a constant bit rate. A multiframe is recommended by ITU-T G.704 and set up based on the first bit of timeslot 0. The CRC-4 multiframe is totally different from the CAS multiframe in principle and implementation. Each CRC-4 multiframe contains 16 PCM frames. Each CRC-4 multiframe consists of two CRC-4 sub-multiframes. Each CRC-4 sub-multiframe is a CRC-4 check block that contains 256 x 8 = 2048 bits. Bits C1 to C4 of a check block can check the previous check block.
congestion constant bit rate CRC-4 multiframe
D
differentiated services code point digital network DNS domain name service/ server double wrapping Values for a 6-bit field defined for the IPv4 and IPv6 packet headers that enhance class of service (CoS) distinctions in routers. A telecommunication network where information is first converted into distinct electronic pulses and then transmitted to a digital bit stream. See domain name service/server An Internet protocol to relate the service names or URLs to an IP address and conversely. A coding mode. In binary codec, parameters of the OCTET STRING type are coded with the standard BER grammar, and then H.248 binary coding is performed. It is stipulated in the H.248V2 protocol. For details, refer to the H.248V2 protocol. See differentiated services code point See dual tone multi-frequency A solution in which signaling transfer points are configured in pairs, that is, each signaling 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 dual homing solution is a network security solution put forward by Huawei first. This solution is used to ensure the security of MSC servers. Nowadays, the dual homing solution is applied in multiple commercial networks. It is an analogue inband access signalling system. See double wrapping
DSCP DTMF dual homing
dual tone multifrequency DW
E
E-LABEL E1 EC
B-6
See electronic label A European standard for high-speed data transmission at 2.048 Mbit/s. It provides 32 x 64 kbit/s channels. See echo cancellation
B Glossary
echo
In the traditional PSTN network, an echo is caused by the 2/4 wire conversion. In a common session, the end-to-end delay is small, an echo can be rapidly transmitted to the ears of speakers, and thus it is not easily felt. In long-distance calls or international longdistance calls, however, the end-to-end delay is big, and the echo canceller must be used to control echoes. Echo cancellation indicates to configure an echo canceller (usually called EC) in the communication network with the echo problem to reduce or eliminate echoes. See enhanced full rate The label that stores the codes for identifying objects in the format of electronic data.With the feature of large capacity, high confidentiality, read-write capability and working in had condition, it is much better than other electronic label. An element management system (EMS) manages one or more of a specific type of network elements (NEs). An EMS allows the user to manage all the features of each NE individually, but not the communication between NEs - this is done by the network management system (NMS). See element management system Encapsulating Security Payload is used in the transmission mode and tunnel mode. It adopts the encryption and authentication mechanism and provides the services such as data source authentication, data completeness, anti-replay, and secret security. A procedure of packetizing a protocol data unit in a group of protocol header and tail. A method used to guarantee the security and authenticity of data in end-to-end transmission. Encryption can be implemented through technologies such as data pseudorandom alteration and data substitution. A network entity that sends and receives packets in IS-IS. A technology that improves the quality of calls made on a digital mobile network. It is achieved through more efficient use of bandwidth. Technique for restoring integrity in data that is corrupted during transmission. It requires additional information to be sent with the original data and allows the data to be reconstructed from this information if the original data is corrupted. See encapsulating security payload A local technology based on CSMA/CD, The speed of Ethernet can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/ s or 10000 Mbit/s. It is easily maintained and of high reliability. The multiframe format of T1. Each multiframe comprises of 24 single frames.
echo cancellation EFR electronic label
element management system
EMS encapsulating security payload encapsulation encryption
end system enhanced full rate error correction
ESP ethernet extend superframe
F
file transfer protocol FTP is commonly used application. It is the Internet standard for file transfer. The file transfer provided by FTP copies a complete file from one system to another system. To use FTP we need an account to login to on the server, or we need to use it with a server that allows anonymous FTP (which we show an example of in this chapter). A security gateway that is positioned between two different networks, usually between a trusted network and the Internet. Data amount through a piece of equipment within a unit of time.
firewall flow
Issue 02 (2008-05-07)
B-7
B Glossary
flow control FR AMR codec algorithm
A method used to control the data packets that traverse a device so that the device is not to be overloaded because of heavy traffic. A full rate AMR codec algorithm that can be used only in GSM networks. The bit rate can 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, which adopts the algebraic code excitation linear prediction (ACELP) mechanism. Logical grouping of information sent as a data link layer unit over a transmission medium. Often refers to the header and the trailer, used for synchronization and error control, 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 at various layers of the OSI reference model and in various technology circles. The number of completing tasks per unit of time with Hz as its unit. 1 Hz = 1 cycle per second. FSK is used in low speed modems to modulate data that uses two frequencies, one of which is used to represent a binary one and the other a binary zero. In full-duplex transmission, two different frequencies are used in each direction, which leads to four different frequencies being used. See frequency shift keying See file transfer protocol It is a mode to transmit signals along a bearer channel or carrier in both directions at the same time. A rate for transmitting data services. The service bandwidth can be 9.6 kbit/s, 4.8 kbit/ s, or 2.4 kbit/s.
frame
frequency frequency shift keying
FSK FTP full duplex full rate
G
gateway A device that implements protocol conversion between different devices or networks. gateway GPRS support It is short for gateway GPRS support node. In the IMS, a UE can find the entry point of node the IMS through the GPRS process. That is, it can obtain the IP address of the P-CSCF through the GGSN. gCause global system for mobile communications GSM GSM EFR codec algorithm An event type stipulated in the H.248 protocol. Abbreviated GSM. The second-generation mobile networking standard defined by ETSI.
See global system for mobile communications The GSM enhanced full rate (EFR) algorithm, a compressed mixed codec algorithm based 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 spectrum transition characteristic of the voice, this codec mode improves the codec algorithm of the voice source to make the voice quality clear and sufficient, thus improving the voice quality greatly. When the bandwidth used in the EFR algorithm is the same as that in the FR algorithm, the EFR algorithm can improve the call quality under the condition of weak signals through a more advanced algorithm. This codec mode is used in GSM networks.
B-8
Issue 02 (2008-05-07)
B Glossary
GSM FR codec algorithm
The GSM full rate (FR) algorithm, a compressed mixed codec algorithm. It adopts the regular-pulse excitation-long term prediction (RPE-LTP) codec technology, and the compressed bit rate is 13 kbit/s. The outstanding characteristic of this codec mode is its stability, namely, it has relative stable voice quality under different mobile noise backgrounds and unstable wireless transmission condition (different error modes). This codec 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. See half rate A half rate AMR codec algorithm that can be used only in GSM networks. The bit rate can 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. The AMR algorithm is an adaptive rate-based codec algorithm, which adopts the algebraic code excitation linear prediction (ACELP) mechanism. A half rate GSM voice encoding algorithm.
HR HR AMR codec algorithm
HR codec algorithm
I
ICMP IETF IKE integrated services digital network See internet control message protocol See internet engineering task force See internet key exchange Integrated Services Digital Network (ISDN) is comprised of digital telephony and datatransport services offered by regional telephone carriers. ISDN involves the digitization of the telephone network, which permits voice, data, text, graphics, music, video, and other source material to be transmitted over existing telephone wires.
intermediate system-to- Intermediate System-to-Intermediate System. OSI link-state hierarchical routing intermediate system protocol based on DECnet Phase V routing whereby ISs (routers) exchange routing information based on a single metric to determine network topology. international standards A United Nations agency, based in Geneva, Switzerland, responsible for worldwide organization standards, including many networking standards. The OSI reference model, published as ISO standard 7498, was jointly developed by the ISO and the ITU. international telecommunication union internet internet control message protocol internet engineering task force A United Nations agency, one of the most important and influential recommendation bodies, responsible for recommending standards for telecommunication (ITU-T) and radio networks (ITU-R). A global network that uses IP to link various physical networks into a single network. An extension to the Internet Protocol. It allows for the generation of error messages, test packets and informational messages related to IP. An international community of network designers, operators, vendors, and researchers. IETF focuses on the evolution of the Internet architecture and the smooth operation of the Internet.
Issue 02 (2008-05-07)
B-9
B Glossary
internet key exchange
An optional function of the IPSec that provides ways for encryption. It is used to provide the function of sharing the internet key through negotiating whether the AH Header and the ESP Header of the IPSec packet are consistent. A protocol that enables data to be sent from one point to another on the Internet. A protocol that allows the message receiver to get a public key and use digital certificates to authenticate the sender's identity. See internet protocol An exclusive address on the Internet for each interface, which is 32 bits long. An IP address indicates a connection to a network, not a host. A general designation of a set of open protocols. With the IPSec, the encryption and data source verification between specific communication parties can ensure the confidentiality, intactness, and authenticity of data packets when they are transmitted over the Internet. See IP security protocol See intermediate system-to-intermediate system See internet security association and key management protocol See integrated services digital network See international standards organization See international telecommunication union
internet protocol internet security association and key management protocol IP IP address IP security protocol
IPSec IS-IS ISAKMP ISDN ISO ITU
J
jitter The variation in the time taken for packets to be delivered to an endpoint or network entity.
L
LAN LAPV5 signaling link link local area network See local area network A layer-2 link on the V5 interface. The V5 interface is the interface between the access network and switches, and it is a service node interface (SNI). It is the physical or logical connection for two pieces of equipment to communicate with each other. A network intended to serve a small geographic area, (few square kilometers or less), a single office or building, or a small defined group of users. It features high speed and little errors. Ethernet, FDDI and Toke Ring are three technologies implemented in LAN.
M
M3UA destination entity MAC An M3UA logical entity that equals the MTP3 destination signaling point. See media access control
B-10
Issue 02 (2008-05-07)
B Glossary
maximum transmission The MTU (Maximum Transmission Unit) is the size of the largest datagram that can be unit sent over a network. MD5 media access control See message digest 5 Media Access Control is the lower of the two sublayers of the Data Link Layer. In general terms, MAC handles access to a shared medium, and can be found within many different technologies. For example, MAC methodologies are employed within Ethernet , GPRS , and UMTS etc. Media Gateway. A logical entity that converts the format of the media of a network to meet the format requirement of another network. It can process audio services, video services 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 media conference. The Media Gateway Controller (MGC), also known as Call Agents or Soft Switches, handles registration, management, and control functionality of resources in the Media Gateway (MG). One-way hashing algorithm that generates a 128-bit hash for producing message authentication signatures. A part of the Signaling System 7 (SS7) used for communication in Public Switched Telephone Networks. MTP Level 3 provides routing functionality to transport signaling messages through the SS7 network to the requested endpoint. Message Transfer Part level 3 broadband provides message routing, discrimination and distribution (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 a broadband ISDN based protocol used typically in ATM (Asynchronous Transfer Mode). A descriptor that identify the function of a message. Stimulus call control has one message type, that is, information, while, the functional call control has several message types concerning call connection, call disconnection, and call status. See media gateway controller See media gateway See mobile identification number A number that identifies a mobile unit in wireless carrier's networks, and dials from other networks or fixed lines. In addition, it can be electronically checked to help prevent fraud. A mobile device, such as cellular phones or mobile personal digital assistants (PDAs).
media gateway
media gateway controller message digest 5 message transfer part
message transfer part level 3(broadband)
message type
MGC MGW MIN mobile identification number mobile station
mobile switching center Mobile Switching Center. A logical entity that provides interfaces for interworking with the function entities in a GSM/WCDMA system and the public network. It plays a core role for switch in the GSM/WCDMA system. It provides mobile management and switch to mobile subscribers and sets up communications between mobile subscribers, or between a mobile subscriber and a fixed line subscriber. modem MPLS MS MSC A device that enables data to be exchanged by interpreting and converting both analogue signals and digital signals. See multiprotocol label switching See mobile station See mobile switching center
Issue 02 (2008-05-07)
B-11
B Glossary
MSC pool MTP MTP3b MTU multiplexer
A pool formed by multiple MSC servers that serve a pool area. A device in the access network interconnects with multiple MSC servers in the pool. See message transfer part See message transfer part level 3(broadband) See maximum transmission unit An equipment which combines a number of tributary channels onto a fewer number of aggregate bearer channels, the relationship between the tributary and aggregate channels being fixed. A technology that uses short tags of fixed length to encapsulate packets in different link layers, and provides connection-oriented switching for the network layer on the basis of IP routing and control protocols. It improves the cost performance and expandability of networks, and is beneficial to routing. See multiplexer
multiprotocol label switching
MUX
N
narrowband A term used to depict the communication services that transmit over TDM timeslot. The PSTN is normally a narrowband network. A communication channel whose transmission rate is lower than 2 Mbit/s is usually considered to be narrowband. In communications, a system of interconnected communication facilities.
network
network service access A connection to a network that is identified by a network address. point network time protocol The Network Time Protocol was developed to maintain a common sense of "time" among Internet hosts around the world. Many systems on the Internet run NTP, and have the same time (relative to Greenwich Mean Time), with a maximum difference of about one second. Indicates that the protective group uses the master/slave interfaces mode. The APS protective mode is not supported.One protection group has 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 the master interface becomes DOWN, services on it are switched to the slave interface. This mode can be automatically supported by hardware for some interfaces, and is not required to be configured. Indicates that the protective group uses one protective channel and N pieces of working channels. The APS protective mode is not supported.One protection group has N+1 interfaces, and services are switched based on the UP/DOWN status of the interface. In the normal state, N interfaces are working. When one interface becomes DOWN, services on it are switched to the slave interface. See network service access point See network time protocol The point in an ATM network where an ATM connection is initiated or terminated. ATM endpoints include ATM-attached workstations, ATM-attached servers, ATM-to-LAN switches, and ATM routers. ATM The number of concurrently available IP terminations on a gateway.
non APS 1+1
non APS 1:N
NSAP NTP number of ATM endpoints number of IP terminations

B-12
Issue 02 (2008-05-07)
B Glossary
P
packet Data packets and local packets. Logical grouping of information that includes a header containing control information and (usually) user data. Packets are most often used to refer to network layer units of data. When a router receives a datagram, it is found that the destination IP address of the datagram do not match the IP address of the router, then the router queries the route list and forwards the datagram to another router or the destination host. A technology of compensating packets according to an appropriate algorithm if packets are lost in the transmission. Packets transmitted over SDH. See password authentication protocol A method for character level error detection. An extra bit added to a string of bits, usually a 7-bit ASCII character, so that the total number of bits 1 is odd or even (odd or even parity). Both ends of a data transmission must use the same parity. When the transmitting device frames a character, it counts the numbers of 1s in the frame and attaches the appropriate parity bit. The recipient counts the 1s and, if there is parity error, may ask for the data to be retransmitted.
packet forwarding
packet loss compensation packet over SDH PAP parity
password A method for verifying the identity of a user attempting to log on to a Point-to-Point authentication protocol Protocol (PPP) server. PAP is used if a more rigorous method, such as the Challenge Handshake Authentication Protocol (CHAP), is not available or if the user name and password that the user submitted to PAP must be sent to another program without encryption. PBX PCM PCR PDH peak peak cell rate pending transaction See private branch exchange See pulse code modulation See peak cell rate See plesiochronous digital hierarchy A time period when calls are the busiest in terms of service traffic. The maximum rate at which an ATM connection can accept cells. A transaction type stipulated in the H.248 protocol. For details, refer to the H.248 protocol. When a transaction lasts for a long time and the gateway processes the transaction, the gateway sends a Pending transaction to the MGC to inform the MGC of the processing to avoid retransmission. One of five categories of network management defined by ISO to manage the OSI networks. Performance management subsystems are in charging of analyzing and controlling network performance, including network throughput and error rates. A method of testing whether a device in the IP network is reachable according to sent ICMP Echo messages and received the response messages. See packet loss compensation
performance management ping PLC
Issue 02 (2008-05-07)
B-13
B Glossary
plesiochronous digital hierarchy
A technology used in telecommunications networks to transport large quantities of data over digital transport equipment such as fibre optic and microwave radio systems.Plesiochronous Digital Hierarchy is the first multiplexing hierarchy used in digital 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 varied between Europe, the US and Japan. See performance management
PM
point-to-point protocol Point-to-Point Protocol. A widely used WAN protocol designed to provide router to router and host to network connections over synchronous and asynchronous circuits. In addition, PPP has a built-in security mechanism. pool A concept raised in 3GPP TS 23.236. It means that multiple serving CN nodes in the network form a pool area. Within this area, an MS can roam at will without changing the serving CN node. A physical or logical communication interface. See packet over SDH See point-to-point protocol A telephone switch for use inside a corporation. A parameter for interconnection between the MGW and the peer MGC. Each profile can be considered as a subset of the H.248 standard. ETSI_GateControl/1 defines the ServiceChange message in a more detailed manner. For details, refer to ETSI TS 102 333 V1.1.2. ETSI_Tgw/1 defines partial subsystems in the NGN. For details, refer to ETSI 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>. On the Internet "protocol" usually refers to a set of rules that define an exact format for communication between systems. See public switched telephone network Network by which household and business phones are connected, typically by conventional fixed cables. It is the infrastructure providing a country's telephone system and it is the original analog telephone network. A variation above or below a normal level and a given duration in electrical energy.
port POS PPP private branch exchange profile negotiation
protocol PSTN public switched telephone network pulse
pulse code modulation A method of converting an analog voice signal to digital. It samples the signal 8,000 times per second and encodes the signal amplitude as an 8 bit value. The produced digital transmission rate is 64 kbit/s.
Q
Q.921 signaling link QoS quality of service An ISDN data link. The corresponding protocol is ITU-T Q.921. See quality of service Short for Quality of Service, QoS refers to service capacity assessment of IP network packets. Typically, the capability of supporting service requirements such as delay, delay jitter, and packet loss is considered as the core assessment object. Certain support technologies are required to meet the core requirements.
B-14
Issue 02 (2008-05-07)
B Glossary
R
radio network controller real time real time variable bit rate An entity that manages the radio part of the network in UMTS. Pertaining to the processing of data by a computer in connection with another process outside the computer according to time requirements imposed by the outside process. A rate that is intended for real-time applications. The rt-VBR services are connectionoriented with variable bit rates. The bandwidth used by a termination varies with the information sending rate of the termination. The ATM network guarantees the sustainable cell rate (SCR) for communication terminations, and requires that the terminations adopt rates equal to or lower than the peck cell rate (PCR) to send information. rt-VBR is typically used in the services that require much on time sensitivity such as image services. The statuses of sessions in the connection are contained in the packets to guarantee QoS of RTP. A host-to-host protocol that is used in real-time multimedia services such as Voice over IP (VoIP) and video. See radio network controller A route is a set of all sub-routes from local office to a destination office. A route contains multiple sub-routes and different routes may contain the same sub-routes. It is a piece of equipment that can forward the data, which should not be routed to it. In other words, a router can receive packets and forwards them to the right destination, because a router connects to more than one physical network. See real time variable bit rate See real-time control protocol See real-Time transport protocol
real-time control protocol real-Time transport protocol RNC route router
rt-VBR RTCP RTP
S
SCCP SCTP association See signaling connection control part An association is the logic relationship, or channel, established between two SCTP endpoints for data transmission, through the four-way handshake mechanism prescribed in SCTP. A networking of 3GPP R4 or later in which one MGW belongs to two MSC Servers. See synchronous digital hierarchy A set of elements, a security policy, a security authority and a set of security relevant activities in which the set of elements are subject to the security policy, administered by the security authority, for the specified activities. The Security Domain focuses on the identification of industry standards related to cybersecurity and the creation of policies to promote a more secure environment. A numeric identifier in IPsec, used with the destination address and security protocol to identify a security association (SA).
SCTP dual-homing networking mode SDH security domain
security parameter index
Issue 02 (2008-05-07)
B-15
B Glossary
segmentation server
A term used to set limits to collision domains, which allows Ethernet networks to achieve higher performance. It is also called network segmentation. 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 support A device in the mobile network that requests PDP contexts with a GGSN. node session initiation protocol An application layer protocol used for creating, modifying, and terminating a multimedia session in IP networks. It is part of the multimedia protocol system that IETF standardizes constantly. The SIP protocol is used to initiate the interactive user sessions containing the multimedia elements of video, voice, chatting, game, and virtual reality. See serving GPRS support node The instructions and the signals that are transmitted among different levels of exchanges to enable the network to run normally as an entire entity and thus implement call connections. The instructions control connections, and the signals indicate the execution results and running status. Signaling Connection Control Part. A protocol used by the MSOFTX3000 to establish circuit-independent signaling connections with the VLR, HLR, EIR, MSC, SMC, GMLC, and SCP through the SS7 signaling network. Signaling Point. A node that sends or receives signaling messages in a signaling network. A protocol used in telecommunication for delivering calls and services.SS7 typically employs a dedicated 64 kilobit data circuit to carry packetized machine language messages about each call connected between and among machines of a network to achieve connection control.
SGSN signaling
signaling connection control part signaling point signaling system 7
signaling transfer point Signaling Transfer Point. A node that transfers messages received from a signaling link to another. Element of an SS7-based Intelligent Network that performs routing of the SS7 signaling. SIP softswitch See session initiation protocol A term that refers to a softswitch device in a narrow sense. A softswitch provides call control 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 the bearer, and adopt the application program interface (API) and standard protocols. This makes it easy for network carriers to develop new services and realize new features. See synchronous optical network See signaling point See security parameter index See signaling system 7 A networking mode relative to the MSC Pool networking. In standard SG networking mode, the UMG8900 serves only as an SG in signaling processing. The signaling messages are processed only to the MTP3 layer. The UMG8900 does not resolve the MTP3 user contents; instead, the UMG8900 forwards them according to the destination point codes in the messages.
SONET SP SPI SS7 standard SG networking
B-16
Issue 02 (2008-05-07)
B Glossary
static route
A route that cannot adapt to the change of network topology. Operators must configure it manually. When a network topology is simple, the network can work in normal state if only the static route is configured. It can improve network performance and ensure bandwidth for important applications. Its disadvantage is: When a network is faulty or the topology changes, the static route does not change automatically. It must be changed by operators. See synchronous transport module See signaling transfer point An index that is used to uniquely identify a media stream. It is stipulated in the H.248 protocol. For details, refer to the H.248 protocol. A mode that identifies the direction of the media stream on a termination. It is stipulated in the H.248 protocol. For details, refer to the H.248 protocol. A type of board used in the separated architecture for the UMG8900. The board with the separated architecture consists of the baseboard and the subboard that work jointly to implement certain functions. Take the SPF as an example. The SPF subboard mainly processes layer-2 narrowband signaling such as signaling on the MTP2 links, Q.921 links, and LAPV5 links. The SPF baseboard typically processes layer-3 signaling. The technique used by the IP protocol to determine which network segment packets are destined 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. See softswitch The European counterpart to SONET. SONET is an intelligent system that provides advanced network management and a standard optical interface. Specified in the Broadband ISDN (B-ISDN) standard, SONET backbones are widely used to aggregate T1 and T3 lines. The European counterpart to SONET is the Synchronous Digital Hierarchy, and the term "SONET/SDH" is widely used when referring to SONET. A North American standard for Synchronous Data Transfer over Optical Networks.
STM STP stream index stream mode subboard
subnet mask
SX synchronous digital hierarchy
synchronous optical network
synchronous transport An information structure supporting section layer connections. module
T
T1 TCP temporary mobile subscriber identity A basic physical layer protocol that is used by the digital signal level 1 (DS1) multiplexing method in North America. See transmission control protocol A temporary mobile station identification assigned by the MSC. The TMSI is stored in the VLR and the SIM card and used by the MS to originate and receive calls. One TMSI maps to only one IMSI in a VLR area. The TMSI is used to conceal the international mobile subscriber identity (IMSI) for sake of security. A period of time starting when resources such as sessions and terminations are allocated and ended when the resources are released. See temporary mobile subscriber identity The topology of a network describes the way computers are connected together. Topology is a major design consideration for cost and reliability.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd B-17
time to live TMSI topology
Issue 02 (2008-05-07)
B Glossary
ToS traffic transit transmission control protocol transmit mode transparent transmission tunnel
See type of service The average number of calls made and received by call sources in a seizure duration. Connection to and use of a telecommunication path that is provided by a vendor. A connection oriented packet switching protocol that provides reliable data transmission service for applications on the Internet. The mode employed for transmission. Transmission of signals over the network without any change of structures and data. For signals, the network is transparent. One of the NAT traversal solutions. Configure the tunnel client in the private network and the tunnel server on the proxy device. The client transmits packets to the server through the UDP tunnel or HTTP tunnel. An IPSec mode of operation in which the entire IP packet, including the header, is encrypted and authenticated and a new VPN header is added, which protects the entire original packet. A field in an IP packet (IP datagram) that is used for quality of service (QoS). The TOS field is 8 bits, broken into five subfields.
tunnel mode
type of service
U
UBR UDP UMTS See unspecified bit rate See user datagram protocol See universal mobile telecommunication system
UMTS terrestrial radio A WCDMA radio network in UMTS. access network universal mobile telecommunication system unspecified bit rate 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 up to 2 Mbit/s. A transmission service that does not guarantee a fixed transmission capacity. Any application that can tolerate delays is ideally satisfied by an UBR.
user datagram protocol A connectionless transport layer protocol, in TCP/IP, that exchanges datagram without acknowledgments or guaranteed delivery. UTRAN See UMTS terrestrial radio access network
V
VAD variable bit rate See voice activity detection QoS class defined by the ATM Forum for ATM networks. VBR is subdivided into a real time (RT) class and non-real time (NRT) class. VBR (RT) is used for connections in which there is a fixed timing relationship between samples. See variable bit rate See virtual circuit identifier
VBR VCI
B-18
Issue 02 (2008-05-07)
B Glossary
video gateway
When the MGW serves as a VIG, audio, video and H.245 (multimedia communication control protocol) data is multiplexed in H.223 frames. The MGW needs to demultiplex H.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. This configuration is unnecessary in other networking applications. See video gateway A term that enables queuing, packet scheduling, and accounting rules to be applied to one or more logical interfaces.
VIG virtual channel
virtual circuit identifier A 16-bit field in the header of an ATM cell. The VCI, together with the VPI, identifies the next destination of a cell as it passes through a series of ATM switches on its way to its destination. virtual local area network virtual path identifier A LAN is divided into several logical LANs to suppress broadcast packets. Each virtual LAN is a broadcast area. Hosts in the same VLAN can directly communicate but hosts in different VLANs cannot. Thus, broadcast packets are restricted in a VLAN. 8-bit field in the header of an ATM cell. The VPI, together with the VCI, identifies the next destination of a cell as it passes through a series of ATM switches on its way to its destination. See virtual local area network
VLAN
voice activity detection Voice activity detection or voice activity detector is an algorithm used in speech processing wherein, the presence or absence of human speech is detected from the audio samples. The main uses of VAD are in speech coding and speech recognition. A VAD may not just indicate the presence or absence of speech, but also whether the speech is voiced or unvoiced, sustained or early, etc. VPI See virtual path identifier
W
W-CDMA WB-AMR wide band AMR See wideband code division multiple access See 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 division A radio interface technology used in most of the third-generation (3G) wireless systems. multiple access It is the third generation standard developed and supported by GSM proponents.
Issue 02 (2008-05-07)
B-19
Index
Index
C
cascading mixed cascading(UG01NET and BLU.A Configured), 3-20, 3-26 mixed cascading(UG02NET and BLU.C Configured), 3-26 SSM-256 self-cascading, 3-17 SSM-32 self-cascading, 3-19 cautions for data configuration, 1-5 centralized forwarding, 3-35 configuration index access gateway(AG), 2-4 NGN-enabled switch, 2-6 trunk gateway(TG), 2-3 video interworking gateway(VIG), 2-5 configuring ATM physical layer SDH interface protection, 12-8 configuring control interface IP over E1, 10-20 mixed cascading, 10-17 single-frame, 10-2 SSM-256 self-cascading, 10-10 SSM-32 self-cascading, 10-13 configuring gateway address, 13-18 configuring hardware, 8-1 configuring IP interface FE interface, 13-2 GE interface, 13-4 IP over E1, 13-9 configuring IP interface address, 13-13 configuring IP interface protection, 13-14 configuring MGW control data activate VMGW, 11-15 H.245 link, 11-12 H.248 link over SCTP, 11-8 H.248 link over UDP, 11-5 MGW data, 11-2 configuring NMS interface, 7-2 SNMP, 7-8 configuring office direction information, 12-15 configuring QoS parameter, 17-9 configuring service parameter, 17-6
Issue 02 (2008-05-07)
configuring signaling transfer based on CAS, 14-32 based on IUA, 14-15 based on M2UA, 14-2 based on M3UA, 14-21 based on semi-permanent connection, 14-29 based on V5UA, 14-8 configuring system parameter, 5-1 configuring system time, 6-1 configuring TDM interface E1/T1, 12-2 E3/T3, 12-3 SDH interface, 12-5 SDH interface protection, 12-8 configuring TDM timeslot, 12-11 configuring the clock, 9-1 configuring trunk group management, 12-13
D
dual homing, 3-40
F
frames and boards board, 3-7 numbering rules, 3-3 SSM-256 frame, 3-2 SSM-32 frame, 3-3
G
general planning of examples, 4-1 general procedures for data configuration, 2-2
I
interface protection, 3-41
M
method for data configuration using data script, 1-4 using data scripts, 1-4
i-1
Index
using equipment panel, 1-4 using MML command, 1-2
R
route backup, 3-51
S
security control configuration the firewall, 18-2 configuring IPSec, 18-4 configuring SSH, 18-8
V
virtual media gateway(VMGW), 3-41
i-2
Issue 02 (2008-05-07)

Configuration Guide (V100R007 02, NGN)

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Configuration Guide (V100R007 02, NGN)

Diunggah oleh

Hak Cipta:

Format Tersedia

HUAWEI UMG8900 Universal Media Gateway V100R007

Issue Date Part Number

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Huawei Technologies Co., Ltd.

Trademarks and Permissions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

2 General Description of Data Configuration.........................................................................2-1

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

11 Configuring MGW Control Data........................................................................................11-1

12 Configuring TDM Bearer.....................................................................................................12-1

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

14 Configuring Signaling Transfer..........................................................................................14-1

15 Configuring UAM Data........................................................................................................15-1

16 Configuring StandAlone......................................................................................................16-1 17 Configuring Service Resource Parameters........................................................................17-1

18 Configuring IP Network Security Data.............................................................................18-1

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

About This Document

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

About This Document

About This Document

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

1.1 Data Configuration Methods

1.1.1 MML Using Methods

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

Figure 1-1 MML command line

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

1.1.2 Methods of Using Device Panel

Data configuration of hardware (frames and boards) Routine query

1.1.3 Methods of Using Data Scripts

Deployment System expansion Software upgrade Routine maintenance

Huawei compiles a data script file under lab environment to:

Improve efficiency of data configuration Reduce errors of data configuration

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

1.2 Cautions for Data Configuration

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI UMG8900 Universal Media Gateway Configuration Guide

2 General Description of Data Configuration