SJ-20100211152857-010-ZXWN MSCS (V3.09.21) MSC Server Common Configuration Operation Guide

ZXWN MSCSMSC Server

Common Configura-tion Operation Guide

Version 3.09.21

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright 2010 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATIONor of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 Feb. 28, 2010 First edition

Serial Number: SJ-20100211152857-010

Contents

About This Manual............................................. I

Declaration of RoHS Compliance ....................... I

Data Making for New Commissioning ................1Overview....................................................................... 1

MGW Data Configuration ................................................. 1

Overview................................................................... 1

Interface Address Configuration.................................... 3

Overview .......................................................... 3

Creating a Loopback Interface ............................. 4

Creating an SIPI Interface Address....................... 5

Creating a Static Route ............................................... 7

Adjacent Office and Topology Configuration.................... 8

Overview .......................................................... 8

Creating an MGW Adjacent Office ......................... 9

Creating an MGW Voice CODEC Template .............14

Creating a Topology Node...................................15

Creating an Inter-MGW Bearer Mode ...................19

SIGTRAN Configuration ..............................................22

Overview .........................................................22

Creating an SCTP..............................................24

Creating an ASP................................................27

Creating an AS .................................................28

Creating an M3UA Static Route ...........................32

Creating the SIO-Locating-AS .............................33

H.248 Configuration...................................................35

Overview .........................................................35

Creating MGC Static Data...................................37

Creating an MGW Static Data Template ................38

Creating MGW Static Data ..................................40

Creating a TID Analyzer .....................................41

Creating a TID Analyzer Entry.............................43

Confidential and Proprietary Information of ZTE CORPORATION I

ZXWN MSCS Common Configuration Operation Guide

HLR Data Configuration ..................................................44

Overview..................................................................44

Creating a HLR Adjacent Office....................................47

Signaling Data Configuration .......................................48

Creating a Signaling Link Set ..............................48

Creating an SPB-Accessed Signaling Link .............50

Creating a Signaling Route .................................53

Creating a Signaling Office .................................55

Creating IMSI Analysis ...............................................57

SCCP Data Configuration ............................................59

Creating GT Translation Selector .........................59

Creating GT Translation Data ..............................63

STP Data Configuration ..................................................69

Overview..................................................................69

Creating an STP Adjacent Office ..................................71

Signaling Data Configuration .......................................73

Creating a Signaling Link Set to the STP...............73

Creating a Signaling Link to the STP ....................75

Creating a Signaling Route to the STP..................78

Creating a Signaling Office to the STP..................79

Creating a GT Translation Data ....................................81

SCP Data Configuration (Destination Network)...................85

Overview..................................................................85

Creating a Signaling Subsystem ..................................87

Creating GT Translation Data.......................................89

Creating the CAMEL Configuration................................93

Recharge and Query Configuration...............................94

Creating CAMEL Access Subscription

Information...........................................94

Creating Called Number Analysis.........................97

Configuration Related to Intelligent Tone Play ................99

Creating Interconnection Conversion for Service

Keys................................................... 100

Creating Tone Keys on the MGW Tone Board ......... 102

SMC Data Configuration ............................................... 104

Overview................................................................ 104

Creating GT Translation Data..................................... 106

Modifying VLR-Supported Services ............................. 110

Modifying Mobile Data of Local Office.......................... 111

PSTN/2G MSC (M3UA) Data Configuration....................... 111

II Confidential and Proprietary Information of ZTE CORPORATION

Overview................................................................ 111

Creating 2G MSC/PSTN Adjacent Office....................... 113

Configuration Related to Trunk and Route ................... 115

Creating a DT Trunk Group ............................... 115

Creating a PCM System.................................... 119

Creating an Outgoing Route.............................. 121

Creating an Outgoing Route Set ........................ 122

Creating an Outgoing Route Link ....................... 123

SIGTRAN Configuration ............................................ 126

Creating an SCTP............................................ 126

Creating an ASP.............................................. 129

Creating an AS ............................................... 130

Creating an M3UA Static Route ......................... 133

Creating the SIO-Locating-AS ........................... 134

BSC Data Configuration ................................................ 137

Overview................................................................ 137

Office Direction and Topology Configuration................. 139

Creating a BSC Adjacent Office ......................... 139

Creating BSC Office Direction............................ 143

Creating a BSC Topology Node.......................... 145

Creating the Topology Relationship between BSC

and MGW............................................ 148

Trunk and PCM Configuration .................................... 150

Creating a DT Trunk Group ............................... 150


SIGTRAN Configuration ............................................ 159

Creating an SCTP............................................ 159

Creating an ASP.............................................. 161

Creating an AS ............................................... 163

Creating an M3UA Static Route ......................... 165

Creating the SIO-Locating-AS ........................... 166

RNC Data Configuration................................................ 168

Overview................................................................ 168

Creating an RNC Adjacent Office................................ 170

Office Direction and Topology Configuration................. 174

Creating RNC Office Direction ........................... 174

Creating an RNC Topology Node ........................ 178

Creating the Topology Relationship between RNC

and MGW............................................ 181

Trunk and PCM Configuration .................................... 183

Confidential and Proprietary Information of ZTE CORPORATION III


Creating an ATM Trunk Group ........................... 183


Access Data Configuration.............................193Overview.................................................................... 193

Creating Emergency Call Center .................................... 194

Special Serivce Configuration ........................................ 196

Creating a Special Service Phone Group...................... 196

Creating the Special Service Phone Called Number

Analysis ......................................................... 199

LAI and GCI/Service Area Configuration.......................... 201

Creating a LAI Controlled by the Local Office ............... 201

Creating an Adjacent LAI .......................................... 205

Creating a Global Cell............................................... 209

Creating a Service Area............................................ 211

Number Analysis Data Making.......................213Number Analysis ......................................................... 213

Number Analysis Configuration...................................... 218

Overview................................................................ 218

Creating a Number Analyzer Entry ............................. 218

Creating a DAS ....................................................... 221

Setting the Default DAS Template of the Local

Office............................................................. 223

Creating a DAS Template .......................................... 226

Creating the Called Number Analysis .......................... 230

Tone Configuration........................................257Creating MSCS Tones in Batches.................................... 257

Creating the Fixed Tone Play Data.................................. 258

Creating the Basic Service Tone Play Data....................... 265

Creating the Intelligent Service Tone Play Data................ 274

Figure............................................................283

Table .............................................................285

Index ............................................................289

IV Confidential and Proprietary Information of ZTE CORPORATION

About This Manual

Purpose At first, thank you for choosing ZXWN wireless core network sys-tem of ZTE Corporation!

ZXWN system is the 3G mobile communication system developedbased on the UMTS technology. ZXWN system boasts powerfulservice processing capability in both CS domain and PS domain,providing more abundant service contents. Comparing with theGSM, ZXWN provides telecommunication services in wider range,capable of transmitting sound, data, graphics and other multi-me-dia services. In addition, ZXWN has higher speed and resource uti-lization rate. ZXWN wireless core network system supports both2G and 3G subscriber access, and provides various services re-lated with the 3G core network.

The ZXWN MSCS system is designed for the UMTS system at thecore network control level. It supports the GSM core network,UMTS protocols in the R99/R4/R5 stage and relevant functions atthe same time, and provides the carriers with an overall solutionto the evolution from the GSM core network to the 3GPP R99 andthen to the 3GPP R5.

The ZXWN MSCS system completes the functions of the MobileSwitching Center Server and the Visitor Location Register (VLR)together, and provides the Service Switching Point (SSP) functionsof intelligent calls. The ZXWN MSCS system supports the MGCFfunction, and the coexistence of the MGCF and GMSCS. It also cansmoothly upgrade to the MGCF.

This manual aims to help operators master the methods of com-mon data configuration of ZXWN MSCS.

IntendedAudience

This document is intended for engineers, technical and mainte-nance personnel who have mastered the principles of mobile net-work communications.

Prerequisite Skilland Knowledge

To use this document effectively, users should have a general un-derstanding of wireless telecommunications technology. Familiar-ity with the following is helpful:

CS network and its network elements

The basic knowledge, interfaces and protocols, and servicefunctions of ZXWN MSCS

What Is in ThisManual

This manual contains the following chapters:

Chapter Summary

Chapter 1, Data Makingfor New Commissioning

Introduces the procedure and method forcollecting and configuring interconnectiondata so as to add various offices on thesoft-switch equipment that is normallyrunning in the current network

Chapter 2, Access DataConfiguration

Introduces the procedure and method forconfiguring the location area and the celldata on the MSCS



Chapter Summary

Chapter 3, NumberAnalysis Data Making

Introduces the procedure and methodfor configuring the number analysis datawhen the soft-switch equipment runs inthe current network normally

Chapter 4, ToneConfiguration

Introduces the procedure and method forconfiguring the tone resources and toneplay data

FCC ComplianceStatement

This device complies with part 15 of the FCC Rules. Operation issubject to the following two conditions.

1. This device may not cause harmful interference.

2. This device must accept any interference received, includinginterference that may cause undesired operation.

Changes or modifications not expressly approved by the party re-sponsible for compliance could void the user's authority to operatethe equipment.

Conventions ZTE documents employ the following typographical conventions.

Typeface Meaning

Italics References to other Manuals and documents.

Quotes Links on screens.

Bold Menus, menu options, function names, input fields,radio button names, check boxes, drop-down lists,dialog box names, window names.

CAPS Keys on the keyboard and buttons on screens andcompany name.

Note: Provides additional information about a certaintopic.

Checkpoint: Indicates that a particular step needs tobe checked before proceeding further.

Tip: Indicates a suggestion or hint to make thingseasier or more productive for the reader.

Mouse operation conventions are listed as follows:

Typeface Meaning

Click Refers to clicking the primary mouse button (usually theleft mouse button) once.

Double-click

Refers to quickly clicking the primary mouse button(usually the left mouse button) twice.

Right-click Refers to clicking the secondary mouse button (usuallythe right mouse button) once.


Declaration of RoHSCompliance

Tominimize the environmental impact and take more responsibilityto the earth we live, this document shall serve as formal declara-tion that ZXWN MSCS manufactured by ZTE CORPORATION are incompliance with the Directive 2002/95/EC of the European Parlia-ment - RoHS (Restriction of Hazardous Substances) with respectto the following substances:

Lead (Pb)

Mercury (Hg)

Cadmium (Cd)

Hexavalent Chromium (Cr (VI))

PolyBrominated Biphenyls (PBBs)

PolyBrominated Diphenyl Ethers (PBDEs)

The ZXWN MSCS manufactured by ZTE CORPORATION meetthe requirements of EU 2002/95/EC; however, some assembliesare customized to client specifications. Addition of specialized,customer-specified materials or processes which do not meet therequirements of EU 2002/95/EC may negate RoHS compliance of theassembly. To guarantee compliance of the assembly, the need forcompliant product must be communicated to ZTE CORPORATION inwritten form. This declaration is issued based on our current levelof knowledge. Since conditions of use are outside our control, ZTECORPORATION makes no warranties, express or implied, and assumesno liability in connection with the use of this information.



This page is intentionally blank.


C h a p t e r 1

Data Making for NewCommissioning

Table of ContentsOverview........................................................................... 1MGW Data Configuration ..................................................... 1HLR Data Configuration ......................................................44STP Data Configuration ......................................................69SCP Data Configuration (Destination Network).......................85SMC Data Configuration ................................................... 104PSTN/2G MSC (M3UA) Data Configuration........................... 111BSC Data Configuration.................................................... 137RNC Data Configuration.................................................... 168

OverviewDescription This chapter introduces the procedure and method of collecting

and making interconnection data so as to add various office direc-tions on the ZXWN MSCS equipment.

MGW Data Configuration

Overview

TypicalNetworking

Mc interface is the interface between MSCS and MGW. The net-working structure is shown in Figure 1.

Confidential and Proprietary Information of ZTE CORPORATION 1


FIGURE 1 NETWORKING BETWEEN MSCS AND MGW

The Mc interface usually uses the IP bearer. Its protocol stack usesthe H.248/M3UA/SCTP/IP mode.

Data Collection Collect the data related to the Mc interface before data configura-tion, as described in Table 1.

TABLE 1 DATA COLLECTION TABLE

Parameter Items Parameter Values

Real address of the MSCS 192.168.1.11

Loopback address of the MSCS 192.168.11.11

Port number of the MSCS 2001

Real address of the MGW 192.168.1.31

Loopback address of the MGW 192.168.31.31

Port number of the MGW 2001

Coding scheme of H.248 protocol TEXT

MSCS signaling point code 1.11.2

MGW signaling point code 1.31.2

ConfigurationFlow

This configuration aims to complete the interconnection betweenthe MSCS and the MGW over the Mc interface so as to achieve themanagement and control over the media resources of the MGW.Table 2 describes the configuration flow.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Data Making for New Commissioning

TABLE 2 CONFIGURATION FLOW

Steps Operations Related Command

1 Creating a loop-back interfaceINTERFACELOOPBACK

ADD IP ADDRESS

2 Creating an SIPI interfaceaddressINTERFACE

ADD IP ADDRESS

3 Creating a static route ADD IP ROUTE

4 Creating an MGW adjacentoffice ADD ADJOFC

5 Creating an MGW voiceCODEC template ADD CODECTPL

6 Creating a topology node ADD TOPO

7 Creating an inter-MGW bearermode ADD MGWBEARMOD

8 Creating an SCTP ADD SCTPCONN

9 Creating an ASP ADD ASP

10 Creating an AS ADD AS

11 Creating an M3UA static route ADD M3UART

12 Creating the SIO-locating-AS ADD SIOLOCAS

13 Creating MGC static data ADD MGCSCFG

14 Creating an MGW static datatemplate ADD MGSTPL

15 Creating MGW static data ADD MGSCFG

16 Creating a TID analyzer ADD TIDANL

17 Creating a TID analyzer entry ADD TIDENTR

Interface Address Configuration

Overview

Introduction Interface IP addresses are planned according to the actual net-working applications. The IP address of Nc, Iu-CS and other in-terfaces can be configuration independently, or share with the Mcinterface address.



Creating a Loopback Interface

Prerequisites Before the operation, it is required to confirm:

The RPUmodule configuration is completed, and the RPU worksnormally.

The MML Terminal window is opened.

Context Creating the loopback interface means creating the service ad-dress on the RPU loopback port. Since the service address of Mcinterface can use ports 1 and 2, it is recommended that each portis configured with one IP address.

Steps 1. If no exchange is specified, execute command SET on theMMLTerminal window or select a NE from the system tree to spec-ify the exchange to be configured.

Example: Select the MSCS exchange with ID as 11 from thesystem tree.

SET:NEID=11;

2. Create the RPU loop back interface. The command is INTERFACE LOOPBACK.

Port represents the port number, ranging from 1 to 128.

Example: Create the loop-back interface whose port numberis 1.

The command is as follows.

INTERFACE LOOPBACK:PORT=1;

3. Create the interface address. The command is ADD IP ADDRESS.

Table 3 describes the main parameters in the ADD IP AD-DRESS command.

TABLE 3 PARAMETERS IN THE ADD IP ADDRESS COMMAND

ParameterName

ParameterDescription Instruction

ADDRESS IP addressIt is a mandatory parameter.The IP address of theloop-back address.

MASK MaskIt is a mandatory parameterof 32-bit. In general, it is255.255.255.255.

BROADCASTIP Broadcast IPaddressIt is an optional parameter. Ingeneral, it is 255.255.255.255.

Example: Create a loop back address with the following re-quirements.

IP address: 192.168.11.11

Subnet mask: 255.255.255.255.




ADD IP ADDRESS:ADDRESS="192.168.11.11",MASK="255.255.255.255",BROADCASTIP="255.255.255.255";

4. Save the online configured data. Otherwise, these will losswhen the RPU is restarted.The command is SAVE ONLINEDATA;.

5. Exit the interface configuration mode. The command is EXIT;

END OF STEPS

Creating an SIPI Interface Address


The SIPI unit is created.


Context MSCS is interconnected to MGW on the CE through its SIPI board.The online configuration of SIPI board interface is to assign an IPaddress to some physical port of this SIPI board.



SET:NEID=11;

2. Enter the SIPI board interface configuration mode. The com-mand is INTERFACE.

Table 4 describes the main parameters in the INTERFACEcommand.

TABLE 4 INTERFACE REAL INTERFACE

ParameterName


SUBSYS-TEM Subsystem ID

It is a mandatory parameter.Select the default value 0.

MODULE Module No. It is a mandatory parameter.Select the default value 1.

UNIT Unit No.

It is a mandatory parameter. Itis the unit number of the realinterface. Select the unit numberof the board corresponded by theinterface.

SUNIT Subunit NoIt is a mandatory parameter. Realinterfaces sub-unit number fixedlyadopts 1.

PORT Port number

It is a mandatory parameter. Theport number refers to the networkinterface serial number of theSIPI rear board for connecting tothe external. The four network



ParameterName


interfaces are numbered 1 to 4from top to bottom. Only the firstport is used.

Example: Create the interface address of SIPI board. The con-figuration requirements are as follows.

Unit number: 321

Sub-unit number: 1

Port number: 1

Home module number: No.1 OMP module.


INTERFACE:SUBSYSTEM=0,MODULE=1,UNIT=321,SUNIT=1,PORT=1;

3. Create the interface address of the SIPI. The command is ADDIP ADDRESS.

Table 5 describes the main parameters in the ADD IP ADDRESS command.

TABLE 5 ADD IP ADDRESS REAL INTERFACE

ParameterName


ADDRESS IP addressIt is a mandatory parameter.The Mc interface address of SIPIboard

MASK Subnet maskIt is a mandatory parameter. Thereal interface subnet address ofcorresponding interface board

BROADCAS-TIP

Broadcast IPaddress

It is an optional parameter,corresponding to the broadcastaddress of the real address of thecorresponding interface board.

Example: The configured parameters are as follows.

IP address: 192.168.1.11

Subnet mask: 255.255.255.248

Broadcast address: 255.255.255.255.


ADD IP ADDRESS:ADDRESS="192.168.1.11",MASK="255.255.255.248",BROADCASTIP="255.255.255.255";

4. Save the online configured data. Otherwise, these will losswhen the RPU is restarted.The command is SAVE ONLINEDATA;.



5. Exit the interface configuration mode. The command is EXIT;

END OF STEPS

Creating a Static Route


The interface address is created.

The BFD parameters are created when load-sharing networkingmode is adopted.


Context Static route is created when the service IP address of local sig-naling plane and PE interface address are not in the same net-work section. Under the active/standby working mode, a destina-tion address needs to be configured with a route only. Under theload-sharing working mode, a destination address usually needsto be configured with two routes.



SET:NEID=11;

2. Create the static route. The command is ADD IP ROUTE.

Table 6 describes the parameters in the ADD IP ROUTE com-mand.

TABLE 6 PARAMETERS IN THE ADD IP ROUTE COMMAND

ParameterName


NETPRE Net prefix

MASK Mask

It is a mandatory parameter.Type the network section of theopposite-end equipment serviceaddress according to the networkplanning. Its prefix should matchits mask

NEXTHOP Next hop IP

It is an optional parameter,indicating the router interfaceaddress (VRRP address). Type thegateway address to the oppositeend office

DISTANCE Distance It is an optional parameter with adefault of 1, ranging from 1 to 254

BFDDETECT Enable BFDDetect

It is an optional parameter. Ingeneral, select NO. The settingEnable BFD Detect is effectiveonly when IP address acts as thenext hop.



Example: Create the static route to the opposite end with thefollowing requirements.

Working mode: active/standby mode

Service address of the opposite equipment: 11.11.11.11

Mask: 255.255.255.0

Next hop IP: 10.0.74.1.

The command is as follows:

ADD IP ROUTE:NETPRE="11.11.11.11",MASK="255.255.255.0",NEXTHOP="10.0.74.1",DISTANCE=1,BFDDETECT=NO;

Example: Create two static routes to the opposite end with thefollowing requirements.

Working mode: load-sharing mode

Service address of the opposite equipment: 11.11.11.11

Mask: 255.255.255.0

Next hop IP: 10.0.74.1 and 10.0.74.2.

The command is as follows:



END OF STEPS

Adjacent Office and TopologyConfiguration

Overview

Introduction Adjacent office configuration means configuring the neighboringoffice of the local office. There are two association modes, directassociation and quasi-association.

If the adjacent office is regarded as a node in the whole networktopology when the local office is in the center, topological nodeconfiguration means adding the topological node of its adjacentoffice in the local office. The topological nodes configured on MSCSinclude MGW, RNC/BSC, and MSCS (Nc).



ConfigurationFlow Steps Operations Instructions Command

1 Creating an MGWadjacent office

Create the ba-sic information ofMGW adjacent of-fice.

ADD ADJOFC

2Creating an MGWvoice CODEC tem-plate

Create the encod-ing and decodingspeech type mod-ules supported byIM-MGW.

ADD CODECTPL

3 Creating a topol-ogy node

Create the topol-ogy relationshipbetween MGCFnode and IM-MGWnode.

ADD TOPO

4Creating inter-MGW bear mode(optional)

The inter-MGWbearer mode isconfigured whenthe Nb interfacesbetween severalIM-MGWs underthe same MGCFare connected.

ADD MGWBEARMOD

Creating an MGW Adjacent Office


The physical IP connection between the MSCS and the MGWis clear, which is implemented by the connection between theFE1 interfaces on the rear board of the SIPI boards of thesetwo NEs.

The signaling interworking data is planned and negotiated.

The basic configuration of the local office is completed.

The range of adjacent office number is configured in the re-source management.


Context Perform this procedure to configure the basic information of MGWadjacent office. On the MSCS, each MGW is configured with threeadjacent offices according to the SCTP Planning.



SET:NEID=11;

2. Create the MGW adjacent office. The command is ADD ADJOFC.

Table 7 describes the main parameters in the ADD ADJOFCcommand.



TABLE 7 PARAMETERS IN THE ADD ADJOFC COMMAND

ParameterName


ID Office ID

A mandatory parameter,indicating the identificationnumber of the adjacentoffice, and ranging from1 to 3000. In general,it is configured as theexchange ID of theadjacent office during theall-network planning

NAME User-defined aliasIt is a mandatoryparameter. Type acustomized name.

NET Network type

A mandatory parameter,indicating the networktype of the SPC used forconnecting the local officeto the adjacent officewhen the local office isconfigured with severalSPs. The default is thenetwork type of this SPwhen there is only one SPin the local office

OFCTYPE The type of adjacentoffice

It is a mandatoryparameter. Select MGWfor the MGW bearing H248signaling. Select SGW foranother two MGW offices.

SPCFMT SPC format Select TRIPLE_DEC.

SPCTYPE SPC type

DPC Destination SPC

It is a mandatoryparameter. Select itbased on the SPC typeof the adjacent officeaccording to the signalingpoint planning. In China,all the NEs adopt the 24-bitSPC except the BSC thatadopts the 14-bit SPC.

RC Area code

It is an optional parameter,indicating the local tollzone code of the adjacentoffice. This parameterhas impact on the areacode added by the callingnumber



ParameterName


ASSOTYPE

Association type,including:

AM_SURE (directconnection mode)

AM_QUASI (halfdirect connectionmode)

AM_NONE (noneconnection mode).

It is an optional parameter.Select AM_SURE

SPTYPESignaling point type,including SEP, STP,and STEP

It is an optional parameter.Select SEP (signalingend point) for the MGWbearing H248 signaling.Select STEP (signalingtransition / end point) foranother two MGW offices

SSF

Subservice function,including

INTERNATIONAL(Internationalsignaling pointcode)

INTERNATIONALSTANDBY(Internationalstandby signalingpoint code)

NATIONAL(National signalingpoint code)

NATIONALSTANDBY(National standbysignaling pointcode).

It is an optional parameter.

In general, NATIONALis selected at home. Forthe BSC adjacent office,NATIONAL STANDBY isselected.

TAG

Office Attribute,including:

ISNI (Has ISNIFunction)

TRANS (TranslateNode)

TEST (Need TestInfo:0X02/0X01)

It is an optional parameter

TEST Test flag

It is an optional parameter.It is used to set whetherthe MTP3 link activelyinitiates the link testafter entering the servicestatus. In most cases, thisparameter is selected.



ParameterName


BANDFLAG Broadband attribute

It is an optional parameterwith a default of NO. Itis used for SCCP to judgewhether to use the LUDTmessage.

The maximum length of abroadband link messageis 4,000, and that of anarrowband link messageis 255. Because the MTPlayer does not have thesegmentation function, theincorrect configuration ofthis parameter probablycauses the long packet tobe discarded.

Select this parameterwhen all the links betweentwo SPs are SIGTRAN orATM signaling links.

PRTCTYPE

Protocol Type,including:

CHINA (China)

ITU (InternationalTelecommunica-tions Union)

ANSI (AmericanNational StandardsInstitute)

It is an optional parameter.The CHINA and the ITUare used for the NO.7signaling networking ofthe ITU standard and theANSI is used for the NO.7signaling networking ofthe American standard.In general, select CHINAfor the domestic officeand select ITU for theinternational office

CLST Cluster ID

It is an optional parameterwithin 0~65535. Ingeneral, select the defaultvalue 65535. It is validwhen the protocol typeof the adjacent office isANSI. The signaling pointconnected to the signalingtransfer point belongs tothe corresponding cluster

INFO

Office Info, including:

CIC_PCM (CICstarts the loadsharing accordingto the PCM codemode)

BLOCK (Manualblock status)

EVEN_CIC (Theoffice controlsthe even CICwhen CIC resourcecontention occurs)

It is an optional parameterand the default value isCIC_PCM



ParameterName


CALLING(Callingtransform isallowed)

CALLED (Calledtransform isallowed)

MOD24_CIC (CICmode with 24mode)

TEST (Dynamictest)

RELATE-DOFC1 Related Office ID

It is an optional parameterranging from 0 to 3000

INFOEX

Office Extend Info,including:

SIGBRDCST(Support SignalingBroadcastMessage)

MTP (HongkongMTP Standard)

DUPU ( ScreenDUPU message)

SUA_REC_DT1(Receive SUAmessage andhandle it as DT1message)

SUA_SND_DT1(Send SUAmessage andhandle it as DT1message withoutSN.)

OPEN_TG_RES(Open outter trunkgroup resource)

It is an optional parameter

For example, create MGW adjacent office. The office ID is 101,the alias is MGW1, and the destination SPC is 1.31.2. For otherparameters, adopt the default value. The command is as fol-lows:

ADD ADJOFC:ID=101,NAME="MGW1",NET=3,OFCTYPE=MGW,SPCFMT=TRIPLE_DEC,SPCTYPE=14,DPC="1.31.2",RC="25",ASSOTYPE=AM_SURE,SPTYPE=SEP,SSF=NATIONAL STANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BANDFLAG=YES,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_PCM",RELATEDOFC1=0;

END OF STEPS



Creating an MGW Voice CODEC Template


The basic configuration of the local office is completed.

The range of the MGW voice CODEC template numbers is con-figured in the resource management configuration.


Context Perform this procedure to create the encoding and decodingspeech type modules supported by MGW. In general, MSCS isconfigured with a default common voice CODEC template.



SET:NEID=11;

2. Create the MGW voice CODEC template. The command is ADDCODECTPL.

Table 8 describes the main parameters in the ADD CODECTPLcommand.

TABLE 8 PARAMETERS IN THE ADD CODECTPL COMMAND

ParameterName


ID Templatenumber

It is a mandatory parameterfor defining an encoding anddecoding speech template,ranging from 1 to 255.

GRPIDThe groupnumber of thespeech coding.

It is a mandatory parameter forspecifying the OID format andencoding and decoding type list.Up to eight types can be definedin an encoding and decodingtemplate.

VALFG

Valid option,including YES(valid) and NO(invalid)

It is a mandatory parameter forsetting whether this encodingand decoding speech template isvalid. Select YES

OID OID

It is a mandatory parameter forspecify an Organization Identifier(OID).

It has the following parameters.

OID_NONE: No OID

OID_ITU_T: ITU_T

OID_ETSI: ETSI

OID_IETF: IETF



ParameterName


ITYPE ITU_T CODECtype.

It is an optional parameter. Ingeneral, ITUT_G711A_64 isselected.

ETYPE ETSI CODECtype

It is an optional parameter. Ingeneral, ETSI_UMTS_AMRand ETSI_UMTS_AMR_2 areselected.

ACTRATE ActivatedCODEC rate

It is an optional parameter. Ingeneral, the default value isselected

SUPRATE SupportedCODEC rate


OM ACS optimizedmode


Example: Configure an MGW encoding and decoding speechtemplate with the following requirements.

Template ID: 1

CODEC group number: 1

Valid option: YES

OID: ETSI

ETSI CODEC type: ETSI_UMTS_AMR2

Activated CODEC rate: 5.90 K and 6.70 K

Supported CODEC rate: 5.90 K and 6.70 K

ACS optimize mode: Yes.

ADD CODECTPL:ID=1,GRPID=GRPID1,VALFG=YES,OID=OID_ETSI,ETYPE=ETSI_UMTS_AMR_2,ACTRATE="Rate590"&"Rate670",SUPRATE="Rate590"&"Rate670",OM=YES;

END OF STEPS

Creating a Topology Node


The encoding and decoding speech template is configured.

The range of the topological node number is configured in theresource management.


Context Perform this procedure to configure the topology relationshipbetween MSCS node and MGW node. This command is used toconfigure the adjacent NE information, including equipment type,



bearer type and attributes, user plane version, encoding anddecoding template, and other information.

For Mc interface, only the adjacent office bearing H.248 protocolis configured as a topological node.



SET:NEID=11;

2. Create an MGW topology node. The command is ADD TOPO.

Table 9 describes the main parameters in the ADD TOPO com-mand.

TABLE 9 PARAMETERS IN THE ADD TOPO COMMAND

ParameterName


ID Topological nodeID

It is a mandatory parameter todefine ID of this node, rangingfrom 1 to 2,048.

It is recommended that the IDand office No. of a topologicalnode are consistent

OFCID Office ID

It is a mandatory parameterfor specifying the office ID ofthis topological node. Thisparameter must be defined bythe ADD ADJOFC commandfirst.

In this case, type the actualMGW office number

NAME Alias

It is a mandatory parameterfor naming this topologicalnode, with a length rangingfrom 1 to 50 characters.

CODECID CODEC identity

It is a mandatory parameterfor specify the CODECtemplate used by thistopological node. Thisparameter must be definedby the ADD CODECTPLcommand first.

ETYPE Equipment type

This parameter is used tospecify the NE type of thistopological node.

Select R4GW for an MGWnode

PROTTYPE Protocol type Select H.248 for Mc interface.



ParameterName


IPVER IP version of thenode

It is the IP protocol versionsupported between nodes.Select IPV4 or IPV6according to the actualconditions. Currently, IPV4 issupported.

ATTR Bearer attributes

This parameter is only validfor the node with the typeof R4GW (MGW). The bearertypes supported by MGWare BNCAAL1, BNCAAL2,BNCAAL1S, BNCIPRTP, andBNCTDM. MGW can supportone or more of these types ofbearers.

In general, select BNCAAL2,BNCIPRTP, and BNCTDM

UPVERUser planeprotocol versionof RNC or MGW

This parameter is used to setthe user plane version of thisnode.

In general, select V2

ATTR2

Extendedattributes (tunnelmode), including:

NOTUNL(None tunnelmode)

RTUNL(Rapid tunnelmode)

DTUNL(Delay tunnelmode)

This parameter is used to setwhich tunnel mode is adoptedfor bearer establishment whenthis node supports the IP/RTPbearer. The default value isNOTUNL (None tunnel mode).

In general, select DTUNL(Delay tunnel mode) for anMGW topological node.

TRFMOD

Signaling transfermode, including:

MCINTF (Mcinterface signaltransfer mode)

This parameter is used to setwhich mode is used by thetopology for reporting whenit detects CNG or CED faxsignals.

The default value is MCINTF

UPERRCTRL

Error SDUcontrol, includingoptions:

YES: The userplane entity im-plements errorinspection, andsets the FQC bitposition accord-ing to the result.It will transmitall frames in-cludes the errorframes to theuser plane layer.

This parameter regulates thehandling method of the userplane for error frames. It isonly valid for MGW-type andRNC-type topological node.The default value is YES



ParameterName


During a call, theerror packet con-trol parameterdelerrsdu=Yes,which is deliveredby the terminalestablished byMGW on the Mcinterface. Theerror packet con-trol parameterdeliveryOfErro-neousSDU is YES,NA, NA duringRAB assignment.

NO: The userplane entity im-plements theerror inspection.It will directlydiscard the errorframe. Duringa call, the er-ror packet con-trol parameterdelerrsdu=No,which is deliveredby the terminalestablished byMGW on the Mcinterface. Theerror packet con-trol parameterdeliveryOfErro-neousSDU is NO,NA, NA duringRAB assignment.

INVALIDTION:The user planeentity does notimplement theerror inspection.During a call, theerror packet con-trol parameterdelerrsdu=NA,which is deliveredby the terminalestablished byMGW on the Mcinterface. Theerror packet con-trol parameterdeliveryOfErro-neousSDU is NA,NA, NA duringRAB assignment.



ParameterName


DTMFTC

Tandem officesend DTMFuse TC mode,including twooptions:

NO

YES

This parameter is used to setwhether the tandem officeuses the TC resources duringDTMF number delivery.

The default value is NO

MGWCONMGW congestionreportingcapability

It contains the followingoptions.

SMGWCON (StandardMGW congestion event)

CMGWCON (Custom MGWcongestion event).

The default value isSMGWCON.

Example: Create a topology node with the following require-ments.

MGW office ID: 101

Equipment type: R4 gateway

Protocol type: H248

Supported user plane protocol version: V2

CODEC ID: 1.

The specific command is as follows.

ADD TOPO:ID=101,OFCID=101,NAME="MGW101",CODECID=1,ETYPE=R4GW,PROTTYPE=H248,IPVER=IPV4,ATTR="BNCAAL2"&"BNCIPRTP"&"BNCTDM",UPVER="V2",ATTR2=DTUNL,TRFMOD=MCINTF,UPERRCTRL=YES,DTMFTC=NO,MGWCON=SMGWCON,AUTOFAX=YES,OOBTC=NO,BCUID=0,SENDCAP=NO,G711TRAN=NO,BICCDTMF=TRANSPARENT,IPBCP2833=BYMGW,BICCDTMPPER=0,AOIPPRO=PRIVATE;

END OF STEPS

Creating an Inter-MGW Bearer Mode


The MGW topological node is created.


Context The inter-MGW bearer mode is configured when the Nb interfacesbetween several MGWs under the same MSCS are connected.





SET:NEID=11;

2. Create the inter-MGW bearer mode. The command is ADDMGWBEARMOD.

Table 10 describes the main parameters in the ADD MGWBEARMOD command.

TABLE 10 PARAMETERS IN THE ADD MGWBEARMOD COMMAND

ParameterName


MGWPAIR MGW node pairType the gateway node IDconfigured in the topologicalnode configuration.

ATTR

Bearer attributebetween MGWs,the optionsinclude:

AAL1(supportbncAAL1)

AAL2(supportbncAAL2)

AAL1S (supportnbcAAL1Struct)

RTP (supportbncIPRTP)

TDM(supportbncTDM)

The parameter specifies thebearer attribute betweenMGWs. Select RTP or TDMaccording to the type of Nbinterface bearer.

CTYPE

Type of tone codebetween MGWs,the optionsincluding:

GENERAL

AMRONLY

AMRONLY represents the AMRencoding and decoding modeis used only. When G.711 andother encoding and decodingmodes are allowed, selectGENERAL

NAME AliasAdjacent office alias ofgateway 1-Adjacent office aliasof gateway 21

AAL1 AAL1 bearer typerate(%)

The parameter specifies therate (%) of the AAL1 bearerbetween two gateways

AAL2 AAL2 bearer typerate(%)

The parameter specifies therate (%) of the AAL2 bearerbetween two gateways

AAL1SAAL1STRUCTbearer typerate(%)

The parameter specifies therate (%) of the AAL1 STRUCTbearer between two gateways

RTP IPRTP bearer typerate(%)

The parameter specifies therate (%) of the IPRTP bearerbetween two gateways



ParameterName


TDM TDM bearer typerate(%)

The parameter specifies therate (%) of the TDM bearerbetween two gateways

DIRECT

Top-priority directlink topology, theoptions include:

NO

YES

The default is NO

UPMODE

User plane modefor multi-gatewayIP bearer, theoptions include:

TRANSPAR-ENT(transparentmode)

SUPPORT(supportmode)

The default is TRANSPARENT

IPNET Public IP networkdomain index

The parameter is used to setthe public IP network domainindex (ADD IPDOMAIN)

G711TRAN

G711 that isforced to usethe transparentmode. Optionsinclude:

NO

YES

The default is NO

Example: Configure the bearer mode between two MGWs withthe following requirements.

MGW 1 node ID: 101

MGW 2 node ID: 201

Bearer mode: RTP

Type of tone code between MGWS: AMRONLY

Supported version: V2

Alias: MGW101-MGW201

Other parameters: default value.


ADD MGWBEARMOD:MGWPAIR="101"-"201",ATTR="RTP",NAME="MGW101-MGW201",CTYPE=AMRONLY,AAL1=0,AAL2=0,AAL1S=0,RTP=100,TDM=0,DIRECT=NO,UPMODE=TRANSPARENT,G711TRAN=NO;

END OF STEPS



SIGTRAN Configuration

Overview

Description SINGTRAN-related configuration is required not only by the Mcinterface between MSCS and MGW, but also by the Nc interfacebetween MSCS and other direct-associated office over IP.

When the SCTP bears the M3UA protocol, configuring SCTP, ASP,AS, M3UA static route and SIO-locating-AS is required.

When the SCTP bears H248 protocol, configuring SCTP is requiredonly. In general, this mode is not used.

Compared with the MTP data configuration of the traditional No.7signaling, the SCTP association configuration and the ASP config-uration of the M3UA are similar to the link logic and bearer infor-mation configurations in the MTP configuration, and the AS config-uration of the M3UA is similar to the link set configuration in theMTP configuration. The configuration of SIO location AS is similarto the signaling office direction and route configuration in the MTPconfiguration. The only difference between them is that one pieceof SIO location AS configuration record is configured the IP routeto a subscriber of an office.



ConfigurationFlow

Figure 2 shows the flow of SIGTRAN configuration.

FIGURE 2 SIGTRAN CONFIGURATION FLOW

According to the rules regulated in SCTP Planning, perform theconfiguration by following the procedure specified below.

Steps Operations Instructions Command

1 Creating SCTP Create an associationbetween two offices ADD SCTPCONN

2 Creating ASP

Create the one-to-one relationshipbetween the ASP andthe association. ASPis one of instances ofAS.

ADD ASP

3 Creating ASCreate the tag, usertype, subsystem typeof AS

ADD AS




4 Creating M3UAstatic route

Create the mappingrelationship betweenthe M3UA static routeand the AS.

ADD M3UART

5Creatingthe SIO-Locating-AS

Locate one service toa routing table thatis maintained by theASP under the AS.

ADD SIOLOCAS

Creating an SCTP


The physical configuration of the SMP module is completed.

The SCTP flag is configured in the resource management.


Context The SCTP connection is called as association, which is of one-to-one correspondence with ASP. It can be equivalent to the com-munication link used by the AS. An SMP can support up to 128associations. When multiple BCTC shelves are configured, associ-ations must share the load in each shelf.



SET:NEID=11;

2. Create the SCTP connection. The command is ADD SCTPCONN.

Table 11 describes the chief parameters of the ADD SCTPCONN command.

TABLE 11 PARAMETERS IN THE ADD SCTPCONN COMMAND

ParameterName


MODULE Module No.

It is a mandatoryparameter, indicatingthe number of thesignaling modulehomed by this SCTPassociation. Select theSMP module number.Each SMP can supportup to 128 associations.The associations underthe same AS arerequired sharing loadon SMP modules asmore as possible.



ParameterName


OFCID SCTP opposite officeID

It is a mandatoryparameter, designatingthe office No. ofthe direct-associatedassociation. Typethe MGW adjacentoffice No. specifiedin the adjacent officeconfiguration.

PROT

Bearer protocoltypes, including

M2UA

M2PA

M3UA

SUA

H248

BICC

IUA

DHCTRL

SIP

DIM

V5UA

H245

It is a mandatoryparameter. It is used toidentify the upper-layerprotocol type borne bythe SCTP association.In general, M3UA isselected. M2UA isselected when MGWtransfers the signalingwith the M2UA mode.

ROLE

SCTP applicationattributes. Optionsinclude:

SVR: SCTP is usedas server

CLT: SCTP is used asclient

It is a mandatoryparameter. For Mcinterface, MSCS isconfigured as CLT, andMGW is configuredas SVR. For Ncinterface, this shouldbe negotiated by bothsides. For example, thesmall signaling pointserves as CLT, andthe big signaling pointserves as SVR

LOCADDR Local IP address

It is a mandatoryparameter. Itdesignates the serviceaddress of local endof this association,with a format ofLocal IP addresstype-VPN of localIP address-Local IPaddress

Local IP address type:IPv4 and IPv6

VPN of local IP address:Rang from 0 to 65535



ParameterName


Local IP address:the format isxxx.yyy.zzz.mmm

LOCPORT Local port number

It is a mandatoryparameter. It is thelocal SCTP port numberof the association,ranging from 1 to65535.

REMADDR Opposite IP address

It is a mandatoryparameter. Itdesignates the serviceaddress of remote endof this association,with a format ofRemote IP addresstype-VPN of remoteIP address-RemoteIP address

Remote IP addresstype: IPv4 and IPv6;

VPN of remote IPaddress: Rang from 0to 65535

Remote IP address:the format isxxx.yyy.zzz.mmm

REMPORT Opposite portnumber

It is a mandatoryparameter. It isthe opposite SCTPport number of theassociation, rangingfrom 1 to 65535.

NAME Alias

It is a mandatoryparameter with alength ranging from 1to 50 characters.

ID SCTP ID

It is an optionalparameter. It is theglobal serial number ofthe SCTP association,ranging from 1 to 2048.Configure it accordingto the associationplanning.

Example: Create the SCTP connection for the Mc interface withthe following requirements.

MGW office ID: 101

Bearer protocol: M3UA

Application attribute: CLT

SCTP signaling processing module number: 3



Local port number: 2001

Opposite port number: 2001

Local IP address: 192.168.1.11

Opposite IP address: 192.168.1.31

SCTP association ID: 1



ADD SCTPCONN:MODULE=3,OFCID=101,PROT=M3UA,ROLE=CLT,LOCADDR="IPv4"-"0"-"192.168.1.11",LOCPORT=2001,REMADDR="IPv4"-"0"-"192.168.1.31",REMPORT=2001,NAME="MGW101-1",ID=1,INSTRM=16,OUTSTRM=16,MAXRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=100,HB=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYACK=20,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,BREAKTIME=0,PDTHRESH=0,MINCWND=0,PLTIMER=10,MPPLTHRD=2,DPLEN=MTU,CB=200;

END OF STEPS

Creating an ASP


The SCTP association information configuration is completed.

The range of the ASP configuration identification is created inthe resource management configuration.


Context Perform this procedure to define the one-to-one relationship be-tween the ASP and the association. ASP is one of instances of AS.



SET:NEID=11;

2. Create the ASP. The command is ADD ASP.

Table 12 describes the main parameters in the ADD ASP com-mand.



TABLE 12 PARAMETERS IN THE ADD ASP COMMAND

ParameterName


ASSOCID SCTP ID

It is a mandatory parameter,ranging from 1 to 2048

Type the association IDconfigured in the SCTPconnection configuration.

NAME Alias

It is a mandatory parameter,with a lengthen ranging from1 to 50 characters. It maybe named with a format ofAdjacent office alias-SCTPnumber.

ID ASP ID

It is an optional parameter,ranging from 1 to 2048.

It is recommended to beconsistent with ASSOCID.

ISLOOP ASP self-loop ID

It is an optional parameter. It isused to set whether the ASP isself-looped.

Select the default value NO

ISLOCK ASP blocking flag

It is an optional parameter. It isused set whether the ASP is inblocking state.

Blocking is used formanagement. Select thedefault value NO

Example: Create the ASP between MSCS and MGW for Mc in-terface with the following requirements.

MGW office ID: 101

SCTP association ID: 1

ASP configuration ID: 1

User alias: MGW101-1.


ADD ASP:ASSOCID=1,NAME="MGW101-1",ID=1,ISLOOP=NO,ISLOCK=NO;

END OF STEPS

Creating an AS


The ASP configuration is finished.




Context The AS provides the transmission channels for upper-layer ser-vices. For example, H248 and TUP/UP are different services. Theyuse different AS for transmission. The AS can use one or moreassociations for communication.



SET:NEID=11;

2. Create the AS. The command is ADD AS.

Table 13 describes the main parameters in the ADD AS com-mand.

TABLE 13 PARAMETERS IN THE ADD AS COMMAND

ParameterName


PROTSupportedadaptation layerprotocols

It indicates the protocoltype of a bearer. In general,M3UA is selected accordingto the networking planning.It is configured as M2UAwhen MGW transfers thesignaling with M2UA mode.

ASP ASP IDIt is associated with theASP ID configured in theASP configuration.

NAME AliasIt is a mandatoryparameter. The aliascustomized by the user.

ID AS ID

It is an optionalparameter. It is the uniqueidentification of the AS. Ingeneral, it is the same asthat of the ASP for easymemory. The parameterranges from 1 to 640

EXISTCTX Whether the routingcontext ID exists

CTXID Routing context ID

It is an optional parameter.The routing context isunique in the network.This parameter mustbe consistent with theAS configuration of theopposite-end. Its defaultvalue is NO



ParameterName


ASTAG

Usage tag. Optionsinclude:

SGP

ASP

SRV (IPSP server)

CLT (IPSP client)

It is an optional parameter.

For Mc interface, MSCSgenerally serves asIPSP_Client, and MGWserves as IPSP_Server.When MGW acts as a SGW,the AS at the MSCS sideserves as ASP, and the ASat the SGW side serves asSGP.

For Nc interface, this shouldbe negotiated by bothsides. For example, thesmall signaling point servesas IPSP_Client, and the bigsignaling point serves asIPSP_Server.

ASUP

User typessupported by AS.Options include TUP,ISUP, BICC, H.248,ALCAPSCCP, PCA,NNSF and ALL

It is an optional parameter.It defines the upper-layeruser types supported bythe AS. Currently, there areeight types of users.

User type is not configuredwhen MGW transfers thesignaling with the M2UAmode

ASMD Service modessupported

It is an optional parameter.The supported servicemodes include:

OVERRIDE(Over-ridemode)

LOAD (Load sharemode).

In the over-ride mode,only one ASP is in theactivated statue. In thiscase, only one ASP needsbe configured. In theload sharing mode, NASPs should be configuredin the activated workingstatue, and K ASPs shouldbe configured in thedeactivated standby statue.

The value of N+K is notmore than the number ofASPs actually configured



ParameterName


SSN

Types of subsystem.Options includeNO_SSN (subsystemSSN excluded(null)), SCCP, REV2(standby), ISUP,OMAP, MAP, HLR,VLR, MSC, EIR, AUC,REV11(standby),INAP, USSD, VLRA,SGSN_BSCAP,RANAP, RNSAP,GMLC_MAP, CAP,GSMSCF_MAP,SIWF_MAP, SGSN_MAP, GGSN_MAP,IP (intelligentperipherals),SMC, SSP_SCP,BSC_BSSAP_LE,MSC_BSSAP_LE,SMLC_BSSAP_LE,BSS_O_M_A ,BSSAP_A andRVE255.

Types of subsystemsupported by applicationserver (AS).

NVAL The N value in loadsharing mode

The parameter ranges from0 to 16.

The N+K should be equal tothe number of ASP underAS.

The N value indicates thatAS puts into use if N ASPsput into use.

Example: Configure the AS between MSCS and MGW for Mcinterface with the following requirements.

MGW office ID: 101

Supported adaptation layer protocol: M3UA

AS configuration ID: 1

Supported user type: H248

ASP ID: 1

Client: MSCS

Alias: H248


ADD AS:PROT=M3UA,ASPID="1",NAME="H248",ID=1,EXISTCTX=NO,ASTAG=SGP,ASUP="H248",ASMD=LOAD,NVAL=1,KVAL=0;

END OF STEPS



Creating an M3UA Static Route


The AS configuration is finished.

The range of the M3UA static route identification is configuredin the resource management configuration.


Context Perform this procedure to configure the mapping relationship be-tween the M3UA static route and the AS. An M3UA static routecan be used by up to 64 SIO-locating-ASs. Otherwise, configuringmore M3UA static routes is required.



SET:NEID=11;

2. Create the M3UA static route. The command is ADDM3UART.

Table 14 describes the main parameters in the ADD M3UARTcommand.

TABLE 14 PARAMETERS IN THE ADD M3UART COMMAND

ParameterName


ID ID of M3UAstatic route

It is an optional parameter,indicating the serial number of theM3UA static route ID, ranging from1 to 640. In general, it is the sameas the AS ID.

ASID AS IDIt is a mandatory parameter,corresponding to the AS IDspecified in the ADD AS command.

MODE

Alignmentmode ofroutes.Optionsinclude

BYTURNS

LOCAL

NATURE

Nature: routes are directly sortedaccording by the ASP marshallingsequence in the routing table.

Local: It is unnecessary to realizethe algorithm in the background.The background just needs to makethe alignment according to theNature option.

BYTURNS: in the routing table,the routes at the odd-bit positionare sorted by the serial number ofthe activated ASP, and the routesat the even-bit position are sortedinversely by the serial number ofthe activated ASP

The default is BYTURNS.

NAME AliasIt is a mandatory parameter definedby a user, with a length rangingfrom 1 to 50 characters.



Example: Create an M3UA static route for Mc interface withthe following requirements.

MGW office ID: 101

M3UA static route ID: 1

AS ID: 1

User alias: MGW101.


ADD M3UART:ID=1,ASID=1,MODE=BYTURNS,NAME="MGW101";

END OF STEPS

Creating the SIO-Locating-AS


The M3UA static route configuration is completed.

The range of the SIO-locating-AS configuration ID is configuredin the resource management configuration.


Context The configuration of SIO-locating-AS is used to locate one serviceto a routing table that is maintained by the ASP under the AS. OnMSCS, H248 protocol is generally configured between MSCS andMGW, and ISUP, TUP, and SCCP protocols are configured betweenMSCS and other adjacent offices that are switched by MGW.

A routing key describes a set of No.7 signaling parameters andparameter values. The corresponded AS is selected according tothe message attributes, thus to select a route for the message.

The message attributes include DPC+NET+OPC+SIO. The DPCrepresents the destination SPC, the NET represents the networktype, OPC represents the original SPC, and the SIO representsthe service information octet.



SET:NEID=11;

2. Create the SIO-locating-AS. The command is ADD SIOLOCAS.

Table 15 describes the main parameters in the ADD SIOLOCAS command.



TABLE 15 PARAMETERS IN THE ADD SIOLOCAS COMMAND

ParameterName


ID SIO-location-AS ID

It is an optional parameter,indicating the serial number ofSIO-locating-AS, ranging from 1 to4096. In general, it is the same asthe AS ID.

NAME Alias It is a mandatory parameter, whichis the alias customized by the user.

SIO

Serviceindication.Options include

NULL

TUP

ISUP

BICC

H.248

ALCAP

SCCP

PCA

NNSF

It is a mandatory parameter,indicating the subscriber typebelonged by the transmittedmessage. Different user types canbe located to the same AS underthe precondition that the MS mustsupport these user types

Select H.248 for Mc interface,BICC for Nc interface, SCCP forthe RNC or BSC office transferredthrough MGW, and TUP or ISUPfor the 2G MSC/PSTN officetransferred through MGW.

OFCIDDestinationadjacent officeID

It is a mandatory parameter,indicating the adjacent office IDcorresponded by the destinationsignaling point of the M3UA.It needs to associate with theadjacent office ID in the adjacentoffice configuration.

OPOFCIDOriginaladjacent officeID

It is the adjacent office IDcorresponding to the M3UAoriginating signaling point. If0 (indicating the local office)is selected, it indicates thatthe message is sent from thelocal office, and the routingcontext is routed according toDPC+NET+OPC+SIO. If 65535(invalid) is selected, it indicatesthat the OPC field is invalid, andthe routing context is routedaccording to DPC+NET+SIO

PCM PCM systemnumber

It is an optional parameter. Itranges from 0 to 65535, with adefault of 65535 (invalid).



ParameterName


RT1 ID 1 of M3UAstatic route

RT2 ID 2 of M3UAstatic route

It corresponds to the IDspecified in the M3UA staticroute configuration. RT1 is amandatory parameter. In general,RT1 is required. When theoptimum route mode is adopted,RT1 is set as an active route, andRT2 is set as a standby route.

Example: Create SIO-locating-AS between MSCS and MGWwith the following requirements.

MGW office ID: 101

Destination adjacent office ID: 101

Service indication: H.248

M3UA static route ID: 1.


ADD SIOLOCAS:ID=1,NAME="MGW-H248",SIO=H248,OFCID=101,OPOFCID=65535,PCM=65535,RT1=1,RT2=0;

END OF STEPS

H.248 Configuration

Overview

Description H.248 protocol is only used on Mc interface. It provides the fol-lowing functions.

Under the control of MGC, it can establish, modify and releasethe media channel in the MG, and can control the attributes ofbearer and user plane.

It reports the events in the MG to the MGC.

It maintains the office and terminal status between MGC andMG.



ConfigurationFlow

Figure 3 shows the configuration flow of H.248 protocol.

FIGURE 3 CONFIGURATION FLOW

Flow Description The H.248 configuration procedures are as follows:


1 Creating MGCstatic data

Cofigure the datarelated to theMGCF and H.248.

ADD MGCSCFG

2Creating anMGW static datatemplate

Create thetemplate usedby the MGWstatic dataconfiguration.

ADD MGSTPL

3 Creating MGWstatic data

Create the staticdata for eachIM-MGW underthe MGCF.

ADD MGSCFG




4 Creating a TIDanalyzer

The TID analysisconfiguration isnecessary forthe H.248 serverto perform thecharacter stringconversion ofthe CIC. Nomallyadopt the defaultconfiguration.

ADD TIDANL

5 Creating a TIDanalysis entry

Create aTID analyzerentrance.Nomally adoptthe defaultconfiguration.

ADD TIDENTR

Creating MGC Static Data


The data configuration of the local office is completed.


Context Perform this procedure to set the data related to the MSCS andH.248.



SET:NEID=11;

2. Create the MGC static data. The command is ADD MGCSCFG.

Table 16 describes the main parameters in the ADD MGCSCFGcommand.

TABLE 16 PARAMETERS IN THE ADD MGCSCFG COMMAND

ParameterName


MEGACO MEGACO versionnumber

It is an optional parameter.Select the supported MEGACOversion number, which must beconsistent with that negotiatedwith the MGW. The default valueis 1

ACTTMService activationdetectiontimer(s)

It is an optional parameter,ranging from 0 to 3600, with adefault of 600

ACTCHK Service activationdetection switchIt is an optional parameter,being activated by default.



ParameterName


WAITTMMGW answerwaiting timer(ms)


PTRYNUM PEND retrytimes(t)


PTRYTM PEND retry time(ms)


CTXLIVETM Context livetime(s)


NAME Alias

It is an optional parameter,ranging from 0 to 50 characters.It may be the same as the officename

Example: To create the MGC static data of an MSCS office withall the parameters adopting default value, the specific com-mand is as follows.

ADD MGCSCFG:MEGACO=1,ACTTM=600,ACTCHK=ON,WAITTM=7800,PTRYNUM=5,PTRYTM=4000,CTXLIVETM=1200,MGACTTM=600;

END OF STEPS

Creating an MGW Static Data Template




Context Perform this procedure to set the template used by the MGW staticdata configuration.



SET:NEID=11;

2. Create an MGW static data template. The command is ADDMGSTPL.

Table 17 describes the main parameters in the ADD MGSTPLcommand.



TABLE 17 PARAMETERS IN THE ADD MGSTPL COMMAND

Parame-ter Name


NAME Alias

This is a mandatory parameterwith a length ranging from1 to 50 characters. It canbe consistent with the officename.

ID Static data templatenumberThe number of a template,ranging from 1 to 255

MEGACO MEGACO versionnumber

This parameter must beconsistent with that negotiatedwith the MGW.

ACTCHK Gateway activationdetection switchIt is configured as ON bydefault

PRTTM Transient protectiontimer (s)It ranges from 1 to 180. Typethe default value 10

PRT Transient protectionswitchIt is configured as ON bydefault.

PENDTM Interval of PENDmessages (ms)It ranges from 0 to 3600, witha default of 200

LNGTM Maximum existencetime (ms)It ranges from 0 to 65535,with a default of 15000

RTRNTM Retransmissiontimer (ms)It ranges from 0 to 65535,with a default of 3800

MTRNNUM Maximumtransmission timesIt ranges from 0 to 15, with adefault of 1

TRNMD Retransmissionmode

FIXED: Duration un-changeable

UNFIXED: Durationchangeable

CTYPE H.248 protocolcoding mode

It must be consistent with thatnegotiated with the MGW dataconfiguration

Example: Create an MGW static data template with the follow-ing requirements.

Template ID: 1

User name: MGW101



ADD MGSTPL:NAME="MGW101",ID=1,MEGACO=1,ACTCHK=ON,PRTTM=10,PRT=ON,PENDTM=200,LNGTM=1500



0,RTRNTM=3800,MTRNNUM=1,TRNMD=UNFIXED,CTYPE=TEXT;

END OF STEPS

Creating MGW Static Data


The MGW topological node is configured.

The MGW static data template is configured.

The MSCS voice batch processing is finished.


Context Perform this procedure to configure the static data for each MGWunder the MSCS.



SET:NEID=11;

2. Create MGW static data. The command is ADD MGSCFG.

Table 18 describes the main parameters in the ADD MGSCFGcommand.

TABLE 18 PARAMETERS IN THE ADD MGSCFG COMMAND

Parame-ter Name


ID Gatewaynumber

It is a mandatory parameter forconfiguring the node number ofthis gateway, ranging from 1 to2048. It is associated with the nodeID specified by the ADD TOPOcommand.

TPLIDStatic datatemplatenumber

It is a mandatory parameterassociated with the templatenumber configured on the MGWstatic data template configuration.

TONEID Service tonetemplate ID

It is an optional parameter rangingfrom 0 to 65535. It uses thetemplate ID specified in the BADDSTONE command.

LANGIDLanguagedescriptiontemplate ID

It is an optional parameter, rangingfrom 0 to 65535. It uses thetemplate ID specified in the BADDSTONE command.



Parame-ter Name


NAME AliasIt is a mandatory parameter,ranging from 0 to 50 characters. Itmay be the same as the office name

BKMGC Backup MGCinformationIt is an optional parameter, with adefault of NULL

PKGLOSTThreshold ofpackage lossrate (0.01%)

It is an optional parameter, rangingfrom 0 to 10000, with a default of10

JITThresholdof networkjittering (ms)


DELAYThreshold ofnetwork delay(ms)


MGW MGW tandem

It is an optional parameter forsetting whether this MGW is usedfor the tandem function. Type thedefault value NO

Example: Create static data for an MGW with the followingrequirements.

MGW office ID: 101

Static configuration template ID: 1

Alias: MGW101.


ADD MGSCFG:ID=101,NAME="MGW101",TPLID=1,TONEID=1,LANGID=1,PKGLOST=10,JIT=50,DELAY=200,MGW=NO;

END OF STEPS

Creating a TID Analyzer




Context The TID analysis configuration is necessary for the H.248 serverto perform the character string conversion of the CIC. The H.248server converts the CIC on the server to the corresponding char-acter string according to the mode configured by the TID analysis.Then it sends this character string to the gateway's H.248 for an-alyzing and operating the corresponded CIC. Since the form of theterminals used by the Mc interface is relatively fixed currently, youmay adopt the default configuration.





SET:NEID=11;

2. Create the TID analyzer. The command is ADD TIDANL.

Table 19 describes the main parameters in the ADD TIDANLcommand.

TABLE 19 PARAMETERS IN THE ADD TIDANL COMMAND

Parame-ter Name


NAME User alias

It is a mandatory parameter,ranging from 1 to 50characters. It may be thesame as the office name.

PREV TID analyzer index

It is an optional parameter.It is the global number ofthe current analyzer for TIDanalyzer entry to use, rangingfrom 1 to 255.

TIDPFX TID prefix It is an optional parameter witha default of TDM

TAG

Analysis result flag.Options includeUSER, TRUNK, RTP,ATM, ROOT andPCM+IDX.

It is an optional parameter,with a default of TRUNK (trunktype).

Example: TDM_5/1 is atrunk terminal form. TDM isthe TID prefix, _ is the PCMseparation mark, 5 is the PCMnumber, "/ is the IDX (timeslot index) is the separationmark, and 1 is the time slotnumber

PCMSPR PCM flag It is an optional parameter,with a default of .

IDXSPR IDX flag It is an optional parameter,with a default of /.

PCMPOS1 PCM start location

It is an optional parameter,ranging from 0 to 255, with adefault of 1, indicating that thePCM number starts from thefirst digit of the PCM flag.

PCMPOS2 PCM end location

It is an optional parameter,ranging from 0 to 255, with adefault of 0. Since there is aPCM flag, the End Location ismeaningless.

IDXPOS1 IDX start location It is an optional parameter,ranging from 0 to 255, with a



Parame-ter Name


default of 1, indicating that thetime slot number starts fromthe first digit of the IDX flag.

IDXPOS2 IDX end location

It is an optional parameter,ranging from 0 to 255, with adefault of 0. Since there is anIDX flag, the End Location ismeaningless.

Example: Create a TID analyzer with the following require-ments.

MGW office ID: 101

TID index: 1

Alias: MGW101


The command is:

ADD TIDANL:NAME="MGW101",PREV=1,TIDPFX="TDM",TAG=TRUNK,PCMSPR="_",IDXSPR="/",PCMPOS1=1,PCMPOS2=0,IDXPOS1=1,IDXPOS2=0;

END OF STEPS

Creating a TID Analyzer Entry


The MGW topological node is configured.

The TID analyzer configuration is completed.


Context Perform this procedure to configure a TID analyzer entry.



SET:NEID=11;

2. Create a TID analyzer entry. The command is ADD TIDENTR.

Table 20 describes the main parameters in the ADD TIDENTRcommand.



TABLE 20 PARAMETERS IN THE ADD TIDENTR COMMAND

ParameterName


ND GatewayIt is a mandatory parameter. It is thenode ID allocated by the topologicalnode configuration.

TIDENTID TID analyzerindex

It is a mandatory parameterassociating the TID analyzer IDspecified in the TID analyzerconfiguration.

TIDTPLID TID templatenumber

By default, the system alreadycreates a TID template whose ID is1. You may query it with the SHOWTIDTPL command.

NAME User Alias

It is a mandatory parameter witha length ranging from 0 to 50characters. It may be the same asthe office name.

Example: Create a TID analyzer entry with the following re-quirements.

MGW office ID: 101

TID analyzer index: 1

TID template ID: 1

Alias: MGW101.


ADD TIDENTR:ND=101,TIDENTID=1,TIDTPLID=1,NAME="MGW101";

END OF STEPS

HLR Data Configuration

Overview

TypicalNetworking

When ZXWN CS is interconnected with the HLR, the HLR is usuallyconnected to the MSCS in the TDM mode in the existing network.Figure 4 shows the typical networking between ZXWN CS and theHLR.



FIGURE 4 TYPICAL NETWORKING BETWEEN THE ZXWN CS AND THE HLR

Data Collection Before data configuration, it is supposed to complete collectingand negotiating the related data from the MSCS to the HLR office.Table 21 lists the data to be collected. The parameter values arejust examples. Input these parameters according to the actualcondition during the practical data construction procedure.

TABLE 21 MSCS-HLR INTERCONNECTION DATA COLLECTION

Parameter Items Parameter Values

ZXWN MSCS signaling point code (24-bit) 3.11.1

HLR signaling point code (24-bit) 3.1.1

HLR number 8613907551

Signaling point code type 24-bit signaling point code

SP type SEP

Association type Direct connect

Signaling link code 0

Signaling E1 number E1 9

Start timeslot number of E1 16TS

Quantity of timeslots 1

Data Configura-tion Flow

Table 22 describes the data configuration flow of the HLR adjacentoffice.



TABLE 22 DATA FOR INTERCONNECTION WITH THE HLR

Steps Operations Related Command

1 Creating a HLR AdjacentOffice ADD ADJOFC

2 Creating a Signaling Link Set ADD N7LKS

3 Creating an SPB-accessedSignaling Link ADD N7LNKE1

4 Creating a Signaling Route ADD N7ROUTE

5 Creating a Sig

SJ-20100211152857-010-ZXWN MSCS (V3.09.21) MSC Server Common Configuration Operation Guide

Documents

Transcript of SJ-20100211152857-010-ZXWN MSCS (V3.09.21) MSC Server Common Configuration Operation Guide