Download SJ-20100211152857-007-ZXWN MSCS (V3.09.21) MSC Server Data Configuration Guide(MGCF)...
ZXWN MSCS MSC Server
Data Configuration Guide(MGCF) Version 3.09.21
ZTE CORPORATION NO. 55, Hi-tech Road South, ShenZhen, P.R.China Postcode: 518057 Tel: (86) 755 26771900 Fax: (86) 755 26770801 URL: http://ensupport.zte.com.cn E-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 of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION 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 CORPORATION or of their respective owners. This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the information contained herein. ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject matter 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-007
Contents
About This Manual............................................. I Declaration of RoHS Compliance ....................... I Data Configuration Overview.............................1 MGCF Introduction.......................................................... 1 Overall Flow of MGCF Data Configuration ........................... 2 Basic Operations of the OMM System ................................ 4 Logging in the OMM Client ........................................... 4 Entering the MML Terminal........................................... 7 Operations on the MML Terminal ................................... 8 Synchronizing Data....................................................10
Local Office Data Configuration ....................... 13 Overview......................................................................14 Local Exchange Configuration ..........................................15 Overview..................................................................15 Creating an Exchange ................................................15 Setting Province and City Information of the Bureau .............................................................17 Physical Configuration ....................................................18 Overview..................................................................18 Creating a Rack.........................................................19 Creating a Shelf ........................................................20 Creating the UIM Unit ................................................21 Creating a Module .....................................................23 Creating other Units...................................................25 Creating a CHUB Unit ........................................26 Creating a CLKG Unit.........................................27 Creating an SIPI Unit.........................................29 Creating a USI Unit ...........................................30 Creating an SPB Unit .........................................32 Creating Background Server Node ...............................33 Capacity Configuration ...................................................34
Confidential and Proprietary Information of ZTE CORPORATION
I
ZXWN MSCS Data Configuration Guide(MGCF)
Overview..................................................................34 Configuring the MGCF Office Capacity...........................34 Configuring Service Data Area .....................................37 Version Loading.............................................................39 Overview..................................................................40 Creating Version File Directory ....................................41 Creating OMP Boot Files .............................................44 Configuring OMP Running Parameters via Serial Port .................................................................47 Configuring OMP Global Data ......................................58 Synchronizing All Tables .............................................59 Loading Version Files..................................................62 Creating MGCF Tones in Batches ......................................65 Office Information Configuration ......................................67 Overview..................................................................67 Creating Local Office Signaling Point.............................67 Creating Local Office Configuration...............................70
Resource Configuration ................................... 73 Resource Planning .........................................................73 Configuring Resource Attributes.......................................73
MGCF-IM-MGW Interconnection Data Configuration .................................................. 79 Overview......................................................................79 Interface IP Address Configuration ...................................81 Overview..................................................................81 Creating a Loopback Interface .....................................82 Creating an SIPI Interface Address ..............................83 Creating a Virtual Interface Address .............................85 BFD Configuration (Optional) ..........................................87 Overview..................................................................87 Creating BFD Authentication .......................................87 Creating a BFD Session ..............................................88 Creating a Static Route ..................................................90 Adjacent Office and Topology Configuration .......................92 Overview..................................................................92 Creating an IM-MGW Adjacent Office............................92 Creating an MGW Voice CODEC Template ......................97 Creating a Topology Node ...........................................99 Creating Inter-MGW Bear Mode ................................. 103 SIGTRAN Configuration ................................................ 106
II
Confidential and Proprietary Information of ZTE CORPORATION
Overview................................................................ 106 SCTP Planning......................................................... 108 Creating an SCTP .................................................... 108 Creating an ASP ...................................................... 111 Creating an AS ........................................................ 113 Creating an M3UA Static Route .................................. 116 Creating the SIO Locate AS....................................... 117 H.248 Configuration..................................................... 119 Overview................................................................ 119 Creating MGC Static Data ......................................... 121 Creating MGW Static Data Template ........................... 122 Creating MGW Static Data ........................................ 124 Creating a TID Analyzer ........................................... 126 Creating a TID Analysis Entrance ............................... 127
MGCF-SIP Office Interconnection Data Configuration ................................................ 129 Overview.................................................................... 129 SIPCC Data Configuration ............................................. 130 Overview................................................................ 130 Creating a SIP Adjacent Office................................... 130 Creating SIP Office Direction ..................................... 135 Creating SIP Adjacent Office Topology Node ................ 136 SIP Protocol Stack Configuration.................................... 141 Overview................................................................ 141 Creating an IP Link .................................................. 142 Setting the Capacity for a SIP Module......................... 144 Creating a Domain where the MGCF Belongs ............... 145 Creating a MGCF Host .............................................. 146 Creating Route Selector............................................ 147 Creating Service Group ............................................ 148 Creating an Adjacent Host ........................................ 149 Creating UDP Bear ................................................... 151 Creating a SIP Signaling Link .................................... 153 Creating a SIP Signaling Route .................................. 154 Creating a SIP signaling Route Set ............................. 155 Creating IP Distribution Policy ................................... 156 Creating URI Analysis............................................... 158 Creating an RTP Trunk Group ........................................ 160
Confidential and Proprietary Information of ZTE CORPORATION
III
ZXWN MSCS Data Configuration Guide(MGCF)
MGCF-Other-Exchange Interconnection Data Configuration ................................................ 165 Networking Mode......................................................... 165 Office Interconnection in IP Domain ............................... 166 Overview................................................................ 166 Direct-Associated Office Configuration in IP Domain .......................................................... 167 Overview ....................................................... 167 Creating an Adjacent Office .............................. 168 Creating an MSCS Topological Node ................... 172 M3UA-Transferred Office Configuration ....................... 175 M2UA-Transferred Office Configuration ....................... 177 Overview ....................................................... 177 Creating an M2UA IP Link................................. 179 TDM Office Interconnection ........................................... 181 Overview................................................................ 181 Creating a Signaling Link Set .................................... 183 Creating an SPB-Accessed Signaling Link .................... 185 Creating a Signaling Route........................................ 188 Creating a Signaling Office........................................ 190
Basic Service Data Configuration................... 193 Overview.................................................................... 193 Number Analysis Configuration ...................................... 193 Overview................................................................ 198 Creating Number Analysis Entrance............................ 198 Creating Number Analysis Selector ............................ 201 Setting the Template of Number Analysis Selector of the Current Office ............................................ 203 Creating Templet of Number Analysis Selector (Optional)....................................................... 206 Creating Called Number Analysis ............................... 211 Trunk Data Configuration .............................................. 235 Overview................................................................ 235 Creating a DT Trunk Group........................................ 236 Creating an ATM Trunk Group .................................... 243 Creating RTP Trunk Group......................................... 250 Creating PCM .......................................................... 254 Configure a PCM System between MGWs .................... 256 Route Data Configuration.............................................. 258 Overview................................................................ 258
IV
Confidential and Proprietary Information of ZTE CORPORATION
Creating a Route ..................................................... 259 Creating a Route Set................................................ 260 Creating an Outgoing Route Chain ............................. 262
Configuration Instance.................................. 265 Overview.................................................................... 265 Local Office Data Configuration...................................... 266 Local Exchange Configuration ................................... 267 Physical Configuration .............................................. 267 Capacity Configuration ............................................. 268 Version Loading....................................................... 269 Office Data Configuration.......................................... 269 Resource Attribute Configuration ................................... 270 Adjacent IM-MGW Office Interconnection Data Configuration ...................................................... 271 Adjacent SCSCF Office Interconnection Data Configuration ...................................................... 274 Basic Service Data Configuration ................................... 276 Call Data Configuration............................................. 276 SIP Service Data Configuration .................................. 277 Data Synchronization ................................................... 277 MGCF-IM-MGW Interconnection Debugging Procedure........................................................... 277 Checking the IM-MGW Office Status ........................... 278 Checking the Physical Connection .............................. 279 Debugging the SCTP ................................................ 279 Debugging the M3UA ............................................... 279 Confirming the Working Status of the IM-MGW ............ 280 H.248/SCTP Problem Location Method ........................ 281 M3UA Problem Location Method................................. 281
Figure............................................................ 283 Table ............................................................. 285 Index ............................................................ 289
Confidential and Proprietary Information of ZTE CORPORATION
V
ZXWN MSCS Data Configuration Guide(MGCF)
This page is intentionally blank.
VI
Confidential and Proprietary Information of ZTE CORPORATION
About This Manual Purpose
At first, thank you for choosing ZXWN wireless core network system of ZTE Corporation! ZXWN system is the 3G mobile communication system developed based on the UMTS technology. ZXWN system boasts powerful service processing capability in both CS domain and PS domain, providing more abundant service contents. Comparing with the GSM, ZXWN provides telecommunication services in wider range, capable of transmitting sound, data, graphics and other multi-media services. In addition, ZXWN has higher speed and resource utilization rate. ZXWN wireless core network system supports both 2G and 3G subscriber access, and provides various services related with the 3G core network. The ZXWN MSCS system is designed for the UMTS system at the core network control level. It supports the GSM core network, UMTS protocols in the R99/R4/R5 stage and relevant functions at the same time, and provides the carriers with an overall solution to the evolution from the GSM core network to the 3GPP R99 and then to the 3GPP R5. The ZXWN MSCS system completes the functions of the Mobile Switching Center Server and the Visitor Location Register (VLR) together, and provides the Service Switching Point (SSP) functions of intelligent calls. The ZXWN MSCS system supports the MGCF function, and the coexistence of the MGCF and GMSCS. It also can smoothly upgrade to the MGCF. This purpose of this manual is to let the carrier master the data configuration method of MGCF.
Intended Audience
This manual is intended for engineers and technicians who have mastered the communication principle of the mobile network.
Prerequisite Skill and Knowledge
To use this document effectively, users should have a general understanding of wireless telecommunications technology. Familiarity with the following is helpful: �
What Is in This Manual
MSCS system and its various components
This manual contains the following chapters: Chapter
Summary
Chapter 1, Data Configuration Overview
Describes the overall flow of the MGCF data configuration and basic operations of the background network management (OMM) system
Chapter 2, Local Office Data Configuration
Describes the physical configuration, capacity configuration, version configuration, and office information configuration of MGCF
Confidential and Proprietary Information of ZTE CORPORATION
I
ZXWN MSCS Data Configuration Guide(MGCF)
FCC Compliance Statement
Chapter
Summary
Chapter 3, Resource Configuration
Describes MGCF resource planning and attribute configuration
Chapter 4, MGCF-IM-MGW Interconnection Data Configuration
Describes the signaling interworking configuration between MGCF and IM-MGW
Chapter 5, MGCF-SIP Office Interconnection Data Configuration
Describes the signaling interworking configuration between MGCF and SIP office
Chapter 6, MGCF-OtherExchange Interconnection Data Configuration
Describes the signaling interworking configuration between MGCF and other exchanges at the network side
Chapter 7, Basic Service Data Configuration
Describes the basic data configuration related with the call service
Chapter 8, Configuration Instance
Sets MGCF trial office as an example to describe the data configuration of the local office and the peer office
This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions. 1. This device may not cause harmful interference. 2. This device must accept any interference received, including interference that may cause undesired operation. Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the 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 and company name. Note: Provides additional information about a certain topic. Checkpoint: Indicates that a particular step needs to be checked before proceeding further. Tip: Indicates a suggestion or hint to make things easier or more productive for the reader.
II
Confidential and Proprietary Information of ZTE CORPORATION
About This Manual
Mouse operation conventions are listed as follows: Typeface
Meaning
Click
Refers to clicking the primary mouse button (usually the left mouse button) once.
Doubleclick
Refers to quickly clicking the primary mouse button (usually the left mouse button) twice.
Right-click
Refers to clicking the secondary mouse button (usually the right mouse button) once.
Confidential and Proprietary Information of ZTE CORPORATION
III
ZXWN MSCS Data Configuration Guide(MGCF)
This page is intentionally blank.
IV
Confidential and Proprietary Information of ZTE CORPORATION
Declaration of RoHS Compliance To minimize the environmental impact and take more responsibility to the earth we live, this document shall serve as formal declaration that ZXWN MGCF manufactured by ZTE CORPORATION are in compliance with the Directive 2002/95/EC of the European Parliament - RoHS (Restriction of Hazardous Substances) with respect to the following substances: �
Lead (Pb)
�
Mercury (Hg)
�
Cadmium (Cd)
�
Hexavalent Chromium (Cr (VI))
�
PolyBrominated Biphenyls (PBB’s)
�
PolyBrominated Diphenyl Ethers (PBDE’s)
… The ZXWN MGCF manufactured by ZTE CORPORATION meet the requirements of EU 2002/95/EC; however, some assemblies are customized to client specifications. Addition of specialized, customer-specified materials or processes which do not meet the requirements of EU 2002/95/EC may negate RoHS compliance of the assembly. To guarantee compliance of the assembly, the need for compliant product must be communicated to ZTE CORPORATION in written form. This declaration is issued based on our current level of knowledge. Since conditions of use are outside our control, ZTE CORPORATION makes no warranties, express or implied, and assumes no liability in connection with the use of this information.
Confidential and Proprietary Information of ZTE CORPORATION
I
ZXWN MSCS Data Configuration Guide(MGCF)
This page is intentionally blank.
II
Confidential and Proprietary Information of ZTE CORPORATION
Chapter
1
Data Configuration Overview Table of Contents MGCF Introduction.............................................................. 1 Overall Flow of MGCF Data Configuration ............................... 2 Basic Operations of the OMM System .................................... 4
MGCF Introduction Networking
ZXWN MSCS can serve as a MGCF, composing an IMS system together with NEs of ZXUN. The MGCF can be combined with the GMSCS, or separately set. The position of the MGCF in the IMS network is shown in Figure 1. FIGURE 1 IMS NETWORKING
Interface
When the MSCS serves as a MGCF, the following interfaces are involved: �
Mg interface: The MGCF is connected with the CSCF through the Mg interface adopting the SIP protocol.
�
Nc: The MGCF is connected with the R4 CS network through the Nc interface adopting the BICC protocol.
�
Ai interface: The MGCF is connected with the PSTN network through the Ai interface adopting the ISUP protocol.
�
Mn interface: The MGCF is connected with the IM-MGW through the Mn interface adopting the H.248 protocol.
Confidential and Proprietary Information of ZTE CORPORATION
1
ZXWN MSCS Data Configuration Guide(MGCF)
Overall Flow of MGCF Data Configuration Prerequisites
Before the data configuration, it is required to confirm: �
The hardware installation is completed and the cable connections are normal. The rack, shelves, and boards are all installed. Cables are all connected well, and the equipment can be normally powered on.
�
The background network management system is installed. The IP addresses of the background OMM server and client are planned. The LAN is constructed, and the foreground OMP is connected. The OMM server software and client software are installed, ensuring that the OMM client can normally log in to the OMM server. For the installation of the OMM server software and client software, refer to ZXWN MSCS MSC Server Software Installation.
Configuration Flow
2
The overall flow of the MGCF data configuration is shown in Figure 2.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 1 Data Configuration Overview
FIGURE 2 OVERALL FLOW OF THE MGCF DATA CONFIGURATION
Flow Description
The flow description of MGCF data configuration is shown in . Steps
Operations
Description
1
Local office data configuration
Perform local exchange configuration, physical configuration, capacity configuration, version loading, office information configuration, and basic SIP configuration for the local office
2
MGCF-IM-MGW interconnection data configuration
Configure the Mn-interface signaling interconnection data
3
MGCF-SIP office interconnection data configuration
Configure the SIP signaling interconnection data with CSCF, BGCF, and MGCF office
Confidential and Proprietary Information of ZTE CORPORATION
3
ZXWN MSCS Data Configuration Guide(MGCF)
Steps
Operations
Description
4
MGCF-other exchange interconnection data configuration
Configure the signaling interconnection data with other offices at the network side except the MGW, such as MSCS, PSTN, and 2G MSC
5
Basic service data configuration
Configure the data related to the SIP service and the basic call service
Basic Operations of the OMM System To perform data configuration, it is required to be familiar with the basic operations of the OMM system, including the following operations. No.
Operations
1
Logging in the OMM Client
2
Entering the MML Terminal
3
Operations on the MML Terminal
4
Synchronizing Data
Logging in the OMM Client Prerequisites
4
Before the operation, it is required to confirm: �
The server and the client of the network management are installed.
�
The communication between the server and the client is normal.
Context
The purpose of logging in to the OMM client is to perform data configuration and daily maintenance by using the background OMM software.
Steps
1. On the OMM server, select Start > Programs > ZXWN-CS (OMM) > Start Server. the NetNumen (TM) Console window pops up, displaying the start process of the OMM server, as shown in Figure 3.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 1 Data Configuration Overview
FIGURE 3 START PROCESS OF THE OMM SERVER
2. After the OMM server starts successfully, the prompt messages are displayed in the Detailed Specification area, as shown in Figure 4. FIGURE 4 START INFORMATION OF THE OMM SERVER
3. On the server, click Start > Programs > ZXWN-CS (OMM) > Start Client , and then the Login dialog box appears, as shown in Figure 5.
Confidential and Proprietary Information of ZTE CORPORATION
5
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 5 LOGIN WINDOW
4. After entering the login information, click OK. The parameter description is described in Table 1. TABLE 1 LOGIN PARAMETER DESCRIPTION
6
Name
Meaning
Default
User name
Indicates the name of the subscriber who logs in the network server. The default name is admin (system administrator). If other subscriber fails to log in the network management server for many times (exceeds the maximum), the subscriber will be locked automatically. This subscriber only could be unlocked by the administrator or when the locking duration expires. The login operation that exceeds the maximum should be reported to the network management, so that the network management could know the maintenance status of the equipment in order to avoid the login of the unauthorized subscriber and other operation errors. The maximum login limitation times in this system is 3
admin
Password
It indicates the password that is used to log in the OMM server. The password of the new installed network management is null
Null
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 1 Data Configuration Overview
Name
Meaning
Default
Server address
Indicates the IP address of the network management server. If the server and the client are not installed in the same computer, it is required to enter the real IP address of the server. or else, you can enter the actual IP address or adopt the default IP address
127.0.0.1
END OF STEPS Result
After the login is successful, the main window of the OMM system pops up, as shown in Figure 6. FIGURE 6 NETNUMEN M30 MSCS/MGW OMM SYSTEM WINDOW
Entering the MML Terminal Prerequisites
To enter the MML terminal, the following condition must be met: The user has logged in the OMM Server successfully.
Context Steps
This topic describes how to enter the MML terminal. 1. On the OMM client, select Views > MML Terminal to enter the MML Terminal window. The left shows the configuration tree, and the right shows the attribute pane, as shown in Figure 7.
Confidential and Proprietary Information of ZTE CORPORATION
7
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 7 MML TERMINAL WINDOW
END OF STEPS Result
Enters the MML Terminal successfully.
Operations on the MML Terminal Command Terminal Window
8
The main operation of the data configuration is to type the command in the MML Terminal window, as shown in Figure 8.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 1 Data Configuration Overview
FIGURE 8 MML TERMINAL WINDOW
On the left pane of the MML Terminal window, the root node represents the OMM server node, which is the real root node. The nodes under the root node represent the specific NEs to be configured. Command Typing
The command is typed in the input box at the lower right corner of the MML Terminal window. For example, type in command SET:NEID=11;, as shown in Figure 8. In general, a command is associated with a network element (except the command used to configure an exchange). For example, create a shelf for MGCF11(the ID can be queried with the command SHOW NE;). The following two methods can be used to perform the conjunction:
Command Execution
�
Type the command SET: NEID=11; and click F5 to execute the command (the method is widely adopted in this document).
�
Select the network element of which the exchange ID is 11 from the left configuration system tree, such as MGCF11.
This part describes the procedure of command line operation. Click F5 to execute the command after it is typed. After the command is executed, the Command Execute Result pane shows the result or the information read by this command, as shown in Figure 9.
Confidential and Proprietary Information of ZTE CORPORATION
9
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 9 COMMAND EXECUTION OPERATIONS
Synchronizing Data Prerequisites
Context
Before the operation, it is required to confirm: �
The MML Terminal window is opened.
�
Some data configurations or all data configuration are completed.
When configuring the data on the OMM, such as creating data, modifying data or deleting data, the data will be saved to the OMM Server in the form of data list after executing the F5 button. At this time, the foreground data are not modified. The data synchronization is to synchronize the data on the OMM Server to the foreground. The data synchronization operation could be done after finishing each step or after finishing configuring all the data.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Data transfer includes transferring data by using the “Admin” user and transferring data by using the current login user. �
Synchronize Admin data. The command is SYNA.
Tip: This command is used by Admin users to synchronize all table data, no matter whether the tables are locked by other users. Table 2 describes the parameters in this command.
10
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 1 Data Configuration Overview
TABLE 2 PARAMETERS IN THE SYNA COMMAND Name
Meaning
Instructions
USERNAME
User name
It consists of 0~50 characters and the default value is admin It includes
STYPE
CHG (Single User Changed Tables)
–
ALL (All Tables)
–
ALLCHG (All Changed Tables)
Module list
It indicates the module ID in decimal. If there are many module IDs, use the symbol & to connect them.
TIMEOUT
Response timeout (100ms)
It is an optional parameter and the default value is 600. Adjust the response timeout according to the actual requirement.
SAVE
Save when completed
It is an optional parameter and the default value is YES
TOSLAVE
Sync to slave when completed
It is an optional parameter and the default value is YES
MODULES
�
Sync type
–
Synchronize the data of currently login user. The command is SYN.
Tip: This command is used to synchronize the table data configured by a login user. The table data not configured by the login user can not be synchronized to the foreground. Table 3 describes the parameters in this command. TABLE 3 PARAMETERS IN THE SYN COMMAND Name
Meaning
Instructions
MODULES
Module list
It indicates the module ID in decimal. If there are many module IDs, use the symbol & to connect them.
TIMEOUT
Response timeout (100ms)
It is an optional parameter and the default value is 600. Adjust the response
Confidential and Proprietary Information of ZTE CORPORATION
11
ZXWN MSCS Data Configuration Guide(MGCF)
�
Name
Meaning
SAVE
Save when completed
It is an optional parameter and the default value is YES
TOSLAVE
Sync to slave when completed
It is an optional parameter and the default value is YES
Instructions timeout according to the actual requirement.
Example: To synchronize all the tables with admin user. The command is as follows: SYNA:STYPE=ALL,TIMEOUT=600,SAVE=YES,TOSLAV E=YES;
�
Example: To synchronize the data of the current user, the command is as follows: SYN:TIMEOUT=600,SAVE=YES,TOSLAVE=YES;
END OF STEPS Result
12
After the command is executed, the progress of table transferring is shown on the Message Report pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter
2
Local Office Data Configuration Table of Contents Overview..........................................................................14 Local Exchange Configuration..............................................15 Physical Configuration ........................................................18 Capacity Configuration .......................................................34 Version Loading.................................................................39 Creating MGCF Tones in Batches ..........................................65 Office Information Configuration ..........................................67
Confidential and Proprietary Information of ZTE CORPORATION
13
ZXWN MSCS Data Configuration Guide(MGCF)
Overview Configuration Flow
Figure 10 shows the flow of the local office data configuration. FIGURE 10 LOCAL OFFICE DATA CONFIGURATION FLOW
Flow Description
14
The local office data configuration contains the following steps. Steps
Operations
Procedures
1
Local exchange Configuration
Create MGCF exchange and set the province and city information of the local office
2
Physical configuration
Create foreground-corresponded racks, shelves, units, modules, and their attributes on the background OMM system
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Steps
Operations
Procedures
3
Capacity configuration
Set the MP table capacity
4
Version loading
Load the version files to the foreground, which are required for normal running of different foreground boards
5
Create MGCF tones in batches
Create a batch MGCF tones
6
Office information configuration
Configure the local office signaling point, exchange type and country code
Local Exchange Configuration Overview Introduction
Contents
Local exchange configuration is to define the information of the local exchange on the OMM system such as its type. It is the first data configuration in deployment. The exchange configuration contains the following steps. Steps
1
2
Operations
Instructions
Commands
Creating an exchange
Create the NE corresponded by the exchange on the background OMM system
ADD NE
Setting province and city information of the bureau
Configure the provincial and city codes of the exchange, thus to display the area information in the Element Management System (EMS)
SET PCINFO
Creating an Exchange Prerequisites Context Steps
The MML Terminal window is opened. Perform this procedure to create the NE corresponded by the exchange on the background OMM system. 1. Create an MGCF exchange with the ADD NE command.
Confidential and Proprietary Information of ZTE CORPORATION
15
ZXWN MSCS Data Configuration Guide(MGCF)
Table 4 describes the main parameters in the ADD NE command. TABLE 4 PARAMETERS IN THE ADD NE COMMAND Parameter Name
Parameter Description
Instruction
ID
The unique ID of an exchange
It is a mandatory parameter. It ranges from 11 to 30. It cannot be modified once it is created.
TYPE
Type of the exchange to be created
It is a mandatory parameter. Select MSCS.
MESUBTYPE
NE sub-type
It is an optional parameter. Select NONE for an end office, and TMSC1 or TMSC2 for a tandem office.
NAME
Exchange name customized by user
It is an optional parameter. With a length ranging from 0 to 50 characters.
VENDOR
Equipment manufacturer
It is an optional parameter. Type ZTE, by default.
STATE
State defined by the user
It is an optional parameter. Select 0, by default.
Location where the equipment is located
It is an optional parameter. Type the location information of the equipment. It is recommended to describe it with letters or digits.
LOC
Example: Create an MGCF office with the following requirements. �
Office ID: 11
�
TYPE: MSCS
�
Alias: MGCF11
�
Other parameter: default.
The specific command is as follows. ADD NE:ID=11,TYPE=MSCS,MESUBTYPE=NONE,NAME ="MGCF11",VENDOR="ZTE",STATE=0; END OF STEPS Result
16
After the command is executed successfully, the MGCF11 node is created under the root node in the OMM client interface. Mean-
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
while, the rack is generated, with the rack No. as 1 and the alias as rack1.
Setting Province and City Information of the Bureau Prerequisites
Before the operation, it is required to confirm: �
The MGCF exchange is added.
�
The MML Terminal window is opened.
Context
Perform this procedure to configure the provincial and city codes of the exchange, thus to display the area information in the Element Management System (EMS).
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Set the province and city codes of the exchange. The command is SET PCINFO. Table 5 describes the main parameters in the SET PCINFO command. TABLE 5 PARAMETERS IN THE SET PCINFO COMMAND Parameter Name
Parameter Description
Instruction
PROVINCE
Provincial code
It is a mandatory parameter. For displaying area information of the exchange in the EMS.
CITY
City code
It is a mandatory parameter. For setting the city code.
Example: Set the province and city codes of the exchange. The exchange is located in Nanjing city of Jiangsu province. The specific command is as follows. SET PCINFO:PROVINCE="320000",CITY="320101"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
17
ZXWN MSCS Data Configuration Guide(MGCF)
Physical Configuration Overview Introduction Flow diagram
This section describes the physical configuration . Figure 11 shows the physical configuration flow. FIGURE 11 PHYSICAL CONFIGURATION FLOW
Flow description
18
The physical configuration contains the following steps.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Steps
Operations
Instructions
Command
1
Creating a Rack
Create a logic rack on the background OMM system
ADD RACK
2
Creating a Shelf
Create a logic shelf on the background OMM system
ADD SHELF
3
Creating the UIM Unit
Create the UIM board
ADD UNIT
Creating a Module
When MSCS has several modules, it is required to create SMP board for BCTC shelf
ADD MODULE
5
Creating Other Units
Create other logic boards in the BCTC shelf of MSCS exchange, except for UIM unit
ADD UNIT
6
Creating Background Server Node
Connect the SMP with the billing server
ADD SVRINF
4
Creating a Rack Prerequisites
Before the operation, it is required to confirm: �
The exchange has been created.
�
The MML Terminal window is opened.
Context
Perform this procedure to create a logic rack on the background OMM system. It corresponds to the rack on the foreground. Since the system automatically creates rack 1 during the exchange creation, you need not to create it again. But you need to create other racks manually here.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a rack. The command is ADD RACK. Table 6 describes the parameters in the ADD RACK command.
Confidential and Proprietary Information of ZTE CORPORATION
19
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 6 PARAMETERS IN THE ADD RACK COMMAND Parameter Name
RACK
Parameter Description
Instructions
Rack No.
It is a mandatory parameter within 1~15. Rack 1 is generated during creating the exchange. Other racks need to be created by manual. The rack No. begins from 2
Rack type, includes �
3G_STANDARD_RACK: ZTE standard rack
�
3G_INTEGRATION_RACK: ZTE integration rack
RACK TYPE
NAME
Alias
It is an optional parameter. Select it according to the actual rack type.
It is an optional parameter and consists of 0~50 strings
Example: Create a ZTE standard rack whose rack No. is 2. The command is as follows. ADD RACK:RACK=2,RACKTYPE=3G_STANDARD_RACK,NA ME="RACK2"; Example: Create a ZTE integration rack whose rack No. is 3. The command is as follows. ADD RACK:RACK=3,RACKTYPE=3G_INTEGRATION_RAC K,NAME="RACK2"; END OF STEPS Result
After the command is executed successfully, the rack is created under MGCF11 exchange, and is shown on the Daily Maintenance > Rackchart Management tab.
Creating a Shelf Prerequisites
Context
20
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
The rack is created under the corresponding exchange.
�
The MML Terminal window is opened.
Perform this procedure to create a logic shelf on the background OMM system. It corresponds to the shelf on the foreground. MGCF only adopts BCTC shelf. One rack can be configured with up to four BCTC shelves.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Note: Shelf 2 of rack 1 must be created first, and then other shelves are created. Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a shelf. The command is ADD SHELF. Table 7 describes the parameters in the ADD SHELF command. TABLE 7 PARAMETERS IN THE ADD SHELF COMMAND Name
Meaning
Instructions
RACK
Rack No.
It is a mandatory parameter that is within 1~15.
SHELF
Shelf No.
It is a mandatory parameter, ranging from 1 to 4. Shelf 2 must be configured first.
TYPE
Shelf type
It is a mandatory parameter. MGCF can only be configured with BCTC shelf (control shelf).
NAME
Alias
It is an optional parameter, with a length ranging from 0 to 50 characters.
Example: Create a BCTC shelf in rack 1, with the shelf number as 2 and the name as “BCTC”. The specific command is as follows. ADD C";
SHELF:RACK=1,SHELF=2,TYPE=BCTC,NAME="BCT
END OF STEPS Result
After BCTC shelf is created successfully, the OMP module and the RPU module are created at the same time. The numbers of these two modules are 1 and 2. Slots 11 and 12 of the rack display the OMP board.
Creating the UIM Unit Prerequisites
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
The BCTC shelf is created in the corresponding rack.
�
The MML Terminal window is opened.
Confidential and Proprietary Information of ZTE CORPORATION
21
ZXWN MSCS Data Configuration Guide(MGCF)
Context
Creating the UIM unit is to create the UIM board. In general, UIM board adopts 1+1 backup mode. It is fixedly inserted into slots 9 and 10 in the BCTC shelf.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a UIM Unit. The command is ADD UNIT.
Note: You must first create the UIMC unit in shelf 2 of rack 1, and then create the UIMC units in other BCTC shelves. Table 8 describes the parameters in the ADD UNIT command. TABLE 8 PARAMETERS IN THE ADD UNIT COMMAND Parameter Name
Parameter Description
Instruction It is a mandatory parameter and the format is RACK-SHELF-SLOT.
LOC
22
Unit location
�
The rack No. is within 1~15 and the default value is 1. This parameter is defined by the ADD RACK command.
�
The shelf No. is within 1~4. This parameter is defined by the ADD SHELF command.
�
The slot represents the slot number. In BCTC shelf, the UIM slot number must be 9 and 10.
MODULE
Module No.
It is a mandatory parameter. Select 1.
UNIT
Unit No.
It is an optional parameter, ranging from 1 to 2000.
TYPE
Unit type
It is a mandatory parameter. Select it according to the CPU type of the UIMC board, including UIM2_GCS_755 and UIM2_GCS_8260. UIM2_GCS_755 sub-card is mostly used at present.
BKMODE
Backup mode
It is a mandatory parameter and the backup mode is ONEPLUSONE.
NAME
Alias
It is an optional parameter and consists of 0~50 characters.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Example: Add the UIM units with the following requirements. �
Rack No.: 1
�
Shelf No.: 2
�
Slot No.: 9 and 10
�
Unit type: UIM2_GCS_755
�
Backup mode: 1+1 backup
The specific command is as follows. ADD UNIT:LOC="1"-"2"-"9",MODULE=1,UNIT=921,TYPE =UIM2_GCS_755,BKMODE=ONEPLUSONE,CLK1=16383,CL K2=16383;
Tip: After the 1+1 backup mode is selected for the UIM board located in slot 9, the system will automatically create the UIM board located in slot 10. In addition, the unit numbers of left and right slots are consistent. END OF STEPS Result
After the UIM unit is created successfully, the active and standby UIM boards are shown in the corresponding slots of the rack chart.
Creating a Module Prerequisites
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
The UIM unit is created under the exchange.
�
The MML Terminal window is opened.
Context
When MGCF has several modules, it is required to create SMP board for BCTC shelf. When BCTC has more shelves, SMP and CMP modules should be allocated to each BCTC shelf equally.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a module. The command is ADD MODULE. Table 9 describes the parameters in the ADD MODULE command.
Confidential and Proprietary Information of ZTE CORPORATION
23
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 9 PARAMETERS IN THE ADD MODULE COMMAND Name
Meaning
Instructions
LOC
Location
It is a mandatory parameter. Its format is RACK-SHELF-SLOT. The range of RACK is within 1~15 and the default value is 1. The shelf No. is within 1~4 and the slot No. is within 1~17.
MODULE
Module No.
It is a mandatory parameter, ranging from 3 to 127. A new module is numbered from 3. It is a mandatory parameter.
FUNC1
Module 1 type
�
Select SMP for a signaling module.
�
Select MSCBASECMP for a service module.
�
When MSCS serves as MGCF, select SIP type.
Module 2 type
It is an optional parameter. If it is left blank, its configuration is the same as that of FUNC1.
CPU type
It is an optional parameter. Two options available, X86 and CENTRINO. Select according to the actual board type.
BKMODE
Backup mode
It is an optional parameter. In general, select ONEPLUSONE (one plus one backup) for a service module, and ONEPLUSONE (one plus one backup) or No (Without backup) for a signaling module, which is determined by the actual configuration.
NAME1
Module 1 user alias
It is an optional parameter and consists of 0~50 characters.
NAME2
Module 2 user alias
It is an optional parameter and consists of 0~50 characters.
FUNC2
CPUTYPE
Example: Create SMP modules with the following requirements.
24
�
Location: Slots 5 and 6 in BCTC shelf 2 of rack 1
�
Module number: 3 and 4
�
Module type: SMP
�
CPU type: CENTRINO
�
Backup mode: 1+1 backup
�
Module 1 name: SMP3
�
Module 2 name: SMP4.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
The specific command is as follows. ADD MODULE:LOC="1"-"2"-"5",MODULE="3"&"4",FUNC1 ="SMP",FUNC2="SMP",CPUTYPE=CENTRINO,BKMODE=ON EPLUSONE,NAME="SMP3",NAME2="SMP4"; Example: Create CMP modules with the following requirements. �
Location: Slots 7 and 8 in BCTC shelf 2 of rack 1
�
Module number: 5 and 6
�
Module type: CMP
�
CPU type: CENTRINO
�
Backup mode: 1+1 backup
�
Module 1 name: CMP5
�
Module 2 name: CMP6.
The specific command is as follows. ADD MODULE:LOC="1"-"2"-"7",MODULE="5"&"6",FUNC1 ="MSCBASECMP"&"SIP",FUNC2="MSCBASECMP"&"SIP",CP UTYPE=CENTRINO,BKMODE=ONEPLUSONE,NAME="CMP5 ",NAME2="CMP6"; END OF STEPS Result
After the SMP/CMP module is created successfully, its corresponding slot in the rack chart displays the SMP board.
Creating other Units Prerequisites
Context
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
The UIM unit is created.
�
The MML Terminal window is opened.
Perform this procedure to create other logic boards in the BCTC shelf of MGCF exchange, except for UIM unit. Table 10 lists the main boards in MGCF. TABLE 10 MGCF BOARD TYPES Board
Board Type
Backup Mode
SIPI2_IPSEC SIPI
SIPI2_NC
No backup or 1+1 active/standby backup
SIPI_NC SPB2_8260_8260C4 SPB
No backup SPB2_8250_85XXC2
Confidential and Proprietary Information of ZTE CORPORATION
25
ZXWN MSCS Data Configuration Guide(MGCF)
Board
Board Type
Backup Mode
USI2_NC USI
1+1 active/standby backup USI_NC
Steps
CHUB
CHUB
1+1 active/standby backup
CLKG
CLKG
1+1 active/standby backup
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create other units. The command is ADD UNIT. No.
Operations
1
Creating a CHUB unit
2
Creating a CLKG unit
3
Creating an SIPI unit
4
Creating a USI Unit
5
Creating an SPB unit
END OF STEPS
Creating a CHUB Unit Prerequisites
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
The UIM unit is created.
�
The MML Terminal window is opened.
Context
Perform this procedure to create the CHUB logic board corresponding to that in the foreground BCTC shelf of MGCF exchange.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a CHUB unit. The command is ADD UNIT. Table 11 describes the main parameters in the command.
26
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
TABLE 11 PARAMETER IN THE ADD UNIT COMMAND Parameter Name
Parameter Description
Instruction It is a mandatory parameter, with a format of RACK-SHELF-SLOT
Location of the unit in the system
LOC
�
RACK represents the rack number, ranging from 1 to 15. In general, it is configured as 1.
�
SHELF represents the shelf number, ranging from 1 to 4.
�
SLOT represents the slot number. CHUB boards are fixedly inserted into slots 15 and 16 in shelf 2 of rack 1.
MODULE
Module number of the unit
It is a mandatory parameter. Select 1
UNIT
Unit number of the board
It is an optional parameter ranging from 1 to 2000.
TYPE
Logic unit type of the board
Select CHUB
BKMODE
Backup mode of the unit
Select ONEPLUSONE 1+1 active/standby backup
Example: Create CHUB boards with the following requirements. Location: Slots 15 and 16 of shelf 2 in rack 1 Unit type: CHUB Backup mode: 1+1 active/standby backup Other parameters: default. The specific command is as follows. ADD UNIT:LOC="1"-"2"-"15",MODULE=1,UNIT=1521,TY PE=CHUB,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=16 383; END OF STEPS Result
After the unit is created successfully, corresponding slots of the rack chart display these CHUB boards.
Creating a CLKG Unit Prerequisites
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
The UIM unit is created.
�
The MML Terminal window is opened.
Confidential and Proprietary Information of ZTE CORPORATION
27
ZXWN MSCS Data Configuration Guide(MGCF)
Context
Perform this procedure to create the CLKG logic board corresponding to that in the foreground BCTC shelf of MGCF exchange.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a CLKG unit. The command is ADD UNIT. Table 12 describes the parameters in the command. TABLE 12 PARAMETERS IN THE ADD UNIT COMMAND Parameter Name
Parameter Description
LOC
Unit location
Instruction It is a mandatory parameter and the format is RACK-SHELF-SLOT. �
The rack No. is within 1~15 and the default value is 1. This parameter is defined by the ADD RACK command.
�
The shelf No. is within 1~4. This parameter is defined by the ADD SHELF command.
�
The slot No. is within 1~17.
MODULE
Module No.
It is a mandatory parameter. Select the OMP module belonging to CLKG.
UNIT
Unit No.
It is an optional parameter, ranging from 1 to 2000.
TYPE
Unit type
It is a mandatory parameter. For CLKG, select CLKG
BKMODE
Backup mode
It is a mandatory parameter and the backup mode is ONEPLUSONE.
NAME
Alias
It is an optional parameter and consists of 0~50 characters.
Example: ments.
Create CLKG boards with the following require-
�
Location: Slots 13 and 14 of shelf 2 in rack 1
�
Unit type: CLKG
�
Backup mode: 1+1 active/standby backup
�
Other parameters: default.
The specific command is as follows. ADD UNIT:LOC="1"-"2"-"13",MODULE=1,UNIT=1321,TY PE=CLKG,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=163 83;
28
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
3. After creating the CLKG unit, configure the CLKG board parameters with the SET CLKETHR command as required. Configure its parameters based on the clock source actually provided. Example: Configure clockbase setting of the CLKG board to be allowed, and the clock reference is 8KBase. The command is as follows. SET CLKETHR:CLKBASE=ALLOWED,BASETYPE=8KBase,B ASEINFO="8KBase"; END OF STEPS Result
After the unit is created successfully, corresponding slots of the rack chart display these CLKG boards.
Creating an SIPI Unit Prerequisites
Context
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
The UIM unit is created.
�
The MML Terminal window is opened.
Perform this procedure to create the SIPI logic board corresponding to that in the foreground BCTC shelf of MGCF exchange. �
SIPI boards work in load-sharing mode In load-sharing mode, two SIG-IPI boards both serve as active board, and maintain each own associations. The relationship between associations is load-sharing, which means that the service transmission is shared evenly by the associations of these two SIG_IPI boards. When the association on one of these two interface boards is interrupted, all the service data will be moved to the association of another interface board that works normally. In this way, the inter-office communication will not be interrupted for this cause. This project is recommended for office commissioning .
�
SIPI boards work in active/standby mode . Two SIG_IPI boards serve as mutual backup. In normal conditions, associations are only processed on active board, and backed up only on standby board. The associations on the active board are disconnected when the active board is abnormal or extracted. At this moment, the standby board quickly replaces the active board to connect the associations, thus to restore the normal communication between offices.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an SIPI unit. The command is ADD UNIT. Table 13 describes the main parameters in the command.
Confidential and Proprietary Information of ZTE CORPORATION
29
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 13 PARAMETERS IN THE ADD UNIT COMMAND Parameter Name
Parameter Description
Instruction It is a mandatory parameter, with a format of RACK-SHELF-SLOT
LOC
�
RACK represents the rack number, ranging from 1 to 15. In general, it is configured as 1
�
SHELF represents the shelf number, ranging from 1 to 4
�
SLOT represents the slot number
Location of the unit in the system
MODULE
Module number of the unit
It is a mandatory parameter. Select 1
UNIT
Unit number of the board
It is an optional parameter. Ranging from 1 to 2000.
TYPE
Logic unit type of the board
Select SIPI_NC
Backup mode of the unit
It supports the NO (Without backup) and ONEPLUSONE (One plus one backup) modes. Select it according to the actual networking mode
BKMODE
Example: Add SIPI boards with the following requirements. �
Location: Slots 3 and 4 of shelf 2 in rack 1
�
Unit type: SIPI_NC
�
Backup mode: 1+1 active/standby backup
�
Other parameters: default.
The specific command is as follows. ADD UNIT:LOC="1"-"2"-"3",MODULE=1,UNIT=321,TYPE =SIPI_NC,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=16 383; END OF STEPS Result
After the unit is created successfully, corresponding slots of the rack chart display these SIPI boards.
Creating a USI Unit Prerequisites
30
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
The UIM unit is created.
�
The MML Terminal window is opened.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Context
Perform this procedure to create the USI logic board corresponding to that in the foreground BCTC shelf of MGCF exchange.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a USI unit. The command is ADD UNIT. Table 14 describes the main parameters in the ADD UNIT command. TABLE 14 PARAMETERS IN THE ADD UNIT COMMAND Parameter Name
Parameter Description
Instruction It is a mandatory parameter, with a format of RACK-SHELF-SLOT �
RACK represents the rack number, ranging from 1 to 15. In general, it is configured as 1
�
SHELF represents the shelf number, ranging from 1 to 4
�
SLOT represents the slot number
Location of the unit in the system
LOC
MODULE
Module number of the unit
It is a mandatory parameter. Select 1
UNIT
Unit number of the board
It is an optional parameter. Ranging from 1 to 2000
TYPE
Logic unit type of the board
Select USI_NC
BKMODE
Backup mode of the unit
Select ONEPLUSONE
Example: Create SIPI boards with the following requirements. �
Location: Slots 1 and 2 of shelf 2 in rack 1
�
Unit type: USI_NC
�
Backup mode: 1+1 active/standby backup
�
Other parameters: default.
The specific command is as follows. ADD UNIT:LOC="1"-"2"-"1",MODULE=1,UNIT=121,TYPE =USI_NC,BKMODE=ONEPLUSONE,CLK1=16383,CLK2=163 83; END OF STEPS
Confidential and Proprietary Information of ZTE CORPORATION
31
ZXWN MSCS Data Configuration Guide(MGCF)
Result
After the unit is created successfully, corresponding slots of the rack chart display these USI boards.
Creating an SPB Unit Prerequisites
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
The UIM unit is created.
�
The MML Terminal window is opened.
Context
Perform this procedure to create the SPB logic board corresponding to that in the foreground BCTC shelf of MGCF exchange. SPB board is created only when the narrowband No.7 signaling is used between MGCF and other offices.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an SPB unit. The command is ADD UNIT. Table 15 describes the main parameters in the ADD UNIT command. TABLE 15 PARAMETERS IN THE ADD UNIT COMMAND Parameter Name
Parameter Description
Instruction It is a mandatory parameter and the format is RACK-SHELF-SLOT.
LOC
32
�
The rack No. is within 1~15 and the default value is 1. This parameter is defined by the ADD RACK command.
�
The shelf No. is within 1~4. This parameter is defined by the ADD SHELF command.
�
The slot No. is within 1~17.
Location of the unit in the system
MODULE
Module number of the unit
It is a mandatory parameter. Select 1
UNIT
Unit number of the boar
It is an optional parameter. Ranging from 1 to 2000.
TYPE
Logic unit type of the board
Select it according to the CPU type of this SPB board, for example, SPB2_8260_8260C4
BKMODE
Backup mode of the unit
Select No backup
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Example: Create an SPB board with the following requirements. �
Location: Slot 7 of shelf 2 in rack 1
�
Unit type: SPB_8260_8260C4
�
Backup mode: No backup
�
Other parameters: default.
The command is as follows. ADD UNIT:LOC="1"-"2"-"7",MODULE=1,UNIT=721,TYPE =SPB2_8260_8260C4,BKMODE=NO,CLK1=16383,CLK2=16 383; Example: Create an SPB board with the following requirements. �
Location: Slot 8 of shelf 2 in rack 1
�
Unit type: SPB_8260_8260C4
�
Backup mode: No backup
�
Other parameters: default.
The command is as follows. ADD UNIT:LOC="1"-"2"-"8",MODULE=1,UNIT=821,TYPE =SPB2_8260_8260C4,BKMODE=NO,CLK1=16383,CLK2=16 383; END OF STEPS Result
After the unit is created successfully, corresponding slot of the rack chart display the SPB board.
Creating Background Server Node Prerequisites
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
The corresponding MP module is created.
�
The MML Terminal window is opened.
Context
Perform this procedure to connect the SMP with the billing server. All SMP units should be mapped to the billing server.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create the background server node. The command is ADD SVRINF. Table 16 describes the main parameters in the ADD SVRINF command.
Confidential and Proprietary Information of ZTE CORPORATION
33
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 16 PARAMETER IN THE ADD SVRINF COMMAND Parameter Name
Parameter Description
Instruction
MODULE
Module number of foreground MP
It is a mandatory parameter, ranging from 1 to 127, including all the modules except for module 2
CGMODULE
Module number of billing server
It is an optional parameter, ranging from 130 to 135
Example: Create the billing server node 130 corresponding to the foreground SMP module 3. The specific command is as follows. ADD SVRINF:MODULE=3,CGMODULE=130; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Capacity Configuration Overview Table 17 shows the capacity configuration flow. TABLE 17 CAPACITY CONFIGURATION Steps
Operation
Instruction
Command
1
Configuring the MGCF office capacity
Configure the capacity for each table in the MP module
SET MSCSCAPAC ITY
2
Configuring service data area
Normally select the default value for all parameters
SET DATASIZE
Configuring the MGCF Office Capacity Prerequisites
34
To perform this operation, the following conditions must be met:
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
�
The ID of the exchange to be configured is known.
�
The physical configuration is completed.
�
The MML Terminal window is opened.
Context
This topic describes how to configure the capacity for each table in the MP module. MGCF capacity is configured according to the actual capacity of the equipment. In general, these parameters adopt their default value, except in special cases.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Configure the MGCF office capacity with the command SET MSCSCAPACITY. The parameter description of the command SET MSCSCAPAC ITY is shown in Table 18. TABLE 18 OFFICE CAPACITY CONFIGURATION PARAMETERS Name
Meaning
Range
Default
GCI
Capacity Of GCI Config Table
1~12000
1280
LAI
Capacity Of LAI Config Table
1~1000
64
AOCFEE
Capacity Of Tariff Config Table
1~1000
128
IROAM
Capacity Of IMSI Analysis Config Table
1~3000
1000
PCM
Capacity Of PCM Table
2000~20000
2048
BSC
Capacity Of Config Table
1~128
32
MASK
Capacity Of Black/ White List Number
1~80000
2048
NUMLEN
Capacity Of Number Preanalysis
1~20000
1000
CALLDATA
Capacity Of CFG Relationship Table
1~1024
512
CTRLUNT
Capacity Of Access Network Unit
1~128
64
SIPTRA
Capacity Of SIP Process Data
2000~20000
6000
SIPSTA
Capacity Of SIP Function Adaptor Data
1000~8000
3000
BSC/RNC
Confidential and Proprietary Information of ZTE CORPORATION
35
ZXWN MSCS Data Configuration Guide(MGCF)
Name
Meaning
SIPRES
Capacity Of SIP Call Resources
1000~8000
2500
HRBTMS
Capacity Of Home Ring Back Tone
1~80000
1
SSP
Capacity Of Special Service Phone Group
1~60000
1024
USER
Capacity Of Users Undercontrol
1~80000
4000
TIDTRUNK
Capacity Of Trunk Link
1~1024
512
MDNAL
Capacity Of Mobile NumAnalysis Config
1~65535
8192
DNAL
Capacity Of Num-Analysis Config
1~100000
8192
MPDFT
Capacity Of Default PerDef Timer(MP)
2000~10000
2000
MPDEF
Capacity Of Defined PreDef Timer(MP)
2000~15000
2000
PPDFT
Capacity Of Default PreDef Timer(PP)
2000~10000
2000
PPDEF
Capacity Of Defined PreDef Timer(PP)
2000~10000
2000
LIMITMS
Capacity Of Limit Cheating Subscriber
0~60000
0
DNHOME
Capacity Home
1~400000
150000
LINK
Capacity Of Link
1920~5000
1920
GT
Capacity Of GT
20001~50000
20000
SPC
Capacity Of SPC
1~2000
2000
VMSC
Capacity Of VMSC Table
16~256
16
SAI
Capacity Of SAI Config Table
1~12000
1280
MGW
Capacity Of MGW
1~128
32
ANANACAPACITY
Capacity Of Announcement User Analyzer
1~65535
1024
TID
Of
Range
And
Number
Default
For example, configure the MGCF office capacity. Select the default value for all parameters. The command is as follows:
36
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
SET MSCSCAPACITY; END OF STEPS Result Postrequisite
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane. 1. Configure the OMP startup parameters through a serial port. 2. Synchronize the capacity planning table to the foreground. 3. Restart OMP and the realted MP boards. 4. Synchronize all the tables to the foreground again.
Note: It is required to synchronize the office capacity table to the foreground twice. After the first synchronization, wait 5~10 minutes for the OMP to complete the disk saving, and then restart the OMP. When the OMP starts successfully, it is required to synchronize the capacity tables to the OMP again. After the first synchronization, only the space of the capacity table on the OMP is established, but the table contents are not added. After the second synchronization, the table contents are synchronization.
Configuring Service Data Area Prerequisites
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
The physical configuration is completed.
�
The MML Terminal window is opened.
Context
Perform this procedure to configure the service data area. Generally, it adopts the default value, except in special cases.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Configure the service data area. The command is SET DATA SIZE. Table 19 shows the description of main parameters in the SET DATASIZE command.
Confidential and Proprietary Information of ZTE CORPORATION
37
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 19 PARAMETERS IN THE SET DATASIZE COMMAND Parameter Name
Parameter Description
Instruction
CMODEL
One-MSC multi-MGW call model, including AMONLY(Associated Mode Only) and QAMALLOW(Quasi-associated Mode Allowed)
Select QMALLOW when a call needs three MGWs under the MSCS to provide bearers. Otherwise, select AMONLY
Number of BCBM data areas
Configure it as 10 when the MSCS is associated with one MGW to conform a network, or in a full IP networking mode. Configure it as 3600 when the end office adopts the multi-call model. Configure it as 12400 when the tandem office and gateway office adopt the multi-call model.
DSTCDNUM
Number of destination codes
Type an integer ranging from 1 to 10000, which is associated with the destination-code traffic-statistics in the performance statistics.
CTSTNUM
Maximum number of mixed flow of traffic
Integer numbers ranging from 100 to 11000
CTSTINDEXS IZE
CTST index size (KB)
Integer numbers ranging from 16 to 4096
VMSCNO7 NUM
Number of VMSC/OMP module NO7 call data area
Integer numbers ranging from 2000 to 10000
CMPNO7NUM
Number of CMP module NO7 call data area
Integer numbers ranging from 10000 to 30000
BCBMNUM
Example: Configure a service data area. The MGCF is associated with an MGW. The number of destination codes is 4096. Other parameters adopt the default value. The specific command is as follows. SET DATASIZE:CMODEL=AMONLY,BCBMNUM=10,DSTCD NUM=4096; END OF STEPS Result
38
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Version Loading All physical boards need the software to support the running. If the same physical board is loaded with different running software, it will be with different functions. At first, the physical board is not loaded with the software supporting the running, so it is required to load it by manual. The version files of the OMP module are obtained from the OMC server via FTP. For the version files of other boards (including RPU), they are obtained from OMP during the restart. The steps to load the version files are as follows: �
Load the version files that are needed by the board from the configured version file directory to the version database of the OMC server.
�
Add the version files in the version database into the foreground OMP.
�
Add the corresponding records into the database table related to the version files, so the other boards could obtain the version files from OMP according to these records.
�
During restarting the board, compare the existing version files with the old version files on OMP and check whether they are consistent. If they are the same, adopt the old version fiels; otherwise, download the new version files from OMP.
Confidential and Proprietary Information of ZTE CORPORATION
39
ZXWN MSCS Data Configuration Guide(MGCF)
Overview Configuration Flow
Figure 12 shows the loading flow of a board version files. FIGURE 12 FLOW OF LOADING VERSION FILES
Flow Description
40
Steps
Operations
Instructions
1
Creating the version file directory
Make sure the version number and path of the version files to be loaded.
2
Creating OMP boot files
Generate the ompcfgX.ini (X is the ID of corresponded exchange) boot file on the OMM server. OMP board loads its version files according to this file.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Steps
Operations
Instructions
3
Configuring the OMP startup parameters via serial port
Configures some parameter information for OMP board to communicate with OMM server during startup.
Configuring OMP global data
After OMP board is started, the OMP global data should be configured to make sure that the foreground/background IP addresses are in the same network section.
5
Synchronizing all tables
After the data configuration is completed, the configuration data stored on the OMM server are synchronized to the foreground for foreground NEs to get the configuration data from the OMM server.
6
Loading version files
Manually loads the version files required for board running.
4
Creating Version File Directory Prerequisites
Before the operation, it is required to confirm: �
The version file has been prepared.
�
The physical configuration and the capacity configuration are completed.
�
The MML Terminal window is opened.
Context
Perform this procedure to create the version ID and version path of the version file to be loaded.
Steps
1. On the NetNumen M30 window, select menus Views > Professional Maintenance to enter the Professional Maintenance window. 2. In the left pane, double-click the exchange node in the Professional Maintenance tree. Select Version Management > Version Mainenance to show the Version Maintenance tab in the right pane, as shown inFigure 13.
Confidential and Proprietary Information of ZTE CORPORATION
41
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 13 VERSION LOADING
3. On the Load Version tab, Click the button on the sub-toolbar to pop up the Config Version Path tab, as shown in Figure 14. FIGURE 14 CONFIGURING VERSION PATH
4. Right-click the list on the Config Version Path tab, and select Create from the short-cut menu. A new blank entry is created on the Config Version Path tab, as show in Figure 15.
42
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
FIGURE 15 ADDING NEW BLANK ENTRY
5. Double-click the Version Name on the tab, and type the version name (the version name format is V0.00.00.B0, in which, 0 indicates digital and B indicates character), which should be consistent with the version name of the version file, as show in Figure 16. FIGURE 16 CONFIGURING VERSION NAME
Confidential and Proprietary Information of ZTE CORPORATION
43
ZXWN MSCS Data Configuration Guide(MGCF)
6. On the Config Version Path tab, double-click the blank entry in the File Path column. The button appears. 7. Click the button and then the OPEN dialog will pop up. Select the save path for the version file, the version file path appears in the File Path entry, as shown in Figure 17. FIGURE 17 VERSION FILE PATH
8. After setting the path, it is required to save the setting. On the Config Version Path tab, right click any item and then select the Save button. After the successful saving, the Save Successfully dialog appears. Click the OK button. END OF STEPS Result
The correct Version Name and File Path appears on the the Version Maintenance tab.
Creating OMP Boot Files Prerequisites
Context
Before the operation, it is required to confirm: �
Version file directory is configured.
�
The MML Terminal window is opened.
To create an OMP boot file is to generate an ompcfgX.ini boot file on the OMM server, of which the “X” is the number of the corresponding exchange. This file contains the file names of CPU and FPGA required for normal running of OMP module. The CPU files and the FPGA files required by OMP are listed in Table 20.
44
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
TABLE 20 VERSION DESCRIPTION OF OMP BOOT FILE OMP CPU Type
Version Type
Version File Name
CPU
MSCS_MPX86_MP_X86_CS_Z_T. BIN
FPGA
MPX86_05_040202_FPGA_105. RBF
CPU
MSCS_MPX86_2_MP_P4_CS_Z_ T.BIN
FPGA
MPX862_04_040704_FPGA_109. RBF
MPX86
CENTRINO
Steps
1. On the NetNumen M30 window, select menus Views > Professional Maintenance to enter the Professional Maintenance window. 2. In the left pane, double-click the exchange node in the Professional Maintenance tree. Select Version Management > Version Mainenance to show the Version Mainenance tab in the right pane, as shown in Figure 18. FIGURE 18 LOAD VERSION
3. On the Version Mainenance tab, select the version name from the pull-down list of the Version, as shown in Figure 19.
Confidential and Proprietary Information of ZTE CORPORATION
45
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 19 VERSION LIST
4. On the Version Mainenance tab, press the CTRL key while selecting the CPU file and FPGA file required by the OMP, which are listed in Table 20. Right-click the selected version files, and then select Create OMP Ini File from the shortcut menu, as shown in Figure 20. FIGURE 20 CREATING OMP BOOT FILES
5. After the OMP boot file is created successfully, the message area prompts that OMP boot files are created successfully, click OK, as show in Figure 21.
46
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
FIGURE 21 SUCCESSFUL INFOMATION
END OF STEPS Result
The boot file and version file appear in directory \zxwomcs\umssvr on the OMM server.
Configuring OMP Running Parameters via Serial Port Prerequisites
Before the operation, it is required to confirm: �
The serial cable has been prepared.
�
The OMP boot file has been created.
�
The hyper-terminal has been installed on the computer.
Context
Perform this procedure to configure some parameters, including OMM address, OMC server address, office ID, FTP user name/password and startup mode. These parameters are required by OMP board to communicate with the OMM server during startup.
Steps
1. Connect one end of RS232 serial cable to serial port of debugging computer, another end to debug port of OMP backboard. 2. On the debugging computer, click Start > Programs > Accessories > Communications > Hyper Terminal in the Windows OS, as shown in Figure 22.
Confidential and Proprietary Information of ZTE CORPORATION
47
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 22 CONNECTION DESCRIPTION
3. After click OK, the following figure pops up. Select the serial port connected to the foreground and then click OK, as shown in Figure 23. FIGURE 23 CONNECT TO DIALOG BOX
4. On the COM1 dialog box, click the Restore Defaults button, and then click OK, as shown in Figure 24
48
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
FIGURE 24 COM1 PROPERTIES
5. After entering the hyper-terminal, if there is no words, restart the OMP board. When the Press any key to stop auto-boot... prompt appears after entering hyper-terminal, press any key instantly to stop automatic booting and then to configure the OMP parameters, as shown in Figure 25. FIGURE 25 PRESS ANY KEY TO STOP AUTO-BOOT
6. If the Boot Password (3GPLAT or 3gplat) appears, as shown in Figure 26, type the password 3gplat and press Enter.
Confidential and Proprietary Information of ZTE CORPORATION
49
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 26 BOOT PASSWORD
7. When the 3GPlat Boot appears, type 1 to select Config MPnet parameters (only for Omp and Cmp), and then press Enter, as shown in Figure 27. FIGURE 27 3GPLAT BOOT
8. Open the Config selection window, type 1 to select Set Omp (or Cmp)’s Omc IP.MAC.Gateway IP, and then press Enter, as shown in Figure 28.
50
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
FIGURE 28 CONFIG SELECTION
9. Enter the OMP’s OMC Ip Address window, and type the IP address 192.168.X.1 in which, the X indicates the office direction ID of the office, and then Press Enter, as shown in Figure 29. FIGURE 29 ENTER OMP’S OMC IP ADDRESS
10. Enter the Enter OMP’s OMC Mac address window, type the hardware address 00.208.208.161.00.X planned by OMP, in which, the X indicates the office ID of the office, as shown in Figure 30. Press Enter.
Confidential and Proprietary Information of ZTE CORPORATION
51
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 30 ENTER OMP’S OMM MAC ADDRESS
11. Enter the Enter OMP’s Gateway Ip address window, type the network gateway IP address of the OMM server, or press Enter to skip this configuration, as shown in Figure 31. FIGURE 31 ENTER OMP’S GATEWAY IP ADDRESS
12. Enter the Enter OMC Server IP Address address window, type the IP address of the OMM server, and press Enter, or press Enter directly to skip this configuration, as shown in Figure 32.
52
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
FIGURE 32 OMC SERVER IP ADDRESS
13. Enter the Config selection window, type 2, and then press Enter, as shown in Figure 33. FIGURE 33 CONFIG SELECTION
14. Enter the Enter OMC IP Address window, type the IP address of the OMM server, and then press Enter, as shown in Figure 34.
Confidential and Proprietary Information of ZTE CORPORATION
53
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 34 OMM IP ADDRESS
15. Enter the Enter OMC FTPSVR User Name window, type the default FTP name uep, and then press Enter. Then the Enter OMC FTPSVR User Password window will pop up, type the default FTP password uep and press Enter, as shown in Figure 35. FIGURE 35 FTP CONFIG
16. Enter the Enter OMC FTPSVR File Path window, press Enter to skip this configuration, and then enter the boot file configuration window. 17. Type the boot file name ompcfgX.ini, in which, the X indicates the office direction ID of this office, then press Enter, as shown in Figure 36.
54
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
FIGURE 36 OMPCFG FILE
18. Enter the Config selection window and type 3, as shown in Figure 37. FIGURE 37 CONFIG SELECTION
19. Enter the Set OMP Boot Type window, type 0 and then press Enter, as shown in Figure 38.
Confidential and Proprietary Information of ZTE CORPORATION
55
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 38 OMP BOOT TYPE
20. Enter the Config selection window and then type 4, as shown in Figure 39. FIGURE 39 CONFIG SELECTION
21. Enter the Enter Bureau No. window, type the office direction ID, and then press Enter, as shown in Figure 40.
56
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
FIGURE 40 BUREAU NO.
22. Enter the Config selection window and then type 5, as shown in Figure 41. FIGURE 41 CONFIG SELECTION
23. Enter the 3GPlat Boot configuration window, type 0 and then press Enter, as shown in Figure 42.
Confidential and Proprietary Information of ZTE CORPORATION
57
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 42 3GPLAT BOOT
END OF STEPS Result
When the OMP starts up automatically, it will download the version file and the FPGA file from the OMM server. The OMP board runs normally, and the RUN indicator on the OMP board flashes slowly.
Configuring OMP Global Data Prerequisites
Before the operation, it is required to confirm: �
The OMM server and the local maintenance terminal are installed correctly.
�
OMP startup parameters are configured.
�
The MML Terminal window is opened.
Context
After OMP board is started, the OMP global data should be configured to make sure that the foreground/background IP addresses are in the same network section. For example, the IP of the OMM server is 192.4.1.1, and the IP of the foreground is 192.168.79.1. In order to ensure that the IP address of the foreground and that of the background are in the same network section, it is required to set the MASK as 255.0.0.0.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Set the global data OMP configuration, the command is SET OMP. Table 21 describes the parameters in this command SET OMP.
58
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
TABLE 21 PARAMETERS IN THE SET OMP COMMAND Name
Meaning
Instructions
OMPIP
OMP background IP address
It indicates the valid IP address. Enter it according to the actual conditions. The background can access the OMP through this IP address
MASK
OMP background IP mask
Configure the address range of OMP. Types it according to the real condition
GATEWAY
OMP to OMM gateway
If there is no gateway, it can be the sub-network address of OMMSERVER
OMCIP
OMC server sub network
It indicates the valid IP address. Enter it according to the actual conditions
Example: Configure the global data OMP information with the following requirements. �
OMP IP address: 192.168.4.1
�
OMP subnet address to the background IP: 255.255.0.0
�
Gateway IP address: 192.168.1.1
�
OMM server IP address: 192.168.79.1
The command is as follows: SET OMP:OMPIP=192.168.4.1 MASK=255.255.0.0, GATE WAY=192.168.1.1, OMCIP=192.168.79.1; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Synchronizing All Tables Prerequisites
Before the operation, it is required to confirm: �
The OMM server and the local maintenance terminal are installed correctly.
�
The MML Terminal window is opened.
Context
To synchronize the data is to send the data saved in the OMM server to the foreground so that the foreground network element can obtain the data from the OMM server. Only the admin subscriber can synchronize all the tables.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11;
Confidential and Proprietary Information of ZTE CORPORATION
59
ZXWN MSCS Data Configuration Guide(MGCF)
2. Synchronize all the tables. The command is SYNA. Table 22 describes the parameters in this command SYNA. TABLE 22 PARAMETERS IN THE SYNA COMMAND Parameter
Explanation
Instruction
USERNAME
User Name
It is an optional parameter for designating the name of the user whose data are transferred, with a length ranging from 0 to 50 characters. If it is left blank, the table data of admin's own are transferred.
STYPE
Transmission type
Select ALL
It is an optional parameter for designating the module(s) to be transferred.
MODULES
Module list
Up to 127 modules can be selected, which is represented by a decimal numeral, and separated with & (for example, MODULES=1&3&4). Empty string indicates all modules. It is an optional parameter, with a default of 600. Adjust this duration according to the actual requirements. Set a longer timeout duration when the data are large, otherwise, timeout failure may occur
TIMEOUT
Response timeout (100ms)
SAVE
Save when completed
It is an optional parameter. Usually the default value YES is selected.
TOSLAVE
Sync to slave when completed
It is an optional parameter. In general, the default value YES is selected.
Example: Admin synchronization data synchronizes all the tables. The command is as follows. SYNA:STYPE=ALL,TIMEOUT=600,SAVE=YES,TOSLAVE=Y ES; END OF STEPS Result
60
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Postrequisite
It is required to restart the OMP board.
Note: It is required to resynchronize the data for three times and restart the OMP board for two times. Before the restart, it is required to confirm whether the synchronized table is saved. The save operation may take three to five minutes. Two methods are available. �
Check the disk saving status of the foreground on the OMM client.
�
Check whether the usage ratio of the foreground CPU is about 3% with the GetCpu command.
Checking Operations 1. Select Start > Run, then the Run dialog box will pop up. 2. Type CMD and then press Enter to enter the CMD dialog box. 3. Type telnet 192.168.X.1, in which, the X indicates the office direction ID, and then press Enter. 4. Type the user name zte and the password zte, and then press Enter for two times, as shown in Figure 43. FIGURE 43 USER NAME AND PASSWORD
5. Type SCSSHowMcmInfo to check the status of the board and then press Enter, as shown in Figure 44.
Confidential and Proprietary Information of ZTE CORPORATION
61
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 44 STATUS
The printed status of the board is MASTER and Work, which means that the OMP board runs normally.
Loading Version Files Prerequisites
Context
Before the operation, it is required to confirm: �
All the tables are synchronized.
�
The version files of each board are ready.
�
The foreground and background are correctly connected.
A physical board initially does not load its version files, so you need to load them manually. Table 23 lists the board version files. TABLE 23 BOARD VERSION FILES Physical Board Type
Logical Board Type
Version Type
MPX86_2
RPU
MPX86_2
UIM_2
MNIC_2
Version File Name
Instructions
CPU
MSCS_MPX86_2_RPU _P4_CS_Z_T.BIN
Version file of RPU
MP
CPU
MSCS_MPX86_2_MP_ P4_CS_Z_T.BIN
Version file of SMP
UIM
CPU
MSCS_UIM_2_UIM_75 5_CS_Z_T.BIN
Version file of UIMC
CPU
MSCS_MNIC_2_SIG_I PI_23XX_CS_Z_T.BIN
SIPI MICROCODE
62
UC_MSCSERVER_MNI C__2_SIG_IPI_CS__T. UOF
Confidential and Proprietary Information of ZTE CORPORATION
Version file of SIPI
Chapter 2 Local Office Data Configuration
Physical Board Type SPB_2
MNIC_2
CHUB
CLKG
Steps
Logical Board Type
Version Type
SPB
Version File Name
Instructions
CPU
MSCS_SPB_2_SPB_82 60_CS_Z_T.BIN
Version file of SPB
CPU
MSCS_MNIC_2_USI_2 3XX_CS_Z_T.BIN
USI
CHUB
-
Version file of USI
MICROCODE
UC_MSCSERVER_MNI C_2_USI_CS__T.UOF
CPU
MSCS_CHUB_CHUB_8 245_CS_Z_T.BIN
Version file of CHUB
-
It is not required to load the version files
-
1. On the NetNumen(TM) M30 MSCS/MGW window, select Views > Professional Maintenance to enter the Professional Maintenance window. 2. In the left pane, double-click the exchange node in the Professional Maintenance tree. Select Version Management > Version Mainenance to show the Version Mainenance tab in the right pane, as shown in Figure 45. FIGURE 45 VERSION MAINENANCE
3. On the Version Mainenance tab, select the version name from the Version pull-down list, as shown in Figure 46.
Confidential and Proprietary Information of ZTE CORPORATION
63
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 46 VERSION LIST
4. On the Version Maintenance tab, press down the CTRL key, and select all the version files (the version files required by each board are shown in Table 23) required by the foreground board, as shown in Figure 47. FIGURE 47 BATCH VERSION LOADING BY DEFAULT
5. Right click the selected version files and select the shortcut menu Batch Load Default Version. The Switch Process
64
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
window will pop up, which displays the process of the version file (that is the multicast process). END OF STEPS Result
Postrequisite
After the version loading is completed, the board will restart. The board compares its version files, and obtains its required version files. After the version files are loaded, the board is in normal running status. The RUN indicator on the front panel of the board will flash at 1 Hz. It is required to synchronize the data. Verifications 1. Judge whether the board runs normally through the indicators on the panel. Table 24 lists the indicator statuses of each board. TABLE 24 BOARD INDICATOR STATUSES Name
RUN
ACT
ALM
Color
Meanings
Green
RUN indicator
Green
Active/ standby indicator
Red
Alarm indicator
Instruction Flashing at 5 Hz: the board is being powered on. Flashing at 1 Hz: the board is running normally. On: The board is active Off: The board is standby On: The board gives an alarm. Off: The board gives no alarm.
Remarks
When all the indicators on the board are ON, probably the board hardware is faulty, the board data is not configured, or the boot file of the does not match the version files.
2. On the Version Query tab, check whether the version file number of the board is correct, thus to verify whether the version files are loaded correctly.
Creating MGCF Tones in Batches Prerequisites
Before the operation, it is required to confirm: �
The tone scripts are loaded.
�
The MML Terminal window is opened.
Confidential and Proprietary Information of ZTE CORPORATION
65
ZXWN MSCS Data Configuration Guide(MGCF)
Context
Perform this procedure to create the tone-related data on the MGCF side in batches, including tone ID, service key and its relation to tone ID and other tone packet configuration. All the tone packet configurations are created in batches, except interconnection conversion of external service keys that is configured manually with the ADD SVRTRANSKEY command.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create MGCF tones in batches. STONE.
The command is BADD
Table 25 describes main parameters in the BADD STONE command. TABLE 25 PARAMETERS IN THE BADD STONE COMMAND Parameter Name
Parameter Description
Instruction
Voice type, includes
TYPE
�
ALL: All configuration of tone
�
ICP: tone service
�
KD: the relationship between the call type and the KD
�
LANGDES: language description string
�
MSGID: external MSGID, relation to inter service key
�
TONEID: the service tone ID to the protocol package
�
TONEIN: service key and its relation to tone ID
�
TONEPLAYMT: the method of playing tones
In general, the ALL option is selected, indicating that all the tone types are created in batches.
Example: Create the batch processing of all the MGCF tones. The specific command is as follows. BADD STONE:TYPE=ALL; END OF STEPS Result
66
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Office Information Configuration Overview Table 26 shows the office information configuration flow. TABLE 26 OFFICE INFORMATION CONFIGURATION Steps
1
2
Topic
Instructions
Command
Creating local signaling point
The local SPC configuration includes 14-bit SPC configuration, 24-bit SPC configuration and the upper-layer user configuration of MTP3.
ADD OPC
Creating the local office configuration
Configure some parameters of the local exchange, including the exchange type, signaling point type, MTP3 test code, and other parameters.
ADD LOFC
Creating Local Office Signaling Point Prerequisites
Before the operation, it is required to confirm: �
You know the ID of the exchange to be configured.
�
You know the 14-bit SPC, 24-bit SPC, and the local toll area code.
�
The MML Terminal window is opened.
Context
Signaling Point Code (SPC) is a unique code for identifying each node in the signaling network. The local SPC configuration includes 14-bit SPC configuration, 24-bit SPC configuration and the upperlayer user configuration of MTP3. If the multi-SPC networking is adopted, it is required to create multiple local signaling points with different network types.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree.
Confidential and Proprietary Information of ZTE CORPORATION
67
ZXWN MSCS Data Configuration Guide(MGCF)
SET:NEID=11; 2. Create the local office signaling point. The command is ADD OPC. Table 27 describes the main parameters in the ADD OPC command. TABLE 27 PARAMETERS IN THE ADD OPC COMMAND Parameter Name
Parameter Description
Instruction
NET
The signaling network where the local office runs, which has the same signaling network type of the adjacent office configured later.
It is a mandatory parameter. It ranges from 1 to 8. In general, 1 is selected.
NAME
User-defined alias
It is a mandatory parameter, with a length ranging from 1 to 50 characters.
RC
The toll zone code of the place where the local office is located
It is an optional parameter. Do not add 0 ahead of an area code
SPCFMT
Signaling point code format
It is an optional parameter. By default, select TRIPLE_DEC, which is a three-section decimal number in 888/383 format.
OPC14
14-bit SPC of local office, which is provided by the operator
OPC24
24-bit SPC of local office, which is provided by the operator
PREFIX
Dialing prefix
Toll dialing prefix. It is 0 for China.
Protocols supported by local office
Select the application types of this signaling point, not unrelated subscribers. According to different network types, Select H248 User for Mn Interface, select BICC User, TUP User, ISUP User for inter-office signaling point code.
APPTYPE
68
It is configured according to the signaling point planning.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Parameter Name
NETAPP
INFO
Parameter Description
Instruction
Network appearance used in M3UA layer
This field is not used when the local office is interconnected with a TDM office. It is configured as 0. When this signaling point is interconnected with an IP signaling point with the same network type, you need to negotiate this field with the opposite end for consistency.
Identification field used to configure whether the network appearance is effective. Three modes can be chosen, including NOUSE, NETAPP and NONETAPP.
When NOUSE is chosen, if the NETAPP field is 0, the network appearance is ineffective; if the NETAPP field is not 0, the network appearance is effective. When NETAPP is chosen, the network appearance is effective. When NONETAPP is chosen, the network appearance is ineffective.
TAG
Other attributes
Configure whether the network corresponding to the office has the ISNI function and translation node.
Example: Create a 24-bit signaling point with the following requirements. �
Direct-associated office: MSCS, CSCF, BGCF
�
Signaling point type: 24-bit signaling point
�
SPC: 3.11.1
�
Application type: ISUP, SCCP, BICC, and TUP
�
Alias: NET1.
�
Other parameters: default.
The specific command is as follows. ADD OPC:NET=1,NAME="NET1",SPCFMT=TRIPLE_DEC,O PC24="3.11.1",APPTYPE="BICC"&"ISUP"&"SCCP"&"TUP",R C="25",PREFIX="0",NETAPP=0,INFO=NONETAPP,DMIDX =0; Example: Add a 14-bit signaling point that is interconnected with IM-MGW through Mn interface with the following requirements. �
SPC: 1.11.1
Confidential and Proprietary Information of ZTE CORPORATION
69
ZXWN MSCS Data Configuration Guide(MGCF)
�
Application type: H.248
�
Alias: NET2
�
Other parameters: default.
The specific command is as follows. ADD OPC:NET=2,NAME="NET2",SPCFMT=TRIPLE_DEC,OP C14="1.11.1",APPTYPE="H.248",RC="25",PREFIX="0",NE TAPP=0,INFO=NONETAPP,DMIDX=0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating Local Office Configuration Prerequisites
Before the operation, it is required to confirm: �
The local office signaling point is created.
�
You know the ID of the exchange to be configured.
�
The MML Terminal window is opened.
Context
Perform this procedure to configure some parameters of the local exchange, including the exchange type, signaling point type and other parameters.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create the local office configuration. The command is ADD LOFC. Table 28 describes the parameters in the ADD LOFC command. TABLE 28 PARAMETERS IN THE ADD LOFC COMMAND Parameter Name
Parameter Description Local office type, including �
LOCAL (Local Exchange)
It is a mandatory parameter. Several options can be selected.
�
DOMTOLL (National Toll Exchange)
Configure this parameter according to actual type.
�
INTTOLL (International Toll Exchange)
�
OA (In One Area)
In general, select Local Exchange, National Toll Exchange and MGCF Exchange when MSCS serves as MGCF.
�
UM (User Telephone)
OFFTYPE
70
Instruction
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 Local Office Data Configuration
Parameter Name
Parameter Description �
R2NAT (R2 National Exchange)
�
R2INT (R2 International Exchange)
�
MGCF (MGCF Exchange)
Instruction
Network type
It is a mandatory parameter for designating the network type ID of the local office. In this case, one network type is configured.
Sequence in area
It is a mandatory parameter with a default of 0, ranging from 0 to 255.
TCODE
Test code
It is an optional character-type parameter with a length not more than 15 characters. This parameter can contain 0~9, *, and #, with a default of 1234
SPTYPE
Signaling point type, including SEP, STP, and STEP
NET
SEQ
RESTART
Signaling point restart
It is an optional parameter. Select STEP It is an optional parameter, with a default of YES. The default value indicates that this function is enabled
Languages of the office, including:
LANG
�
DEFAULT
�
FRENCH
�
ENGLISH
�
GERMAN
�
RUSSIAN
�
SPAISH
The default value is DEFAULT.
Confidential and Proprietary Information of ZTE CORPORATION
71
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
RSTTIME
Reset Time(ms)
The restart time when the signaling point used as STIP (the unit is ms). It is an integral parameter, ranging from 100 to 59900, the default value is 10000.
NAME
Alias
Not more than 50 characters. It is the name customized by a user for easy memory.
Example: Configure the local exchange with the following requirements. �
Office type: LOCAL&DOMTOLL&MGCF
�
Network type No.: 1
�
Signaling point type: STEP
�
Other parameters: Default.
The command is as follows: ADD LOFC:OFCTYPE="LOCAL"&"DOMTOLL"&"MGCF",NET =1,SEQ=0,TCODE="1234",SPTYPE=STEP,LANG=DEFAUL T,RESTART=YES,RSTTIME=10000,T19=68,T20=60,T21 =64; END OF STEPS Result
72
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter
3
Resource Configuration Table of Contents Resource Planning .............................................................73 Configuring Resource Attributes...........................................73
Resource Planning It is very important to make the overall resource planning in advance no matter whether common networking, region-system networking, or dual-homing networking is adopted. The basic principle of resource allocation is as follows: 1. Do not add unused resources in the resource management system. For example, if it is not required to configure the “SIP called number analysis selector”, do not configure the corresponding resources. 2. Allocate the required resources on a basis of sections to avoid too separate resource allocation. For example, when the “Office ID” resource is allocated to 5 areas, each area is allocated with 100*N adjacent office IDs. Each section has 100 adjacent office IDs, and N can be different in different areas. 3. Add moderate surpluses for required resources, and do not use up them. For example, if the “Office ID” resource is allocated to 5 areas, do not allocate all 2048 adjacent office IDs, except that each area really has 400 adjacent offices to be configured. If the “Office ID” resource in one area is insufficient after a period of time, separately allocate one section of (100) adjacent office IDs to this area.
Configuring Resource Attributes Prerequisites
Before the operation, it is required to confirm:
Confidential and Proprietary Information of ZTE CORPORATION
73
ZXWN MSCS Data Configuration Guide(MGCF)
Context
�
The overall resource planning is made.
�
The MML Terminal window is opened.
The MGCF has authority-division and area-division function, so it is required to allocate different resource attributes for different areas before configuring the data. If the area is not divided, all the resource attributes can be configured in the common area. Table 29 lists the resource types, key fields and value ranges in the MGCF resource management system. TABLE 29 RESOURCE TYPES, KEY FIELDS AND VALUE RANGES OF THE MGCF Configuration Items
Resource Types
Key Fields
Minimum
Maximum
Office data configuration
Adjacent office
Office ID
1
3000
Signaling linkset
Link set No.
1
1024
Signaling route
Signaling route No.
1
2000
SCTP
SCTP ID
1
2048
ASP
ASP ID
1
2048
AS
AS ID
1
640
M3UA static route
M3UA static route ID
1
640
Node Topology Config
Topology node ID.
1
2048
Voice Codec Template
Template ID
1
255
Trunk group
Trunk group number
1
4000
Outgoing route
Route No.
1
20000
Outgoing route set
Route set No.
1
3000
Outgoing route chain
Route chain ID
1
3000
Chain analysis
Chain analysis index
1
3000
Protocol configuration
Topology configuration
Trunk routing configuration
74
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Resource Configuration
Configuration Items
Number analysis
Access configuration
Service configuration
Steps
Resource Types
Key Fields
Minimum
Maximum
Automatic Re-routing Route Set
Re-routing route set
1
1000
Number Pre-analysis Selector
Number Preanalysis Selector
1
1000
Number Analysis Entrance
Number Analysis Entrance
1
1000
Number Analysis Selector
Number Analysis Selector
1
4096
Template of Number Analysis Selector
Template of Number Analysis Selector
1
65535
Number Transform Index
Number Transform Index
1
2048
Black White List Selector
Black White List Selector
1
1000
SIP Called Number Analysis Selector
Selector
1
1000
Location Area
Location Area ID
1
65534
Emergency Call Center Index
Emergency call center index
1
255
Welcome Messages
Welcome Message Code
1
128
Camel Access Subscription Information
Camel Information Index Number
1
255
1. On the NetNumen (TM) M30 window, select menus Views > Resource Management, and the Resource Management window appears, as shown in Figure 48 .
Confidential and Proprietary Information of ZTE CORPORATION
75
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 48 AREA TREE
2. In Area Tree, right click the area where resources need to be added under the MSCS. Click the shortcut menu Add resource, as shown in Figure 49. FIGURE 49 ADDING RESOURCES
3. The Add Resource dialog box appears, as shown in Figure 50. The parameter description is shown in Table 29.
76
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 3 Resource Configuration
FIGURE 50 RESOURCE ADDING DIALOG BOX
4. Select the resource type to be added from the field Resource Type drop-down list box, and input the corresponding parameters. Click the Add button, and the added resource is displayed in the resource list. 5. After all kinds of required resource types are configured, click the Confirm button to exit the resource configuration. END OF STEPS Result
Resource types display on the Resource Management window.
Confidential and Proprietary Information of ZTE CORPORATION
77
ZXWN MSCS Data Configuration Guide(MGCF)
This page is intentionally blank.
78
Confidential and Proprietary Information of ZTE CORPORATION
Chapter
4
MGCF-IM-MGW Interconnection Data Configuration Table of Contents Overview..........................................................................79 Interface IP Address Configuration .......................................81 BFD Configuration (Optional) ..............................................87 Creating a Static Route ......................................................90 Adjacent Office and Topology Configuration ...........................92 SIGTRAN Configuration .................................................... 106 H.248 Configuration......................................................... 119
Overview Description
Mn interface is the interface between MGCF and IM-MGW. It usually adopts the IP bearer, and its protocol stack adopts the BICC/M3UA/SCTP/IP mode.
Configuration Flow
Figure 51 shows the flow of configuring the interconnection data between MGCF and IM-MGW.
Confidential and Proprietary Information of ZTE CORPORATION
79
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 51 FLOW OF MGCF-IM-MGW INTERCONNECTION CONFIGURATION
Description
The flow of MGCF-IM-MGW interconnection data is shown in Table 30. TABLE 30 FLOW DESCRIPTION
80
Steps
Operations
Procedures
1
Interface IP address configuration
According to the IP address planning , configure the loopback interface address, SIPI interface address, and USI interface address.
2
BFD configuration (optional)
BFD parameters are configured when load-sharing networking mode is adopted. BFD is not required for active/standby networking mode.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Steps
Operations
Procedures
3
Creating static route
It is configured when the service IP address of local signaling plane and PE interface address are not in the same network section .
4
Adjacent office and topological node configuration
It is to create adjacent office and topological node .
5
SIGTRAN configuration
It is configured when IP bearer is adopted.
6
H.248 configuration
It is only configured for Mn/Mc interface.
Interface IP Address Configuration Overview Interface IP addresses are planned according to the actual networking applications. The IP address of Nc, Mj/Mg interfaces can be configuration independently, or share with the Mn interface address. Table 31 TABLE 31 INTERFACE IP ADDRESS CONFIGURATION Steps
1
2
3
Operations
Instruction
Creating a Loopback Interface
Create the service address on the RPU loopback port.
Creating an SIPI Interface Address
Create IP address to some physical port of this SIPI board
Creating a Virtual Interface Address
Create a virtual interface address. MGCF is interconnected to a SIP office through its virtual interface.
Command INTERFACE LOOPBACK ADD IP ADDRESS
INTERFACE ADD IP ADDRESS
INTERFACE ADD IP ADDRESS
Confidential and Proprietary Information of ZTE CORPORATION
81
ZXWN MSCS Data Configuration Guide(MGCF)
Creating a Loopback Interface Prerequisites
Before the operation, it is required to confirm: �
The RPU module configuration is completed, and the RPU works normally.
�
The MML Terminal window is opened.
Context
Configuring the loopback interface means configuring the service address on the RPU loopback port. Since the service address of Mc interface can use ports 1 and 2, it is recommended that each port is configured with one IP address.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Enter the RPU loop back interface. The command is INTERF ACE LOOPBACK. Port represents the port number, ranging from 1 to 128. Example: Enter the loop-back interface whose port number is 1. The command is as follows. INTERFACE LOOPBACK:PORT=1; 3. Create the loopback interface address. The command is ADD IP ADDRESS. Table 32 describes the main parameters in the ADD IP ADDRESS command. TABLE 32 PARAMETERS IN THE ADD IP ADDRESS COMMAND Parameter Name
Parameter Description
Instruction
IP
IP address
It is a mandatory parameter. The IP address of the loop-back address.
MASK
Mask
It is a mandatory parameter of 32-bit. In general, it is 255.255.255.255.
BROADCASTIP
Broadcast address
It is an optional parameter. In general, it is 255.255.255.255.
Example: Create a loop back address with the following requirements.
82
�
IP address: 192.168.11.11
�
Subnet mask: 255.255.255.255.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
The command is as follows. 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 loss when the RPU is restarted. The command is SAVE ONLINED ATA;. 5. Exit the interface configuration mode. The command is EXIT; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating an SIPI Interface Address Prerequisites
Before the operation, it is required to confirm: �
The SIPI unit is created.
�
The MML Terminal window is opened.
Context
MGCF is interconnected to IM-MGW on the CE through its SIPI board. The online configuration of SIPI board interface is to assign an IP address to some physical port of this SIPI board.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Enter the SIPI board interface configuration mode. The command is INTERFACE. Table 33 describes the main parameters in the INTERFACE command. TABLE 33 INTERFACE REAL INTERFACE Parameter Name
Parameter Description
Instruction
SUBSYSTEM
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 No.
It is a mandatory parameter. It is the unit number of the real interface. Select the unit number of the board corresponded by the interface.
UNIT
Confidential and Proprietary Information of ZTE CORPORATION
83
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
SUNIT
Subunit No
It is a mandatory parameter. Real interface’s sub-unit number fixedly adopts 1.
Port number
It is a mandatory parameter. The port number refers to the network interface serial number of the SIPI rear board for connecting to the external. The four network interfaces are numbered 1 to 4 from top to bottom. Only the first port is used.
PORT
Example: Enter the interface address of SIPI board. The configuration requirements are as follows. �
Unit number: 321
�
Sub-unit number: 1
�
Port number: 1
�
Home module number: No.1 OMP module.
The command is as follows. INTERFACE:SUBSYSTEM=0,MODULE=1,UNIT=321,SUNI T=1,PORT=1; 3. Create the interface address of the SIPI. The command is ADD IP ADDRESS. Table 34 describes the main parameters in the ADD IP ADDR ESS command. TABLE 34 PARAMETERS IN THE ADD IP ADDRESS COMMAND Parameter Name
Parameter Description
Instruction
IP
IP address
It is a mandatory parameter. The Mn interface address of SIPI board
MASK
Subnet mask
It is a mandatory parameter. The real interface subnet address of corresponding interface board
BROADCASTIP
Broadcast address
It is an optional parameter, corresponding to the broadcast address of the real address of the corresponding interface board.
Example: Create the interface address of the SIPI. The configured parameters are as follows. �
IP address: 192.168.1.11
�
Subnet mask: 255.255.255.248
�
Broadcast address: 255.255.255.255.
The command is as follows.
84
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
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 loss when the RPU is restarted. The command is SAVE ONLINED ATA;. 5. Exit the interface configuration mode. The command is EXIT; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a Virtual Interface Address Prerequisites
Before the operation, it is required to confirm: �
Physical configuration of SMP module is completed.
�
The MML Terminal window is opened.
Context
MGCF is interconnected to a SIP office through its virtual interface.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Enter the virtual interface configuration mode. The command is INTERFACE. Table 35 describes the main parameters in the INTERFACE command. TABLE 35 INTERFACE VIRTUAL INTERFACE Parameter Name
Parameter Description
Instruction
SUBSYSTEM
Subsystem ID
It is a mandatory parameter. The changeless value for virtual address is 255.
MODULE
Module No.
It is a mandatory parameter. Select the SMP which processes the IP signaling.
UNIT
Unit No.
It is a mandatory parameter. The changeless value for virtual address is 65535.
SUNIT
Subunit No
It is a mandatory parameter. The changeless value for virtual address is 255.
Confidential and Proprietary Information of ZTE CORPORATION
85
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
PORT
Port number
It is a mandatory parameter. The changeless value for virtual address is 65530.
Example: Enter the vitual interface address. The configuration requirements are as follows. �
Subsystem number: 255
�
Module number: 3
�
Unit number: 65535
�
Sub-unit number: 255
�
Port number: 65530
The command is as follows. INTERFACE:SUBSYSTEM=255,MODULE=3,UNIT=65535,S UNIT=255,PORT=65530; 3. Create a virtual interface address. The command is ADD IP ADDRESS. Table 36 describes the main parameters in the ADD IP ADDRESS command. TABLE 36 PARAMETERS IN THE ADD IP ADDRESS COMMAND Parameter Name
Parameter Description
Instruction
IP
IP address
It is a mandatory parameter. The IP address of the virtual interface address.
MASK
Mask
It is a mandatory parameter of 32-bit. In general, it is 255.255.255.255.
BROADCASTIP
Broadcast address
It is an optional parameter. In general, it is 255.255.255.255.
Example: Create a virtual address with the following requirements. �
IP address: 10.1.44.77
�
Subnet mask: 255.255.255.255.
�
Broadcast address: 255.255.255.255
The command is as follows. ADD IP ADDRESS:IP="10.1.44.77",MASK="255.255.255.2 55",BROADCASTIP="255.255.255.255";
86
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
4. Save the online configured data. Otherwise, these will loss when the RPU is restarted.The command is SAVE ONLINEDA TA;. 5. Exit the interface configuration mode. The command is EXIT; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
BFD Configuration (Optional) Overview Definition
Bidirectional Forwarding Detection (BFD) can greatly accelerate the fault detection speed and enhance the recovery function. Currently, EFD function is mainly used to quickly detect the link status of soft-switching equipment. It can not only find the link fault quickly, but also inform the equipment that initiates this detection to handle this fault.
BFD Function Configuration
In general, BFD function is configured in the load-sharing networking mode. One interface is configured with a BFD session. Steps
1
2
Operation
Instruction
Command
Create a BFD authentication
The BFD authentication entry is configured only when the authentication to the BFD session is required.
ADD BFD AUTH
Create a BFD session
Configure the mapping relationship between the real address of the local SIPI interface board and the router interface.
ADD BFD SESSION
Creating BFD Authentication Prerequisites
Before the operation, it is required to confirm: The MML Terminal window is opened.
Context
The BFD authentication is created only when the authentication to the BFD session is required.
Confidential and Proprietary Information of ZTE CORPORATION
87
ZXWN MSCS Data Configuration Guide(MGCF)
Note: Authentication type and Key of both ends must be consistent. Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create BFD authentication. The command is ADD BFD AUTH. Table 37 describes the parameters in the ADD BFD AUTH command. TABLE 37 PARAMETERS IN THE ADD BFD AUTH COMMAND Parameter Name
Parameter Description
Instruction
AUTHTYPE
Authentication type
It is a mandatory parameter including SIMPLE, MD5, METIC_MD5, SHA1, and METIC_SHA
AUTHKEYID
Authentication ID
It is a mandatory parameter. Type an integer within 1~255.
KEY
KEY
It is a mandatory parameter. Enter it according to different authentication types.
Example: Create BFD authentication with the following requirements. �
Authentication type: SIMPLE
�
Authentication ID: 1
�
KEY: 1.
The command is as follows: ADD BFD AUTH:AUTHTYPE=SIMPLE,AUTHKEYID=1,KEY ="1"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a BFD Session Prerequisites
Before the operation, it is required to confirm: The MML Terminal window is opened.
88
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Context
Perform this procedure to configure the mapping relationship between the real address of the local SIPI interface board and the router interface.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create BFD session. The command is ADD BFD SESSION. Table 38 describes the parameters in the ADD BFD SESSION command. TABLE 38 PARAMETERS IN THE ADD BFD SESSION COMMAND Parameter Name
Parameter Description
Instruction
SRCIP
Local address of BFD session
It is a mandatory parameter. Types the interface address of SIPI.
DSTIP
Remote address of BFD session
It is a mandatory parameter. Types the address of the corresponding router
Multi hop flag
It is a mandatory parameter. Includes SINGLE_HOP and MULTIHOP. In general, select SINGLE_HOP
MULTIHOP
DESMINTXINTVAL
Min-transmit interval (ms)
REQMINRXINTVAL
Min-receive interval (ms)
DETECTMULT
Detect accumulator
It is an optional parameter, ranging from 100000 to 10000000. The router produced by different manufacturers is configured with different values. Both ends of the BFD session should be consistent. It is an optional parameter. Type an integer ranging from 2 to 255. The recommended value is 2
OPTMODE
Work mode
It is an optional parameter. Select ASYNCHRONOUS
AUTHID
Authentication ID
The parameter ranges from 1 to 255
CHGOVER
Change Over
YES can be selected
Confidential and Proprietary Information of ZTE CORPORATION
89
ZXWN MSCS Data Configuration Guide(MGCF)
Example: Create the BFD session when SIPI interface board is connected with the router. The requirements are as follows. �
Local address of BFD session: 10.0.74.4
�
Remote address of BFD session: 10.0.74.1
�
Single hop flag: SINGLE_HOP
�
Working mode: Asynchronous.
The command is as follows: ADD BFD SESSION:SRCIP="10.0.74.4",DSTIP="10.0.74.1 ",MULTIHOP=SINGLE_HOP,DESMINTXINTVAL=100000,R EQMINRXINTVAL=100000,DETECTMULT=3,OPTMODE=A SYNCHRONOUS; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a Static Route Prerequisites
Before the operation, it is required to confirm: �
The interface address is created.
�
The BFD parameters are created when load-sharing networking mode is adopted.
�
The MML Terminal window is opened.
Context
Static route is created when the service IP address of local signaling plane and PE interface address are not in the same network section. Under the active/standby working mode, a destination address needs to be configured with a route only. Under the load-sharing working mode, a destination address usually needs to be configured with two routes.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a static route. The command is ADD IP ROUTE. Table 39 describes the parameters in the ADD IP ROUTE command.
90
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
TABLE 39 PARAMETERS IN THE ADD IP ROUTE COMMAND Parameter Name
Parameter Description
NETPRE
Net prefix
MASK
Mask
Instruction
It is a mandatory parameter. Type the network section of the opposite-end equipment service address according to the network planning. Its prefix should match its mask
NEXTHOP
Next hop IP
It is an optional parameter, indicating the router interface address (VRRP address). Type the gateway address to the opposite end office
DISTANCE
Distance
It is an optional parameter with a default of 1, ranging from 1 to 254
BFDDETECT
Enable BFD Detect
It is an optional parameter. In general, select NO. Only when next hop is IP address, BFDDETECT option is in effect
Example: Create the static route to the opposite end with the following requirements. �
Working mode: active/standby mode
�
Service address of the opposite equipment: 11.11.11.1
�
Mask: 255.255.255.0
�
Next hop IP: 10.0.74.1.
The command is as follows: ADD IP ROUTE:NETPRE="11.11.11.1",MASK="255.255. 255.0",NEXTHOP="10.0.74.1",DISTANCE=1,BFDDETECT =NO; Example: Create two static routes to the opposite end with the following requirements. �
Working mode: load-sharing mode
�
Service address of the opposite equipment: 11.11.11.1
�
Mask: 255.255.255.0
�
Next hop IP: 10.0.74.1 and 10.0.74.2.
The command is as follows: ADD IP ROUTE:NETPRE="11.11.11.1",MASK="255.255. 255.0",NEXTHOP="10.0.74.1",DISTANCE=1,BFDDETECT =NO; ADD IP ROUTE:NETPRE="11.11.11.1",MASK="255.255. 255.0",NEXTHOP="10.0.74.2",DISTANCE=1,BFDDETECT =NO; END OF STEPS
Confidential and Proprietary Information of ZTE CORPORATION
91
ZXWN MSCS Data Configuration Guide(MGCF)
Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Adjacent Office and Topology Configuration Overview Introduction
Adjacent office configuration means configuring the neighboring office of the local office. There are two association modes, direct association and quasi-association. If the adjacent office is regarded as a node in the whole network topology when the local office is in the center, topological node configuration means adding the topological node of its adjacent office in the local office. The topological nodes configured on MGCF include IM-MGW, CSCF, BGCF, MGCF, and MSCS. Table 40 shows adjacent office and topology configuration. TABLE 40 ADJACENT AND TOPOLOGY CONFIGURATION Steps
Operation
Instruction
1
Creating an MGW adjacent office
Create the basic information of MGW adjacent office.
ADD ADJOFC
2
Creating an MGW voice CODEC template
Create the encoding and decoding speech type modules supported by IM-MGW.
ADD CODECTPL
3
Creating topology node
Create the topology relationship between MGCF node and IM-MGW node.
ADD TOPO
4
Creating inter-MGW bear mode (optional)
The inter-MGW bearer mode is configured when the Nb interfaces between several IM-MGWs under the same MGCF are connected.
ADD MOD
a
Command
MGWBEAR
Creating an IM-MGW Adjacent Office Prerequisites
92
Before the operation, it is required to confirm:
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
�
The physical IP connection between the MGCF and the IM-MGW is clear, which is implemented by the connection between the FE1 interfaces on the rear board of the SIPI boards of these two 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 resource management.
�
The MML Terminal window is opened.
Context
Perform this procedure to configure the basic information of IM-MGW adjacent office.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an IM-MGW adjacent office. ADJOFC.
The command is ADD
Table 41 describes the main parameters in the ADD ADJOFC command. TABLE 41 PARAMETERS IN THE ADD ADJOFC COMMAND Parameter Name
Parameter Description
Instruction
ID
Office ID
A mandatory parameter, indicating the identification number of the adjacent office, and ranging from 1 to 3000. In general, it is configured as the exchange ID of the adjacent office during the all-network planning
NAME
User-defined alias
It is a mandatory parameter. Type a customized name
Network type
A mandatory parameter, indicating the network type of the SPC used for connecting the local office to the adjacent office when the local office is configured with several SPs. The default is the network type of this SP when there is only one SP in the local office
The type of adjacent office
It is a mandatory parameter. Select MGW for the IM-MGW bearing H.248 signaling. Select SGW for another IM-MGW office
NET
OFCTYPE
Confidential and Proprietary Information of ZTE CORPORATION
93
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
SPCFMT
SPC format
Select TRIPLE_DEC
SPCTYPE
SPC type
DPC
Destination SPC
RC
Area code
It is a mandatory parameter. Select it based on the SPC type of the adjacent office according to the signaling point planning. In China, all the NEs adopt the 24-bit SPC It is an optional parameter, indicating the local toll zone code of the adjacent office. This parameter has impact on the area code added by the calling number
Association type, including: �
AM_SURE (direct connection mode)
�
AM_QUASI (half direct connection mode)
�
AM_NONE (none connection mode)
ASSOTYPE
SPTYPE
Signaling point type, including SEP, STP and STEP
It is an optional parameter. Select AM_SURE
It is an optional parameter. Select SEP (signaling end point) for the IM-MGW bearing H248 signaling. Select STEP (signaling transition /end point) for another IM-MGW office
Subservice function, including �
INTERNATIONAL (International signaling point code)
�
INTERNATIONAL STANDBY (International standby signaling point code)
SSF
94
�
NATIONAL (National signaling point code)
�
NATIONAL STANDBY (National standby signaling point code).
Confidential and Proprietary Information of ZTE CORPORATION
It is an optional parameter. In general, NATIONAL is selected at home.
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction
Office Attribute, including: ISNI (Has ISNI Function)
TAG
TRANS (Translate Node)
It is an optional parameter
TEST (Need Test Info:0X02/0X01)
TEST
Test flag
It is an optional parameter. It is used to set whether the MTP3 link actively initiates the link test after entering the service status. In most cases, this parameter is selected. It is an optional parameter with a default of NO. It is used for SCCP to judge whether to use the LUDT message.
BANDFLAG
Broadband attribute
The maximum length of a broadband link message is 4,000, and that of a narrowband link message is 255. Because the MTP layer does not have the segmentation function, the incorrect configuration of this parameter probably causes the long packet to be discarded. Select YES when all the links between two SPs are SIGTRAN or ATM signaling links.
Protocol Type, including: �
CHINA (China)
�
ITU (International Telecommunications Union)
�
ANSI (American National Standards Institute)
PRTCTYPE
It is an optional parameter. The CHINA and the ITU are used for the NO.7 signaling networking of the ITU standard and the ANSI is used for the NO.7 signaling networking of the American standard. In general, select CHINA for the domestic office and select ITU for the international office
Confidential and Proprietary Information of ZTE CORPORATION
95
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
CLST
Parameter Description
Instruction
Cluster ID
It is an optional parameter within 0~65535. In general, select the default value 65535. It is valid when the protocol type of the adjacent office is “ANSI”. The signaling point connected to the signaling transfer point belongs to the corresponding cluster. The cluster ID is configured in the command ADD CLST
Office Info, including: CIC_PCM (CIC starts the load sharing according to the PCM code mode) BLOCK (Manual block status)
INFO
EVEN_CIC (The office controls the even CIC when CIC resource contention occurs)
It is an optional parameter and the default value is CIC_PCM
CALLING ( Calling transform is allowed) CALLED (Called transform is allowed) MOD24_CIC (CIC mode with 24 mode) TEST (Dynamic observation) RELATEDOFC1
Related Office ID
It is an optional parameter ranging from 0 to 3000
Office Extend Info, including:
INFOEX
96
�
SIGBRDCST (Support Signa ling Broadcast Message)
�
MTP (Hongkong MTP Standard)
�
DUPU ( Screen DUPU message)
�
SUA_REC_DT1 (Receive SUA message and handle it as DT1 message)
�
SUA_SND_DT1 (Send SUA message and handle it as DT1
Confidential and Proprietary Information of ZTE CORPORATION
It is an optional parameter
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction
message without SN.) �
OPEN_TG_RES (Open outter trunk group resource)
For example, create an IM-MGW adjacent office. The office ID is 101, the alias is MGW1, and the destination SPC is 1.31.1. For other parameters, adopt the default value. The command is as follows: ADD ADJOFC:ID=101,NAME="IM-MGW1",NET=2,OFCTYP E=MGW,SPCFMT=TRIPLE_DEC,SPCTYPE=14,DPC="1.31.1 ",RC="25",ASSOTYPE=AM_SURE,SPTYPE=SEP,SSF=NATIO NAL STANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BAND FLAG=YES,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_P CM",RELATEDOFC1=0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating an MGW Voice CODEC Template Prerequisites
Before the operation, it is required to confirm: �
The basic configuration of the local office is completed.
�
The range of the MGW encoding and decoding speech template numbers is configured in the resource management configuration.
�
The MML Terminal window is opened.
Context
Perform this procedure to configure the encoding and decoding speech type modules supported by MGW. In general, MSCS is configured with a default common encoding and decoding speech template.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create the MGW voice CODEC template. The command is ADD CODECTPL. Table 42 describes the main parameters in the ADD CODEC TPL command.
Confidential and Proprietary Information of ZTE CORPORATION
97
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 42 PARAMETERS IN THE ADD CODECTPL COMMAND Parameter Name
Parameter Description
Instruction
ID
Template number
It is a mandatory parameter for defining an encoding and decoding speech template, ranging from 1 to 255.
GRPID
The group number of the speech coding.
It is a mandatory parameter for specifying the OID format and encoding and decoding type list. Up to eight types can be defined in an encoding and decoding template.
VALFG
Valid option, including YES (valid) and NO (invalid)
It is a mandatory parameter for setting whether this encoding and decoding speech template is valid. Select YES It is a mandatory parameter for specify an Organization Identifier (OID). It has the following parameters.
OID
OID
�
OID_NONE: No OID
�
OID_ITU_T: ITU_T
�
OID_ETSI: ETSI
�
OID_IETF: IETF
ITYPE
ITU_T CODEC type
It is an optional parameter. In general, ITUT_G711A_64 is selected.
ETYPE
ETSI CODEC type
It is an optional parameter. In general, ETSI_UMTS_AMR and ETSI_UMTS_AMR_2 are selected.
ACTRATE
Activated CODEC rate
It is an optional parameter. In general, the default value is selected
SUPRATE
Supported CODEC rate
It is an optional parameter. In general, the default value is selected
OM
ACS optimized mode
It is an optional parameter. In general, the default value is selected
Example: Configure an MGW encoding and decoding speech template with the following requirements.
98
�
Template ID: 1
�
CODEC group number: 1
�
Valid option: YES
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
�
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="Rate59 0"&"Rate670",SUPRATE="Rate590"&"Rate670",OM=YES; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a Topology Node Prerequisites
Context
Before the operation, it is required to confirm: �
The encoding and decoding speech template is configured.
�
The range of the topological node number is configured in the resource management.
�
The MML Terminal window is opened.
Perform this procedure to configure the topology relationship between MGCF node and IM-MGW node. This command is used to configure the adjacent NE information, including equipment type, bearer type and attributes, user plane version, encoding and decoding template, and other information. For Mn interface, only the adjacent office bearing H.248 protocol is configured as a topological node.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an IM-MGW topological node. The command is ADD TOPO. Table 43 describes the main parameters in the ADD TOPO command.
Confidential and Proprietary Information of ZTE CORPORATION
99
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 43 PARAMETERS IN THE ADD TOPO COMMAND Parameter Name
ID
OFCID
Parameter Description
Topological node ID
Office ID
Instruction It is a mandatory parameter to define ID of this node, ranging from 1 to 2,048. It is recommended that the ID and office No. of a topological node are consistent It is a mandatory parameter for specifying the office ID of this topological node. This parameter must be defined by the ADD ADJOFC command first. In this case, type the actual IM-MGW office number
NAME
CODECID
ETYPE
Alias
It is a mandatory parameter for naming this topological node, with a length ranging from 1 to 50 characters.
CODEC identity
It is a mandatory parameter for specify the CODEC template used by this topological node. This parameter must be defined by the ADD CODECTPL command first.
Equipment type
This parameter is used to specify the NE type of this topological node. Select R4GW for an MGW node
PROTTYPE
IPVER
ATTR
Protocol type
Select H.248 for Mn interface.
IP version of the node
It is the IP protocol version supported between nodes. Select IPV4 or IPV6 according to the actual conditions. Currently, IPV4 is supported.
Bearer attributes
This parameter is only valid for the node with the type of R4GW (MGW). The bearer types supported by MGW are BNCAAL1, BNCAAL2, BNCAAL1S, BNCIPRTP, and BNCTDM. MGW can one or more of these types of bearers. In general, select BNCAAL2, BNCIPRTP, and BNCTDM
100
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Parameter Name
Parameter Description
UPVER
User plane protocol version of RNC or MGW Extended attributes (tunnel mode), including: �
NOTUNL (None tunnel mode)
�
RTUNL (Rapid tunnel mode)
ATTR2
�
DTUNL (Delay tunnel mode)
Signaling transfer mode, including: TRFMOD
MCINTF (Mc interface signal transfer mode)
Instruction This parameter is used to set the user plane version of this node. In general, select V2
This parameter is used to set which tunnel mode is adopted for bearer establishment when this node supports the IP/RTP bearer. The default value is NOTUNL (None tunnel mode). In general, select DTUNL (Delay tunnel mode) for an MGW topological node.
This parameter is used to set which mode is used by the topology for reporting when it detects CNG or CED fax signals. The default value is MCINTF
Error SDU control, including options:
UPERRCTRL
YES: The user plane entity implements error inspection, and sets the FQC bit position according to the result. It will transmit all frames includes the error frames to the user plane layer. During a call, the error packet control parameter delerrsdu=Yes, which is delivered by the terminal established by MGW on the Mc interface. The error packet control parameter deliveryOfErroneousSDU is YES, NA, NA during RAB assignment.
This parameter regulates the handling method of the user plane for error frames. It is only valid for MGW-type and RNC-type topological node. The default value is YES
NO: The user plane entity implements the error inspection.
Confidential and Proprietary Information of ZTE CORPORATION
101
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description It will directly discard the error frame. During a call, the error packet control parameter delerrsdu=No, which is delivered by the terminal established by MGW on the Mc interface. The error packet control parameter deliveryOfErroneousSDU is NO, NA, NA during RAB assignment.
Instruction
INVALIDTION: The user plane entity does not implement the error inspection. During a call, the error packet control parameter delerrsdu=NA, which is delivered by the terminal established by MGW on the Mc interface. The error packet control parameter deliveryOfErroneousSDU is NA, NA, NA during RAB assignment.
DTMFTC
Tandem office send DTMF use TC mode, including two options, NO and YES
This parameter is used to set whether the tandem office uses the TC resources during DTMF number delivery. The default value is NO It contains the following options.
MGWCON
MGW congestion reporting capability
�
SMGWCON (Standard MGW congestion event)
�
CMGWCON (Custom MGW congestion event).
The default value is SMGWCON.
Example: Create a topological node with the following requirements.
102
�
MGW office ID: 101
�
Equipment type: R4 gateway
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
�
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="IM-MGW101",CO DECID=1,ETYPE=R4GW,PROTTYPE=H248,IPVER=IPV4,A TTR="BNCAAL2"&"BNCIPRTP"&"BNCTDM",UPVER="V2",ATT R2=NOTUNL,TRFMOD=MCINTF,UPERRCTRL=YES,DTMFTC =NO,MGWCON=SMGWCON,AUTOFAX=YES,OOBTC=NO,B CUID=0,SENDCAP=NO,G711TRAN=NO,BICCDTMF=TRAN SPARENT,IPBCP2833=BYMGW,BICCDTMPPER=0,AOIPPR O=PRIVATE; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating Inter-MGW Bear Mode Prerequisites
Before the operation, it is required to confirm: �
The MGW topological node is configured.
�
The MML Terminal window is opened.
Context
The inter-MGW bearer mode is configured when the Nb interfaces between several IM-MGWs under the same MGCF are connected.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create the inter-MGW bearer mode. The command is ADD MGWBEARMOD. Table 44 describes the main parameters in the ADD MGWBE ARMOD command. TABLE 44 PARAMETERS IN THE ADD MGWBEARMOD COMMAND Parameter Name
Parameter Description
Instruction
MGWPAIR
MGW node pair
Type the gateway node ID configured in the topological node configuration.
ATTR
Bearer attribute between MGWs, the options include:
The parameter specifies the bearer attribute between MGWs. Select RTP or TDM
Confidential and Proprietary Information of ZTE CORPORATION
103
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
AAL1(support bncAAL1) AAL2(support bncAAL2) AAL1S (support nbcAAL1Struct)
according to the type of Nb interface bearer.
RTP (support bncIPRTP) TDM(support bncTDM)
CTYPE
Type of tone code between MGWs, the options including: GENERAL
AMRONLY represents the AMR encoding and decoding mode is used only. When G.711 and other encoding and decoding modes are allowed, select GENERAL
AMRONLY NAME
Alias
“Adjacent office alias of gateway 1-Adjacent office alias of gateway 2”
AAL1
AAL1 bearer type rate(%)
The parameter specifies the rate (%) of the AAL1 bearer between two gateways
AAL2
AAL2 bearer type rate(%)
The parameter specifies the rate (%) of the AAL2 bearer between two gateways
AAL1S
AAL1STRUCT bearer type rate(%)
The parameter specifies the rate (%) of the AAL1 STRUCT bearer between two gateways
RTP
IPRTP bearer type rate(%)
The parameter specifies the rate (%) of the IPRTP bearer between two gateways
TDM
TDM bearer type rate(%)
The parameter specifies the rate (%) of the TDM bearer between two gateways
DIRECT
Top-priority direct link topology, the options include: NO; YES
104
Confidential and Proprietary Information of ZTE CORPORATION
The default is NO
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Parameter Name
Parameter Description User plane mode for multi-gateway IP bearer, the options include:
UPMODE
TRANSPARENT(transparent mode)
Instruction
The default is TRANSPARENT
SUPPORT(support mode) IPNET
G711TRAN
Public IP network domain index G711 that is forced to use the transparent mode. Options include:
The parameter is used to set the public IP network domain index (ADD IPDOMAIN)
The default is NO
NO; YES
Example: Configure the bearer mode between two IM-MGWs with the following requirements. �
MGW 1 node ID: 101
�
MGW 2 node ID: 201
�
Bearer mode: RTP
�
Type of tone code between IM-MGWS: AMRONLY
�
Encoding and decoding template ID: 1
�
Alias: IM-MGW101-IM-MGW201
�
Other parameters: default value.
The specific command is as follows. ADD MGWBEARMOD:MGWPAIR="101"-"201",ATTR="RT P",CTYPE=AMRONLY,AAL1=0,AAL2=0,AAL1S=0,RTP=10 0,TDM=0,DIRECT=YES,UPMODE=TRANSPARENT,NAME="I M-MGW101-IM-MGW201",G711TRAN=NO; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
105
ZXWN MSCS Data Configuration Guide(MGCF)
SIGTRAN Configuration Overview Description
SINGTRAN-related configuration is required not only by the Mc interface between MSCS and MGW, but also by the Nc interface between 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 required only. In general, this mode is not used. Compared with the MTP data configuration of the traditional No.7 signaling, the SCTP association configuration and the ASP configuration of the M3UA are similar to the link logic and bearer information configurations in the MTP configuration, and the AS configuration of the M3UA is similar to the link set configuration in the MTP configuration. The configuration of SIO location AS is similar to the signaling office direction and route configuration in the MTP configuration. The only difference between them is that one piece of SIO location AS configuration record is configured the IP route to a subscriber of an office.
106
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Configuration Flow
Figure 52 shows the flow of SIGTRAN configuration. FIGURE 52 SIGTRAN CONFIGURATION FLOW
According to the rules regulated in SCTP Planning, perform the configuration by following the procedure specified below. Steps
Operations
Instructions
Command
1
Creating an SCTP
Create an association between two offices
ADD SCTPC ONN
Creating an ASP
Configure the one-to-one relationship between the ASP and the association. ASP is one of instances of AS.
ADD ASP
2
Confidential and Proprietary Information of ZTE CORPORATION
107
ZXWN MSCS Data Configuration Guide(MGCF)
Steps
3
4
5
Operations
Instructions
Command
Creating an AS
Configure the tag, user type, subsystem type of AS
ADD AS
Creating an M3UA static route
Configure the mapping relationship between the M3UA static route and the AS.
ADD M3UART
Creating the SIO-Locating-AS
Locate one service to a routing table that is maintained by the ASP under the AS.
ADD SIOLO CAS
SCTP Planning The signaling carried by associations between MSCS and MGW is as follows. 1. If the association bears the H248 signaling between MGCF and IM-MGW, the H248/M3UA/SCTP bearer is adopted usually, and the H248/SCTP bearer is supported. 2. The association bears the ISUP, TUP, and SCCP signaling between MGCF and MSC/PSTN (MGW acts as an agent or transfers the signaling). M3UA/SCTP adopts the (ISUP, TUP, SCCP)/M3UA/SCTP bearer. If the MTP3 direct-associated office does not exist on MGW, the SCTP configuration is not required. According to the rules regulated in SPC configuration rules, both MGCF and IM-MGW adopts different combinations of signaling points and network types for the three bearer modes mentioned above. That is, an MGCF is configured with three adjacent offices on IM-MGW, and one group of associations is configured between every two adjacent offices for bearing different services. The number of associations is related with the signaling networking, equipment capacity, and configured SMP number. It is also limited by the configuration. For example, an AS can be configured with up to 16 SCTP associations.
Creating an SCTP Prerequisites
Before the operation, it is required to confirm: �
108
The physical configuration of the SMP module is completed.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
�
The SCTP flag is configured in the resource management.
�
The MML Terminal window is opened.
Context
The SCTP connection is called as association, which is of one-toone correspondence with ASP. It can be equivalent to the communication link used by the AS. An SMP can support up to 128 associations. When multiple BCTC shelves are configured, associations must share the load in each shelf.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create the SCTP connection. The command is ADD SCTPCO NN. Table 45 describes the chief parameters of the ADD SCTPC ONN command. TABLE 45 PARAMETERS IN THE ADD SCTPCONN COMMAND Parameter Name
MODULE
OFCID
Parameter Description
Instruction
Module No.
It is a mandatory parameter, indicating the number of the signaling module homed by this SCTP association. Select the SMP module number. Each SMP can support up to 128 associations. The associations under the same AS are required sharing load on SMP modules as more as possible.
SCTP opposite office ID
It is a mandatory parameter, designating the office No. of the direct-associated association. Type the IM-MGW adjacent office No. specified in the adjacent office configuration.
Bearer protocol types, including �
M2UA
�
M2PA
�
M3UA
�
SUA
�
H248
�
BICC
�
IUA
�
DHCTRL
�
SIP
�
DIM
PROT
It is a mandatory parameter. It is used to identify the upper-layer protocol type borne by the SCTP association. In general, M3UA is selected. M2UA is selected when IM-MGW transfers the signaling with the M2UA mode.
Confidential and Proprietary Information of ZTE CORPORATION
109
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description �
V5UA
�
H245
SCTP application attributes. Options include: ROLE
SVR: SCTP is used as server CLT: SCTP is used as client
Instruction
It is a mandatory parameter. For Mn interface, MGCF is configured as CLT, and IM-MGW is configured as SVR. For Nc interface, this should be negotiated by both sides. For example, the small signaling point serves as CLT, and the big signaling point serves as SVR It is a mandatory parameter. It designates the service address of local end of this association, with a format of Local IP address type-VPN of local IP address-Local IP address
LOCADDR
Local IP address
Local IP address type: IPv4 and IPv6 VPN of local IP address: Rang from 0 to 65535 Local IP address: the format is xxx.yyy.zzz.mmm
LOCPORT
REMADDR
Local port number
Opposite IP address
It is a mandatory parameter. It is the local SCTP port number of the association, ranging from 1 to 65535. It is a mandatory parameter. It designates the service address of remote end of this association, with a format of Remote IP address type-VPN of remote IP address-Remote IP address Remote IP address type: IPv4 and IPv6 VPN of remote IP address: Rang from 0 to 65535 Remote IP address: the format is xxx.yyy.zzz.mmm
REMPORT
Opposite port number
It is a mandatory parameter. It is the opposite SCTP port number of the association, ranging from 1 to 65535.
NAME
Alias
It is a mandatory parameter with a length ranging from 1 to 50 characters.
SCTP ID
It is an optional parameter. It is the global serial number of the SCTP association, ranging from 1 to 2048. Configure it according to the association planning.
ID
110
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Example: Create the SCTP connection for the Mn interface with the 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
�
Other parameters: default value.
The command is as follows. ADD SCTPCONN:MODULE=3,OFCID=101,PROT=M3UA,R OLE=CLT,LOCADDR="IPv4"-"0"-"192.168.1.11",LOCPORT =2001,REMADDR="IPv4"-"0"-"192.168.1.31",REMPORT=2 001,NAME="IM-MGW101-1",ID=1,INSTRM=16,OUTSTRM =16,MAXRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=1 00,HB=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYA CK=20,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,B REAKTIME=0,PDTHRESH=0,MINCWND=0,PLTIMER=1 0,MPPLTHRD=2,DPLEN=MTU,CB=200; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating an ASP Prerequisites
Before the operation, it is required to confirm: �
The SCTP association information configuration is completed.
�
The range of the ASP configuration identification is configured in the resource management configuration.
�
The MML Terminal window is opened.
Context
Perform this procedure to define the one-to-one relationship between the ASP and the association. ASP is one of instances of AS.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an ASP. The command is ADD ASP.
Confidential and Proprietary Information of ZTE CORPORATION
111
ZXWN MSCS Data Configuration Guide(MGCF)
Table 46 describes the main parameters in the ADD ASP command. TABLE 46 PARAMETERS IN THE ADD ASP COMMAND Parameter Name
Parameter Description
Instruction It is a mandatory parameter, ranging from 1 to 2048
ASSOCID
NAME
ID
SCTP ID
Alias
ASP ID
ISLOOP
ASP self-loop ID
Type the association ID configured in the SCTP connection configuration. It is a mandatory parameter, with a lengthen ranging from 1 to 50 characters. It may be named with a format of “Adjacent office alias-SCTP number”. It is an optional parameter, ranging from 1 to 2048. It is recommended to be consistent with ASSOCID. It is an optional parameter. It is used to set whether the ASP is self-looped. Select the default value NO
ISLOCK
ASP blocking flag
It is an optional parameter. It is used set whether the ASP is in blocking state. Blocking is used for management. Select the default value NO
Example: Configure the ASP between MGCF and IM-MGW for Mn interface with the following requirements. �
MGW office ID: 101
�
SCTP association ID: 1
�
ASP configuration ID: 1
�
User alias: MGW101-1
The command is as follows. ADD ASP:ASSOCID=1,NAME="MGW101-1",ID=1,ISLOOP =NO,ISLOCK=NO; END OF STEPS Result
112
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Creating an AS Prerequisites
Before the operation, it is required to confirm: �
The ASP configuration is finished.
�
The MML Terminal window is opened.
Context
The AS provides the transmission channels for upper-layer services. For example, H248 and TUP/ISUP are different services. They use different AS for transmission. The AS can use one or more associations for communication.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create the AS. The command is ADD AS. Table 47 describes the main parameters in the ADD AS command. TABLE 47 PARAMETERS IN THE ADD AS COMMAND Parameter Name
Parameter Description
Instruction
PROT
Supported adaptation layer protocols
It indicates the protocol type of a bearer. In general, M3UA is selected according to the networking planning. It is configured as M2UA when MGW transfers the signaling with M2UA mode.
ASPID
ASP ID
It is associated with the ASP ID configured in the ASP configuration.
NAME
Alias
It is a mandatory parameter. The alias customized by the user.
ID
AS ID
It is an optional parameter. It is the unique identification of the AS. In general, it is the same as that of the ASP for easy memory. The parameter ranges from 1 to 640
EXISTCTX
Whether the routing context ID exists
CTXID
Routing context ID
It is an optional parameter. The routing context is unique in the network. This parameter must be consistent with the AS configuration of the opposite-end. Its default value is NO
Confidential and Proprietary Information of ZTE CORPORATION
113
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction It is an optional parameter.
Usage tag. Options include: SGP ASTAG
ASP SRV (IPSP server) CLT (IPSP client)
ASUP
SSN
114
User types supported by AS. Options include TUP, ISUP, BICC, H.248, ALCAP SCCP, PCA, NNSF and ALL
Types of subsystem. Options include NO_SSN (subsystem SSN 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 (intelligent peripherals), SMC, SSP_SCP, BSC_BSSAP_LE, MSC_BSSAP_LE, SMLC_BSSAP_LE, BSS_O_M_A , BSSAP_A and RVE255.
Confidential and Proprietary Information of ZTE CORPORATION
For Mn interface, MGCF generally serves as IPSP_Client, and IM-MGW serves as IPSP_Server. When IM-MGW acts as a SGW, the AS at the MGCF side serves as ASP, and the AS at the SGW side serves as SGP. For Nc interface, this should be negotiated by both sides. For example, the small signaling point serves as IPSP_Client, and the big signaling point serves as IPSP_Server. It is an optional parameter. It defines the upper-layer user types supported by the AS. Currently, there are eight types of users. User type is not configured when IM-MGW transfers the signaling with the M2UA mode
Types of subsystem supported by application server (AS).
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction It is an optional parameter. The supported service modes include:
ASMD
Service modes supported
�
OVERRIDE (Over-ride mode)
�
LOAD (Load share mode).
In the over-ride mode, only one ASP is in the activated statue. In this case, only one ASP needs be configured. In the load sharing mode, N ASPs should be configured in the activated working statue, and K ASPs should be configured in the deactivated standby statue. The value of N+K is not more than the number of ASPs actually configured The parameter ranges from 0 to 64.
NVAL
The N value in load sharing mode
The N+K should be equal to the number of ASP under AS. The N value indicates that AS comes into service when N ASPs are put into service. The parameter ranges from 0 to 63.
The K value in load sharing mode
KVAL
The N+K should be equal to the number of ASP under AS. The K value indicates that AS is out of service when K ASPs are used as standby ASP.
Example: Configure the AS between MGCF and IM-MGW for Mn interface with the following requirements. �
MGW office ID: 101
�
Supported adaptation layer protocol: M3UA
�
AS configuration ID: 1
�
Supported user type: H248
�
ASP ID: 1
�
Usage Tag: CLT
�
Alias: H248
The command is as follows.
Confidential and Proprietary Information of ZTE CORPORATION
115
ZXWN MSCS Data Configuration Guide(MGCF)
ADD AS:PROT=M3UA,ASPID="1",NAME="H248",ID=1,EX ISTCTX=NO,ASTAG=CLT,ASUP="H248",ASMD=LOAD,NVA L=1,KVAL=0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating an M3UA Static Route Prerequisites
Before the operation, it is required to confirm: �
The AS configuration is finished.
�
The range of the M3UA static route identification is configured in the resource management configuration.
�
The MML Terminal window is opened.
Context
Perform this procedure to configure the mapping relationship between the M3UA static route and the AS. An M3UA static route can be used by up to 64 SIO-locating-ASs. Otherwise, configuring more M3UA static routes is required.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create the M3UA static route. The command is ADD M3UART. Table 48 describes the main parameters in the ADD M3UART command. TABLE 48 PARAMETERS IN THE ADD M3UART COMMAND
116
Parameter Name
Parameter Description
Instruction
ID
ID of M3UA static route
It is an optional parameter, indicating the serial number of the M3UA static route ID, ranging from 1 to 640. In general, it is the same as the AS ID.
ASID
AS ID
It is a mandatory parameter, corresponding to the AS ID specified in the ADD AS command.
MODE
Alignment mode of routes. Options include BYTURNS,
Nature: routes are directly sorted according by the ASP marshalling sequence in the routing table. Local: It is unnecessary to realize the algorithm in the background. The background just needs to make the alignment according to the Nature option.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Parameter Name
Parameter Description
LOCAL and NATURE.
Instruction BYTURNS: in the routing table, the routes at the odd-bit position are sorted by the serial number of the activated ASP, and the routes at the even-bit position are sorted inversely by the serial number of the activated ASP The default is BYTURNS.
NAME
Alias
It is a mandatory parameter defined by a user, with a length ranging from 1 to 50 characters.
Example: Create an M3UA static route for Mn interface with the following requirements. �
MGW office ID: 101
�
M3UA static route ID: 1
�
AS ID: 1
�
User alias: IM-MGW101
The specific command is as follows. ADD M3UART:ID=1,ASID=1,MODE=BYTURNS,NAME="IM -MGW101"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating the SIO Locate AS Prerequisites
Context
Before the operation, it is required to confirm: �
The M3UA static route configuration is completed.
�
The range of the SIO-locating-AS configuration ID is configured in the resource management configuration.
�
The MML Terminal window is opened.
The configuration of SIO-locating-AS is used to locate one service to a routing table that is maintained by the ASP under the AS. On MGCF, H248 protocol is generally configured between MGCF and IM-MGW, and ISUP, TUP, and SCCP protocols are configured between MGCF and other adjacent offices that are switched by IM-MGW. A routing key describes a set of No.7 signaling parameters and parameter values. The corresponded AS is selected according to the message attributes, thus to select a route for the message.
Confidential and Proprietary Information of ZTE CORPORATION
117
ZXWN MSCS Data Configuration Guide(MGCF)
The message attributes include DPC+NET+OPC+SIO. The DPC represents the destination SPC, the NET represents the network type, OPC represents the original SPC, and the SIO represents the service information octet. Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create the SIO-locate-AS. The command is ADD SIOLOCAS. Table 49 describes the main parameters in the ADD SIOLO CAS command. TABLE 49 PARAMETERS IN THE ADD SIOLOCAS COMMAND Parameter Name
Parameter Description
Instruction
ID
SIO-locate-AS ID
It is an optional parameter, indicating the serial number of SIO-locate-AS, ranging from 1 to 4096. In general, it is the same as the AS ID.
NAME
Alias
It is a mandatory parameter, which is the alias customized by the user
SIO
OFCID
OPOFCID
118
Service indication. Options include TUP, ISUP, BICC, H.248, ALCAP, SCCP,PCA and NNSF
It is a mandatory parameter, indicating the subscriber type belonged by the transmitted message. Different user types can be located to the same AS under the precondition that the AS must support these user types. Select H.248 for Mn interface, BICC for Nc interface, and TUP or ISUP for the 2G MSC/PSTN office transferred through MGW.
Destination adjacent office ID
It is a mandatory parameter, indicating the adjacent office ID corresponded by the destination signaling point of the M3UA. It needs to associate with the adjacent office ID in the adjacent office configuration.
Original adjacent office ID
It is the adjacent office ID corresponding to the M3UA originating signaling point. If 0 (indicating the local office) is selected, it indicates that the message is sent from the local office, and the routing context is routed according to DPC+NET+OPC+SIO. If 65535 (invalid) is selected, it indicates that the OPC field is invalid, and
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction the routing context is routed according to DPC+NET+SIO
PCM system number
PCM
RT1
ID 1 of M3UA static route
RT2
ID 2 of M3UA static route
It is an optional parameter. It ranges from 0 to 65535, with a default of 65535 (invalid).
It corresponds to the ID specified in the M3UA static route configuration. RT1 is a mandatory parameter. In general, RT1 is required. When the optimum route mode is adopted, RT1 is set as an active route, and RT2 is set as a standby route.
Example: Create SIO-locate-AS between MGCF and IM—MGW with the following requirements. �
IM-MGW office ID: 101
�
Destination adjacent office ID: 101
�
Service indication: H248
�
M3UA static route ID: 1.
The specific command is as follows. ADD SIOLOCAS:ID=1,NAME="IM-MGW-H248",SIO=H24 8,OFCID=101,OPOFCID=65535,PCM=65535,RT1=1,RT2 =0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
H.248 Configuration Overview Description
H.248 protocol is used on Mn interface. It provides the following functions. �
Under the control of MGC, it can establish, modify and release the media channel in the MG, and can control the attributes of bearer and user plane.
�
It reports the events in the MG to the MGC.
�
It maintains the office and terminal status between MGC and MG.
Confidential and Proprietary Information of ZTE CORPORATION
119
ZXWN MSCS Data Configuration Guide(MGCF)
Configuration Flow
Figure 53 shows the configuration flow of H.248 protocol. FIGURE 53 CONFIGURATION FLOW
Flow Description
120
The H.248 configuration procedures are as follows: Steps
Operations
Instructions
Command
1
Creating MGC static data
Cofigure the data related to the MGCF and H.248.
ADD MGCSCFG
2
Creating an MGW static data template
Configure the template used by the MGW static data configuration.
ADD MGSTPL
3
Creating MGW static data
Configure the static data for each IM-MGW under the MGCF.
ADD MGSCFG
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Steps
4
5
Operations
Instructions
Command
Creating a TID analyzer
The TID analysis configuration is necessary for the H.248 server to perform the character string conversion of the CIC. Nomally adopt the default configuration.
ADD TIDANL
Creating a TID analysis entrance
Configure a TID analyzer entrance. Nomally adopt the default configuration.
ADD TIDENTR
Creating MGC Static Data Prerequisites
Before the operation, it is required to confirm: �
The data configuration of the local office is completed.
�
The MML Terminal window is opened.
Context
Perform this procedure to set the data related to the MSCS and H.248.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create the MGC static data. The command is ADD MGCSCFG. Table 50 describes the main parameters in the ADD MGCSCFG command. TABLE 50 PARAMETERS IN THE ADD MGCSCFG COMMAND Parameter Name
Parameter Description
Instruction
MEGACO
MEGACO version number
It is an optional parameter. Select the supported MEGACO version number, which must be consistent with that negotiated with the MGW. The default value is 1
ACTTM
Service activation detection timer(s)
It is an optional parameter, ranging from 0 to 3600, with a default of 600
Confidential and Proprietary Information of ZTE CORPORATION
121
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
ACTCHK
Service activation detection switch
It is an optional parameter, being activated by default.
WAITTM
MGW answer waiting timer (ms)
It is an optional parameter, ranging from 0 to 65535, with a default of 7800
PTRYNUM
PEND retry times(t)
It is an optional parameter, ranging from 1 to 255, with a default of 5
PTRYTM
PEND retry time (ms)
It is an optional parameter, ranging from 0 to 65535, with a default of 4000
CTXLIVETM
Context live time(s)
It is an optional parameter, ranging from 0 to 65535, with a default of 1200
NAME
Alias
It is an optional parameter, ranging from 0 to 50 characters. It may be the same as the office name
Example: To add the MGC static data of an MGCF office with all the parameters adopting default value, the specific command is as follows. ADD MGCSCFG:MEGACO=1,ACTTM=600,ACTCHK=ON,W AITTM=7800,PTRYNUM=5,PTRYTM=4000,CTXLIVETM=1 200,MGACTTM=600; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating MGW Static Data Template Prerequisites
Before the operation, it is required to confirm: �
The data configuration of the local office is completed.
�
The MML Terminal window is opened.
Context
Perform this procedure to set the template used by the MGW static data configuration.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11;
122
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
2. Create an MGW static data template. The command is ADD MGSTPL. Table 51 describes the main parameters in the ADD MGSTPL command. TABLE 51 PARAMETERS IN THE ADD MGSTPL COMMAND Parameter Name
Parameter Description
Instruction
NAME
Alias
This is a mandatory parameter with a length ranging from 1 to 50 characters. It can be consistent with the office name.
ID
Static data template number
The number of a template, ranging from 1 to 255
MEGACO
MEGACO version number
This parameter must be consistent with that negotiated with the MGW.
ACTCHK
Gateway activation detection switch
It is configured as ON by default
PRTTM
Transient protection timer (s)
It ranges from 1 to 180. Type the default value 10
PRT
Transient protection switch
It is configured as ON by default.
PENDTM
Interval of PEND messages (ms)
It ranges from 0 to 3600, with a default of 200
LNGTM
Maximum existence time (ms)
It ranges from 0 to 65535, with a default of 15000
RTRNTM
Retransmission timer (ms)
It ranges from 0 to 65535, with a default of 3800
MTRNNUM
Maximum transmission times
It ranges from 0 to 15, with a default of 1
TRNMD
Retransmission mode
CTYPE
H.248 protocol coding mode
�
FIXED: Duration unchangeable
�
UNFIXED: Duration changeable
It must be consistent with that negotiated with the MGW data configuration
Example: Add an MGW static data template with the following requirements.
Confidential and Proprietary Information of ZTE CORPORATION
123
ZXWN MSCS Data Configuration Guide(MGCF)
�
Template ID: 1
�
User name: IM-MGW101
�
Other parameters: default value.
The specific command is as follows. ADD MGSTPL:NAME="IM-MGW101",MEGACO=1,ACTCHK =ON,PRTTM=10,PRT=ON,PENDTM=200,LNGTM=15000,R TRNTM=3800,MTRNNUM=1,TRNMD=UNFIXED,CTYPE=TE XT; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating MGW Static Data Prerequisites
Before the operation, it is required to confirm: �
The MGW topological node is configured.
�
The MGW static data template is configured.
�
The MGCF voice batch processing is finished.
�
The MML Terminal window is opened.
Context
Perform this procedure to configure the static data for each IM-MGW under the MGCF.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create MGW static data. The command is ADD MGSCFG. Table 52 describes the main parameters in the ADD MGSCFG command. TABLE 52 PARAMETERS IN THE ADD MGSCFG COMMAND Parameter Name
124
Parameter Description
Instruction
ID
Gateway number
It is a mandatory parameter for configuring the node number of this gateway, ranging from 1 to 2048. It is associated with the node ID specified by the ADD TOPO command.
TPLID
Static data template number
It is a mandatory parameter associated with the template number configured on
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction the IM-MGW static data template configuration.
TONEID
Service tone template ID
It is an optional parameter ranging from 0 to 65535. It uses the template ID specified in the BADD STONE command.
LANGID
Language description template ID
It is an optional parameter, ranging from 0 to 65535. It uses the template ID specified in the BADD STONE command.
NAME
Alias
It is a mandatory parameter, ranging from 0 to 50 characters. It may be the same as the office name
BKMGC
Backup MGC information
It is an optional parameter, with a default of NULL
PKGLOST
Threshold of package loss rate (0.01%)
It is an optional parameter, ranging from 0 to 10000, with a default of 10
JIT
Threshold of network jittering (ms)
It is an optional parameter, ranging from 0 to 10000, with a default of 50
DELAY
Threshold of network delay (ms)
It is an optional parameter, ranging from 0 to 5000, with a default of 200
MGW tandem
It is an optional parameter for setting whether this MGW is used for the tandem function. Type the default value NO
MGW
Example: Create static data for an MGW with the following requirements. �
MGW office ID: 101
�
Static configuration template ID: 1
�
Alias: IM-MGW101
The specific command is as follows. ADD MGSCFG:ID=101,NAME="IM-MGW101",TPLID=1,TO NEID=1,LANGID=1,PKGLOST=10,JIT=50,DELAY=200,M GW=NO; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
125
ZXWN MSCS Data Configuration Guide(MGCF)
Creating a TID Analyzer Prerequisites
Before the operation, it is required to confirm: �
The data configuration of the local office is completed.
�
The MML Terminal window is opened.
Context
The TID analysis configuration is necessary for the H.248 server to perform the character string conversion of the CIC. The H.248 server converts the CIC on the server to the corresponding character string according to the mode configured by the TID analysis. Then it sends this character string to the gateway's H.248 for analyzing and operating the corresponded CIC. Since the form of the terminals used by the Mn interface is relatively fixed currently, you may adopt the default configuration.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create the TID analyzer. The command is ADD TIDANL. Table 53 describes the main parameters in the ADD TIDANL command. TABLE 53 PARAMETERS IN THE ADD TIDANL COMMAND Parameter Name
Parameter Description
Instruction
User alias
It is a mandatory parameter, ranging from 1 to 50 characters. It may be the same as the office name.
PREV
TID analyzer index
It is an optional parameter. It is the global number of the current analyzer for TID analyzer entry to use, ranging from 1 to 255.
TIDPFX
TID prefix
It is an optional parameter with a default of TDM
NAME
TAG
126
Analysis result flag. Options include USER, TRUNK, RTP, ATM, ROOT and PCM+IDX.
Confidential and Proprietary Information of ZTE CORPORATION
It is an optional parameter, with a default of TRUNK (trunk type). Example: “TDM_5/1” is a trunk terminal form. “TDM” is the TID prefix, “_” is the PCM separation mark, “5” is the PCM number, "/” is the IDX (time slot index) is the separation mark, and “1” is the time slot number
Chapter 4 MGCF-IM-MGW Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction
PCMSPR
PCM flag
It is an optional parameter, with a default of “ ”.
IDXSPR
IDX flag
It is an optional parameter, with a default of “/”.
PCM start location
It is an optional parameter, ranging from 0 to 255, with a default of 1, indicating that the PCM number starts from the first digit of the PCM flag.
PCM end location
It is an optional parameter, ranging from 0 to 255, with a default of 0. Since there is a PCM flag, the End Location is meaningless.
IDX start location
It is an optional parameter, ranging from 0 to 255, with a default of 1, indicating that the time slot number starts from the first digit of the IDX flag.
IDX end location
It is an optional parameter, ranging from 0 to 255, with a default of 0. Since there is an IDX flag, the End Location is meaningless.
PCMPOS1
PCMPOS2
IDXPOS1
IDXPOS2
Example: Create a TID analyzer with the following requirements. �
MGW office ID: 101
�
TID index: 1
�
Alias: IM-MGW101
�
Other parameters: default value.
The command is: ADD TIDANL:NAME="IM-MGW101",PREV=1,TIDPFX="TD M",TAG=TRUNK,PCMSPR="_",IDXSPR="/",PCMPOS1=1,P CMPOS2=0,IDXPOS1=1,IDXPOS2=0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a TID Analysis Entrance Prerequisites
Before the operation, it is required to confirm: �
The MGW topological node is configured.
Confidential and Proprietary Information of ZTE CORPORATION
127
ZXWN MSCS Data Configuration Guide(MGCF)
Context Steps
�
The TID analyzer configuration is completed.
�
The MML Terminal window is opened.
Perform this procedure to configure a TID analyzer entrance. 1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a TID analysis entrance. The command is ADD TIDEN TR. Table 54 describes the main parameters in the ADD TIDENTR command. TABLE 54 PARAMETERS IN THE ADD TIDENTR COMMAND Parameter Name
Parameter Description
Instruction
ND
Gateway
It is a mandatory parameter. It is the node ID allocated by the topological node configuration.
TIDENTID
TID analyzer index
It is a mandatory parameter associating the TID analyzer ID specified in the TID analyzer configuration.
TIDTPLID
TID template number
By default, the system already creates a TID template whose ID is 1. You may query it with the SHOW TIDTPL command.
User Alias
It is a mandatory parameter with a length ranging from 0 to 50 characters. It may be the same as the office name.
NAME
Example: Create a TID analyzer entry with the following requirements. �
MGW office ID: 101
�
TID analyzer index: 1
�
TID template ID: 1
�
Alias: IM-MGW101
The specific command is as follows. ADD TIDENTR:ND=101,TIDENTID=1,TIDTPLID=1,NAME ="IM-MGW101"; END OF STEPS Result
128
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter
5
MGCF-SIP Office Interconnection Data Configuration Table of Contents Overview........................................................................ 129 SIPCC Data Configuration ................................................. 130 SIP Protocol Stack Configuration........................................ 141 Creating an RTP Trunk Group ............................................ 160
Overview The configuration flow of MGCF-SIP office interconnection data is shown in Table 55. TABLE 55 FLOW DESCRIPTION No.
1
2
Operations
Instructions
SIP call control data configuration
Including local office data configuration, adjacent office data configuration, SIP office direction data configuration, TOPO configuration, trunk data configuration, and number analysis data configuration
SIP protocol stack data configuration
Including IP link data configuration, host data configuration, adjacent host data configuration, UDP bear data configuration, SIP signaling data configuration, IP distribution policy data configuration, SIP signaling route data configuration, and SIP signaling route set data configuration
Confidential and Proprietary Information of ZTE CORPORATION
129
ZXWN MSCS Data Configuration Guide(MGCF)
SIPCC Data Configuration Overview This section introduces how to configure the signaling interworking with the adjacent offices through the SIP protocol. Steps
Operations
1
Interface address configuration
2
Creating a static route
3
Creating a SIP adjacent office
4
5
Instructions Create the IP protocol stack for the IP interface over the SIP protocol, and configure virtual interface address, refer to Creating a Virtual Interface Address Create the static route for the IP interface over the SIP protocol, refer to Creating a Static Route Create an adjacent office connected with the MGCF through SIP protocol
Commands
INTERFACE ADD IP ADDRESS
ADD IP ROUTE
ADD ADJOFC
Creating a SIP office direction
Create a SIP office direction connected with the MGCF through SIP protocol.
ADD SIPOFC
Creating SIP adjacent office topology node
Create the topology relationship between MGCF node and SIP adjacent office node
ADD TOPO
Creating a SIP Adjacent Office Prerequisites
130
Before the operation, it is required to confirm: �
The exchange ID to be configured is known.
�
The local office data configuration is completed.
�
The adjacent office ID range is set in the Resource Management system.
�
The MML Terminal window is opened.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
Context
This section introduces how to configure an adjacent office connected with the MGCF through SIP protocol, which is I-CSCF, S-CSCF, P-CSCF or BGCF in general.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an adjacent office (such as CSCF or BGCF) connected with the MGCF through SIP protocol by executing command ADD ADJOFC. The explanation of the main parameters in command ADD ADJOFC is shown in Table 56. TABLE 56 PARAMETERS FOR CREATING A SIP ADJACENT OFFICE Parameter Name
Parameter Description
Instruction
ID
Office ID
It is a mandatory parameter, ranging from 1 to 3000. During the whole network planning, this parameter is generally configured to the adjacent office ID
NAME
Alias
It is a mandatory parameter, defined by users
NET
Network type
It is a mandatory parameter. Select the network type of the SPC used for the connection between the local office and the adjacent office when the local office is configured with multiple signaling points. If the local office is only configured with only one signaling point, the network type of this signaling point is selected by default. For the adjacent office connected with the MGCF through SIP protocol, this parameter is meaningless
SPCFMT
Signaling Point Code Format
TRIPLE_DEC is selected by default
SPCTYPE
Signaling Point Code type
Configure it according to the signaling point plan
Confidential and Proprietary Information of ZTE CORPORATION
131
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
Signaling Point Code
It is a mandatory parameter. It is the SPC used for the connection between the local office and the adjacent office. For the adjacent office connected with the MGCF through SIP protocol, this parameter needs not be configured and is meaningless. Just enter a non-zero value
Area code
It is an optional parameter. Enter the code of the area where the adjacent office is located. This parameter has influence on the area code added for the calling number
Office Type
It is a mandatory parameter. Configure the adjacent office connected with the MSCS through SIP protocol to LOCAL&DOMTOLL&IP
ASSOTYPE
Association type
It is an optional parameter. Select AM_SURE (associated mode), or AM_QUASI (quasi-associated mode) according to the networking condition
SPTYPE
Signaling point type, including SEP, STP, and STEP
Select it according to the role of the adjacent office in the signaling network
DPC
RC
OFCTYPE
Subservice function, including �
INTERNATIONAL (International signaling point code)
�
INTERNATIONAL STANDBY (International standby signaling point code)
SSF
132
�
NATIONAL (National signaling point code)
�
NATIONAL STANDBY (National standby signaling point code).
Confidential and Proprietary Information of ZTE CORPORATION
It is an optional parameter. NATIONAL is generally selected in China
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction
Office Attribute, including: ISNI (Has ISNI Function)
TAG
TRANS (Translate Node)
It is an optional parameter
TEST (Need Test Info:0X02/0X01)
TEST
Test flag
It is an optional parameter. In general, select this parameter, which is used to set whether the MTP3 link actively initiates the link test after going into service status It is an optional parameter with a default of NO. It is used for SCCP to judge whether to use the LUDT message.
BANDFLAG
Broadband Attribute
The maximum length of a broadband link message is 4,000, and that of a narrowband link message is 255. Because the MTP layer does not have the segmentation function, the incorrect configuration of this parameter probably causes the long packet to be discarded. Select YES when all the links between two SPs are SIGTRAN or ATM signaling links.
Protocol types, including: �
CHINA (China)
�
ITU (International Telecommunications Union)
�
ANSI (American National Standards Institute).
PRTCTYPE
It is an optional parameter. CHINA and ITU are used for the NO.7 signaling networking of the ITU standards. ANSI is used for the No.7 signaling networking of the American standards. In general, national offices select CHINA, while international offices select ITU
Confidential and Proprietary Information of ZTE CORPORATION
133
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
CLST
Parameter Description
Instruction
Cluster ID
It is an optional parameter within 0~65535. In general, select the default value 65535. It is valid when the protocol type of the adjacent office is “ANSI”. The signaling point connected to the signaling transfer point belongs to the corresponding cluster. The cluster ID is configured in the command ADD CLST
Office Info, including: CIC_PCM (CIC starts the load sharing according to the PCM code mode) BLOCK (Manual block status)
INFO
EVEN_CIC (The office controls the even CIC when CIC resource contention occurs)
It is an optional parameter and the default value is CIC_PCM
CALLING (Calling transform is allowed) CALLED (Called transform is allowed) MOD24_CIC (CIC mode with 24 mode) TEST (Dynamic observation) RELATEDOFC1
Related Office ID
It is an optional parameter ranging from 0 to 3000
Office Extend Info, including:
INFOEX
134
�
SIGBRDCST (Support Signa ling Broadcast Message)
�
MTP (Hongkong MTP Standard)
�
DUPU ( Screen DUPU message)
�
SUA_REC_DT1 (Receive SUA message and handle it as DT1 message)
�
SUA_SND_DT1 (Send SUA message and handle it as DT1
Confidential and Proprietary Information of ZTE CORPORATION
It is an optional parameter
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction
message without SN.) �
OPEN_TG_RES (Open outter trunk group resource)
For example, add the S-CSCF. The office ID is 12, the office type is LOCAL&DOMTOLL&IP, the signaling point code type is 24, the signaling point code is 3.12.1, the area code is 25, the association type is AM_SURE, the signalng point type is SEP. For the other parameters, adopt the default value. The command is as follows: ADD ADJOFC:ID=12,NAME="SCSCF",NET=1,OFCTYPE="L OCAL"&"DOMTOLL"&"IP",SPCFMT=TRIPLE_DEC,SPCTYPE=2 4,DPC="3.12.1",RC="25",ASSOTYPE=AM_SURE,SPTYPE =SEP,SSF=NATIONAL,SUBPROTTYPE=DEFAULT,TEST=YE S,BANDFLAG=YES,PRTCTYPE=CHINA,CLST=65535,INFO ="CIC_PCM",RELATEDOFC1=0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating SIP Office Direction Prerequisites
Before the operation, it is required to confirm: �
The local office data is configured.
�
The SIP adjacent office is configured.
�
The MML Terminal window is opened.
Context
This section introduces how to create a SIP office direction connected with the MGCF through SIP protocol.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a SIP office direction. The command is ADD SIPOFC. Table 57 describes the main parameters in the ADD SIPOFC command.
Confidential and Proprietary Information of ZTE CORPORATION
135
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 57 PARAMETERS IN THE COMMAND ADD SIPOFC Parameter Name
OFCID
Parameter Description
Instruction
Office ID
It is a mandatory parameter, ranging from 1 to 3000. Adopt the SIP adjacent office ID configured in the ADD ADJOFC command
URL type, includes URL
�
TEL: TEL format
�
URI: SIP URI format
�
IP: SIP IP format
MGCF Charging Mode, includes BTYPE
ENOPT
�
IN: Inner Bill
�
Rf: Rf Bill
Enable Option
It is an optional parameter with a default value URI
It is an optional parameter with a default value IN
Select SIP ESSO&SIP PRECOND
Example: Create a S-CSCF SIP office with the following requirements. �
SIP office ID: 12
�
URL type: URI
�
MGCF charging mode: IN
�
Enable option: SIP ESSO& SIP PRECOND
The specific command is as follows. ADD SIPOFC:OFCID=12,URL=URI,BYPASS=NO,BYPASS PCT=80,BYPASSPRD=5,BYPASSTLEN=30,BYPASSLEV=L N,BYPASSCALLNUM=1,BTYPE=IN,OVERLAP=RINVT,CFIN FO=HIS,PBRTFMT=EQUAL,DTMF=IN,FMT4733=97,SIPRE L=NO,ENOPT="SIP ESSO"&"SIP PRECOND"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating SIP Adjacent Office Topology Node Prerequisites
Before the operation, it is required to confirm: �
136
The encoding and decoding speech template is configured.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
�
The range of the topological node number is configured in the resource management.
�
The MML Terminal window is opened.
Context
Perform this procedure to create the topology relationship between MGCF node and SIP adjacent office node. This command is used to configure the adjacent NE information, including equipment type, bearer type and attributes, user plane version, encoding and decoding template, and other information.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a SIP adjacent office topology node. The command is ADD TOPO. Table 58 describes the main parameters in the ADD TOPO command. TABLE 58 PARAMETERS IN THE ADD TOPO COMMAND Parameter Name
Parameter Description
Topological node ID
ID
OFCID
Office ID
Instruction It is a mandatory parameter to define ID of this node, ranging from 1 to 2,048. It is recommended that the ID and office No. of a topological node are consistent It is a mandatory parameter for specifying the office ID of this topological node. This parameter must be defined by the ADD ADJOFC command first. In this case, type the actual IM-MGW office number
NAME
CODECID
Alias
It is a mandatory parameter for naming this topological node, with a length ranging from 1 to 50 characters.
CODEC identity
It is a mandatory parameter for specify the CODEC template used by this topological node. This parameter must be defined by the ADD CODECTPL command first.
Confidential and Proprietary Information of ZTE CORPORATION
137
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
ETYPE
Parameter Description
Equipment type
Instruction This parameter is used to specify the NE type of this topological node. Select R4GW for an MGW node
PROTTYPE
IPVER
ATTR
Protocol type
Select H.248 for Mn interface.
IP version of the node
It is the IP protocol version supported between nodes. Select IPV4 or IPV6 according to the actual conditions. Currently, IPV4 is supported.
Bearer attributes
This parameter is only valid for the node with the type of R4GW (MGW). The bearer types supported by MGW are BNCAAL1, BNCAAL2, BNCAAL1S, BNCIPRTP, and BNCTDM. MGW can one or more of these types of bearers. In general, select BNCAAL2, BNCIPRTP, and BNCTDM
UPVER
User plane protocol version of RNC or MGW Extended attributes (tunnel mode), including: �
NOTUNL (None tunnel mode)
�
RTUNL (Rapid tunnel mode)
ATTR2
�
DTUNL (Delay tunnel mode)
Signaling transfer mode, including: TRFMOD
138
MCINTF (Mc interface signal transfer mode)
Confidential and Proprietary Information of ZTE CORPORATION
This parameter is used to set the user plane version of this node. In general, select V2
This parameter is used to set which tunnel mode is adopted for bearer establishment when this node supports the IP/RTP bearer. The default value is NOTUNL (None tunnel mode). In general, select DTUNL (Delay tunnel mode) for an MGW topological node.
This parameter is used to set which mode is used by the topology for reporting when it detects CNG or CED fax signals. The default value is MCINTF
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction
Error SDU control, including options: YES: The user plane entity implements error inspection, and sets the FQC bit position according to the result. It will transmit all frames includes the error frames to the user plane layer. During a call, the error packet control parameter delerrsdu=Yes, which is delivered by the terminal established by MGW on the Mc interface. The error packet control parameter deliveryOfErroneousSDU is YES, NA, NA during RAB assignment. UPERRCTRL
NO: The user plane entity implements the error inspection. It will directly discard the error frame. During a call, the error packet control parameter delerrsdu=No, which is delivered by the terminal established by MGW on the Mc interface. The error packet control parameter deliveryOfErroneousSDU is NO, NA, NA during RAB assignment.
This parameter regulates the handling method of the user plane for error frames. It is only valid for MGW-type and RNC-type topological node. The default value is YES
INVALIDTION: The user plane entity does not implement the error inspection. During a call, the error packet control parameter delerrsdu=NA, which is delivered
Confidential and Proprietary Information of ZTE CORPORATION
139
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
by the terminal established by MGW on the Mc interface. The error packet control parameter deliveryOfErroneousSDU is NA, NA, NA during RAB assignment.
DTMFTC
Tandem office send DTMF use TC mode, including two options, NO and YES
This parameter is used to set whether the tandem office uses the TC resources during DTMF number delivery. The default value is NO It contains the following options.
MGWCON
MGW congestion reporting capability
�
SMGWCON (Standard MGW congestion event)
�
CMGWCON (Custom MGW congestion event).
The default value is SMGWCON.
Example: Create a topological node with the following requirements. �
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=12,OFCID=12,NAME="SCSCF",CODECID =1,ETYPE=MSCVLR,PROTTYPE=SIP,IPVER=IPV4,ATTR ="BNCIPRTP",ATTR2=NOTUNL,TRFMOD=MCINTF,UPERRCT RL=YES,DTMFTC=NO,MGWCON=SMGWCON,AUTOFAX=YE S,OOBTC=NO,BCUID=0,SENDCAP=NO,G711TRAN=NO,BI CCDTMF=TRANSPARENT,IPBCP2833=BYMGW,BICCDTMP PER=0,AOIPPRO=PRIVATE; END OF STEPS Result
140
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
SIP Protocol Stack Configuration Overview When the MSCS serves as a MGCF, after the local office data configuration is completed, it is required to add the basic SIP configuration, including the following contents. Steps
Operations
Instructions
Commands
1
Creating an IP link
Create an IP bearer link used for SIP signaling.
ADD IPLINK
2
Setting the capacity for a SIP module
Configure the capacity for a SIP module according to the system capacity
SET SIPCAPA
3
Creating a domain where the MGCF belongs
Creating the domain of MGCF system
ADD REALM
4
Creating a MGCF host
Creating MFCF host name, type and IP address
ADD HOST
5
Creating route selector
A routing selector is a set of multiple number analyses, used to store the analyses of MSISDN, IP numbers and domain addresses in the IMS domain
ADD RTSEL
6
Creating a service group
Service groups are used to specify the routing selector for a number.
ADD SRVG
7
Creating an adjacent host
Create an adjacent host (CSCF or BGCF) of the MGCF.
ADD ADJHOST
8
Creating UDP bear
Create two modes of UDP bear: LOCAL_VALID and REMOTE_VALID
ADD UDPBR
Confidential and Proprietary Information of ZTE CORPORATION
141
ZXWN MSCS Data Configuration Guide(MGCF)
Steps
Operations
Instructions
Commands
Creating a SIP signaling link
For the adjacent office connected with the MGCF through SIP, it is required to configure SIP signaling links.
ADD SIPLNK
Creating a SIP signaling route
Create signaling routes. Each SIP signaling route contains at most 12 SIP signaling links.
ADD SIPRT
Creating a SIP signaling route set
Create signaling route sets. Each SIP signaling route set contains at most 4 SIP signaling routes.
ADD SIPRTS
12
Creating IP Distribution Policy
When the MGCF can be configured with multiple IP addresses, the SIP on each IP needs to be distributed to different signaling SMP modules for processing.
ADD IPDPLC
13
Creating URI analysis
The URI analysis is used to analyze domain names on routes.
ADD URI
9
10
11
Creating an IP Link Prerequisites
Before the operation, it is required to confirm: �
The SIP adjacent office is created.
�
The SMP module with SIP attribute is added.
�
The MML Terminal window is opened.
Context
This section introduces how to create an IP bearer link used for SIP signaling. Different bearer information is configured for different peer-end addresses.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11;
142
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
2. Create an IP link used for SIP signaling transfer by executing command ADD IPLINK. The explanation of the main parameters in command ADD IPLINK is shown in Table 59. TABLE 59 PARAMETERS IN THE ADD IPLINK COMMAND Parameter Name
Parameter Description
Instruction
Peer-end adjacent office ID
It is a mandatory parameter. Enter ID of the adjacent office connected with this link, which is associated with the adjacent office ID configured in the adjacent office configuration
Module No.
It is a mandatory parameter. It is the No. of the SMP module where the Socket associated with the IP link belongs, which should be consistent with MODULE in command ADD MODULE
IP link ID
It is a mandatory parameter, which is an integer, ranging from 1 to 1024. It is used to identify an IP link. It cannot be repeated
LOCIP
Local IP
It is a mandatory parameter. Input the IP address of the local end of this link, in the format of “Local IP type-Local IP VPN-Local IP address”. At present, the IPV4 address type is used in general
LOCPORT
Local port No.
It is usually set to 5060
REMIP
Peer-end IP
It is a mandatory parameter. Input the IP address of the peer end of this link, in the format of “Peer-end IP address type-Peer-end IP address VPN-Peer-end IP address”. At present, the IPV4 address type is used in general
REMPORT
Peer-end port No.
It is usually set to 5060
Transfer protocol type
It is the transfer protocol type used by this link, which can be set to TCP or UDP. The transfer protocol type should be consistent with that used by the peer-end IP link
TCP connection type
If the PRO is configured as TCP, this option can set the local end as the CLT (client) or the SVR (server) of the TCP. If the PRO is configured as UDP, it is not required to configure this option
OFCID
MODULE
ID
PRO
TCPROTO
Confidential and Proprietary Information of ZTE CORPORATION
143
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
TSTIMER
Duration (ms) of the link test timer
If it is not required to test the link, set it to 0
Example: Create a bearer link between the MGCF and the S-CSCF with the following requirements. �
S-CSCF office ID: 12
�
No. of the SMP module managing this link: 3
�
User alias: IPLINK-12
�
IP link ID: 12
�
Local IP: 10.1.44.77
�
Peer-end IP: 10.1.33.11
�
Local port No. and peer-end port No.: 5060
�
Transfer protocol type: UDP
�
Other parameters: Adopt the default values.
The command is: ADD IPLINK:OFCID=12,MODULE=3,NAME="IPLINK-12",I D=12,LOCIP="IPv4"-"0"-"10.1.44.77",LOCPORT=5060,RE MIP="IPv4"-"0"-"10.1.33.11",REMPORT=5060,PRO=UDP,T CPROTO=NULL,TSTIMER=0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Setting the Capacity for a SIP Module Prerequisites
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The SMP module with SIP attribute is added.
�
The MML Terminal window is opened.
Context
This section introduces how to set the capacity for a SIP module according to the system capacity.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Set the capacity for the SIP module by executing command SET SIPCAPA.
144
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
The explanation of the main parameters in command SET SIPC APA is shown in Table 60. TABLE 60 PARAMETERS IN THE SET SIPCAPA COMMAND Parameter Name
SIPSOCKET
SIPTR
SIPTU
SIPTUMSG
Parameter Description
Instruction
SIP SOCKET data area capacity
It is an optional parameter, which is an integer, ranging from 1 to 1024. It is configured according to the system capacity
SIP TR data area capacity
It is an optional parameter, which is an integer, ranging from 1 to 30000. It is configured according to the system capacity
SIP TU data area capacity
It is an optional parameter, which is an integer, ranging from 1 to 15000. It is configured according to the system capacity
SIP TUMSG data area capacity
It is an optional parameter, which is an integer, ranging from 1 to 7000. It is configured according to the system capacity
Example: Set the capacity for the SIP module with the following requirements. �
SIP SOCKET data area capacity: 128
�
SIP TU data area capacity: 15000
�
SIP TU data area capacity: 9000
�
SIP TUMSG data area capacity: 4000
The command is as follows. SET SIPCAPA:SIPSOCKET=128,SIPTR=15000,SIPTU=90 00,SIPTUMSG=4000; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a Domain where the MGCF Belongs Prerequisites
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
Confidential and Proprietary Information of ZTE CORPORATION
145
ZXWN MSCS Data Configuration Guide(MGCF)
�
The MML Terminal window is opened.
Context
The MGCF system can be configured with one or more domains. In general, it is configured with one domain.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a domain by executing command ADD REALM. The explanation of the main parameters in command ADD REALM is shown in Table 61. TABLE 61 PARAMETERS IN THE ADD REALM COMMAND Parameter Name
Parameter Description
Instruction
ID
Domain ID
It is an integer, ranging from 1 to 65534. In general, the MGCF is configured with one domain whose ID is set to 1
Domain name
It is a mandatory parameter, consisting of 1 to 63 characters. When the host name is set, it is required to add the domain name of the host after it
REALM
Example: Add a domain with the following requirements. �
Domain ID: 1
�
Domain name: zte.com
The command is as follows. ADD REALM:ID=1,REALM="zte.com"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a MGCF Host Prerequisites
Context
146
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The MML Terminal window is opened.
The host name of the local office must be configured when the SIP function is used. The MGCF can have one or more hosts, and each host belongs to one domain. When SIP messages are sent, the host information is used to construct the parameter contents in messages “From” and “Contact”.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a MGCF host by executing command ADD HOST. The explanation of the main parameters in command ADD HOST is shown in Table 62. TABLE 62 PARAMETERS IN THE ADD HOST COMMAND Parameter Name
Parameter Description
Instruction
ID
Host ID
It is the ID of this host, which is an integer, ranging from 1 to 65534. It can not be repeated
HOST
Host name
It is a mandatory parameter, consisting of 1 to 63 characters. The host name is composed of short description and domain name. For example, a host name is host1.zte.com, where zte.com is the domain name
IPV4
IPV4
IPV4 address of this host
IPV6
IPV6
IPV6 address of this host
Example: Add a host with the following requirements. �
Host ID: 1
�
Host name: host1.zte.com
�
IPV4 address: 11.11.11.1.
The command is: ADD HOST:ID=1,HOST="host1.zte.com",IPV4="11.11.11. 1"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating Route Selector Prerequisites
Before the operation, it is required to confirm: The MML Terminal window is opened.
Context
To implement the MGCF function, SIP routing selectors must be configured. A routing selector is a set of multiple number analyses, used to store the analyses of MSISDN, IP numbers and domain
Confidential and Proprietary Information of ZTE CORPORATION
147
ZXWN MSCS Data Configuration Guide(MGCF)
addresses in the IMS domain. In general, one routing selector is configured. Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a SIP routing selector by executing command ADD RTSEL. The explanation of the main parameters in command ADD RTSEL is shown in Table 63. TABLE 63 PARAMETERS IN THE ADD RTSEL COMMAND Parameter Name
ID
NAME
Parameter Description
Instruction
SIP route selector ID
It is a mandatory parameter, which is an integer, ranging from 1 to 65534
SIP routing selector name
It is a mandatory parameter, consisting of 0~50 characters. It is used to specify a routing selector to make it easily recognized
Example: Create a SIP route selector with the following requirements. �
SIP route selector ID: 1
�
SIP route selector name: RTS1.
The command is: ADD RTSEL:ID=1, NAME="RTS1"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating Service Group Prerequisites
Context
148
Before the operation, it is required to confirm: �
The routing selector is added.
�
The MML Terminal window is opened.
Service groups are used to specify the routing selector for a number. Service groups are used by SIP signaling links and entry poli-
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
cies. If more service groups are needed, add new service groups after setting the default service group. Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Creating a service group by executing command ADD SRVG. The explanation of the main parameters in command ADD SRVG is shown in Table 64. TABLE 64 PARAMETERS IN THE ADD SRVG COMMAND Parameter Name
Parameter Description
Instruction
ID
Service group ID
It is the service group ID, which is an integer, ranging from 1 to 65534. It is numbered from 1
NAME
Service group name
It is a mandatory parameter, consisting of 1~50 characters. It is used to specify a service group
RTSEL
Routing selector
Enter the routing selector ID, which is associated with the ID in command ADD RTSEL
CHGID
Charge Policy Index
It is an integer, ranging from 1 to 65535
IOI
Inter Operator Identifier
It is an optional parameter, consisting of 0~63 characters.
Example: Create a service group with the following requirements. �
Service group ID: 1
�
Corresponding route selector ID of the service group: 1
�
The service group is not associated with the billing policy.
The command is: ADD SRVG:NAME="SRVG1",ID=1,RTSEL=1; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating an Adjacent Host Prerequisites
Before the operation, it is required to confirm:
Confidential and Proprietary Information of ZTE CORPORATION
149
ZXWN MSCS Data Configuration Guide(MGCF)
�
The SIP adjacent office is created.
�
The MML Terminal window is opened.
Context
This section introduces how to create an adjacent host (CSCF or BGCF) of the MGCF. Multiple adjacent hosts can belong to the same adjacent office. Each SIP signaling link corresponds to one adjacent host of the MGCF, and it refers to the host ID of the adjacent host.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an adjacent host by executing command ADD ADJHO ST. The explanation of the main parameters in command ADD ADJHOST is shown in Table 65. TABLE 65 PARAMETERS IN THE ADD ADJHOST COMMAND Parameter Name
ID
HOSTNAME
REALM
SRVGRP
Parameter Description
Instruction
Adjacent host ID
It is the ID of the adjacent office where the adjacent host belongs, which is consistent with the ID in command ADD ADJOFC.
Host name
It is a mandatory parameter, consisting of 1 to 63 characters. It should be consistent with that of the peer end. The host name is composed of short description and domain name. For example, a host name is scscf.zte.com, where zte.com is the domain name
Domain name
It consists of 0 to 63 characters. It is the name of the domain where the adjacent host belongs, which should be consistent with that of the peer end
Service Group Number
If the URL in ADD SIPOFC is not configured as URI, this option can be set to the default service group number. If URL in ADD SIPOFC is configured as URI, selected the related service group number
Example: Create a SCSCF adjacent office with the following requirements.
150
�
Adjacent host name: SCSCF
�
Adjacent host ID: 12
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
�
Name of the domain where the host belongs: zte.com
�
Topology level: UPPER
�
Service group number: 1
The command is: ADD ADJHOST:ID=12,HOSTNAME="SCSCF",REALM="zte. com",SRVGRP=1; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating UDP Bear Prerequisites
Before the operation, it is required to confirm: �
The SIP adjacent office is created.
�
The MML Terminal window is opened.
Context
This section introduces how to create a UDP bear. Two modes of UDP bear are required to be configured. LOCAL_VALID mode of UDP bear is for relating the local UDP bear ID in ADD IPDPLC command. REMOTE_VALID mode of UDP bear is for relating the remote UDP bear ID in ADD SIPLNK command.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create UDP bear. The command is ADD UDPBR. The explanation of the main parameters in command ADD UDPBR is shown in Table 66. TABLE 66 PARAMETERS IN THE ADD UDPBR COMMAND Parameter Name
Parameter Description
Instruction
ID
Bear ID
It is a mandatory parameter to define bear ID, ranging from 1 to 65,535.
Alias
It is an optional parameter for naming the bear, with a length ranging from 0 to 50 characters.
NAME
Confidential and Proprietary Information of ZTE CORPORATION
151
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
UDP IP Mode, includes �
LOCAL_VALID: Local IP valid
�
REMOTE_VALID: Remote IP valid
IPMODE
The default value is LOCAL_VALID.
ADJHOST
Adjacent Host
Select the adjacent host ID configured in ADD ADJHOST
IPLINK
IP Link ID
Select the IP link ID configured in ADD IPLINK
Destination IP Address Type, includes DSTADDRTYPE
�
IPV4: IPV4 addres type
�
IPV6: IPV6 addres type
Currently, IPV4 is supported.
DSTV4ADDR
Destination IPV4
Destination IPV4 address
DSTVPN
Destination VPN ID
Destination VPN ID
DSTPORT
Destination port
Destination port
Example, Create a UDP bear with the following requirements. �
Bear ID: 1
�
Alias: LOCAL
�
UDP IP Mode: LOCAL_VALID
The command is as follows. ADD UDPBR:ID=1,NAME="LOCAL",IPMODE=LOCAL_VALI D,ADJHOST=0,IPLINK=12,DSTADDRTYPE=IPV4,DSTVPN =0,DSTPORT=0; Example, Create a UDP bear with the following requirements. �
Bear ID: 2
�
Alias: REMOTE
�
UDP IP Mode: REMOTE_VALID
The command is as follows. ADD UDPBR:ID=2,NAME="REMOTE",IPMODE=REMOTE_V ALID,ADJHOST=12,IPLINK=0,DSTADDRTYPE=IPV4,DSTV 4ADDR="10.1.33.11",DSTVPN=0,DSTPORT=5060; END OF STEPS Result
152
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
Creating a SIP Signaling Link Prerequisites
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The adjacent host is added.
�
The MML Terminal window is opened.
Context
Signaling links are the physical channels bearing signaling messages. For the adjacent office connected with the MGCF through SIP, it is required to configure SIP signaling links.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a SIP signaling link by executing command ADD SIPL NK. The explanation of the main parameters in command ADD SIPLNK is shown in Table 67. TABLE 67 PARAMETERS IN THE ADD SIPLNK COOMMAND Parameter Name
Parameter Description
Instruction
ID
Signaling link ID
It is the SIP signaling link ID, which is an integer, ranging from 1 to 65534. It is referred to in the SIP signaling route configuration
NAME
Signaling link name
It is a mandatory parameter, consisting of 0~50 characters. It is the SIP signaling link name
Bearer ID
It is a mandatory parameter. It is the IP link ID associated with this SIP signaling link, which is consistent with the ID in command ADD IPLINK
Sending Heart Beat Interval(s)
It is the interval of sending link heartbeat test messages, used to test the link connection. It ranges from 0 to 3600 (s). If this option is set to 0, means disable heartbeat monitor.
BRID
HBTIME
Example: Create a SIP signaling link with the following requirements. �
Link ID: 12
�
Link name: SCSCFLINK
Confidential and Proprietary Information of ZTE CORPORATION
153
ZXWN MSCS Data Configuration Guide(MGCF)
�
Bear ID: 2
�
Adjacent office connected with this link: S-CSCF
The command is: ADD SIPLNK:ID=12,NAME="SCSCFLINK",BRID=2,HBTIM E=0,NORMALHBTIME=120,UNUSECNT=3,USECNT=3; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a SIP Signaling Route Prerequisites
Before the operation, it is required to confirm: �
The SIP signaling link is configured.
�
The MML Terminal window is opened.
Context
For the adjacent office connected with the MGCF through SIP, it is required to create signaling routes. Each SIP signaling route contains at most 12 SIP signaling links.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a SIP signaling route by executing command ADD SIPRT. The explanation of the main parameters in command ADD SIPRT is shown in Table 68. TABLE 68 PARAMETERS IN THE ADD SIPRT COMMAND Parameter Description
Instruction
ID
Route ID
It is the SIP signaling route ID, which is an integer, ranging from 1 to 65534. It is referred to in the SIP signaling route group configuration
NAME
Route name
It is a mandatory parameter, consisting of 0~50 characters. It is the SIP signaling route name
SPLC
Link selecting policy
It is a mandatory parameter. It is the policy for selecting SIP links managed by the signaling route. It can be configured to SEQ and RND. SEQ indicates that links are selected based
Parameter Name
154
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction on priority, while RND indicates that links are selected based on order
Signaling link ID
LNK
It is a mandatory parameter. It is the ID of the SIP signaling link managed by the SIP signaling route. It is consistent with the ID in command ADD SIPLNK. One SIP signaling route can be configured with at most 12 links
Example: Create a SIP signaling route with the following requirements. �
Route ID: 12.
�
Signaling route name: SCSCFR
�
Link selecting policy: SEQ
�
Signaling link ID: 12
The command is: ADD 2";
SIPRT:ID=12,NAME="SCSCFR",SPLC=SEQ,LNK="1
END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a SIP signaling Route Set Prerequisites
Before the operation, it is required to confirm: �
The SIP signaling route is configured.
�
The MML Terminal window is opened.
Context
For the adjacent office connected with the MGCF through SIP, it is required to create signaling route sets. Each SIP signaling route group contains at most 4 SIP signaling routes.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a SIP signaling route set by executing command ADD SIPRTS. The explanation of the main parameters in command ADD SIPRTS is shown in Table 69.
Confidential and Proprietary Information of ZTE CORPORATION
155
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 69 PARAMETERS IN THE ADD SIPRTS COMMAND Parameter Name
Parameter Description
Instruction
ID
Route group ID
It is a mandatory parameter, which is an integer, ranging from 1 to 65534. It is the SIP signaling route group ID, which cannot be repeated in the system
NAME
Route group name
It is a mandatory parameter, consisting of 0~50 characters. It is the SIP signaling route group name
Route Select Policy, includes RTPLC
SIPRT
�
SEQ: Sequential
�
PCT: Percent
Route ID
It is a mandatory parameter with a default value of SEQ
It is a mandatory parameter. It is the ID of the SIP signaling route managed by the SIP signaling route group. It is consistent with the ID in command ADD SIPRT. One SIP signaling route group can be configured with at most 4 routes
Example: Create a SIP signaling route group with the following requirements. �
Route ID: 12
�
Signaling route group name: SCSCFRS
�
Route Select Policy: Sequential
�
Route group ID: 12.
The command is: ADD SIPRTS:ID=12,NAME="SCSCFRS",RTPLC=SEQ,SIPR T="12"-"0"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating IP Distribution Policy Prerequisites
156
Before the operation, it is required to confirm: �
The number of exchange to be configured is known.
�
The SIP access address is configured.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
�
The MML Terminal window is opened.
Context
When the MGCF can be configured with multiple IP addresses, the SIP on each IP needs to be distributed to different signaling SMP modules for processing. The IP distribution policy implements the service allocation of the signaling SMP module processing SIP.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create IP distribution policy by executing command ADD IPDP LC. The explanation of the main parameters in command ADD IPDPLC is shown in Table 70. TABLE 70 PARAMETERS IN THE ADD IPDPLC COMMAND Parameter Name
Parameter Description
Instruction
ID
IP distribution policy ID
It is an integer, ranging from 1 to 65535
NAME
IP distribution policy name
It is a mandatory parameter, consisting of 1~50 characters. It is the IP distribution policy name
IP address type
It is the IP address type of the local office, which can be set to IPV4 or IPV6. When it is set to IPV4, configure the IPV4 subnet and subnet mask. When it is set to IPV6, configure the IPV6 subnet and subnet mask
IPV4 subnet
It is the subnet number of the IPV4 address of the local office. When ADDRTYPE is set to IPV4, the IPV4 address needs to be configured
IPV6 subnet
It is the subnet number of the IPV6 address of the local office. When ADDRTYPE is set to IPV6, the subnet number of the IPV6 address needs to be configure
V4MSK
IPV4 subnet mask
It is the subnet mask of the IPV4 address of the local office. When ADDRTYPE is set to IPV4,, the subnet mask of the IPV4 address needs to be configure
V6MSK
IPV6 subnet mask
It is the subnet mask of the IPV6 address of the local office. When ADDRTYPE is set to
ADDRTYPE
V4NET
V6NET
Confidential and Proprietary Information of ZTE CORPORATION
157
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction IPV6, the subnet mask of the IPV6 address needs to be configure
Distribution policies of UDP, including: DEF: Default distribution UPLC
PRIROR: Excellent choice priority
Selct PRIROR or LOADSHARE, DO NOT select DEF.
LOADSHARE: Load share priority UDPID
UDP Bear ID
Select the Bear ID configured in ADD UDPBR command
Example: Create an IP distribution policy with the following requirements. �
IP distribution policy name: MGCF11
�
IP distribution policy ID: 1
�
The local office uses the IPV4 address
�
IPV4 subnet: 10.1.33.11
�
IPV4 subnet mask: 255.255.255.0
�
UDP distribution policy: Excellent choice priority
�
UDP Bear ID: 1
The command is: ADD IPDPLC:ID=1,NAME="MGCF11",ADDRTYPE=IPV4,V 4NET="10.1.33.11",V4MSK="255.255.255.0",PORT=0,UPL C=PRIROR,UDPID="1"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating URI Analysis Prerequisites
158
Before the operation, it is required to confirm: �
The number of exchange to be configured is known.
�
The outgoing SIP signaling route group is added.
�
The routing selector is added.
�
The MML Terminal window is opened.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
Context
The URI analysis is used to analyze domain names on routes. Different URI numbers can be analyzed to different results.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create URI analysis by executing command ADD URI. The explanation of the main parameters in command ADD URI is shown in Table 71. TABLE 71 PARAMETERS IN THE ADD URI COMMAND Parameter Name
Parameter Description
Instruction
RTSEL
Routing selector
It is a mandatory parameter, which should be consistent with the ID in command ADD RTSEL
URI
Uniform Resource Identifier
It is a mandatory parameter, consisting of 1~50 characters. It is the analyzed domain name
SIP methods, including
METHOD
SIPRTS
�
ACK
�
BYE
�
CANCEL
�
INFO
�
INVITE
�
MESSAGE
�
NOTIFY
�
OPTIONS
�
PRACK
�
PUBLISH
�
REFER
�
REGISTER
�
SUBSCRIBE
�
UPDATE
SIP signaling routing group
It is a mandatory parameter. In general, it is configured to ACK, BYE, CANCEL, INVITE, PRACK, or UPDATE
It is the outgoing route group ID, which is associated with the ID in command ADD SIPRTS
Example: Create URI analysis with the following requirements.
Confidential and Proprietary Information of ZTE CORPORATION
159
ZXWN MSCS Data Configuration Guide(MGCF)
�
Routing selector: 1
�
Uniform Resource Identifier: scscf.zte.com
�
SIP method: ACK&BYE&CANCEL&INVITE&PRACK&UPDATE
�
SIP signaling route group: 12 (pointing to S-CSCF)
�
Other parameters: Adopt the default values.
The command is: ADD URI:RTSEL=1,URI="scscf.zte.com",METHOD="ACK "&"BYE"&"CANCEL"&"INVITE"&"PRACK"&"UPDATE",SIPRTS =12; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating an RTP Trunk Group Prerequisites
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The adjacent SIP office to which the trunk group points is created.
�
The trunk group No. range is set in the resource management system.
�
The MML Terminal window is opened.
Context
When the MSCS servers as a MGCF, the MGCF needs to control the IP resources from the IM-MGW to the IMS domain through the RTP trunk group configuration data. In this case, SIP trunk groups need to be configured.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Creating a RTP trunk group by executing command ADD TG RTP. The explanation of the main parameters in command ADD TG RTP is shown in Table 72.
160
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
TABLE 72 PARAMETERS IN THE ADD TG RTP COMMAND Parameter Name
TG
OFC
NAME
MODULE
Parameter Description
Instruction
Trunk group ID
It is a mandatory parameter. It is used to define a trunk group. This trunk group can be BICC trunk group or SIP trunk group. It is a global unified number
ID of the office where the trunk group belongs
It is a mandatory parameter. It is used to specify the corresponding office of the trunk group. This parameter must be defined by command ADD ADJOFC at first. Then it can be indexed here
User alias
It is an optional parameter, consisting of 0~50 characters. It is used to specifically describe a trunk group to make it easily recognized
Module where the trunk group belongs
It is a mandatory parameter, which is an integer, ranging from 1 to 127. It is used to specify the SMP module of processing traffic on this trunk group
Inter-office line signal identification, including SIGLINE
�
BICC (BICC signaling)
�
SIP (SIP signaling)
It is an optional parameter. Select SIP for the MGCF.
Trunk group types, including the following three types:
KIND
IN (incoming trunk group): Indicates that the local office processes the incoming calls from the peer-end office. OUT (outgoing trunk group): Indicates that the local office only processes the outgoing calls to the peer-end office.
It is an optional parameter. BIDIR is selected by default. It should be negotiated with the peer-end office.
BIDIR (Two-way trunk group): Indicates that the local
Confidential and Proprietary Information of ZTE CORPORATION
161
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
office processes both the incoming calls from the peer-end office and the outgoing calls to the peer-end office Bearer establishment direction, including the following three types:
BWAY
NODIR (No direction): The inter-office bearer is established without direction. BACK: The inter-office bearer is established based on the backward mode.
It is an optional parameter. For RTP trunk groups, it is set according to the network plan of operators
FORWD: The inter-office bearer is established based on the forward mode THD
Threshold for overload control
It is an optional parameter, ranging from 0 to 100, with a default of 100
Circuit selecting modes, including: MIN: Every time when the system selects a trunk circuit, it always begins with the circuit with the minimum number. This mode can implement the preferred plan of trunk circuits.
CICSEL
MAX: Every time when the system selects a trunk circuit, it always begins with the circuit with the maximum number. This mode can implement the preferred plan of trunk circuits. CYC: Every time when the system selects a trunk circuit, it always begins with the circuit next to the one previously selected. Suppose the numbers of the trunk circuits in a trunk group in ascending order are “TKC0, TKC1, …. ,
162
Confidential and Proprietary Information of ZTE CORPORATION
It is an optional parameter, with a default of CYC. In general, the signaling point with big code prefers the circuit with an even number, while the one with small code prefers the circuit with an odd number. It should be negotiated with the peer-end office
Chapter 5 MGCF-SIP Office Interconnection Data Configuration
Parameter Name
Parameter Description TKCn”. If TKC0 is selected at the first time, the system will select the trunk circuit in the order of “TKC0 ®TKC1®…®TKCn®TK C0®TKC1®…®TKCn”.
Instruction
ODD: Every time when the system selects a trunk circuit, it always selects the circuit with an odd number. EVEN: Every time when the system selects a trunk circuit, it always selects the circuit with an even number. IDLE: Every time when the system selects a trunk circuit, it always selects the idlest circuit. BUSY: Every time when the system selects a trunk circuit, it always selects the busiest circuit
DAS
SIPDAS
DAS for the called number
It is an optional parameter, which is an integer ranging from 0 to 4096, with a default of 0. When the local office has the GMSC function, this DAS is used to analyze the called number from other offices. When the called number is from the BSC office, this DAS is meaningless, and does not need to be configured
DAS for the domain name of the called number during SIP outgoing calls
It is used get the name of the IMS domain where the called party is located through analyzing the called number during a SIP outgoing call. If the outgoing SIP trunk group is configured with this DAS, the “invite” message during a SIP outgoing call can only contain SIP URL mode. If the outgoing SIP trunk group is not configured with this DAS, configure the URLOPT in the SIP adjacent office configuration to decide whether the outgoing call uses TEL or SIP URL mode.
Confidential and Proprietary Information of ZTE CORPORATION
163
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction After this DAS is used on this trunk group, all outgoing calls on this trunk group will get the corresponding domain name according to the called number, and then form a SIP URL
OPDAS
DAS for the calling number
It is an optional parameter, which is an integer ranging from 0 to 4096, with a default of 0. When the local office has the GMSC function, this DAS is used to analyze the calling number from other offices. When the calling number is from the BSC office, this DAS is meaningless, and does not need to be configured
Example: Create a SIP trunk group with the following requirements. �
Trunk group ID: 12
�
ID of the office where the trunk group belongs: 12
�
User alias: SCSCF
�
No. of the module processing the trunk group: 0
�
Inter-office line signal identification: SIP
�
SIP route set: 12
�
Other parameters: Adopt the default values.
The command is: ADD TG RTP:TG=12,OFC=12,MODULE=0,NAME="SCSCF ",SIGLINE=SIP,KIND=BIDIR,BWAY=NODIR,THD=100,CI CSEL=CYC,DAS=0,SIPDAS=0,OPDAS=0,PREDAS=0,DDI =0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT=0,MAXI NT=26,INREG=INVALID,OUTREG=INVALID,COLEN=10,B USYRATE=100,ROAMDAS=0,Q850CCIDX=0,SMENTERID =0,MLPPDM=4294967295,SIPRUTS=12,DISINDEX=0; END OF STEPS Result
164
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter
6
MGCF-Other-Exchange Interconnection Data Configuration Table of Contents Networking Mode............................................................. 165 Office Interconnection in IP Domain ................................... 166 TDM Office Interconnection ............................................... 181
Networking Mode Overview
When MGCF is interconnected with the equipment (such as MSCS, 2G MSC/PSTN) at the network side, the interfaces between them fall into TDM-type or IP-type according to different bearer modes, as described in Table 73. These interfaces may also fall into directassociated mode and quasi-associated mode according to their connection method. You should select the corresponding configuration method according to the actual networking condition. TABLE 73 BEARER MODES OF MAIN INTERFACES Interconnected Equipment
Interface
Bearer Mode
MSCS
Nc
IP
2G MSC/PSTN
Ai
TDM/IP
Take the interconnection between 2G MSC and MGCF/IM-MGW for example. When the traffic bearer is TDM bearer or IP bearer, 2G MSC is directly connected with IM-MGW. However, the signaling modes between 2G MSC and MGCF divide into the following three types. 1. 2G MSC is connected with MGCF in TDM bearer mode. When 2G MSC is interconnected with the MGCF in TDM bearer mode, they only transmit the narrowband signaling. i. 2G MSCMGCF 2G MSC is directly associated with MGCF in a TDM bearer mode.
Confidential and Proprietary Information of ZTE CORPORATION
165
ZXWN MSCS Data Configuration Guide(MGCF)
ii. 2G MSCSTPMGCF 2G MSC is quasi-associated with MGCF through STP in TDM bearer mode. This method is applicable to the interconnection between two devices in the circuit domain, which requires configuring the narrow-band signaling processing board SPB on MGCF. 2. 2G MSC is connected with MGCF in an IP bearer mode. 2G MSC is directly connected with MGCF in an IP bearer mode. The signaling between them is transmitted through SIGTRAN. The upper-layer signaling, such as BICC, is borne through M3UA/SCTP or SCTP. This method is applicable to the interconnection between two devices in the IP domain. 3. 2G MSC is connected with MGCF in IP bearer and TDM bearer modes. The signaling adaptation between 2G MSC and MGCF is implemented through an intermediate node, which is IM-MGW usually. The signaling is transmitted by the path of 2G MSCIMMGWMGCF, where the narrow-band signaling is transmitted between 2G MSC and IM-MGW, and SIGTRAN is transmitted between IM-MGW and MGCF. The signaling may also be switched on IM-MGW in M3UA or M2UA mode. �
�
�
When MGCF and IM-MGW adopt different signaling points, M3UA transfer mode is usually adopted. When MGCF and IM-MGW adopt the same signaling point, M3UA proxy mode is usually adopted. When MGCF and IM-MGW adopt the same signaling point, and MGCF manages several IM-MGWs that are all connected with MGCF, M2UA transfer mode may be adopted.
Office Interconnection in IP Domain Overview Introduction
This section describes the procedure for configuring the office interconnection in the IP domain. There are the following three interconnection modes in the IP domain. 1. Direct-associated office in the IP domain The office is directly connected with MGCF in IP bearer mode. 2. M3UA-transferred office
166
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
MGCF and its opposite-end office provide IP and TDM bearers respectively. The signaling between them is transferred by IM-MGW in M3UA mode. 3. M2UA-transferred office MGCF and its opposite-end office provide IP and TDM bearers respectively. The signaling between them is transferred by IM-MGW in M2UA mode.
Direct-Associated Office Configuration in IP Domain The direct-associated office in the IP domain is the office directly connected with MGCF in the IP bearer mode. For example, MGCF and MSCS are connected through an Nc interface.
Overview Configuration Flow
Figure 54 shows the flow of configuring a direct-associated office in the IP domain. FIGURE 54 FLOW OF CONFIGURING A DIRECT-ASSOCIATED OFFICE IN IP DOMAIN
Flow Description
Perform the following steps.
Confidential and Proprietary Information of ZTE CORPORATION
167
ZXWN MSCS Data Configuration Guide(MGCF)
Steps
Operations
Instructions
Commands
1
Creating an Adjacent Office
Create other interconnected office at the network side, except for IM-MGW. Select a different adjacent office type.
ADD ADJOFC
2
Creating an MSCS Topological Node
The topological node of the opposite-end MSCS office is configured during the Nc interface configuration.
ADD TOPO
3
SIGTRAN protocol configuration
It is similar to the SIGTRAN configuration on the Mn interface, refer to Overview.
-
Creating an Adjacent Office Prerequisites
Before the operation, it is required to confirm: �
The signaling interworking data planning and negotiation between MSCS and other office are completed.
�
The data configuration of local office is completed.
�
The basic configuration of the local office is completed.
�
The MML Terminal window is opened.
Context
Perform this procedure to configure the basic information of an inteconnected adjacent office.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an adjacent office. The command is ADD ADJOFC. Table 74 describes the main parameters in the ADD ADJOFC command. TABLE 74 PARAMETERS IN THE ADD ADJOFC COMMAND Parameter Name
ID
168
Parameter Description
Instruction
Office ID
A mandatory parameter, indicating the identification number of the adjacent office, and ranging from 1 to 3000. In general, it is configured as the exchange ID of the adjacent office during the all-network planning
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction
NAME
User-defined alias
It is a mandatory parameter. Type a customized name
NET
Network type
A mandatory parameter, indicating the network type of the SPC used for connecting the local office to the adjacent office when the local office is configured with several SPs. The default is the network type of this SP when there is only one SP in the local office
OFCTYPE
The type of adjacent office
It is a mandatory parameter.
SPCFMT
SPC format
Select TRIPLE_DEC
SPCTYPE
SPC type
DPC
Destination SPC
RC
Area code
It is a mandatory parameter. Select it based on the SPC type of the adjacent office according to the signaling point planning. In China, all the NEs adopt the 24-bit SPC It is an optional parameter, indicating the local toll zone code of the adjacent office. This parameter has impact on the area code added by the calling number
Association type, including: �
AM_SURE (direct connection mode)
�
AM_QUASI (half direct connection mode)
�
AM_NONE (none connection mode)
ASSOTYPE
SPTYPE
Signaling point type, including SEP, STP and STEP
It is an optional parameter. Select AM_SURE
It is an optional parameter. Select SEP (signaling end point), STEP (signaling transfer/end point) or STP (signaling transfer point) according to the role of the adjacent office in the signaling network.
Confidential and Proprietary Information of ZTE CORPORATION
169
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
Subservice function, including �
INTERNATIONAL (International signaling point code)
�
INTERNATIONAL STANDBY (International standby signaling point code)
SSF �
NATIONAL (National signaling point code)
�
NATIONAL STANDBY (National standby signaling point code).
It is an optional parameter. In general, NATIONAL is selected at home.
Office Attribute, including: TAG
ISNI (Has ISNI Function) TRANS (Translate Node)
It is an optional parameter
TEST (Need Test Info:0X02/0X01)
TEST
Test flag
It is an optional parameter. It is used to set whether the MTP3 link actively initiates the link test after entering the service status. In most cases, this parameter is selected. It is an optional parameter with a default of NO. It is used for SCCP to judge whether to use the LUDT message.
BANDFLAG
Broadband attribute
The maximum length of a broadband link message is 4,000, and that of a narrowband link message is 255. Because the MTP layer does not have the segmentation function, the incorrect configuration of this parameter probably causes the long packet to be discarded. Select YES when all the links between two SPs are
170
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction SIGTRAN or ATM signaling links.
Protocol Type, including: �
CHINA (China)
�
ITU (International Telecommunications Union)
�
ANSI (American National Standards Institute)
PRTCTYPE
CLST
Cluster ID
It is an optional parameter. The CHINA and the ITU are used for the NO.7 signaling networking of the ITU standard and the ANSI is used for the NO.7 signaling networking of the American standard. In general, select CHINA for the domestic office and select ITU for the international office It is an optional parameter within 0~65535. In general, select the default value 65535. It is valid when the protocol type of the adjacent office is “ANSI”. The signaling point connected to the signaling transfer point belongs to the corresponding cluster. The cluster ID is configured in the command ADD CLST
Office Info, including: CIC_PCM (CIC starts the load sharing according to the PCM code mode) BLOCK (Manual block status)
INFO
EVEN_CIC (The office controls the even CIC when CIC resource contention occurs)
It is an optional parameter and the default value is CIC_PCM
CALLING ( Calling transform is allowed) CALLED (Called transform is allowed) MOD24_CIC (CIC mode with 24 mode) TEST (Dynamic observation)
Confidential and Proprietary Information of ZTE CORPORATION
171
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
RELATEDOFC1
Related Office ID
It is an optional parameter ranging from 0 to 3000
Office Extend Info, including: �
SIGBRDCST (Support Signa ling Broadcast Message)
�
MTP (Hongkong MTP Standard)
�
DUPU ( Screen DUPU message)
�
SUA_REC_DT1 (Receive SUA message and handle it as DT1 message)
INFOEX
�
SUA_SND_DT1 (Send SUA message and handle it as DT1 message without SN.)
�
OPEN_TG_RES (Open outter trunk group resource)
It is an optional parameter
For example, configure the MSCS adjacent office. The network type is 1, the alias is MSCS105, the signaling point code is 3.105.1 the signaling point code format is 24, the association type is AM_SURE, and the office type is LOCAL&DOMTOLL&OA&MSCSERVER For other parameters, select the default value. The command is as follows: ADD ADJOFC:ID=105,NAME="MSCS105",NET=1,OFCTYP E="LOCAL"&"DOMTOLL"&"OA"&"MSCSERVER",SPCFMT=TR IPLE_DEC,SPCTYPE=24,DPC="3.105.1",RC="25",ASSOTY PE=AM_SURE,SPTYPE=SEP,SSF=NATIONAL,SUBPROTTYP E=DEFAULT,TEST=YES,BANDFLAG=NO,PRTCTYPE=CHIN A,CLST=65535,INFO="CIC_PCM",RELATEDOFC1=0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating an MSCS Topological Node Prerequisites
Before the operation, it is required to confirm: �
172
The encoding and decoding speech template configuration is completed.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
�
The range of topological nodes is configured in the resource management.
�
The MML Terminal window is opened.
Context
For Nc interface, the topological node of the opposite-end MSCS office needs to be configured.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Configure an MSCS topological node. The command is ADD TOPO. Table 75 describes the main parameters in the ADD TOPO command. TABLE 75 PARAMETERS IN THEADD TOPO COMMAND Parameter Name
Parameter Description
Instruction
Topological node ID
It is a mandatory parameter. For identifying this node with a serial number, ranging from 1 to 3000. It is recommended to be consistent with the office ID of this node
OFCID
Office ID
It is a mandatory parameter for specify the office ID of this topological node. This parameter must be defined by the ADD ADJOFC command first. Type the MSCS office ID according to the actual conditions.
NAME
Alias
It is a mandatory parameter for describing a topological node, with a length ranging from 1 to 50 characters.
CODEC identity
It is a mandatory parameter for specify the CODEC template used by this topological node. This parameter must be defined by the ADD CODECTPL command first.
ETYPE
Equipment type
This parameter is used to specify the NE equipment type of this topological node. Select MSCS for an MSCS device.
PROTTYPE
Protocol type
Select BICC for an Nc interface.
ID
CODECID
Confidential and Proprietary Information of ZTE CORPORATION
173
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
IPVER
ATTR
Parameter Description
Instruction
IP version of the node
This parameter indicates the IP protocol version supported between nodes. Select IPV4 or IPV6 according to the actual conditions. Currently, it is usually configured as IPV4
Bearer attributes
This parameter is only valid for the node with the type of R4GW (MGW). You need not to configure it for an MSCS topological node.
Extended attributes (tunnel mode), including: �
NOTUNL (None tunnel mode)
�
RTUNL (Rapid tunnel mode)
�
DTUNL (Delay tunnel mode)
ATTR2
Signaling transfer mode, including: TRFMOD
MCINTF (Mc interface signal transfer mode)
This parameter sets which tunnel mode is used for setting up a bearer when this node supports the IP/RTP bearer, with a default of NOTUNL (None tunnel mode).
This parameter is used to set that mode used by the topology for reporting the detected CNG or CED fax signals, with a default of MCINTF (Mc interface signal transfer mode).
DTMFTC
Tandem office send DTMF use TC mode, including NO (No) and YES (Yes)
This parameter designates whether TC resources are used during DTMF number delivery, with a default of NO
MGWCON
MGW congestion reporting capability, including SMGWCON (standard MGW congestion event) and CMGWCON (custom MGW congestion event)
This parameter designates the MGW congestion reporting capability, with a default of SMGWCON (standard MGW congestion event).
Example: Create an MSCS topological node with the following requirements. �
MSCS office ID: 105
�
Equipment type: MSCS
�
Protocol type: BICC
�
CODEC ID: 1
�
Other parameters: Default.
The specific command is as follows.
174
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
ADD TOPO:ID=105,OFCID=105,NAME="MSCS105",CODE CID=1,ETYPE=MSCS,PROTTYPE=BICC,IPVER=IPV4,ATT R2=NOTUNL,TRFMOD=MCINTF,UPERRCTRL=YES,DTMFTC =NO,MGWCON=SMGWCON,AUTOFAX=YES,OOBTC=NO,B CUID=0,SENDCAP=NO,G711TRAN=NO,BICCDTMF=TRAN SPARENT,IPBCP2833=BYMGW,BICCDTMPPER=0,AOIPPR O=PRIVATE; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
M3UA-Transferred Office Configuration Description
MGCF and its opposite-end office provide IP and TDM bearers respectively. The signaling between them is transferred by IM-MGW in M3UA mode.
Networking mode
Take the quasi-associated networking (M3UA-based) between MGCF and 2G MSC/PSTN for example. Figure 55 shows its interface protocol stack. FIGURE 55 QUASI-ASSOCIATED NETWORKING BETWEEN MSCS AND 2G MSC/PSTN (BASED ON M3UA)
The connection between MGCF and IM-MGW is in the IP bearer mode, and the connection between IM-MGW and 2G MSC/PSTN is in the TDM bearer mode. Therefore, to configure the interworking data between MGCF and 2G MSC/PSTN, you only need to create a 2G MSC/PSTN adjacent office on the MGCF, and to configure the SIGTRAN data between MGCF and IM-MGW to make the IM-MGW complete the signaling transit. In this case, the IM-MGW serves as a signaling gateway, working in a switching mode. Configuration Description
Figure 56 shows the flow of configuring an M3UA transit exchange.
Confidential and Proprietary Information of ZTE CORPORATION
175
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 56 FLOW OF M3UA TRANSIT EXCHANGE
Perform the following steps.
Steps
1
2
176
Operations
Configuration Description
Reference
Creating an adjacent office
Create other interconnected office at the network side, except for IM-MGW. Select a different adjacent office type. It is required that the network type of this adjacent office is consistent with the IM-MGW network type configured for this group of associations.
Creating an Adjacent Office
SIGTRAN configuration
Based on the principles of SCTP Planning, specify the office ID parameter in the SIO-locating-AS configuration to be consistent with the office ID of the adjacent office that is switched through IM-MGW, when the association between IM-MGW and MGCF is configured.
Overview
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
M2UA-Transferred Office Configuration Overview Introduction
MGCF and its opposite-end office provide IP and TDM bearers respectively. The signaling between them is transferred by IM-MGW in M2UA mode.
Networking mode
Take the quasi-associated networking (M2UA-based) between MGCF and 2G MSC/PSTN as an example. Figure 57 shows its interface protocol stack. FIGURE 57 QUASI-ASSOCIATED NETWORKING BETWEEN MGCF AND 2G MSC/PSTN (BASED ON M2UA)
The connection between MGCF and IM-MGW is in the IP bearer mode, and the connection between IM-MGW and 2G MSC/PSTN is in the TDM bearer mode. When the signaling is transferred in the M2UA mode, IM-MGW serves as SG to only complete the adaptation of the MTP2-layer protocol, and transparently transmits the MTP3 layer protocols to the MGCF for processing. Therefore, you only need to configure the No. 7 signaling data on the MGCF, which are transmitted to the adjacent office. Configuration flow
Figure 58 shows the flow of configuring an M2UA transit exchange.
Confidential and Proprietary Information of ZTE CORPORATION
177
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 58 FLOW OF M2UA TRANSIT EXCHANGE
Flow Description
178
Perform the following steps.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
Steps
Operations
Instruction
Reference
1
Creating an adjacent office
Create other interconnected office at the network side, except for MGW. Select a different adjacent office type.
Creating an Adjacent Office
2
Creating an SCTP
OFCID: select the adjacent office ID configured in Step 1.
Creating an SCTP
PROT: Select M2UA 3
Creating an ASP
-
Creating an ASP
PROT: Select M2UA 4
Creating an AS
EXISTCTX: No routing context is configured ASTAG: Select ASP on MSCS.
Creating an AS
ASUP: Select NULL
5
Creating a signaling link set
Select the type of this signaling link set according toits signaling link type. In general, select N64 (64K narrowband link set).
Creating a Signaling Link Set
6
Creating an M2UA IP link
-
Creating an M2UA IP Link
7
Creating a signaling route
-
Creating a Signaling Route
8
Creating a signaling office
-
Creating a Signaling Office
Creating an M2UA IP Link Prerequisites
Before the operation, it is required to confirm: �
The signaling link group configuration is completed.
�
The MML Terminal window is opened.
Context
When IM-MGW forwards signaling in the M2UA mode, the M2UA IP link connection to the adjacent office should be configured. The signaling link is accessed through SIPI board, and SIGTRAN protocol is used for transmission.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an M2UA IP link. The command is ADD M2UAIPLNK.
Confidential and Proprietary Information of ZTE CORPORATION
179
ZXWN MSCS Data Configuration Guide(MGCF)
Table 76 describes the main parameters in the ADD M2UAIP LNK command. TABLE 76 PARAMETERS IN THE ADD M2UAIPLNK COMMAND Parameter Name
Parameter Description
Instruction
Signaling link set ID
It is a mandatory parameter. Type the link set No. of this link, ranging from 1 to 1024.Which is associated with the ID of the signaling link set that is created
Signaling link set code
It is an optional parameter to configure the SLC of this signaling link. It needs to be consistent with the SLC of the same signaling link of the opposite-end office
SMP module No.
It is a mandatory parameter. Type the No. the SMP module that processes this link, ranging from 1 to 127
Destination AS ID
It is a mandatory parameter. Type the AS No. used by this signaling link, ranging from 1 to 640. In this case, type the AS ID whose adaptation layer is M2UA
Link number
It is an optional parameter, designating the global No. of the signaling link on the MSCS. It ranges from 1 to 5000
NAME
Alias
It is a mandatory parameter, for describing the name of this signaling link for easy identification
IIDTYPE
Interface ID type, including INT(Integer Type), TEXT(Text Type and BOTH(Integer and Text Type)
The parameter indicates the interface ID type. Currently, only the integer type is supported.
IID
Interface ID
The parameter ranges from 0 to 4294967295
LOOP
Self loop, including options: NO(Not Self Loop) and YES(Self Loop)
The parameter indicates whether the link is at a self loop status.
LKSID
SLC
MODULE
ASID
ID
Example: Create an M2UA IP signaling link connecting to a 2G MSC office with the following requirements.
180
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
�
Link set ID: 2
�
SMP module No.: 3
�
Destination AS ID: 2
�
Link No.: 2
�
Alias: MSC
�
ID of it in the signaling link set: 0
�
Other parameters: default.
The specific command is as follows. ADD M2UAIPLNK:LKSID=2,SLC=0,MODULE=3,ASID=2,I D=2,NAME="MSC",IIDTYPE=INT,LOOP=NO; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
TDM Office Interconnection Overview Introduction
TDM office refers to the office connecting with MGCF through TDM bearer. To configure a direct-associated office, you need to configure signaling link set, signaling link, signaling route, and signaling office. To configure a quasi-associated office, you only need to configure the signaling office.
Configuration Flow
Figure 59 shows the flow of configuring the interconnection data between MGCF and TDM office.
Confidential and Proprietary Information of ZTE CORPORATION
181
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 59 TDM OFFICE INTERCONNECTION CONFIGURATION FLOW
Flow Description
Perform the following steps. Steps
Operations
Instructions
Command
1
Creating signaling link set
Configure a narrowband signaling link set to the adjacent office.
ADD N7LKS
Create SPB signaling link
Configure a narrowband signaling link to the adjacent office.
ADD N7LNKE1
2
182
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
Steps
3
4
Operations
Instructions
Command
Create signaling route
The signaling routing configuration is used for specifying the signaling link set to be selected and the method when the signaling selects a route.
ADD N7ROUTE
Create signaling office
Configure the correspondence between the destination signaling office and the signaling route.
ADD N7OFC
Creating a Signaling Link Set Prerequisites
Context
Before the operation, it is required to confirm: �
The adjacent office configuration is completed.
�
The data configuration of local office is completed.
�
The range of signaling link set is configured in the resource management.
�
The MML Terminal window is opened.
Perform this procedure to configure a narrowband signaling link set to the adjacent office, including 64k signaling link set, 2M signaling link set, N×64k signaling link set. When configuring the signaling link set connected by TDM, you may select N64, NN64, and N2M.
Steps
�
64k indicates that the narrow-band signaling link in this signaling link set only seizures one time slot on one E1 line, with 64 Kbps bandwidth.
�
N×64K indicates that the narrow-band signaling link in this signaling link set seizures N consecutive time slots on one E1 line (8≤n≤25).
�
2M indicates that the narrow-band signaling link in this signaling link set seizures all 31 time slots on one E1 line (time slot 0 is unavailable), with 1.984Mbps bandwidth.
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a signaling link set. The command is ADD N7LKS.
Confidential and Proprietary Information of ZTE CORPORATION
183
ZXWN MSCS Data Configuration Guide(MGCF)
Table 77 describes the main parameters in the ADD N7LKS command. TABLE 77 PARAMETERS IN THE ADD N7LKS COMMAND Parameter Name
OFCID
TYPE
ID
Parameter Description
Instruction
Direct-associated office of the signaling link set
It is a mandatory parameter. Type the adjacent office ID of this signaling link set, which is specified in the adjacent office configuration.
Signaling link set type
This parameter indicates the types of the signaling links in this signaling link set. Select N64 for a 64K signaling link, NN64 for an n×64K signaling link, and N2M for a 2M signaling link.
Signaling link set ID
It is a mandatory parameter. It designates the signaling link set No. for distinguishing signaling link sets, ranging from 1 to 1024.
Link error revision, including:
LECM
BASIC (basic error revision, transit delay ≤ 15 ms): all the signaling links use this method for relatively short transit delay, except for satellite links. PCR (Preventive Cyclic Retransmission: transit delay≥15 ms): Satellite links use this method for it has a relatively long transit delay.
NAME
Alias
This parameter designates the error correction method of the signaling links in this set. In general, select BASIC. In general, BASIC is selected when the line transit delay is less than 15ms, and PCR is selected when the line transit delay is greater than 15ms. For a 2M signaling link, BASIC must be selected. This parameter shall be consistent with that of the opposite end through negotiation. It is a mandatory parameter describing the name of this signaling link set for easy identification.
Example: Create a signaling link set connected TDM office 104 with the following requirements.
184
�
TDM office ID: 104
�
Signaling link set No.: 1
�
Group type: 64K narrowband link set
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
�
Link error revision: Basic error revision
�
Alias: TDM-1.
The specific command is as follows. ADD N7LKS:OFCID=104,TYPE=N64,ID=1,LECM=BASIC,N AME="TDM-1"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating an SPB-Accessed Signaling Link Prerequisites
Context
Before the operation, it is required to confirm: �
The signaling link group configuration is completed.
�
The MML Terminal window is opened.
Signaling link is the physical channel carrying signaling messages. The narrow-band signaling link used on the MGCF is an SPB-accessed signaling link.
Note: In order to evenly distribute the traffic load to an office on each link that is selected in the dynamic routing table corresponded by the SLC, usually the number of links in a link set to a directassociated office is configured as 2n, namely, 2, 4, 8, or 16 links are configured. Make sure that load onto each link is not too heavy to cause it breakdown. Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an SPB-accessed signaling link. The command is ADD N7LNKE1 Table 78 describes the main parameters in the ADD N7LNKE1 command.
Confidential and Proprietary Information of ZTE CORPORATION
185
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 78 PARAMETERS IN THE ADD N7LNKE1 COMMAND Parameter Name
LKSID
SLC
MODULE
NAME
Parameter Description
Instruction
Signaling link set ID
It is a mandatory parameter, designating the signaling link set No. of this signaling link. It is associated with the ID of the signaling link set that is configured.
Signaling Link Code (SLC)
This parameter designates the SLC of this signaling link, ranging from 0 to 15. It needs to be consistent with the SLC of the same signaling link of the opposite-end office.
Signaling management module No.
It is a mandatory parameter. Select a signaling module. Several signaling links of the same office should be configured to different physical boards. In addition, the signaling links managed by each SMP module should share load.
Alias
It is a mandatory parameter designating the name of the signaling link for easy identification, with a length ranging from 1 to 50 characters.
SPBUNT
SPB unit number
CPU
CPU ID of SPB
E1
E1 number of the SPB board
It is a mandatory parameter. The CPU ID ranges from 1 to 4. Several signaling links of the same office should be configured to different SPB boards. In addition, the signaling links processed by the CPUs on SPB board should share load.
This parameter designates the number of the E1 where the signaling link is located, ranging from 9 to 25. By default, it is numbered from 9 64k signaling link: the time slot number of the signaling link is 16
TS
Start timeslot number of E1
N×64k signaling link: its start time slot ranges from 1 to 31 2M signaling link: Its start time slot is 1
186
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction Configure the number of the time slots occupied by the signaling link.
TSNUM
Quantity of timeslots
64K signaling link: Its time slot amount is 1. N×64K signaling link: Its time slot amount is N. 2M signaling link: Its time slot amount is 31.
Miscellaneous information, including: E1: This link uses the E1-type interface.
INFO
N64KT1: This link uses the T1-type interface, with 64K normal coding mode. I64KT1: This link uses the T1-type interface, with 64K reversal phase coding mode.
Configure the interface type and coding mode of this link. In general, it is an E1 link.
56KT1: This link uses the T1-type interface, with 54K coding mode.
Example: Create an SPB-accessed signaling link with the following requirements. �
Signaling link set No.: 1
�
SMP module No.: 3
�
Signaling link alias: TDM-1
�
SPB board unit No.: 721
�
Start time slot number of E1: 1
�
Time slot amount: 1
�
Signaling link No.: 0
�
Other parameters: default.
The specific command is as follows.
Confidential and Proprietary Information of ZTE CORPORATION
187
ZXWN MSCS Data Configuration Guide(MGCF)
ADD N7LNKE1:LKSID=1,SLC=0,MODULE=3,NAME="TDM -1",ID=1,SPBUNT=721,CPU=1,E1=9,TS=16,TSNUM=1,LO OP=NO,INFO=E1,FCPLTHR=255; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a Signaling Route Prerequisites
Before the operation, it is required to confirm: �
The signaling link group configuration is completed.
�
The range of signaling route ID is configured in the resource management.
�
The MML Terminal window is opened.
Context
The signaling routing configuration is used for specifying the signaling link set to be selected and the method when the signaling selects a route. The signaling route to a direct-associated office only contains the signaling link sets to this office. The signaling route to a quasi-associated office contains one or two signaling link sets to the intermediate office.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a signaling route. The command is ADD N7ROUTE. Table 79 describes the main parameters in the ADD N7ROUTE command. TABLE 79 PARAMETERS IN THE ADD N7ROUTE COMMAND Parameter Name
Parameter Description
Instruction
NAME
Alias
It is a mandatory parameter designating a signaling route for easy identification.
Signaling link set 1
The signaling route contains the first signaling link set. Type the serial number of the signaling link set 1.
Signaling link set 2
It is the second signaling link set contained by the signaling route. At least either LKSID1 or LKSID2 is not equal to zero and contains signaling links. If
LKSID1
LKSID2
188
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
Parameter Name
Parameter Description
Instruction only one signaling link set exists, type 0
Signaling route number
This parameter designates the serial number of the signaling route, ranging from 1 to 2000. When there is only one signaling link set, this parameter may be configured to be consistent with the signaling link set number.
LPM
Arrangement mode of signaling link sets. Refer to Table 80 for its options.
This parameter designates the rules that should be obeyed when the signaling links of two signaling link sets are sorted. When two link sets have the same signaling links, and the total number is not more than 16, RAND (random order) is recommended
LPMIN
Arrangement mode in a signaling link set. Refer to Table 80 for its options.
This parameter designates the rules that should be obeyed when the signaling links in a signaling link set are sorted. RAND (random order) is recommended
MANUAL
Sort manually, including NO(Need Not Manual) and YES(Need Manual):
The parameter indicates whether to manually sort the signaling routes of the two link groups
Link list
The maximum number of instance is 16. The format is -, representing the alignment order and link number respectively.
ID
LINKS
TABLE 80 ARRANGEMENT MODE OF SIGNALING SETS Mode
Meanings
Instruction
RAND
Random arrangement mode
Random arrangement mode
SLS0
Select On SLS_BIT0
Selecting links between two link sets according to Bit 0 of SLS
SLS1
Select On SLS_BIT1
Selecting links between two link sets according to Bit 1 of SLS
Confidential and Proprietary Information of ZTE CORPORATION
189
ZXWN MSCS Data Configuration Guide(MGCF)
Mode
Meanings
Instruction
SLS2
Select On SLS_BIT2
Selecting links between two link sets according to Bit 2 of SLS
SLS3
Select On SLS_BIT3
Selecting links between two link sets according to Bit 3 of SLS
SLS01
Select On SLS_BIT0-1
Selecting links between two link sets according to Bits 0 and 1 of SLS
SLS12
Select On SLS_BIT1-2
Selecting links between two link sets according to Bits 1 and 2 of SLS
SLS23
Select On SLS_BIT2-3
Selecting links between two link sets according to Bits 2 and 3 of SLS
Example: Create a signaling route with the following requirements. �
Alias: TDM
�
Signaling link set No.: 1
�
Signaling route No.: 1
�
Other parameters: default.
The specific command is as follows. ADD N7ROUTE:NAME="TDM",LKSID1=1,LKSID2=0,ID =1,LPM=RAND,LPMIN=RAND,MANUAL=NO; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a Signaling Office Prerequisites
Before the operation, it is required to confirm: �
The signaling route configuration is completed.
�
The MML Terminal window is opened.
Context
Perform this procedure for configuring the correspondence between the destination signaling office and the signaling route.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11;
190
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 6 MGCF-Other-Exchange Interconnection Data Configuration
2. Create a signaling office. The command is ADD N7OFC. Table 81 describes the main parameters in the ADD N7OFC command. TABLE 81 PARAMETERS IN THE ADD N7OFC COMMAND Parameter Name
Parameter Description
Instruction
ID
Signaling route office
It is a mandatory parameter. Type the adjacent office No. of the destination office
RT1
This parameter designates the serial number of the direct route to the destination adjacent office.
It is a mandatory parameter. Configure the serial number of the direct route to this office, ranging from 1 to 2000
RT2
Alternate route 1, indicating the serial number of the first alternate route to the destination adjacent office.
RT3
Alternate route 2, indicating the serial number of the second alternate route to the destination adjacent office. This parameter is configured when only the first alternate route is already configured.
RT4
Alternate route 3, indicating the serial number of the third alternate route to the destination adjacent office. This parameter is configured when only the second alternate route is already configured.
NAME
Alias
This parameter ranges from 0 to 2000. Select up to three available alternate routes according to the actual conditions. When there is no alternate route, configure it as 0.
It is a mandatory parameter. This parameter designates the name of the signaling office for easy identification
Example: Create a signaling office to a TDM adjacent office whose office ID is 104 and the direct-associated route number is 1. The specific command is as follows. ADD N7OFC:ID=104,RT1=1,RT2=0,RT3=0,RT4=0,NAME ="TDM"; END OF STEPS
Confidential and Proprietary Information of ZTE CORPORATION
191
ZXWN MSCS Data Configuration Guide(MGCF)
Result
192
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter
7
Basic Service Data Configuration Table of Contents Overview........................................................................ 193 Number Analysis Configuration .......................................... 193 Trunk Data Configuration .................................................. 235 Route Data Configuration.................................................. 258
Overview The configuration flow of basic service data is as follows: No.
Operations
1
Number analysis configuration
2
Trunk data configuration
3
Route data configuration
Number Analysis Configuration If the SIP address format is TEL/IP, the SIP number analysis is the same with the ordinary number analysis. If the SIP address format is URI, besides the ordinary number analysis, a URI analysis configuration is required. ZXWN MSCS system provides seven number analyzers: new service number analyzer, CENTREX number analyzer, private-network number analyzer, special-service number analyzer, local-network number analyzer, national toll-service number analyzer, and international toll-service number analyzer. For a specified DAS, numbers pass each type of analyzers specified by this DAS in a fixed order. The analyzers strictly follow the following order to perform number analysis, as shown in Figure 60.
Confidential and Proprietary Information of ZTE CORPORATION
193
ZXWN MSCS Data Configuration Guide(MGCF)
FIGURE 60 ANALYSIS ORDER OF NUMBER ANALYZERS
Configuration instances of common DASs and the number analysis results are as follows: 1. DAS for pre-analyzing the called number It is used to process special dial prefixes, including performing call restriction, format conversion of the called number. After an exchange receives “10193+called number” dialed by a subscriber, 10193 is deleted in this exchange, and the subsequent routing is based on the existing traffic routing, as shown in Table 82. TABLE 82 DAS FOR PRE-ANALYZING THE CALLED NUMBER Analyzer Entry
Analyzed Number
Analysis Result If call restriction is required, analyze it to “pre-analysis ending, and call rejected”
10193 + 0 + local area code New service number analyzer
10193 + 0 + non-local area code
If no call restriction is required, analyze it to “pre-analysis normally ending”, and delete “10193 + 0 + local area code” from the change index of the called number Analyze it to “pre-analysis normally ending”, and delete 10193 from the change index of the called number. Whether to add 10193 to the called-number index
194
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Analyzer Entry
Analyzed Number
Analysis Result
10193 + G network number section
10193 + C network number section
in the CDR depends on the CDR filling requirements on the billing center
2. Originating DAS: used to analyze the called number in the local-office-originated call, as shown in Table 83. TABLE 83 ORIGINATING DAS Analyzer Entry
Analyzed Number
Analysis Result
New service number analyzer
Charging query number
Analyze it to the SSP charging query service
Free special-service number
Analyze it to the local-office free special service, pointing to the special-service number configured on the attendant console
Corresponding attendant console number of the special-service number
Analyze it to the outgoing free special service, pointing to the special-service circuit group
Short number
-
Special-service number of the operator
Analyze it to the outgoing free special service, pointing to the special-service circuit group
Specialservice number analyzer
Vacant number 0 Localnetwork number analyzer Local PSTN number
All numbers are analyzed by the subsequent analyzers Analyze it to the local-network outgoing/local-call service, pointing to the gateway office
Confidential and Proprietary Information of ZTE CORPORATION
195
ZXWN MSCS Data Configuration Guide(MGCF)
Analyzer Entry
Analyzed Number
Analysis Result
Local number section of other mobile network
Analyze it to the local-network outgoing/local-call service, pointing to the gateway office
Non-local number section of other mobile network
Analyze it to the automatic service in the national toll region, pointing to the tandem office of the local province
Number section of the local mobile network
Analyze it to the MSC common service Vacant number
0
National toll-service number analyzer
International toll-service number analyzer
All numbers are analyzed by the subsequent analyzers
0 + Local area code + Local PSTN number
Analyze it to the local-network outgoing/local-call service, pointing to the gateway office
0 + Non-local area code
Analyze it to the automatic service in the national toll region, pointing to the tandem office of the local province
00 + International number
Analyze it to the international toll automatic service
3. Forwarding DAS: used to analyze the number to which the call is forwarded, as shown in Table 84. TABLE 84 FORWARDING DAS Analyzer Entry
Analyzed Number
Analysis Result Vacant number
0 Local-network number analyzer Local PSTN number
196
Confidential and Proprietary Information of ZTE CORPORATION
All numbers are analyzed by the subsequent analyzers Analyze it to the local-network outgoing/local-call service, pointing to the gateway office
Chapter 7 Basic Service Data Configuration
Analyzer Entry
Analyzed Number
Analysis Result
Local number section of other mobile network
Analyze it to the local-network outgoing/local-call service, pointing to the gateway office
Non-local number section of other mobile network
Analyze it to the automatic service in the national toll region, pointing to the tandem office of the local province
Number section of the local mobile network
Analyze it to the MSC common service Vacant number
0
National tollservice number analyzer
All numbers are analyzed by the subsequent analyzers
0 + Local area code + Local PSTN number
Analyze it to the local-network outgoing/local-call service, pointing to the gateway office
0 + Non-local area code
Analyze it to the automatic service in the national toll region, pointing to the tandem office of the local province
4. Roaming DAS: used to analyze the roaming number in the response message to the routing information query message, as shown in Table 85. It is unnecessary to analysis the CC in national roaming numbers. TABLE 85 ROAMING DAS Analyzer Entry
Local-network number analyzer
Analyzed Number
Analysis Result
Roaming number section of the local service area in the local office
Analyze it to the local MSC service Analyze it to the outgoing service of the local MSC.
Roaming number section of non-local service area in the local office
Note: The roaming DAS is used when there is no direct voice channel between MGWs (switched through the T office) in the region networking
Confidential and Proprietary Information of ZTE CORPORATION
197
ZXWN MSCS Data Configuration Guide(MGCF)
Analyzer Entry
Analyzed Number
Analysis Result
National other roaming sections
Analyze it to the national toll call
00 + International number
Analyze it to the international toll automatic service
Overview Description Data Configuration
This section only introduces the basic steps of number analysis. The related operations of the number analysis configuration are as follows. Steps
Operations
Commands
1
Creating a number analyzer entrance
ADD ENTR
2
Creating a DAS
ADD DAS
3
Creating the default DAS template of the local office
SET LDASTMPLT
4
Creating a DAS template (optional)
ADD ACRTMPLT
5
Creating the called numbers analysis
ADD TPDNAL
Creating Number Analysis Entrance Prerequisites
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The number analysis entrance range is set in the resource management system.
�
The MML Terminal window is opened.
Context
Configuring number analysis entrance means specifying an ID for each type of number analyzers.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a number analysis entrance by executing command A DD ENTR.
198
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
The explanation of the main parameters in command ADD ENTR is shown in Table 86. TABLE 86 PARAMETERS IN THE ADD ENTR COMMAND Parameter Name
Parameter Description
Instruction
ID
Analyzer entry
It is an optional parameter, which is an integer, ranging from 1 to 1000
NAME
User alias
It is a mandatory parameter, consisting of 0~50 characters
Analyzer entry type
It is an optional parameter. Refer to Table 87 for the configuration description
TYPE
Number analysis result under this analyzer, including
NTYPE
VMSCIDX
�
CALLED (analysis on called numbers)
�
CALLING (analysis on calling numbers)
�
FORWARD (analysis on calling numbers during call forwarding)
�
OPIMSI (analysis on calling IMSI numbers)
�
TPIMSI (analysis on called IMSI numbers)
�
FWDIMSI (analysis on IMSI numbers during call forwarding)
�
RDCALLED (Redirecting Number Analysis)
Virtual MSC index
It is an optional parameter, with CALLED as the default value. In general, select CALLED
It is an optional parameter, which is an integer, ranging from 0 to 65535. Enter it according to the actual condition. The default value is 0 (public domain)
Confidential and Proprietary Information of ZTE CORPORATION
199
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 87 ANALYZER ENTRY TYPES Parameter Name
Parameter Description
Configuration Description
NEWSRV
New service number analyzer
After this analyzer is configured, if the number is not matched in this analyzer, it is sent to the next entry for analysis
CENTREX
CENTREX number analyzer
This analyzer is not configured
PRINET
Private-network number analyzer
This analyzer is not configured
SPECSRV
Special-service number analyzer
After this analyzer is configured, if the number is not matched in this analyzer, it is is sent to the next entry for analysis
LOCAL
Local-network number analyzer
After this analyzer is configured, if the number is not matched in this analyzer, the analysis ends
NATIONAL
National toll-service number analyzer
After this analyzer is configured, if the number is not matched in this analyzer, the analysis ends
INTER
International toll-service number analyzer
After the number is analyzed in this analyzer, the analysis ends
Example: Create a number analysis entrance with the following requirements. �
Number analyzer entry ID: 1
�
User alias: Entr1
�
Number analyzer entry type: Local number analyzer
�
Analyzed number type: Called number.
The command is: ADD ENTR:ID=1,NAME="Entr1",TYPE=LOCAL,NTYPE=CAL LED; END OF STEPS Result
200
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Creating Number Analysis Selector Prerequisites
Context
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The Nnumber analysis selector (DAS) range is set in the resource management system.
�
The number analyzer entry is configured.
�
The MML Terminal window is opened.
The DAS is the collection of various number analyzer entries, specifying the order and rule of performing number analysis. Table 88 lists common DASs. TABLE 88 COMMON DAS Parameter Name
Parameter Description
Configuration Description
MS
MS originating
Used to analyze the called number when an MS originates a call
MSRN
Mobile station roaming number
Used to analyze roaming numbers or handover numbers
CNG
Calling number analysis
Used for traffic division of calling numbers
LI
Intercepted number
Used for the interception function
PBRT
Personal Back Ring Tone
Used for the PBRT function
FWD
Forwarding number analysis
Used to analyze the third-party number to which the call is forwarded
Number pre-analysis
Used for the number pre-analysis function, standardizing called numbers, and performing call restriction based on numbers
PREDAS
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create number analysis selector by executing command ADD DAS. The explanation of the main parameters in command ADD DAS is shown in Table 89.
Confidential and Proprietary Information of ZTE CORPORATION
201
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 89 PARAMETERS IN THE ADD DAS COMMAND
Parameter Name
Parameter Description
Instruction
ID
DAS
It is a mandatory parameter, which is an integer, ranging from 1 to 4096. It is the index number of the newly-added DAS
NAME
User alias
It is an optional parameter, consisting of 0~50 characters.
NEWSRV
New service number analyzer entry
CENTR
CENTREX number analyzer entry
PRINET
Private-network number analyzer entry
SPECSRV
Special-service number analyzer entry
LOCAL
Local-network number analyzer entry
NATIONAL
National toll-service number analyzer entry
INTER
International toll-service number analyzer entry
Enter the number analyzer entry IDs contained by a DAS
Example: Create a MS originating DAS with the following requirements. �
DAS ID: 101
�
User alias: MSQH
�
Local number analyzer entry: 1
�
Other parameters: Adopt the default values.
The command is: ADD DAS:ID=101,NAME="MSQH",NEWSRV=0,CENTR =0,PRINET=0,SPECSRV=0,LOCAL=1,NATIONAL=0,INTE R=0; END OF STEPS Result
202
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Setting the Template of Number Analysis Selector of the Current Office Prerequisites
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The DAS is configured.
�
The MML Terminal window is opened.
Context
Configuring the default DAS template of the local office means configuring the DAS used for local-office service processing.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Setting the template of number analysis selector of the current office by executing command SET LDASTMPLT. The explanation of the main parameters in command SET LDASTMPLT is shown in Table 90. TABLE 90 PARAMETERS IN THE SET LDASTMPLT COMMAND Parameter Name
MS
MSRN
Parameter Description
Instruction
MS-Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096. It is used to analyze the called number when an MS originates a call. If the called party is a mobile subscriber, the MSC needs to query the routing information from the corresponding HLR. If the called party is a fixed subscriber, the MSC connect the call to the corresponding local exchange or toll exchange according to location of the called party
Roaming Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096. It is used to analyze the MSRN returned from the HLR, and judge whether the call belongs to the local-office mobile service or outgoing mobile service based on this number. If the call belongs to the local-office mobile service, this number is sent to the corresponding module for processing. If the call belongs
Confidential and Proprietary Information of ZTE CORPORATION
203
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction to the outgoing mobile service, select the corresponding route chain for call connection. In addition, this DAS also analyzes forwarding numbers returned from the HLR, and subscriber numbers from other mobile office or fixed office
OR
Optimal Routing Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096. When it is set that the local office supports preferred routing in the global variable control system, configure this DAS for international roaming call and the forwarding service It is an optional parameter, which is an integer, ranging from 0 to 4096.
CNG
Calling Number Selector
LI
Lawful Interception Number Selector
IP
IP Call Selector
It is used to analyze the calling number in outgoing calls to implement traffic division of the calling number and calling number change function It is an optional parameter, which is an integer, ranging from 0 to 4096. It is used for the interception service It is an optional parameter, which is an integer, ranging from 0 to 4096. It is used for the IP telephone service
ICBCNG
It is an optional parameter, which is an integer, ranging from 0 to 4096. It is used for the incoming call restriction service
Personal Back Ring Tone Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096.
FWD
Default Forward Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
FWDCNG
Default Forward Calling Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
PBRT
204
Incoming Call Limit Calling Number
It is used for the PBRT service
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Instruction
ROUTCAT1
MS Category 1 Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
ROUTCAT2
MS Category 2 Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
ROUTCAT3
MS Category 3 Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
ROUTCAT4
MS Category 4 Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
ROUTCAT5
MS Category 5 Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
IMSIOPDAS
Calling IMSI Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
OVERLAY
Overlay Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
SHLRSKEY
SHLR Service Key Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
IMSITPDAS
Called IMSI Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
IMSIFWDAS
Forward IMSI Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
TESTCALLDAS
Test Call Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
MBRT
Multimedia Back Ring Tone Number
It is an optional parameter, which is an integer, ranging from 0 to 4096
INTPREDAS
International Number Pre-analysis
It is an optional parameter, which is an integer, ranging from 0 to 4096
PREDAS
Originating Number Pre-Analysis Selector
It is an optional parameter, which is an integer, ranging from 0 to 1000
RECNCTDAS
Default Reconnection Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
Confidential and Proprietary Information of ZTE CORPORATION
205
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
CAMELDNALIDX
CAMEL Caller Number Selector Index
It is an optional parameter, which is an integer, ranging from 0 to 1000
SSDAS
Caller Supplementary Service Code Selector Index
It is an optional parameter, which is an integer, ranging from 0 to 1000
ASCODEDAS
ASCODE Selector Index
It is an optional parameter, which is an integer, ranging from 0 to 4096
Example: Configure the default DAS template of the local office with the following requirements. �
MS originating DAS: 101
�
MSRN DAS: 201
�
Forwarding DAS: 301.
The command is: SET LDASTMPLT:MS=101,MSRN=201,FWD=301; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating Templet of Number Analysis Selector (Optional) Prerequisites
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The MML Terminal window is opened.
Context
It is required to configure multiple DAS templates in the dual-homing or regional networking.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create templet of number analysis selector by executing command ADD ACRTMPLT. The explanation of the main parameters in command ADD ACRTMPLT is shown in Table 91.
206
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
TABLE 91 PARAMETERS IN THE ADD ACRTMPLT COMMAND Parameter Name
Parameter Description
Instruction
TPLIDX
Analysis Selector Templet Index
It is a mandatory parameter, ranging from 1~65535
NAME
User alias
It is a mandatory parameter, consisting of 1~50 characters
MS-Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096. It is used to analyze the called number when an MS originates a call. If the called party is a mobile subscriber, the MSC needs to query the routing information from the corresponding HLR. If the called party is a fixed subscriber, the MSC connect the call to the corresponding local exchange or toll exchange according to location of the called party
Roaming Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096. It is used to analyze the MSRN returned from the HLR, and judge whether the call belongs to the local-office mobile service or outgoing mobile service based on this number. If the call belongs to the local-office mobile service, this number is sent to the corresponding module for processing. If the call belongs to the outgoing mobile service, select the corresponding route chain for call connection. In addition, this DAS also analyzes forwarding numbers returned from the HLR, and subscriber numbers from other mobile office or fixed office
MS
MSRN
Confidential and Proprietary Information of ZTE CORPORATION
207
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction It is an optional parameter, which is an integer, ranging from 0 to 4096.
OR
Optimal Routing Number Selector
When it is set that the local office supports preferred routing in the global variable control system, configure this DAS for international roaming call and the forwarding service It is an optional parameter, which is an integer, ranging from 0 to 4096.
CNG
LI
Calling Number Selector
Lawful Interception Number Selector
It is used to analyze the calling number in outgoing calls to implement traffic division of the calling number and calling number change function It is an optional parameter, which is an integer, ranging from 0 to 4096. It is used for the interception service
IP
IP Call Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096. It is used for the IP telephone service
ICBCNG
PBRT
Incoming Call Limit Calling Number
Personal Back Ring Tone Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096. It is used for the incoming call restriction service It is an optional parameter, which is an integer, ranging from 0 to 4096. It is used for the PBRT service
FWD
208
Default Forward Number Selector
Confidential and Proprietary Information of ZTE CORPORATION
It is an optional parameter, which is an integer, ranging from 0 to 4096
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Instruction
FWDCNG
Default Forward Calling Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
ROUTCAT1
MS Category 1 Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
ROUTCAT2
MS Category 2 Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
ROUTCAT3
MS Category 3 Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
ROUTCAT4
MS Category 4 Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
ROUTCAT5
MS Category 5 Originating Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
IMSIOPDAS
Calling IMSI Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
OVERLAY
Overlay Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
SHLRSKEY
SHLR Service Key Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
IMSITPDAS
Called IMSI Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
IMSIFWDAS
Forward IMSI Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
TESTCALLDAS
Test Call Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
Confidential and Proprietary Information of ZTE CORPORATION
209
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
MBRT
Multimedia Back Ring Tone Number
It is an optional parameter, which is an integer, ranging from 0 to 4096
INTPREDAS
International Number Pre-analysis
It is an optional parameter, which is an integer, ranging from 0 to 4096
PREDAS
Originating Number Pre-Analysis Selector
It is an optional parameter, which is an integer, ranging from 0 to 1000
RECNCTDAS
Default Reconnection Number Selector
It is an optional parameter, which is an integer, ranging from 0 to 4096
CAMELDNALIDX
CAMEL Caller Number Selector Index
It is an optional parameter, which is an integer, ranging from 0 to 1000
SSDAS
Caller Supplementary Service Code Selector Index
It is an optional parameter, which is an integer, ranging from 0 to 1000
ASCODE Selector Index
It is an optional parameter, which is an integer, ranging from 0 to 4096
ASCODEDAS
Example: Create a DAS template with the following requirements. �
DAS template ID: 1
�
User alias: VMSC1
�
MS originating DAS: 101
�
MSRN DAS: 201
�
Preferred routing DAS: 301
�
Calling number DAS: 401
�
Other parameters: Adopt the default values.
The command is: ADD ACRTMPLT:TPLIDX=1,NAME="VMSC1",MS=101,M SRN=201,OR=301,CNG=401,LI=0,IP=0,CBCNG=0,PBRT =0,CFU=0,CFUCNG=0,CFNDUB=0,CFNDUBCNG=0,CFUD UB=0,CFUDUBCNG=0,CFNRC_E=0,CFNRCCNG_E=0,CF NRC_L=0,CFNRCCNG_L=0,CFNRY=0,CFNRYCNG=0,CD =0,CDCNG=0,FWD=0,FWDCNG=0,CNGVIGW=0,FWDVI GW=0,INTRA=0,ROUTCAT1=0,ROUTCAT2=0,ROUTCAT3 =0,ROUTCAT4=0,ROUTCAT5=0,IMSIOPDAS=0,OVERLA Y=0,LIIGW=0,SHLRSKEY=0,IMSITPDAS=0,IMSIFWDAS
210
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
=0,MBRT=0,INTPREDAS=0,PREDAS=0,CFPRE=0,CFUPR E=0,NDUBPRE=0,UDUBPRE=0,CFNRCE_PRE=0,CFNRCL_ PRE=0,CFNRYPRE=0,CDPRE=0,MORCPRE=0,GMSCRCPR E=0,CFRCPRE=0,MTRCPRE=0,RECNCTDAS=0,CAMELDN ALIDX=0,SSDAS=0,ASCODEDAS=0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating Called Number Analysis Prerequisites
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The number analyzer entry is configured.
�
The MML Terminal window is opened.
Context
This section introduces how to configure number analysis for prefixes of called numbers and roaming numbers. The called number analysis determines the subsequent service procedures of the call.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create the called number analysis by executing command ADD TPDNAL. The explanation of the main parameters in command ADD TPDNAL is shown in Table 92. TABLE 92 PARAMETERS IN THE ADD TPDNAL COMMAND Parameter Name
ENTR
DIGIT
Parameter Description
Instruction
Number analyzer entry
It is a mandatory parameter, which is an integer, ranging from 1 to 1000. Select the corresponding analyzer entry of the analyzed number prefix. For local calls, select the corresponding analyzer entry of the local number analyzer
Analyzer number
It is a mandatory parameter, consisting of 1~20 digits. Input the prefix of the called number, whose length must make it be distinguished in the local office. For intra-office calls, it is required to configure both the prefix of the called number and that of the local-office roaming number
Confidential and Proprietary Information of ZTE CORPORATION
211
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction It is an optional parameter, consisting of 0~50 characters.
NAME
SPECRST
SPECIDX
212
User alias
It is used to specifically describe the called number analysis to make it easily recognized
Special analysis result rule
It is used to specify the index number of the special analysis result rule for the associated called number. This parameter must be defined by command ADD CEDSPECRL at first. Then it can be indexed here. This parameter is configured to implement the routing service based on number length. When the system performs analysis on the called number, it automatically matches the actual length of the called number to see whether the length is within the range of “Special analysis result rule for called numbers”. If the length is within the range, the system adopts the routing information in “Special analysis result of called numbers”. Otherwise, the system adopts the routing information in the called number analysis
Special analysis result index
It is used to specify the index number of the special analysis result of the associated called number. This parameter must be defined by command ADD SPECRST at first. Then it can be indexed here. This parameter is configured to implement the routing service based on number length. When the system performs analysis on the called number, it automatically matches the actual length of the called number to see whether the length is within the range of “Special analysis result rule for called numbers”. If the length is within the range, the system adopts the routing information in “Special analysis result of called numbers”. Otherwise, the system adopts the routing information in the called number analysis
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Call service types, including the options in
CAT
Instruction It is an optional parameter. It is used to specify the service type triggered by this number, and determine the direction of this call. The system adopts “vacant number” by default. The called number of the local office is analyzed to LOL (Outgoing/local service of the local network). When the call service type is vacant number, local-network local-office/common service, MSC local-network local-office service, Mobile Number Portability (MNP), or H323 call, number analysis result 1 must be fixed to 0. When the call service type is outgoing call or toll call, number analysis result 1 is used to specify the index number of the outgoing route chain. When the call service type is “equal access: CIC of the operator where the subscriber is located” or “equal access: non-local-network CIC”, number analysis result 1 is used to specify the index number of the outgoing route chain.
RST1
Number analysis result 1
When the call service type is “OVERLAY prefix incoming service”, number analysis result 1 is used to specify the index number of the outgoing route chain. When the call service type is “OVERLAY: CAMEL service triggered by MO”, or “OVERLAY: CAMEL service triggered by MT”, number analysis result 1 is used to specify the index number of the outgoing route chain. When the call service type is “IP service”, “IP mobile service”, or “independent IP service” number analysis result 1 is used to specify the index number of the outgoing route chain. When the call service type is “MNP outgoing routing” number analysis result 1 is used to specify the index number of the outgoing route chain. When the call service type is “Outgoing paid special service” or “Outgoing free special service”, number analysis result 1 is used to specify the index number of the outgoing route chain.
Confidential and Proprietary Information of ZTE CORPORATION
213
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction The above-specified index number of the outgoing route chain must be defined by command ADD CHAIN at first. Then it can be indexed here. When the call service type is “Mobile emergency special service”, “Local-office paid special service” or “Local-office free special service”, number analysis result 1 is used to specify the special-service number. This parameter must be defined by command ADD SSPN at first. Then it can be indexed here. When the call service type is “Tone play service, CAT_SEND_TONE”, number analysis result 1 is used to specify the ID of the tone to be played
RST2
Number analysis result 2
It is used to specify the index number of CAMEL access subscription information of the calling subscriber. This parameter must be defined by command ADD CAINFO at first. Then it can be indexed here. When the call service type is “equal access: CIC of the operator where the subscriber is located” or “equal access: non-local-network CIC, this parameter must be configured. When the call service type is “OVERLAY: CAMEL service triggered by MO”, or “OVERLAY: CAMEL service triggered by MT”, this parameter must be configured. When the call service type is other types except the above-listed, number analysis result 2 must be fixed to 0
RST3
214
Number analysis result 3
It is used to specify the index number of CAMEL access subscription information of the called subscriber. This parameter must be defined by command ADD CAINFO at first. Then it can be indexed here. When the call service type is “OVERLAY: CAMEL service triggered by MO”, or “OVERLAY: CAMEL service triggered by MT”, this parameter must be configured. When the call service type is other types except the above-listed, number analysis result 3 must be fixed to 0
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
CHAINAL
RNLEN
Parameter Description
Instruction
Route chanin analysis index
It is used to specify the analysis index number of the route chain. This parameter must be defined by command ADD CHAINAL at first. Then it can be indexed. This parameter takes effect only when the call service type is outgoing service (including various outgoing services). It priority is higher than that of the outgoing route chain referred to in number analysis result 1. Route chain analysis is an intelligent routing policy better than the policy of specifying a single route chain
Length of the carried routing number
When the call service type is “MNP outgoing routing”, it is configured to the length of the carried routing number. When the call service type is other types except the above-listed, it must be fixed to 0 It is an optional parameter, which is an integer ranging from 0 to 255, with a default of 3. It is used to specify the minimum digit length of the analyzed number required for call connection.
MINLEN
Minimum digit length of numbers
During an incoming call, if the received digits are shorter than this length, the system waits for the subsequent digits. If the system judges that there is no subsequent digit, and the received digits are shorter than this length, the system considers that the number format is wrong, and releases the call. During a local-office-originated call, if the received digits are shorter than this length, the system considers that the number format is wrong, and releases the call. For the OVERLAY prefix incoming service, the system gets the length of the OVERLAY prefix according to the minimum digit length of numbers. Therefore, it is required to configure the minimum digit length of numbers to the length of the OVERLAY prefix. Otherwise, procedures cannot be correctly processed
Confidential and Proprietary Information of ZTE CORPORATION
215
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction It is an optional parameter, which is an integer ranging from 0 to 255, with a default of 20. It is used to specify the maximum digit length of the analyzed number required for call connection.
MAXLEN
Maximum digit length of numbers
During an incoming call, it is the basis of whether to wait for subsequent digits. If the received digits reach this length, the system does not wait for subsequent digits. During a local-office-originated call, if the received digits are longer than this length, the system determines whether to continue or release the call according to flag “No call when the called number exceeds the length” in the option enabling configuration. If the system determines to continue the call, it cuts the exceeding digits
OVERLAY priority, including:
OVLYPRI
NO (No priority): Trigger the intelligent service based on CSI at first, and then trigger the intelligent service again based on OVERLAY HCSI (Higher than the CSI in priority): Trigger the intelligent service based on OVERLAY at first, and then trigger the intelligent service again based on CSI
216
It is used to the priority relationship between triggering the intelligent service based on CSI and triggering the intelligent service based on OVERLAY. The system adopts “no priority” by default. When the call service type is “OVERLAY: CAMEL service triggered by MO”, this parameter is effective. Otherwise, this parameter is ineffective
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Instruction
Voice channel release mode, including: CING (calling control release): The calling party controls whether to release the call. In this mode, when only the called party hooks on, the call still can continue.
REL
CED (called control release): The called party controls whether to release the call. In this mode, when only the calling party hooks on, the call still can continue.
It is an optional parameter. It indicates a resource release mode when subscribers hook on. In general, select NO. Select CED for such special numbers as 110 and 119
NO (noncontrol release): Both the calling party and the called party can control whether to release the call. In this mode, no matter whether the calling party or the called party hooks on, the call is released
NET
Type of the destination network
It is an optional parameter, with a default of 1. For calls to other office in the local network, select the signaling network where the destination office is located. For intra-office calls, this option is meaningless.
Confidential and Proprietary Information of ZTE CORPORATION
217
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
Number address attribute, including: DEF (default attribute): Do not replace the address attribute of the analyzed number. INT (international number): Replace the address attribute of the analyzed number with international number. NAT
NAT (national number): Replace the address attribute of the analyzed number with national (valid) number. LOC (local number): Replace the address attribute of the analyzed number with local number.
It is an optional parameter. It is used to replace the address attribute of the analyzed number. In general, it is set to DEF, or is set according to the requirements of the peer end
UNK (attribute unknown): Replace the address attribute of the analyzed number with unknown Transforming the calling number again, including:
OPDDICONT
NO (Not allowed): It is not allowed to transform the calling number again in the subsequent call procedures.
It is an optional parameter. It is used to specify whether it is allowed to transform the calling number again in the subsequent call procedures when the calling number was already transformed once. The system adopts NO by default
YES (allowed): It is allowed to transform the
218
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Instruction
calling number again in the subsequent call procedures. Transforming the called number again, including:
TPDDICONT
NO (Not allowed): It is not allowed to transform the called number again in the subsequent call procedures. YES (allowed): It is allowed to transform the called number again in the subsequent call procedures
OPDDI
TPDDI
OPDLYDDI
It is an optional parameter. It is used to specify whether it is allowed to transform the called number again in the subsequent call procedures when the called number was already transformed once. The system adopts NO by default
Calling-number immediate transform index
It is an optional parameter. It is the number stream transform index of the calling-number immediate transform. Immediate transform immediately makes the calling number transformed. This parameter must be defined by command ADD DDI at first. Then it can be indexed here
Called-number immediate transform index
It is an optional parameter. It is the number stream transform index of the called-number immediate transform. Immediate transform immediately makes the called number transformed. This parameter must be defined by command ADD DDI at first. Then it can be indexed here
Calling-number delay transform index
It is an optional parameter. It is the number stream transform index of the calling-number delay transform. Delay transform takes effects in the IAM message at the outgoing side instead of making the calling number transformed immediately. This parameter must be defined by command ADD DDI at first. Then it can be indexed here. According to the IAM message at the outgoing side, perform the calling-number delay transform here, and then perform the
Confidential and Proprietary Information of ZTE CORPORATION
219
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction calling-number delay transform in the number pre-analysis
TPDLYDDI
DDIOVERB
Called-number delay transform index
It is an optional parameter. It is the number stream transform index of the called-number immediate transform. Immediate transform immediately makes the called number transformed. This parameter must be defined by command ADD DDI at first. Then it can be indexed here
B-interface number transform index
It is the number stream transform index of the called number in the outgoing call request message between the MSC and the VLR. The transform purpose is to facilitate the VLR judging the toll call authority. This parameter must be defined by command ADD DDI at first. Then it can be indexed here
Whether to support the interworking between video calls, including:
IWVEDIO
LSUP: Local-network subscribers support the interworking between video calls by default). The call continues. OSUP: Subscribers in other networks support the interworking between video calls). The call continues.
It is an optional parameter. It is used to specify whether to support the interworking between video calls. The default value is LSUP
ONSUP: Subscribers in other networks do not support the interworking
TIMELMT
220
Maximum call duration (minute)
It is used to specify the maximum call duration allowed for a call. When the duration of a call reaches the maximum call duration, the system automatically release the call. If it is unnecessary to restrict the maximum call duration, adopt the default value of 0
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Instruction
AUXDAS
Assistant DAS
It is an optional parameter. It is used to specify the DAS for analyzing the called number again when the call service type is outgoing service, and when the connection between the local office and the mutually-backed-up office is broken in the mutual backup dual-homing networking. This parameter must be defined by command ADD DAS at first. Then it can be indexed here
A6
Sending A6 signal after receiving how many digits during incoming calls
It is used to specify the number of digits that the system receives enough to send A6 signal to the front office. This parameter only takes effect during incoming calls using Channel Associated Signaling (CAS)
Toll prefix + Area code length
It is an optional parameter, which is an integer, ranging from 0 to 15. When the call service type is national/international toll service, this parameter needs to be configured
Enabled options Refer to Table 94 for details
It is an optional parameter. In general, select CCS7 (Automatically sending the calling number when using CCS7 for outgoing services) and (No call when the called number exceeds the maximum digit length)
Fax analysis resutl index
It is used to specify the bearer analysis result index number of the called number associated with the fax service. This parameter must be defined by command ADD BEARRST at first. Then it can be indexed here. This parameter is configured to implement the routing service based on the bearer capability. For the fax service, if the associated bearer analysis result index of the called number is configured, the call adopts the associated bearer analysis result of the called number, thus flexible routing is implemented
PFXLEN
ENOPT
FAXIDX
Confidential and Proprietary Information of ZTE CORPORATION
221
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
AVIDX
DVIDX
ADATAIDX
222
Parameter Description
Instruction
Analog video analysis result index
It is used to specify the bearer analysis result index number of the called number associated with the analog video service. This parameter must be defined by command ADD BEARRST at first. Then it can be indexed here. This parameter is configured to implement the routing service based on the bearer capability. For the analog video service, if the associated bearer analysis result index of the called number is configured, the call adopts the associated bearer analysis result of the called number, thus flexible routing is implemented
Digital video analysis result index
It is used to specify the bearer analysis result index number of the called number associated with the digital video service. This parameter must be defined by command ADD BEARRST at first. Then it can be indexed here. This parameter is configured to implement the routing service based on the bearer capability. For the digital video service, if the associated bearer analysis result index of the called number is configured, the call adopts the associated bearer analysis result of the called number, thus flexible routing is implemented
Analog data analysis result index
It is used to specify the bearer analysis result index number of the called number associated with the analog data service. This parameter must be defined by command ADD BEARRST at first. Then it can be indexed here. This parameter is configured to implement the routing service based on the bearer capability. For the analog data service, if the associated bearer analysis result index of the called number is configured, the call adopts the associated bearer analysis result of the called number, thus flexible routing is implemented
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
DDATAIDX
Parameter Description
Instruction
Digital data analysis result index
It is used to specify the bearer analysis result index number of the called number associated with the digital data service. This parameter must be defined by command ADD BEARRST at first. Then it can be indexed here. This parameter is configured to implement the routing service based on the bearer capability. For the digital data service, if the associated bearer analysis result index of the called number is configured, the call adopts the associated bearer analysis result of the called number, thus flexible routing is implemented
Whether to play the DDC tone, including:
DDCPLAY
NONE (Not playing the DDC tone): It is not required to play the DDC tone in the local office. PLAY (Playing the DDC tone): It is required to play the DDC tone in the local office.
It is used to specify whether to play the DDC tone in the local office. The system adopts NONE by default. The purpose of configuring whether to play the DDC tone in the number analysis configuration is to avoid no tone play or repeated tone play caused by inconsistent tone play configuration during inter-office DDC calls
Voice Activity Detection (VAD) flag, including: CLOSE: Not starting the VAD function. OPEN: Starting the VAD function.INVALID: The VAD function is invalid
VAD
OPPMGWID
Opposite-end MGW ID
It is used to specify whether to start the VAD function. The system adopts INVALIDby default
It is used to specify between which opposite-end MGW and the local MGW the TDM backup route is adopted. The QOSs between the local MGW and all opposite-end MGWs can be found through automatic test calls. When the QOS difference between the opposite-end MGW and the local MGW is specified, the call adopts the TDM backup route
Confidential and Proprietary Information of ZTE CORPORATION
223
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
Call type priority, including: INVALID: The call priority is invalid. HIGHEST: The call has the highest priority.
CALLSERVPRILVL
HIGHER: The call has a priority one level lower than the highest priority. NORMAL: The call has a priority one level lower than the higher priority.
It is used to specify the call priority. The system adopts INVALID by default. The call priority has two functions. In one case, in the softswitch office in the toll softswitch network, the voice coding format can be dynamically selected according to the call priority and the load on the IP bearer network. In another case, based on the combined information of office ID and priority configured in the number analysis configuration, the final priority of a call is got to perform load control
LOW: The call has the lowest priority
RERTS
Re-routing route chain
It is used to specify the re-routing route chain ID. This parameter must be defined by command ADD RERTS at first. Then it can be indexed here. When flag RRTO in enabled options takes effect, the re-routing route chain takes effect too. For an outgoing call procedure, if the call fails, and the corresponding failure cause is configured with “Enabling rerouting for failure” in the R_ICP configuration, re-select the route from this route chain according to the re-routing route chain. For an incoming call using ISUP, TUP, or BICC signaling, when the call procedure is an outgoing procedure, and the call fails before the IAM message is sent, the re-routing route chain serves as the standby route, and is not controlled by RRTO. If route chain analysis is configured, the re-routing route chain here is invalid. In this case, use the re-routing route chain configured in the route chain analysis
224
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Inter-MGW route chain or not, including:
INCHAIN
NO: The outgoing route chain got from number analysis is not an inter-MGW route chain. YES: The outgoing route chain got from number analysis is an inter-MGW route chain
Instruction It is used to specify whether the outgoing route chain got from number analysis is an inter-MGW route chain. The system select NO by default. If YES is selected, the routes in the outgoing route chains will not be selected for the outgoing route. The outgoing route will be got after perform number analysis again according to the associated called number DAS configured in the outgoing route chain. This parameter is used in the following cases: One virtual outgoing route chain is got based on number analysis at first, and then the real outgoing route is got based on the called number DAS associated with the virtual outgoing route chain. When one MSCS controls multiple areas, the outgoing route chain facilitates subscriber management
RECMDMGWNODEID
Recommended MGW nodes
It is used to specify the set of recommended MGWs for outgoing service. In the case of multiple IP domains, if one MSCS manages multiple MGWs, and these MGWs belong to different IP domains, the set of recommended MGWs for outgoing service needs to be configured. The MGW set here should be a sub-set of the MGW set supported by outgoing service. This parameter must be defined by command ADD TOPO at first. Then it can be indexed here
TABLE 93 CALL SERVICE TYPES Call Service Types
Meanings
Description
NULL
Vacant number
Indicates that the subsequent call procedures are processed based on the procedure of processing vacant numbers
LLC
Localnetwork localoffice/common service
Indicates that the subsequent call procedures are processed based on the local service procedure
Confidential and Proprietary Information of ZTE CORPORATION
225
ZXWN MSCS Data Configuration Guide(MGCF)
Call Service Types
Meanings
Description
LOL
Local-network outgoing/localcall service
Indicates that the subsequent call procedures are processed based on the local-call service procedure. The mobile-to-fixed local outgoing call service is usually analyzed to this type
LORU
Local-network outgoing/rural (network) call service
Indicates that the subsequent call procedures are processed based on the local rural (network) outgoing call service procedure. The mobile-to-fixed rural outgoing call service is usually analyzed to this type
DWTM
Domestic toll (intra-region) manual service
Indicates that the subsequent call procedures are processed based on the domestic toll (intra-region) manual service procedure. In general, it is not recommended to configure this service type
DWTA
Domestic toll (intra-region) automatic service
Indicates that the subsequent call procedures are processed based on the domestic toll (intra-region) automatic service procedure. In general, it is not recommended to configure this service type
DBTM
Domestic toll (inter-region) manual service
Indicates that the subsequent call procedures are processed based on the domestic toll (inter-region) manual service procedure. In general, it is not recommended to configure this service type
DBTA
Domestic toll (inter-region) automatic service
Indicates that the subsequent call procedures are processed based on the domestic toll (inter-region) automatic service procedure. The domestic toll call service is usually analyzed to this type
INTM
International toll manual service
Indicates that the subsequent call procedures are processed based on the international toll manual service procedure. In general, it is not recommended to configure this service type
International toll automatic service
Indicates that the subsequent call procedures are processed based on the international toll automatic service procedure. The international toll call service is usually analyzed to this type
INTA
226
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Call Service Types
Meanings
Description
Local-office paid special service
Indicates that the subsequent call procedures are processed based on the local-office paid special service procedure. The local-office paid special service is usually analyzed to this type
Local-office free special service
Indicates that the subsequent call procedures are processed based on the local-office free special service procedure. The local-office free special service is usually analyzed to this type
Outgoing paid special service
Indicates that the subsequent call procedures are processed based on the outgoing paid special service procedure. The outgoing paid special service is usually analyzed to this type
Outgoing free special service
Indicates that the subsequent call procedures are processed based on the outgoing free special service procedure. The outgoing free special service is usually analyzed to this type
DEPS
Additional service
Indicates that the subsequent call procedures are processed based on the additional service procedure. In general, it is not recommended to configure this service type
CENTL
Intra-office call within the CENTREX business group
Indicates that the subsequent call procedures are processed based on the intra-office call procedure within the CENTREX business group.
CENTO
Outgoing call within the CENTREX business group
Indicates that the subsequent call procedures are processed based on the outgoing call procedure within the CENTREX business group
TELCA
Intelligent Ntwork service call
Indicates that the subsequent call procedures are processed based on the intelligent network service call procedure
EQACL
Equal access: CIC of the operator where the subscriber is located
Indicates that the subsequent call procedures are processed based on the procedure of “Equal access: CIC of the operator where the subscriber is located”
LSPA
LSFR
OUPA
OUFR
Confidential and Proprietary Information of ZTE CORPORATION
227
ZXWN MSCS Data Configuration Guide(MGCF)
Call Service Types
Meanings
Description
EQACO
Equal access: non-localnetwork CIC
Indicates that the subsequent call procedures are processed based on the procedure of “Equal access: non-local-network CIC”
Tone play service, CAT_SEND_TONE
Indicates that the subsequent call procedures are processed based on the tone play service procedure. After calling the number that is analyzed to this type, the system will directly play the tone according to the tone ID configured in number analysis result 1
Toll DDC incoming call
Indicates that the subsequent call procedures are processed based on the toll DDC incoming call service procedure. The toll incoming DDC call that needs to be routed in the local office is analyzed to this type
Local DDC call
Indicates that the subsequent call procedures are processed based on the local DDC call service procedure. The local DDC call (dialing the MSISDN number) that needs to be routed in the local office is analyzed to this type
Toll DDC outgoing call
Indicates that the subsequent call procedures are processed based on the toll DDC outgoing call service procedure. The toll outgoing DDC call is analyzed to this type
Local DDC outgoing call
Indicates that the subsequent call procedures are processed based on the local DDC outgoing call service procedure. The local outgoing DDC call is analyzed to this type
MSCO
MSC common service
Indicates that the subsequent call procedures are processed based on the MSC common service procedure. The call (dialing the MSISDN number) that needs to be routed in the local office is analyzed to this type
MSLL
MSC localnetwork local-office service (only for roaming numbers)
Indicates that the subsequent call procedures are processed based on the MSC local-network local-office service procedure. It is used to analyze the roaming numbers and handover numbers of the local office
STONE
DDCI
DDCC
DDCO
DDCCO
228
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Call Service Types
Meanings
Description
MSLO
MSC local outgoing service (only for roaming numbers)
Indicates that the subsequent call procedures are processed based on the local outgoing service procedure. The local outgoing call of roaming numbers is analyzed to this type
CINRE
Calling-number incoming call restriction
Indicates that the subsequent call procedures are processed based on the calling-number incoming call restriction procedure
MSLTE
MSC national toll call (only for roaming numbers)
Indicates that the subsequent call procedures are processed based on the MSC national toll call service procedure. The toll outgoing call of roaming numbers is analyzed to this type
AAC
Automatic response number
Indicates that the subsequent call procedures are processed based on the automatic response number service procedure
OVERLAY prefix incoming service
Indicates that the subsequent call procedures are processed based on the OVERLAY prefix incoming service procedure. The OVERLAY prefix incoming call is analyzed to this type
OVCS
OVERLAY call service
Indicates that the subsequent call procedures are processed based on the OVERLAY call service procedure. It is used for the IGW system
MSITE
MSC international toll call (only for roaming numbers)
Indicates that the subsequent call procedures are processed based on the MSC international toll call service procedure. The international toll outgoing call is analyzed to this type
IP
IP fixed service
Indicates that the subsequent call procedures are processed based on the IP fixed service procedure. It is used for the IGW system
SSP
SSP charging and querying service
Indicates that the subsequent call procedures are processed based on the SSP charging and querying service procedure.
NSSP
Non-SSP charging and querying service
Reserved
OVPRE
Confidential and Proprietary Information of ZTE CORPORATION
229
ZXWN MSCS Data Configuration Guide(MGCF)
Call Service Types
230
Meanings
Description
IPMO
IP mobile service
Indicates that the subsequent call procedures are processed based on the IP mobile service procedure. The IP service in the mobile system is analyzed to this type
INSIP
IP service dialed by intelligentnetwork subscribers
Reserved
ALIP
Independent IP service
Indicates that the subsequent call procedures are processed based on the independent IP service procedure. The independent IP incoming call is analyzed to this type
OVMO
OVERLAY: MO-triggered CAMEL service
Indicates that the subsequent call procedures are processed based on the “OVERLAY: MO-triggered CAMEL service” procedure
OVMT
OVERLAY: MT-triggered CAMEL service
Indicates that the subsequent call procedures are processed based on the “OVERLAY: MT-triggered CAMEL service” procedure
MNP
Mobile number portability
Indicates that the subsequent call procedures are processed based on the MNP service procedure
MNPR
MNP MNP outgoing routing
Indicates that the subsequent call procedures are processed based on the MNP outgoing routing service procedure
SIPO
SIP outgoing call
Indicates that the subsequent call procedures are processed based on the SIP outgoing call service procedure
H323
H323 call
Indicates that the subsequent call procedures are processed based on the H323 call service procedure.
MOIMC
Mobile emergency special service
Indicates that the subsequent call procedures are processed based on the mobile emergency special service procedure
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Call Service Types
Meanings
Description
SSSP
Independent SSP outgoing service
Indicates that the subsequent call procedures are processed based on the independent SSP outgoing service procedure. The SSSP (Independent SSP outgoing service) in the analysis result of the called number is used for the IGW system
IGWA
IGW supplementary service (only for IGW)
Indicates that the subsequent call procedures are processed based on the IGW supplementary service procedure
DASA
DAS service (virtual IGW) (only for IGW)
A new DAS is got through number analysis, which is used for the subsequent analysis of the called number
OCIC
Local valid CIC service
Indicates that the subsequent call procedures are processed based on the local valid CIC service procedure. This parameter is reserved
OUPAOD
Outgoing paid special service (can be dialed by the defaulting subscribers)
Indicates that the subsequent call procedures are processed based on the outgoing paid special service (can be dialed by the defaulting subscribers) procedure
LINTS
Local-office intelligent service
Indicates that the subsequent call procedures are processed based on the local-office intelligent service procedure. It is used for the IGW system
SHLRQ
SHLR querying service (only for IGW)
Indicates that the subsequent call procedures are processed based on the SHLR querying service procedure
IGWC
IGW common service (only for IGW)
Indicates that the subsequent call procedures are processed based on the IGW common service procedure. The call to PHS subscribers, which needs to be routed in the local office, is analyzed to this type
ISSPQ
IGWSSP charging and querying service (only for IGW)
Indicates that the subsequent call procedures are processed based on the IGW SSP charging and querying service procedure
IGWLF
IGW local-office free special service
Indicates that the subsequent call procedures are processed based on the IGW local-office free special service procedure
Confidential and Proprietary Information of ZTE CORPORATION
231
ZXWN MSCS Data Configuration Guide(MGCF)
Call Service Types
Meanings
Description
IGWLP
IGW local-office paid special service
Indicates that the subsequent call procedures are processed based on the IGW local-office paid special service procedure
IGWOV
IGWOVERLAY prefix incoming service
Indicates that the subsequent call procedures are processed based on the IGWOVERLAY prefix incoming service procedure
IGWDDCIN
IGW toll DDC incoming call
Indicates that the subsequent call procedures are processed based on the IGW toll DDC incoming call service procedure
IGWDDCLOCAL
IGW local DDC call
Indicates that the subsequent call procedures are processed based on the IGW local DDC call service procedure
Test call
Indicates that the subsequent call procedures are processed based on the test call service procedure. It is used to analyze test calls
TEST
TABLE 94 ENABLED OPTIONS Enabled Options
CCS7
CHGK
232
Meanings
Description
Automatically sending the calling number when using CCS7 for outgoing services
It indicates whether the outgoing TUP signaling carries the calling number. When the local office actively sends the calling number, it sends an IAI message of TUP signaling to the peer-end office, carrying the calling number. Otherwise, the local office sends an IAM message of TUP signaling to the peer-end office, not carrying the calling number. For ISUP signaling, it indicates whether the local MSC number is filled in the location number information
Changing the type of calling subscribers
Indicates whether to set the type of the calling subscriber in the outgoing IAM message of ISUP or BICC signaling to the calling subscriber types flexibly configured in security variables
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Enabled Options
Meanings
Description
CHGN
Changing the number
Indicates that the analyzed number is changed, and the system notifies the calling subscriber by playing the tone
DELA
Delayed dialing of the special service
Reserved
MAIL
166-voice-mailbox service
Indicates that the call is a 166-voice-mailbox service
NSCP
Not waiting for SCP responses
Reserved
RRTO
Rerouting after outgoing failure
For incoming calls using ISUP, TUP, or BICC signaling, the call procedure is an outgoing call procedure. When the local office does not receives a REL message after sending an outgoing IAM message to the peer-end office, this option control whether rerouting is allowed
NETF
IN forward message
Reserved
VNUM
Virtual number
Reserved
HRA
High rate
Reserved
NTC
Not triggering IN service of the calling number
Indicates whether the call triggers the IN service of the calling number. This option is used for the case where the IN service of the calling number cannot be triggered when the call to the IN subscriber is forwarded or when some special numbers are dialed
NCEL
No call when the called number exceeds the length
Indicates whether the system releases the call if the analyzed number exceeds the configured maximum digit length
Interception number incoming
Indicates whether the call is an incoming call returned from the interception center. This option is only used in the IGW system
LSIN
Confidential and Proprietary Information of ZTE CORPORATION
233
ZXWN MSCS Data Configuration Guide(MGCF)
Enabled Options
CON
SHLRF
SHLRG
JUDG
REBO
Meanings
Description
Sending the “connect” message in advance (only for IGW)
Indicates whether the local office sends a ringing message of the called subscriber and a “connect” message to the calling subscriber at the same time (that is, sends a “connect” message to the calling subscriber before the called subscriber answers the call). This option is only used in the IGW system
Not triggering SHLR query
Indicates whether the number section needs to be transformed in the SHLR during call origination. In the SHLR mixed networking, common call origination procedures need to interact with the SHLR to get the calling logic number, and the called physical number. However, in the specific calls, the called number needs no transform. In this case, select this option in the number analysis result. This option is only used in the IGW system
Over net number in SHLR
Indicates whether the incoming call restrain the SHLR from returning the IN access code. This option is used to prevent repeatedly triggering IN services. This option is only used in the IGW system
Needing to judge the IP resource
Indicates whether the routing query in the SHLR is forcibly performed during IP calls. This option is only used in the IGW system
Restraining HOMEBOX service
Indicates whether incoming calls trigger the HOMEBOX service in the local office. This option is only used in the IGW system
Example: Configure the called number analysis with the following requirements.
234
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
�
Analyzer entry: 1
�
User alias: TPDNAL1
�
Analyzed number: 13902099
�
Call service type: MSC common service
�
Other parameters: Adopt the default values.
The command is: ADD TPDNAL:ENTR=1,DIGIT="13902099",NAME="TPDN AL1",SPECRST=0,SPECIDX=0,CAT=MSCO,RST1=0,RST2 =0,RST3=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN =20,OVLYPRI=NO,REL=NO,NET=1,NAT=DEF,OPDDICO NT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYDD I=0,TPDLYDDI=0,DDIOVERB=0,IWVIDEO=LSUP,TIMEL MT=0,AUXDAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXIDX =0,AVIDX=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,DDC PLAY=NONE,VAD=CLOSE,CALLSERVPRILVL=INVALID,RE RTS=0,INCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GNM=NO RMAL,STBILL=INVALID,HOPDAS=0; Example: Configure the roaming number analysis of the local office with the following requirements. �
Analyzer entry: 1
�
User alias: TPDNAL1
�
Analyzed number: 15902099
�
Call service type: MSC local service
�
Other parameters: Adopt the default values.
The command is: ADD TPDNAL:ENTR=1,DIGIT="15902099",NAME="TPDN AL2",SPECRST=0,SPECIDX=0,CAT=MSLL,RST1=0,RST2 =0,RST3=0,CHAINAL=0,RNLEN=0,MINLEN=3,MAXLEN =20,OVLYPRI=NO,REL=NO,NET=1,NAT=DEF,OPDDICO NT=NO,TPDDICONT=NO,OPDDI=0,TPDDI=0,OPDLYDD I=0,TPDLYDDI=0,DDIOVERB=0,IWVIDEO=LSUP,TIMEL MT=0,AUXDAS=0,A6=0,PFXLEN=0,INSRV=INM,FAXIDX =0,AVIDX=0,DVIDX=0,ADATAIDX=0,DDATAIDX=0,DDC PLAY=NONE,VAD=CLOSE,CALLSERVPRILVL=INVALID,RE RTS=0,INCHAIN=NO,BICT=NO,ICT=0,ICTT=10,GNM=NO RMAL,STBILL=INVALID,HOPDAS=0; END OF STEPS
Trunk Data Configuration Overview The related operations of the trunk data configuration are as follows.
Confidential and Proprietary Information of ZTE CORPORATION
235
ZXWN MSCS Data Configuration Guide(MGCF)
Steps
1
Operations
Instructions
Commands
Creating a DT trunk group
When the A interface and Ai interface adopts the TDM bearer, or when MGWs are interconnected through the TDM bearer, configure DT trunk groups
ADD TG DT
Creating an ATM trunk group
When the ATM bearer is adopted between MGWs, configure ATM trunk groups
ADD TG ATM
Creating a RTP trunk group
When the IP bearer is adopted between MGWs, configure BICC trunk groups. When the MSCS servers as a MGCF, configure SIP trunk groups for MGWs
ADD TG RTP
Creating a PCM system
DT, ATM, and RTP trunk groups all need to be configured with PCM systems
ADD SPCM
Creating a PCM system between MGWs
When the MGWs managed by one MSCS are interconnected through TDM circuits, no trunk group or trunk route needs to be configured, and only PCM systems between the MGWs need to be configured
ADD INPCM
2
Creating a DT Trunk Group Prerequisites
Context
236
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The adjacent office to which the trunk group points is created.
�
The trunk group No. range is set in the resource management system.
�
The MML Terminal window is opened.
When the Ai interface adopts the TDM bearer, or when IM-MGWs are interconnected through the TDM bearer, DT trunk groups need to be configured. The circuit status in each trunk group is managed by the corresponding trunk management module, so it is required
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
to configure multiple trunk groups to each 2G MSC/PSTN office (4~8 trunk groups are recommended). To implement load sharing, it is required to allocate roughly the same number of Ai interface circuits to each CMP module. Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a DT trunk group by executing command ADD TG DT. The explanation of the main parameters in command ADD TG DT is shown in Table 95. TABLE 95 PARAMETERS IN THE ADD TG DT COMMAND Parameter Name
Parameter Description
Instruction
Trunk group ID
It is a mandatory parameter. It is used to define a trunk group, and needs to be planned in the resource management system in advance
ID of the office where the trunk group belongs
It is a mandatory parameter. It is used to specify the corresponding office of the trunk group. This parameter must be defined by command ADD ADJOFC at first. Then it can be indexed here
MODULE
Module where the trunk group belongs
It is a mandatory parameter. It indicates a service module. Different trunk groups to the same office need to be allocated to different CMP modules
ND
Node No. of the MGW where the trunk group belongs
It is a mandatory parameter. Select the MGW topology node connected with the 2G MSC/PSTN node
User alias
It is an optional parameter, consisting of 0~50 characters. It is used to specifically describe a trunk group to make it easily recognized
TG
OFC
NAME
Confidential and Proprietary Information of ZTE CORPORATION
237
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
Inter-office line signal identification. Options include: �
BSC: BSC Ground Circuit
�
TUP: Interoffice Common Channel Signaling TUP
�
ISUP: Interoffice Common Channel Signaling ISUP
�
DLC1: Interoffice Channel Associated Signaling DL/DC(1)
�
R2: R2 Signaling
�
BICC: BICC Type
�
ANU: ANU Signaling
�
SORMUP: SORMUP Signaling
SIGLINE
It is an optional parameter. It is used to identify the line type of this trunk. Select it according to inter-office signaling. For the Ai interface, select ISUP or TUP
Trunk group types, including the following three types: IN (incoming trunk group): Indicates that the local office processes the incoming calls from the peer-end office.
KIND
OUT (outgoing trunk group): Indicates that the local office only processes the outgoing calls to the peer-end office. BIDIR (Two-way trunk group): Indicates that the local office processes both the incoming calls from the peer-end office and the outgoing calls to the peer-end office
238
Confidential and Proprietary Information of ZTE CORPORATION
It is an optional parameter. If BSC is selected for the inter-office line signal identification, it must be configured to BIDIR
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Instruction
Bearer establishment direction, including the following three types: NODIR: The inter-office bearer is established without direction. BWAY
BACK: The inter-office bearer is established based on the backward mode.
It is an optional parameter. Select NODIR for DT trunk groups
FORWD: The inter-office bearer is established based on the forward mode
Overload control threshold
THD
It is an optional parameter, ranging from 0 to 100, with a default of 100. This parameter takes effect when levels of congestion occur and load control is required
Circuit selecting modes, including: MIN: Every time when the system selects a trunk circuit, it always begins with the circuit with the minimum number. This mode can implement the preferred plan of trunk circuits.
CICSEL
MAX: Every time when the system selects a trunk circuit, it always begins with the circuit with the maximum number. This mode can implement the preferred plan of trunk circuits. CYC: Every time when the system selects a trunk circuit, it always begins with the circuit next to the one previously selected. Suppose the numbers of the trunk circuits in a trunk group in ascending order are “TKC0, TKC1, …. , TKCn”. If TKC0 is selected at the first time, the system will select the trunk circuit in the order of “TKC0®T KC1®…®TKCn®TKC0 ®TKC1®…®TKCn”.
It is an optional parameter. It is used to specify the trunk circuit selecting policy of the system within this trunk group, with a default of CYC. If this No.7 trunk group is a two-way trunk group, it is recommended to set the circuit selecting mode to ODD/EVEN mode to prevent contention when two exchanges select circuits
ODD: Every time when the system selects a
Confidential and Proprietary Information of ZTE CORPORATION
239
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description trunk circuit, it always selects the circuit with an odd number.
Instruction
EVEN: Every time when the system selects a trunk circuit, it always selects the circuit with an even number. IDLE: Every time when the system selects a trunk circuit, it always selects the idlest circuit. BUSY: Every time when the system selects a trunk circuit, it always selects the busiest circuit
DAS
SIPDAS
OPDAS
PREDAS
240
DAS for the called number
It is an optional parameter. It is used to analyze the called number in an incoming call. This parameter must be defined by command ADD DAS at first. Then it can be indexed here
DAS for the domain name of the called number during a SIP outgoing call
It is used get the name of the IMS domain where the called party is located through analyzing the called number during a SIP outgoing call. It is only used for RTP trunk groups
DAS for the calling number
It is used to analyze the calling number in an incoming call. This parameter must be defined by command ADD DAS at first. Then it can be indexed here
DAS for pre-analyzing the called number
It is used to pre-analyze the called number in an incoming call. This parameter must be defined by command ADD PREDAS at first. Then it can be indexed here
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
DDI
OPDDI
MINNAT
MAXNAT
MININT
MAXINT
Parameter Description
Instruction
Incoming called number transform ID
It is the index of the incoming called number transform. This parameter must be defined by command ADD DDI at first. Then it can be indexed here
Incoming calling number transform ID
It is the index of the incoming calling number transform. This parameter must be defined by command ADD DDI at first. Then it can be indexed here
Minimum national number length
It is an optional parameter, which is an integer ranging from 0 to 26, with a default of 0. It is used to specify the minimum digit length of the called number during a national incoming call
Maximum national number length
It is an optional parameter, which is an integer ranging from 0 to 26, with a default of 26. It is used to specify the maximum digit length of the called number during a national incoming call
Minimum international number length
It is an optional parameter, which is an integer ranging from 0 to 26, with a default of 0. It is used to specify the minimum digit length of the called number during an international incoming call
Maximum international number length
It is an optional parameter, which is an integer ranging from 0 to 26, with a default of 26. It is used to specify the maximum digit length of the called number during an international incoming call
Confidential and Proprietary Information of ZTE CORPORATION
241
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
INREG
Incoming register signaling flag, including options: INVALID, MFC, MFP, DTMF, DP and MF
It is an optional parameter, with a default of INVALID
OUTREG
Outgoing register signaling flag, including options: INVALID, MFC, MFP, DTMF, DP and MF
It is an optional parameter, with a default of INVALID
COLEN
The maximum length of CAS calling number end
It is an optional parameter. It ranges from 1 to 32, with a default of 10.
Trunk circuit usage
It is an optional parameter, which is an integer ranging from 1 to 100, with a default of 100. After the trunk circuit usage is configured, when the ratio of busy circuits to all circuits in this trunk group exceeds this value, congestion occurs in this trunk group. After the congestion is relieved, report the trunk congestion times and congestion duration in the performance statistics. This parameter does not take effect when it is configured to 100
DAS for roaming numbers
It is an optional parameter. After this DAS is configured, if the local office serves as a GMSC, this DAS is preferred for the returned roaming numbers. Otherwise, the roaming number DAS configured in the number analysis template is used
BUSYRATE
ROAMDAS
242
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Instruction
Q850CCIDX
Q850 customization index
It is an optional parameter. It ranges from 0 to 65535, with a default of 0.
ID of signaling modification entrance
It is an optional parameter, associated with the inter-office signaling modification entrance. It ranges from 0 to 65535, with a default of 0
SMENTERID
Example: Create a DT trunk group to the 2G MSC office with the following requirements: �
Trunk group ID: 1
�
ID of the office where the trunk group belongs: 28
�
User alias: MSC28
�
No. of the CMP module where the trunk group belongs: 3
�
MGW topology node No.: 101
�
Other parameters: Adopt the default values.
The command is: ADD TG DT:TG=28,OFC=28,MODULE=5,ND=101,NAME ="MSC28",SIGLINE=ISUP,KIND=BIDIR,BWAY=NODIR,TH D=100,CICSEL=ODD,DAS=0,SIPDAS=0,OPDAS=0,PRED AS=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT =0,MAXINT=26,INREG=INVALID,OUTREG=INVALID,COLE N=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX=0,SME NTERID=0,MLPPDM=4294967295,DISINDEX=0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating an ATM Trunk Group Prerequisites
Context
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The trunk group No. range is set in the resource management system.
�
The adjacent MGW office to which the trunk group points is created.
�
The MML Terminal window is opened.
When the ATM bearer is adopted between MGWs, configure ATM trunk groups.
Confidential and Proprietary Information of ZTE CORPORATION
243
ZXWN MSCS Data Configuration Guide(MGCF)
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an ATM trunk group by executing command ADD TG ATM. The explanation of the main parameters in command ADD TG ATM is shown in Table 96. TABLE 96 PARAMETERS IN THE ADD TG ATM COMMAND Parameter Name
TG
OFC
NAME
MODULE
ND
244
Parameter Description
Instruction
Trunk group ID
It is a mandatory parameter. It is used to define an ATM trunk group, and needs to be planned in the resource management system in advance. It is a global unified number
ID of the office where the trunk group belongs
It is a mandatory parameter, ranging from 1 to 256. It is used to specify the corresponding office of the trunk group. This parameter must be defined by command ADD ADJOFC at first. Then it can be indexed here
User alias
It is an optional parameter, consisting of 0~50 characters. It is used to specifically describe a trunk group to make it easily recognized
Module where the trunk group belongs
It is a mandatory parameter, which is an integer, ranging from 1 to 127. It is used to specify the SMP module of processing traffic on this trunk group
Node No. of the MGW where the trunk group belongs
It is a mandatory parameter, which is an integer, ranging from 1~2048. It is used to specify the topology node No. of the MGW providing bearer, which is controlled by the local MGCF
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Instruction
SIGLINE
Inter-office line signal identification, including BICC (BICC signaling)
It is an optional parameter. It is used to identify the line type of this trunk, with a default of BICC
Trunk group types, including the following three types: IN (incoming trunk group): Indicates that the local office processes the incoming calls from the peer-end office.
KIND
OUT (outgoing trunk group): Indicates that the local office only processes the outgoing calls to the peer-end office. BIDIR (Two-way trunk group): Indicates that the local office processes both the incoming calls from the peer-end office and the outgoing calls to the peer-end office
It is an optional parameter. It is used to specify the call connection direction in this trunk group in the local office, with a default of BIDIR. It should be negotiated with the peer-end office
Bearer establishment direction, including the following three types: NODIR (No direction): The inter-office bearer is established without direction. BWAY
BACK: The inter-office bearer is established based on the backward mode.
It is an optional parameter. It is used to specify the inter-office bearer establishment direction, with a default of NODIR
FORWD: The inter-office bearer is established based on the forward mode
THD
Overload control threshold
It is an optional parameter, ranging from 0 to 100, with a default of 100. This parameter takes effect when levels of congestion occur and load control is required
Confidential and Proprietary Information of ZTE CORPORATION
245
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
Circuit selecting modes, including: MIN: Every time when the system selects a trunk circuit, it always begins with the circuit with the minimum number. This mode can implement the preferred plan of trunk circuits. MAX: Every time when the system selects a trunk circuit, it always begins with the circuit with the maximum number. This mode can implement the preferred plan of trunk circuits.
CICSEL
CYC: Every time when the system selects a trunk circuit, it always begins with the circuit next to the one previously selected. Suppose the numbers of the trunk circuits in a trunk group in ascending order are “TKC0, TKC1, …. , TKCn”. If TKC0 is selected at the first time, the system will select the trunk circuit in the order of “TKC0®TKC 1®…®TKCn®TKC0®TK C1®…®TKCn”. ODD: Every time when the system selects a trunk circuit, it always selects the circuit with an odd number. EVEN: Every time when the system selects a trunk circuit, it always selects the circuit with an even number. IDLE: Every time when the system selects a trunk circuit, it always selects the idlest circuit. BUSY: Every time when the system selects a trunk circuit, it always selects the busiest circuit
246
Confidential and Proprietary Information of ZTE CORPORATION
It is an optional parameter. It is used to specify the trunk circuit selecting policy of the system within this trunk group, with a default of CYC. If this trunk group is a two-way trunk group, it is recommended to set the circuit selecting mode to ODD/EVEN mode to prevent contention when two exchanges select circuits
Chapter 7 Basic Service Data Configuration
Parameter Name
DAS
SIPDAS
OPDAS
PREDAS
DDI
OPDDI
MINNAT
Parameter Description
Instruction
DAS for the called number
It is an optional parameter. It is used to analyze the called number in an incoming call. This parameter must be defined by command ADD DAS at first. Then it can be indexed here
DAS for the domain name of the called number during SIP outgoing calls
It is used get the name of the IMS domain where the called party is located through analyzing the called number during a SIP outgoing call. It is only used for RTP trunk groups
DAS for the calling number
It is used to analyze the calling number in an incoming call. This parameter must be defined by command ADD DAS at first. Then it can be indexed here
DAS for pre-analyzing the called number
It is used to pre-analyze the called number in an incoming call. This parameter must be defined by command ADD PREDAS at first. Then it can be indexed here
Incoming called number transform ID
It is the index of the incoming called number transform. This parameter must be defined by command ADD DDI at first. Then it can be indexed here
Incoming calling number transform ID
It is the index of the incoming calling number transform. This parameter must be defined by command ADD DDI at first. Then it can be indexed here
Minimum national number length
It is an optional parameter, which is an integer ranging from 0 to 26, with a default of 0. It is used to specify the minimum digit length of the called number during a national incoming call
Confidential and Proprietary Information of ZTE CORPORATION
247
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
MAXNAT
MININT
MAXINT
INREG
Parameter Description
Instruction
Maximum national number length
It is an optional parameter, which is an integer ranging from 0 to 26, with a default of 26. It is used to specify the maximum digit length of the called number during a national incoming call
Minimum international number length
It is an optional parameter, which is an integer ranging from 0 to 26, with a default of 0. It is used to specify the minimum digit length of the called number during an international incoming call
Maximum international number length
It is an optional parameter, which is an integer ranging from 0 to 26, with a default of 26. It is used to specify the maximum digit length of the called number during an international incoming call
Incoming register signaling flag. Options include: INVALID
OUTREG
Outgoing register signaling flag. Options include: INVALID
COLEN
BUSYRATE
248
It is an optional parameter, with a default value of INVALID
It is an optional parameter, with a default value of INVALID
The maximum length of CAS calling number end
It is an optional parameter. It ranges from 1 to 32, with a default of 10.
Trunk circuit usage
It is an optional parameter, which is an integer ranging from 1 to 100, with a default of 100. After the trunk circuit usage is configured, when the ratio of busy circuits to all circuits in this trunk group exceeds this value, congestion occurs in this trunk group. After the congestion is relieved, report the trunk congestion times and congestion duration in the performance statistics. This
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Instruction parameter does not take effect when it is configured to 100
ROAMDAS
DAS for roaming numbers
It is an optional parameter. After this DAS is configured, if the local office serves as a GMSC, this DAS is preferred for the returned roaming numbers. Otherwise, the roaming number DAS configured in the number analysis template is used
Q850CCIDX
Q850 customization index
It is an optional parameter. It ranges from 0 to 65535, with a default of 0.
ID of signaling modification entrance
IIt is an optional parameter, associated with the inter-office signaling modification entrance. It ranges from 0 to 65535, with a default of 0
SMENTERID
Example: Create an ATM trunk group with the following requirements. �
Trunk group ID: 1
�
ID of the office where the trunk group belongs: 102
�
User alias: MGW102
�
No. of the module processing the trunk group: 3
�
MGW topology node No.: 101
�
Inter-office line signal identification: BICC
�
Other parameters: Adopt the default values.
The command is: ADD TG ATM:TG=102,OFC=102,MODULE=5,ND=101,NA ME="MGW102",SIGLINE=BICC,KIND=BIDIR,BWAY=NODI R,THD=100,CICSEL=ODD,DAS=0,SIPDAS=0,OPDAS=0,P REDAS=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,M ININT=0,MAXINT=26,INREG=INVALID,OUTREG=INVALI D,COLEN=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX =0,SMENTERID=0,MLPPDM=4294967295,DISINDEX=0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
249
ZXWN MSCS Data Configuration Guide(MGCF)
Creating RTP Trunk Group Prerequisites
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The adjacent IM-MGW office to which the trunk group points is created.
�
The trunk group No. range is set in the resource management system.
�
The MML Terminal window is opened.
Context
When the IP bearer is adopted between MGWs, configure RTP trunk groups, which are BICC trunk groups.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Creating a RTP trunk group by executing command ADD TG RTP. The explanation of the main parameters in command ADD TG RTP is shown in Table 97. TABLE 97 PARAMETERS IN THE ADD TG RTP COMMAND Parameter Name
TG
OFC
NAME
250
Parameter Description
Instruction
Trunk group ID
It is a mandatory parameter. It is used to define a trunk group. This trunk group can be BICC trunk group or SIP trunk group. It is a global unified number
ID of the office where the trunk group belongs
It is a mandatory parameter. It is used to specify the corresponding office of the trunk group. This parameter must be defined by command ADD ADJOFC at first. Then it can be indexed here
User alias
It is an optional parameter, consisting of 0~50 characters. It is used to specifically describe a trunk group to make it easily recognized
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
MODULE
Parameter Description
Instruction
Module where the trunk group belongs
It is a mandatory parameter, which is an integer, ranging from 1 to 127. It is used to specify the SMP module of processing traffic on this trunk group
Inter-office line signal identification, including SIGLINE
�
BICC (BICC signaling)
�
SIP (SIP signaling)
It is an optional parameter. Select SIP for the MGCF.
Trunk group types, including the following three types: IN (incoming trunk group): Indicates that the local office processes the incoming calls from the peer-end office.
KIND
OUT (outgoing trunk group): Indicates that the local office only processes the outgoing calls to the peer-end office.
It is an optional parameter. BIDIR is selected by default. It should be negotiated with the peer-end office.
BIDIR (Two-way trunk group): Indicates that the local office processes both the incoming calls from the peer-end office and the outgoing calls to the peer-end office Bearer establishment direction, including the following three types:
BWAY
NODIR (No direction): The inter-office bearer is established without direction. BACK: The inter-office bearer is established based on the backward mode.
It is an optional parameter. For RTP trunk groups, it is set according to the network plan of operators
FORWD: The inter-office bearer is established based on the forward mode
Confidential and Proprietary Information of ZTE CORPORATION
251
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
THD
Threshold for overload control
It is an optional parameter, ranging from 0 to 100, with a default of 100
Circuit selecting modes, including: MIN: Every time when the system selects a trunk circuit, it always begins with the circuit with the minimum number. This mode can implement the preferred plan of trunk circuits. MAX: Every time when the system selects a trunk circuit, it always begins with the circuit with the maximum number. This mode can implement the preferred plan of trunk circuits.
CICSEL
CYC: Every time when the system selects a trunk circuit, it always begins with the circuit next to the one previously selected. Suppose the numbers of the trunk circuits in a trunk group in ascending order are “TKC0, TKC1, …. , TKCn”. If TKC0 is selected at the first time, the system will select the trunk circuit in the order of “TKC0 ®TKC1®…®TKCn®TK C0®TKC1®…®TKCn”. ODD: Every time when the system selects a trunk circuit, it always selects the circuit with an odd number. EVEN: Every time when the system selects a trunk circuit, it always selects the circuit with an even number. IDLE: Every time when the system selects a trunk circuit, it always selects the idlest circuit.
252
Confidential and Proprietary Information of ZTE CORPORATION
It is an optional parameter, with a default of CYC. In general, the signaling point with big code prefers the circuit with an even number, while the one with small code prefers the circuit with an odd number. It should be negotiated with the peer-end office
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Instruction
BUSY: Every time when the system selects a trunk circuit, it always selects the busiest circuit
DAS for the called number
DAS
SIPDAS
DAS for the domain name of the called number during SIP outgoing calls
It is an optional parameter, which is an integer ranging from 0 to 4096, with a default of 0. When the local office has the GMSC function, this DAS is used to analyze the called number from other offices. When the called number is from the BSC office, this DAS is meaningless, and does not need to be configured It is used get the name of the IMS domain where the called party is located through analyzing the called number during a SIP outgoing call. If the outgoing SIP trunk group is configured with this DAS, the “invite” message during a SIP outgoing call can only contain SIP URL mode. If the outgoing SIP trunk group is not configured with this DAS, configure the URLOPT in the SIP adjacent office configuration to decide whether the outgoing call uses TEL or SIP URL mode. After this DAS is used on this trunk group, all outgoing calls on this trunk group will get the corresponding domain name according to the called number, and then form a SIP URL
OPDAS
DAS for the calling number
It is an optional parameter, which is an integer ranging from 0 to 4096, with a default of 0. When the local office has the GMSC function, this DAS is used to analyze the calling number from other offices. When the calling number is from the BSC office, this DAS is meaningless, and does not need to be configured
Confidential and Proprietary Information of ZTE CORPORATION
253
ZXWN MSCS Data Configuration Guide(MGCF)
Example: Create a RTP trunk group with the following requirements. �
Trunk group ID: 1
�
ID of the office where the trunk group belongs: 102
�
User alias: IM-MGW102
�
No. of the module processing the trunk group: 3
�
Inter-office line signal identification: BICC
�
Other parameters: Adopt the default values.
The command is: ADD TG RTP:TG=1,OFC=102,MODULE=5,NAME="IM-M GW102",SIGLINE=BICC,KIND=BIDIR,BWAY=NODIR,THD =100,CICSEL=CYC,DAS=0,SIPDAS=0,OPDAS=0,PREDA S=0,DDI=0,OPDDI=0,MINNAT=0,MAXNAT=26,MININT =0,MAXINT=26,INREG=INVALID,OUTREG=INVALID,COLE N=10,BUSYRATE=100,ROAMDAS=0,Q850CCIDX=0,SME NTERID=0,MLPPDM=4294967295,SIPRUTS=0,DISINDEX =0; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating PCM Prerequisites
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The DT, ATM, or RTP trunk group is configured.
�
The MML Terminal window is opened.
Context
The PCM system management data associate the resources on the MGW with the signaling on the MGCF.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create PCM by executing command ADD SPCM. The explanation of the main parameters in command ADD SPCM is shown in Table 98.
254
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
TABLE 98 PARAMETERS IN THE ADD SPCM COMMAND Parameter Name
TG
Parameter Description
Instruction
No. of the trunk group where the PCM system belongs
It is a mandatory parameter, which is an integer, ranging from 1~1000. Select the trunk group where this PCM system belongs from the list of configured trunk groups. It is used to specify the trunk group invoking this PCM system. This parameter is associated with the trunk group No. in command ADD TG ATM, ADD TG DT, ADD TG PRA, and ADD TG RTP It is a mandatory parameter. It is a parameter for interconnection with the peer-end office. If the configured PCM system belongs to the inter-office trunk, the PCM system No. of the same circuit between two offices must be the same.
PCM
PCM system No.
When the inter-office line identification of a trunk group is TUP or ISUP, the PCM system No. ranges from 0 to 127. When the inter-office line identification of a trunk group is BICC, the PCM system No. ranges from 0 to 5999. When the inter-office line identification of a trunk group is BSC or ANU, the PCM system No. ranges from 0 to 2047
Number of created PCM systems
NUM
PCM No. in the MGW
MGWPCM
The corresponding trunk group can invoke the PCM resources between the start PCM No. in the MGW and the end PCM No.
It is an optional parameter. If PCM systems belong to a DT trunk group, this parameter needs not be configured. If PCM systems belong to a RTP or ATM trunk group, select the number the created PCM systems It is an optional parameter. If the PCM system belongs to a RTP or ATM trunk group, this parameter needs not be configured. If the PCM system belongs to a DT trunk group, select the corresponding PCM No. in the MGW
Confidential and Proprietary Information of ZTE CORPORATION
255
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
NAME
E1
DDF
Parameter Description
Instruction
User alias
It is an optional parameter, consisting of 1~50 characters. It is used to specifically describe the PCM system configuration to make it easily recognized
E1 identification
It is an optional parameter, consisting of 1~50 characters. For DT trunk groups, describes the E1 with any characters, which can be set to “DTB/SDTB unit No.-E1 No.”
Digital Distribution Frame (DDF) location description
It is an optional parameter, consisting of 1~50 characters. For DT trunk groups, the DDF location description can be set to “Frame No.-Row No.-Port No.”
Example: Create PCM to the 2G MSC office with the following requirements: �
No. of the trunk group where the PCM system belongs: 28
�
PCM No.: 1
�
PCM No. in the MGW: 1-1
�
User alias: 2G MSC1-1.
The command is: ADD SPCM:TG=28,PCM=0,MGWPCM="1"-"1",INFO=6553 5,NAME="2G MSC1-1"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Configure a PCM System between MGWs Prerequisites
Context
256
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The bearer mode between the MGWs is configured in the topology configuration.
�
The MML Terminal window is opened.
When the MGWs managed by one MGCF are interconnected through TDM circuits, it is required to configure the PCM systems between the MGWs. Since the MGWs are interconnected within
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
the MGCF, it is required to add the bearer mode between the MGWs in the topology configuration, but no trunk group, trunk route or other parameters need to be configured. Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a PCM system between MGWs by executing command ADD INPCM. The explanation of the main parameters in command ADD INPCM is shown in Table 99. TABLE 99 PARAMETERS IN THE ADD INPCM COMMAND Parameter Name
Parameter Description
Instruction
ND1
MGW1 node No.
It is a mandatory parameter. Enter the topology node No. of MGW1
ND2
MGW2 node No.
It is a mandatory parameter. Enter the topology node No. of MGW2
PCM
PCM system No.
It is a mandatory parameter. Enter the PCM system No. in the MSCS
ND1PCM
PCM No. in MGW1
It is a mandatory parameter. Enter the PCM system No. in MGW1
ND2PCM
PCM No. in MGW2
It is a mandatory parameter. Enter the PCM system No. in MGW2
MODULE
Management module No.
It is a mandatory parameter. Select the No. of the CMP module of managing this PCM system
PCMTYPE
PCM type
It is an optional parameter, with a default of E1
NAME
User alias
It is an optional parameter, which is in the format of “Adjacent office MGW1 user alias-Adjacent office MGW2 user alias-PCM system No.”
ND1E1
E1 identification
It is an optional parameter, which can be set to “DTB/SDTB unit No.-E1 No.”
ND1DDF
DDF location description
It is an optional parameter, which can be set to “Frame No.-Row No.-Port No.”
Confidential and Proprietary Information of ZTE CORPORATION
257
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
ND2E1
MGW2 E1 ID
It is an optional parameter, which can be set to “DTB/SDTB unit No.-E1 No.”
ND2DDF
Description of MGW2 DDF location
It is an optional parameter, which can be set to “Frame No.-Row No.-Port No.”
Example: Add a PCM system between MGWs with the following requirements. �
PCM system No.: 0
�
PCM No. in MGW1 and MGW2: 1
�
Management module No.: 3
�
User alias: MGW1-MGW2.
The command is: ADD INPCM:ND1=101,ND2=102,PCM=0,ND1PCM=1,ND2 PCM=1,MODULE=3,PCMTYPE=E1,NAME="MGW1-MGW2"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Route Data Configuration Overview Description
Outgoing route chains are directly referred to in number analysis results. Each outgoing route chain contains at most 4 outgoing route groups (in active/standby relationship), and each outgoing route group contains at most 12 outgoing routes (in load sharing relationship). The outgoing route has a one-to-one correspondence with the trunk group.
Data Configuration
The related operations of the routing data configuration are as follows.
258
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Steps
Operations
Instructions
Commands
1
Creating an outgoing route
Each trunk group corresponds to an outgoing route.
ADD RT
Creating an outgoing route set
Each route belongs to a route group, and each route group contains at most 12 routes.
ADD RTS
Creating an outgoing route chain
Each outgoing route group belongs to an outgoing route chain, and each route chain contains at most 4 route groups.
ADD CHAIN
2
3
Creating a Route Prerequisites
Context Steps
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The outgoing route No. range is set in the resource management system.
�
The MML Terminal window is opened.
Each trunk group corresponds to an outgoing route. 1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create route by executing command ADD RT. The explanation of the main parameters in command ADD RT is shown in Table 100. TABLE 100 PARAMETERS IN THE ADD RT COMMAND Parameter Name
RT
Parameter Description
Instruction
Route No.
It is a mandatory parameter, which is an integer, ranging from 1~2000. It exclusively identifies a route. To facilitate management, the route No. is configured to be consistent with the trunk group No.
Confidential and Proprietary Information of ZTE CORPORATION
259
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
TG
Trunk group No.
It is a mandatory parameter, corresponding to the trunk group No. in the trunk group configuration
Called number transform index during outgoing calls
It is an optional parameter, which is an integer ranging from 0 to 2048, with a default of 0. The called number is transformed according to this index during outgoing calls. This index has no influence on the incoming calls through this trunk
OPDDI
Calling number transform index during outgoing calls
It is an optional parameter, which is an integer ranging from 0 to 2048, with a default of 0. The calling number is transformed according to this index during outgoing calls. This index has no influence on the incoming calls through this trunk
DLPFX
Whether to delete the prefix of the calling number during outgoing calls, including NO and YES
It is an optional parameter, with a default of NO. If YES is selected, the prefix of the calling number (such as 0/00) will be deleted during outgoing calls
NAME
User alias
It is an optional parameter, consisting of 0~50 characters.
DDI
Example: Create an outgoing route with the following requirements. �
Route No.: 28
�
Trunk group No.: 28
�
User alias: Rout28.
The command is: ADD RT:RT=28,TG=28,DDI=0,OPDDI=0,DLPFX=NO,NAM E="ROUT28",HOPCNT=0,RERTS=0,CLISETIDX=65535; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating a Route Set Prerequisites
260
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The outgoing route No. is created.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
� Context
The MML Terminal window is opened.
Each route belongs to a route group, and each route group contains at most 12 routes.
Note: Each outgoing route group can be configured with at most 12 outgoing routes, performing load sharing based on the poll or percentage mode. One outgoing route can be allocated to different adjacent offices (such as TMSC1 and TMSC2), thus to implement traffic load sharing to different offices. Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create a route set by executing command ADD RTS. The explanation of the main parameters in command ADD RTS is shown in Table 101. TABLE 101 PARAMETERS IN THE ADD RTS COMMAND Parameter Name
RTS
NAME
Parameter Description
Instruction
Route group No.
It is a mandatory parameter, which is an integer, ranging from 1~3000. It is used to identify a route group
User alias
It is an optional parameter, consisting of 0~50 characters. It is used to specifically describe a route group to make it easily recognized t is an optional parameter. It is in the format of “No.-Route No.-Load sharing proportion. When the percentage is set to 0, the poll mode is adopted. SEQ: No., which is the location of the route in the route group.
RTPER
Route No. and load sharing proportion list
RTVAL: Route No., associated with the route group. This parameter must be defined by command ADD RT at first. Then it can be indexed here. PERVAL: Load sharing proportion of each route in the route group. If it is set to 0 for all routes by default, the load is evenly allocated to each route
Confidential and Proprietary Information of ZTE CORPORATION
261
ZXWN MSCS Data Configuration Guide(MGCF)
Example: Create an route set with the following requirements. �
Route group No.: 28
�
User alias: Rout28
�
Locaiton: 1
�
Route No.: 28
�
Percentage: 0.
The command is: ADD RTS:RTS=28,NAME="ROUT28",RTPER="1"-"28"-"0"; END OF STEPS Result
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Creating an Outgoing Route Chain Prerequisites
Before the operation, it is required to confirm: �
The exchange ID to be configured is given.
�
The outgoing route chain No. range is set in the resource management system.
�
The MML Terminal window is opened.
Context
Each outgoing route group belongs to an outgoing route chain, and each route chain contains at most 4 route groups.
Steps
1. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the exchange to be configured. Example: Select the MGCF exchange with ID as 11 from the system tree. SET:NEID=11; 2. Create an outgoing route chain by executing command ADD CHAIN. The explanation of the main parameters in command ADD CHAIN is shown in Table 102. TABLE 102 PARAMETERS IN THE ADD CHAIN COMMAND Parameter Name
CHAIN
262
Parameter Description
Instruction
Route chain No.
It is a mandatory parameter, which is an integer, ranging from 1 to 3000. It is used to define an outgoing route chain. When it is configured in the number analysis configuration, it
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 7 Basic Service Data Configuration
Parameter Name
Parameter Description
Instruction is associated to the route chain configured here
NAME
User alias
It is an optional parameter, consisting of 0~50 characters. It is used to specifically describe a route chain to make it easily recognized
Whether the preference policy is supported in the MGW, including:
PRINODE
NO: When 2B occurs, the calls in the same MGW are not preferred, and routing is performed according to other routing policies of the system instead.
It is an optional parameter, with a default of YES. It is a policy for selecting the rouging route
YES: When 2B occurs, the calls in the same MGW are preferred
RTS1
No. of route group 1, used to set the route group with the highest priority in a route chain during routing. One route chain can be configured with at most 4 route groups
RTS2
No. of route group 2, used to set the route group with the level-2 priority in a route chain during routing. One route chain can be configured with at most 4 route groups
RTS3
No. of route group 3, used to set the route group with the level-3 priority in a route chain during routing. One route chain can be configured with at most 4 route groups
RTS4
No. of route group 4, used to set the route group with the level-4 priority in a route chain during routing. One route chain can be configured with at most 4 route groups
It is an optional parameter. Select route groups according to the priority order. Select route group 1 fist. Only when the circuits in route group 1 are used up or all the circuits are unavailable, the circuits in route group 2 can be selected. Only when the circuits in route group 2 are used up or all the circuits are unavailable, the circuits in route group 3 can be selected
Confidential and Proprietary Information of ZTE CORPORATION
263
ZXWN MSCS Data Configuration Guide(MGCF)
Parameter Name
Parameter Description
Instruction
RTPLC
Route Selection Policy Number
It is an optional parameter. Select the route selection policy number configured in ADD RTPLC command
DAS for the called number
It is an optional parameter. It is used to analyze the called number in an incoming call. This parameter must be defined by command ADD DAS at first. Then it can be indexed here. It needs to be set only when “Inter-MGW route chain” is set in the called number analysis. The default value is 0
TPDAS
Example: Create an outgoing route chain with the following requirements. �
Route chain No.: 28
�
User alias: RLink28
�
No. of Route group 1: 28
�
Other parameters: Adopt the default values.
The command is: ADD CHAIN:CHAIN=28,NAME="RLink28",PRINODE=YE S,RTS1=28,RTS2=0,RTS3=0,RTS4=0,RTPLC=0,TPDAS =0; END OF STEPS Result
264
After the command is executed, the SUCCESS result is shown in the Execute Result column of the History Command pane.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter
8
Configuration Instance Table of Contents Overview........................................................................ 265 Local Office Data Configuration.......................................... 266 Resource Attribute Configuration ....................................... 270 Adjacent IM-MGW Office Interconnection Data Configuration ............................................................................... 271 Adjacent SCSCF Office Interconnection Data Configuration ............................................................................... 274 Basic Service Data Configuration ....................................... 276 Data Synchronization ....................................................... 277 MGCF-IM-MGW Interconnection Debugging Procedure .......... 277
Overview Introduction
This chapter introduces the local office configuration procedure and office interconnection data configuration procedure by taking the example of creating a MGCF pilot office. Figure 61 shows the networking diagram. FIGURE 61 NETWORKING DIAGRAM
Note: Real lines indicate bearer connections, while dashed lines indicate signaling connections The MGCF is directly connected with the CSCF/BGCF/IM-MGW through the IP bearer. The MGCF and IM-MGW can be interconnected with the R4 CS through different signaling points.
Confidential and Proprietary Information of ZTE CORPORATION
265
ZXWN MSCS Data Configuration Guide(MGCF)
According to the networking condition shown in Figure 61, the operator is required to provide the negotiation data listed in Table 103 and Table 104. TABLE 103 NEGOTIATION DATA INSTANCE NE
Parameter
Attributes
Office ID
11
Signaling point type of the local office
24-bit
SPC of the local office
3.11.1
Call prefix of the test number
8613902099
Office ID
31
Signaling point type of the local office
24-bit
SPC of the local office
3.31.1
Office ID
12
Signaling point type of the local office
24-bit
SPC of the local office
3.12.1
MGCF
IM-MGW
CSCF
TABLE 104 SIGTRAN IP ADDRESS INSTANCE OF THE MC INTERFACE Parameter
Attributes
IP of the loop-back interface at the MGCF side
192.168.11.11/32
IP of the SIPI interface at the MGCF side
192.168.1.11/16
IP of the loop-back interface at the IM-MGW side
192.168.31.31/32
IP of the SIPI interface at the IM-MGW side
192.168.1.31/16
Local Office Data Configuration The procedure of the local office data configuration is as follows:
266
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 8 Configuration Instance
Steps
Operations
1
Local exchange configuration
2
Physical configuration
3
Capacity configuration
4
Version loading
5
Office data configuration
Local Exchange Configuration Data Planning
Table 105 lists the parameters in the local exchange configuration. TABLE 105 DATA PLANNING OF THE LOCAL EXCHANGE CONFIGURATION
Command
Configuration Parameters
Configuration Description
Office ID
11
Exchange type
MSCS
User alias
MGCF11
ADD NE:ID=11,TYPE=MSCS,MESUBTYPE=NONE,NAME="MG CF11",VENDOR="ZTE",STATE=0;
Physical Configuration Data Planning
When the MSCS office uses only one shelf, the board layout of the BCTC shelf is shown in Figure 62. Table 106 lists the data planning of the physical configuration. FIGURE 62 BOARD LAYOUT OF THE BCTC SHELF
Confidential and Proprietary Information of ZTE CORPORATION
267
ZXWN MSCS Data Configuration Guide(MGCF)
TABLE 106 DATA PLANNING OF THE PHYSICAL CONFIGURATION
Command
Board
Type
CPU
Slot No.
Unit No.
OMP
-
CENTRINO
Slots 11 and 12
-
Module No.
Backup Mode
No. 1 OMP
1+1 activ e/standby mode
No.2 RPU
UIMC
UIM2_GC S_755
-
Slots 9 and 10
921
-
1+1 activ e/standby mode
SMP
-
CENTRINO
Slots 7 and 8
-
3, 4
1+1 activ e/standby mode
SIPI
SIPI_NC
-
Slot 3
321
-
No backup
SPB
SPB2_826 0_8260C4
-
Slot 5
521
-
No backup
1. Select an exchange. SET:NEID=11; 2. Create a shelf. ADD SHELF:RACK=1,SHELF=2,TYPE=BCTC; 3. Create UIM units ADD UNIT:LOC="1"-"2"-"9",MODULE=1,UNIT=921,TYPE =UIM2_GCS_755,BKMODE=ONEPLUSONE,CLK1=16383,CL K2=16383; 4. Create modules. ADD MODULE:LOC="1"-"2"-"7",MODULE="3",FUNC1="S MP"&"MSCBASECMP"&"SIP",CPUTYPE=CENTRINO,BKMODE =NO; 5. Create an SPB unit. ADD UNIT:LOC="1"-"2"-"5",MODULE=1,UNIT=521,TYPE =SPB2_8260_8260C4,BKMODE=NO,CLK1=16383,CLK2=16 383; 6. Create an SIPI unit. ADD UNIT:LOC="1"-"2"-"3",MODULE=1,UNIT=321,TYPE =SIPI_NC,BKMODE=NO,CLK1=16383,CLK2=16383;
Capacity Configuration Data Planning
268
Table 107 lists the parameters in the capacity and load sharing configuration.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 8 Configuration Instance
TABLE 107 DATA PLANNING OF THE CAPACITY CONFIGURATION
Command
Configuration Parameters
Configuration Description
Office capacity
Adopts the default value
Service data area
The number of destination codes is 4096
1. Configure the MSCS office capacity. SET MSCSCAPACITY; For the subsequent steps, refer to Configuring the MGCF Office Capacity. 2. Configure the service data area. SET DATASIZE:CMODEL=AMONLY,BCBMNUM=10,DSTCD NUM=4096;
Version Loading After the physical configuration and capacity configuration are completed, it is required to load the board version in order to let the foreground board run normally. For the steps of loading the version files, refer to Overview.
Office Data Configuration Data Planning
Table 108 lists the parameters in the office data configuration. TABLE 108 DATA PLANNING OF THE OFFICE DATA CONFIGURATION
Command
Configuration Parameters
Configuration Description
Network type
1
Area code
25
Signaling point type of the local office
24-bit
SPC of the local office
3.11.1
Exchange type
Local exchange/toll exchange/MGCF exchange
Signaling point type
STEP
1. Create the signaling point of the local office. ADD OPC:NET=1,NAME="NET1",SPCFMT=TRIPLE_DEC,O PC24="3.11.1",APPTYPE="BICC"&"ISUP"&"SCCP"&"TUP",R
Confidential and Proprietary Information of ZTE CORPORATION
269
ZXWN MSCS Data Configuration Guide(MGCF)
C="25",PREFIX="0",NETAPP=0,INFO=NONETAPP,DMIDX =0; 2. Create the local exchange attributes. ADD LOFC:OFCTYPE="LOCAL"&"DOMTOLL"&"MGCF",NET =1,SEQ=0,TCODE="1234",SPTYPE=STEP,LANG=DEFAUL T,RESTART=YES,RSTTIME=10000,T19=68,T20=60,T21 =64; 3. Set SIP module capacity SET SIPCAPA:SIPSOCKET=16,SIPTR=16,SIPTU=128,SIP TUMSG=3000; 4. Create realm ADD REALM:ID=1,REALM="zte.com"; 5. Create host ADD HOST:ID=1,HOST="host1.zte.com",IPV4="11.11.11. 1";
Resource Attribute Configuration Resource Planning
The instance of resource attribute configuration is shown in Table 109. TABLE 109 RESOURCE PLANNING INSTANCE Configuration Items
Resource Types
Key Fields
Minimum
Maximum
Office data configuration
Adjacent office
Adjacent office ID
1
20
Node Topology Config
Topology node ID.
1
20
Voice Codec Template
Template ID
1
10
SCTP
SCTP ID
1
20
ASP
ASP ID
1
20
AS
AS ID
1
20
M3UA static route
M3UA static route ID
1
5
Signaling linkset
Link set No.
1
20
Topology configuration
Protocol configuration
270
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 8 Configuration Instance
Configuration Items
Resource Types
Key Fields
Minimum
Maximum
Signaling route
Signaling route No.
1
20
Number Analysis Selector
Number Analysis Selector
1
300
Number Analysis Entrance
Number Analysis Entrance
1
50
Adjacent IM-MGW Office Interconnection Data Configuration Data Planning
Table 110 lists the parameters in the adjacent-MGW-office interconnection data configuration. TABLE 110 PARAMETERS IN THE ADJACENT MGW OFFICE INTERCONNECTION DATA CONFIGURATION Configuration Parameters
Configuration Description
IP of the loop-back interface at the MGCF side
192.168.11.11/32
IP of the SIPI interface at the MGCF side
192.168.1.11/16
IP of the loop-back interface at the IM-MGW side
192.168.31.31/32
IP of the SIPI interface at the IM-MGW side
192.168.1.31/16
Adjacent IM-MGW office ID
101
Adjacent IM-MGW office type
MGW
Association mode
AM_SURE (Associated)
IM-MGW topology node No.
3
Signaling point type of the IM-MGW
14-bit
SPC of the IM-MGW
1.31.1
Tone coding/decoding template No.
The coding/decoding template No. is 1. The ETSI coding/decoding type is ETSI_UMTS_AMR_2.
Confidential and Proprietary Information of ZTE CORPORATION
271
ZXWN MSCS Data Configuration Guide(MGCF)
Configuration Parameters
Configuration Description The supported coding/decoding rates are “5.90K” and “6.70K”. The activated coding/decoding rates are “5.90K” and “6.70K”
Command
SCTP ID
1
ASP ID
1
AS ID
1
M3UA static route ID
1
SIO-locating-AS ID
1
TID analyzer index
1
TID command template No.
It is 1 by default
1. Create the loop-back interface. INTERFACE LOOPBACK:PORT=1; ADD IP ADDRESS:ADDRESS="192.168.11.11",MASK="255 .255.255.255",BROADCASTIP="255.255.255.255"; SAVE ONLINEDATA; EXIT; 2. Create the SIPI interface address. INTERFACE:SUBSYSTEM=0,MODULE=1,UNIT=321,SUNI T=1,PORT=1; ADD IP ADDRESS:ADDRESS="192.168.1.11",MASK="255. 255.255.248",BROADCASTIP="255.255.255.255"; SAVE ONLINEDATA; EXIT; 3. Create an adjacent IM-MGW office. ADD ADJOFC:ID=101,NAME="IM-MGW1",NET=2,OFCTYP E=MGW,SPCFMT=TRIPLE_DEC,SPCTYPE=14,DPC="1.31.1 ",RC="25",ASSOTYPE=AM_SURE,SPTYPE=SEP,SSF=NATIO NAL STANDBY,SUBPROTTYPE=DEFAULT,TEST=YES,BAND FLAG=YES,PRTCTYPE=CHINA,CLST=65535,INFO="CIC_P CM",RELATEDOFC1=0; 4. Create a tone coding/decoding template. ADD CODECTPL:ID=1,GRPID=GRPID1,VALFG=YES,OID =OID_ETSI,ETYPE=ETSI_UMTS_AMR_2,ACTRATE="Rate59 0"&"Rate670",SUPRATE="Rate590"&"Rate670",OM=YES; 5. Create a IM-MGW topology node. ADD TOPO:ID=101,OFCID=101,NAME="IM-MGW101",CO DECID=1,ETYPE=R4GW,PROTTYPE=H248,IPVER=IPV4,A TTR="BNCAAL2"&"BNCIPRTP"&"BNCTDM",UPVER="V2",ATT R2=NOTUNL,TRFMOD=MCINTF,UPERRCTRL=YES,DTMFTC =NO,MGWCON=SMGWCON,AUTOFAX=YES,OOBTC=NO,B CUID=0,SENDCAP=NO,G711TRAN=NO,BICCDTMF=TRAN
272
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 8 Configuration Instance
SPARENT,IPBCP2833=BYMGW,BICCDTMPPER=0,AOIPPR O=PRIVATE; 6. Create the SCTP. ADD SCTPCONN:MODULE=3,OFCID=101,PROT=M3UA,R OLE=CLT,LOCADDR="IPv4"-"0"-"192.168.1.11",LOCPORT =2001,REMADDR="IPv4"-"0"-"192.168.1.31",REMPORT=2 001,NAME="IM-MGW101-1",ID=1,INSTRM=16,OUTSTRM =16,MAXRTRY=5,MAXRTO=500,MINRTO=50,INITRTO=1 00,HB=500,FIXNH=NO,SCTPMAXRTRYNUM=10,DELAYA CK=20,MAXBURST=4,PRIMARYPATH=REMIP1,PMTU=0,B REAKTIME=3,PDTHRESH=0,MINCWND=0,PLTIMER=1 0,MPPLTHRD=2,DPLEN=MTU,CB=200; 7. Create the ASP. ADD ASP:ASSOCID=1,NAME="IM-MGW101-1",ID=1,ISLO OP=NO,ISLOCK=NO; 8. Create the AS. ADD AS:PROT=M3UA,ASPID="1",NAME="H248",ID=1,EX ISTCTX=NO,ASTAG=CLT,ASUP="H248",ASMD=LOAD,NVA L=1,KVAL=0; 9. Create a M3UA static route. ADD M3UART:ID=1,ASID=1,MODE=BYTURNS,NAME="IM -MGW101"; 10. Create the SIO-locating-AS. ADD SIOLOCAS:ID=1,NAME="IM-MGW-H248",SIO=H24 8,OFCID=101,OPOFCID=65535,PCM=65535,RT1=1,RT2 =0; 11. Create MGCF tones in batches. BADD STONE:TYPE=ALL; 12. Create the MGC static data. ADD MGCSCFG:MEGACO=1,ACTTM=600,ACTCHK=ON,W AITTM=7800,PTRYNUM=5,PTRYTM=4000,CTXLIVETM=1 200,MGACTTM=600; 13. Create the IM-MGW static data template. ADD MGSTPL:NAME="IM-MGW101",ID=1,MEGACO=1,AC TCHK=ON,PRTTM=10,PRT=ON,PENDTM=200,LNGTM=15 000,RTRNTM=3800,MTRNNUM=1,TRNMD=UNFIXED,CTYP E=TEXT; 14. Create the IM-MGW static data. ADD MGSCFG:ID=101,NAME="IM-MGW101",TPLID=1,TO NEID=1,LANGID=1,PKGLOST=10,JIT=50,DELAY=200,M GW=NO; 15. Create the TID analyzer. ADD TIDANL:NAME="IM-MGW101",PREV=1,TIDPFX="TD M",TAG=TRUNK,PCMSPR="_",IDXSPR="/",PCMPOS1=1,P CMPOS2=0,IDXPOS1=1,IDXPOS2=0; 16. Create the TID analysis entrance. ADD TIDENTR:ND=101,TIDENTID=1,TIDTPLID=1,NAME ="MGW101";
Confidential and Proprietary Information of ZTE CORPORATION
273
ZXWN MSCS Data Configuration Guide(MGCF)
Adjacent SCSCF Office Interconnection Data Configuration Data Planning
Table 111 lists the parameters in the adjacent-SCSCF-office interconnection data configuration. TABLE 111 PARAMETERS IN THE ADJACENT SCSCF OFFICE INTERCONNECTION DATA CONFIGURATION
Command
Configuration Parameters
Configuration Description
IP of the virtual interface at the MGCF side
10.1.44.77
IP of the virtual interface at the CSCF side
10.1.33.11
Adjacent CSCF office ID
12
Adjacent CSCF office type
"LOCAL"&"DOMTOLL"&"IP"
Association mode
AM_SURE (Associated)
CSCF topology node No.
12
Signaling point type of the CSCF
24-bit
SPC of the CSCF
2.12.1
IP link No.
12
Route selector
1
Service group
1
CSCF adjacent host
12
UDP bear ID
1 (Local valid), 2 (Remote valid)
SIP signaling link ID
12
SIP route ID
12
SIP route set ID
12
1. Create an SCSCF adjacent office. ADD ADJOFC:ID=12,NAME="SCSCF",NET=1,OFCTYPE="L OCAL"&"DOMTOLL"&"IP",SPCFMT=TRIPLE_DEC,SPCTYPE=2 4,DPC="2.12.1",RC="25",ASSOTYPE=AM_SURE,SPTYPE =SEP,SSF=NATIONAL,SUBPROTTYPE=DEFAULT,TEST=YE S,BANDFLAG=YES,PRTCTYPE=CHINA,CLST=65535,INFO ="CIC_PCM",RELATEDOFC1=0; 2. Create an SCSCF topology node.
274
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 8 Configuration Instance
ADD TOPO:ID=12,OFCID=12,NAME="SCSCF",CODECID =1,ETYPE=MSCVLR,PROTTYPE=SIP,IPVER=IPV4,ATTR ="BNCIPRTP",ATTR2=NOTUNL,TRFMOD=MCINTF,UPERRCT RL=YES,DTMFTC=NO,MGWCON=SMGWCON,AUTOFAX=YE S,OOBTC=NO,BCUID=0,SENDCAP=NO,G711TRAN=NO,BI CCDTMF=TRANSPARENT,IPBCP2833=BYMGW,BICCDTMP PER=0,AOIPPRO=PRIVATE; 3. Create a SIP office direction. ADD SIPOFC:OFCID=12,URL=URI,BYPASS=NO,BYPASS PCT=80,BYPASSPRD=5,BYPASSTLEN=30,BYPASSLEV=L N,BYPASSCALLNUM=1,BTYPE=IN,OVERLAP=RINVT,CFIN FO=HIS,PBRTFMT=EQUAL,DTMF=IN,FMT4733=97,SIPRE L=NO,ENOPT="SIP_ESSO"&"SIP_PRECOND"&"T30"&"FCPL"; 4. Create an IP link. ADD IPLINK:OFCID=12,MODULE=3,NAME="IPLINK-12",I D=12,LOCIP="IPv4"-"0"-"10.1.44.77",LOCPORT=5060,RE MIP="IPv4"-"0"-"10.1.33.11",REMPORT=5060,PRO=UDP,T CPROTO=CLT,TSTIMER=15000; 5. Create an adjacent host. ADD ADJHOST:ID=12,HOSTNAME="SCSCF",REALM="zte. com",SRVGRP=1; 6. Create a local valid UDP bear. ADD UDPBR:ID=1,NAME="LOCAL",IPMODE=LOCAL_VALI D,ADJHOST=0,IPLINK=12,DSTADDRTYPE=IPV4,DSTVPN =0,DSTPORT=0; Create a remote valid UDP bear. ADD UDPBR:ID=2,NAME="REMOTE",IPMODE=REMOTE_V ALID,ADJHOST=12,IPLINK=0,DSTADDRTYPE=IPV4,DSTV 4ADDR="10.1.33.11",DSTVPN=0,DSTPORT=5060; 7. Create SIP signaling link. ADD SIPLNK:ID=12,NAME="SCSCFLINK",BRID=2,HBTIM E=0,NORMALHBTIME=120,UNUSECNT=3,USECNT=3; 8. Create SIP signaling route. ADD 2";
SIPRT:ID=12,NAME="SCSCFR",SPLC=SEQ,LNK="1
9. Create SIP signaling route set. ADD SIPRTS:ID=12,NAME="SCSCFRS",RTPLC=SEQ,SIPR T="12"-"100";
Confidential and Proprietary Information of ZTE CORPORATION
275
ZXWN MSCS Data Configuration Guide(MGCF)
Basic Service Data Configuration Call Data Configuration Data Planning
Table 112 lists the parameters in the call data configuration. TABLE 112 PARAMETERS IN THE CALL DATA CONFIGURATION
Command
Configuration Parameters
Configuration Description
Number analyzer entry
1 (Local number analyzer)
DAS
Originating DAS 101
Call prefix of the test number
8613902099
Call service type
13902099: LOL (Outgoing/Local service of the local network)
1. Create a number analysis entrance. ADD ENTR:ID=1,NAME="LOCAL",TYPE=LOCAL,NTYPE=CA LLED; 2. Create a DAS. ADD DAS:ID=101,NAME="MSQH",NEWSRV=0,CENTR =0,PRINET=0,SPECSRV=0,LOCAL=1,NATIONAL=0,INTE R=0; 3. Set the default DAS template of the local office. SET LDASTMPLT:MS=101,MSRN=201; 4. Create the called number analysis. ADD TPDNAL:ENTR=1,DIGIT="13902099",SPECRST=0,S PECIDX=0,CAT=LOL,RST1=1,RST2=0,RST3=0,CHAINA L=0,RNLEN=0,MINLEN=3,MAXLEN=20,OVLYPRI=NO,R EL=NO,NET=1,NAT=DEF,OPDDICONT=NO,TPDDICONT =NO,OPDDI=0,TPDDI=0,OPDLYDDI=0,TPDLYDDI=0,DD IOVERB=0,IWVIDEO=LSUP,TIMELMT=0,AUXDAS=0,A6 =0,PFXLEN=0,INSRV=INM,FAXIDX=0,AVIDX=0,DVIDX =0,ADATAIDX=0,DDATAIDX=0,DDCPLAY=NONE,VAD=IN VALID,CALLSERVPRILVL=INVALID,RERTS=0,INCHAIN=N O,BICT=NO,ICT=0,ICTT=10,GNM=NORMAL,STBILL=INVA LID,HOPDAS=0,MCA=NO,IVVR=NO,WANTL=0,IMSCENTR =NO;
276
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 8 Configuration Instance
SIP Service Data Configuration Data Planning
Table 113 lists the parameters in the SIP service data configuration. TABLE 113 PARAMETERS IN THE SIP SERVICE DATA CONFIGURATION
Command
Configuration Parameters
Configuration Description
IP distribution policy ID
1
V4NET
10.1.33.11
URI
scscf.zte.com
SIP method
ACK"&"BYE"&"CANCEL"&"INVITE "&"PRACK"&"UPDATE
UDP distribution policy
Excellent choice priority
UDP bear ID
1
1. Create IP distribution policy. ADD IPDPLC:ID=1,NAME="MGCF11",ADDRTYPE=IPV4,V 4NET="10.1.33.11",V4MSK="255.255.255.0",PORT=0,UPL C=PRIROR,UDPID="1"; 2. Create URI analysis. ADD URI:RTSEL=1,URI="scscf.zte.com",METHOD="ACK "&"BYE"&"CANCEL"&"INVITE"&"PRACK"&"UPDATE",SIPRTS =12;
Data Synchronization Command
SYNA:STYPE=ALL,TIMEOUT=600,SAVE=YES,TOSLAVE=YES;
MGCF-IM-MGW Interconnection Debugging Procedure After data of the IM-MGW are configured on the MGCF, the common procedures for data debugging are as follows.
Confidential and Proprietary Information of ZTE CORPORATION
277
ZXWN MSCS Data Configuration Guide(MGCF)
Steps
Operations
Description
1
Checking the IM-MGW office status
Check whether the IM-MGW office is accessible
2
Checking the physical connection
When the office is inaccessible, first confirm whether there is any hardware problem
3
Debugging the SCTP
After the hardware problem is removed, confirm whether there is any problem in the SCTP association
4
Debugging the M3UA
After the problem in the SCTP association is removed, confirm whether there is any problem in upper-layer M3UA signaling link
5
Confirming the working status of the IM-MGW
After the problem on the M3UA layer is removed, check the H.248 gateway configuration
Checking the IM-MGW Office Status Prerequisites
The IM-MGW adjacent office data configuration is completed.
Context
Check whether the office is accessible is the first step for debugging. This section introduces the detailed procedures for checking whether the IM-MGW office is accessible.
Steps
1. On the NetNumen M30 window, select menus Views > MML Terminal to enter the MML Terminal window. 2. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the MGCF exchange to be configured. 3. Enter the following command on the MML Terminal window, and click Execute to query the status of the adjacent IM-MGW office. OFC is the adjacent IM-MGW office ID. SHOW OFCSTAT:OFC=101;
Note: You can check whether the office is accessible, and the status of the SIGTRAN signaling on the Dinamic management page of the View window. END OF STEPS Result Postrequisite
278
The Command Execute Result shows the M3UA Office State is Reachable. If the office is inaccessible, check the physical connection.
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 8 Configuration Instance
Checking the Physical Connection Prerequisites
The IM-MGW adjacent office data configuration is completed.
Context
If it is found that the adjacent IM-MGW office is not reachable on the NetNumen M30 window, confirm whether the physical connection between the MGCF and the IM-MGW is normal.
Steps
1. When the MGCF is connected with the IM-MGW through HUB, the straight network cable should be adopted. When the MGCF is directly connected with the IM-MGW, the crossover network cable should be adopted. END OF STEPS
Result
The physical connection is normal when the indicators Link1 and Link3 on the SIPI board are always on.
Debugging the SCTP Prerequisites
Context Steps
�
The IM-MGW adjacent office data configuration is completed.
�
The physical connection is normal between MGCF and IM-MGW.
�
The MML Terminal window is opened.
If the physical connection is normal, debug the SCTP. 1. On the NetNumen M30 window, select menus Views > MML Terminal to enter the MML Terminal window. 2. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the MGCF exchange to be configured. 3. Enter the following command on the command terminal, and click Execute to query the STCP status. ASSOCID is the association ID. SHOW SCTPSTAT:ASSOCID=1; END OF STEPS
Result
The Command Execute Result shows the SCTP Status is Established.
Postrequisite
If the association is not established, check whether the IP address configuration of the port is correct.
Debugging the M3UA Prerequisites
�
The IM-MGW adjacent office data configuration is completed.
�
The physical connection is normal between MGCF and IM-MGW.
�
The association between MGCF and IM-MGW is established.
Confidential and Proprietary Information of ZTE CORPORATION
279
ZXWN MSCS Data Configuration Guide(MGCF)
� Context
The MML Terminal window is opened.
If the SCTP is established, debug the M3UA. The physical status of the ASP is decided by the association status. After the association is established, the ASPs at the both ends perform handshaking of the service status maintenance message “ASPTM”. If the handshaking is successful, the service can be used.
Steps
1. On the NetNumen M30 window, select menus Views > MML Terminal to enter the MML Terminal window. 2. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the MGCF exchange to be configured. 3. Enter the following command on the MML Terminal window, and click Execute to query the ASP status. ASID is the AS ID, and ASPID is the ASP ID. SHOW ASPSTAT:ASID=1,ASPID=1; 4. Enter the following command on the MML Terminal window, and click Execute to query the AS status. ASID is the AS ID. SHOW ASSTAT:ASID=1; END OF STEPS
Result
�
When the ASP status in active, ASP Status Active should be displayed.
�
When the AS status in normal, AS Status Active should be displayed.
Confirming the Working Status of the IM-MGW Context
After the office direction to the IM-MGW is debugged successfully, the status of the IM-MGW is not guaranteed to be normal. This section introduces the method of confirming the working status of the IM-MGW. After the data for connection between the MGCF and the IM-MGW are configured and the equipment is started, the IM-MGW will actively register the gateway information to the MGCF. This topic describes the method of confirming the working status of the IM-MGW.
Steps
1. On the NetNumen M30 window, select menus Views > MML Terminal to enter the MML Terminal window. 2. If no exchange is specified, execute command SET on the MML Terminal window or select a NE from the system tree to specify the MGCF exchange to be configured. 3. Enter the following command on the MML Terminal window, and click Execute to query the registration status of the gateway.
280
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 8 Configuration Instance
SHOW MGWSTAT; END OF STEPS Result
The Command Execute Result shows the MGW Status is In Service.
Postrequisite
When the working status of the gateway is exceptional, check whether the corresponding parameters in the H248 configuration and the SIGTRAN configuration on the MGCF and the IM-MGW are consistent and meet the requirements.
H.248/SCTP Problem Location Method For two NEs adopting SIGTRAN networking, to judge whether the bottom-layer link is reliable, it is necessary to confirm whether two connections are normal. One is the connection between two SIG_IPIs, and the other is the control channel between the SIG_IPI and the SMP. �
Debugging the IP protocol stack Debugging the connection between two SIG_IPIs means debugging the IP protocol stack. When the physical connection is normal, connect one computer to HUB or to SIGIPI through the crossover network cable. Ping the IP addresses of the SIPI interface and the loop-back interface of the local end, and those of the opposite end. When the IP protocol stack is correctly configured, these IP addresses should be pinged successfully. If they cannot be pinged successfully, confirm whether the IP protocol stack is correctly configured.
�
Debugging the basic SCTP connection information After the protocol stack is normal, it is necessary to check data in the SCTP configuration , including whether the protocol type, the server and the client are normal; whether the office ID, IP address, and port number are correct; and whether the port number is repeated.
M3UA Problem Location Method When the status of the lower-layer association is normal, and the status of the AS/ASP is abnormal, it is necessary to confirm whether AS data, ASP data, and SIO-locating-AS data are correctly configured, and whether the interconnecting parameters between the local office and the opposite-end office are consistent.
Confidential and Proprietary Information of ZTE CORPORATION
281
ZXWN MSCS Data Configuration Guide(MGCF)
This page is intentionally blank.
282
Confidential and Proprietary Information of ZTE CORPORATION
Figure
Figure 1 IMS NETWORKING ................................................. 1 Figure 2 OVERALL FLOW OF THE MGCF DATA CONFIGURATION .. 3 Figure 3 START PROCESS OF THE OMM SERVER ..................... 5 Figure 4 START INFORMATION OF THE OMM SERVER............... 5 Figure 5 LOGIN Window ...................................................... 6 Figure 6 NETNUMEN M30 MSCS/MGW OMM SYSTEM WINDOW .. 7 Figure 7 MML Terminal Window .......................................... 8 Figure 8 MML TERMINAL Window .......................................... 9 Figure 9 COMMAND EXECUTION OPERATIONS .......................10 Figure 10 LOCAL OFFICE DATA CONFIGURATION FLOW...........14 Figure 11 PHYSICAL CONFIGURATION FLOW .........................18 Figure 12 FLOW OF LOADING VERSION FILES .......................40 Figure 13 VERSION LOADING..............................................42 Figure 14 CONFIGURING VERSION PATH ..............................42 Figure 15 Adding New Blank Entry .......................................43 Figure 16 Configuring Version Name.....................................43 Figure 17 VERSION FILE PATH.............................................44 Figure 18 Load Version .......................................................45 Figure 19 Version List.........................................................46 Figure 20 CREATING OMP BOOT FILES .................................46 Figure 21 Successful Infomation ..........................................47 Figure 22 CONNECTION DESCRIPTION .................................48 Figure 23 CONNECT TO DIALOG BOX ...................................48 Figure 24 COM1 PROPERTIES ..............................................49 Figure 25 PRESS ANY KEY TO STOP AUTO-BOOT ....................49 Figure 26 BOOT PASSWORD................................................50 Figure 27 3GPLAT BOOT .....................................................50 Figure 28 CONFIG SELECTION.............................................51 Figure 29 ENTER OMP’S OMC IP ADDRESS ............................51 Figure 30 ENTER OMP’S OMM MAC ADDRESS ........................52 Figure 31 ENTER OMP’S GATEWAY IP ADDRESS .....................52 Figure 32 OMC SERVER IP ADDRESS ....................................53 Figure 33 CONFIG SELECTION.............................................53 Figure 34 OMM IP ADDRESS ...............................................54
Confidential and Proprietary Information of ZTE CORPORATION
283
ZXWN MSCS Data Configuration Guide(MGCF)
Figure 35 FTP CONFIG........................................................54 Figure 36 OMPCFG FILE......................................................55 Figure 37 CONFIG SELECTION.............................................55 Figure 38 OMP BOOT TYPE ..................................................56 Figure 39 CONFIG SELECTION.............................................56 Figure 40 BUREAU NO. .......................................................57 Figure 41 CONFIG SELECTION.............................................57 Figure 42 3GPLAT BOOT .....................................................58 Figure 43 USER NAME AND PASSWORD ................................61 Figure 44 STATUS..............................................................62 Figure 45 Version Mainenance .............................................63 Figure 46 Version List.........................................................64 Figure 47 BATCH VERSION LOADING BY DEFAULT ..................64 Figure 48 AREA TREE .........................................................76 Figure 49 ADDING RESOURCES ...........................................76 Figure 50 RESOURCE ADDING DIALOG BOX ..........................77 Figure 51 FLOW OF MGCF-IM-MGW INTERCONNECTION CONFIGURATION ...............................................80 Figure 52 SIGTRAN CONFIGURATION FLOW ........................ 107 Figure 53 CONFIGURATION FLOW ...................................... 120 Figure 54 FLOW OF CONFIGURING A DIRECT-ASSOCIATED OFFICE IN IP DOMAIN ...................................... 167 Figure 55 QUASI-ASSOCIATED NETWORKING BETWEEN MSCS AND 2G MSC/PSTN (BASED ON M3UA) ...... 175 Figure 56 FLOW OF M3UA TRANSIT EXCHANGE ................... 176 Figure 57 QUASI-ASSOCIATED NETWORKING BETWEEN MGCF AND 2G MSC/PSTN (BASED ON M2UA) ...... 177 Figure 58 FLOW OF M2UA TRANSIT EXCHANGE ................... 178 Figure 59 TDM OFFICE INTERCONNECTION CONFIGURATION FLOW............................................................. 182 Figure 60 ANALYSIS ORDER OF NUMBER ANALYZERS ........... 194 Figure 61 NETWORKING DIAGRAM..................................... 265 Figure 62 BOARD LAYOUT OF THE BCTC SHELF ................... 267
284
Confidential and Proprietary Information of ZTE CORPORATION
Table
Table 1 LOGIN PARAMETER DESCRIPTION.............................. 6 Table 2 PARAMETERS IN THE SYNA COMMAND .....................11 Table 3 PARAMETERS IN THE SYN COMMAND........................11 Table 4 PARAMETERS IN THE ADD NE COMMAND ..................16 Table 5 PARAMETERS IN THE SET PCINFO COMMAND ...........17 Table 6 PARAMETERS IN THE ADD RACK COMMAND ..............20 Table 7 PARAMETERS IN THE ADD SHELF COMMAND.............21 Table 8 PARAMETERS IN THE ADD UNIT COMMAND ..............22 Table 9 PARAMETERS IN THE ADD MODULE COMMAND .........24 Table 10 MGCF BOARD TYPES .............................................25 Table 11 PARAMETER IN THE ADD UNIT COMMAND ..............27 Table 12 PARAMETERS IN THE ADD UNIT COMMAND.............28 Table 13 PARAMETERS IN THE ADD UNIT COMMAND.............30 Table 14 PARAMETERS IN THE ADD UNIT COMMAND.............31 Table 15 PARAMETERS IN THE ADD UNIT COMMAND.............32 Table 16 PARAMETER IN THE ADD SVRINF COMMAND...........34 Table 17 CAPACITY CONFIGURATION....................................34 Table 18 Office Capacity Configuration Parameters .................35 Table 19 PARAMETERS IN THE SET DATASIZE COMMAND ......38 Table 20 VERSION DESCRIPTION OF OMP BOOT FILE .............45 Table 21 PARAMETERS IN THE SET OMP COMMAND ..............59 Table 22 PARAMETERS IN THE SYNA COMMAND....................60 Table 23 Board Version Files................................................62 Table 24 BOARD INDICATOR STATUSES ................................65 Table 25 PARAMETERS IN THE BADD STONE COMMAND ........66 Table 26 Office Information Configuration .............................67 Table 27 PARAMETERS IN THE ADD OPC COMMAND ..............68 Table 28 PARAMETERS IN THE ADD LOFC COMMAND ............70 Table 29 RESOURCE TYPES, KEY FIELDS AND VALUE RANGES OF THE MGCF....................................................74 Table 30 FLOW DESCRIPTION..............................................80 Table 31 INTERFACE IP ADDRESS CONFIGURATION................81 Table 32 PARAMETERS IN THE ADD IP ADDRESS COMMAND...82 Table 33 INTERFACE REAL INTERFACE ................................83
Confidential and Proprietary Information of ZTE CORPORATION
285
ZXWN MSCS Data Configuration Guide(MGCF)
Table 34 PARAMETERS IN THE ADD IP ADDRESS COMMAND...84 Table 35 INTERFACE VIRTUAL INTERFACE ...........................85 Table 36 PARAMETERS IN THE ADD IP ADDRESS COMMAND...86 Table 37 PARAMETERS IN THE ADD BFD AUTH COMMAND .....88 Table 38 PARAMETERS IN THE ADD BFD SESSION COMMAND ........................................................89 Table 39 PARAMETERS IN THE ADD IP ROUTE COMMAND......91 Table 40 ADJACENT AND TOPOLOGY CONFIGURATION............92 Table 41 PARAMETERS IN THE ADD ADJOFC COMMAND ........93 Table 42 PARAMETERS IN THE ADD CODECTPL COMMAND ....98 Table 43 PARAMETERS IN THE ADD TOPO COMMAND .......... 100 Table 44 PARAMETERS IN THE ADD MGWBEARMOD COMMAND ...................................................... 103 Table 45 PARAMETERS IN THE ADD SCTPCONN COMMAND .. 109 Table 46 PARAMETERS IN THE ADD ASP COMMAND ............ 112 Table 47 PARAMETERS IN THE ADD AS COMMAND .............. 113 Table 48 PARAMETERS IN THE ADD M3UART COMMAND...... 116 Table 49 PARAMETERS IN THE ADD SIOLOCAS COMMAND... 118 Table 50 PARAMETERS IN THE ADD MGCSCFG COMMAND.... 121 Table 51 PARAMETERS IN THE ADD MGSTPL COMMAND ...... 123 Table 52 PARAMETERS IN THE ADD MGSCFG COMMAND...... 124 Table 53 PARAMETERS IN THE ADD TIDANL COMMAND....... 126 Table 54 PARAMETERS IN THE ADD TIDENTR COMMAND..... 128 Table 55 FLOW DESCRIPTION............................................ 129 Table 56 PARAMETERS FOR CREATING A SIP ADJACENT OFFICE .......................................................... 131 Table 57 PARAMETERS IN THE COMMAND ADD SIPOFC ....... 136 Table 58 PARAMETERS IN THE ADD TOPO COMMAND .......... 137 Table 59 PARAMETERS IN THE ADD IPLINK COMMAND ....... 143 Table 60 PARAMETERS IN THE SET SIPCAPA COMMAND...... 145 Table 61 PARAMETERS IN THE ADD REALM COMMAND ........ 146 Table 62 PARAMETERS IN THE ADD HOST COMMAND .......... 147 Table 63 PARAMETERS IN THE ADD RTSEL COMMAND ......... 148 Table 64 PARAMETERS IN THE ADD SRVG COMMAND .......... 149 Table 65 PARAMETERS IN THE ADD ADJHOST COMMAND .... 150 Table 66 PARAMETERS IN THE ADD UDPBR COMMAND........ 151 Table 67 PARAMETERS IN THE ADD SIPLNK COOMMAND..... 153 Table 68 PARAMETERS IN THE ADD SIPRT COMMAND ......... 154 Table 69 PARAMETERS IN THE ADD SIPRTS COMMAND ....... 156 Table 70 PARAMETERS IN THE ADD IPDPLC COMMAND ....... 157
286
Confidential and Proprietary Information of ZTE CORPORATION
Tables
Table 71 PARAMETERS IN THE ADD URI COMMAND............. 159 Table 72 PARAMETERS IN THE ADD TG RTP COMMAND ....... 161 Table 73 BEARER MODES OF MAIN INTERFACES .................. 165 Table 74 PARAMETERS IN THE ADD ADJOFC COMMAND ...... 168 Table 75 PARAMETERS IN THEADD TOPO COMMAND........... 173 Table 76 PARAMETERS IN THE ADD M2UAIPLNK COMMAND ...................................................... 180 Table 77 PARAMETERS IN THE ADD N7LKS COMMAND ........ 184 Table 78 PARAMETERS IN THE ADD N7LNKE1 COMMAND .... 186 Table 79 PARAMETERS IN THE ADD N7ROUTE COMMAND.... 188 Table 80 ARRANGEMENT MODE OF SIGNALING SETS............ 189 Table 81 PARAMETERS IN THE ADD N7OFC COMMAND ........ 191 Table 82 DAS FOR PRE-ANALYZING THE CALLED NUMBER ..... 194 Table 83 ORIGINATING DAS .............................................. 195 Table 84 FORWARDING DAS.............................................. 196 Table 85 ROAMING DAS.................................................... 197 Table 86 PARAMETERS IN THE ADD ENTR COMMAND .......... 199 Table 87 ANALYZER ENTRY TYPES ...................................... 200 Table 88 COMMON DAS .................................................... 201 Table 89 PARAMETERS IN THE ADD DAS COMMAND ............ 202 Table 90 PARAMETERS IN THE SET LDASTMPLT COMMAND .. 203 Table 91 PARAMETERS IN THE ADD ACRTMPLT COMMAND .. 207 Table 92 PARAMETERS IN THE ADD TPDNAL COMMAND ...... 211 Table 93 CALL SERVICE TYPES .......................................... 225 Table 94 ENABLED OPTIONS ............................................. 232 Table 95 PARAMETERS IN THE ADD TG DT COMMAND ......... 237 Table 96 PARAMETERS IN THE ADD TG ATM COMMAND ....... 244 Table 97 PARAMETERS IN THE ADD TG RTP COMMAND ....... 250 Table 98 PARAMETERS IN THE ADD SPCM COMMAND .......... 255 Table 99 PARAMETERS IN THE ADD INPCM COMMAND ........ 257 Table 100 PARAMETERS IN THE ADD RT COMMAND............. 259 Table 101 PARAMETERS IN THE ADD RTS COMMAND........... 261 Table 102 PARAMETERS IN THE ADD CHAIN COMMAND ...... 262 Table 103 NEGOTIATION DATA INSTANCE ........................... 266 Table 104 SIGTRAN IP ADDRESS INSTANCE OF THE MC INTERFACE ..................................................... 266 Table 105 DATA PLANNING OF THE LOCAL EXCHANGE CONFIGURATION ............................................. 267 Table 106 DATA PLANNING OF THE PHYSICAL CONFIGURATION ............................................. 268
Confidential and Proprietary Information of ZTE CORPORATION
287
ZXWN MSCS Data Configuration Guide(MGCF)
Table 107 DATA PLANNING OF THE CAPACITY CONFIGURATION ............................................. 269 Table 108 DATA PLANNING OF THE OFFICE DATA CONFIGURATION ............................................. 269 Table 109 RESOURCE PLANNING INSTANCE ........................ 270 Table 110 PARAMETERS IN THE ADJACENT MGW OFFICE INTERCONNECTION DATA CONFIGURATION ........ 271 Table 111 PARAMETERS IN THE ADJACENT SCSCF OFFICE INTERCONNECTION DATA CONFIGURATION ........ 274 Table 112 PARAMETERS IN THE CALL DATA CONFIGURATION .. 276 Table 113 PARAMETERS IN THE SIP SERVICE DATA CONFIGURATION ............................................. 277
288
Confidential and Proprietary Information of ZTE CORPORATION
Index A
MML Terminal......................4
Active/standby mode ......... 29 Active/standby networking...................... 80 Address planning............... 80 Adjacent office .................. 81
N Network section ................ 81
O
B Background ........................2 BFD configuration .............. 80
OMM Client .........................4 OMM server ........................2
C
P
Cable connection .................2 Commissioning.................. 29 crossover network cable ............................ 279 Crossover network cable ............................ 281
Physical configuration ........ 18 Protocol stack ................... 79
D Data configuration ...............4 Data Synchronization ...........4
Q Quasi-associated ............. 177
R Rack ..................................2
H
S
H248 configuration ............ 81 Hardware installation ...........2
SCTP configuration .......... 281 Shelf..................................2 Signaling Route ............... 179 SIGTRAN ........................ 281 SIGTRAN configuration ....... 81
I Inter-office ....................... 29 Interconnection data ........................... 3, 79 IP address ...................... 281 IP protocol stack ............. 281
T Topological node................ 81 Topological node configuration ................... 81
L LAN ...................................2 Link ............................... 281 Load-sharing .................... 80 Load-sharing mode ............ 29 local office ...................... 281 Loop-back interface ......... 281
M M3UA............................. 280
Confidential and Proprietary Information of ZTE CORPORATION
289
