Professional Documents
Culture Documents
SJ-20101208143956-008-ZXWN MSCS (V4.10.13) MSC Server Data Configuration Guide (MSCS II)
SJ-20101208143956-008-ZXWN MSCS (V4.10.13) MSC Server Data Configuration Guide (MSCS II)
MSC Server
Data Configuration Guide (MSCS II)
Version: V4.10.13
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: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2011 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
Figures............................................................................................................. I
Tables ............................................................................................................ III
Index ...............................................................................................................V
I
Glossary .......................................................................................................VII
II
About This Manual
Purpose
ZXWN MSCS MSC Server Configuration Guide (MSCS I) describes MSCS data
configuration principle, basic office data configuration, version loading, resource
configuration, Mc interface interconnection data configuration, office direction signaling
interconnection data configuration, and radio office interconnection data configuration.
ZXWN MSCS MSC Server Data Configuration Guide (MSCS II) describes basic service
debugging related to call service, general service debugging related to billing.
Intended Audience
This manual is intended for engineers and technicians who have mastered the
communication principle of the mobile network.
Chapter Summary
Chapter 1, Basic Service Configuration and Describes the basic service debugging related with
Debugging call service
Conventions
ZTE documents employ the following typographical conventions.
I
Typeface Meaning
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.
II
Declaration of RoHS
Compliance
To minimize environmental impacts and take more responsibilities to the earth we live
on, this document shall serve as a formal declaration that MSCS manufactured by
ZTE CORPORATION is in compliance with the Directive 2002/95/EC of the European
Parliament - RoHS (Restriction of Hazardous Substances) with respect to the following
substances:
l Lead (Pb)
l Mercury (Hg)
l Cadmium (Cd)
l Hexavalent Chromium (Cr (VI))
l PolyBrominated Biphenyls (PBBs)
l PolyBrominated Diphenyl Ethers (PBDEs)
I
II
Chapter 1
Basic Service Configuraiton
and Debugging
Table of Contents
Location Update Configuration and Debugging...........................................................1-1
Interior Calls Data Configuration and Debugging ......................................................1-43
Inter-office Calls Data Configuration and Debugging ................................................1-82
1-1
The difference between the GT and the DPC+SSN routing modes is manifested in the case
where there are STPs in the source signaling point and the destination signaling point.
In the DPC+SSN routing mode, it is required that all the signaling points (including the
source signaling point, destination signaling point, and STP) in the network can identify
the Destination signaling Point Code (DPC). The signaling is directly sent from the MTP
layer after reaching the intermediate point instead of passing the SCCP layer. In this case,
more DPC data need to be configured for the source signaling point and the STP.
The GT routing mode can be used when the final DPC of the signaling is unknown to
the source signaling point and part of STPs. When this addressing mode is adopted, and
when the signaling is transferred to the STP, the SCCP translates the GT to the destination
signaling point or the DPC of the next-hop STP, and then sends the message to the MTP
for transfer. When the GT routing mode is adopted, the source signaling point only needs
to send the signaling to the STP of the next-hop GT translation according to the GT number
prefix, and then the STP determines whether to send the signaling to the next STP or the
destination signaling point . In this case, less DPC data need to be configured for the
source signaling point and the STP.
Configuration Rules
Tip:
Comply with operator’s specification for data compiling.
Usually you only need to configure two GT translation selectors, selector 1 for E.164
and selector 2 for E.214.
Data Configuration
The related operations of the SCCP data configuration are as follows.
1-2
Abstract
In general, two GT translation selectors are configured, corresponding to E164 and E214
numbering plans respectively.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l Interconnection with the adjacent HLR office is completed, and the signaling office
direction is successfully debugged.
l The MML Terminal window is opened.
Context
The numbers to be configured are described as follows:
1. E214 number
The format of the E.212 number is “MCC+MNC+MSIN”, while that of the E.214 number
is “CC+NDC+MSIN”, which are used for location registration of mobile subscribers.
It is usually required to convert the “MCC+MNC” part to “CC+NDC” according to mobile
number analysis, to construct the format of the E214 number.
2. E164 number
The format of the E.164 number is “MSISDN”, which is used for communication when
the mobile subscriber acts as the called party, and the communication between mobile
NEs.
During the location update debugging procedure, it is only required to configure the
MSC/VLR GT and HLR GT of the local office.
1-3
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create a GT translation selector by executing command ADD GTT.
The explanation of the main parameters in command ADD GTT is shown in Table 1-1.
1-4
NMIN National minimum digit length They are optional parameters, which are
integers, ranging from 1 to 20. They
NMAX National maximum bit length
respectively correspond to the national
minimum GT number length, and national
maximum GT number length configured in the
GT translation data configuration. In general,
the national minimum digit length is set to 5,
while the national maximum digit length is set
to 15.
1-5
IMIN International minimum digit They are optional parameters, which are
length integers, ranging from 1 to 20. They
respectively correspond to the international
IMAX International maximum digit
minimum GT number length, and international
length
maximum GT number length configured in the
GT translation data configuration. In general,
the international minimum digit length is set
to 1, while the international maximum digit
length is set to 5.
l GT type: 4
l Translation type: 0
l Numbering plan: E.164
l Address attribute: international number
l GT translation selector: 1
l National minimum digit length: 5
l National maximum digit length: 15
l International minimum digit length: 1
l International maximum digit length: 5
l User alias: E.164.
1-6
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l GT translation selectors are configured.
l The MML Terminal window is opened.
Context
The GT translation data are used for location update, calls and inter-office handover. When
configuring GT translation data, it is required to add the GT translation data for the source
address and the destination address of the signaling on each end point or transfer point.
When configuring location update data, it is required to translate the local GT number to
the office ID 0, that is, local office, and translate the GT number of the HLR to the HLR or
STP. Therefore, it is required to configure at lease two sets of GT translation data on the
MSCS.
E164 number: It is required to configure the local MSC/VLR GT, MSISDN number, and the
MSC/VLR GT having the LAI adjacency relationship.
1-7
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
an NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create GT translation data by executing command ADD GT.
The explanation of the main parameters in command ADD GT is shown in Table 1-2.
1-8
1-9
1-10
1-11
SSN Meaning
SCCP SCCP
ISDN/ASE ISDN_ASE(11)
USSD USSD
VLRA VLRA
RANAP RANAP
RNSAP RNSAP
CAP CAP
NPDB NPDB
ATER ATER
IP IP
HLR_SSAP HLR_SSAP
UDS_DMCC UDS_DMCC
BSC_BSSAP_LE/MPC BSC_BSSAP_LE/MPC
MSC_BSSAP_LE MSC_BSSAP_LE
1-12
SSN Meaning
SMLC_BSSAP_LE SMLC_BSSAP_LE
BSS_O_M_A BSS_O_M_A
BSSAP_A BSSAP_A
Example: Create the HLR GT translation data with the following requirements:
l GT number: 8613907551
l GT translation selector ID: 1
l Office ID poll: 1-1
l Routing mode: GT routing
l Other parameters: Adopt default values.
The command is:
ADD GT: GT= "8613907551", GTSL= 1, GTDI= 0, OFCIDS= "1"-"1", GRP= NO, SSN=
NO_SSN, NTRNTYPE= 0, TRNRLT= "SSN", RTTYPE= GT, NGTTAG= NGT, SCCP=
INT, MAP= R4, VGT= NO, TT= NO, NPFLAG= NO, NPLAN= NULL, SRVTYPE= NULL;
– End of Steps –
Abstract
This topic introduces the system control parameters configuration related to MAP.
Prerequisites
The GT data configuration is completed.
1-13
Steps
1. In the NetNumen M30 window, select Views > Professional Maintenance > MSCS
> Security Variable > WCN Security Variable > System Control. The System
Control tab pops up.
2. On the System Control tab, select the corresponding variables, and click on the
sub-toolbar to enter the editing status. Select the corresponding options, as shown in
Figure 1-1.
l Send MAP Phase Setting: Phase2+ for domestic 2G and R4 for 3G. The phase
number actually sent in MAP message should be the lower one of the MAP phase
configured here and the MAP phase configured in GT translation.
l Receive MAP Phase Setting: it is usually same as the MAP phase of the sending
end.
l TM Packet Size (Byte): it is related to capacity of interconnected devices. If they
support XUDT message, size of TM packet can be set as 2000 to reduce number
of message sending. It should be set as 150 if XUDT is not supported so that
over-long streams can be sent in packets.
– End of Steps –
1-14
Abstract
This topic introduces the CS network entity config parameters configuration related to MAP.
Prerequisites
The GT data configuration is completed.
Steps
1. On the NetNumen M30 window, select Views > Professional Maintenance > MSCS
> Security Variable > WCN Security Variable > CS Network Entity Config. The CS
Network Entity Config tab pops up.
2. On the CS Network Entity Config tab, select the corresponding variables, and click
on the sub-toolbar to enter the editing status. Select the corresponding options, as
shown in Figure 1-2.
l Filling Rule of MSC Number or VLR Number in MAP/CAP Dialog Message:
choose Fill MSCNum/VLRNum Corresponding to GCI/LAI.
l Filling Rule of GT in MAP/CAP Dialog Initial Message: same as above
1-15
Data Configuration
The related operations of the roaming data configuration are as follows.
3 Creating a mobile network ID and area Configure the relationship ADD NCCFG
code mapping between a mobile network
ID and a area code
to judge whether a
subscribers is roaming
Prerequisites
Before the operation, it is required to confirm:
1-16
Context
IMSI number analysis is used to convert the IMSI number to a number that can address
the HLR. The VLRMAP performs GT translation through this number to address the HLR
where the IMSI is registered. Create IMSI number analysis according to the roaming data
provided by operators, usually configuring the local-network and international roaming
data.
Background
In IMSI number analysis, it is required to set the “home destination code type”, which can
be “ISDN” or “HLR”.
1. ISDN
The corresponding number prefix in the IMSI is converted into the specified analysis
result, and the rest digits are added behind the analysis result. For example, if the
analyzed number is 46000, it is converted to 86139, the network-admitted IMSI number
is 460001234567890, the corresponding Country Code (CC) is 86, and the Network
Destination Code (NDC) is 139. In this mode, this IMSI number is analyzed into
861391234567890. Based on this, the typical application of this mode is to convert
the MCC+MNC in the IMSI into the CC+NDC, and keep the rest part, forming the E214
number format.
2. HLR
The corresponding number prefix in the IMSI is converted into the specified analysis
result, and the rest digits are deleted. For example, if the analyzed number is 46000,
it is converted to the GT number 8613903066 of the HLR, and the network-admitted
IMSI number is 460001234567890. In this mode, this IMSI number is analyzed to
8613903066, that is the GT number of the HLR. Based on this, the typical application
of this mode is to convert the IMSI headed by specific MCC+MNC into the GT number
of a HLR.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
The explanation of the main parameters in command ADD IMSIANA is shown in Table
1-5.
1-17
1-18
Example: Create the IMSI number analysis with the following requirements:
l Prefix: 46000
l Home destination code: 86139
l Home destination code type: ISDN
l Other parameters: Adopt default values.
The command is:
ADD IMSIANA: IMSI= "46000", HDSTCODE= "86139", HDSTCODET= ISDN, INDAD
C= NO, SM= 0, OPID= 0;
– End of Steps –
Abstract
This section introduces how to configure the relationship between a mobile service access
number and an MNC for inter-network roaming.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create the relationship between a mobile service access number and an MNC by
executing command ADD NDCMNC.
The explanation of the main parameters in command ADD NDCMNC is shown in Table
1-6.
1-19
NDC National destination code It indicates the mobile digital service access
number. Enter it according to the actual
condition
Example: Create the relationship between a mobile service access number and a
MNC with the following requirements.
l Access number configuration ID: 1
l CC: 86
l Mobile service access number: 139
l MCC: 460
l MNC: 00.
The command is:
ADD NDCMNC: ID= 1, CC= "86", NDC= "139", MCC= "460", MNC= "00";
– End of Steps –
Abstract
This section introduces how to configure the relationship between a mobile network ID and
a area code to judge whether a subscribers is roaming.
Prerequisites
Before the operation, it is required to confirm:
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 MSCS exchange with ID as 11 from the system tree.
1-20
2. Create the relationship between a mobile network ID and an area code by executing
command ADD NCCFG.
The explanation of the main parameters in command ADD NCCFG is shown in Table
1-7.
Example: Create the relationship between a mobile network ID and an area code with
the following requirements.
l Mobile Subscriber Identification Number: 1234
l Area code: 755.
The command is:
ADD NCCFG: MSIN= "1234", ACODE= "755";
– End of Steps –
Note:
These parameters are closely related to safety policy of the customer so you need to set
them as required. The configurations below are for your reference. For 2G access, you
need to set authentication and encryption parameters in Access Configuration > Mobility
Management. For 3G access, you need to set authentication, encryption and integrity
protection parameters in Access Configuration > Mobility Management.
1-21
Configuration Flow
4 Creating IMEI request Create IMEI request policy for ADD IMEIREQ
policy services
Abstract
Set encryption algorithm for 2G and set encryption and integrity protection algorithms for
3G.
Prerequisites
Before the operation, it is required to confirm:
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
1-22
1-23
1-24
1-25
Abstract
This topics describes how to modify authentication policy.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Modify authentication policy, the command is SET AUTHP.
The explanation of the main parameters in command SET AUTHP is shown in Table
1-9.
1-26
1-27
1-28
1-29
Abstract
When TMSI reallocation is enabled, the TMSI reallocation process includes encryption
process, and Kc(2G) or Ck(3G) is necessary for encryption process.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Modify TMSI reallocation policy, the command is SET TMSI.
The explanation of the main parameters in command SET TMSI is shown in Table
1-10.
1-30
1-31
1-32
1-33
Abstract
This topic describes how to create IMEI request policy.
Normally, configure not to obtain IMEI in all conditions.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
Table 1-11 describes the main parameters in the ADD IMEIREQ command.
1-34
ANATYPE Analysis Type, including: For the same VMSC, the matching
l ImsiPrefix: IMSI prefix of IMSI prefixes and roaming
l RoamType: roaming type types can be set at the same time.
The matching of IMSI prefixes has
a higher priority. The matching of
IMSI prefixes supports left match
and long match. For example,
when 420 and the 42003 prefix
are set at the same time, the
IMSI 4200388261624 matches
the record whose IMSI prefix is
42003.
1-35
SSRF Call Independent SS Ratio (1/n) This parameter is optional and its
value is an integer from 0 to 255.
The value 0 indicates that no IMEI
is requested for this access type.
REESTABRF Call Re-establishment Ratio (1/n) This parameter is optional and its
value is an integer from 0 to 255.
The value 0 indicates that no IMEI
is requested for this access type.
1-36
LUPERIODICRF Periodic LU Ratio (1/n), including: This parameter is optional and its
l NO: An IMEI is not obtained value is of enumeration type.
for a greylist.
l YES: An IMEI is obtained for
an unknown user.
LUATTACH Get IMEI at IMSI Attach, including: This parameter is optional and its
l NO: An IMEI is not obtained value is of enumeration type.
for a greylist.
l YES: An IMEI is obtained for
an unknown user.
LUFIRSTREG Get IMEI At First Register, This parameter is optional and its
including: value is of enumeration type.
l NO: An IMEI is not forcibly
obtained when the IMEI is
invalid. IMEIs are obtained
by ratio according to service
types.
l YES: An IMEI is always
obtained when the IMEI is
invalid.
INVADIMEI Get IMEI when IMEI invalid, This parameter is optional and its
including: value is of enumeration type.
l NO: An IMEI is not forcibly
obtained when the IMEI is
invalid. IMEIs are obtained
by ratio according to service
types.
l YES: An IMEI is always
obtained when the IMEI is
invalid.
BLACKPLC Get IMEI for Black List, including: This parameter is optional and its
l NO: An IMEI is not obtained value is of enumeration type.
for a blacklist.
l YES: An IMEI is obtained for
a blacklist.
1-37
GREYPLC Get IMEI For Grey List, including: This parameter is optional and its
l NO: An IMEI is not obtained value is of enumeration type.
for a greylist.
l YES: An IMEI is obtained for
a greylist.
UNKPLC Get IMEI for Unknown User, This parameter is optional and its
including: value is of enumeration type.
l NO: An IMEI is not obtained
for an unknown user.
l YES: An IMEI is obtained for
an unknown user.
IMEISVFLPLC Policy of Obtain IMEISV Fail, This parameter is optional and its
including: value is of enumeration type.
l REL: Release the process.
l IGN: Ignore it.
l RETRY: Continue to obtain
an IMEI only.
l CHKRETRY: Have a retry if
IMEI checking is required.
Otherwise, ignore it.
IMEIFLPLC Policy Of Obtain IMEI Fail, This parameter is optional and its
including: value is of enumeration type.
l REL: Release the process.
l IGN: Ignore it.
– End of Steps –
1-38
Abstract
For 2G and 3G access, set paging parameters in Access Configuration > Mobility
Management.
If second paging is enabled, set Whether to enable Retry Page with IMSI in place
of TMSI as YES in Security Variable > WCN Security Variable > CS Network Entity
Config, which means using TMSI for the first paging and IMSI for the second paging.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Modify page policy, the command is SET PAGE.
The explanation of the main parameters in command SET PAGE is shown in Table
1-12.
PAGECNT Resending times of paging This parameter indicates the number of times
message for resending a paging message. The value of
this parameter is an integer from 0 to 2. Set
it as 1 if you need to enable second paging.
Otherwise, set it as 0.
1-39
PAGETIMER Page response timer (s) This parameter indicates the duration for
waiting for a paging response. The value of
this parameter is an integer from 0 to 255. If
a paging message (including Search) does
not need to be resent, the MSC sets the page
response timer to twice of this duration.
Prerequisites
The GT data configuration is completed.
Context
This topic introduces the CS security parameters configuration related to encryption and
authentication.
1-40
Steps
1. On the NetNumen M30 window, select Views > Professional Maintenance > MSCS
> Security Variable > WCN Security Variable > CS Security Parameter. The CS
Security Parameter tab pops up.
2. On the CS Security Parameter tab, select the corresponding parameters, and click
on the sub-toolbar to enter the editing status, as shown in Figure 1-3.
l Whether to request IMSI when MS access with unknown TMSI: choose YES.
l Whether to get IMSI from MS when Authentication fails using TMSI: choose
YES.
l Num of Auth Vectors Kept: after the current authentication is completed, initiate
the flow to get authentication parameters from HLR if number of authentication
sets left is lower than the value. Recommended value is 1.
Abstract
This topic introduces the CS Network Entity Config parameter configuration related to
encryption and authentication.
1-41
Prerequisites
The GT data configuration is completed.
Steps
1. On the NetNumen M30 window, select Views > Professional Maintenance >
MSCS > Security Variable > WCN Security Variable > CS Network Entity Config
Parameter. The CS Network Entity Config Parameter tab pops up.
2. On the CS Network Entity Config tab, select Number of Authentication Vectors,
and click on the sub-toolbar to enter the editing status. Enter the value as 5, as
shown in Figure 1-4.
1-42
Prerequisites
l The interconnection configuration between MSCS and local HLR is completed.
l The interconnection configuration between MSCS and BSC/RNC is completed.
Steps
1. Prepare for the debugging.
l The HLR office direction is reachable and sub-system state is normal.
l The office direction between MSCS and BSC/RNC is reachable.
l The LA and cell configuration is completed.
2. Check state.
a. Check if office directions between MSCS and HLR and between MSCS and
BSC/RNC are reachable.
Check office direction state through signaling options of Dynamic Management.
b. Check sub-system status of HLR and BSC/RNC office directions is normal.
3. Open Signaling Trace and Failure Observer, switch on handset, choose network,
log in and perform LU debugging.
l Signaling Trace: Track with IMSI or MSISDN of subscriber , select BSSAP,
RANAP, and MAP, then start.
l Failure Observer: Trace failure observation of MSCS and SCCP.
– End of Steps –
1-43
Data Configuration
The related operations of the number analysis configuration are as follows.
3 Setting the default DAS Set the default DAS SET LDASTMPLT
template of the local office template of the local office
means creating the DAS
used for local-office service
processing.
5 Creating the called numbers Create number analysis for ADD TPDNAL
analysis prefixes of called numbers
and roaming numbers
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
1-44
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 1-5.
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 1-13.
New service 10193 + 0 + local area code If call restriction is required, analyze
number analyzer it to “pre-analysis ending, and call
rejected”
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
1-45
2. Originating DAS: used to analyze the called number in the local-office-originated call,
as shown in Table 1-14.
New service Charging query number Analyze it to the SSP charging query
number analyzer service
Short number -
1-46
3. Forwarding DAS: used to analyze the number to which the call is forwarded, as shown
in Table 1-15.
1-47
4. Roaming DAS: used to analyze the roaming number in the response message to
the routing information query message, as shown in Table 1-16. It is unnecessary
to analysis the CC in national roaming numbers.
Abstract
Creating number analyzer entries means specifying an ID for each type of number
analyzers.
1-48
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The number analyzer entry range is set in resource configuration.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET in the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
1-49
– End of Steps –
1-50
Abstract
The DAS is the collection of various number analyzer entries, specifying the order and rule
of performing number analysis.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The DAS range is set in resource configuration.
l The number analyzer entry is configured.
l The MML Terminal window is opened.
Context
Table 1-19 lists common DASs.
PBRT Personal Back Ring Tone Used for the PBRT function.
Steps
1. If no office is specified, execute command SET in the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create a DAS by executing command ADD DAS.
The explanation of the main parameters in command ADD DAS is shown in Table 1-20.
1-51
NEWSRV New service number analyzer entry Enter the umber analyzer entry IDs
contained by a DAS.
CENTR CENTREX number analyzer entry
Abstract
Creating the default DAS template of the local office means creating the DAS used for
local-office service processing.
Prerequisites
Before the operation, it is required to confirm:
1-52
Steps
1. If no office is specified, execute command SET in the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Set the default DAS template of the local office by executing command SET LDAST
MPLT.
The explanation of the main parameters in command SET LDASTMPLT is shown in
Table 1-21.
1-53
1-54
Example: Configure the default DAS template of the local office with the following
requirements.
l MS originating DAS: 101
l MSRN DAS: 201
l Forwarding DAS: 301.
The command is:
1-55
Abstract
It is required to create multiple DAS templates in the dual-homing or regional networking.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET in the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create a DAS template by executing command ADD ACRTMPLT.
The explanation of the main parameters in command ADD ACRTMPLT is shown in
Table 1-22.
1-56
1-57
Abstract
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.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The number analyzer entry is configured.
l The MML Terminal window is opened.
1-58
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create called number analysis, the command is ADD TPDNAL.
The explanation of the main parameters in command ADD TPDNAL is shown in Table
1-23.
1-59
SPECRST Special analysis result It is used to specify the index number of the
rule 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.
SPECIDX Special analysis result It is used to specify the index number of the special
index 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.
1-60
RST1 Number analysis result l When the call service type is vacant number,
1 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.
l 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.
l 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.
l 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.
l When the call service type is MNP outgoing
routing number analysis result 1 is used to
1-61
1-62
CHAINAL Route chanin analysis It is used to specify the analysis index number of
index 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.
BACKCHAINAL Backup chain set It is used to specify the analysis index number of
the route chain. This parameter must be defined
by command ADD CHAINAL at first.
RNLEN Length of the carried When the call service type is MNP outgoing
routing number 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.
1-63
1-64
service based on
OVERLAY at first,
and then trigger
the intelligent
service again
based on CSI
1-65
1-66
l ISUP_BICC_0
X08 ISUP&BICC
0X08
l ISUP_BICC_0
X7E ISUP&BICC
0X7E
TIMELMT Maximum call duration It is used to specify the maximum call duration
(minute) 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.
DDCPLAY Whether to play the It is used to specify whether to play the DDC tone
DDC tone, including: in the local office. The system adopts NONE by
l NONE (Not default. The purpose of configuring whether to play
playing the DDC the DDC tone in the number analysis configuration
tone): It is not is to avoid no tone play or repeated tone play
required to play caused by inconsistent tone play configuration
the DDC tone in during inter-office DDC calls.
the local office.
l PLAY (Playing the
DDC tone): It is
required to play
the DDC tone in
the local office.
1-67
CALLSERVPRIL- Call type priority, It is used to specify the call priority. The system
VL including: adopts INVALID by default. The call priority has
l INVALID: The call two functions. In one case, in the softswitch office
priority is invalid. in the toll softswitch network, the voice coding
l HIGHEST: The format can be dynamically selected according
call has the to the call priority and the load on the IP bearer
highest priority. network. In another case, based on the combined
l HIGHER: The information of office ID and priority configured in
call has a priority the number analysis configuration, the final priority
one level lower of a call is got to perform load control.
than the highest
priority.
l NORMAL: The
call has a priority
one level lower
than the higher
priority.
l LOW: The call has
the lowest priority
1-68
IP IP Fixed Service
1-69
HONET HONET_G
1-70
Example: Configure the called number analysis with the following requirements.
l Analyzer entry: 1
l Analyzed number: 13901234
l Call service type: MSC common service
l Other parameters: Adopt the default values.
The command is:
Example: Configure the roaming number analysis of the local office with the following
requirements.
l Analyzer entry: 1
l Analyzed number: 115901234
l Call service type: MSC local service
l Other parameters: Adopt the default values.
1-71
Abstract
Number change index configures the basic number change method for number analysis.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The number analysis selector and called number analysis configuration is completed.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create number transform index, the command is ADD DDI.
The explanation of the main parameters in command ADD DDI is shown in Table 1-26.
1-72
MTHD Number Transform Mode, including: This parameter is mandatory and its
l ADD: Add Number value is of enumeration type.
l DEL: Delete Number
l OVR: Modify Number
l REP: Replace
l ORG: No Transform_G
l HCODE: H Code Transform
l PRO: Only Transform Address
Nature
OFFSET Start Position Of The Number This parameter specifies the start
position of number change. Its value
is an integer ranging from 0 to 48.
LENGTH Deleted Or Modified Number Length This parameter specifies the length
of the number to be deleted or
modified. Its value is an integer
ranging from 0 to 48.
NEWNAT New Address Nature, including: This parameter is optional and its
l DEF: Default attribute value is of enumeration type.
l INT: International number
l NAT: Domestic number
l LOC: Local number
l UNK: Attribute unknown
Example: create number transform index, add 0086 in front of the first digit of the
number. The command is:
ADD DDI: DDI= 1, MTHD= ADD, OFFSET= 1, LENGTH= 0, DN= "0086", NEWNAT=
DEF, PI= PASS, IC= PASS, NEWTYPE= 0;
1-73
Example: create number transform index, delete the two digits of number starting from
the first digit. The command is:
ADD DDI: DDI= 2, MTHD= DEL, OFFSET= 1, LENGTH= 2, NEWNAT= DEF, PI= PA
SS, IC= PASS, NEWTYPE= 0;
Example: create number transform index, change the three digits of number starting
from the first digit as 0086. The command is:
ADD DDI: DDI= 3, MTHD= MOD, OFFSET= 1, LENGTH= 3, DN= "0086", NEWNAT=
DEF, PI= PASS, IC= PASS, NEWTYPE= 0;
Example: create number transform index, replace the number with 0086. The
command is:
ADD DDI: DDI= 4, MTHD= REP, OFFSET= 1, LENGTH= 0, DN= "0086", NEWNAT=
DEF, PI= PASS, IC= PASS, NEWTYPE= 0;
Tip:
Number attribute change can be used seperately or together with number adding,
deleting, modifying and substitution.
Example: create number transform index the number transorm mode is original
No-change works only in CDR number change. The command is:
ADD DDI: DDI= 6, MTHD= ORIGINAL, OFFSET= 1, LENGTH= 0, NEWNAT= DEF,
PI= PASS, IC= , NEWTYPE= 0PASS;
– End of Steps –
1-74
Context
This function is used to configure a mobile number prefix. The system determines whether
a number is a mobile number or not based on the number prefix. When the system collates
number formats, organizes number address attributes or judges the validity of a dialing
method, the system may need to know whether a number is a mobile number or not. Then,
this function is helpful.
The international format of a fixed number is country code + area code + subscriber
number and the international format of a mobile number is country code + mobile
subscriber number. When the system collates numbers in international format, it needs
to analyze whether the number is a fixed number or a mobile number. Then, the system
can handle the area code correctly.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create mobile number prefix, the command is ADD MCODE.
The explanation of the main parameters in command ADD MCODE is shown in Table
1-27.
CODE MSISDN Prefix Mobile number prefix. The value of this parameter is
a string consisting of 1 to 10, *, #, D and E.
– End of Steps –
1-75
Prerequisites
Before the operation, it is required to confirm:
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
1-76
CLEDTYPE Called User Type, including: This parameter is optional and its
l LOCMB: LAN value is of enumeration type.
l OTHMB: Other Mobile
l LOCFIX: Local Fixed
l OTHFIX: Other Fixed
l INTL: International
l UN: Unknown
l INTROAM: International
Roam
l ALL: All
1-77
l NO_NDC_NAT_NAT: No
NDC,national prefix,Number
attribute is national
l NO_NDC_NAT_UNKN: No
NDC,national prefix,Number
attribute is unknown
l DEFOPDN: Default calling
number
l DEFOPDN_INTL:
International format Default
calling number
l ONHC_No_INTPREFIX:
ONHC, INT Format Number
With Prefix
l ONHC_With_INTPREFIX:
ONHC, INT Format Number
With Prefix
1-78
Example: create number transform for CLIP with the following requirements:
l Calling User Type: LAN
l Called User Type: All
l Alias: OPNUMTRFDSP_LOCMB
l Calling Number Format: national prefix, number attribute is unknown
l Other parameters: default.
The command is:
ADD OPNUMTRFDSP: CLINGTYPE= LOCMB, CLEDTYPE= ALL, NAME= "OPNUMT
RFDSP_LOCMB", NUMCHG= NAT_UNKN, SI= PASS, PI= PASS, IC= PASS, NPI= PASS,
TRFAS= 0;
– End of Steps –
Abstract
This topic introduces the security variable configuration for adding international prefix to
national calls.
Prerequisites
l The office ID to be configured is given.
l The data configuration is completed.
Steps
1. On the NetNumen M30 window, select Views > Professional Maintenance > MSCS
> Security Variable > WCN Security Variable > CS Security Parameter. The CS
Security Parameter tab pops up.
2. On the CS Security Parameter tab, select Whether to delete home MCC where
analysis the MSISDN, and click on the sub-toolbar to enter the editing status, select
YES, as shown in Figure 1-6.
1-79
Abstract
This topic introduces the System Control configuration related to MSISDN length.
You must examine the Length of MSISDN before increasing in international offices and
make sure the value is correct. Otherwise, MT fails.
Prerequisites
l The office ID to be configured is given.
l The data configuration is completed.
Steps
1. In the NetNumen M30 window, select Views > Professional Maintenance > MSCS
> Security Variable > WCN Security Variable > System Control. The System
Control tab pops up.
2. On the System Control tab, select the corresponding parameters, and click on the
sub-toolbar to enter the editing status, as shown in Figure 1-7.
l Phone number upgrading status setting: choose After upgrade.
l Length of MSISDN before increasing: enter 11.
1-80
Prerequisites
l Signaling interconnection debugging is completed.
l Location update debugging is completed.
l Call data configuration is completed.
Steps
1. Make preparations for debugging.
l MS LU succeeds.
1-81
3. Open Signaling Trace and Failure Observer, make interior calls and debug
according to the signaling and call losses.
l Signaling Trace: Open user signal tracing, open SCCP signaling tracing in MTP3
signaling tracing to HLR and open SCCP signaling tracing in MTP3 signaling
tracing to BSC/RNC.
l Failure Observer: Track failure observation of MSCS and SCCP.
– End of Steps –
You need to configure PCM allocation and VTCD load-sharing for RTP/RTCP at MGW.
You need to configure trunk groups, trunk group tags, PCM system,inter-MGW PCMs,
outgoing routes, outgoing route groups and outgoing route links at MSCS.
Inter-office calls data configuration and debugging flow is as follows:
1. Trunk data configuration, refer to 1.3.1 Trunk Data Configuration.
2. Routing data configuration, refer to 1.3.2 Routing Data Configuration.
3. Timers configuration, refer to 1.3.3 Modifying Pre-defined Timer.
4. Inter-office calls debugging, refer to 1.3.4 Debugging Inter-office Calls.
1-82
2 Creating a PCM system DT, ATM, RTP, and RTP ADD SPCM
trunk groups all need to be
created with PCM systems
Abstract
When the A interface or Ai interface adopts the TDM bearer, or when 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 to configure multiple trunk groups to each BSC office (4~8 trunk
groups are recommended). To implement load sharing, it is required to allocate roughly
the same number of BSC circuits to each CMP module.
Prerequisites
Before the operation, it is required to confirm:
1-83
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office 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
1-29.
NODE Node No. of the MGW where the It is a mandatory parameter. Select
trunk group belongs the MGW topology node connected
with the 2G MSC/PSTN node.
1-84
1-85
OPDAS 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.
1-86
PREDAS DAS for pre-analyzing the called It is used to pre-analyze the called
number number in an incoming call. This
parameter must be defined by
command ADD PREDAS at first.
Then it can be indexed here.
1-87
Example: Create a DT trunk group to the 2GMSC/PSTN office with the following
requirements:
l Trunk group ID: 28
l ID of the office where the trunk group belongs: 28
l MGW topology node No.: 101
l Line signaling flag: ISUP
l No. of the CMP module where the trunk group belongs: 7
l Method Of Circuit Selection: ODD
l Other parameters: Adopt the default values.
The command is:
1-88
ADD TG DT: TG= 28, OFC= 28, NODE= 101, MODULE= 7, LINE= ISUP, VDT= FALSE,
KIND= BIDIR, INREG= INVALID, OUTREG= INVALID, TPDAS= 0, OPDAS= 0, ROA
MDAS= 0, PREDAS= 0, TPINDAS= 0, OPINDAS= 0, TPOUTDAS= 0, OPOUTDAS=
0, PLSCLDDAS= 0, PLSCLRDAS= 0, BEARWAY= NODIR, CICSEL= ODD, GATE=
100, SMENTERID= 0, EQUC1= FALSE, ACCL1= 100, EQUC2= FALSE, ACCL2= 100,
HOPCUN= 20, CASOPLEN= 10, VMSCIDX= 0, BUSYRATE= 100, FAILCONVIDX=
0, DISINDEX= 0, MLPPDM= 4294967295, SUPERCLIINDEX= 0, AIFTCRES= "GSM-
FR"&"GSM HR"&"GSM-EFR"&"FR-AMR"&"HR AMR"&"OFR AMR-WB"&"OHR AMR-W
B"&"FR AMR-WB"&"OHR AMR"&"CSD", MNPDAS= 0;
– End of Steps –
Abstract
When the PRA is adopted, create PRA trunk groups.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The trunk group No. range is set in resource configuration.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create a PRA trunk group by executing command ADD TG PRA.
The explanation of the main parameters in command ADD TG PRA is shown in Table
1-30.
1-89
NODE Node No. of the MGW where the It is a mandatory parameter. Select
trunk group belongs the MGW topology node connected
with the 2G MSC/PSTN node.
1-90
OPDAS 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.
PREDAS DAS for pre-analyzing the called It is used to pre-analyze the called
number number in an incoming call. This
parameter must be defined by
command ADD PREDAS at first.
Then it can be indexed here.
1-91
1-92
Abstract
When the ATM bearer is adopted between MGWs, create ATM trunk groups.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The trunk group No. range is set in the resource management system.
1-93
l The adjacent MGW office to which the trunk group points is created.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office 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
1-31.
NODE Node No. of the MGW where the It is a mandatory parameter. Select
trunk group belongs the MGW topology node connected
with the 2G MSC/PSTN node.
1-94
OPDAS 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.
1-95
PREDAS DAS for pre-analyzing the called It is used to pre-analyze the called
number number in an incoming call. This
parameter must be defined by
command ADD PREDAS at first.
Then it can be indexed here.
1-96
1-97
Abstract
When the IP bearer is adopted between MGWs, configure RTP trunk groups, which are
BICC trunk groups.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The adjacent MGW office to which the trunk group points is created.
l The trunk group No. range is set in the resource management system.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
The explanation of the main parameters in command ADD TG RTP is shown in Table
1-32.
1-98
1-99
OPDAS 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.
PREDAS DAS for pre-analyzing the called It is used to pre-analyze the called
number number in an incoming call. This
parameter must be defined by
command ADD PREDAS at first.
Then it can be indexed here.
1-100
1-101
1-102
Abstract
The PCM system management data associate the resources on the MGW with the
signaling on the MSCS.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The DT, ATM, or RTP trunk group is configured.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create a PCM system by executing command ADD SPCM.
The explanation of the main parameters in command ADD SPCM is shown in Table
1-33.
1-103
Example: Create a PCM system to the 2G MSC/PSTN office with the following
requirements:
l No. of the trunk group where the PCM system belongs: 28
l PCM system No.: 1
l PCM No. in the MGW: 7
The command is:
ADD SPCM: TG= 28, PCM= 1, MGWPCM= 7, INFO= 65535;
– End of Steps –
Abstract
When the MGWs managed by one MSCS are interconnected through TDM circuits, it
is required to configure the PCM systems between the MGWs. Since the MGWs are
1-104
interconnected within the MSCS, 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.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The bearer mode between the MGWs is configured in the topology configuration. .
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office 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
1-34.
1-105
Example: Add a PCM system between MGWs with the following requirements.
l Trunk group of inner MGW: 102
l Management module No.: 7
l PCM system No.: 1
l PCM No. in MGW1 and MGW2: 1
The command is:
ADD INPCM: INTG= 102, MODULE= 7, PCM= 1, LOCWPCM= 1, REMWPCM= 1;
– End of Steps –
Data Configuration
The related operations of the routing data configuration are as follows.
1-106
Abstract
Each trunk group corresponds to an outgoing route.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The outgoing route No. range is set in resource configuration.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET in the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Create an outgoing route by executing command ADD RT.
The explanation of the main parameters in command ADD RT is shown in Table 1-35.
1-107
ADD RT: RT= 28, TG= 28, METHOD= SeBySe, DLPFX= NO, RERT= 0, CLISETIDX=
65535, TPDASOUT= 0, OPDASOUT= 0;
– End of Steps –
Abstract
Each route belongs to a route group.
This topics introduces how to create an outgoing route group.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The outgoing route No. is added.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
1-108
RTINFO Route No. and load sharing It is an optional parameter. It is in the format
proportion list of “No.-Route No.-Load sharing proportion.
When the percentage is set to 0, the poll
mode is adopted.
l SEQ: No., which is the location of the
route in the route group.
l 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.
l 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
l CSTVAL: Route cost.
1-109
Abstract
Each outgoing route group belongs to an outgoing route chain, and each route chain
contains at most 8 route groups.
Prerequisites
Before the operation, it is required to confirm:
l The office ID to be configured is given.
l The outgoing route chain No. range is set in resource configuration.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET in the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
RTS1 Direct route set number, used It is an mandatory parameter. Type the
to set the route group with the direct route set number.
highest priority in a route chain
during routing
1-110
RTS2 No. of route group 2, used to set It is an optional parameter. Select route
the route group with the level-2 groups according to the priority order.
priority in a route chain during
routing. One route chain can be
configured with at most 4 route
groups
1-111
Prerequisites
Before the operation, it is required to confirm:
1-112
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. Modify pre-defined timer, the command is SET DEFPRETMR.
The explanation of the main parameters in command SET DEFPRETMR is shown in
Table 1-38.
Prerequisites
l Signaling interconnection debugging is completed.
l Location update debugging is completed.
1-113
Steps
1. Make preparations for debugging.
Note:
– End of Steps –
1-114
2.1 Overview
Billing configuration includes:
l CU office configuration
l MSCS billing parameters configuration
l ZXWN CU billing server configuration
The billing configuration and debugging flow is as follows:
1. CU office and bill server module configuration, refer to 2.2 CU Office Configuration.
2. On MSCS, need to set billing configuration, then CDR can be generated normally.
MSCS billing parameters configuration is as follows:
a. Charge parameter configuration, refer to 2.3.1 Setting Charge Parameter.
b. CS Network Entity Config configuration, refer to 2.3.2 Configuring CS Network
Entity Config Parameters.
c. NE-back server communication IP address configuration, refer to 2.3.3
Configuring an IP Address for Communication Between Foreground and
Background Subsystems.
Tip:
Before billing configuration, need to finish CU billing server commissioning.
2-1
Create the CU NE
corresponded by the
1 Creating a CU NE ADD NE
exchange on the
background OMM system.
2.2.1 Creating a CU NE
Abstract
Perform this procedure to create the CU NE corresponded by the exchange on the
background OMM system.
Prerequisites
Before the operation, it is required to confirm:
The MML Terminal window is opened.
Steps
1. Create a CU NE with the ADD NE command.
Table 2-1 describes the main parameters in the ADD NE command.
2-2
Result
After the command is executed successfully, the CU node is added under the root node in
the OMM client interface.
Prerequisites
Before the operation, it is required to confirm:
l You know the ID of the CU to be configured.
l The MML Terminal window is opened.
Steps
1. If no offcie is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the offcie to be configured.
Example: Select the CU with ID as 71 from the system tree.
2-3
MODULE Module No. of the charging server Indicates the module No. of the
charging server. The module No.
must be consistent with the module
No. that is set during the installation
of the charging server. It is a
mandatory parameter ranging from
130 to 135.
Configure variables
Configuring CS network
2 control configurations -
entity config parameters
related to charging.
2-4
Prerequisites
Before the operation, it is required to confirm:
l You know the ID of the MSCS to be configured.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS with ID as 11 from the system tree.
SET: NEID= 11;
TIMETHD Time threshold for call ticket (m) Partial CDR's time threshold (min).
It's value range is 5~60. Default
value is 30 min.
LONGTHD Time threshold for long call(m) long time supervise threshold(min).
It's value range is 0~2880. 0 means
this parameter is not useful.
2-5
2-6
ALMLTCALL Alarm time threshold for long call(m) It is an optional parameter, ranging
from 0 to 2,880.
2-7
2-8
Prerequisites
l The office ID to be configured is given.
l The MSCS charge parameter configuration is completed.
l The MML Terminal window is opened.
Steps
1. On the NetNumen M30 window, select Views > Professional Maintenance > MSCS
> Security Variable > WCN Security Variable > CS Network Entity Config. The CS
Network Entity Config tab pops up.
2. On the CS Network Entity Config tab, select the corresponding parameters, and click
on the sub-toolbar to enter the editing status, as shown in Figure 2-1.
l Whether to support PPS flag in SMS-MO CDR: whether to add prepaid flag
(PPS-FLAG)in prepaid user SMS-MO CDR, it is easier for billing center charging,
normally set as NO.
l Whether report call duration for ANN: whether to report call duration when
CAMEL users dial free call, when it set as NO: call duration in ACR will be 0
for free call answer; when it set as YES: report actual call duration in ACR for free
call answer, suggest to set as YES.
– End of Steps –
2-9
Prerequisites
Before you begin, make sure that:
l The ID of the office to be configured is known.
l The physical configuration is completed.
l The MML Terminal window is opened.
Steps
1. If no office is specified, execute command SET on the MML Terminal window or select
a NE from the system tree to specify the office to be configured.
Example: Select the MSCS office with ID as 11 from the system tree.
SET: NEID= 11;
2. To configure an IP address for communication between the foreground and the
background subsystems, use the SET BKIP command.
Table 2-4 gives description of the parameters in the SET BKIP command.
MODULE Module number Type the CMP module number on the MSCS,
ranging from 2 to 511.
2-10
For example, set the IP address for communication between CMP 7 and the IP address
is 172.11.32.7, the subnet mask is 255.255.240.0, and the port is the control plane port.
The command is:
SET BKIP: MODULE= 7, MODULENAME= "CMP7", PORT= CTRL, IP= "172.11.32.7";
– End of Steps –
2-11
2-12
I
Figures
III
ZXWN MSCS Data Configuration Guide (MSCS II)
IV
Index
D
Destination signaling point.................... 1-2
G
GT routing ............................................ 1-2
GT translation data............................... 1-3
GT translation selector ......................... 1-3
S
SCCP................................................... 1-1
Source signaling point .......................... 1-2
V
Index
VII