SJ-20101208143956-014-ZXWN MSCS (V4.10.13) MSC Server Security Variable Reference

ZXWN MSCS
MSC Server
Security Variable Reference
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 © 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 2011-2-28 First edition
Serial Number: SJ-20101208143956-014
Publishing Date: 2011-2-28(R1.0)

Contents
About This Manual ........................................................................................................... I
Declaration of RoHS Compliance.................................................................................. I
Chapter 1 Overview......................................................................................................1-1
1.1 Introduction to Security Variables .................................................................. 1-1
1.2 Modifying Security Variables.......................................................................... 1-2
Chapter 2 Common Security Variables....................................................................2-1

2.1 Security Control Variable ............................................................................... 2-1
2.1.1 Maximum Call Diversion Times............................................................................2-3
2.1.2 Whether to Support Larger-Than-Limit Forward Times in Signaling Codec .........2-4
2.1.3 DualHome Heartbeat Interval ..............................................................................2-4
2.1.4 DualHome Heartbeat Try Times...........................................................................2-5
2.1.5 Whether to Delete VLR Data After Switching.......................................................2-5
2.1.6 Whether to Delete VLR Data in Appointed Time ..................................................2-6
2.1.7 Show Original and Modified Sig Message ...........................................................2-6
2.1.8 Whether to Use IP Load Control When the Call Is SIP Outgoing Call..................2-7
2.1.9 Whether to Support Incoming IP Test Call ...........................................................2-7
2.1.10 The Type of Test Termination of IP Load Control Test Call.................................2-8
2.1.11 The Reference Value of Delay for 100 ...............................................................2-8
2.1.12 The Reference Value of Delay for 60 .................................................................2-9
2.1.13 The Reference Value of Lost for 100 ............................................................... 2-11
2.1.14 The Reference Value of Lost for 60 .................................................................2-12
2.1.15 The Reference Value of Jitter for 100 ..............................................................2-13
2.1.16 The Reference Value of Jitter for 60 ................................................................2-15
2.1.17 The Weight for Delay .......................................................................................2-16
2.1.18 The Weight for Lost..........................................................................................2-17

2.1.19 The Weight for Jitter.........................................................................................2-18
2.1.20 The Reference Value of Congest Lever 1 ........................................................2-20
2.1.21 The Reference Value of Congest Lever 2 ........................................................2-21
2.1.22 The Reference Value of Congest Level 3 ........................................................2-22
2.1.25 The Step of Normal Level ................................................................................2-25
2.1.26 The Step of Congestion Level 1.......................................................................2-26
2.1.31 The Hour of Time for Counter Check ...............................................................2-31
2.1.32 The Minute of Time for Counter Check ............................................................2-32
2.1.33 Support User Level in IP_LoadCtrl Function....................................................2-33
2.1.34 The Percent of Call Number for the High Level Subscribers Having Priority to Use
the IP Bearer...............................................................................................................2-34
2.1.35 Whether the Cycle of Send Circuit (Group) Message or CCR Message..........2-34
2.1.36 The Upper Limit of National Number Length....................................................2-35
2.1.37 The Upper Limit of Subscriber Number Length................................................2-36
2.1.38 Whether the Fail Announce Counted in Call Completed Ratio.........................2-37
2.1.39 Support Calling subscriber's Category Conversion for Outgoing Signaling .....2-37
2.1.40 WCDMA Network Type ....................................................................................2-38
2.1.41 Forbid Calling Number in Outgoing Signaling ..................................................2-38
2.1.42 The Flag of Whether Record the Status of Blocked CIC by Local Operator to Disk
....................................................................................................................................2-39
2.1.43 Whether to Hold OMC Operate CIC Block State Allowed ................................2-39
2.1.44 The Indication of NNI Process When Nature of Calling Number Is Unknown ..2-40
2.1.45 Whether COT is Expected ...............................................................................2-40
2.1.46 IWF Description Type in SDP ..........................................................................2-42
2.1.47 Speed Variable of GRS Sent............................................................................2-43

2.1.48 Event Indicator Parameter Mode .....................................................................2-44
2.1.49 Allow Scan NNI Data........................................................................................2-45
2.1.50 Support Modify Caller Number Totally for Inter-Office DDI...............................2-45
2.1.51 Whether ACM with Wait Indicator or Not..........................................................2-46
2.1.52 Transmit Unknown Parameter in ISUP ............................................................2-46
2.1.53 Which DTone Signal Need to Detect................................................................2-47
2.1.54 Ratio between Max-Forwards and Hop Counter..............................................2-48
2.2 Service Control Function Set ....................................................................... 2-48
2.2.1 Need Terminal for SIP in and SIP Out................................................................2-49
2.2.2 Support Routing by Dialed Number Length .......................................................2-49
2.2.3 Not Pass Through Signal's Free Charge Indication ...........................................2-50
2.2.4 Control Countering of Answer Times .................................................................2-51
2.2.5 Use Satellite Circuit for ISUP .............................................................................2-51
2.2.6 Support Routing by Calling Number ..................................................................2-52
2.2.7 Priority to Use T38 Fax ......................................................................................2-52
2.2.8 Continue to Detect DTone After CED Is Detected..............................................2-53
2.2.9 VAD Controlled When Alerting ...........................................................................2-53
2.2.10 Incoming Toll End Call Request Caller Category When it is Unknown.............2-54
2.3 Other Variables ............................................................................................ 2-54
2.3.1 Max Count of Message to OMC.........................................................................2-56
2.3.2 Alarm Count of Message to OMC ......................................................................2-57
2.3.3 Open MGW User Trace Function.......................................................................2-58
2.3.4 Allowed Fail Count Every 10 Heart Beat of Dual Home .....................................2-58
2.3.5 Traffic Control ....................................................................................................2-59
2.3.6 Traffic Control's Priority......................................................................................2-59
2.3.7 Call Service Control Number Type.....................................................................2-60
2.3.8 The Length of Called Number in Sending ..........................................................2-60
2.3.9 Equivalent CPU of Location Update ..................................................................2-60
2.3.10 Equivalent CPU of Authentication ....................................................................2-61
2.3.11 Equivalent CPU of SMS(MO)...........................................................................2-61
2.3.12 Equivalent CPU of SMS(MT) ...........................................................................2-62

2.3.13 Equivalent CPU of 2G Normal Call (MO) .........................................................2-62
2.3.14 Equivalent CPU of 2G Normal Call (MT) .........................................................2-63
2.3.15 Equivalent CPU of 3G Normal Call (MO) .........................................................2-63
2.3.16 Equivalent CPU of 3G Normal Call (MT) .........................................................2-64
2.3.17 Equivalent CPU of GMSC................................................................................2-64
2.3.18 Equivalent CPU of SMS (CAMEL) ...................................................................2-65
2.3.19 Equivalent CPU of Call (CAMEL).....................................................................2-65
2.3.20 Equivalent CPU of ISUP/TUP Incoming...........................................................2-65
2.3.21 Equivalent CPU of ISUP/TUP Outgoing...........................................................2-66
2.3.22 Equivalent CPU of BICC (CMN) Incoming .......................................................2-66
2.3.23 Equivalent CPU of BICC(CMN) Outgoing ........................................................2-67
2.3.24 Equivalent CPU of BICC (TSN) Incoming ........................................................2-67
2.3.25 Equivalent CPU of BICC (TSN) Outgoing ........................................................2-68
2.3.26 Equivalent CPU of SIP Incoming .....................................................................2-68
2.3.27 Equivalent CPU of SIP Outgoing .....................................................................2-69
2.3.28 Equivalent CPU of CAS Incoming....................................................................2-69
2.3.29 Equivalent CPU of CAS Outgoing....................................................................2-69
2.3.30 Equivalent CPU of PRI Incoming .....................................................................2-70
2.3.31 Equivalent CPU of PRI Outgoing .....................................................................2-70
2.3.32 Equivalent CPU of VIG Incoming.....................................................................2-71
2.3.33 Equivalent CPU of VIG Outgoing.....................................................................2-71
2.3.34 Equivalent CPU of HO Intra .............................................................................2-72
2.3.35 Equivalent CPU of HO Out ..............................................................................2-72
2.3.36 Equivalent CPU of HO In .................................................................................2-72
2.3.37 Equivalent CPU of BSSAP Service Request ...................................................2-73
2.3.38 Equivalent CPU of BSSAP Location Update....................................................2-73
2.3.39 Equivalent CPU of BSSAP HO ........................................................................2-74
2.3.40 Equivalent CPU of BCBM ................................................................................2-74
2.3.41 Equivalent CPU of MCF...................................................................................2-75
2.3.42 Equivalent CPU of USSD.................................................................................2-75
2.3.43 Equivalent CPU of LCS ...................................................................................2-76

2.3.44 Equivalent CPU of PBRT .................................................................................2-76
2.3.45 Equivalent CPU of Adding 2G MO Terminal.....................................................2-76
2.3.46 Equivalent CPU of Adding 2G MT Terminal .....................................................2-77
2.3.47 Equivalent CPU of Adding 2G HO Terminal .....................................................2-77
2.3.48 Equivalent CPU of Adding 3G HO Terminal .....................................................2-78
2.3.49 Equivalent CPU of Adding NNI Incoming Terminal ..........................................2-78
2.3.50 Equivalent CPU of Adding NNI Outgoing Terminal ..........................................2-79
2.3.51 Equivalent CPU of Adding NNI TDM Terminal .................................................2-79
2.3.52 Equivalent CPU of Adding 3G ATM MO Terminal.............................................2-80
2.3.53 Equivalent CPU of Adding 3G ATM MT Terminal .............................................2-80
2.3.54 Equivalent CPU of Adding 2/3G IP MO Terminal .............................................2-81
2.3.55 Equivalent CPU of Adding 2/3G IP MT Terminal ..............................................2-81
2.3.56 Max Congest Module Weighted Ratio..............................................................2-82
2.3.57 Local Office Congest Stat Interval (100 ms).....................................................2-82
2.3.58 Congesting Send Overload to RNC (BSC) Message Number .........................2-83
2.3.59 Congesting Send Overload to RNC (BSC) Minimum Level .............................2-83
2.3.60 MSC Reset Times............................................................................................2-83
2.3.61 MSC Reset Circuit Times.................................................................................2-84
2.3.62 Whether to Send Confusion Message .............................................................2-84
2.3.63 Whether Control Downlink Message According the Congest Level of

RNC/BSC/MGW .........................................................................................................2-85
2.3.64 Mc Number Trace for User Plane Tool Is Needed............................................2-85
2.3.65 Support SIP Message Edit...............................................................................2-86
2.3.66 Report SIP Edit Message.................................................................................2-86
2.3.67 Traffic Control Period .......................................................................................2-87
2.4 Other Function Set....................................................................................... 2-87
2.4.1 Not Handle the Clock Modification Notification Event for Call Service...............2-88
2.4.2 Play Change Number Tone for Other Bureau Forward Call ...............................2-88
2.4.3 Simplify the Control of EC Indication .................................................................2-89
2.4.4 Report Alert-Level Fail Information in Fail Observe ...........................................2-89
2.4.5 Support Auto Delete Dead Sub-Data Area.........................................................2-90

2.4.6 Include ReconnectB Traffic ................................................................................2-90
2.4.7 Support DNS/ENUM Function ...........................................................................2-91
2.4.8 DNS Cache Preload After TTL for the Records with High Hit Count Rate..........2-91
2.4.9 Cache Still in Valid After TTL..............................................................................2-92
2.5 License Function Set ................................................................................... 2-93
2.5.1 Support Failed Call Bill ......................................................................................2-94
2.5.2 Support Lawful Interception ...............................................................................2-94
2.5.3 Voice Service Turn to Fax Service .....................................................................2-94
2.5.4 Support MGCF...................................................................................................2-95
2.5.5 VAD Controlled by MSCe...................................................................................2-95
2.5.6 Black and White List Function............................................................................2-96
2.5.7 Authentication for Other Network User Function................................................2-96
2.5.8 Authentication for Trunk Group Function............................................................2-97
2.5.9 Support MLPP Service.......................................................................................2-97
2.5.10 Support Direct Message ..................................................................................2-98
2.5.11 Support MSC Pool ...........................................................................................2-98
2.5.12 Support BSC CIC Managed by MGW ..............................................................2-99
2.5.13 Support Dual Home .........................................................................................2-99
2.5.14 Support Rf Interface.......................................................................................2-100
2.5.15 Support VLR Dump........................................................................................2-100
2.5.16 Support AoIP..................................................................................................2-101
2.5.17 Support CMN .................................................................................................2-101
2.5.18 Support Iu Over IP .........................................................................................2-101
2.5.19 Whether to Use MAP Policing Flag................................................................2-102
2.5.20 Whether to Support Mobile Number Portable ................................................2-102
2.5.21 Whether to Support Category Route..............................................................2-103
2.5.22 Whether Support DTMF Limit for MT Calling Number ...................................2-103
2.5.23 Whether to Enable MAP OPC Function .........................................................2-104
2.5.24 Whether to Enable VLR CAMEL Roaming Function ......................................2-104
2.5.25 Ability of Prior Access ....................................................................................2-104
2.5.26 Whether to Enable Forced Release Call Function .........................................2-105

2.5.27 Whether to Play Announcement After Temporarily Disconnection .................2-106
2.5.28 Support ICS ...................................................................................................2-106
2.5.29 Whether to Support Suppression of Announcement when T-CSI ..................2-107
2.5.30 Support Fraud Profile Function ......................................................................2-107
2.5.31 Support Access Bearer Statistic Test .............................................................2-108
Chapter 3 WCN Security Variables............................................................................3-1

3.1 System Control Parameters........................................................................... 3-1
3.1.1 Phone Number Upgrading Status Setting ............................................................3-2
3.1.2 Length of MSISDN Before Increasing..................................................................3-3
3.1.3 Position for Insertion Value ..................................................................................3-4
3.1.4 Insertion Value on Increasing...............................................................................3-5
3.1.5 Send MAP Phase Setting ....................................................................................3-6
3.1.6 Receive MAP Phase Setting................................................................................3-7
3.1.7 TM Packet Size (Byte) .........................................................................................3-7
3.1.8 Duration of Call Gap Specified in Network (s)......................................................3-8
3.1.9 Whether to Use ATI Prior Flag .............................................................................3-8
3.1.10 Time Zone..........................................................................................................3-9
3.1.11 ATI Send Phase ...............................................................................................3-10
3.1.12 Whether to Use Call Forwarding OSB Check Control Switch ..........................3-10
3.1.13 Whether to Use Register Forwarding OSB Check Control Switch ................... 3-11
3.1.14 Interval of Force Location Update to HLR (Minute).......................................... 3-11
3.1.15 Version of TM...................................................................................................3-12
3.1.16 Whether to Enable Control Parameter of Location Reject Cause for CS.........3-12
3.1.17 Location Reject Cause for CS..........................................................................3-13
3.1.18 Roaming not Allowed in Cell Cause.................................................................3-13
3.1.19 Roaming not Allowed in LAI Cause..................................................................3-14
3.1.20 ARD Reject Cause in Same PLMN..................................................................3-15
3.1.21 ARD Reject Cause Not in Same PLMN ...........................................................3-16
3.1.22 Whether Cell Roaming Restrict Option is Enabled in LU Process ...................3-16
3.1.23 Whether Cell Roaming Restrict Option is Enabled when MO Processes ........3-17
3.1.24 Cause Value of Roaming Restrict by MSISDN ................................................3-17
3.1.25 Support Length Coding Type ...........................................................................3-18
3.1.26 Whether USSD Service Message Sent by CN Is Used Fixed Length Encode.3-18
3.1.27 Location Reject Cause About ODB Roam Not Allowed ...................................3-19
3.1.28 Whether to Enable Switch of the MSCNumber Coding in PSI-Rsp Msg..........3-20
3.1.29 Is Paid Special Service Under ODB Control ....................................................3-20
3.2 CS Security Parameter ................................................................................ 3-21
3.2.1 Whether to Request IMSI When MS Access With Unknown TMSI ....................3-21
3.2.2 Whether to Get IMSI From MS When Authentication Fails Using TMSI.............3-22
3.2.3 Num of Auth Vectors Kept..................................................................................3-22
3.2.4 Whether CODEC Is Accordance to the Control Switch......................................3-23
3.2.5 Whether to Delete Home MCC Where Analysis the MSISDN............................3-23
3.2.6 Choice of Service When Fallback for Outside Reason ......................................3-24
3.2.7 Whether H324M Is Allowed When NISU............................................................3-24
3.2.8 Whether SCUDIF Is Allowed for CAMEL2/3 User..............................................3-25
3.2.9 When MS Access Network With TMSI, Whether VLR Check MSÌMEI..............3-25
3.2.10 Do not Issued ClassMarkReq Instructions in LocationUpdate Process ...........3-26
3.2.11 Whether Replace IMEISV by IMEI when Obtain IMEISV from MS...................3-26
3.3 CS Network Entity Configuration ................................................................. 3-27
3.3.1 Whether to Support GPRS.................................................................................3-29
3.3.2 Whether to Support Multiple Bearer in Local MSC (CC) ....................................3-30
3.3.3 Whether to Support Long FTN...........................................................................3-30
3.3.4 Whether to Enable Sending Identification Operation Segmentation ..................3-31
3.3.5 Whether to Enable Sending AuthInfo Operation Segmentation .........................3-31
3.3.6 Whether to Enable Allowing Re-synchronous Case Authentication ...................3-32
3.3.7 Number of Authentication Vectors......................................................................3-32
3.3.8 Whether to Check Bear Capability When MSRN Is Supplied ............................3-33
3.3.9 The Times of Resend the CPData Message When MM Permit .........................3-33
3.3.10 SM Max. Packet Size.......................................................................................3-33
3.3.11 The Times of Resending the Alert Message.....................................................3-34
3.3.12 The Times of Resending the Reset Message ..................................................3-34

3.3.13 Whether to Support NSD Check ......................................................................3-35
3.3.14 Whether to Support Super-Charger .................................................................3-35
3.3.15 Whether to Limit 2G/3G User Access ..............................................................3-36
3.3.16 Whether to Limit Forwarding Long Distance or Not .........................................3-36
3.3.17 Whether Charge Is Needed When Camel Play Tone, the Mark Indicated........3-37
3.3.18 Location Report Control Type ..........................................................................3-37
3.3.19 Whether to Support Bengal Prepaid Subscriber SMS Charging ......................3-38
3.3.20 Whether HO Req Is Same as SIEMENS .........................................................3-38
3.3.21 Whether to Support Cater to GSM During Inter-Handover From UTRAN to GSM
....................................................................................................................................3-39
3.3.22 The Framework of MGW in an MSCS..............................................................3-39
3.3.23 Filling Rule of MSC Number or VLR Number in MAP/CAP Dialog Message ...3-40
3.3.24 Filling Rule of GT in MAP/CAP Dialog Initial Message ....................................3-41
3.3.25 SMMT Fail Cause Switch Rate ........................................................................3-41
3.3.26 Whether to Support QUANZHOU Prepaid-SMS ..............................................3-42
3.3.27 Modify SMSC Number Function ......................................................................3-42
3.3.28 Whether Inter MSC Handover With Cell Load Group Info or Not.....................3-43
3.3.29 Whether to Adapt Container Info Within Handover/Relocation Request Message

....................................................................................................................................3-43
3.3.30 Whether the Bill for NNI OverlayMo Is Produced.............................................3-44
3.3.31 Max Percent of Dialog-id Area Occupation for USSD Service (%)...................3-45
3.3.32 Whether to Supply Optimize Half-Rate for Paktel ............................................3-45
3.3.33 Whether to Apply EGSM Frequency by Force .................................................3-45
3.3.34 Whether to Adapt Cause for Camel Play Tone Bill...........................................3-46
3.3.35 Whether Modify PresentInd of Generic Number Send by SCP........................3-46
3.3.36 The Maximum of DTMF Signals Sent by Mobile Subscriber in a Terminated Call3-
47
3.3.37 The Maximum of DTMF Signals Sent by Mobile Subscriber Before Answering in
an Outgoing Call .........................................................................................................3-48
3.3.38 Whether to Support PPS Flag in SMS-MO CDR .............................................3-48
3.3.39 Whether Report Call Duration for ANN ............................................................3-49
3.3.40 Preferred Voice Codec Type of Service Priority Level 1...................................3-49

3.3.44 Whether Delete International Prefix of Reconnect Number .............................3-51
3.3.45 Whether to Enable Sending out of Band DTMF Signal to UE ..........................3-52
3.3.46 The ANM/CONNECT Indication of BothwayThroughConnectionInd for ETC...3-52
3.3.47 The ACM (CPG)/Alerting Indication of BothwayThroughConnectionInd for ETC .3-

53
3.3.48 The ANM/CONNECT Indication of BothwayThroughConnectionInd for CTR ..3-54
3.3.49 The ACM (CPG)/Alerting Indication of BothwayThroughConnectionInd for CTR.3-

54
3.3.50 Not Sent Forwarding Notification to SCP .........................................................3-55
3.3.51 When OVMO, Send IMSI to SCP if It Can Be Got ...........................................3-56
3.3.52 Whether to Enable Retry Page with IMSI in Place of TMSI .............................3-56
3.3.53 How to Fill Called Party BCD Number in IDP Message ...................................3-57
3.3.54 CAP Interface Information Field Differences Control Switch............................3-57
3.3.55 Cancel GSMSSF Periodic Inspection of Basic Call .........................................3-58
3.3.56 SRF Calculate the Maximum Number of Income Excluding the Terminator.....3-58
3.3.57 SRF Can Be Collected in the First Number is the Terminator ..........................3-59
3.3.58 After MSC Connect the Call, Received TC_END (zero elements) and There Is AC
Pending, Release Call ................................................................................................3-59
3.3.59 Whether to Allow Paging in Search Mode for MSC Pool .................................3-60
3.3.60 Time Interval of Heart Beat Test for MSC Pool User Data Synchronization (in Sec)
....................................................................................................................................3-60
3.3.61 Allowed Heart Beat Abnormal Times for MSC Pool User Data Synchronization ..3-
61
3.3.62 Whether to Check IMSI Sent by PVLR ............................................................3-61
3.3.63 Interval of Send User Capacity to NNSF..........................................................3-62
3.3.64 Contain CIC in Called Number.........................................................................3-62
3.3.65 Pre-CIC Located at the Head of Called Number..............................................3-63
3.3.66 Whether to Adapt Termination Cause for Preemption ......................................3-63
3.3.67 LCS Version.....................................................................................................3-64

3.3.68 Whether to Support Long EPLMN List .............................................................3-64
3.3.69 CSL Location Report Control ...........................................................................3-65
3.3.70 Get HandOver Priority From Subscriber ..........................................................3-65
3.3.71 Ban the UE/MS Access With Illegal CI/SAI ......................................................3-66
3.3.72 Get PLMN of Iu Interface Global CN ID From Local Office Mobile Data
Configuration ..............................................................................................................3-66
3.3.73 Build MPTY With MPTY Bridge........................................................................3-67
3.3.74 The Indication of RedirectionInfo and RedirectingNum for TCSI Reconnect ...3-67
3.3.75 Business Process Control Parameters ............................................................3-68
3.3.76 Continue Call When CAMEL Tone Is too Short for the Calling User ................3-68
3.3.77 The Switches of Buffer Scan of CAMEL/HO Module .......................................3-69
3.3.78 Format Adjustment for MNP Is Needed or Not.................................................3-70
3.3.79 The Indication of Local CLIP Process When Nature of Calling Number Is
Unknown.....................................................................................................................3-70
3.3.80 Routing According to the PLMN-Specific SS Code ..........................................3-71
3.3.81 Paging Protect Time in MSC Pool....................................................................3-71
3.3.82 DDI Delay Saving Method................................................................................3-72
3.3.83 Threshold of A Interface PCM ..........................................................................3-72
3.3.84 For MF Calls Triggering at DP Collected_Info whether to Internationalize the

Destination Number Before Matching it ......................................................................3-73
3.4 Call Control .................................................................................................. 3-73
3.4.1 Whether to Support CUG Service......................................................................3-75
3.4.2 ISUP Simulation Failure Code ...........................................................................3-75
3.4.3 Whether to Force Passing on Impossible Indicator............................................3-77
3.4.4 Whether to Check the PESQ INFO....................................................................3-78
3.4.5 The Scale of Reset CIC Per 200 ms ..................................................................3-78
3.4.6 Support Multiple ColorRing Center by SSCODE Method ..................................3-79
3.4.7 Whether MS Alerts Automatically.......................................................................3-79
3.4.8 Whether to Judge the Called Number for Local or Toll in GMSC .......................3-80
3.4.9 Whether to Pause Call Protecting......................................................................3-80
3.4.10 Change Category of Calling User ....................................................................3-81
3.4.11 CAMEL Service Diff..........................................................................................3-82

3.4.12 Whether RAB Modification of RNC Supported by MSCS.................................3-83
3.4.13 Whether CODEC Modification Supported by MSCS........................................3-83
3.4.14 Whether Mid-Call Codec Negotiation Supported by MSCS .............................3-84
3.4.15 Whether to Support RAB Modification by RNC................................................3-84
3.4.16 International Calling Dial Method .....................................................................3-85
3.4.17 Whether to Support Data Transfer Method When MT Control .........................3-85
3.4.18 Whether HoReq Message Is Transferred in SCCP CR....................................3-86
3.4.19 Assignment After OP Bearer Established for Terminal Call ..............................3-86
3.4.20 Whether to Release When Call Handling in Abnormity of DDC Announcement ..3-
87
3.4.21 Whether to Release When Call Handling in Abnormity of DDC Indicator in

Signalling ....................................................................................................................3-87
3.4.22 Whether to Support Macao SMARTTONE CAMEL Service.............................3-88
3.4.23 Whether to Support Home Ring Back Tone Service ........................................3-88
3.4.24 Whether to Play Special RBT for Fault Call .....................................................3-89
3.4.25 Whether Redirecting Number Present in the Setup Message to the Forwarded-to
Mobile Subscriber C or Not.........................................................................................3-89
3.4.26 V32 Value in Q.931 ..........................................................................................3-90
3.4.27 Whether to Correct the BC Received From HLR When Facsimile Group 3 Service
in 2G Network Is Used................................................................................................3-90
3.4.28 Delete Special Prefix for International Number in CLIP ...................................3-91
3.4.29 Conversion Mode of ModemType in Bear Capability IE...................................3-91
3.4.30 Optional IE of L3 Message (to MS) Whether Be Included ...............................3-92
3.4.31 Whether the Mode of Dialed Number With International Prefix+Local CC Is

Allowed .......................................................................................................................3-92
3.4.32 Whether to Include Facility IE in Alerting Message ..........................................3-93
3.4.33 Whether to Support Independent OOBTC While GMSC Forwarding...............3-93
3.4.34 Whether to Support Start Bearer Timer While Paging at VMSC ......................3-94
3.4.35 Whether to Support Start Bearer Timer While Pre-Paging at GMSC ...............3-94
3.4.36 Forced Release Call Type................................................................................3-95
3.4.37 Intelligence Service Charging Warning Tone Playing Times ............................3-95
3.4.38 Whether to Return CAP Error if Duplicate TSW...............................................3-96

3.4.39 Reserved Variable............................................................................................3-96
3.4.40 Dialed Number With International Prefix + Local CC + National Prefix Mode
Control ........................................................................................................................3-97
3.4.41 Send Busy Tone to User When Call Released in Conversation.......................3-98
3.4.42 Send Status Enquire to MS..............................................................................3-98
3.4.43 Support OM in OOBTC....................................................................................3-99
3.4.44 Support CONC.................................................................................................3-99
3.4.45 Mobile Emergency Call Suppress SS ............................................................3-100
3.4.46 Transfer Area Infor in TRACER System.........................................................3-100
3.4.47 Use DialedNumber for OSB Analysis.............................................................3-101
Figures ................................................................................................................................ I
Tables ................................................................................................................................ III
Index...................................................................................................................................V
Glossary...........................................................................................................................VII
About This Manual
———————————————————————————————————————————
Purpose
This manual introduces the function, value range, default value and related security
variable of the security variables in the ZXWN MSCS system.
Intended Audience
This document is intended for:

z Engineers who have basic knowledge about mobile communications
z Engineers who have known the basic structure, and basic functions of ZXWN
MSCS
z Engineers who need to know the functions and value ranges of the timers of
ZXWN MSCS
Prerequisite Skill and Knowledge
To use this manual effectively, users should have a general understanding of wireless
telecommunications technology. Familiarity with the following is helpful:
z ZXWN MSCS system and its various components
z User interfaces on the MSCS
z Local operating procedures
What is in This Manual
This manual contains the following chapters:
Chapter Summary
Chapter 1, Overview Briefly describes the security variables and the procedure for
modifiying them.
Chapter 2, Common Describes the detailed information of the common security
Security Variables variables, including functions, default values, value range and
related security variables.
Chapter 3, WCN Security Describes the detailed information of the WCN security
Variables variables, including functions, default values, value range and
related security variables.
I
Conventions
ZTE documents employ the following typographical conventions.
Typeface Meaning
Italics References to other manuals or 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.
Mouse operation conventions are listed as follows:
Typeface Meaning
Click Refers to clicking the primary mouse button (usually the left mouse button)
once.
Double-click Refers to quickly clicking the primary mouse button (usually the left mouse
button) twice.
Right-click Refers to clicking the secondary mouse button (usually the right mouse
button) once.
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 ZXWN 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:
z Lead (Pb)
z Mercury (Hg)
z Cadmium (Cd)
z Hexavalent Chromium (Cr (VI))
z PPolyBrominated Biphenyls (PBBs)
z PolyBrominated Diphenyl Ethers (PBDEs)
ZXWN MSCS manufactured by ZTE CORPORATION meets 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.
I
II
Chapter 1
Overview
———————————————————————————————————————————
Table of Contents
Introduction to Security Variables …………………………………………………1-1

Modifying Security Variables ………………………………………………………1-2
1.1 Introduction to Security Variables

Definition
Some security variables function as switches that determine whether to support

one service. Some security variables are parameters that determine the flow of a
service. Some security variables are thresholds that control the amount of the
traffic. As the important parameters, security variables affect the crucial
performance of the system.
Function
Security variables manage dynamic system parameter configuration related with

protocols and services. These parameters are saved in the front-end boards in
forms of global variables and files. You can view and set these dynamic
parameters with interaction between the security variable module and the front-
end OMP module.
Structure
Figure 1 shows the structure tree of security variables.
1-1
SJ-20101208143956-014|2011-2-28(R1.0) ZTE Proprietary and Confidential

ZXWN MSCS MSC Server Security Variable Reference
FIGURE 1 STRUCTURE TREE OF SECURITY V ARI ABLES
1.2 Modifying Security Variables

Purpose
The purpose of modifying security variables is to adjust the system operation

parameters to satisfy users’ different requirements. Modifying security variables
refers to activating some service functions, adjusting a threshold upward or
downward, or setting parameters involved in services flow.
Note:
Generally, modifying security variables is not required. If necessary, contact the local ZTE office.
Taking security variable “The Maximum of DTMF Signals Sent by Mobile

Subscriber in a Terminated Call” as an example, this topic describes how to
modify a security variable.
Prerequisite
You have logged in to the main process client.

1-2

Chapter 1 Overview
Related Information
Security variable “The maximum of DTMF signals sent by mobile subscriber in a

terminated call” places restrictions on the dial-back card service by limiting the
number of the DTMF numbers dialed in a call termination process.
The security variable that is related to security variable “The Maximum of DTMF
Signals Sent by Mobile Subscriber in A Terminated Call” is “The Maximum of
DTMF Signals Sent by Mobile Subscriber Before Answering in an Outgoing Call”.
The “The Maximum of DTMF Signals Sent by Mobile Subscriber Before
Answering in an Outgoing Call” security variable is used to control the number of
DTMFs sent by the calling subscriber before the calling party is connected.
Steps
1. In the main window of the main process client, select Views > Professional
Maintenance to open the Professional Maintenance window.
2. In the Professional Maintenance tree, expand the Security Variable node, as

shown in Figure 2.
FIGURE 2 SECURITY V ARIABLE NODE
3. Click CS Network Entity Config, as shown in Figure 3.
1-3

FIGURE 3 CS NETWORK ENTITY CONFIGURATION P AR AMETERS
4. Select the row where security variable “The Maximum of DTMF Signals Sent by
Mobile Subscriber in A Terminated Call” is located, and then click the Modify
button. In the Current Value column, type a value as required (the default value is
255, indicating there is no limitation).
Note:
Be careful with this operation because the security variable to be modified may be
relevant with other security variables. Therefore, it is necessary to consider whether
this modification will affect other related security variables. In case of any questions,
please contact the local ZTE office.
5. After you modify this security variable, click the Save button.
Subsequent Task
Synchronize all changed tables after the modification.
1-4

Chapter 2
Common Security Variables
———————————————————————————————————————————
Table of Contents
Security Control Variable……………………………………………………………..2-1

Service Control Function Set…………………………………………………….2-48
Other Variables………………………………………………………………….2-54
Other Function Set…………………………………………………………………...2-86
License Function Set…………………………………………………………………2-93
2.1 Security Control Variable

Table 1 lists the security variables displayed in the Service Control Variable tab
page.
TABLE 1 SECURITY V ARIABLES DISPLAYED IN THE SERVICE CONTROL V ARI ABLE TAB
P AGE
Security Variable Page No.

Maximum Call Diversion Times 2-3
Whether to Support Larger-Than-Limit Forward Times in Signaling Codec 2-4
DualHome Heartbeat Interval 2-4
DualHome Heartbeat Try Times 2-5
Whether to Delete VLR Data After Switching 2-5
Whether to Delete VLR Data in Appointed Time 2-6
Show Original and Modified Sig Message 2-6
Whether to Use IP Load Control When the Call Is SIP Outgoing Call 2-7
Whether to Support Incoming IP Test Call 2-7
The Type of Test Termination of IP Load Control Test Call 2-8
The Reference Value of Delay for 100 2-8
The Reference Value of Delay for 60 2-9
The Reference Value of Lost for 100 2-11
The Reference Value of Lost for 60 2-12
2-1

The Reference Value of Jitter for 100 2-13
The Reference Value of Jitter for 60 2-15
The Weight for Delay 2-16
The Weight for Lost 2-17
The Weight for Jitter 2-18
The Reference Value of Congest Lever 1 2-20
The Reference Value of Congest Lever 2 2-21
The Reference Value of Congest Level 3 2-22
The Step of Normal Level 2-25
The Step of Congestion Level 1 2-26
The Hour of Time for Counter Check 2-31
The Minute of Time for Counter Check 2-32
Support User Level in IP_LoadCtrl Function 2-33
The Percent of Call Number for the High Level Subscribers Having 2-34
Priority to Use the IP Bearer
Whether the Cycle of Send Circuit (Group) Message or CCR Message 2-34
The Upper Limit of National Number Length 2-35
The Upper Limit of Subscriber Number Length 2-36
Whether the Fail Announce Counted in Call Completed Ratio 2-37
Support Calling subscriber's Category Conversion for Outgoing Signaling 2-37
WCDMA Network Type 2-38
Forbid Calling Number in Outgoing Signaling 2-38
The Flag of Whether Record the Status of Blocked CIC by Local Operator 2-39
to Disk
Whether to Hold OMC Operate CIC Block State Allowed 2-39
The Indication of NNI Process When Nature of Calling Number Is 2-40
Unknown
Whether COT is Expected 2-40
IWF Description Type in SDP 2-42
Speed Variable of GRS Sent 2-43
2-2

Chapter 2 Common Security Variables

Event Indicator Parameter Mode 2-44
Allow Scan NNI Data 2-45
Support Modify Caller Number Totally for Inter-Office DDI 2-45
Whether ACM with Wait Indicator or Not 2-46
Transmit Unknown Parameter in ISUP 2-46
Which DTone Signal Need to Detect 2-47
Ratio between Max-Forwards and Hop Counter 2-48
2.1.1 Maximum Call Diversion Times

Security Variable ID
Function
This security variable specifies the maximum number of times that a call is
forwarded, including intra-office call forwarding and inter-office call forwarding.
1. When a call is being forwarded in an office, this call is released when the number
of times that this call is forwarded is greater than the value of this security variable.
2. During an incoming call, the IAM message carries the number of times that this
call is forwarded.
z If the number of times that this call is forwarded (carried by the IAM
message) is greater than or equal to the value of this security variable, the
system allows continuing connecting this call. The system, however, inhibits
the call from being forwarded again in the local office. Otherwise, it directly
releases this call.
z If the number of times that this call is forwarded (carried by the IAM
message) is less than the value of this security variable, this call is allowed
to be forwarded in the local office. It is release when the sum of the number
of times that the call is forwarded in the local office and the number of times
contained in the IAM message is greater than or equal to the value of this
security variable.
Default Value
3
2-3

Value Range
Value Meaning
1 The system supports call forwarding of up to one time.
2 The system supports call forwarding of up to two times.
3 The system supports call forwarding of up to three times.
4 The system supports call forwarding of up to four times.
5 The system supports call forwarding of up to five times.
2.1.2 Whether to Support Larger-Than-Limit Forward Times in

Signaling Codec
Function
According to the Signaling System 7 (SS7) protocol, the maximum number of times
that a call is forwarded (in the inter-office SS7 signaling) is five. This variable specifies
whether to use the actual number of times (probably greater than five) that a call is
forwarded (carried by the outgoing signaling) or the maximum number of times
specified in the protocol (less than five).
Default Value
No
Value Range
Value Meaning
The system uses the maximum number of times (five) that a call is
No
forwarded (specified in the protocol).
The system uses the actual number of times that a call is forwarded (that
Yes
can exceed the maximum one specified in the protocol).
2.1.3 DualHome Heartbeat Interval

Function
This security variable sets the interval of sending and waiting for a heartbeat
message between dual-homed partner offices in the same domain.
2-4

Default Value
Value Range
[1, 30]
Unit: second
2.1.4 DualHome Heartbeat Try Times

10
Function
The system allows sending a heartbeat detection message again after the
heartbeat detection of the dual-homing module fails. This security variable sets
the number of heartbeat detections.
Default Value
Value Range
[1, 10]
2.1.5 Whether to Delete VLR Data After Switching

12
Function
This security variable specifies whether to delete the data on standby server after
dual-homing changeover.
Default Value
Yes
Value Range
Value Meaning
No The system retains the data on the standby server after changeover.
Yes The system deletes the data on the standby server after changeover.
2-5

2.1.6 Whether to Delete VLR Data in Appointed Time

13
Function
This security variable specifies the duration of delaying deleting data on the
standby server after dual-homing changeover.
Default Value
Value Range
[1, 10]
Unit: Minute
2.1.7 Show Original and Modified Sig Message

1818
Function
Both the SS7UP and the BICC provide the function of editing the signaling
messages on the incoming side and on the outgoing side. This security variable
specifies whether to display the original and edited incoming and outgoing
messages. The edited message is marked with “[ ]”.
Default Value
Not show
Value Range
Value Meaning
The system does not display the edited incoming messages or the
Not show
original outgoing messages.
The system displays the edited incoming messages and the original
Show
outgoing messages.
2-6

2.1.8 Whether to Use IP Load Control When the Call Is SIP Outgoing
Call
121
Function
The system supports flow control of the outgoing SIP calls to control the INVITE
messages during outgoing SIP calls.
If the system supports flow control of the outgoing SIP calls, it performs call control
according to the QoS parameter measured during flow control. If the system does not
support this function, the system will not control the outgoing SIP calls.
Default Value
No
Value Range
Value Meaning
No Flow control of outgoing SIP calls is not supported.
Yes Flow control of outgoing SIP calls is supported.
2.1.9 Whether to Support Incoming IP Test Call

122
Function
If the system supports incoming IP flow-control test call, when the BCM module
receives an EV_L3L4_SETUP_IND message from the SIP module, it performs IP flow
control to calculate the QoS parameter of this inter-office bearer. This makes sure the
bearer quality to further adjust the quantity of calls on this bearer.
Default Value
Yes
Value Range
Value Meaning
No Incoming IP flow-control test call is not supported
Yes Incoming IP flow-control test call is supported
2-7

2.1.10 The Type of Test Termination of IP Load Control Test Call

123
Function
The system supports to configure the coding/decoding type used for terminal
setup flexibly. Types PCM A and EVRC are available for selection. When
originating a test call, the system selects the coding/decoding type according to
the setting of this security variable.
Default Value
PCMA
Value Range
Value Meaning
PCMA The PCM A coding/decoding type is used.
EVRC The EVRC coding/decoding type is used.
2.1.11 The Reference Value of Delay for 100

124
Function
This security variable sets the reference delay value when the score of IP
transmission delay is 100, which provides a basis for calculating the overall score
of QoS in IP flow control.
IP flow control obtains the current QoS parameter of the bearer of this segment
based on the test call that the system internally originates for this bearer. This
QoS parameter reflects the quality of the bearer. The QoS parameter contains
transmission delay, packet loss rate and jitter on the bearer of this segment.
Calculating the overall QoS score requires the actual delay value, packet loss rate,
jitter value, the index configuration of each parameter in the security variables,
and the weighting of each parameter in the QoS. The system sets the current
congestion level according to the overall QoS score, and controls the step length
and the quantity of connected calls according to the corresponding congestion
level, thus completing dynamic IP flow control.
The formula for calculating the overall QoS score is as follows:
2-8

Overall score = (The Score of Packet Loss Rate × The Weighting of Packet Loss
Rate in the Comprehensive Evaluation of the IP Bearer QoS Level + The Score of
Transmission Delay × The Weighting of Transmission Delay in the
Comprehensive Evaluation of the IP Bearer QoS Level + The Score of Jitter × The
Weighting of Jitter in the Comprehensive Evaluation of the IP Bearer QoS
Level)/10
When the transfer delay value of the test call is less than “The Reference Value of
Delay for 100”, the score of transfer delay is set to 100. If the transmission delay
is between “The Reference Value of Delay for 100” and “The Reference Value of
Delay for 60”, the score of delay is calculated by the above formula. If the
transmission delay is greater than “The Reference Value of Delay for 60”, the
delay is set to zero.
Default Value
100
When delay is less than 100 ms, the score of transmission delay is 100.
Value Range
[0, 600]
Unit: ms
Related Security Variables

Security Variable Description of Relationship
The Reference Value of Delay for 60
The Reference Value of Lost for 100
The Reference Value of Jitter for 100 To calculate the overall QoS score, these
The Reference Value of Jitter for 60 security variables are used together.
The Weight for Delay

The Weight for Lost
The Weight for Jitter
2.1.12 The Reference Value of Delay for 60

125
2-9

Function
This security variable sets the reference delay value when the score of IP
transmission delay is 60. This provides a basis for calculating the overall score of
QoS in IP flow control.
Level)/10
When the transmission delay value of the test call is less than “The Reference
Value of Delay for 100”, the score of transmission delay is set to 100. If the
transmission delay is between “The Reference Value of Delay for 100” and “The
Reference Value of Delay for 60”, the score of delay is calculated by the above
formula. If the transmission delay is greater than “The Reference Value of Delay
for 60”, the delay is set to zero.
Default Value
250
When delay is greater than 250 ms, the score of transmission delay is zero.
Value Range
[0, 600]
Unit: ms

The Reference Value of Delay for 100 To calculate the overall QoS score, these
security variables are used together.
2-10


The Reference Value of Jitter for 100
The Weight for Lost
2.1.13 The Reference Value of Lost for 100

126
Function
This security variable sets the reference packet-loss-rate when the score of IP
transfer packet-loss-rate is 100. This provides a basis for calculating the overall
score of QoS in IP flow control.
Level)/10
When the packet loss rate of the test call is less than “The Reference Value of
Lost for 100”, the score of the packet loss rate is set to 100. If the packet loss rate
is between “The Reference Value of Lost for 100” and “The Reference Value of
Lost for 60”, the score of the packet loss rate is calculated by the above formula.
When the packet loss rate is greater than “The Reference Value of Lost for 60”,
the score of the packet loss rate is set to zero.
2-11

Default Value
3
When the packet loss rate is less than 3%, the score is 100.
Value Range
[0, 20]
Unit: percentage

The reference Value of Delay for 100

The Weight for Lost
2.1.14 The Reference Value of Lost for 60

127
Function
This security variable sets the reference-packet-loss rate when the score of IP
transfer packet-loss-rate is 60. This provides a basis for calculating the overall
score of QoS in IP flow control.
2-12

Level)/10
When the packet loss rate of the test call is less than “The Reference Value of
Lost for 100”, the score of the packet loss rate is set to 100. If the packet loss rate
is between “The Reference Value of Lost for 100” and “The Reference Value of
Lost for 60”, the score of the packet loss rate is calculated by the above formula.
When the packet loss rate is greater than “The Reference Value of Lost for 60”,
the score of the packet loss rate is set to zero.
Default Value
8
When the packet loss rate is greater than 8%, the score is zero.
Value Range
[0, 20]
Unit: percentage


The Weight for Lost
2.1.15 The Reference Value of Jitter for 100

128
2-13

Function
This security variable sets the reference jitter value when the score of IP
transmission jitter is 100. This provides a basis for calculating the overall score of
Level)/10
When the jitter value of the test call is less than “the Reference Value of Jitter for
100”, the score of jitter is set to 100. If the jitter value is between “The Reference
Value of Jitter for 100” and “The Reference Value of Jitter for 60”, the score of
jitter is calculated by the above formula. If the jitter value is greater than “The
Reference Value of Jitter for 60”, the score of jitter is zero.
Default Value
25
When the jitter value is less than 25 ms, the score of jitter is 100.
Value Range
[0, 60]
Unit: ms

The Reference Value of Delay for 100 To calculate the overall QoS score, these
security variables are used together.
2-14


The Weight for Lost
2.1.16 The Reference Value of Jitter for 60

129
Function
This security variable sets the reference jitter value when the score of IP
transmission jitter is 60. This provides a basis for calculating the overall score of
Level)/10
When the jitter value of the test call is less than “The Reference Value of Jitter for
100”, the score of jitter is set to 100. If the jitter value is between “The Reference
Value of Jitter for 100” and “The Reference Value of Jitter for 60”, the score of
jitter is calculated by the above formula. If the jitter value is greater than “The
Reference Value of Jitter for 60”, the score of jitter is zero.
2-15

Default Value
50
When the jitter value is greater than 50 ms, the score of jitter is zero.
Value Range
[0, 60]
Unit: ms

The Reference Value of Lost for 60 To calculate the overall QoS score, these

The Weight for Lost
2.1.17 The Weight for Delay

130
Function
This security variable sets the weighting of transmission delay in the

comprehensive evaluation of the IP-bearer QoS level to calculate the overall QoS
score.
2-16

Level)/10
Default Value
4
It indicates that the weighting of transmission delay in the comprehensive
evaluation of the IP-bearer QoS level is 40%.
Value Range
[0, 10]
Unit: 1/10


The Weight for Lost
2.1.18 The Weight for Lost

131
Function
This security variable sets the weighting of the packet loss rate in the
score.
2-17

Level)/10
Default Value
6
It indicates that the weighting of the packet loss rate in the comprehensive
evaluation of the IP-bearer QoS level is 60%.
Value Range
[0, 10]
Unit: 1/10

The Reference value of Lost for 60 To calculate the overall QoS score, these

2.1.19 The Weight for Jitter

132
2-18

Function
This security variable sets the weighting of transmission jitter in the

score.
Level)/10
Default Value
0
It indicates that the weighting of transmission jitter in the comprehensive
evaluation of the IP-bearer QoS level is zero.
Value Range
[0, 10]


The Weight for Lost
2-19

2.1.20 The Reference Value of Congest Lever 1

133
Function
This security variable sets the lowest overall score of congestion level 1.
After calculating the overall QoS score, the system determines its current
congestion level according to the lowest score of the highest congestion level 1
through that of the lowest congestion level 5, and controls the step length
according to different congestion levels.
The principle of registering congestion and adjusting the step length is as follows:
z When the overall QoS score is greater than “The Reference Value of congest
level 1”, the system is not congested, and it sets the adjustment step length to
“The Step of Normal Level”.
z When the overall QoS is greater than “The Reference Value of Congest Level 2”
but is less than or equal to “The Reference Value of Congest Level 1”, the system
sets the congestion level to 1, and the adjustment step length to “The Step of
Congestion Level 1”.
Default Value
95
It indicates that the lowest overall score of congestion level 1 is 95.
Value Range
[0, 100]

The Reference Value of Congest Level 2
The Step of Normal Level
Used for dynamic IP flow control
The Step of Congestion Level 1
2-20

2.1.21 The Reference Value of Congest Lever 2

134
Function
z When the overall QoS score is greater than “The Reference Value of Congest
Level 2” but is less than or equal to “The Reference Value of Congest Level 1”,
the system sets the congestion level to 1, and the adjustment step length to “The
Step of Congestion Level 1”.
Default Value
85
Value Range
[0, 100]

The Reference Value of Congest Level 1 Used for dynamic IP flow control
2-21


2.1.22 The Reference Value of Congest Level 3

135
Function
Default Value
75
Value Range
[0, 100]

2-22



136
Function
Default Value
60
Value Range
[0, 100]

2-23



137
Function
z When the overall QoS score is less than or equal to “the reference value of
congest lever 5”, the system sets the congestion level to 5, and the adjustment
step length to “the step of congestion level 5”.
Default Value
40
Value Range
[0, 100]

2-24


2.1.25 The Step of Normal Level

138
Function
This security variable sets the adjustment step length when the QoS congestion
level is normal. It provides a basis for adjusting the proportion of connected calls
according to the congestion level.
When the overall QoS score is greater than “the reference value of congest lever
1”, the system is not congested, and it sets the adjustment step length to “The
step of Normal Level”.
Default Value
5
It indicates that the number of calls accepted by the system increases by 5%
compared with the last period.
Value Range
[0, 20]
Unit: percentage
2-25


2.1.26 The Step of Congestion Level 1

139
Function
level is 1. It provides a basis for adjusting the proportion of connected calls
When the overall QoS is greater than “The Reference Value of Congest Level 2”
Default Value
5
It indicates that when the QoS congestion level is 1, the number of calls accepted
by the system decreases by 5%.
Value Range
[0, 20]
2-26

Unit: percentage


140
Function
Default Value
10
2-27

Value Range
[0, 20]
Unit: percentage


141
Function
Default Value
15
2-28

Value Range
[0, 20]
Unit: percentage


142
Function
2-29

Default Value
20
Value Range
[0, 30]
Unit: percentage


143
Function
When the overall QoS score is less than or equal to “The Reference Value of
Congest Level 5”, the system sets the congestion level to 5, and the adjustment
step length to “the step of congestion level 5”.
2-30

Default Value
25
Value Range
[0, 40]
Unit: percentage

2.1.31 The Hour of Time for Counter Check

144
Function
This security variable sets the period (in hours) of detecting counters during
dynamic IP flow control to notify the BCM module to compare these counters. This
ensures that the call counter in the BCM module is consistent with that in the DB
module.
When the one-minute loop timer set by the TCM module expires, the TCM module
reads the current system time to get the current hours (in 24-hour system) and
minutes. Then it compares the hours with the value of security variable “The Hour
of Time for Counter Check”, and the minutes with the value of security variable
“The Minute of Time for Counter Check”. If the current time reaches or is not 10
minutes later than the set time, the TCM module sends a notification message of
2-31

detecting the counters, and sets the corresponding flag bit, indicating that the
detection counter is triggered within the valid range of time difference.
After the subsequent one-minute loop timer expires, and if time difference is still in
the valid range, the corresponding flag bit is valid. The system does not notify the
BCM to detect the counter. If time difference is beyond the valid range, the system
resets the corresponding flag bit, and then detects the counter.
Default Value
0
It indicates that the detection cycle of the hour-counter is reset at 0:00 a.m. every
day.
Value Range
[0, 23]
Unit: hour

The Minute of Time for Counter
Used for cycle detection counter.
Check
2.1.32 The Minute of Time for Counter Check

145
Function
This security variable sets the period (in minutes) of detecting counters during
dynamic IP flow control to tell the BCM module to compare these counters. This
ensures that the call counter in the BCM module is consistent with that in the DB
module.
When the one-minute loop timer set by the TCM module expires, the TCM module
reads the current system time to get the current hours (in 24-hour system) and
minutes. Then it compares the hours with the value of security variable “The Hour
of Time for Counter Check”, and the minutes with the value of security variable
“The Minute of Time for Counter Check”. If the current time reaches or is not 10
minutes later than the set time, the TCM module sends a notification message of
detecting the counters, and sets the corresponding flag bit, indicating that the
detection counter is triggered within the valid range of time difference.
2-32

After the subsequent one-minute loop timer expires, and if time difference is still in the
valid range, the corresponding flag bit is valid. The system does not tell the BCM to
detect the counter. If time difference is beyond the valid range, the system resets the
corresponding flag bit, and then detects the counter.
Default Value
0
It indicates that the detection cycle of this minute-counter is reset exactly on the
hour.
Value Range
[0, 59]
Unit: Minute

The Hour of Time for Counter
Used for cycle detection counter.
Check
2.1.33 Support User Level in IP_LoadCtrl Function
2014
Function
When abnormality occurs in an IP bearer network, congestion occurs to the

system, thus the call quality is degraded. To detect this situation, the system
provides the IP flow control function to control the quantity of calls that are allowed
to be connected.
When this security variable is enabled, the system needs to detect the IP bearer.
During IP bearer detection, the system distinguishes these types of bearers
mentioned-above with the back-end OMC configuration. It can also originate test
calls according to the variable configuration to get the corresponding QoS
parameters for call adjustment. When detecting that the bearer quality is
degraded, the system decreases the number of calls allowed to be connected by
certain proportion according to the number of calls that this bearer accepted in the
previous period. Correspondingly, when detecting the bearer quality is improved,
the system increases the number of the calls allowed to be connected by certain
proportion. In this way, admission control of the IP media plane is achieved. If this
2-33

variable is disabled, the system does not originate test calls, thus IP flow control is
stopped.
Default Value
No
Value Range
Value Meaning
No The system does not support the user priority for IP flow control.
Yes The system supports the user priority for IP flow control.
2.1.34 The Percent of Call Number for the High Level Subscribers
Having Priority to Use the IP Bearer
2015
Function
This security variable specifies the percentage of normal suscribers to all

subscribers.
Default Value
90
Value Range
[0, 100]
Unit: percentage
2.1.35 Whether the Cycle of Send Circuit (Group) Message or CCR

Message
1809
Function
This security variable specifies whether to cyclically resend the circuit

management messages or whether to carry out re-continuity when the timer
waiting for the circuit (group) response message expires.
2-34

Default Value
No
Value Range
Value Meaning
The system neither cyclically resends the circuit management
No
messages nor carries out re-continuity.
When the long timer for circuit management expires, the system
Yes
resends the circuit management messages and allows re-continuity.

Security variable “Allow Scan NNI Data” must be
Allow Scan NNI Data
disabled.
2.1.36 The Upper Limit of National Number Length

1812
Function
Because the Channel Associated Signaling (CAS) protocol does not support
delivery of the calling number attribute, this security variable is for the CAS
signaling module to determine the calling number attribute. The CAS signaling
module first judges whether the calling number contains international or national
dialing prefix. If the calling number does not contain the prefix, the module
determines that:
z The calling number is an international number when its length is greater than “The
Upper Limit of National Number Length”.
z The calling number is a national number when its length is less than or equal to
“The Upper Limit of National Number Length”, but is greater than “The Upper
Limit of Subscriber Number Length”.
Default Value
11
Value Range
[0, 40]
2-35


This security variable is used together with security variable
The Upper Limit of Subscriber “The Upper Limit of National Number Length” to determine
Number Length the upper limit and the inferior limit of the length of a
number.
2.1.37 The Upper Limit of Subscriber Number Length

1813
Function
Because the Channel Associated Signaling (CAS) protocol does not support
delivery of the calling number attribute, this security variable is for the CAS
signaling module to determine the calling number attribute. The CAS signaling
module first judges whether the calling number contains international or national
dialing prefix. If the calling number does not contain the prefix,
z The module judges that the calling number is a national number when its length is
less than or equal to “The Upper Limit of National Number Length”, but is greater
than “The Upper Limit of Subscriber Number Length”.
z When the number length is less than or equal to "The Upper Limit of Subscriber
Number Length", and the number format conforms to the national standards of
China, the module judges that the number is an “unknown” number.
z When the number length is less than or equal to "The Upper Limit of Subscriber
Number Length", but the number format does not conform to the national
standards of China, the module judges that the number is a local number.
Default Value
Value Range
[0，40]

This security variable is used together with security variable
The Upper Limit of National “The Upper Limit of National Number Length” to determine
Number Length the upper limit and the inferior limit of the length of a
number.
2-36

2.1.38 Whether the Fail Announce Counted in Call Completed Ratio

1814
Function
If an incoming call actually is not connected, but the failure announcement tone is
played in the local office, and the ACM message is sent to the origination office,
this security variable determines whether to calculate this call into the call
completion ratio of the local office.
Default Value
Yes
Value Range
Value Meaning
A call that the failure tone is played for is not counted into the number
No
of calls connected in the local office.
A call that the failure tone is played for is counted into the number of
Yes
calls connected in the local office.
2.1.39 Support Calling subscriber's Category Conversion for

Outgoing Signaling
1815
Function
When a mobile network is interconnected with a traditional PSTN network, the mobile
network equipment supports the calling subscriber categories received from the PSTN
network, but it is required to map and covert them to the calling subscriber categories
supported by the mobile network.
This security variable specifies whether to support mapping conversion of the
calling subscriber categories.
Default Value
Yes
2-37

Value Range
Value Meaning
The system transparently transmits the received calling subscriber
No
categories instead of mapping and converting them.
The system performs mapping conversion of the calling subscriber
Yes
categories.
2.1.40 WCDMA Network Type

1825
Function
If this security variable is set, the system preferentially gets the SPC of this office
and fills it in the Call Detailed Records (CDR).
Default Value
Value Range
[0, 255]
2.1.41 Forbid Calling Number in Outgoing Signaling

1035
Function
This security variable specifies whether outgoing signaling messages contain

calling numbers.
Default Value
No
Value Range
Value Meaning
No The outgoing signaling message contains the calling number.
Neither the outgoing IAM message contains the calling number nor the INVITE
Yes
request message contains the calling number of an outgoing SIP call.
2-38

2.1.42 The Flag of Whether Record the Status of Blocked CIC by

Local Operator to Disk
1829
Function
This security variable specifies whether to write the status of the manually blocked
local circuit (maintenance-oriented) to a disk or an electronic disk on the front-end
OMP.
Default Value
No
Value Range
Value Meaning
No The status is not written to a disk or an electronic disk.
Yes The status is written to a disk or an electronic disk.
2.1.43 Whether to Hold OMC Operate CIC Block State Allowed

1043
Function
This security variable specifies whether it is allowed to keep the CIC in blocked
status that is initiated through the dynamic management in the back-end
subsystem. If it is allowed to keep the CIC in blocked status that is initiated
through the dynamic management, excepting resetting the circuit management
module, this blocked circuit can only be released by the circuit (group) unblocking
or restoring operation initiated from the back end.
This security variable is used only when a circuit is manually blocked and
manually unblocked. After modifying this security variable, you need to restart the
corresponding module on the front end.
Default Value
No
2-39

Value Range
Value Meaning
The system does not keep the CIC in blocked status that is initiated
No
through the dynamic management.
The system keeps the CIC in blocked status that is initiated through the
Yes
dynamic management until it is released manually.
2.1.44 The Indication of NNI Process When Nature of Calling

Number Is Unknown
1830
Function
This security variable specifies transform of calling numbers with unknown nature
in outgoing signaling messages.
When the calling number nature is UNK (unknown), and the number does not
contain the international prefix and domestic toll prefix, and if this variable is
enabled, the domestic country code is added before the calling number when this
calling number is internationalized. In addition, the number nature is changed to
INT (international). If this security variable is disabled, the calling number is not
transformed.
Default Value
No
Value Range
Value Meaning
No No special processing
The domestic country code is added in front of the calling number with
Yes
UNK nature during internationalization.
2.1.45 Whether COT is Expected

1056
Function
This security variable specifies whether the outgoing IAM signaling message
contains the Continuity Check indication.
2-40

If this security variable is enabled, the Continuity Check (COT) flow is supported.
If the Continuity Check indication in the outgoing IAM message is set to indicate
either “continuity check required on this circuit” or “continuity check performed on
previous circuit” according to the actual call situations, the COT message
subsequently is sent to the backward office.
In case of the incoming→outgoing call model, if the incoming IAM message
carries the Continuity Check indication (indicating either “continuity check required
on this circuit” or “continuity check performed on previous circuit”), the outgoing
IAM message carries the indication of “continuity check performed on previous
circuit”. If the system receives the incoming COT message or the incoming COT
message with the Continuity indication of “continuity check successful” during the
subsequent call flow, it forwards the COT message to the backward office.
If the bearer is not established yet when the IAM message is outgoing, the
outgoing IAM message carries the indication of “continuity check performed on
previous circuit”. After the bearer is established, the COT message is sent.
Or, if the label of “containing continuity check” is selected on the outgoing trunk,
regardless of what call model is used or whether the previous circuit is under
continuity or whether the bearer is established, the continuity check is required in
this call. The outgoing IAM message contains the indication of “continuity check
required on this circuit” while exiting. In addition, the system initiates the process
of continuity-check-tone self-loop detection. When the continuity check is
successful, and “continuity check performed on previous circuit” is successful (if
any), the system sends the COT message to the backward office after
establishment of the bearer.
If this security variable is disabled, the Continuity Check indication is not sent to
the backward office. The entire continuity test is terminated in the local office.
In case of incoming→outgoing call model, if the incoming IAM message carries
the Continuity Check indication (indicating either “continuity check performed on
previous circuit” or “continuity check required on this circuit”), the outgoing side
defers sending the outgoing IAM message until the incoming side receives the
COT message or the continuity check is completed at the incoming side. This
outgoing IAM message does not carry the continuity check indication.
If the bearer is not established when the IAM message is outgoing, the outgoing
side defers sending the outgoing IAM message until the bearer is established.
The IAM message does not carry the continuity check indication.
If the label of “containing continuity check” is selected on the outgoing trunk,
regardless of what call model is used or whether the previous circuit is under
continuity or whether the bearer is established, the continuity check will not be
performed. The system defers sending the outgoing IAM message until the
continuity check is performed on previous circuit (in any) and the bearer is
established. The IAM message does not carry the continuity check indication.
2-41

Default Value
No
Value Range
Value Meaning
No No continuity-check-indication is carried while outgoing.
The continuity check indication is carried while outgoing. Whether this
Yes indication is carried depends on the actual call situations and the
configuration of the trunk label.
2.1.46 IWF Description Type in SDP

244
Function
This security variable provides different indicators to describe the IWF service
during an outgoing or incoming SIP call, fully meeting the requirements of different
vendors, countries or areas on supporting this service. It can be set to the
following values:
z G.711 (with Fax/Modem indicator): This mode complies with the standards of
China Telecom by adding a line in the SDP information. The specific format is as
follows:
Fax service:
m=audio 8766 RTP/AVP 0
a=Fax
Modem service:
m=audio 8766 RTP/AVP 0
a=Modem
z G.711 (without Fax/Modem indicator): This mode is to be compatible with other

vendors because the protocol requires that all vendors must support the G.711
format. In this way, the fax service can run properly when the network quality is
good.
z IWF: This coding and decoding format is reserved for compatible with the internal
version of IWF.
The G.711 mode is classified into G.711 PCMA (PCM A law) and G.711 PCMU
(PCM µ law).
2-42

Strict inspection: indicates that the system checks the SDP parameter during
incoming SIP calls and outgoing SIP calls.
Without strict inspection: The system does not check the SDP parameter during
incoming SIP calls. The outgoing SIP calls carry the SDP parameter according to
the indication of this security variable.
Default Value
G.711A (with Fax/Modem indicator, strict inspection)
Value Range
Value Meaning
G.711A (with Fax/Modem indicator, strict G.711 PCMA + with Fax/Modem indicator +
inspection) strict inspection
G.711U (with Fax/Modem indicator, strict G.711 PCMU + with Fax/Modem indicator +
inspection) strict inspection
IWF CODEC (strict inspection) IWF CODEC + strict inspection
G.711A (without Fax/Modem indicator) G.711 PCMA + without Fax/Modem indicator
G.711U (without Fax/Modem indicator) G.711 PCMU + without Fax/Modem indicator
G.711A (with Fax/Modem indicator, without G.711 PCMA + with Fax/Modem indicator +
strict inspection) without strict inspection
G.711U (with Fax/Modem indicator, without G.711 PCMU + with Fax/Modem indicator +
strict inspection) without strict inspection
IWF CODEC (without strict inspection) IWF CODEC + without strict inspection
2.1.47 Speed Variable of GRS Sent

1966
Function
This security variable specifies the number of GRS messages sent every 400 ms
to control the speed of sending the GRS messages. It is used to be compatible
with the message processing capability of the peer office.
Default Value
4
It indicates that 16 GRS messages are sent every 400 ms.
2-43

Value Range
Value Meaning
1 Indicates that two GRS messages are sent every 400 ms.
2 Indicates that four GRS messages are sent every 400 ms.
3 Indicates that eight GRS messages are sent every 400 ms.
4 Indicates that 16 GRS messages are sent every 400 ms.
2.1.48 Event Indicator Parameter Mode

1897
Function
This security variable specifies the mode of filling the Event indication parameter
in the CPG message.
Default Value
WCS mode
Value Range
Value Meaning
Only an office in the WCDMA Circuit Switched (WCS) domain can
be configured with this mode.
WCS mode If both the called subscriber status and the billing indication are “0
no indication”, the event indication in the CPG is set to “2
PROGRESS”; otherwise, the event indication is set to “1 Alert”.
Only an office in the CDMA Circuit Switched (CCS) domain can
be configured with this mode.
If the called subscriber status is not “0 No indication”, the event
indication is set to “1 Alert”.
If there is a forwarding indication with the forwarding cause “call
forward unconditional”, the event indication is set to “6 CFU”. If
CCS mode the forwarding indication carries the forwarding cause “Call
Forward on no Reply”, the event indication is set to “5 CFNRy”. If
the forwarding indication carries the forwarding cause “Call
Forward on Busy”, the event indication is set to “4 CFB”. If the
forwarding indication carries other causes, the event indication is
set to “5 CFNRy”.
Otherwise, the event indication is set to “2 PROGRESS”.
2-44

2.1.49 Allow Scan NNI Data

1972
Function
The NNI data area is a data area related with interoffice calls, Including ISUP,
BICC, TUP, ISDN, and R2. This security variable specifies whether to scan all
NNI data areas to find the suspended one. The system scans 300 data areas
once every 10 seconds. If finding a suspended data area, it directly releases this
data area. Generally, a data area that has been occupied over 24 hours is
regarded as a suspended data area.
Default Value
Yes
Value Range
Value Meaning
No The system disables the function of scanning NNI data areas.
Yes The system enables the function of scanning NNI data areas.

Whether the Cycle of Send Circuit
This security variable must be disabled.
(Group) Message or CCR Message
2.1.50 Support Modify Caller Number Totally for Inter-Office DDI

1974
Function
If an incoming call does not carry the calling number, the system can specify a
number as the calling number by configuring the replacement mode of the calling
number transform on the trunk. This calling number is shown in the CDR and
used in the succeeding connection processing.
In case of the incoming calls from the same trunk, some of them carry the calling
number, while some of them do not. If it is only required to fill in the calling
number for the call without a calling number, you also need to configure the trunk
flag “Calling Number Stream Transform for Calls without Calling Number only”.
2-45

Otherwise, the system will replace the calling number with the configured one no
matter whether the call carries a calling number.
Default Value
Yes
Value Range
Value Meaning
The system does not support providing the calling number in
No
“replacement” mode.
The system supports providing the calling number in “replacement”
Yes
mode.
2.1.51 Whether ACM with Wait Indicator or Not

1034
Function
This security variable sets whether the local office sends an ACM message
carrying the call-waiting indication when call waiting occurs.
Default Value
No
Value Range
Value Meaning
The subsequently transmitted CPG message instead of the ACM message
No
carries the call-waiting indication.
Yes The ACM message directly carries the call-waiting indication.
2.1.52 Transmit Unknown Parameter in ISUP

2031
Function
Some unknown parameters often appear during ISUP interworking. This security
variable instructs whether the ISUP protocol transparently transmits unknown
parameters.
2-46

z If transparent transmission is not allowed, the ISUP protocol determines whether

this unknown parameter conforms to the definition in the protocol. If this
parameter conforms to the protocol, the ISUP protocol transparently transmit it,
otherwise, it discards the unknown parameter.
z For example, when the IAM message carries unknown parameter E7, the ISUP
protocol transparently transmits it when the ISUP protocol is set to ANSI ISUP,
and discards it when the ISUP protocol is set to HK ISUP. This is due to that
supporting parameter E7 is defined in the ANSI ISUP instead of the HK ISUP,
z When transparent transmission is allowed, this unknown parameter will be
transparently transmitted no matter whether the protocol supports this unknown
parameter.
Default Value
Yes
Value Range
Value Meaning
No Transparent transmission of unknown parameters disallowed
Yes Transparent transmission of unknown parameters allowed
2.1.53 Which DTone Signal Need to Detect

2036
Function
When a call allows determining the fax service with the in-band fax signal
detected by the TDM terminal, this security variable determines whether the
detected DTone signal can be used to tell the service module to process the fax
service.
Default Value
Detect CNG CED and V.21 signal
Value Range
Value Meaning
The system notifies the service module to process the
Only detect V.21 signal
fax service when V.21 signal is detected.
Detect CED and V.21 signal
fax service when the CED or V.21 signal is detected.
2-47

Value Meaning
Only detect V.21 signal
fax service when V.21 signal is detected.
Detect CNG, CED and V.21 signal fax service when the CNG, CED or V.21 signal is
detected.

This security variable is valid when security variable
Continue to Detect DTone After “Which DTone Signal Need to Detect” is set to “Detect
CED is Detected CED and V.21 Signal” or “Detect CNG, CED and V.21
Signal”.
2.1.54 Ratio between Max-Forwards and Hop Counter

2107
Function
Parameter Max-Forward defined in the SIP protocol and parameter Hop Counter
defined in the ISUP protocol describe the maximum number of forwardings so as
to prevent loopback. This security variable is used to configure the ratio between
Max-Forwards and Hop Counter.
Default Value
Value Range
[1, 32]
2.2 Service Control Function Set

Table 2 lists the security variables displayed in the Service Control Function Set
tab page.
TABLE 2 SECURITY V ARIABLES DISPLAYED IN THE SERVICE CONTROL FUNCTION SET TAB
P AGE

Need Terminal for SIP in and SIP Out 2-49
2-48


Support Routing by Dialed Number Length 2-49
Not Pass Through Signal's Free Charge Indication 2-50
Control Countering of Answer Times 2-51
Use Satellite Circuit for ISUP 2-51
Support Routing by Calling Number 2-52
Priority to Use T38 Fax 2-52
Continue to Detect DTone After CED Is Detected 2-53
VAD Controlled When Alerting 2-53
Incoming Toll End Call Request Caller Category When it is Unknown 2-54
2.2.1 Need Terminal for SIP in and SIP Out

185
Function
This security variable sets whether to create terminals for incoming/outgoing SIP
calls.
z If only some incoming/outgoing SIP calls requires a terminal, disable this security
variable, and then select creating a terminal in number analysis.
z If all incoming/outgoing SIP calls require a terminal, enable this security variable.
Default Value
No
Value Range
Value Meaning
This office transparently transmits media instead of creating a
No
terminal for the incoming/outgoing SIP call.
Yes This office creates a terminal for the incoming/outgoing SIP call.
2.2.2 Support Routing by Dialed Number Length

186
2-49

Function
Generally, the number analysis only matches the longest number instead of
checking the minimum bit length and the maximum bit length in the number
analysis configuration. Routing by number length is allowed in the new service
analyzer. This security variable sets whether to support routing by number length
in the new service analyzer.
Default Value
No
Value Range
Value Meaning
No All analyzers perform routing according to the longest number.
The new service analyzer performs routing according to the number
Yes
length.
2.2.3 Not Pass Through Signal's Free Charge Indication

187
Function
This security variable specifies whether to transparently transmit the free-phone

indication from the backward office to the forward office.
If this office needs not to perform special processing on the free-phone indication
from the backward office, we recommend transparently transmitting it to the
forward office.
Default Value
No
Value Range
Value Meaning
Yes The system does not transparently transmit the free-phone indication.
No The system transparently transmits the free-phone indication.
2-50

2.2.4 Control Countering of Answer Times

189
Function
This security variable specifies whether to count it as being answered on receipt

of an Answer signal, No Charge (ANN) message.
Default Value
Yes
Value Range
Value Meaning
No On receipt of an ANN message, the system counts it as no response.
On receipt of an ANN message, the system counts it as being
Yes
answered.
2.2.5 Use Satellite Circuit for ISUP

1806
Function
This security variable specifies whether to select a satellite circuit to connect the
incoming ISUP call.
Default Value
Yes
Value Range
Value Meaning
Yes The system supports selecting a satellite circuit for call connection.
The system does not support selecting a satellite circuit for call
No
connection.
2-51

2.2.6 Support Routing by Calling Number

483
Function
Calling route enforcement means that the system can get the Digit Analysis
Selector (DAS) of the called number according to the calling number, thus routing
the call by calling number.
During a local-office-originated call, the system analyzes the calling number
according to "DAS 17 (Common Calling Subscriber)" in the VMSC configuration to
get the DAS of the called number. During an incoming call, the system analyzes
the calling number according to "Calling DAS" in the SIP office configuration or
“Calling-Number Route Selector” in the trunk group configuration to get the DAS
of the called number.
Default Value
No
Value Range
Value Meaning
No Calling number route enhancement not supported
Yes Calling number route enhancement supported
2.2.7 Priority to Use T38 Fax

2037
Function
This security variable sets whether to support the function of using type T38 for
the Fax service in precedence.
Default Value
No
Value Range
Value Meaning
2-52

The system uses type T30 when the service module delivers the Fax type
No
and the peer end does not specify which type is used.
The system uses type T38 in precedence when the service module delivers
Yes
the Fax type and the peer end does not specify which type is used.
2.2.8 Continue to Detect DTone After CED Is Detected

2038
Function
This security variable specifies whether to continue detecting the DTone signals
after the CED signals are detected to determine whether the Fax service really
starts.
Default Value
No
Value Range
Value Meaning
After receiving the message of the CED signals being detected from the
No MGW, the system regards that the Fax service starts, and sends a request of
stopping detecting signals.
After receiving the message of the CED signals being detected from the
Yes MGW, the system keeps detecting the signals from the MGW to wait for the
DTone signal.
2.2.9 VAD Controlled When Alerting

1939
Function
When a call is alerting, the MSCS determines whether to tell the MGW to enable
the VAD function according to this security variable.
Default Value
No
2-53

Value Range
Value Meaning
The system notifies the MGW to enable the VAD function in alerting
No
status.
The system does not notify the MGW to enable the VAD function in
Yes
alerting status.

VAD Controlled by Security variable “VAD Controlled When Alerting” is valid only after
MSCe security variable “VAD Controlled by MSCe” is enabled.
2.2.10 Incoming Toll End Call Request Caller Category When it is

Unknown
2063
Function
During the ISUP/TUP/BICC incoming call, the system performs the following
special processing according to this security variable when the number analysis is
completed if the local office is a tandem and toll terminated office. If the calling
category is unknown, request the category of the calling number. If the request
operation fails, set it to “Normal subscriber”.
Default Value
Yes
Value Range
Value Meaning
The system does not perform a special processing on the category
No
of the calling number.
The system performs a special processing on the category of the
Yes
calling number if the condition is met.
2.3 Other Variables

Table 3 lists the security variables displayed in the Other Variable tab page.
2-54

TABLE 3 SECURITY V ARIABLES DISPLAYED IN THE OTHER V ARI ABLE TAB P AGE
Security Variable Page No

Max Count of Message to OMC 2-56
Alarm Count of Message to OMC 2-57
Open MGW User Trace Function 2-58
Allowed Fail Count Every 10 Heart Beat of Dual Home 2-58
Traffic Control 2-59
Traffic Control's Priority 2-59
Call Service Control Number Type 2-60
The Length of Called Number in Sending 2-60
Equivalent CPU of Location Update 2-60
Equivalent CPU of Authentication 2-61
Equivalent CPU of SMS(MO) 2-61
Equivalent CPU of SMS(MT) 2-62
Equivalent CPU of 2G Normal Call (MO) 2-62
Equivalent CPU of 2G Normal Call (MT) 2-63
Equivalent CPU of 3G Normal Call (MO) 2-63
Equivalent CPU of 3G Normal Call (MT) 2-64
Equivalent CPU of GMSC 2-64
Equivalent CPU of SMS (CAMEL) 2-65
Equivalent CPU of Call (CAMEL) 2-65
Equivalent CPU of ISUP/TUP Incoming 2-65
Equivalent CPU of ISUP/TUP Outgoing 2-66
Equivalent CPU of BICC (CMN) Incoming 2-66
Equivalent CPU of BICC(CMN) Outgoing 2-67
Equivalent CPU of BICC (TSN) Incoming 2-67
Equivalent CPU of BICC (TSN) Outgoing 2-68
Equivalent CPU of SIP Incoming 2-68
Equivalent CPU of SIP Outgoing 2-69
Equivalent CPU of CAS Incoming 2-69
Equivalent CPU of CAS Outgoing 2-69
Equivalent CPU of PRI Incoming 2-70
Equivalent CPU of PRI Outgoing 2-70
Equivalent CPU of VIG Incoming 2-71
Equivalent CPU of VIG Outgoing 2-71
Equivalent CPU of HO Intra 2-72
Equivalent CPU of HO Out 2-72
2-55


Equivalent CPU of HO In 2-72
Equivalent CPU of BSSAP Service Request 2-73
Equivalent CPU of BSSAP Location Update 2-73
Equivalent CPU of BSSAP HO 2-74
Equivalent CPU of BCBM 2-74
Equivalent CPU of MCFEquivalent CPU of USSD 2-75
Equivalent CPU of LCS 2-75
Equivalent CPU of PBRT 2-76
Equivalent CPU of Adding 2G MO Terminal 2-76
Equivalent CPU of Adding 2G MT Terminal 2-76
Equivalent CPU of Adding 2G HO Terminal 2-77
Equivalent CPU of Adding 3G HO Terminal 2-77
Equivalent CPU of Adding NNI Incoming Terminal 2-78
Equivalent CPU of Adding NNI Outgoing Terminal 2-78
Equivalent CPU of Adding NNI TDM Terminal 2-79
Equivalent CPU of Adding 3G ATM MO Terminal 2-79
Equivalent CPU of Adding 3G ATM MT Terminal 2-80
Equivalent CPU of Adding 2/3G IP MO Terminal 2-80
Equivalent CPU of Adding 2/3G IP MT Terminal 2-81
Max Congest Module Weighted Ratio 2-82
Local Office Congest Stat Interval (100 ms) 2-82
Congesting Send Overload to RNC (BSC) Message Number 2-83
Congesting Send Overload to RNC (BSC) Minimum Level 2-83
MSC Reset Times 2-83
MSC Reset Circuit Times 2-84
Whether to Send Confusion Message 2-84
Whether Control Downlink Message According the Congest Level of 2-85
RNC/BSC/MGW
Mc Number Trace for User Plane Tool Is Needed 2-85
Support SIP Message 2-86
Report SIP Edit Message 2-86
Traffic Control Period 2-87
2.3.1 Max Count of Message to OMC

17
2-56

Function
This security variable specifies the maximum data traffic between the front end
and the back end during failure observation and signaling trace. This prevents the
front-end CPU occupancy from being too high because of large data traffic, which
affects service processing on the front end. When the data traffic between the
front end and the back end is greater than the reference value, the system stops
the failure observation task or the signaling trace task, and gives an alarm on the
window of the OMM main process client.
Default Value
1000
Value Range
[10, 1000]
Unit: message/second

The value of security variable “Max Count of Message to OMC” must be
Alarm Count of
greater than the value of security variable “Alarm Count of Message to
Message to OMC
OMC”.
2.3.2 Alarm Count of Message to OMC

18
Function
This security variable indicates that the system reports an alarm on the back-end
interface when the data traffic between the front end and the back end reaches
the preset value.
Default Value
800
Value Range
[10, 800]
Unit: message/second
2-57

2.3.3 Open MGW User Trace Function
20
Function
This security variable specifies whether the MSCS brings signaling trace
reference to the MGW, that is, controlling the MGW to perform the subscriber
signaling trace.
Default Value
Disable
Value Range
Value Meaning
Disable Tracing subscriber signaling on the MGW not supported.
Enable Tracing subscriber signaling on the MGW supported.

Mc Number Trace for User Plane Only when this security variable is set to Yes, security
Tool Is Needed variable “Open MGW User Trace Function” is valid.
2.3.4 Allowed Fail Count Every 10 Heart Beat of Dual Home

21
Function
In a disaster-recovery environment, it is assumed that the heartbeat line between

the active and standby devices is disconnected when the number of the
successive heartbeat detection failures between the active and standby devices
reach the preset value. This security variable flexibly sets the number of permitted
heartbeat detection failures to detect the communication status of the active and
standby devices.
In most cases, the Default Value is used. You can appropriately set a larger value
when the actual network condition is poor.
2-58

Default Value
Value Range
[1, 5]
2.3.5 Traffic Control

28
Function
This security variable specifies whether the system supports traffic control of the
local office.
Default Value
Disable
Value Range
Value Meaning
Disable The system does not control local office traffic.
The system supports traffic control on destination codes and trunk
Enable
groups.
2.3.6 Traffic Control's Priority

29
Function
This security variable sets the priority level for traffic control. Traffic control is
divided into static traffic control based on man-machine command and dynamic
traffic control based on traffic statistics.
Default Value
Manual command
Value Range
Value Meaning
2-59

Manual Command Traffic control based on the man-machine command is preferred.

Traffic Statistic Traffic control based on traffic statistics is preferred.
2.3.7 Call Service Control Number Type

30
Function
This security variable specifies the number types used for traffic control.
Default Value
Called number
Value Range
Value Meaning
During traffic statistics report, the called number is filled in with the
Called Number system-connected number. Meanwhile, the destination code is filled in
with the system-connected number during traffic control.
During traffic statistics report, the called number is filled in with the
Dialed Number subscriber-dialed number. Meanwhile, the destination code is filled in
with the subscriber-dialed number during traffic control.
2.3.8 The Length of Called Number in Sending

1819
Function
This security variable specifies the length of the called number to be transmitted.
Default Value
15
Value Range
[1, 48]
2.3.9 Equivalent CPU of Location Update
1557
2-60

Function
This security variable is a weighting coefficient. During the global flow calculation,
it weights the CPU resource consumed by the location update service so as to get
the total equivalent CPU consumption of the current system for the convenient of
performing the configuration on the background and restricting the global traffic by
manual.
Default Value
Value Range
[0, 100]
2.3.10 Equivalent CPU of Authentication

1558
Function
it weights the CPU resource consumed by the authentication service so as to get
the whole equivalent CPU consumption of the current system, perform the
configuration on the background and restrict the global traffic by manual.
Default Value
Value Range
[0, 100]
2.3.11 Equivalent CPU of SMS(MO)

1559
Function
it weights the CPU resource consumed by the short message(MO) service so as
2-61

to get the whole equivalent CPU consumption of the current system, perform the
Default Value
Value Range
[0, 100]
2.3.12 Equivalent CPU of SMS(MT)

1560
Function
it weights the CPU resource consumed by the short message (MT) service so as
Default Value
Value Range
[0, 100]
2.3.13 Equivalent CPU of 2G Normal Call (MO)
1561
Function
it weights the CPU resource consumed by 2G normal call (MO) service so as to
get the whole equivalent CPU consumption of the current system, perform the
2-62

Default Value
Value Range
[0, 100]
2.3.14 Equivalent CPU of 2G Normal Call (MT)

1562
Function
This security variable is a weighting coefficient.

During the global flow calculation, it weights the CPU resource consumed by 2G
normal call (MT) service so as to get the whole equivalent CPU consumption of
the current system, perform the configuration on the background and restrict the
global traffic by manual.
Default Value
Value Range
[0, 100]
2.3.15 Equivalent CPU of 3G Normal Call (MO)

1563
Function
it weights the CPU resource consumed by 3G normal call (MO) service so as to
Default Value
2-63

Value Range
[0, 100]
2.3.16 Equivalent CPU of 3G Normal Call (MT)

1564
Function
it weights the CPU resource consumed by 3G normal call (MT) service so as to
Default Value
Value Range
[0, 100]
2.3.17 Equivalent CPU of GMSC

1565
Function
it weights the CPU resource consumed by the GMSC service so as to get the
whole equivalent CPU consumption of the current system, perform the
Default Value
Value Range
[0, 100]
2-64

2.3.18 Equivalent CPU of SMS (CAMEL)

1566
Function
it weights the CPU resource consumed by the short message(CAMEL) service so
as to get the whole equivalent CPU consumption of the current system, perform
the configuration on the background and restrict the global traffic by manual.
Default Value
Value Range
[0, 100]
2.3.19 Equivalent CPU of Call (CAMEL)

1567
Function
it weights the CPU resource consumed by the CAMEL call service so as to get the
Default Value
Value Range
[0, 100]
2.3.20 Equivalent CPU of ISUP/TUP Incoming

1568
2-65

Function
it weights the CPU resource consumed by the ISUP/TUP incoming call service so
Default Value
Value Range
[0, 100]
2.3.21 Equivalent CPU of ISUP/TUP Outgoing

1569
Function
it weights the CPU resource consumed by the ISUP/TUP outgoing call service so
Default Value
Value Range
[0, 100]
2.3.22 Equivalent CPU of BICC (CMN) Incoming

1570
Function
it weights the CPU resource consumed by the BICC(CMN) incoming call service
so as to get the whole equivalent CPU consumption of the current system,
2-66

perform the configuration on the background and restrict the global traffic by
manual.
Default Value
Value Range
[0, 100]
2.3.23 Equivalent CPU of BICC(CMN) Outgoing

1571
Function
it weights the CPU resource consumed by the BICC(CMN) outgoing call service
manual.
Default Value
Value Range
[0, 100]
2.3.24 Equivalent CPU of BICC (TSN) Incoming

1572
Function
it weights the CPU resource consumed by the BICC(TSN) incoming call service
manual.
2-67

Default Value
Value Range
[0, 100]
2.3.25 Equivalent CPU of BICC (TSN) Outgoing

1573
Function
it weights the CPU resource consumed by the BICC(TSN) outgoing call service so
Default Value
Value Range
[0, 100]
2.3.26 Equivalent CPU of SIP Incoming

1574
Function
it weights the CPU resource consumed by the SIP incoming call service so as to
Default Value
Value Range
[0, 100]
2-68

2.3.27 Equivalent CPU of SIP Outgoing

1575
Function
it weights the CPU resource consumed by the SIP outgoing call service so as to
Default Value
Value Range
[0, 100]
2.3.28 Equivalent CPU of CAS Incoming

1576
Function
it weights the CPU resource consumed by the CAS incoming call service so as to
Default Value
Value Range
[0, 100]
2.3.29 Equivalent CPU of CAS Outgoing

1577
2-69

Function
it weights the CPU resource consumed by the CAS outgoing call service so as to
Default Value
Value Range
[0, 100]
2.3.30 Equivalent CPU of PRI Incoming

1578
Function
it weights the CPU resource consumed by the PRI incoming call service so as to
Default Value
Value Range
[0, 100]
2.3.31 Equivalent CPU of PRI Outgoing

1579
Function
it weights the CPU resource consumed by the PRI outgoing call service so as to
2-70

Default Value
Value Range
[0, 100]
2.3.32 Equivalent CPU of VIG Incoming

1580
Function
it weights the CPU resource consumed by the VIG incoming call service so as to
Default Value
Value Range
[0, 100]
2.3.33 Equivalent CPU of VIG Outgoing

1581
Function
it weights the CPU resource consumed by the VIG outgoing call service so as to
Default Value
Value Range
[0, 100]
2-71

2.3.34 Equivalent CPU of HO Intra

1582
Function
it weights the CPU resource consumed by the intra-office HO service so as to get
Default Value
Value Range
[0, 100]
2.3.35 Equivalent CPU of HO Out

1583
Function
it weights the CPU resource consumed by the interoffice HO service so as to get
Default Value
Value Range
[0, 100]
2.3.36 Equivalent CPU of HO In

1584
2-72

Function
it weights the CPU resource consumed by the incoming service of interoffice HO
manual.
Default Value
Value Range
[0, 100]
2.3.37 Equivalent CPU of BSSAP Service Request

1585
Function
it weights the CPU resource consumed by the request service of BSSAP so as to
Default Value
Value Range
[0, 100]
2.3.38 Equivalent CPU of BSSAP Location Update

1586
Function
it weights the CPU resource consumed by the location update service of BSSAP
2-73

manual.
Default Value
Value Range
[0, 100]
2.3.39 Equivalent CPU of BSSAP HO

1587
Function
it weights the CPU resource consumed by the handover service of BSSAP so as
Default Value
Value Range
[0, 100]
2.3.40 Equivalent CPU of BCBM

1588
Function
it weights the CPU resource consumed by the BCBM service so as to get the
Default Value
2-74

Value Range
[0, 100]
2.3.41 Equivalent CPU of MCF

1589
Function
it weights the CPU resource consumed by the MCF service so as to get the whole
equivalent CPU consumption of the current system, perform the configuration on
the background and restrict the global traffic by manual.
Default Value
Value Range
[0, 100]
2.3.42 Equivalent CPU of USSD

1590
Function
it weights the CPU resource consumed by the USSD service so as to get the
Default Value
Value Range
[0, 100]
2-75

2.3.43 Equivalent CPU of LCS

1591
Function
it weights the CPU resource consumed by the LCS service so as to get the whole
equivalent CPU consumption of the current system, perform the configuration on
the background and restrict the global traffic by manual.
Default Value
Value Range
[0, 100]
2.3.44 Equivalent CPU of PBRT

1592
Function
it weights the CPU resource consumed by the PBRT service so as to get the
Default Value
Value Range
[0, 100]
2.3.45 Equivalent CPU of Adding 2G MO Terminal

1593
2-76

Function
it weights the CPU resource consumed by the “Adding 2G MO Terminal” service
manual.
Default Value
Value Range
[0, 100]
2.3.46 Equivalent CPU of Adding 2G MT Terminal

1594
Function
it weights the CPU resource consumed by the “Adding 2G MT Terminal” service
manual.
Default Value
Value Range
[0, 100]
2.3.47 Equivalent CPU of Adding 2G HO Terminal

1595
Function
it weights the CPU resource consumed by the “Adding 2G HO Terminal” service
2-77


manual.
Default Value
Value Range
[0, 100]
2.3.48 Equivalent CPU of Adding 3G HO Terminal

1596
Function
it weights the CPU resource consumed by the “Adding 3G HO Terminal” service
manual.
Default Value
Value Range
[0, 100]
2.3.49 Equivalent CPU of Adding NNI Incoming Terminal

1597
Function
it weights the CPU resource consumed by the “Adding NNI Incoming Terminal”
service so as to get the whole equivalent CPU consumption of the current system,
manual.
2-78

Default Value
Value Range
[0, 100]
2.3.50 Equivalent CPU of Adding NNI Outgoing Terminal

1598
Function
it weights the CPU resource consumed by the “Adding NNI Outgoing Terminal”
manual.
Default Value
Value Range
[0, 100]
2.3.51 Equivalent CPU of Adding NNI TDM Terminal

1599
Function
it weights the CPU resource consumed by the “Adding NNI TDM Terminal” service
manual.
Default Value
2-79

Value Range
[0, 100]
2.3.52 Equivalent CPU of Adding 3G ATM MO Terminal

1600
Function
it weights the CPU resource consumed by the “Adding 3G ATM MO Terminal”
manual.
Default Value
Value Range
[0, 100]
2.3.53 Equivalent CPU of Adding 3G ATM MT Terminal

1601
Function
it weights the CPU resource consumed by the “Adding 3G ATM MT Terminal”
manual.
Default Value
Value Range
[0, 100]
2-80

2.3.54 Equivalent CPU of Adding 2/3G IP MO Terminal

1602
Function
it weights the CPU resource consumed by the “Adding 2/3G IP MO Terminal”
manual.
Default Value
Value Range
[0, 100]
2.3.55 Equivalent CPU of Adding 2/3G IP MT Terminal

1603
Function
it weights the CPU resource consumed by the “Adding 2/3G IP MT Terminal”
manual.
Default Value
Value Range
[0, 100]
2-81

2.3.56 Max Congest Module Weighted Ratio

718
Function
When computing the global congestion conditions, the system weights the module
with the most serious congestion, thus avoiding affecting the normal operation of
the system because of unbalanced load sharing or hardware fault. This security
variable sets the weighting coefficient of the module with the most serious
congestion.
Default Value
30
Value Range
[0, 100]
2.3.57 Local Office Congest Stat Interval (100 ms)

720
Function
This security variable sets the period of load statistics of the local office. When a
period ends, the OMP computes the congestion conditions, total traffic and traffic
of each service of this system within this period according to the report of each
CMP. The result is the basis of load control in the next period.
Default Value
50
Value Range
[0, 4294967295]
Unit: 100 ms
2-82

2.3.58 Congesting Send Overload to RNC (BSC) Message Number

787
Function
This security variable sets the number of messages received when the Iu/A
interface reaches a certain congestion level. When the Iu/A interface has received
this number of messages, it sends an OVERLOAD message to the RNC.
Default Value
300
Value Range
[0, 65535]
2.3.59 Congesting Send Overload to RNC (BSC) Minimum Level

788
Function
This security variable sets the lowest congestion level when the Iu/A interface
sends an OVERLOAD message.
Default Value
255
Value Range
Value Meaning
0 No congestion occurs.
1 Overload is sent on congestion level 1.
2 Overload is sent on congestion level 2.
255 Overload is not sent when congestion occurs.
2.3.60 MSC Reset Times

797
2-83

Function
This security variable sets the maximum number of the RESET messages that the
MSCS sends to the BSC in case of no response from the peer end.
Default Value
Value Range
[1, 8]
2.3.61 MSC Reset Circuit Times

798
Function
This security variable sets the number of circuit reset attempts of the MSC.
Default Value
Value Range
[1, 8]
2.3.62 Whether to Send Confusion Message

799
Function
This security variable sets whether to send CFU messages.
Default Value
No
Value Range
Value Meaning
No No CFU message is sent.
2-84

Value Meaning
No No CFU message is sent.
Yes CFU messages are sent.
2.3.63 Whether Control Downlink Message According the Congest

Level of RNC/BSC/MGW
874
Function
If the system supports controlling downlink messages according to the congestion

level of the MGW/RNC/BSC, it will observe the overload message sent from the
MGW/RNC/BSC message. Once the local office finds the congestion indication
from its adjacent office, it will restrict the messages sent to this adjacent office.
Default Value
No
Value Range
Value Meaning
Controlling downlink messages according to the congestion level not
No
supported.
Controlling downlink messages according to the congestion level
Yes
supported.
2.3.64 Mc Number Trace for User Plane Tool Is Needed

1225
Default Value
No
Function
This security variable specifies whether the user plane of the Mc interface
supports number portability.
2-85

Value Range
Value Meaning
No The user plane of the Mc-interface does not support number portability.
Yes The user plane of the Mc interface supports number portability.
Related Security Variable

Open MGW User Only when this security variable is enabled, the user plane of the Mc
Trace Function interface can support number portability.
2.3.65 Support SIP Message Edit

2103
Default Value
Not support
Function
If this security variable is enabled, the system edits the SIP messages that this
office sends or receives according to the preset editing policy. If this security
variable is disabled, the system cannot edit the SIP messages.
Value Range
Value Meaning
Not support The system cannot edit the SIP messages.
The system can edit the SIP messages according to preset editing
Support
policy.
2.3.66 Report SIP Edit Message

2134
Default Value
No
2-86

Function
This security variable determines whether to report editable messages of the SIP
signaling.
Value Range
Value Meaning
No The system does not report editable messages of the SIP signaling.
Yes The system reports editable messages of the SIP signaling.
2.3.67 Traffic Control Period

2146
Default Value
10
Function
This security variable is used for the traffic control function.It calculates the total
traffic of a whole office or a single service in a measurement period.
Value Range
[1, 600]
Unit: second
2.4 Other Function Set

Table 4 lists the security variables displayed in the Other Function Set tab page.
TABLE 4 SECURITY V ARIABLES IN OTHER FUNCTION SET

Not Handle the Clock Modification Notification Event for Call Service 2-88
Play Change Number Tone for Other Bureau Forward Call 2-88
Simplify the Control of EC Indication 2-89
Report Alert-Level Fail Information in Fail Observe 2-89
Support Auto Delete Dead Sub-Data Area 2-90
Include ReconnectB Traffic 2-90
2-87


Support DNS/ENUM Function 2-91
DNS Cache Preload After TTL for the Records with High Hit Count Rate 2-91
Cache Still in Valid After TTL 2-92
2.4.1 Not Handle the Clock Modification Notification Event for Call
Service
193
Function
This security variable specifies whether to adjust the time for the call service after
the absolute time of the system is adjusted.
Default Value
No
Value Range
Value Meaning
No The system adjusts the absolute time of the call service.
Yes The system does not adjust the absolute time of the call service.
2.4.2 Play Change Number Tone for Other Bureau Forward Call
1802
Function
If the CHGN (Number Change by the Subscriber) option is selected in the

number analysis configuration, this security variable determines whether to play
change-number-tone during a forwarded incoming call.
Default Value
Yes
Value Range
Value Meaning
2-88

The system directly connects the forwarded incoming call instead of

No
playing tones.
The system plays the change number tone for a forwarded incoming
Yes
call.
2.4.3 Simplify the Control of EC Indication

1922
Function
This security variable determines whether the Echo Canceller (EC) control
function is processed in simplified mode.
Default Value
No
Value Range
Value Meaning
The system performs negotiation of EC control according to the ISUP
No
protocol.
When the trunk configuration contains the EC configuration, the EC is
Yes opened for TDM terminals. When the EC is closed in the trunk configuration,
the EC is closed for TDM terminals.
2.4.4 Report Alert-Level Fail Information in Fail Observe

1965
Function
This security variable specifies whether to report failure information of Alert level
in the failure observation system.
Default Value
No
Value Range
Value Meaning
2-89

The system does not report the failure information of the alert level in
No
the failure observation system.
The system reports the failure information of the alert level in the
Yes
failure observation system.
2.4.5 Support Auto Delete Dead Sub-Data Area

1981
Function
This security variable specifies whether to release the suspended sub-data-areas

when scanning and detecting sub-data-areas.
Default Value
No
Value Range
Value Meaning
The system only resets the timer without any processing when the timer for sub-
No
data-area scanning expires.
The system releases the suspended sub-data-areas detected during scanning
Yes
when the timer for sub-data-area scanning expires.
2.4.6 Include ReconnectB Traffic

2026
Function
This security variable specifies whether to include the previous outgoing traffic
when a call exits the office again because of automatic rerouting, call forwarding,
MAH, number portability and other situations
Default Value
No
Value Range
Value Meaning
No Statistics including ReconnectB not supported.
2-90

Value Meaning
No Statistics including ReconnectB not supported.
Yes Statistics including ReconnectB supported.
2.4.7 Support DNS/ENUM Function
2050
Function
This security variable specifies whether to support the functions of Domain Name
Server (DNS) and E.164 Number Mapping (ENUM).
Default Value
No
Value Range
Value Meaning
No The DNS and ENUM functions not supported
Yes The DNS and ENUM functions supported

DNS Cache Preload After TTL for the When security variable “Support DNS/ENUM
Records With High Hit Count Rate Function” is set to Yes, security variables “DNS
Cache Preload After TTL for the Records With High
Cache still in Valid After TTL Hit Count Rate” and “Cache still in Valid After TTL”
are valid.
2.4.8 DNS Cache Preload After TTL for the Records with High Hit
Count Rate
2051
Function
This security variable specifies whether to pre-load the records with high hit ratio
and to automatically initiate DNS request and update the Cache status after the
Cache records in the DNS expires in the TTL.
2-91

Default Value
No
Value Range
Value Meaning
No The system does not pre-load the records with high hit ratio after TTL expires.
The system pre-loads the records with high hit ratio and automatically initiates
Yes
DNS request to this Cache and updates the Cache status.

Support DNS/ENUM Function This security variable must be enabled.
2.4.9 Cache Still in Valid After TTL

2052
Function
For the records in the Cache with TTL expiring, if security variable “Cache still in
Valid After TTL” and the address records exist in the Cache, the system
synchronously returns the address records in the Cache. If security variable
“Cache still in Valid After TTL” is not supported, the system adds this request to
the waiting list. When the records in the Cache are unavailable, the system
initiates a DNS query, and asynchronously returns the address records.
Default Value
No
Value Range
Value Meaning
No The cache still being valid after expiration of TTL not supported.
Yes The cache still being valid after expiration of TTL supported.

Support DNS/ENUM Function This security variable must be enabled.
2-92

2.5 License Function Set

Table 5 lists the security variables displayed in the License Function Set tab
page.
TABLE 5 SECURITY V ARIABLES DISPLAYED IN THE LICENSE TAB P AGE

Support Failed Call Bill 2-94
Support Lawful Interception 2-94
Voice Service Turn to Fax Service 2-94
Support MGCF 2-95
VAD Controlled by MSCe 2-95
Black and White List Function 2-96
Authentication for Other Network User Function 2-96
Authentication for Trunk Group Function 2-97
Support MLPP Service 2-97
Support Direct Message 2-98
Support MSC Pool 2-98
Support BSC CIC Managed by MGW 2-99
Support Dual Home 2-99
Support Rf Interface 2-100
Support VLR Dump 2-100
Support AoIP 2-101
Support CMN 2-101
Support Iu Over IP 2-101
Whether to Use MAP Policing Flag 2-102
Whether to Support Mobile Number Portable 2-102
Whether to Support Category Route 2-103
Whether Support DTMF Limit for MT Calling Number 2-103
Whether to Enable MAP OPC Function 2-104
Whether to Enable VLR CAMEL Roaming Function 2-104
Ability of Prior Access 2-104
Whether to Enable Forced Release Call Function 2-105
Whether to Play Announcement After Temporarily Disconnection 2-106
Support ICS 2-106
Whether to Support Suppression of Announcement when T-CSI 2-107
Support Fraud Profile Function 2-107
Support Access Bearer Statistic Test 2-108
2-93

2.5.1 Support Failed Call Bill
584
Function
This security variable specifies whether to support the failure CDR service.
Default Value
No
Value Range
Value Meaning
No Failure CDR service not supported.
Yes Failure CDR service supported.
2.5.2 Support Lawful Interception

585
Function
This security variable specifies whether to support lawful interception.
Default Value
No
Value Range
Value Meaning
No Lawful interception not supported.
Yes Lawful interception supported.
2.5.3 Voice Service Turn to Fax Service

607
2-94

Function
This security variable specifies whether to support converting the voice service to
the facsimile service.
Default Value
No
Value Range
Value Meaning
The system does not support converting the voice service to the
No
facsimile service.
The system supports converting the voice service to the facsimile
Yes
service.
2.5.4 Support MGCF

608
Function
This security variable specifies whether this office supports the MGCF function.
Default Value
No
Value Range
Value Meaning
No MGCF function not supported.
Yes MGCF function supported.
2.5.5 VAD Controlled by MSCe

614
Function
This security variable specifies whether to support flexible VAD control.
2-95

Default Value
No
Value Range
Value Meaning
No Flexible VAD control not supported.
Yes Flexible VAD control supported.

VAD Controlled When security variable “VAD Controlled by MSCe” is enabled, this
When Alerting security variable is valid.
2.5.6 Black and White List Function
616
Function
This security variable specifies whether to support the black/white list function.
Default Value
No
Value Range
Value Meaning
No The black/white list function not supported.
Yes The black/white list function supported.
2.5.7 Authentication for Other Network User Function
617
Function
This security variable specifies whether to support authentication of the

subscribers of other networks.
2-96

Default Value
No
Value Range
Value Meaning
No Authentication of the subscriber of other networks not supported.
Yes Authentication of the subscriber of other networks supported.
2.5.8 Authentication for Trunk Group Function
618
Function
This security variable specifies whether to support authentication for trunk groups.
Default Value
No
Value Range
Value Meaning
No Authentication for trunk group not supported.
Yes Authentication for trunk group supported.
2.5.9 Support MLPP Service

1919
Function
This security variable specifies whether to support the Enhanced Multi-Level

Precedence and Pre-emption (EMLPP) service.
Default Value
No
Value Range
Value Meaning
2-97

No EMLPP service not supported.

Yes EMLPP service supported.
2.5.10 Support Direct Message

2016
Function
This security variable specifies whether to support the direct message function.
Default Value
No
Value Range
Value Meaning
No Direct message function not supported.
Yes Direct message supported.
2.5.11 Support MSC Pool

2017
Function
This security variable specifies whether to support the MSC pool function.
Default Value
No
Value Range
Value Meaning
No MSC pool function not supported.
Yes MSC pool function supported.

Whether to Allow Paging in Search Mode for MSC Pool These security variables are valid
l h th MSC lf ti
2-98

Time Interval of Heart Beat Test for MSC Pool User

Data Synchronization (in Sec)
Allowed Heart Beat Abnormal Times for MSC Pool User
Data Synchronization
Paging Protect Time in MSC Pool
2.5.12 Support BSC CIC Managed by MGW

2018
Function
This security variable specifies whether to support managing circuits on the MGW.
When this security variable is enabled, the circuits the A interface are allocated on
the MGW, therefore, configuring the A interface trunk on the MGW is required.
After that, the trunk configuration of the A interface of the MSCS is not valid any
longer.
Default Value
No
Value Range
Value Meaning
No Managing circuits on the MGW not supported.
Yes Managing circuits on the MGW supported.
2.5.13 Support Dual Home

2019
Function
This security variable specifies whether the system supports the dual-homing
function.
Default Value
No
2-99

Value Range
Value Meaning
No The dual-homing function not supported.
Yes The dual-homing function supported.
2.5.14 Support Rf Interface

2020
Function
This security variable specifies whether the MGCF supports the Rf interface (for
off-line billing).
Default Value
No
Value Range
Value Meaning
No The MGCF does not support the Rf interface.
Yes The MGCF supports the Rf interface.
2.5.15 Support VLR Dump

2021
Function
This security variable specifies whether to support the VLR Dump function.
Default Value
No
Value Range
Value Meaning
No VLR dump not supported.
Yes VLR dump supported.
2-100

2.5.16 Support AoIP

2022
Function
This security variable specifies whether the A interface supports the AoIP function,
including AoIP of China Mobile and AoIP of 3GPP.
Default Value
No
Value Range
Value Meaning
No The AoIP function not supported.
Yes The AoIP function supported.
2.5.17 Support CMN

2023
Function
This security variable specifies whether the MGCF supports the Call Mediation
Nodes (CMN) function of SIP.
Default Value
No
Value Range
Value Meaning
No The MGCF does not support the CMN function.
Yes The MGCF supports the CMN function.
2.5.18 Support Iu Over IP

2024
2-101

Function
This security variable specifies whether to support the Iu over IP function.
Default Value
No
Value Range
Value Meaning
No Iu over IP not supported.
Yes Iu over IP supported.
2.5.19 Whether to Use MAP Policing Flag

676
Function
This security variable specifies whether to use the MAP Policing function.
Default Value
No
Value Range
Value Meaning
No MAP policing not used.
Yes MAP policing used.
2.5.20 Whether to Support Mobile Number Portable

1140
Function
This security variable specifies whether to support the Mobile Number Portability
(MNP) function.
Default Value
No
2-102

Value Range
Value Meaning
No MNP not supported.
Yes MNP supported.
2.5.21 Whether to Support Category Route

1197
Function
This security variable specifies whether to select a calling route according to the
category.
Default Value
No
Value Range
Value Meaning
No The system does not select a calling route according to the category.
Yes The system selects a calling route according to the category.
2.5.22 Whether Support DTMF Limit for MT Calling Number

1213
Function
This security variable specifies whether to enable the DTMF calling white list
function.
Default Value
No
Value Range
Value Meaning
No The system disables the DTMF calling white-list function.
Yes The system enables the DTMF calling white-list function.
2-103

2.5.23 Whether to Enable MAP OPC Function
1216
Function
This security variable specifies whether to enable the MAP OPC function.
Default Value
No
Value Range
Value Meaning
No The system disables the MAP OPC function.
Yes The system enables the MAP OPC function.
2.5.24 Whether to Enable VLR CAMEL Roaming Function
1218
Function
This security variable specifies whether to enable the VLR CAMEL roaming
function.
Default Value
No
Value Range
Value Meaning
No The system disables the VLR CAMEL roaming function.
Yes The system enables the VLR CAMEL roaming function.
2.5.25 Ability of Prior Access

1130
2-104

Function
This security variable specifies whether the MSCS supports the preferential
access function.
Default Value
Not support
Value Range
Value Meaning
No The MSCS does not support preferential access.
The MSCS supports preferential access. You can set the operation
Yes mode in “Service Configuration > RAB Configuration > Different
Service” in the MML Terminal window.
2.5.26 Whether to Enable Forced Release Call Function
1096
Function
This security variable specifies whether to enable the function of forcedly

releasing subscriber calls.
Default Value
0: None
Value Range
Value Meaning
0: None The function of forcedly releasing subscriber calls is disabled.
This function is enabled for all HLRs, but security variable “Forced
1: All HLR Release Call Type” determines in which service flow this function
is enabled.
This function is enabled for specific HLR(s). The specific HLR
number and the procedure for enabling this function are configured
2: Specific HLR
in Service Configuration > Call > Force Cancel Calling User in
the MML Terminal window of the main processor client.

2-105

Forced Release Call This security variable is valid only when security variable “Whether
Type to Enable Forced Release Call Function” is set to All HLR.
2.5.27 Whether to Play Announcement After Temporarily

Disconnection
1098
Function
This security variable specifies whether to plan an announcement tone after call
drop.
Default Value
No
Value Range
Value Meaning
No The system does not play an announcement tone after call drop.
Yes The system plays an announcement tone after call drop.
2.5.28 Support ICS

2129
Function
This security variable determines whether to support the ICS function.
Default Value
No
Value Range
Value Meaning
No The system does not support the ICS function.
Yes The system supports the ICS function.
2-106

2.5.29 Whether to Support Suppression of Announcement when T-

CSI
2132
Function
This security variable determines whether the MSCS supports the announcement
suppression function during the T-CSI service.
Default Value
No
Value Range
Value Meaning
The system does not support the announcement suppression
No
function during the T-CSI service.
The system supports the announcement suppression function
Yes
during the T-CSI service.
2.5.30 Support Fraud Profile Function

2133
Function
This security variable determines whether to support the Fraud Profile function.
Default Value
No
Value Range
Value Meaning
No The system does not support the Fraud Profile function.
Yes The system supports the Fraud Profile function.
2-107

2.5.31 Support Access Bearer Statistic Test

2141
Function
This security variable is the License switch of the “Access Bearer Statistic Test”
function.
If the “Access bearer statistic test” function is supported, the system performs
statistics and tests the availability of the bearer on the access side (including IP
bearer, ATM bearer, and TDM bearer when the MGW manages the A-interface
circuit in the NNSF networking mode) according to the bearer establishment
information of a real call. For the bearer with lower stability, the system reduces
the call occupancy rate so as to improve the conversation quality of the end office.
Default Value
No
Value Range
Value Meaning
The system does not support the “Access Bearer Statistic Test”
No
function.
Yes The system supports the “Access Bearer Statistic Test” function.
2-108

Chapter 3
WCN Security Variables
———————————————————————————————————————————
Table of Contents
System Control Parameters…………………………………………………………3-1

CS Security Parameter…………………………………………….….……………3-21
CS Network Entity Configuration………………………………….………………3-26
Call Control………………………………………………………….……………….3-72
3.1 System Control Parameters

Table 6 lists the security variables displayed in the System Control Parameters
tab page.
TABLE 6 SYSTEM CONTROL P AR AMETERS

Phone Number Upgrading Status Setting 3-2
Length of MSISDN Before Increasing 3-3
Position for Insertion Value 3-4
Insertion Value on Increasing 3-5
Send MAP Phase Setting 3-6
Receive MAP Phase Setting 3-7
TM Packet Size (Byte) 3-7
Duration of Call Gap Specified in Network (s) 3-8
Whether to Use ATI Prior Flag 3-8
Time Zone 3-9
ATI Send Phase 3-10
Whether to Use Call Forwarding OSB Check Control Switch 3-10
Whether to Use Register Forwarding OSB Check Control Switch 3-11
Interval of Force Location Update to HLR (Minute) 3-11
Version of TM 3-12
3-1
3-1


Whether to Enable Control Parameter of Location Reject Cause for CS 3-12
Location Reject Cause for CS 3-13
Roaming not Allowed in Cell Cause 3-13
Roaming not Allowed in LAI Cause 3-14
ARD Reject Cause in Same PLMN 3-15
ARD Reject Cause Not in Same PLMN 3-16
Whether Cell Roaming Restrict Option is Enabled in LU Process 3.1.22
Whether Cell Roaming Restrict Option is Enabled when MO Processes 3.1.23
Cause Value of Roaming Restrict by MSISDN 3-17
Support Length Coding Type 3-18
Whether USSD Service Message Sent by CN Is Used Fixed Length Encode 3-18
Location Reject Cause About ODB Roam Not Allowed 3-19
Whether to Enable Switch of the MSCNumber Coding in PSI-Rsp Msg 3-20
Is Paid Special Service Under ODB Control 3-20
3.1.1 Phone Number Upgrading Status Setting
665
Function
This security variable is only used for number expansion.
Default Value
Before update
Value Range
Value Meaning
Before upgrade Before number expansion
In the upgrade process During number expansion
After upgrade After number expansion
3-2


Length of MSISDN When security variable “Phone Number Upgrading Status Setting” is
Before Increasing set to “Before Upgrade”, it is irrelevant to security variable “Length of
MSISDN Before Increasing”.
When security variable “Phone Number Upgrading Status Setting” is
set to “In the Upgrade Process” and the length of the subscriber
MSISDN is equal to the value of security variable “Length of
MSISDN Before Increasing”, the system expands the number.
When “Phone Number Upgrading Status Setting” is set to “After
Upgrade”, the length of the subscriber MSISDN should be less than
the value of “Length of MSISDN Before Increasing”
Position for Insertion When security variable “Phone Number Upgrading Status Setting” is
Value set to “In the Upgrade Process”, security variable “Position for
Insertion Value” indicates the position of inserting the new numeric
value that is the value of security variable “Insertion Value on
Increasing”.
Insertion Value on When security variable “Phone Number Upgrading Status Setting” is
Increasing set to “In the Upgrade Process”, security variable “Insertion Value on
Increasing” specifies the new numeric value in the position specified
by security variable “Position for Insertion Value”.
3.1.2 Length of MSISDN Before Increasing

666
Function
This security variable specifies the length of the MSISDN before number
expansion. If the subscriber MSISDN contains a country code, the length is equal
to the sum of the value of “Length of MSISDN Before Increasing” and the length
of the country code.
Default Value
11
Value Range
[6, 15]
3-3


When security variable “Phone Number Upgrading Status
Setting” is set to “Before Upgrade”, the system does not perform
number expansion.
Setting” is set to “In the Upgrade Process” and the length of the
Phone Number
subscriber MSISDN is equal to the value of security variable
Upgrading Status Setting
“Length of MSISDN Before Increasing”, the system expands the
number.
upgrade”, the length of the subscriber MSISDN should be less
than the value of “Length of MSISDN Before Increasing”
Setting” is set to “In the Upgrade Process”, security variable
Position for Insertion
“Position for Insertion Value” indicates the position of inserting the
Value
new numeric value that is the value of security variable “Insertion
Value on Increasing”.
Setting” is set to “In the Upgrade Process”, security variable
Insertion Value on
“Insertion Value on Increasing” specifies the new numeric value
Increasing
in the position specified by security variable “Position for Insertion
Value”.
3.1.3 Position for Insertion Value

667
Function
This security variable specifies the position for inserting a number. We assume
that this security variable is set to N, if the subscriber MSISDN contains a country
code, the new number is inserted after the “N+length of the country code” digit of
the original number.
Default Value
Value Range
[1, 15]
3-4


Phone Number When security variable “Phone Number Upgrading Status
Upgrading Status Setting Setting” is set to “Before Upgrade”, the system does not perform
number expansion.
number.
Length of MSISDN When security variable “Phone Number Upgrading Status
Before Increasing Setting” is set to “before upgrade”, it is irrelevant to security
variable “length of MSISDN before increasing”.
Setting” is set to “In the upgrade process” and the length of the
number.
Insertion Value on When security variable “Phone Number Upgrading Status
Increasing Setting” is set to “In the Upgrade Process”, security variable
“Insertion Value on Increasing” specifies the new numeric value
in the position specified by security variable “Position for Insertion
Value”.
3.1.4 Insertion Value on Increasing

668
Function
This security variable specifies the value inserted during number expansion.
Default Value
Value Range
[0, 9]
3-5


Phone number When security variable “Phone Number Upgrading Status
upgrading status setting Setting” is set to “Before Upgrade”, the system does not perform
number expansion.
number.
Length of MSISDN When security variable “Phone Number Upgrading Status
before increasing Setting” is set to “before upgrade”, it is irrelevant to security
variable “length of MSISDN before increasing”.
When “Phone Number Upgrading Status Setting” is set to “In the
upgrade process” and the length of the subscriber MSISDN is
equal to the value of security variable “Length of MSISDN Before
Increasing”, the system expands the number.
Position for insertion When security variable “Phone Number Upgrading Status
value Setting” is set to “In the Upgrade Process”, security variable
“Position for Insertion Value” indicates the position of inserting the
new numeric value that is the value of security variable “Insertion
Value on Increasing”.
3.1.5 Send MAP Phase Setting

669
Function
This security variable specifies the MAP dialog transmission phase that the MSCS
supports for processing MAP compatibility. In transmitting the MAP dialog, the
MSCS first checks whether the MAP version number is configured in the GT+AC
configuration. If it is not configured, the MSCS determines the dialog version
number according to the value of this security variable.
Default Value
Release99
3-6

Value Range
Value Meaning
Not support Not support
Phase1 Phase1
Phase2 Phase2
Phase2+ Phase2+
Release99 Release99
Release4 Release4
3.1.6 Receive MAP Phase Setting

670
Function
This security variable specifies the MAP dialog reception phase that the MSCS
supports for processing MAP compatibility. In receiving the MAP dialog, the MSCS
first checks whether the MAP version number is configured in the GT+AC
configuration. If it is not configured, the MSCS determines the dialog version
number according to the value of this security variable.
Default Value
Release99
Value Range
Value Meaning
Not support Not support
Phase1 Phase1
Phase2 Phase2
Phase2+ Phase2+
Release99 Release99
Release4 Release4
3.1.7 TM Packet Size (Byte)

671
3-7

Function
When a subscriber has a lot of subscriber information, such as many

supplementary services and CAMEL information, the maximum transmission
capability of the SCCP should be considered in this case. If necessary, the system
packages the related messages by service or cord/decode. It is set to 150 for 2G
equipment, and 2,000 for 3G equipment.
Default Value
2000
Value Range
[130, 2400]
3.1.8 Duration of Call Gap Specified in Network (s)

672
Function
When the SCP does not specify the call interval, the SSME specified this value
according to the configuration.
Default Value
3600
Value Range
[0, 2147483647]
Unit: second
3.1.9 Whether to Use ATI Prior Flag

673
Function
According to this flag, the GMLCMAP determines whether to send an Any Time
Interrogation (ATI) message or a normal route request message to the HLRMAP
module.
3-8

Default Value
No
Value Range
Value Meaning
No The system sends a route request message.
Yes The system sends an ATI message preferentially.
3.1.10 Time Zone

674
Function
This security variable sets the time zone.
Default Value
Beijing, Urumchi, Hong Kong
Value Range
z Greenwich, Dublin
z Bombay
z Auckland
z Sydney
z Bagdad, Moscow, Teheran
z Beijing, Urumchi, Hong Kong
z Paris, Budapest
z Dhaka
z Magadan
z Cape Verde Islands
z Kabul
z Tokyo
z Cairo
z Bangkok
z Atlantic
3-9

3.1.11 ATI Send Phase

675
Function
Although there is difference in optional parameters between the ATI message in

the R99 phase and the ATI message in the R98+ phase, the HLR in the R98+
phase should be compatible according to the protocol. When the HLR in the
existing network is to be interconnected, the HLR always regarded it as parameter
errors. The GMLC is required to adjust the parameters in the ATI request
message according to the protocol in the R98+ phase or the R99 phase.
Default Value
Send by R99
Value Range
Value Meaning
Send by R99 The protocol phase is R99.
Send by R98+ The protocol phase is R98+.
3.1.12 Whether to Use Call Forwarding OSB Check Control Switch

678
Function
This security variables sets whether to check the forwarding subscriber number of
the subscriber who subscribes to the Operator Specific Barring (OSB) service and
the call forwarding service at the same time.
Default Value
Off
Value Range
Value Meaning
Off The system turns off this control switch.
On The system turns on this control switch.
3-10

3.1.13 Whether to Use Register Forwarding OSB Check Control

Switch
679
Function
This security variable sets whether to check the forwarding subscriber number of
the subscriber who subscribes to the OSB service and registers the call
forwarding service at the same time.
Default Value
Off
Value Range
Value Meaning
Off The system turns off this control switch.
On The system turns on this control switch.
3.1.14 Interval of Force Location Update to HLR (Minute)

681
Function
When difference between the time of this location update and the time of last
network access is less than the value of this security variable, the subscriber
needs to perform location update in the HLR.
Default Value
Value Range
[0, 2880]
Unit: Minute
3-11

3.1.15 Version of TM
682
Function
This security variable ensures compatibility of codec.
Default Value
Value Range
[0, 255]
3.1.16 Whether to Enable Control Parameter of Location Reject

Cause for CS
695
Function
This security variable sets whether to fill in the reason of refusal according to
security variable “Location Reject Cause for CS” when location update fails.
Default Value
No
Value Range
Value Meaning
The reason of refusal set by security variable “Location
No
Reject Cause for CS” is not used.
The reason of refusal set by security variable “Location
Yes
Reject Cause for CS” is used.

This security variable is effective only when security variable
Location Reject Cause for
“Whether to Enable Control Parameter of Location Reject
CS
Cause for CS” is set to Yes.
3-12

3.1.17 Location Reject Cause for CS

696
Function
This security variable sets the reason of refusal filled in when location update fails.
Default Value
11: PLMN not allowed
Value Range
z 2: IMSI unknown in HLR

z 3: Illegal MS
z 4: IMSI unknown in VLR
z 5: IMEI not accepted
z 6: Illegal ME
z 11: PLMN not allowed
z 12: Location area not allowed
z 13: Roaming not allowed in this location area
z 15: No suitable cells in location area
z 17: Network failure
z 22: Congestion
z 32: Service option not supported
z 33: Requested service option not subscribed
z 34: Service option temporarily out of order
z 38: Call cannot be identified

Whether to Enable Control
Parameter of Location This security variable must be enabled in advance.
Reject Cause for CS
3.1.18 Roaming not Allowed in Cell Cause

697
3-13

Function
This security variable sets the reason of refusal returned to the MS in case of cell
restriction.
Default Value
15: No suitable cells in location area
Value Range
z 3: Illegal MS
z 6: Illegal ME
z 22: Congestion
3.1.19 Roaming not Allowed in LAI Cause

698
Function
This security variable sets the reason of refusal returned to the MS in case of
location area restriction.
Default Value
13: Roaming not allowed in this location area
Value Range

z 3: Illegal MS
3-14


z 6: Illegal ME
z 22: Congestion
3.1.20 ARD Reject Cause in Same PLMN

699
Function
This security variable sets the failure cause returned to the Mobile Station (MS)
when access is restricted and when the subscriber IMSI and the RNC/BSC are in
the same PLMN.
Default Value
15: No suitable cells in location area
Value Range

z 3: Illegal MS
z 6: Illegal ME
z 22: Congestion
3-15

3.1.21 ARD Reject Cause Not in Same PLMN

700
Function
This security variable sets the failure cause returned to the Mobile Station (MS)
when there is access restriction and the network number is different from the 2G
network number.
Default Value
13: Roaming not allowed in this location area
Value Range

z 3: Illegal MS
z 6: Illegal ME
z 22: Congestion
3.1.22 Whether Cell Roaming Restrict Option is Enabled in LU

Process
701
Function
3-16

This security variable determines whether to enable the “Cell Roaming Restrict”
option in the location update process or not.
Default Value
No
Value Range
Value Meaning
No The cell roaming restriction function is disabled.
Yes The cell roaming restrict function is enabled.
3.1.23 Whether Cell Roaming Restrict Option is Enabled when MO

Processes
702
Function
This security variable determines whether the cell roaming restriction function is
enabled during the MO process.
Default Value
No
Value Range
Value Meaning
The system does not enable the cell roaming restriction function
No
during the MO process.
The system enables the cell roaming restriction function during the
Yes
MO process.
3.1.24 Cause Value of Roaming Restrict by MSISDN

712
3-17

Function
This security variable sets the reason of refusal returned to the MS in case of
roaming restriction.
Default Value
15
Value Range
[0, 255]
3.1.25 Support Length Coding Type

714
Function
This security variable specifies the encoding mode of oversized code-stream

length field.
Default Value
Value Range
Value Meaning
0 It indicates undefined length encoding.
1 It indicates fixed length encoding.
3.1.26 Whether USSD Service Message Sent by CN Is Used Fixed

Length Encode
715
Function
This security variable sets whether to use the fixed-length encoding mode when
the network delivers the USSD service to the MS.
3-18

Default Value
Value Range
Value Meaning
0 Fixed-length encoding mode not used.
1 Fixed-length encoding mode used.
3.1.27 Location Reject Cause About ODB Roam Not Allowed

716
Function
This security variable sets the reason of refusal for location update of ODB
roaming disallowed.
Default Value
11: PLMN not allowed
Value Range

z 3: Illegal MS
z 6: Illegal ME
z 22: Congestion
3-19

3.1.28 Whether to Enable Switch of the MSCNumber Coding in PSI-

Rsp Msg
717
Function
This security variable specifies whether the location information in the PSI
response message contains MSCNumber.
Default Value
Value Range
Value Meaning
0 MSCNumber is not contained.
1 MSCNumber is contained.
3.1.29 Is Paid Special Service Under ODB Control

1863
Function
In terms of a local originated call, the call service type of the called number
analysis is paid special service (that is, “intraoffice paid special service” or
“outgoing paid special service”). This security variable controls whether this call is
under control of the ODB.
Default Value
0: Not control by ODB
Value Range
Value Meaning
0: Not control by ODB The paid special service is not under control of the ODB.
1: Control by ODB The paid special service is under control of the ODB.
3-20

3.2 CS Security Parameter

Table 7 lists the security variables displayed in the CS Security Parameter tab
page.
TABLE 7 SECURITY V ARIABLES DISPLAYED IN THE CS SECURITY P ARAMETER TAB P AGE

Whether to Request IMSI When MS Access With Unknown TMSI 3-21
Whether to Get IMSI From MS When Authentication Fails Using TMSI 3-22
Num of Auth Vectors Kept 3-22
Whether CODEC Is Accordance to the Control Switch 3-23
Whether to Delete Home MCC Where Analysis the MSISDN 3-23
Choice of Service When Fallback for Outside Reason 3-24
Whether H324M Is Allowed When NISU 3-24
Whether SCUDIF Is Allowed for CAMEL2/3 User 3-25
When MS Access Network With TMSI, Whether VLR Check MSÌMEI 3-25
Do not Issued ClassMarkReq Instructions in LocationUpdate Process 3-26
Whether Replace IMEISV by IMEI when Obtain IMEISV from MS 3-26
3.2.1 Whether to Request IMSI When MS Access With Unknown

TMSI
964
Function
This security variable sets whether to request the IMSI from the MS when the VLR
does not recognize the TMSI during access.
Default Value
Yes
Value Range
Value Meaning
The IMSI is not requested during terminal access when the
No
TMSI is unknown.
The IMSI is requested during terminal access when the TMSI
Yes
is unknown.
3-21

3.2.2 Whether to Get IMSI From MS When Authentication Fails

Using TMSI
965
Function
This security variable sets whether to request the IMSI from the MS when using
the TMSI for authentication fails.
Default Value
Yes
Value Range
Value Meaning
The system does not request the IMSI from the MS when
No
using the TMSI for authentication failed.
The system requests the IMSI from the MS when using the
Yes
TMSI for authentication failed.
3.2.3 Num of Auth Vectors Kept

967
Function
This security variable sets the number of groups reserved for the authentication
parameters. When the number of the unused authentication groups in the VLR is
not enough for reservation, the VLR initiates a process of requesting the
authentication parameter from the HLR. Because this process is independent of
the service flow, it does not prolong the duration of location update or call access.
Default Value
Value Range
[0, 2]
3-22

3.2.4 Whether CODEC Is Accordance to the Control Switch

1018
Function
This security variable sets whether to shield some fields that the existing network
does not support during encoding.
Default Value
No
Value Range
Value Meaning
The system does not shield the unsupported fields of the
No
existing network.
The system shields the unsupported fields of the existing
Yes
network.
3.2.5 Whether to Delete Home MCC Where Analysis the MSISDN

1020
Function
This security variable sets whether to automatically delete the domestic country
code during number analysis.
Default Value
No
Value Range
Value Meaning
The system does not automatically delete the domestic
No
country code during number analysis.
The system automatically deletes the domestic country code
Yes
during number analysis.
3-23

3.2.6 Choice of Service When Fallback for Outside Reason

1022
Function
This security variable specifies the rule of selecting a service according to the
protocol when a fallback occurs because of an external reason. This security variable
in this version is reserved and not used temporarily.
Default Value
No
Value Range
Value Meaning
No High-priority services
Yes Voice services
3.2.7 Whether H324M Is Allowed When NISU

1023
Function
This security variable specifies whether to support not distinguishing the

originators of service update during judgment of Network-Initiated Service
Upgrade (NISU). This security variable in this version is not used temporarily.
Default Value
Yes
Value Range
Value Meaning
The system does not support not distinguishing the originators
No
of service update.
The system supports not distinguishing the originators of
Yes
service update.
3-24

3.2.8 Whether SCUDIF Is Allowed for CAMEL2/3 User

1025
Function
This security variable specifies whether the CAMEL2/3 subscribers support the
Service Change and UDI Fallback (SCUDIF) call. If this is not supported, the
service falls back to a single service according to security variable “Choice of
Service When Fallback for Outside Reason”. This security variable in this version
is not used temporarily.
Default Value
No
Value Range
Value Meaning
No CAMEL2/3 subscribers do not support the SCUDIF call.
Yes CAMEL2/3 subscribers support the SCUDIF call.
3.2.9 When MS Access Network With TMSI, Whether VLR Check

MSÌMEI
1026
Function
When a subscriber initiates the service access by using the TMSI, the VLR
checks the International Mobile Equipment Identifier (IMEI) of the MS when no
authentication is performed during the access.
Default Value
Yes
Value Range
Value Meaning
No The VLR does not check the IMEI of the MS.
Yes The VLR checks the IMEI of the MS.
3-25

3.2.10 Do not Issued ClassMarkReq Instructions in LocationUpdate

Process
1836
Function
This security variable sets whether to issue the ClassMarkReq instructions in the
location update process.
Default Value
No
Value Range
Value Meaning
The system issues the ClassMarkReq instructions in the
No
location update process.
The system does not issue the ClassMarkReq instructions in
Yes
the location update process.
3.2.11 Whether Replace IMEISV by IMEI when Obtain IMEISV from

MS
2136
Function
This security variable determines whether to replace IMEISV with IMEI when the
location update flow supports the ADD operation.
Default Value
No
Value Range
Value Meaning
The system does not replace IMEISV with IMEI during the
No
location update flow.
The system replaces IMEISV with IMEI during the location
Yes
update flow.
3-26

3.3 CS Network Entity Configuration

Table 8 lists the security variable displayed in the CS Network Entity Config tab
page.
TABLE 8 SECURITY V ARIABLE DISPLAYED IN THE CS NETWORK ENTITY CONFIG TAB P AGE

Whether to Support GPRS 3-29
Whether to Support Multiple Bearer in Local MSC (CC) 3-30
Whether to Support Long FTN 3-30
Whether to Enable Sending Identification Operation Segmentation 3-31
Whether to Enable Sending AuthInfo Operation Segmentation 3-31
Whether to Enable Allowing Re-synchronous Case Authentication 3-32
Number of Authentication Vectors 3-32
Whether to Check Bear Capability When MSRN Is Supplied 3-33
The Times of Resend the CPData Message When MM Permit 3-33
SM Max. Packet Size 3-33
The Times of Resending the Alert Message 3-34
The Times of Resending the Reset Message 3-34
Whether to Support NSD Check 3-35
Whether to Support Super-Charger 3-35
Whether to Limit 2G/3G User Access 3-36
Whether to Limit Forwarding Long Distance or Not 3-36
Whether Charge Is Needed When Camel Play Tone, the Mark Indicated 3-37
Location Report Control Type 3-37
Whether to Support Bengal Prepaid Subscriber SMS Charging 3-38
Whether HO Req Is Same as SIEMENS 3-38
Whether to Support Cater to GSM During Inter-Handover From UTRAN to 3-39
GSM
The Framework of MGW in an MSCS 3-39
Filling Rule of MSC Number or VLR Number in MAP/CAP Dialog Message 3-40
Filling Rule of GT in MAP/CAP Dialog Initial Message 3-41
SMMT Fail Cause Switch Rate 3-41
Whether to Support QUANZHOU Prepaid-SMS 3-42
Modify SMSC Number Function 3-42
Whether Inter MSC Handover With Cell Load Group Info or Not 3-43
Whether to Adapt Container Info Within Handover/Relocation Request 3-43
Message
3-27


Whether the Bill for NNI OverlayMo Is Produced 3-44
Max Percent of Dialog-id Area Occupation for USSD Service (%) 3-45
Whether to Supply Optimize Half-Rate for Paktel 3-45
Whether to Apply EGSM Frequency by Force 3-45
Whether to Adapt Cause for Camel Play Tone Bill 3-46
Whether Modify PresentInd of Generic Number Send by SCP 3-46
The Maximum of DTMF Signals Sent by Mobile Subscriber in a Terminated 3-47
Call
The Maximum of DTMF Signals Sent by Mobile Subscriber Before Answering 3-48
in an Outgoing Call
Whether to Support PPS Flag in SMS-MO CDR 3-48
Whether Report Call Duration for ANN 3-49
Preferred Voice Codec Type of Service Priority Level 1 3-49
Whether Delete International Prefix of Reconnect Number 3-51
Whether to Enable Sending out of Band DTMF Signal to UE 3-52
The ANM/CONNECT Indication of BothwayThroughConnectionInd for ETC 3-52
The ACM (CPG)/Alerting Indication of BothwayThroughConnectionInd for ETC 3-53
The ANM/CONNECT Indication of BothwayThroughConnectionInd for CTR 3-54
The ACM (CPG)/Alerting Indication of BothwayThroughConnectionInd for CTR 3-54
Not Sent Forwarding Notification to SCP 3-55
When OVMO, Send IMSI to SCP if It Can Be 3-56
Whether to Enable Retry Page with IMSI in Place of TMSI 3-56
How to Fill Called Party BCD Number in IDP Message 3-57
CAP Interface Information Field Differences Control Switch 3-57
Cancel GSMSSF Periodic Inspection of Basic Call 3-58
SRF Calculate the Maximum Number of Income Excluding the Terminator 3-58
SRF Can Be Collected in the First Number is the Terminator 3-59
After MSC Connect the Call, Received TC_END (zero elements) and There Is 3-59
AC Pending, Release Call
Whether to Allow Paging in Search Mode for MSC Pool 3-60
Time Interval of Heart Beat Test for MSC Pool User Data Synchronization (in 3-60
Sec)
Allowed Heart Beat Abnormal Times for MSC Pool User Data Synchronization 3-61
Whether to Check IMSI Sent by PVLR 3-61
Interval of Send User Capacity to NNSF 3-62
3-28


Contain CIC in Called Number 3-62
Pre-CIC Located at the Head of Called Number 3-63
Whether to Adapt Termination Cause for Preemption 3-63
LCS Version 3-64
Whether to Support Long EPLMN List 3-64
CSL Location Report Control 3-65
Get HandOver Priority From Subscriber 3-65
Ban the UE/MS Access With Illegal CI/SAI 3-66
Get PLMN of Iu Interface Global CN ID From Local Office Mobile Data 3-66
Configuration
Build MPTY With MPTY Bridge 3-67
The Indication of RedirectionInfo and RedirectingNum for TCSI Reconnect 3-67
Business Process Control Parameters 3-68
Continue Call When CAMEL Tone Is too Short for the Calling User 3-68
The Switches of Buffer Scan of CAMEL/HO Module 3-69
Format Adjustment for MNP Is Needed or Not 3-70
The Indication of Local CLIP Process When Nature of Calling Number Is 3-70
Unknown
Routing According to the PLMN-Specific SS Code 3-71
Paging Protect Time in MSC Pool 3-71
DDI Delay Saving Method 3-72
Threshold of A Interface PCM 3-72
For MF Calls Triggering at DP Collected_Info whether to Internationalize the 3-73
Destination Number Before Matching it
3.3.1 Whether to Support GPRS
1105
Function
This security variable sets whether the GMSC supports the GPRS function during
short message termination. If the GPRS function is not supported, the GMSC
does not deliver Mobile Terminated (MT) short messages.
Default Value
No
3-29

Value Range
Value Meaning
No GPRS not supported.
Yes GPRS supported.
3.3.2 Whether to Support Multiple Bearer in Local MSC (CC)

1106
Function
This security variable sets whether the home terminal supports multiple bearers.
Currently, only the MSCMAP module judges the multi-bearer during interoffice
handover.
Default Value
No
Value Range
Value Meaning
No The home terminal does not support multiple bearers.
Yes The home terminal supports multiple bearers.
3.3.3 Whether to Support Long FTN

1107
Function
This security variable sets whether the home terminal supports long forwarding
numbers. In sending an SRI message, the GMSC determines the value of this
security variable. If this value is TRUE, the value of “whether to support long
forwarding numbers” in the SRI message is TRUE, otherwise, it is FALSE.
Default Value
Yes
3-30

Value Range
Value Meaning
The home terminal does not support long forwarding
No
numbers.
Yes The home terminal supports long forwarding numbers.
3.3.4 Whether to Enable Sending Identification Operation

Segmentation
1110
Function
This security variable sets whether to allow sending identification operation

segmentation. Only version 3 supports segmentation.
Default Value
No
Value Range
Value Meaning
No Sending identification operation segmentation disallowed.
Yes Sending identification operation segmentation allowed.
3.3.5 Whether to Enable Sending AuthInfo Operation Segmentation

1111
Function
This security variable sets whether to allow sending AuthInfo operation

segmentation. Only version 3 supports segmentation.
Default Value
Yes
Value Range
Value Meaning
3-31

Value Meaning
No Sending AuthInfo operation segmentation disallowed.
Yes Sending AuthInfo operation segmentation allowed.
3.3.6 Whether to Enable Allowing Re-synchronous Case

Authentication
1112
Function
This security variable sets whether the authentication resynchronization process

is allowed in the CN network. Authentication resynchronization only exists in
UMTS authentication.
Default Value
Yes
Value Range
Value Meaning
No Authentication resynchronization disallowed.
Yes Authentication resynchronization allowed.
3.3.7 Number of Authentication Vectors

1113
Function
This security variable sets the number of the authentication parameter groups that
the VLR acquires from the HLR. It can acquire up to five groups every time.
Default Value
Value Range
[1, 5]
3-32

3.3.8 Whether to Check Bear Capability When MSRN Is Supplied

1114
Function
This security variable specifies whether to check the bearer capacity sent from the
HLR when the VLR provides a roaming number.
Default Value
Yes
Value Range
Value Meaning
The system does not check the bearer capability sent by the
No
HLR in the process of providing a roaming number.
The system checks the bearer capability from the HLR in the
Yes
process of providing a roaming number.
3.3.9 The Times of Resend the CPData Message When MM Permit

1116
Function
This security variable sets the number of the CPData messages that the MM is
allowed to resend when it does not receive a response to the CPData message.
Default Value
Value Range
[0, 3]
3.3.10 SM Max. Packet Size

1117
3-33

Function
When the message length is greater than the value of the security variable, the
MSCMAP module needs to send the message by several packets. Version 1 does
not support sending a message by several packets.
Default Value
120
Value Range
[1, 200]
3.3.11 The Times of Resending the Alert Message

1119
Function
This security variable sets the number of the Alert messages that the VLRMAP is
allowed to resend through the Gs interface when it does not receive a response to
the Alert message.
Default Value
Value Range
Value Meaning
0 Not resending
1 Resending one time
2 Resending twice
3.3.12 The Times of Resending the Reset Message

1120
Function
This security variable sets the number of the Reset messages that the VLRMAP is
allowed to resend through the Gs interface when it does not receive a response to
the Reset message.
3-34

Default Value
Value Range
Value Meaning
0 Not resending
1 Resending one time
2 Resending twice
3.3.13 Whether to Support NSD Check

1123
Function
This security variable sets whether it is necessary for the MM to check NSD for
the layer-3 messages.
Default Value
No
Value Range
Value Meaning
No NSD check not supported.
Yes NSD check supported.
3.3.14 Whether to Support Super-Charger

1127
Function
This security variable specifies whether the home office supports the Super-
Charger function. This function is used to decrease the signaling traffic related to
the mobility management of the UMTS.
Default Value
No
3-35

Value Range
Value Meaning
No Super-charger not supported.
Yes Super-charger supported.
3.3.15 Whether to Limit 2G/3G User Access

1132
Function
This security variable specifies whether to enable the Access Restriction Data
(ARD) function. This function restricts mobile subscribers to use the access side
resources in a mobile network. With the ARD service, the carriers can limit the
access capability of a subscriber to flexibly control whether the subscriber is
accessed from the Radio Access Network (RAN) or the Base Station System
(BSS).
Default Value
No
Value Range
Value Meaning
No The system does not check the ARD.
Yes The system checks the Access Restriction Data.
3.3.16 Whether to Limit Forwarding Long Distance or Not

1141
Function
This security variable specifies whether to support forwarding bypass to bar the
forwarded calls.
Default Value
No
3-36

Value Range
Value Meaning
Forwarding bypass and barring of call forwarding not
No
supported.
Yes Forwarding bypass and barring of call forwarding supported.
3.3.17 Whether Charge Is Needed When Camel Play Tone, the Mark
Indicated
1157
Function
This security variable specifies whether charging is required when the ANM
message is sent in the CAMEL tone playing flow.
Default Value
Yes
Value Range
Value Meaning
No Charging is not performed when an ANM message is sent.
Yes Charging is performed when an ANM message is sent.
3.3.18 Location Report Control Type

1158
Function
This security variable specifies the type of the location report message delivered
to the RNC.
Default Value
Value Range
Value Meaning
3-37

Value Meaning
0 The MSCS does not send the location control report.
1 The MSCS directly reports the Geographical Area (GA).
2 The MSCS directly reports to the Service Area (SA).
3 The MSCS reports GA when SA changes.
4 The MSCS reports SA when GA changes.
5 The MSCS reports GA when SA stops changing.
6 The MSCS reports SA when GA stops changing.
3.3.19 Whether to Support Bengal Prepaid Subscriber SMS

Charging
1162
Function
This security variable specifies whether to enable the short-message billing

function for the prepaid subscribers in Bangladesh.
Default Value
No
Value Range
Value Meaning
No This function is disabled.
Yes This function is enabled.

Whether to support It is not allowed to enable these two security variables
QUANZHOU prepaid-SMS simultaneously.
3.3.20 Whether HO Req Is Same as SIEMENS

1163
3-38

Function
This security variable specifies how to handle the Priority, IMSI and other
parameters contained in the HOReq message during interconnection with the
SIEMEN BSC for compatibility. This is only applicable to the specific scenario. In
case of proper interconnection, you need not to enable it.
Default Value
No
Value Range
Value Meaning
No Parameter compatibility processing is disabled.
Yes Parameter compatibility processing is enabled.
3.3.21 Whether to Support Cater to GSM During Inter-Handover

From UTRAN to GSM
1167
Function
When interoffice handover from 3G to 2G is initiated, if the MAP version of the E

interface is version 2 after the configuration is acquired or the version is
negotiated, this security variable determines whether to implement adaptation for
the handover messages this time and subsequent handover.
Default Value
No
Value Range
Value Meaning
No No adaptation
Yes The system performs adaptation on the handover messages.
3.3.22 The Framework of MGW in an MSCS

1168
3-39

Function
This security variable specifies the mode of connecting the MGWs under the
MSCS.
Default Value
MGW connected to each other in pairs
Value Range
Value Meaning
The MGWs are connected to each other in
MGW connected to each other in pairs
pairs.
The MGWs are connected through
Transfer through TMSCSERV
TMSCSERV, a tandem office.
3.3.23 Filling Rule of MSC Number or VLR Number in MAP/CAP

Dialog Message
1168
Function
1. This security variable specifies MSCNum/VLRNum filled in the Update Location

Request message of the VLRMAP during location update. In terms of location
update between different VLRs under the same physical MSC, this security
variable determines whether to perform location update to the HLR.
If it is set to “0: Fill Default MSCNum/VLRNum”, location update to the HLR will
not be performed, and the original information in the HLR remains unchanged. If
it is set to “1: Fill MSCNum/VLRNum Corresponding to GCI/LAI”, location update
to the HLR is performed, and the location information in the HLR is changed.
2. This security variable also specifies whether “MSCNum/VLRNum” in the IDP

message in an intelligent call is set to “0: Fill Default MSCNum/VLRNum” or “1:
Fill MSCNum/VLRNum Corresponding to GCI/LAI”.
Default Value
1: Fill MSCNum/VLRNum Corresponding to GCI/LAI
Value Range
Value Meaning
0: fill default MSCNum/VLRNum Fill in the default MSCNum/VLRNum.
3-40

Value Meaning
1: Fill MSCNum/VLRNum Corresponding to Fill in the MSCNum/VLRNum
GCI/LAI corresponding to the GCI/LAI.
3.3.24 Filling Rule of GT in MAP/CAP Dialog Initial Message

1170
Function
This security variable specifies the method of filling in the source GT in the initial
message of the Map/Cap dialog, for example, filling in the GT number in the first
MAP OPEN REQUEST message in the VLRMAP during location update.
Default Value
1: Fill MSCNum/VLRNum Corresponding to GCI/LAI
Value Range
Value Meaning
0: fill default MSCNum/VLRNum Fill in the default MSCNum/VLRNum.
1: Fill MSCNum/VLRNum Corresponding to Fill in the MSCNum/VLRNum
GCI/LAI corresponding to the GCI/LAI.
3.3.25 SMMT Fail Cause Switch Rate

1174
Function
This security variable specifies the proportion of the system failure causes
converted to the cause of subscriber busy during short message termination.
Default Value
Value Range
[0, 100]
3-41

3.3.26 Whether to Support QUANZHOU Prepaid-SMS

1180
Function
This security variable specifies whether to support the Quanzhou prepaid Short
Message Service (SMS).
Default Value
No
Value Range
Value Meaning
No The QUANZHOU prepaid-SMS not supported.
Yes QUANZHOU prepaid-SMS supported.

Whether to Support Bengal
It is not allowed to enable these two security variables
Prepaid Subscriber SMS
simultaneously.
Charging
3.3.27 Modify SMSC Number Function
1181
Function
This security variable specifies whether the MSCS supports the function of
modifying the address of the Short Message Service Center (SMSC) upon short
message origination.
Default Value
Not support modifying SCNum
Value Range
Value Meaning
3-42

Value Meaning
The function of modifying the SMSC number is
Not support modifying SCNum
disabled.
The SMSC number is acquired preferentially
SMS route by IMSI firstly
according to the IMSI.
The SMSC address is acquired preferentially
SMS route by CalledNum firstly
according to the called number.
3.3.28 Whether Inter MSC Handover With Cell Load Group Info or
Not
1183
Function
This security variable specifies whether messages PREPARE_HANDOVER

REQUEST and PREPARE_SUBSEQUENT_HANDOVER REQUEST carry the
cell load information during outgoing handover.
Default Value
No
Value Range
Value Meaning
No No need to carry the cell load information during interoffice handover.
Yes The cell load information is carried during interoffice handover.

Security variable “Whether to Adapt Container
Whether to Adapt Container Info Within Info Within Handover/Relocation Request
Handover/Relocation Request Message Message” is valid only when this security
variable is disabled.
3.3.29 Whether to Adapt Container Info Within Handover/Relocation

Request Message
1184
3-43

Function
In some cases, the target BSC/RNC does not support the load-based handover or
that carrying the cell load information is not required during the interoffice
handover. In this case, this security variable specifies whether to delete the cell
load information in “Old BSS to New BSS Information/Source RNC to Target RNC
Transparent Container” in sending the Handover Request/Relocation Request
messages.
Default Value
Yes
Value Range
Value Meaning
No No handing is required.
Yes The Cell Load Information is deleted.

Whether Inter MSC Handover Security variable “Whether to Adapt Container Info Within
With Cell Load Group Info or Handover/Relocation Request Message” is valid only
Not when this security variable is disabled.
3.3.30 Whether the Bill for NNI OverlayMo Is Produced

1185
Function
This security variable specifies whether to produce CDRs for the Network-
Network Interface (NNI) overlay MO service.
Default Value
No
Value Range
Value Meaning
No CDRs are not produred for the NNI overlay MO service.
Yes CDRs are produced for the NNI overlay MO service.
3-44

3.3.31 Max Percent of Dialog-id Area Occupation for USSD Service

(%)
1192
Function
This security variable specifies the maximum proportion of the USSD service
dialog ID resources to all dialog ID resources.
Default Value
80
Value Range
[0, 100]
3.3.32 Whether to Supply Optimize Half-Rate for Paktel

1193
Function
This security variable specifies whether to support Paktel half-rate optimization.
Default Value
No
Value Range
Value Meaning
No Paktel half-rate optimization not supported.
Yes Paktel half-rate optimization supported.
3.3.33 Whether to Apply EGSM Frequency by Force

1194
3-45

Function
This security variable specifies whether to compel the specific subscribers to use
the frequency point of Extended GSM (EGSM).
Default Value
No
Value Range
Value Meaning
The system does not force the specific subscribers to use the
No
EGSM frequency point.
The system forces the specific subscribers to use the EGSM
Yes
frequency point.
3.3.34 Whether to Adapt Cause for Camel Play Tone Bill

1195
Function
This security variable specifies whether to change cause value 101 in the
intelligent tone-playing CDRs to the cause values of other calls, that is, whether to
change the tone-playing CDRs to the non-tone-playing CDRs.
Default Value
No
Value Range
Value Meaning
The system does not implement adaptation of the cause value in the
No intelligent tone-playing CDR, that is, producing the intelligent tone-
playing CDR.
The system implements adaptation of the cause value in the
Yes intelligent tone-playing CDR, that is, producing the calling CDR
instead of the intelligent tone-playing CDR.
3.3.35 Whether Modify PresentInd of Generic Number Send by SCP

1196
3-46

Function
This security variable specifies whether to modify the SCP-delivered universal

number display indication. After modification, the SCP-delivered indication is
overwritten with the calling-number display indication.
Default Value
No
Value Range
Value Meaning
The system does not modify the SCP-delivered universal number
No
display indication.
The system modified the SCP-delivered universal number display
Yes
indication.
3.3.36 The Maximum of DTMF Signals Sent by Mobile Subscriber in

a Terminated Call
1198
Function
This security variable specifies the number of the Dual-Tone Multi-Frequency

(DTMF) signals that a called party is allowed to send during a call. This is used for
the call-back card restriction service.
Default Value
255 (indicating no limitation)
Value Range
[0, 100] and [255, 255]

The maximum of DTMF signals sent by
mobile subscriber before answering in an Used for the call-back card restriction service.
outgoing call
3-47

3.3.37 The Maximum of DTMF Signals Sent by Mobile Subscriber

Before Answering in an Outgoing Call
1199
Function
This security variable specifies the maximum number of the DTMF signals that a
calling party can send before the call is completely connected. This is used for the
call-back card restriction service.
Default Value
255 (indicating no limitation)
Value Range
[0, 100] and 255

The maximum of DTMF signals sent by
Used for the call-back card restriction service.
mobile subscriber in a terminated call
3.3.38 Whether to Support PPS Flag in SMS-MO CDR

1200
Function
This security variable specifies whether to add the PrePaid Service (PPS) flag in
the Short Message Service (SMS) Mobile-Originated (MO) CDRs of prepaid
subscribers.
Default Value
No
Value Range
Value Meaning
No No PPS flag is added in SMS-MO CDRs.
Yes The PPS flag is added in SMS-MO CDRs.
3-48

3.3.39 Whether Report Call Duration for ANN

1201
Function
This security variable specifies whether to fill in the call duration in the ACR
message sent to the SCP in terms of answering without charging.
Default Value
No
Value Range
Value Meaning
The system does not report the call duration of answering without
No
charging
The system reports the call duration of answering without
Yes
charging to the SCP.
3.3.40 Preferred Voice Codec Type of Service Priority Level 1

1202
Function
This security variable specifies the preferred encoding mode of the voice service
at service priority level 1.
Default Value
Value Range
Value Meaning
0 Invalid
1 G.711
2 UMTS AMR2
3-49


1203
Function
Default Value
Value Range
Value Meaning
0 Invalid
1 G.711
2 UMTS AMR2

1204
Function
Default Value
Value Range
Value Meaning
0 Invalid
1 G.711
2 UMTS AMR2
3-50


1205
Function
Default Value
Value Range
Value Meaning
0 Invalid
1 G.711
2 UMTS AMR2
3.3.44 Whether Delete International Prefix of Reconnect Number

1207
Function
During call reconnection, this security variable specifies whether to delete the
international prefix of the reconnected number delivered by the Service Control
Point (SCP).
Default Value
Yes
Value Range
Value Meaning
No The international prefix of the reconnected number is not deleted.
Yes The international prefix of the reconnected number is deleted.
3-51

3.3.45 Whether to Enable Sending out of Band DTMF Signal to UE

1208
Function
This security variable specifies whether to allow sending the out-of-band DTMF
messages to the User Equipment (UE).
Default Value
No
Value Range
Value Meaning
The system prohibits sending out-of-band DTMF signals to the
No
UE.
Yes The system allows sending out-of-band DTMF signals to the UE.
3.3.46 The ANM/CONNECT Indication of

BothwayThroughConnectionInd for ETC
1209
Function
This security variable specifies whether it is mandatory to send an ANM/Connect

message to the calling side during the flow of “Establish Temporary Connection
(ETC)”.
Default Value
No
Value Range
Value Meaning
It is not mandatory to send an ANM/Connect message to the calling side.
Whether to send an ANM/Connect or an ACM (CPG)/Alerting message is
No
dependent on the both-way connection indication carried in the SCP-
delivered ETC message.
It is mandatory to send an ANM/Connect message to the calling side. The
Yes ANM/Connect message is sent regardless of the both-way connection
indication carried in the SCP-delivered ETC message.
3-52


Security variables “The ACM (CPG)/Alerting Indication of
The ACM (CPG)/Alerting
BothwayThroughConnectionInd for ETC” and “The
Indication of
ANM/CONNECT Indication of
BothwayThroughConnectionInd
BothwayThroughConnectionInd for ETC” cannot be set to
for ETC
Yes at the same time.
3.3.47 The ACM (CPG)/Alerting Indication of

BothwayThroughConnectionInd for ETC
1210
Function
This security variable specifies whether it is mandatory to send an ACM

(CPG)/Alerting message to the calling side during the flow of ETC.
Default Value
No
Value Range
Value Meaning
It is not mandatory to send an ACM (CPG)/Alerting message to the calling
side. Whether to send an ANM/Connect or an ACM(CPG)/Alerting message
No
is dependent on the both-way connection indication carried in the SCP-
delivered ETC message.
It is mandatory to send an ACM (CPG)/Alerting message to the calling side.
Yes The ANM/Connect message is sent regardless of the both-way connection
indication carried in the SCP-delivered ETC message.

The ANM/CONNECT Indication
BothwayThroughConnectionInd for ETC” and “The
of
BothwayThroughConnectionInd for ETC” cannot be set to
for ETC
3-53

3.3.48 The ANM/CONNECT Indication of

BothwayThroughConnectionInd for CTR
1211
Function
This security variable specifies whether it is mandatory to send an ANM/Connect

message to the calling side during the flow of “Connect To Resource (CTR)”.
Default Value
No
Value Range
Value Meaning
It is not mandatory to send an ANM/Connect message to the calling side.
Whether to send an ANM/Connect or an ACM (CPG)/Alerting message is
No
dependent on the both-way connection indication carried in the SCP-delivered
CTR message.
It is mandatory to send an ANM/Connect message to the calling side. The
Yes ANM/Connect message is sent regardless of the both-way connection indication
carried in the SCP-delivered CTR message.

The ACM (CPG)/Alerting
BothwayThroughConnectionInd for CTR” and “The
Indication of
BothwayThroughConnectionInd for CTR” cannot be set to
for CTR
3.3.49 The ACM (CPG)/Alerting Indication of

BothwayThroughConnectionInd for CTR
1212
Function
This security variable specifies whether it is mandatory to send an ACM

(CPG)/Alerting message to the calling side during the flow of CTR.
3-54

Default Value
No
Value Range
Value Meaning
It is not mandatory to send an ACM (CPG)/Alerting message to the
calling side. Whether to send an ANM/Connect or an ACM
No
(CPG)/Alerting message is dependent on the both-way connection
indication carried in the SCP-delivered CTR message.
It is mandatory to send an ACM (CPG)/Alerting message to the calling
Yes side. The ANM/Connect message is sent regardless of the both-way
connection indication carried in the SCP-delivered CTR message.

The ANM/CONNECT Indication
BothwayThroughConnectionInd for CTR” and “The
of
BothwayThroughConnectionInd for CTR” cannot be set to
for CTR
3.3.50 Not Sent Forwarding Notification to SCP

1975
Function
If call forwarding occurs during the called Value-Added Service (VAS) with the
Terminating CAMEL Subscriber Information (TCSI) this security variable specifies
whether to send the forwarding notification to the SCP.
Default Value
Yes
Value Range
Value Meaning
The system notifies the SCP of the forwarding condition of the
No
subscriber with the ERB message.
The system continues the subsequent call forwarding processing
Yes
instead of notifying the SCP.
3-55

3.3.51 When OVMO, Send IMSI to SCP if It Can Be Got

1976
Function
When an access number triggers the calling IN service and the subscriber’s IMSI
can be obtained, this security variable specifies whether to send this IMSI to the
SCP.
Default Value
No
Value Range
Value Meaning
The system does not send the IMSI to the SCP during Overlay
No
MO.
Yes The system sends the IMSI to the SCP during Overlay MO.
3.3.52 Whether to Enable Retry Page with IMSI in Place of TMSI

1215
Function
To avoid paging failure due to inconsistency between the TMSI recorded on the
user terminal and the TMSI in the VLR in case of no response to paging, the IMSI
is used for the last time of paging subscriber after this security variable is enabled.
Default Value
No
Value Range
Value Meaning
It is acceptable either containing or not containing the TMSI
No
during paging.
Yes The TMSI is not contained during paging.
3-56

3.3.53 How to Fill Called Party BCD Number in IDP Message

1217
Function
This security variable specifies how to fill in the called BCD number in the IDP
message.
Default Value
Fill original dialed number
Value Range
Value Meaning
Fill original dialed The original dialed number is filled in as the called BCD number in
number the IDP message.
The transformed number is filled in as the called BCD number in
Fill transformed number
the IDP message.
3.3.54 CAP Interface Information Field Differences Control Switch

1219
Function
This security variable specifies whether the Locationinfomation field in the IDP
message contains the MSCNum field.
Default Value
Yes
Value Range
Value Meaning
The Locationinfomation field in the IDP message does not contain
No
the MSCNum field.
The Locationinfomation field in the IDP message contains the
Yes
MSCNum field.
3-57

3.3.55 Cancel GSMSSF Periodic Inspection of Basic Call

2032
Function
By default, intelligent calls periodically detect the basic calls and the correctness
of itself. This security variable specifies whether to disable the periodic detection
function of the GSMSSF module.
Default Value
No
Value Range
Value Meaning
The system does not disable the periodic detection function of the
No
GSMSSF module.
The system disables the periodic detection function of the
Yes
GSMSSF module.
3.3.56 SRF Calculate the Maximum Number of Income Excluding the

Terminator
2033
Function
This security variable specifies whether to count the terminator as a valid digit
when the Specialized Resource Function (SRF) module counts the maximum
number of digits under number receiving.
Default Value
No
Value Range
Value Meaning
The terminator is not regarded as a valid digit when the SRF module counts
No
the maximum number of received digits.
The terminator is regarded as a valid digit when the SRF module counts the
Yes
maximum number of received digits.
3-58

3.3.57 SRF Can Be Collected in the First Number is the Terminator

2034
Function
This security variable specifies whether it is allowed that the terminator is the first
collected digit when the SRF module is receiving digits.
Default Value
No
Value Range
Value Meaning
No It is not allowed that the terminator is the first collected digit.
Yes It is allowed that the terminator is the first collected digit.
3.3.58 After MSC Connect the Call, Received TC_END (zero

elements) and There Is AC Pending, Release Call
2042
Function
This security variable specifies whether to release a call when zero element
TC_END is received after the call is being answered and the AC is pending. Zero
element TC_END means that the TC_END message does not contain any
element. AC pending is a technical CAMEL term, which means that the AC
message that will be reported to the ACR subsequently has been received at
present.
Default Value
No
Value Range
Value Meaning
The system continues to process the call in a way of processing a
No
basic call instead of releasing it.
Yes The system directly releases the call.
3-59

3.3.59 Whether to Allow Paging in Search Mode for MSC Pool

1220
Function
This security variable specifies whether to allow entire-network paging in MSC-

Pool networking mode.
Default Value
Yes
Value Range
Value Meaning
Entire-network paging in MSC Pool networking mode is not
No
allowed.
Yes Entire-network paging in MSC Pool networking mode is allowed.

Security variable “Whether to Allow Paging in Search Mode for
Support MSC Pool
MSC Pool” is valid only when the MSC Pool function is supported.
3.3.60 Time Interval of Heart Beat Test for MSC Pool User Data
Synchronization (in Sec)
1221
Function
After the MSC Pool function is configured, dynamical synchronization of the

subscriber data among the MSCSs in a pool is required. Therefore, these MSCSs
keep sending heartbeat messages to each other to inform the opposite side of its
normal status. This security variable specifies the interval of sending heartbeat
messages.
Default Value
3-60

Value Range
[5, 30]
Unit: second

Security variable “Time Interval of Heart Beat Test for MSC Pool
Support MSC Pool User Data Synchronization (in Sec)” is valid only when the MSC
Pool function is supported.
3.3.61 Allowed Heart Beat Abnormal Times for MSC Pool User Data
Synchronization
1222
Function
In an MSC Pool, an MSCS receives a heartbeat message from the opposite end
at intervals (that is, the heartbeat time interval of subscriber data synchronization
in the MSC pool) in normal cases. An MSCS assumes that it loses contact with
the opposite MSCS if it has continuously not received the heartbeat message for
several times (which is specified by this security variable). This MSCS does not
dynamically synchronizing the subscriber data with its opposite MSCS.
Default Value
Value Range
[1, 5]

Security variable “Allowed Heart Beat Abnormal Times for MSC
Support MSC pool Pool User Data Synchronization” is valid only when the MSC Pool
function is supported.
3.3.62 Whether to Check IMSI Sent by PVLR

1223
3-61

Function
This security variable specifies whether to check the consistency between the
IMSI sent by the PVLR and the IMSI sent by the MS.
Default Value
No
Value Range
Value Meaning
No The system does not check the IMSI sent by the PVLR.
Yes The system checks the IMSI sent by PVLR.
3.3.63 Interval of Send User Capacity to NNSF

1224
Function
In MSC Pool networking mode, the MSCSs need to periodically send its
information of subscriber quantity to the NNSF node (that is, the RNC/BSC/MGW
supporting the pool function) to make the load of each MSCS in the pool meet the
expected configuration. This security variable specifies the interval of the MSCS
sending the subscriber quantity messages to the NNSF.
Default Value
300
Value Range
[30, 3600]
Unit: second
3.3.64 Contain CIC in Called Number

1226
Function
This security variable specifies whether an outgoing called number contains the
carrier access code.
3-62

Default Value
Yes
Value Range
Value Meaning
No The called number does not contain the carrier access code.
Yes The called number contains the carrier access code.
3.3.65 Pre-CIC Located at the Head of Called Number

1227
Function
This security variable specifies whether to add the pre-CIC in front of the called
number.
Default Value
Yes
Value Range
Value Meaning
The pre-CIC is added behind the international toll prefix or the
No
domestic toll prefix of the called number.
Yes The pre-CIC is added in front of the called number.
3.3.66 Whether to Adapt Termination Cause for Preemption

1828
Function
This security variable specifies whether the MOC/MTC CDR that the MSCS sends
to the billing server contains the cause of preemption failure in the Termination
Cause field when a call is actively released by the RNC/BSC due to preemption.
Default Value
No
3-63

Value Range
Value Meaning
No The system processes the call according to the existing flow.
Yes The system adapts the call release CDR due to radio preemption.
3.3.67 LCS Version

1125
Function
This security variable specifies the location service version supported by the
MSCS.
Default Value
Support R4 or later version
Value Range
Value Meaning
Not support The MSCS does not support the location service.
The MSCS supports the location service of version R99, that is,
Support R99
lcsCapSet1.
Support R4 or later The MSCS supports the location service of version R4 or later,
version that is, lcsCapSet1 and lcsCapSet2.
3.3.68 Whether to Support Long EPLMN List

1214
Function
For a subscriber with mobile phone being version mcL3R99_M or later, the MSCS
sends a “Location Update Accept” message containing the PLMN list to the
subscriber. According to this PLMN list, the subscriber selects different mobile
networks for access. This security variable specifies whether to send up to five or
15 groups of PLMN lists to the end user.
Default Value
Support 5 groups
3-64

Value Range
Value Meaning
The “Location Update Accept” message can contain up to five
Support 5 Groups
groups of PLMN lists.
The “Location Update Accept” message can contain up to 15
Support 15 Groups
groups of PLMN lists.
3.3.69 CSL Location Report Control

1831
Function
This security variable specifies that the MSCS sends a Location Report Control
message to the target RNC during the 2G to 3G handover, so that the CDR
contains the initial and the final locations of the subscriber.
Default Value
No
Value Range
Value Meaning
No The CSL location report is not supported.
Yes The CSL location report is supported.
3.3.70 Get HandOver Priority From Subscriber

1832
Function
This security variable specifies whether the subscriber’s subscription information

determines the priority information in the handover request message.
Default Value
No
Value Range
Value Meaning
3-65

Value Meaning
The global configuration of the local office determines the priority
No
information in the handover request message.
The subscriber’s subscription information determines the priority
Yes
information in the handover request message.
3.3.71 Ban the UE/MS Access With Illegal CI/SAI

1834
Function
When a mobile subscriber accesses the network, this security variable specifies
that the BSSAP/RANAP protocol layer of the MSCS determines whether to check
the corresponding configuration according to the cell/service area parameter
contained in the access message. If the check failed, the MSCS rejects the
access of this subscriber.
Default Value
No check
Value Range
Value Meaning
Accessing the network is allowed even if the access
No check
message contains incorrect cell/service area parameter.
Accessing the network is prohibited when the access
Only Check GCI/SAI Config
message contains incorrect cell/service area parameter.
The MSCS checks not only whether the cell/service area
parameter is configured in the access message but also
Also Check BSC/RNC’s Validity
whether the cell/service area associated BSC/RNC
matches the accessed BSC/RNC.
3.3.72 Get PLMN of Iu Interface Global CN ID From Local Office

Mobile Data Configuration
1835
Function
In an MSCS pool network, when this security variable is enabled and the
corresponding RNC supports the pool, and the MSCS pages 3G subscribers with
3-66

IMSI or hands over calls to another 3G RNC, the message contains Global CN-id
that is set in the mobile configuration of the local office.
Default Value
Yes
Value Range
Value Meaning
The Global CN-id set in the mobile configuration of the local office is
No
not used.
The Global CN-id set in the mobile configuration of the local office is
Yes
used.
3.3.73 Build MPTY With MPTY Bridge

1843
Function
This security variable specifies whether to use the conference bridge to establish
a Multi-Party (MPTY) conference.
Default Value
No
Value Range
Value Meaning
The MPTY is held traditionally, that is, the participant terminals are
No
directly put into the MPTY context.
The MPTY conference is held in conference bridge mode where the
Yes participant terminals are connected to the MPTY context through the
bridge bearer.
3.3.74 The Indication of RedirectionInfo and RedirectingNum for

TCSI Reconnect
1844
3-67

Function
This security variable specifies whether to send the reconnection-related

information to the back end in the TCSI reconnection flow.
Default Value
No
Value Range
Value Meaning
No The reconnection information is not sent to the back end.
Yes The reconnection information is sent to the back end.
3.3.75 Business Process Control Parameters

1845
Function
This security variable specifies the parameter for the service flow control.
Default Value
Value Range
[0, 255]
Note:
When Bit0 is equal to 1, it indicates that in case of both-way CTR tone-playing, the
local office backward sends an ANM message in advance during an incoming half-call
with the R2/CAS signal. Both-way means that the stream media attribute of the tone-
playing terminal is “SendRecieve” during tone playing. Other Bits are reserved.
3.3.76 Continue Call When CAMEL Tone Is too Short for the Calling
User
1851
3-68

Function
This security variable specifies whether to continue a call when the duration of the
CAMEL tone is too short for the calling subscriber, that is, before receiving a
Connect Ack message, the MSCS receives a Disconnect Forward Connection
(DFC) message from the SCP instructing it to stop tone playing.
Default Value
No
Value Range
Value Meaning
The MSCS does not continue the call when the duration of the CAMEL
No
tone is too short for the calling subscriber.
The MSCS continues the call when the duration of the CAMEL tone is
Yes
too short for the calling subscriber.
3.3.77 The Switches of Buffer Scan of CAMEL/HO Module

1852
Function
This security variable specifies whether the modules related to the CAMEL or HO
service scans the related buffer areas to check whether these areas are
suspended.
z Bit 0 of this security variable controls the buffer-area scanning function of the CCF
module.
z Bit 1 of this security variable controls the buffer-area scanning of the SSF module.
z Bit 2 of this security variable controls the buffer-area scanning of the CSA module.
z Bit 3 of this security variable controls the buffer-area scanning of the SRF module.
z Bit 4 of this security variable controls the buffer-area scanning of the HO module.
When a bit is set to “0”, it indicates not scanning the buffer areas. When a bit is
set to “0”, it indicates scanning the buffer areas.
Default Value
Value Range
[0, 255]
3-69

3.3.78 Format Adjustment for MNP Is Needed or Not

1853
Function
This security variable specifies whether to standardize the MSRN when SRI ACK
contains not the MSISDN field but the MSRN field.
Default Value
No
Value Range
Value Meaning
No The MSRN field is not to be standardized.
Yes The MSRN field is to be standardized.
3.3.79 The Indication of Local CLIP Process When Nature of Calling

Number Is Unknown
1862
Function
This security variable specifies how to transform a calling number when nature of
the calling number is unknown in the Calling Number Identification Presentation
(CNIP) of the local office.
Default Value
No
Value Range
Value Meaning
No No special processing
The domestic country code is added in front of the calling number with
Yes
UNK nature when it is transformed to an internal number.
3-70

3.3.80 Routing According to the PLMN-Specific SS Code

1864
Function
This security variable specifies whether the MSCS enables the customized
Supplementary Service (SS) bypassing function.
Default Value
No
Value Range
Value Meaning
No Disabled
Yes Enabled
3.3.81 Paging Protect Time in MSC Pool

1865
Function
An MSCS in the MSC pool mode receives an unknown paging response from a
subscriber. If time difference between the current time of the MSCS and the time
of the MSCS pages this subscriber for the last time is greater than the specified
paging guard time, it indicates that this subscriber returns the paging response
after paging timeout of this MSCS. In this case, this paging response can be
discarded. Otherwise, the NNSF mistakenly distributes this paging response to
this MSCS for processing.
Default Value
20
Value Range
[0, 60]
Unit: second
3-71


Security variable “Paging Protect Time in MSC Pool” is valid only
Support MSC Pool
when the MSC pool function is supported.
3.3.82 DDI Delay Saving Method

1962
Function
This security variable specifies the mode of saving the calling/called number
delay-transformation indexes.
Default Value
Valid value coverage
Value Range
Value Meaning
The index of calling/called number delay transformation obtained
Unconditional Coverage last time is directly overwritten with the index obtained this time in
spite of its validity.
The index of calling/called number delay transformation obtained
Valid Value Coverage last time is overwritten with the index obtained this time only when
this new index is valid.
3.3.83 Threshold of A Interface PCM

2142
Function
This security variable is used to set the trunk load threshold of the A interface.For
the trunk that supports the circuit pool function of the A interface, if the load
exceeds the threshold, the system reduces the trunk load by using the voice
version with lower priority.
Default Value
90
3-72

Value Range
[1, 100]
3.3.84 For MF Calls Triggering at DP Collected_Info whether to

Internationalize the Destination Number Before Matching it
2143
Function
This security variable determines whether to internationalize the destination

number before matching when the call forwarding triggers the IN detection and
triggering standard.
Default Value
No
Value Range
Value Meaning
The system does not internationalize the destination number before
No matching when the call forwarding triggers the IN detection and
triggering standard.
Internationalizes the destination number before matching when the call
Yes
forwarding triggers the IN detection and triggering standard.
3.4 Call Control

Table 9 lists the security variables displayed in the Call Control tab page.
TABLE 9 SECURITY V ARIABLES DISPLAYED IN THE CALL CONTROL TAB P AGE

Whether to Support CUG Service 3-75
ISUP Simulation Failure Code 3-75
Whether to Force Passing on Impossible Indicator 3-77
Whether to Check the PESQ INFO 3-78
The Scale of Reset CIC Per 200 ms 3-78
Support Multiple ColorRing Center by SSCODE Method 3-79
Whether MS Alerts Automatically 3-79
3-73


Whether to Judge the Called Number for Local or Toll in GMSC 3-80
Whether to Pause Call Protecting 3-80
Change Category of Calling User 3-81
CAMEL Service Diff 3-82
Whether RAB Modification of RNC Supported by MSCS 3-83
Whether CODEC Modification Supported by MSCS 3-83
Whether Mid-Call Codec Negotiation Supported by MSCS 3-84
Whether to Support RAB Modification by RNC 3-84
International Calling Dial Method 3-85
Whether to Support Data Transfer Method When MT Control 3-85
Whether HoReq Message Is Transferred in SCCP CR 3-86
Assignment After OP Bearer Established for Terminal Call 3-86
Whether to Release When Call Handling in Abnormity of DDC Announcement 3-87
Whether to Release When Call Handling in Abnormity of DDC Indicator in 3-87
Signalling
Whether to Support Macao SMARTTONE CAMEL Service 3-88
Whether to Support Home Ring Back Tone Service 3-88
Whether to Play Special RBT for Fault Call 3-89
Whether Redirecting Number Present in the Setup Message to the Forwarded- 3-89
to Mobile Subscriber C or Not
V32 Value in Q.931 3-90
Whether to Correct the BC Received From HLR When Facsimile Group 3 3-90
Service in 2G Network Is Used
Delete Special Prefix for International Number in CLIP 3-91
Conversion Mode of ModemType in Bear Capability IE 3-91
Optional IE of L3 Message (to MS) Whether Be Included 3-92
Whether the Mode of Dialed Number With International Prefix+Local CC Is 3-92
Allowed
Whether to Include Facility IE in Alerting Message 3-93
Whether to Support Independent OOBTC While GMSC Forwarding 3-93
Whether to Support Start Bearer Timer While Paging at VMSC 3-94
Whether to Support Start Bearer Timer While Pre-Paging at GMSC 3-94
Forced Release Call Type 3-95
Intelligence Service Charging Warning Tone Playing Times 3-95
Whether to Return CAP Error if Duplicate TSW 3-96
Reserved Variable 3-96
Dialed Number With International Prefix + Local CC + National Prefix Mode 3-97
Control
3-74


Send Busy Tone to User When Call Released in Conversation 3-98
Send Status Enquire to MS 3-98
Support OM in OOBTC 3-99
Support CONC 3-99
Mobile Emergency Call Suppress SS 3-100
Transfer Area Infor in TRACER System 3-100
Use DialedNumber for OSB Analysis 3-101
3.4.1 Whether to Support CUG Service

1032
Function
This security variable specifies whether Close User Group (CUG) call indication is
used during incoming calls. If this security variable is set to No, the system
probably releases the call when the incoming IAM message indicates it is a CUG
call.
Default Value
Yes
Value Range
Value Meaning
No CUG service not supported.
Yes CUG service supported.
3.4.2 ISUP Simulation Failure Code

1036
Function
This security variable specifies the cause value in the REL message that is
transmitted.
3-75

Default Value
0
It indicates that no failure cause is defined.
Value Range
[0, 255]
Value Meaning
0 Unknown
1 Unallocated (unassigned) number
2 No route to specific transit network
3 No route to destination
4 Send special information tone
5 Misdialed the toll prefix
8 Preemption
9 Preemption – circuit reserved for reuse
16 Normal call clearing
17 User busy
18 No user responding
19 No answer from the user
20 Subscriber absent
21 Call rejected
22 Number changed
27 Destination out of order
28 Invalid number format (address incomplete)
29 Facility rejected
31 Normal unspecified
34 No circuit/channel available
38 Network out of order
41 Temporary failure
42 Switching equipment congestion
43 Access information discarded
44 Requested circuit/channel not available
46 Precedence call blocked
47 Resources unavailable, unspecified
50 Requested facility not subscribed
53 Outgoing calls barred within CUG
3-76

Value Meaning
55 Incoming calls barred within CUG
57 Bearer capability not authorized
58 Bearer capability not presently available
62 Inconsistency in designated outgoing access information and subscriber class
63 Service or option not available, unspecified
65 Bearer capability not implemented
69 Requested facility not implemented
70 Only restricted digital bearer capability is available
79 Service or option not implemented, unspecified
87 User not a member of Closed User Group
88 Incompatible destination
90 Non-existent closed user group
91 Invalid transit network selection
95 Invalid message, unspecified
97 Message type non-existent/not implemented
99 Information element/parameter non-existent or not implemented
102 Recovery on timer expiry
103 Parameter non-existent or not implemented, passed on
110 Message with unrecognized parameter, discarded
111 Protocol error, unspecified
127 Interworking unspecified
3.4.3 Whether to Force Passing on Impossible Indicator

1038
Function
This security variable specifies whether to pass on unrecognized parameters

(ABCDbit) without explicit indication. On receipt of some unrecognized
parameters, the system needs to process them according to the compatibility
information. This security variable is set for testing to meet some conditional flows
of the protocol.
Default Value
No
3-77

Value Range
Value Meaning
No The system passes on unrecognized parameters.
Yes The system does not pass on unrecognized parameters.
3.4.4 Whether to Check the PESQ INFO

1039
Function
This security variable specifies whether to audit the bearer network quality during
calls. If this security variable is set to Yes, the audited network quality is compared
with the network thresholds in the static MGW configuration to determine the
optimized coding mode next time.
Default Value
No
Value Range
Value Meaning
No The system does not audit the network bearer quality.
Yes The system audits the network bearer quality on each call.
3.4.5 The Scale of Reset CIC Per 200 ms

1040
Function
During power-on, or when an office is reachable, resetting circuits in batches is

used to reduce the instantaneous load. This security variable specifies the
number of circuits that are reset actively every 200 ms.
Default Value
3-78

Value Range
[1, 6]
3.4.6 Support Multiple ColorRing Center by SSCODE Method

1042
Function
This security variable specifies whether to enable the SSCODE mode to support
the multiple Coloring Ring Back Tone (CRBT) centers.
Default Value
No
Value Range
Value Meaning
The system does not enable the SSCODE mode to support the multiple
No
CRBT center.
The system enables the SSCODE mode to support the multiple CRBT
Yes
centers.
3.4.7 Whether MS Alerts Automatically

1047
Function
This security variable specifies whether the Alerting message sent to the MS
instructs the MS to automatically play the ring back tone (with the progress
indication in the Alerting message).
Default Value
No
Value Range
Value Meaning
No The MS does not automatically play the ring back tone.
Yes The MS automatically plays the ring back tone.
3-79

3.4.8 Whether to Judge the Called Number for Local or Toll in GMSC
1048
Function
The GMSC can check the dialed number in an incoming call. It allows this call to
proceed only when the dialed number meets the following rules.
1. The called number contains an international prefix, such as 0087139****.
2. The called number contains a domestic prefix, such as 0139**** or 02552870108.

If the called number is a fixed number with a domestic prefix, the call proceeds. If
the call comes in from a fixed network of the local toll area, the call is not allowed
to proceed when the called number is not allowed to contain a domestic prefix. If
the call comes in from a fixed network of the non-local toll area, the call is allowed
to proceed when the domestic prefix is required. If the call comes in from a mobile
network, the call is not allowed to proceed when the called number is not allowed
to contain a domestic prefix.
3. The called number does not contain a domestic prefix, such as 139****. If the call
comes in from a fixed network of the local toll area, the call proceeds when the
called number is not allowed to contain a domestic prefix. If the call comes in from
a fixed network of the non-local toll area, the call is not allowed to proceed when
the called number requires a domestic prefix. If the call comes in from a mobile
network, the call proceeds when the called number is not allowed to contain a
domestic prefix.
Default Value
No
Value Range
Value Meaning
No The system does not judge the dialing mode of incoming calls.
Yes The system judges the dialing mode of incoming calls.
3.4.9 Whether to Pause Call Protecting

1049
3-80

Function
This security variable specifies whether to protect calls. It is set to Yes when the
active/standby synchronization is stopped and the standby board is upgraded first.
After both the active and standby boards are successfully upgraded, set this
security variable to No.
Default Value
No
Value Range
Value Meaning
No The system does not stop protecting calls.
Yes The system stops call protection.
3.4.10 Change Category of Calling User

1054
Function
This security variable specifies whether to force to convert the calling subscriber
categories to the value set by the security variable in sending messages.
This security variable takes effect only when the CHGK (Change Calling User
Kind) option in the Enable Options parameter in the Called Number Analysis
Configuration.
Default Value
Unknown
Value Range
Value Meaning
Unknown Unknown
France Operator, language France
English Operator, language English
Germany Operator, language Germany
Russia Operator, language Russia
Spanish Operator, language Spanish
Chinese Negotiated language (Chinese)
3-81

Value Meaning
Consulted Language Negotiated language
Japanese Negotiated language (Japanese)
Domestic National operator
Normal Subscriber Common subscriber
Prior Subscriber Preferential subscriber
Data Service Data call service
Test Call Test call
Pay Phone Paid phone
E911 Call E911 call
Normal Free Common, free
Normal, periodical Common, periodic
Normal, SubscriberSheet, Immediately Common, user list, instance
Normal, Printer, Immediately Common, printer, instance
Prior, free Priority, free
Prior, periodical Priority, periodic
Normal Subscriber (City) Common user (between cities)
3.4.11 CAMEL Service Diff

1058
Function
Different carriers have different requirements for some parameters in different call
scenarios. This security variable is set to different values to meet various
requirements.
Default Value
No difference
Value Range
Value Meaning
No Difference The CTR message contains ipRoutingAddress is allowed.
3-82

Value Meaning
The error cause of the ETC failure to be reported is forcedly set to
capErrETCFail_M (3).
Version negotiation between CAMEL2 and CAMEL3 is allowed.
China Mobile In conversation with the SCP in independent Intelligent Peripheral (IP)
mode, the independent IP, on receipt of an AssistSSFInvoked message,
is allowed to send a response message to the peer Service Switching
Point (SSP).
The CTR message contains ipRoutingAddress is allowed.
CRN is processed according to the requirements of the MT CRDs of
China Unicom
China Unicom.
China Netcom -
The calling number in an IDP message is not added with the country
code of the local office, otherwise, the calling number is converted to its
China TeiTong international number format.
The CTR message contains ipRoutingAddress is allowed.
China Telecom -
3.4.12 Whether RAB Modification of RNC Supported by MSCS

1060
Function
This security variable specifies whether to support the RAB modification triggered
by the RNC.
Default Value
Yes
Value Range
Value Meaning
The system does not support the RAB modification triggered by the
No
RNC.
Yes The system supports the RAB modification triggered by the RNC.
3.4.13 Whether CODEC Modification Supported by MSCS

1061
3-83

Function
This security variable specifies whether to support CODEC modification.
Default Value
Yes
Value Range
Value Meaning
No CODEC modification not supported
Yes CODEC modification supported
3.4.14 Whether Mid-Call Codec Negotiation Supported by MSCS

1062
Function
CODEC negotiation is applicable to the BICC signaling messages transmitted

over the Nc interface and to the ATM bearer or the RTP bearer over the Nb
interface of a gateway. The negotiation function for of the inter-office encoding
and decoding speech means that the two offices negotiate on the consistent
encoding and decoding speech. This security variable specifies whether to
support CODEC negotiation during a call process.
Default Value
Yes
Value Range
Value Meaning
No Code and decode negotiation during a call process not supported.
Yes Code and decode negotiation during a call process supported.
3.4.15 Whether to Support RAB Modification by RNC

1063
Function
This security variable specifies whether the RNC supports the RAB modification.
3-84

Default Value
Yes
Value Range
Value Meaning
No The RNC does not support the RAB modification.
Yes The RNC supports the RAB modification.
3.4.16 International Calling Dial Method

1064
Function
This security variable specifies how to handle the international called number.
Default Value
Without limiting the international number format
Value Range
Value Meaning
Without Limiting the International The system does not restrict the subscribers from
Number Format dialing international numbers.
Forbid to Add "+" Before International The system does not allow “+” in front of the
Prefix international prefix.
The system does not allow the subscribers to dial
Dials International Format Number
international numbers.
3.4.17 Whether to Support Data Transfer Method When MT Control

1065
Function
This security variable specifies how to fill in fields ConnectElement and Structure
in the Setup messages sent to the MS during data service termination.
Default Value
No
3-85

Value Range
Value Meaning
No Without limitation
When ITC is equal to 1 or 2, 1 must be filled in for ConnectElement, and 0
Yes
for Structure.
3.4.18 Whether HoReq Message Is Transferred in SCCP CR

1067
Function
Some BSCs do not support the Connection Request (CR) messages carrying the
HO Request messages. This security variable specifies whether the CR message
carries the HO Request message.
Default Value
Yes
Value Range
Value Meaning
No The CR messages do not carry an HO Request message.
Yes The CR messages carry an HO Request message.
3.4.19 Assignment After OP Bearer Established for Terminal Call

1069
Function
This security variable is a switch for controlling the miss call function.
Default Value
No
Value Range
Value Meaning
No The miss call function is enabled.
3-86

Value Meaning
Yes The miss call function is disabled.
3.4.20 Whether to Release When Call Handling in Abnormity of DDC

Announcement
1072
Function
This security variable specifies whether to release calls when playing DDC
announcement tone failed.
Default Value
No
Value Range
Value Meaning
No The system allows the calls to proceed.
Yes The system releases the calls.
3.4.21 Whether to Release When Call Handling in Abnormity of DDC

Indicator in Signalling
1073
Function
This security variable specifies whether to release calls when some specified
fields in the signaling do not comply with specifications.
Default Value
No
Value Range
Value Meaning
No The system allows the calls to proceed.
Yes The system releases the calls.
3-87

3.4.22 Whether to Support Macao SMARTTONE CAMEL Service

1074
Function
This security variable specifies whether to support the Macao SMARTTONE

CAMEL service.
Default Value
No
Value Range
Value Meaning
No The Macao SMARTTONE CAMEL service not supported.
Yes The Macao SMARTTONE CAMEL service supported.
3.4.23 Whether to Support Home Ring Back Tone Service

1075
Function
This security variable specifies whether to support the home-location ring-back-

tone function.
Default Value
No
Value Range
Value Meaning
No The home-location ring-back-tone function not supported.
Yes The home-location ring-back-tone function supported.
3-88

3.4.24 Whether to Play Special RBT for Fault Call

1078
Function
This security variable specifies whether to play special ringback tone for call
failure.
Default Value
No
Value Range
Value Meaning
No The system does not play special ringback tone for call failure.
Yes The system plays special ringback tone for call failure.
3.4.25 Whether Redirecting Number Present in the Setup Message

to the Forwarded-to Mobile Subscriber C or Not
1084
Function
This security variable specifies whether the L3SETUP message that is sent to the
forwarded-to subscriber C carries the redirecting number. This security variable is
used to handle compatibility of the mobile phones with lower versions.
Default Value
No
Value Range
Value Meaning
The L3SETUP message sent to the forwarded-to subscriber C does not
No
carry the redirecting number.
The L3SETUP message sent to the forwarded-to subscriber C carries
Yes
the redirecting number.
3-89

3.4.26 V32 Value in Q.931

1085
Function
When the defined value of V32 Modem Type in protocol ITU-T Q.931 is
inconsistent in different versions, the configuration of this security variable can be
used.
Default Value
According to the revised definition
Value Range
Value Meaning
According to the revised definition According to the revised definition
According to the former definition
According to the former definition amendment
amendment
3.4.27 Whether to Correct the BC Received From HLR When

Facsimile Group 3 Service in 2G Network Is Used
1086
Function
After this security variable is enabled, the MSC, according to the protocol, corrects
the HLR-generated incomplete Bearer Capability (BC) in the SETUP message
that is sent to the terminal when facsimile group 3 service in a 2G network is used.
Default Value
No
Value Range
Value Meaning
The MSC does not correct the facsimile service BC received from
No
the HLR when facsimile group 3 service in a 2G network is used.
The MSC corrects the facsimile service BC received from the
Yes
HLR when facsimile group 3 service in a 2G network is used.
3-90

3.4.28 Delete Special Prefix for International Number in CLIP

1087
Function
For the calling number identification presentation service, this security variable
specifies whether to delete the special prefix of international numbers according
to the network management configuration.
Default Value
Yes
Value Range
Value Meaning
The system does not delete the special prefix of the international
No
numbers.
The system deletes the special prefix of the international
Yes
numbers.
3.4.29 Conversion Mode of ModemType in Bear Capability IE

1088
Function
If ModemType of L3BC is equal to ModemAuto, this security variable specifies

whether to fill in the values of Negotiation and ext5c fully according to the protocol
when L3BC is converted to ISDNBC.
Default Value
No
Value Range
Value Meaning
The system handles it according to the requirement of the
No
existing network.
Yes The system processes it fully according to the protocol.
3-91

3.4.30 Optional IE of L3 Message (to MS) Whether Be Included

1089
Function
To be compatible with a lower version of the protocol, the security variable

specifies whether to deliver the specified optional fields in the downlink layer-3
message.
Default Value
127
Value Range
[0, 255]
Each bit represents whether to deliver a specific field (0 represents not delivering
the field while 1 represents delivering the field). The corresponding field of each
bit is as follows:
z Bit0: Priority Level (in the setup and callproceeding messages sent to the MS)
z Bit1: Alerting Pattern (in the setup messages sent to the MS)
z Bit2: Network Call Control CAP (in the setup and callproceeding messages sent
to the MS)
z Bit3: Cause of no cli (in the setup messages sent to the MS)
z Bit4：Backup BC
3.4.31 Whether the Mode of Dialed Number With International

Prefix+Local CC Is Allowed
1090
Function
This security variable specifies whether to allow the dialing mode of “international
prefix + local CC”. For example, dialing a number in 0086xxx format in China is
not allowed when this security variable is disabled.
Default Value
No
3-92

Value Range
Value Meaning
Yes The dialing mode of “international prefix + local CC” is allowed.
The dialing mode of “international prefix + local CC” is not
No allowed. The system directly releases the calls with the called
numbers in this format.
3.4.32 Whether to Include Facility IE in Alerting Message

1091
Function
This security variable specifies whether the Alerting message sent to the MS
contains the Facility field. Because some terminals do not the Facility field, the
network uses this security variable to specify whether to deliver this field.
Default Value
No
Value Range
Value Meaning
The Alerting message sent to the MS does not contain the
No
Facility field.
Yes The Alerting message sent to the MS contains the Facility field.
3.4.33 Whether to Support Independent OOBTC While GMSC

Forwarding
1092
Function
This security variable specifies whether the independent coding/decoding

negotiation is performed between the calling party and the forwarded-to party
when the GMSC forwards the call or sends a reconnection message.
Default Value
No
3-93

Value Range
Value Meaning
The independent coding/decoding negotiation is not performed between the
No calling party and the forwarded-to party when the GMSC forwards the call or
sends a reconnection message.
The independent coding/decoding negotiation is performed between the
Yes calling party and the forwarded-to party when the GMSC forwards the call or
sends a reconnection message.
3.4.34 Whether to Support Start Bearer Timer While Paging at VMSC

1093
Function
During paging of a terminating office, the VMSC starts the calling bearer-
monitoring timer to prevent the calling party from expiry.
Default Value
No
Value Range
Value Meaning
No Disabled
Yes Enabled
3.4.35 Whether to Support Start Bearer Timer While Pre-Paging at

GMSC
1094
Function
This security variable specifies whether the GMSC starts the calling bearer-
monitoring timer to prevent the calling party from expiry when the bearer has not
been established at the calling side during an incoming BICC call.
Default Value
No
3-94

Value Range
Value Meaning
No The GMSC does not start the calling bearer-monitoring timer.
Yes The GMSC starts the calling bearer-monitoring timer.
3.4.36 Forced Release Call Type

1097
Function
This security variable specifies whether to enable forced release during the
process of CANCEL LOCATION or the HLR independently inserting subscriber
data.
Default Value
0: None
Value Range
Value Meaning
0: None Disabled
1: ODB Type The ODB type is enabled.
The CANCEL LOCATION type is
2: CANCEL LOCATION Type
enabled.
Both the ODB and the CANCEL
3: ODB and CANCEL LOCATION Type
LOCATION types are enabled.

This security variable is valid only when security variable
Whether to Enable Forced
“Whether to Enable Forced Release Call Function” is set
Release Call Function
to “All HLR”.
3.4.37 Intelligence Service Charging Warning Tone Playing Times

1099
3-95

Function
This security variable specifies the number of times that the charging alarm tone
of the intelligent service is played.
Default Value
10
Value Range
[1, 30]
3.4.38 Whether to Return CAP Error if Duplicate TSW

1100
Function
If a Tsw timer is started currently but the old Tsw timer is not reset, this security
variable specifies whether the system, on receipt of an AC message, returns
CAPError. This security variable is only valid for CAMEL2/3.
Default Value
Yes
Value Range
Value Meaning
If a Tsw timer is started currently but the old Tsw timer is not reset, the
No
system, on receipt of an AC message, does not return CAPError.
If a Tsw timer is started currently but the old Tsw timer is not reset, the
Yes
system, on receipt of an AC message, returns CAPError.
3.4.39 Reserved Variable

1101
Function
Reserved variable
3-96

Default Value
Value Range
[0, 65535]
z Bit0=1: The system supports the second GenericNumber from the intelligent SCP
in called-TCSI.
in forward-OCSI/DCSI/NCSI.
in calling-OCSI/DCSI/NCSI.
in called-VTCSI.
z Bit4=1: Genericnumber is used to fill in the additionCallingPartyNumber field in
the IDP message.
z Bit5=1: It indicates that the performance statistics result is reported during late call
forwarding.
z Bit6=1: It indicates that the MCC directly returns failure in reconnection number
pre-analysis and releases the call.
z Bit7=1: It indicates that the MCC releases the call after the reconnection number
pre-analysis failed.
z Bit8=1: It indicates that the latest BC of the data area is used if the SCP updates
the related BC information.
z Bit9=1: It indicates that the SSF, on receipt of the Exception message of basic call,
sets a timer to wait for the AC message from the SCP.
3.4.40 Dialed Number With International Prefix + Local CC +

National Prefix Mode Control
1103
Function
This security variable specifies whether to restrict the dialing mode of

“international prefix + local CC + national prefix” (such as 00860) when originating
numbers are normalized.
Default Value
No
3-97

Value Range
Value Meaning
No No restriction
Yes Restricted.
3.4.41 Send Busy Tone to User When Call Released in Conversation

1846
Function
This security variable specifies whether the network plays the busy tone to the
subscriber when a call is released during a conversation. It is set when the
network is required to play the busy tone to the party when the other party goes
onhook in a conversation.
Default Value
No busy tone
Value Range
Value Meaning
No busy tone The system does not play the busy tone.
Play Busy Tone for Calling The system plays the busy tone for the calling party when
When Called Hang up at First the called party goes onhook at first.
Play Busy Tone for Called The system plays the busy tone for the called party when
When Calling Hang up at First the calling party goes onhook at first.
Play Busy Tone for User When The system plays the busy tone for the party when the
the Peer Hang up other party goes onhook at first.
3.4.42 Send Status Enquire to MS

1847
Function
This security variable specifies whether to immediately query the MS status after
the call enters the reliable status. If the MS does not support status query, the
network releases the call when the first periodical timer expires.
3-98

Default Value
Yes
Value Range
Value Meaning
No The system does not query the status immediately.
Yes The system queries the status immediately.
3.4.43 Support OM in OOBTC

1849
Function
This security variable specifies whether to support the OM parameter of the

code/decode in the SCL and the ACL.
Default Value
No
Value Range
Value Meaning
The system combines codes/decodes in a normal way when the OM parameter
No
indication in the coding/decoding parameter is 0.
The system does not combine two codes/decodes until the ACS information in
Yes both of them is consistent when the OM parameter indication in the
coding/decoding parameter is 0.
3.4.44 Support CONC

1850
Function
This security variable specifies whether to send a Disconnect message to the MS

in playing a tone for failure.
Default Value
Yes
3-99

Value Range
Value Meaning
The system only sends the Progress message instead of the
No
Disconnect message in playing a tone for failure.
The system sends the Disconnect message in playing a tone for
Yes
failure.
3.4.45 Mobile Emergency Call Suppress SS

2130
Function
This security variable determines whether mobile emergency call suppresses the
supplementary service or not.
Default Value
No
Value Range
Value Meaning
Mobile emergency calls do not suppress the supplementary
No.
service.
Yes Mobile emergency calls suppress the supplementary service.
3.4.46 Transfer Area Infor in TRACER System

2144
Function
This security variable determines whether to transfer the access location

information of the peer end in the TRACER system.
Default Value
No
Value Range
Value Meaning
3-100

Value Meaning
The system does not transfer the access location information
No.
of the peer end in the TRACER system.
Transfers the access location information of the peer end in
Yes
the TRACER system.
3.4.47 Use DialedNumber for OSB Analysis

2145
Function
This security variable determines whether the OSB analyzed number uses
DialedNumber or not.
Default Value
No
Value Range
Value Meaning
No The OSB analyzed number does not use DialedNumber.
Yes The OSB analyzed number uses DialedNumber.
3-101

This page is intentionally blank.
3-102
3-102

Figures
—————————————————————————————————————————————
Figure 1 Structure Tree of Security Variables ........................................................ 1-2

Figure 2 Security Variable Node .......................................................................... 1-3
Figure 3 CS Network Entity Configuration Parameters ............................................ 1-4
I
Figures

Tables
—————————————————————————————————————————————
Table 1 Security Variables Displayed in the Service Control Variable Tab Page ........... 2-1
Table 2 Security Variables Displayed in the Service Control Function Set Tab Page ....2-48
Table 3 Security Variables Displayed in the Other Variable Tab Page .......................2-55
Table 4 Security Variables in Other Function Set...................................................2-87
Table 5 Security Variables Displayed in the License Tab Page .................................2-93
Table 6 System Control Parameters ..................................................................... 3-1
Table 7 Security Variables Displayed in the CS Security Parameter Tab Page ............3-21
Table 8 Security Variable Displayed in the CS Network Entity Config Tab Page ..........3-27
Table 9 Security Variables Displayed in the Call Control Tab Page ...........................3-73
III
Tables

Index
———————————————————————————————————————————
—A— —N—
Alarm Networking mode .............................................3‐60, 3‐62
Man‐machine command ............................. 2‐59, 2‐60
authentication ....................... 2‐96, 2‐97, 3‐22, 3‐25, 3‐32
—O—
—C— Office
local office... 2‐3, 2‐37, 2‐41, 2‐46, 2‐59, 2‐82, 2‐85, 3‐
Clock running mode 66, 3‐67, 3‐70, 3‐83
free .............................................................. 2‐50, 3‐82 Operator.....................................2‐2, 2‐39, 3‐10, 3‐81, VIII
trace ............................................................ 2‐57, 2‐58
Congestion... 2‐2, 2‐20, 2‐21, 2‐22, 2‐23, 2‐24, 2‐25, 2‐26,
2‐27, 2‐28, 2‐29, 2‐30, 2‐31, 3‐13, 3‐14, 3‐15, 3‐16, 3‐ —P—
19 PCM.....................................................................2‐8, 2‐42
Performance
—D— Performance statistics .......................................... 3‐97
Power on .................................................................... 3‐78
Data Prefix ................... 3‐28, 3‐51, 3‐74, 3‐85, 3‐91, 3‐92, 3‐97
Data synchronization................. 2‐99, 3‐28, 3‐60, 3‐61
Data configuration............................................ 3‐29, 3‐66
data synchronization ..................................................3‐61 —S—
Digit analysis selector .................................................2‐52 Security variable 1, I, 1‐1, 1‐2, 1‐3, 1‐4, 2‐1, 2‐3, 2‐4, 2‐5,
2‐6, 2‐7, 2‐8, 2‐9, 2‐10, 2‐11, 2‐12, 2‐13, 2‐14, 2‐15,
—E— 2‐16, 2‐17, 2‐18, 2‐19, 2‐20, 2‐21, 2‐22, 2‐23, 2‐24, 2‐
25, 2‐26, 2‐27, 2‐28, 2‐29, 2‐30, 2‐31, 2‐32, 2‐33, 2‐34,
Equipment commissioning process 2‐35, 2‐36, 2‐37, 2‐38, 2‐39, 2‐40, 2‐41, 2‐42, 2‐43, 2‐
Handover........ 3‐27, 3‐30, 3‐39, 3‐43, 3‐44, 3‐65, 3‐66 44, 2‐45, 2‐46, 2‐47, 2‐48, 2‐49, 2‐50, 2‐51, 2‐52, 2‐53,
2‐54, 2‐55, 2‐56, 2‐57, 2‐58, 2‐59, 2‐60, 2‐82, 2‐83, 2‐
—F— 84, 2‐85, 2‐86, 2‐87, 2‐88, 2‐89, 2‐90, 2‐91, 2‐92, 2‐93,
2‐94, 2‐95, 2‐96, 2‐97, 2‐98, 2‐99, 2‐100, 2‐101, 2‐102,
Failure 2‐103, 2‐104, 2‐105, 2‐106, 3‐1, 3‐2, 3‐3, 3‐4, 3‐5, 3‐6,
Failure observation............................. 2‐57, 2‐89, 2‐90 3‐7, 3‐8, 3‐9, 3‐10, 3‐11, 3‐12, 3‐13, 3‐14, 3‐15, 3‐16,
3‐17, 3‐18, 3‐19, 3‐20, 3‐21, 3‐22, 3‐23, 3‐24, 3‐25, 3‐
—H— 26, 3‐27, 3‐29, 3‐30, 3‐31, 3‐32, 3‐33, 3‐34, 3‐35, 3‐36,
3‐37, 3‐38, 3‐39, 3‐40, 3‐41, 3‐42, 3‐43, 3‐44, 3‐45, 3‐
Heartbeat ..................................................... 2‐1, 2‐4, 2‐5 46, 3‐47, 3‐48, 3‐49, 3‐50, 3‐51, 3‐52, 3‐53, 3‐54, 3‐55,
3‐56, 3‐57, 3‐58, 3‐59, 3‐60, 3‐61, 3‐62, 3‐63, 3‐64, 3‐
—L— 65, 3‐66, 3‐67, 3‐68, 3‐69, 3‐70, 3‐71, 3‐72, 3‐73, 3‐75,
3‐77, 3‐78, 3‐79, 3‐80, 3‐81, 3‐82, 3‐83, 3‐84, 3‐85, 3‐
label .................................................................. 2‐41, 2‐42 86, 3‐87, 3‐88, 3‐89, 3‐90, 3‐91, 3‐92, 3‐93, 3‐94, 3‐95,
3‐96, 3‐97, 3‐98, 3‐99
SIP office configuration .............................................. 2‐52
—M—
mapping............................................................ 2‐37, 2‐38 —T—
Trunk group configuration ......................................... 2‐52
V
Glossary
———————————————————————————————————————————
ANN
- Answer signal, No Charge
AoIP
- A over IP
ARD
- Access Restriction Data
ATI
- Any Time Interrogation
BC
- Bearer Capability
BSS
- Base Station System
CDR
- Call Detailed Records
CNIP
- Calling Number Identification Presentation
CR
- Connection Request
CRBT
- Coloring Ring Back Tone
DFC
- Disconnect Forward Connection
CMN
- Call Mediation Nodes
DNS
- Domain Name Server
DTMF
- Dual-Tone Multi-Frequency
CTR
- Connect To Resource
EGSM
- Extended GSM
EMLPP
- Enhanced Multi-Level Precedence and Pre-emption
VII
ENUM
- E.164 Number Mapping
ETC
- Establish Temporary Connection
GA
- Geographical Area
IMEI
- International Mobile Equipment Identifier
IP
- Intelligent Peripheral
MO
- Mobile-Originated
MPTY
- Multi-Party
MS
- Mobile Station
NISU
- Network-Initiated Service Upgrade
NNI
- Network-Network Interface
OSB
- Operator Specific Barring
PPS
- PrePaid Service
RAN
- Radio Access Network
SA
- Service Area
SCUDIF
- Service Change and UDI Fallback
SCP
- Service Control Point
SMS
- Short Message Service
SMSC
- Short Message Service Center
SRF
- Specialized Resource Function
SS
- Supplementary Service
SSP
- Service Switching Point
VIII
Glossary
TCSI
- Terminating CAMEL Subscriber Information
UE
- User Equipment
VAS
- Value-Added Service
IX

SJ-20101208143956-014-ZXWN MSCS (V4.10.13) MSC Server Security Variable Reference

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

SJ-20101208143956-014-ZXWN MSCS (V4.10.13) MSC Server Security Variable Reference

Diunggah oleh

Hak Cipta:

Format Tersedia

ZXWN MSCS

Serial Number: SJ-20101208143956-014

Publishing Date: 2011-2-28(R1.0)

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

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

1.2 Modifying Security Variables.......................................................................... 1-2

Chapter 2 Common Security Variables....................................................................2-1

2.1.1 Maximum Call Diversion Times............................................................................2-3

2.1.2 Whether to Support Larger-Than-Limit Forward Times in Signaling Codec .........2-4

2.1.3 DualHome Heartbeat Interval ..............................................................................2-4

2.1.4 DualHome Heartbeat Try Times...........................................................................2-5

2.1.5 Whether to Delete VLR Data After Switching.......................................................2-5

2.1.6 Whether to Delete VLR Data in Appointed Time ..................................................2-6

2.1.7 Show Original and Modified Sig Message ...........................................................2-6

2.1.9 Whether to Support Incoming IP Test Call ...........................................................2-7

2.1.10 The Type of Test Termination of IP Load Control Test Call.................................2-8

2.1.11 The Reference Value of Delay for 100 ...............................................................2-8

2.1.12 The Reference Value of Delay for 60 .................................................................2-9

2.1.13 The Reference Value of Lost for 100 ............................................................... 2-11

2.1.14 The Reference Value of Lost for 60 .................................................................2-12

2.1.15 The Reference Value of Jitter for 100 ..............................................................2-13

2.1.16 The Reference Value of Jitter for 60 ................................................................2-15

2.1.17 The Weight for Delay .......................................................................................2-16

2.1.18 The Weight for Lost..........................................................................................2-17

2.1.20 The Reference Value of Congest Lever 1 ........................................................2-20

2.1.21 The Reference Value of Congest Lever 2 ........................................................2-21

2.1.22 The Reference Value of Congest Level 3 ........................................................2-22

2.1.23 The Reference Value of Congest Level 4 ........................................................2-23

2.1.24 The Reference Value of Congest Level 5 ........................................................2-24

2.1.25 The Step of Normal Level ................................................................................2-25

2.1.26 The Step of Congestion Level 1.......................................................................2-26

2.1.27 The Step of Congestion Level 2.......................................................................2-27

2.1.28 The Step of Congestion Level 3.......................................................................2-28

2.1.29 The Step of Congestion Level 4.......................................................................2-29

2.1.30 The Step of Congestion Level 5.......................................................................2-30

2.1.31 The Hour of Time for Counter Check ...............................................................2-31

2.1.32 The Minute of Time for Counter Check ............................................................2-32

2.1.33 Support User Level in IP_LoadCtrl Function....................................................2-33

2.1.36 The Upper Limit of National Number Length....................................................2-35

2.1.37 The Upper Limit of Subscriber Number Length................................................2-36

2.1.38 Whether the Fail Announce Counted in Call Completed Ratio.........................2-37

2.1.40 WCDMA Network Type ....................................................................................2-38

2.1.41 Forbid Calling Number in Outgoing Signaling ..................................................2-38

2.1.45 Whether COT is Expected ...............................................................................2-40

2.1.46 IWF Description Type in SDP ..........................................................................2-42

2.1.47 Speed Variable of GRS Sent............................................................................2-43

2.1.49 Allow Scan NNI Data........................................................................................2-45

2.1.50 Support Modify Caller Number Totally for Inter-Office DDI...............................2-45

2.1.51 Whether ACM with Wait Indicator or Not..........................................................2-46

2.1.52 Transmit Unknown Parameter in ISUP ............................................................2-46

2.1.53 Which DTone Signal Need to Detect................................................................2-47

2.1.54 Ratio between Max-Forwards and Hop Counter..............................................2-48

2.2 Service Control Function Set ....................................................................... 2-48

2.2.1 Need Terminal for SIP in and SIP Out................................................................2-49

2.2.2 Support Routing by Dialed Number Length .......................................................2-49

2.2.3 Not Pass Through Signal's Free Charge Indication ...........................................2-50

2.2.4 Control Countering of Answer Times .................................................................2-51

2.2.5 Use Satellite Circuit for ISUP .............................................................................2-51

2.2.6 Support Routing by Calling Number ..................................................................2-52

2.2.7 Priority to Use T38 Fax ......................................................................................2-52

2.2.8 Continue to Detect DTone After CED Is Detected..............................................2-53

2.2.9 VAD Controlled When Alerting ...........................................................................2-53

2.3 Other Variables ............................................................................................ 2-54

2.3.1 Max Count of Message to OMC.........................................................................2-56