Académique Documents
Professionnel Documents
Culture Documents
HUAWEI HSS9860
(V900R008C50)
2014-11
Contents
(V900R008C50)..................................................................................................................................1
Huawei Technologies Co., Ltd...........................................................................................................1
Contents..............................................................................................................................................2
1 Revision History..........................................................................................................................19
2 Overview.......................................................................................................................................25
2.1 System Description..........................................................................................................................................25
2.2 Network Connection........................................................................................................................................26
2.3 Terms................................................................................................................................................................26
3 Stipulation....................................................................................................................................28
4 Time Setting.................................................................................................................................30
4.1 Handshake Message Time...............................................................................................................................30
4.2 Command Reply Time.....................................................................................................................................30
5 Communication Protocol...........................................................................................................31
6 Command Syntax........................................................................................................................32
7 Command Output........................................................................................................................34
7.1 General Message Format (TCP Port 7777)......................................................................................................34
7.2 General Message Format (TCP Port 7776)......................................................................................................35
7.3 Difference Between Messages over Port 7776 and Port 7777.........................................................................36
7.4 Operation Success Message.............................................................................................................................37
7.5 Operation Failure Message..............................................................................................................................37
7.6 Description of Query Result............................................................................................................................37
8 Key Parameters............................................................................................................................40
9 Summary of Commands.............................................................................................................41
9.1 Operator Login.................................................................................................................................................41
9.2 Operator Logout...............................................................................................................................................42
9.3 Add a Subscriber Using Template....................................................................................................................42
9.4 Delete Subscriber.............................................................................................................................................43
9.5 Query Static Data of a Subscriber....................................................................................................................44
10 Common Enumerations..........................................................................................................554
10.1 TSCODE (Telecommunication Service Code) Enumeration.......................................................................554
10.2 BSG (Basic Service Group for all Supplementary).....................................................................................554
10.3 CBBSG (Basic Service Group for Call Barring) Enumeration...................................................................555
10.4 CFBSG (Basic Service Group for Call Forwarding) Enumeration.............................................................555
10.5 CWBSG (Basic Servic Group for Call Waiting) Enumeration....................................................................555
10.6 BSCODE (Bearer Service Code) Enumeration...........................................................................................556
10.7 BASCODE (Basic Service Code)................................................................................................................556
10.8 DSCODE (Data Service Code)....................................................................................................................558
10.9 CAMEL Phase Enumeration........................................................................................................................559
10.10 TSCODE and DSCODE Enumeration.......................................................................................................559
10.11 BasicServiceCode Enumeration.................................................................................................................560
10.12 ODB Enumeration.....................................................................................................................................566
10.13 NAM (Network Access Mode) Enumeration............................................................................................567
10.14 SMDP (Short Message Delivery Path) Enumeration.................................................................................567
10.15 CSITYPE (the Type Enumeration to Type)...............................................................................................567
10.16 SERVICE_PROPERTY (Service Property Enumeration List for Called Number Analysis) Enumeration
.............................................................................................................................................................................568
10.17 Priority Locate Flag (PLF) Enumeration...................................................................................................568
10.18 Privacy Exception1-SS Code (LCSPCODE) Enumeration.......................................................................569
10.19 Privacy Exception1-SS STatus (LCSSTATUS) Enumeration...................................................................569
10.20 Privacy Exception1-NotificationToMsUser (LCSNOTIFY) Enumeration...............................................569
10.21 PrivacyException1-ExceptionClientList1-GMLC-Restrict(LCSPGMLCR) Enumeration.......................570
10.22 Privacy Exception1-PlmnClientList (LCSPLMNCL) Enumeration.........................................................570
10.23 Molr-ss-code (LCSMOLRCODE) Enumeration.......................................................................................570
10.24 Molr-ss- STatus (LCSMOLRSTATUS) Enumeration...............................................................................571
10.25 Category Enumeration...............................................................................................................................571
10.26 GPRS Qos Enumeration Value for GPRS_BIT_RATE:............................................................................572
10.27 GPRS Qos Enumeration Value for GPRS_EXT_BIT_RATE:..................................................................580
10.28 GPRS Qos Enumeration Value for GPRS_MEAN_THROUGHPUT:......................................................589
10.29 GPRS Qos Enumeration Value for GPRS_PEAK_THROUGHPUT:.......................................................590
12 Abbreviations:...........................................................................................................................636
1 Revision History
2012-12-03 HSS9860 Modified the commands MOD MNUG, LST MNUG, MOD COMISDN:
V900R008C01 Added the MOD MSIM, LST MSIM commands.
Added the error codes:
ERR3076: Request own MSISDN not possible
ERR3335: Forbid removing the primary subscriber in a Multi-SIM
group
ERR3336: COMISDN number is not the primary subscriber in a
Multi-SIM group
ERR3337: Forbid deactivating the primary subscriber in a Multi-SIM
group
ERR3338: Forbid modifying MSISDN of the primary subscriber used
for Multi-SIM
ERR3269: :A group member associated with multiple profiles cannot
be deleted independently
ERR3270: The group does not exist
ERR3271: The number of group members exceeds the maximum
ERR3272: The group member number cannot be a special number
ERR3273: The group member must be defined
ERR3274: A number can belong to only one group
ERR3275: The entered number is not a group pilot number
ERR3276: The entered number is already in use
ERR3277: Sending Cancelocation fails during active number change.
You must manually send Cancelocation
ERR3353: Forbid modifying the order of the primary subscriber in a
Multi-SIM group
ERR3354: Forbid removing an auxiliary subscriber in a Multi-SIM
group
2012-12-04 HSS9860 Modified the command LST DYNSUB:
V900R008C01 Added one paramete: MTRFSupported in return reports in the above
command
2012-12-26 HSS9860 Modified the commands MOD GROUPSIM, LST GROUPIM, MOD
V900R008C01 GROUPUSER, LST SUB:
Added the commands MOD/LST NTCSI
Added the error codes:
ERR3355:The MMS activation isdn must be a member isdn
ERR3356:The LCS activation isdn must be a member isdn
ERR3357:Updating a group MSISDN's data succeeds but updating a
GROUPSIM member's data fails
2013-01-09 HSS9860 Modified the commands ADD SUB, LST SUB,MOD EIN and LST EIN.
V900R008C01 Added the commands MOD/LST PREMSMS
2013-1-25 HSS9860 Modified the command LST DYNSUB:
V900R008C01 Added two parametes: URRP-MME and URRP-SGSN in return reports in
the above command
2 Overview
2.3 Terms
Business Hall Interface
The business hall interface is a string command line that is supported by Huawei HSS9860.
These command lines can be used to define or remove a subscriber, or query or modify
subscription data.
3 Stipulation
The following symbols are used to describe the remarks of the command parameters:
C: means conditional. The parameter of the default value is to be given at least.
M: means mandatory. That is, the parameter must be set.
O: means optional. That is, the parameter may or may not be set.
4 Time Setting
5 Communication Protocol
After the business hall client connects to the PGW, it can manage the service data of mobile
subscribers through the business hall interface commands.
The business hall client interface commands are in the form of command line, are transferred
between the business hall client and the PGW in character stream..
The format of the command string is as follows:
Command Name: parameter 1=parameter value 1, parameter 2=parameter value 2;
For description on the command string, see 6 "Command Syntax."
6 Command Syntax
There are six types of parameters, including the numeral, the Boolean, the string, the
enumeration, the date type and the time type. The values of different types of parameters are
as in different forms:
String
The value of the parameter is a string consisting of the characters from A to Z, from a to
z, from 0 to 9, or other characters in the formats that the WINDOWS operating system
supports.
Numeral
The value of the parameter is an Arabic number consisting of the digits from 0 to 9
Boolean
The value of the parameter can be TRUE or FALSE.
Enumeration type
The values of the parameter are enumerated names or values. ( In command line, the
enumerated name and enumerated value can be interchangeable.for example :enumerated
name TRUE,FALSE can be interchanged by 1,0)
Date type
The format of the date and time must be YYYY-MM-DD HH:MM:SS (or
YYYY&MM&DD&HH&MM&SS).
7 Command Output
The PGW will return the output of each command to the business hall after processing the
command, no matter whether the execution succeeds or not. The output is classified into three
types of messages: success message, error message, and querying result.
The error code rules are as follows:
Operation success message: The error codes must be SUCCESS0001, SUCCESS0002,
SUCCESS0003, SUCCESS0004, SUCCESS0005, SUCCESS0006, SUCCESS0007,
SUCCESS0008, SUCCESS0009, and SUCCESS0010, and SUCCESS0011.
Operation failure message: When the provisioning system matches error messages, only
the prefix ERR is matched, and the specific error code and the description of error codes
are not matched. If an error message does not contain prefix ERR, the provisioning
system searches for the RETCODE. Error codes can contain 4 digits or 9 digits. Error
codes with 9 digits begin with number 9.
<message details>
--- END
Example:
+++ HLR9820 2003-11-21 08:54:14
SMU #000324
%%LGI:OPNAME="admin", PWD="*****";%%
SUCCESS0001:Operation is successful
<message details>
--- END
or
+++ USCDB <date> <time>
PGW #<serial number>
%%<command string>%%
RETCODE = <error code> <message description>
<message details>
--- END
Example:
+++ USCDB 2011-01-28 17:02:52
PGW #002492
%%SET MAPSERV: CFNRTIME=30, MAXTIMECALLFWD=5;%%
RETCODE = 0 SUCCESS0001:Operation is successful
--- END
or
+++ USCDB 2014-01-20 16:17:45
--- END
or
+++ USCDB 2014-11-25 10:45:04
PGW #000503
%%CHK HKI: IMPI="impiinfo", K="*****";%%
RETCODE = 900001007 The value is invalid. <"******"> for <"K">
2. Horizontal format (Each pair of parameter name and parameter value occupies two lines.)
As for the query command, the format of the returned message is as follows:
parameter 1 parameter 2 ...
result 1 result 2 ...
For example, the output for the command LST HSUBINFO: SUBID="6290000001"is as
follows:
+++ USCDB 2014-11-07 18:22:36
PGW #014973
%%LST HSUBINFO: SUBID="6290000001";%%
RETCODE = 0 SUCCESS0001:Operation is successful
SUBID SUBINFO
6290000001
Total count = 1
--- END
Some LST command outputs described in section 9 are displayed with each pair of parameter name
an parameter value occuping two lines. Because all the parameters cannot be displayed in one line,
the parameters are displayed in sevaral lines. You can read the output from the left to the right, from
the top to the bottom, and from the first line to the last line.
SUBID = subinfo
IMSI MASTERFLAG
1234567891 1
1234567892 0
1234567893 0
1234567894 0
1234567895 0
Total count = 6
--- END
2) Mixed format 2 (Each pair of parameter name and parameter value occupies two lines, and
then each pair of parameter name and parameter value occupies two lines.)
As for the query command, the format of the returned message is as follows:
parameter 1
result 1
parameter 2 parameter 3 ...
result 2 result 3 ...
For example, the output for the command LST HSTDPRIOR:
IMPU="sip:impuinfo@huawei.com" is as follows:
+++ USCDB 2014-11-07 18:19:42
PGW #014949
%%LST HSTDPRIOR: IMPU="sip:impuinfo@huawei.com";%%
RETCODE = 0 SUCCESS0001:Operation is successful
STDPRIOR
2
Total count = 2
8 Key Parameters
According to the preceding description, pay attention to the following when setting up the
communication between the business hall system and the PGW:
The PGW opens the TCP port (For a specific port number, run the LST PORT command
with Service type of port set to GU-HLR on the USCDB MML Command Interface of
the OMU client).
The IP addresses of the PGW may vary with the sites.
The business hall client, as the client, must actively send the connection request to the
PGW. If the connection between the business hall client and the PGW is interrupted for
some reasons, the business hall client must actively send connection request to the PGW.
The business hall client must send handshake messages to the PGW within the maximum
handshake duration of the PGW on a regular basis. The time interval between the
handshake messages can be set to 20 seconds.
The business hall client regards that the command fails if it does not receive the response
from the PGW within 60 seconds.
The number of connections established between the PGW and the business hall client is
limited. The maximum number is fifty for one PGW by default, and is three hundred for
six PGW by configuration.
The PGW processes the requests in serial mode. That is, the PGW will process a
command sent from the business hall only after the PGW finishes processing the
previous command.
9 Summary of Commands
Example:
LGI: HLRSN =2, OPNAME="NKR", PWD="*****";
Response:
If the operation succeeds, the following success code is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
ADD TPLSUB: HLRSN =2, IMSI="345612789012345",
ISDN="013623456789",TPLID=4,LINE2NUM="555555555555555";
Response:
If the operation succeeds, the following success code is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details on the preceding error codes,
see 11"Summary of Error Codes".
HLRSN is not present when the current PGW is a common version, and It is a mandatory parameter
when the current PGW is a redundant version and has no default value.
Example:
RMV SUB: ISDN="13623456789", RMVKI=TRUE;
Response:
If the operation succeeds, the message returned is:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST SUB: IMSI="955678112", DETAIL= TRUE;
Response:
If the operation succeeds, the format of the returned message is as follows:
{HLRSN}=< HLR Serial No in the redundant HLR center >
{IMSI}= <IMSI Number>
{ISDN}=<MSISDN Number>
{ISDN}=< MSISDN Number For Line2 of Alternative Line Service >
"Session Transfer Number for SRVCC"
{STNSR}=<Session Transfer Number for Single Radio Voice Call Continuity>
{SMDP}=<MSC|SGSN>
{NAEA}=<0-9999|NOTPROV>
{NLRInd}=<NONE|GSM|GPRS|BOTH>
{ALS}=<"PROV"|"NOTPROV">
{LINE2NUM}=< MSISDN Number For Line2 of Alternative Line Service >
{VVDN}=<"PROV"|"NOTPROV">
{RBT}=<0~254|NOTPROV>
"OfferedCAMEL4CSIsInVLR"
{O-CSI}
{D-CSI}
{VT-CSI}
{T-CSI}
{MT-SMS-CSI}
{MG-CSI}
{PSI-Enhancements}
"OfferedCAMEL4CSIsInSGSN"
{MT-SMS-CSI}
"Supported LCS"
{MSC Supported LCS Capability Set1} = <TRUE |FALSE>,
{MSC Supported LCS Capability Set2} = <TRUE |FALSE>,
"SMS Route"
{SMSROUTETPL}=<0~65534>
Example:
LST DYNSUB: ISDN="955678112";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <Subscriber's MAIN IMSI >
{ISDN}=<MSISDN Number>
{CALL_INDEX} = < 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9>
{IMSI2} = <IMSI Number 2>
{CALL_INDEX} = < 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9>
{IMSI3 = <IMSI Number 3>
{CALL_INDEX} =< 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9>
{IMSI4} = <IMSI Number 4>
{SC3}={SC address3},
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If the parameter CONTENT is set to the default value. ALL the dynamic data in all the result sections will
be displayed.
If the parameter CONTENT is set to GSM , only the dynamic data in section "Dynamic Status Information
For GSM' " will be displayed.
If the parameter CONTENT is set to GPRS, only the dynamic data in section "Dynamic Status information
For GPRS" will be displayed.
If the parameter CONTENT is set to SM, only the dynamic data in sections "Short Message Dynamic data
for GSM", "Short Message Dynamic data for GPRS", and "Short Message Center Information" will be
displayed.
If the parameter CONTENT is set to ODB, only the dynamic data in section "ODB Unsupported Features
For GSM" and "ODB Unsupported Features For GPRS" will be displayed.
If the parameter CONTENT is set to UNSP, only the dynamic data in sections "unsupported TeleService
Feature", "Unsupported Bearer Service Feature", and "Unsupported Supplementary Service Feature" will be
displayed. In these sections, only the unsupported services will be displayed.
If the parameter CONTENT is set to LCS, only the dynamic data in Section "Supported LCS" will be
displayed.
If the parameter CONTENT is set to ALLSM, only the dynamic data in sections "Short Message Dynamic
data for GSM", "Short Message Dynamic data for GPRS", and "Short Message Center Information" will be
displayed.,all the short message center will be displayed.
Example:
MOD LCK: IMSI="984519856312345",IC=TRUE,OC=FALSE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST LCK:IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
{IC}=<TRUE|FALSE>
{OC}=<TRUE|FALSE>
{GPRSLOCK}=<TRUE|FALSE>
{CSUPLLCK}=<TRUE|FALSE>
{PSUPLLCK}=<TRUE|FALSE>
{EPSLOCK}=<TRUE|FALSE>
{NON3GPPLOCK}=<TRUE|FALSE>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD GPRSLCK: IMSI="984519856312345",LOCK=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST GPRSLCK: IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
Example:
MOD SABLCK: IMSI="984519856312345",IC=TRUE,OC=FALSE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST SABLCK: IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>,
{ISDN}=<MSISDN Number>
{IC}=<TRUE|FALSE>
{OC}=<TRUE|FALSE>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
SET MULTISDN: IMSI="444440123456789", ISDN="9854670023",
DEFAULTCALL=BS21, BCALIAS="BC";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002: Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
MOD IMSI: ISDN="9854670023", NEWIMSI ="438320000247111";
Response:
If the operation succeeds, the following success code is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST IMSI: ISDN="9854670023";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
{IMSI2} = <IMSI2 Number>
{IMSI3 = <IMSI3 Number>
{IMSI4} = <IMSI4 Number>
{IMSI5} = <IMSI5 Number>
{IMSI6} = <IMSI6 Number>
{IMSI7} = <IMSI7 Number>
{IMSI8} = <IMSI8 Number>
{IMSI9} = <IMSI9 Number>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD ISDN: ISDN="934567901", NEWISDN="9854670023";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST ISDN: IMSI="452323132423";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN} = < MSISDN Number >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD TELE: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
MOD SMSMT: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD SMSMO: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD TS61: IMSI="444441234567890", PROV=TRUE;
Response:
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD TS62: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST TS: IMSI="444440123456789";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{MSISDN}=<MSISDN Number>
{TSCODE}=<List of all teleservice code which is subscribed by mentioned MSISDN>...
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
This command is only applied to the subscriber whose NAM is BOTH or MSC, and only 3G subscribers
can subscribe to this service.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS21: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD BS22: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS23: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS24: IMSI="444441234567890",PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD BS25: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS26: IMSI="444441234567890",PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS30: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS31: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS32: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS33: IMSI="444441234567890", PROV=TRUE;
Response:
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS34: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS41: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS43: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD BS44: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS45: IMSI="444441234567890",PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS46: IMSI="444441234567890",PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS51: IMSI="444441234567890",PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS52: IMSI="444441234567890",PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS53: IMSI="444441234567890",PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS61: IMSI="444441234567890",PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS81: IMSI="444441234567890",PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST BS: IMSI="444440123456789";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{MSISDN}=<MSISDN Number>
{BSCODE}=<List of all bearer service code which is subscribed by mentioned MSISDN>...
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ODBSS: IMSI="984519856312345",ODBSS=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ODBIC: IMSI="984519856312345",ODBIC=BAIC;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ODBPB1: IMSI="984519856312345",ODBPB1=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ODBPB2: IMSI="984519856312345",ODBPB2=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ODBPB3: IMSI="984519856312345",ODBPB3=TRUE;
Response:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ODBPB4: IMSI="984519856312345",ODBPB4=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ODBENTE: IMSI="984519856312345",ODBENTE=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The subscriber whose NAM is SGSN cannot subscribe to the ODB-Barring of Outgoing Entertainment
Calls service.
Example:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
MOD ODBROAM: IMSI="984519856312345",ODBROAM=NOBAR;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST ODBDAT: IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>
{ISDN}=<MSISDN number>
{ODBSS}=<TRUE|FALSE>
{ODBIC}=<"NOBIC"|"BAIC"|"BICROAM">
{ODBOC}=<"NOBOC"|"BAOC"|"BOIC"|"BOICEXHC"|"BOCROAM">
{ODBPB1}=<TRUE|FALSE>
{ODBPB2}=<TRUE|FALSE>
{ODBPB3}=<TRUE|FALSE>
{ODBPB4}=<TRUE|FALSE>
{ODBENTE}=<TRUE|FALSE>
{ODBINFO}=<TRUE|FALSE>
{ODBROAM}=<"NOBAR"|"BROHPLMN"|"BROHPLMNC"|"BROHPLMNCGPRS">
{ODBRCF}=<"NOBRCF"| "BRACF"| "BRICFEXHC"| "BRICF" >;
{ODBECT}=<"NoBECT"|"BAllECT"|"BChargeableECT"|"BInternationalECT"
|"BInterzonalECT">
{ODBDECT}=<TRUE|FALSE>
{ODBMECT}=<TRUE|FALSE>
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CLIP:IMSI="345126789012345",PROV=FALSE;
MOD CLIP:IMSI="345126789012345",PROV=TRUE,OVERRIDE=FALSE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, the parameter OVERRIDE need not be specified.
If the parameter PROV is set to TRUE, the parameter OVERRIDE is mandatory.
Example:
LST CLIP: IMSI="345126789012345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= <MSISDN number>
{STATUS}= <PROV|NOTPROV>
{OVERRIDE}=<TRUE|FALSE>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD CLIR: IMSI="345126789012345",PROV=FALSE;
MOD CLIR: IMSI="345126789012345",PROV=TRUE,MODE=TEMPALLOWED;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, the parameter MODE need not be specified.
If the parameter PROV is set to TRUE, the parameter MODE is mandatory.
Example:
LST CLIR: IMSI="345126789012345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= <MSISDN number>
{STATUS}=<PROV|NOTPROV>
{MODE}= <PERMANENT|TEMPALLOWED|TEMPRESTRICTED>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD COLP: IMSI="345126789012345",PROV=TRUE,OVERRIDE=FALSE;
MOD COLP: IMSI="345126789012345",PROV=FALSE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, the parameter OVERRIDE need not be specified.
If the parameter PROV is set to TRUE, the parameter OVERRIDE is mandatory.
Example:
LST COLP: IMSI="345126789012345";
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD COLR: IMSI="345126789012345",PROV=FALSE;
Response:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
LST COLR: IMSI="345126789012345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= < MSISDN number>
{STATUS}= <PROV|NOTPROV>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST PRERES: IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
{CLIP}=<TRUE|FALSE>
{OVERRIDE}=<TRUE/FALSE>
{CLIR}=<TRUE|FALSE>
{MODE}=<PERMANENT/TEMPALLOWED/TEMPRESTRICT>
{COLP}=<TRUE|FALSE>
{OVERRIDE}=<TRUE/FALSE>
{COLR}=<TRUE|FALSE>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CFU: IMSI="123454321234543",PROV=TRUE,OFAID=2,NCS=TRUE,
COU= SUBSCRIBER;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, the parameters OFAID, NCS, and COU need not be specified.
If the parameter PROV is set to TRUE, the parameters OFAID, NCS, and COU are optional.
Example:
REG CFU:IMSI="123454321234543",FTN="013645678901", PROPERTY=NATIONAL,
BSG=ALL;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is ALL.
In the MAPCONF command, when RETCODE_MODE is TRUE, SUCCESS0002 is mapped to
ERR3006. The default value of RETCODE_MODE is TRUE.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, the parameters OFAID, NCS, NFS, and COU need not be
specified.
If the parameter PROV is set to TRUE, the parameters OFAID, NCS, NFS, and COU are optional.
Example:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is ALL
In the MAPCONF command, when RETCODE_MODE is TRUE, SUCCESS0002 is mapped to
ERR3006. The default value of RETCODE_MODE is TRUE.
Example:
ERA CFB:IMSI="123454321234543";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is ALL.
Example:
MOD CFNRY:IMSI="123454321234543", PROV=TRUE, OFAID=2, NFS=TRUE,
NCS=TRUE, COU=OPERATOR;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, the parameters OFAID, NCS, NFS, and COU need not be
specified.
If the parameter PROV is set to TRUE, the parameters OFAID, NCS, NFS, and COU are optional.
Example:
REG CFNRY: IMSI="123454321234543",FTN="013645678901", PROPERTY=
INTERNATIONAL;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is ALL.
The default value of the parameter NOREPTIME is the no reply timer value set by the system by default.
In the MAPCONF command, when RETCODE_MODE is TRUE, SUCCESS0002 is mapped to
ERR3006. The default value of RETCODE_MODE is TRUE.
Example:
ERA CFNRY:IMSI="123454321234543";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD CFNRC:IMSI="123454321234543",PROV=TRUE,OFAID=2,NCS=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
REG CFNRC:IMSI="123454321234543", FTN="013645678901",
PROPERTY=NATIONAL;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
ERA CFNRC: IMSI="123454321234543";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
LST CFALL: IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
"CFU"
<"PROV"|"NOTPROV"|"REG"|"ACT"|"QUICENT">
{TPLID}=<OFA Template Id>
{NCS}=<"TRUE"|"FALSE">
{COU}=<"OPERATOR"|"SUBSCRIBER">
{FTN}=<Forward-To Number>
{BSG}=<"TS1X"|"TS6X"|"TSDX"|"BS2X"|"BS3X"|"ALL BS">
{STATUS}=<"PROV"|"NOTPROV"|"REG"|"ACT"|"QUICENT">
"CFB"
<"PROV"|"NOTPROV"|"REG"|"ACT"|"QUICENT">
{TPLID}=<OFA Template Id>
{NFS}=<"TRUE"|"FALSE">
{NCS}=<"TRUE"|"FALSE">
{COU}=<"OPERATOR"|"SUBSCRIBER">
{FTN}=<Forward-To Number>
{BSG}=<"TS1X"|"TS6X"|"TSDX"|"BS2X"|"BS3X"|"ALL BS">
{STATUS}=<"PROV"|"NOTPROV"|"REG"|"ACT"|"QUICENT">
"CFRC"
<"PROV"|"NOTPROV"|"REG"|"ACT"|"QUICENT">
"CFRY"
<"PROV"|"NOTPROV"|"REG"|"ACT"|"QUICENT">
{TPLID}=<OFA Template Id>
{NFS}=<"TRUE"|"FALSE">
{NCS}=<"TRUE"|"FALSE">
{COU}=<"OPERATOR"|"SUBSCRIBER">
{FTN}=<Forward-To Number>
{BSG}=<"TS1X"|"TS6X"|"TSDX"|"BS2X"|"BS3X"|"ALL BS">
{STATUS}=<"PROV"|"NOTPROV"|"REG"|"ACT"|"QUICENT">
{NotReplyTime}=<Not Reply Time>
"CFD"
<"PROV"|"NOTPROV"|"REG"|"ACT"|"QUICENT">
{NFS}=<"TRUE"|"FALSE">
{CFD_SHORTNUM}=<"TRUE"|"FALSE">
{NCS}=<"TRUE"|"FALSE">
{FTN}=<Forward-To Number>
{BSG}=<"TS1X"|"TS6X"|"TSDX"|"BS2X"|"BS3X">
{STATUS}=<"PROV"|"NOTPROV"|"REG"|"ACT"|"QUICENT">
{NotReplyTime}=<Not Reply Time>
... <List of attributes of CF for all Basic Service Group to which CF is provisioned>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
ACT CWAIT:IMSI="123454321234543",BSG=TS1X;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is ALL.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is ALL.
Example:
LST CWAIT: IMSI="444441234567890";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>,
{MSISDN}=<MSISDN Number>
CWAIT
{BSG}=<Basic Service Group1>
{CWAIT}=<"PROV"|"NOTPROV"|"ACT">
{BSG}=<Basic Service Group2>
{CWAIT}=<"PROV"|"NOTPROV"|"ACT">
{BSG}=<Basic Service Group3>
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD HOLD: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HOLD: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>,
{MSISDN}=<MSISDN number>
{HOLD}=<PROV|NOTPROV>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD MPTY: IMSI="444441234567890", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, this command is used to withdraw the Multi-party service for a
subscriber.
If the parameter PROV is set to TRUE, this command is used to provide the Multi-party service for a
subscriber.
Example:
LST MPTY: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{MSISDN}=<MSISDN Number>
{MPTY}=<PROV|NOTPROV>
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD AOCC:IMSI="444441234567890",PROV= TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, this command is used to withdraw the AOCC service for a
subscriber.
Example:
LST AOCC: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{MSISDN}=<MSISDN Number>
{AOCC}=<PROV|NOTPROV>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD AOCI: IMSI="444441234567890", PROV= TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, this command is used to withdraw the AOCI service for a
subscriber.
Example:
LST AOCI: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>
{MSISDN}=<MSISDN number>
{AOCI}=<"Provisioned"|"NotProvisioned">
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ECT: IMSI="444441234567890",PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, this command is used to withdraw the ECT service for a
subscriber.
If the parameter PROV is set to TRUE, this command is used to provide the ECT service for a subscriber.
Example:
LST ECT: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BAOC:IMSI="444441234567890",PROV= TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD BOIC: IMSI="444441234567890",PROV= TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, this command is used to withdraw the BOIC service for a
subscriber.
If the parameter PROV is set to TRUE, this command is used to provide the BOIC service for a subscriber.
Example:
MOD BOICEXHC:IMSI="444441234567890",PROV= TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, this command is used to withdraw the BOIC-exHC service for a
subscriber.
If the parameter PROV is set to TRUE, this command is used to provide the BOIC-exHC service for a
subscriber.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, this command is used to withdraw the BAIC service for a
subscriber.
If the parameter PROV is set to TRUE, this command is used to provide the BAIC service for a subscriber.
Example:
MOD BICROM:IMSI="444441234567890",PROV= TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
ACT BAOC: IMSI="444441234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
ACT BOIC: IMSI="444441234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is applicable to the basic service group
Example:
ACT BOICEXHC: IMSI="444441234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is applicable to the basic service group
Example:
ACT BAIC: IMSI="444441234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is applicable to the basic service group
Example:
ACT BICROM: IMSI="444441234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is applicable to the basic service group
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is applicable to the basic service group.
Example:
DEA BOIC: IMSI="444441234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is applicable to the basic service group.
Example:
DEA BOICEXHC: IMSI="444441234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
DEA BAIC: IMSI="444441234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
DEA BICROM: IMSI="444441234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST CBAR: IMSI="444441234567890",BSG=TS1X;
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>,
{MSISDN}=<MSISDN Number>
<CBCOU>=<"OPERATOR"|"SUBSCRIBER">
<CBCOUReason>=<"NotcaredReason"|"PasswordExceed">
<CBService>+<BSG>+<"PROV"|"NOTPROV"|"ACTIVE"|"QUICENT">
...
<CBService>+<BSG>+<"PROV"|"NOTPROV"|"ACTIVE"|"QUICENT">
CBService includes BAOC,BOIC,BOICEXHC,BAIC,BICROAM, BORO
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD BARPWD: IMSI="444440123456789",PWD="1234";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The new barring password is a decimal number of 4 digits or FFFF, this parameter is mandatory.
The new barring password is unavailable if PWD is set to FFFF.
Example:
MOD CBCOU: IMSI="444441234567890", COU=OPERATOR;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
LST SS: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= < MSISDN number>
{CLIP}=<"PROV"|"NOTPROV">
{CLIPOVERRIDE}=<"TRUE"|"FALSE">
{CLIR}=<"PROV"|"NOTPROV">
{CBCOU}=<"OPERATOR"|"SUBSCRIBER">
{AOCC}=<"PROV"|"NOTPROV">
{AOCI}=<"PROV"|"NOTPROV">
{UUS1}=<"PROV"|"NOTPROV">
{UUS2}=<"PROV"|"NOTPROV">
{UUS3}=<"PROV"|"NOTPROV">
{plmn-specificSS-1}=<"PROV"|"NOTPROV">
{plmn-specificSS-2}=<"PROV"|"NOTPROV">
{plmn-specificSS-3}=<"PROV"|"NOTPROV">
{plmn-specificSS-4}=<"PROV"|"NOTPROV">
{plmn-specificSS-5}=<"PROV"|"NOTPROV">
{CNAP}= <"PROV"|"NOTPROV">
{CNAPOVERRIDE}= <"PROV"|"NOTPROV">
{CCBS}= <"PROV"|"NOTPROV">
{CCBSTARGET}= <"PROV"|"NOTPROV">
{CD}= <"PROV"|"NOTPROV">
...<List of SS status for all mentioned BSG>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD VSRR: IMSI="984519856312345",PROV=TRUE,TPLTYPE=VLR,TPLID=123;
Or:
MOD VSRR: IMSI="984519856312345", PROV=FALSE,TPLTYPE=VLR;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter PROV is set to TRUE, the parameters TPLTYPE and TPLID need not be specified.
If the parameter PROV is set to FALSE, the parameter TPLID need not be specified. If TPLTYPE is not
specified, TPLID need not be specified.
Example:
LST VSRR: IMSI="984519856312345";
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter TPLTYPE is not specified when running this command, the values of both parameters
VLRTPLID and SGSNTPLID will be displayed in the output. Otherwise, only the values of either
parameter will be displayed.
Example:
MOD TPLGPRS: IMSI="984519856312345",PROV=TRUE,TPLID=123;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST GPRS: IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>
{MSISDN}=<MSISDN number>
{CHARGE_GLOBAL}=<NONE|HOT|FLAT|PREPAID|NORMAL|3|5|6|7|9||254>
{CNTXID}=<1>
{PDPTYPE}=<X25|PPP|OCSIHOSS|IPV4|IPV6>
{PDPADD}=<PDP Adddress like 10.64.12.11>
{ADDIND}=<STATIC|DYNAMIC>
{RELCLS}=<ACKALLPRODT|ACKLLCRLCPRODT|ACKRLCPRODT|
UACKALLPRODT|UACKALLUPRODT>
{DELAYCLS}=<DELAY1|DELAY2|DELAY3|DELAY4>
{PRECLS}=<HIGH|NORMAL|LOW>
{PEAKTHR}=<GPRS_PEAK_THROUGHPUT enumeration>
{MEANTHR}=<GPRS_MEAN_THROUGHPUT enumeration>
{ARPRIORITY}=<HIGHPRIORITY|NORMALPRIORITY|LOWPRIORITY>
{ERRSDU}=<NODETECT|YES|NO>
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD NAM: IMSI="984519856312345", NAM=BOTH;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST NAM: IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>,
{MSISDN}=<MSISDN number>,
{NAM}=<BOTH|MSC|SGSN|NONE>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD OCSI:ISDN="987654321",PROV=TRUE,TPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, the parameter TPLID need not be specified.
If the parameter PROV is set to TRUE, the parameter TPLID must be specified. If the data record of a
subscriber already has the O-CSI data, the O-CSI data will be modified when the command is executed.
Example:
MOD TCSI:ISDN="987654321",PROV=TRUE,TPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, the parameter TPLID need not be specified.
If the parameter PROV is set to TRUE, the parameter TPLID must be specified. If the data record of a
subscriber already has the T-CSI data, the T-CSI data will be modified when the command is executed.
Example:
MOD VTCSI:ISDN="987654321",PROV=TRUE,TPLID=2;
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, the parameter TPLID need not be specified.
If the parameter PROV is set to TRUE, the parameter TPLID must be specified. If the data record of a
subscriber already has the VT-CSI data, the VT-CSI data will be modified when the command is executed.
Example:
MOD UCSI:ISDN="987654321",PROV=TRUE,TPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD SSCSI:ISDN="987654321",PROV=TRUE,TPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD TIFCSI:ISDN="987654321",PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, the TIF-CSI flag for the specified subscriber is cleared.
If the parameter PROV is set to TRUE, the TIF-CSI flag for the specified subscriber is enabled.
Example:
MOD MCSI:ISDN="987654321",PROV=TRUE,TPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, the parameter TPLID need not be specified.
If the parameter PROV is set to TRUE, the parameter TPLID must be specified. If the data record of a
subscriber already has the M-CSI data, the M-CSI data will be modified when the command is executed.
Example:
MOD SMSCSI: ISDN="987654321", PROV=TRUE, MOMTSWITCH =MOSMSCSI,
TPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter PROV is set to FALSE, the parameters MOMTSWITCH and TPLID need not be specified.
If the parameter PROV is set to TRUE, the parameters MOMTSWITCH and TPLID must be specified. If
the data record of a subscriber already has the SMS-CSI data, the SMS-CSI data will be modified when the
command is executed.
Example:
MOD GPRSCSI:ISDN="987654321",PROV=TRUE,TPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter PROV is set to FALSE, the parameter TPLID need not be specified.
If the parameter PROV is set to TRUE, the parameter TPLID must be specified. If the data record of a
subscriber already has the GPRS-CSI data, the GPRS-CSI data will be modified when the command is
executed.
Example:
MOD DCSI:ISDN="987654321",PROV=TRUE,TPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST CSI:ISDN="987654321", CSITYPE=ALL;
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
{CSITYPE} = <CSI type>
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
The parameter CSITYPE is optional. If the parameter CSITYPE is not specified, the data of all the
subscribed CSI services will be displayed.
Example:
SND CANCELC: IMSI="984519856312345",VLRNO="123456789",CHECK=FALSE;
Response:
If the operation succeeds, the following success code is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If the parameter VLRNO or SGSNO is specified, the parameter CHECK must be specified.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter DEST is set to VLR, the parameter SGSNO cannot be specified.
If the parameter DEST is set to SGSN, the parameter VLRNO cannot be specified.
Example:
MOD SMDP: IMSI="444441234567890", SMDP=MSC;
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
The command is applied only to the subscriber whose NAM is BOTH.
Example:
LST SMDP: IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>
{ISDN}=<MSISDN number>
{ShortMessageParameter}=<"Sent via MSC when GMSC does not support GPRS"|"Sent via
SGSN when GMSC supports GPRS">;
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD LCS: IMSI="984519856312345",PROV=TRUE,TPLID=123;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed;
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter PROV is set to TRUE, the parameter TPLID must be specified; otherwise, the parameter
TPLID need not be specified..
Example:
LST LCS: IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CATEGORY: IMSI="984519856312345",CATEGORY=COMMON;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST CATEGORY: IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{MSISDN}=<MSISDN Number>
{CATEGORY}=<UNKNOWN|FRENCH|ENGLISH|GERMAN|RUSSIAN|SPANISH|
SPECIAL|RESERVE|COMMON|SUPERIOR|DATACALL|TESTCALL|SPARE|
PAYPHONE|COIN|"16"||"31"|"33"||"254">
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
DEFAULTC Enumeration See " TSCODE and The default basic O (with TS11
ALL DSCODE service call process as default
Enumeration" (including TSCODE& value)
DSCODE) for the
incoming call has not
included the call type.
TS String 40 Combination of O
teleservice enumeration
separated by '&'. The
enumeration definition
can be referred to the
supplementary
definition of TSCODE
BS String 160 Combination of bearer O
services enumeration
separated by '&'. The
enumeration definition
can be referred to the
supplementary
definition of BSCODE
CFU Boolean TRUE CFU Supplementary O
FALSE service
Example:
ADD SUB: HLRSN =2, IMSI="435670998956956", ISDN="9876534345",
CARDTYPE=USIM, TS=TS11&TS21;
Response:
If the operation succeeds, the following success code is displayed:
Example:
MOD CUGSUB: IMSI="123454321234543", PROV=TRUE, INTERLOCK="12345678",
INDEX=999, BSG= TS1X&BS2X, INTRACUG=NO_CUGBAR;
or
MOD CUGSUB: IMSI="1234567891234", PROV=FALSE, INTERLOCK="12345678";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, this command is used to withdraw the CUG service, and the
parameter INDEX, BSG and INTRACUG need not be specified.
If the parameter PROV is set to TRUE, this command is used to provide the CUG service or modify the
CUG service data. If this command is used to provide the CUG service, the parameters INDEX and BSG
are mandatory and INTRACUG is an optional. The default value of INTRACUG is NO_CUGBAR. If
this command is used to modify the CUG service data, at least one of the parameters INDEX, BSG and
INTRACUG must be specified.
A subscriber is allowed to subscribe to up to 10 interlock codes for the CUG service.
Example:
MOD CUGFTR: IMSI="123454321234543", PROV=TRUE, BSG=TS1X,
INTERCUG=ONLY_CUG, PRFCUGPROV=TRUE, PRFCUG=999;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST CUG: ISDN="955678112";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI Number>,
{ISDN}=<MSISDN Number>
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
MOD NAEA: IMSI="444441234567890", PROV= TRUE,NAEA=39;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST NAEA: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>,
{MSISDN}=<MSISDN Number>
{NAEA}=<"PROV"|"NOTPROV">
{NAEA_CIC}=<0-9999>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If the value of the parameter NAEA is in the range 0-9999, it indicates that the NAEA service is provided
and the actual NAEA value is displayed; if the parameter NAEA is set to FFFF, it indicates the NAEA
service is not provided and NOTPROV is displayed. The other values of the parameter NAEA are invalid.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
ADD KI: HLRSN =2, IMSI="111111111111111",
KIVALUE="12345678901234567890123456789012", K4SNO=12, CARDTYPE =USIM,
ALG=MILENAGE, OPCVALUE="FEDCAB123456789ABCDEF01234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
The default value of the parameter K4SNO is 0, which indicates that no K4 value will be used to decrypt
KI.
The parameters ALG and CARDTYPE must be specified together. The value of the parameter ALG
depends on that of the parameter CARDTYPE. Please pay attention to that the MILEANGE algorithm is
also applicable to the SIM card.
If the parameter ALG is set to MILENAGE, MILENAGE_2 or CUSTOM_1, the parameters OPC and
OPSNO are conditional parameters; that is, one of the two parameters must be specified. If the parameter
ALG is not set to MILENAGE, MILENAGE_2 and CUSTOM_1, the parameter OPC need not be
specified. If the parameter OPSNO is set to 0, it indicates that no OP data is used.
The parameter HLRSN need not be specified or is set to the default value 255 if the current PGW is a
common version. The parameter HLRSN must be specified if the current PGW is a redundant version. In
this case, this parameter does not have a default value.
The parameter AMFSNO is a conditionl parameter when CARDTYPE is USIM or ALG is MILENAGE,
MILENAGE_2 or CUSTOM_1.
The difference between MILENAGE_2 and MILENAGE is that different algorithms are used for
converting XRES of authentication quintuplets into SRES of authentication triplets.
Example:
LST KI: IMSI="123456789";
Response:
If the operation succeeds, the returned message is as follows:
{HLRSN}=< HLR Serial No in the redundant HLR center >,
{IMSI}=<IMSI Number>
{KIVALUE}=<KI Value>
{K4SNO}=<K4 Serial Number>
{CARDTYPE}=<SIM|USIM>
{ALG}=<Authentication Algorithm>;
{OPC}=<OPC value if it is applicable>
{OPSNO}={the serial number of OP for MEILEANGE algorithm}
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
No.
Example:
RMV KI: IMSI="123456789";
Response:
For successful execution of the command, result will be displayed in following format..
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
Example:
MOD CARDPARA: IMSI="111111111111111", K4SNO=12, CARDTYPE =USIM,
ALG=MILENAGE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
At least one of the parameters K4SNO, ALG, and CARDTYPE must be specified.
The parameters ALG and CARDTYPE must be specified together. The value of the parameter ALG
depends on that of the parameter CARDTYPE.
If the parameter ALG is set to MILENAGE, MILENAGE_2 or CUSTOM_1, the parameters OPC and
OPSNO are conditional parameters; that is, one of the two parameters must be specified. If the parameter
ALG is not set to MILENAGE, MILENAGE_2 or CUSTOM_1, the parameter OPC need not be
specified. If the parameter OPSNO is set to 0, it indicates that no OP data is used.
The difference between MILENAGE_2 and MILENAGE is that different algorithms are used for
converting XRES of authentication quintuplets into SRES of authentication triplets.
Example:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to TRUE, the parameters VALIDCCF, SUPINTERCFD, NFS, NCS, and
FTN are optional. If the parameter PROV is set to TRUE and the parameter FTN is specified, the
parameters BSG and NRTIME are optional. If the parameter PROV is set to TRUE and the parameter
FTN is not specified, the parameters BSG and NRTIME need not be specified.
If the parameter PROV is set to TRUE, this command is used to provide and register the CFD service.
If the parameter PROV is set to FLASE, the parameters SUPINTERCFD, NFS, NCS, FTN, and
NRTIME need not be specified and the parameters BSG and VALIDCCF are optional, but only one of the
parameters BSG and VALIDCCF can be specified.
If the parameter PROV is set to FLASE, this command is used to withdraw and erase the CFD service.
Example:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters ODBECT, ODBDECT, and ODBMECT are conditional parameters. Specify at least one of
them.
Example:
MOD BORO:IMSI="444441234567890",PROV= TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
ACT BORO: IMSI="444441234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
DEA BORO: IMSI="444441234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The default value of the parameter BSG is applicable to the basic service group
Example:
MOD GPRS: IMSI="123456789",
CHARGE_GLOBAL=PREPAID,PROV=TRUE,CNTXID=1,PDPTYPE=IPV4,PDPADD="1
0.64.12.11",ADDIND=STATIC,RELCLS=ACKALLPRODT,DELAYCLS=DELAY1,PRECL
S=HIGH,PEAKTHR=1,MEANTHR=1,APN="APN",VPLMN=TRUE,CHARGE=PREPAID;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD PLMNSS: IMSI="123454321234543", PROV=TRUE, PLMNSPECSS=PLMN-SS-1;
Or
MOD PLMNSS: IMSI="1234567891234", PROV=FALSE, PLMNSPECSS=PLMN-SS-
1&PLMN-SS-2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, this command is used to withdraw several PLMN specific-SS.
If the parameter PROV is set to TRUE, this command is used to provide several PLMN specific-SS.
Example:
MOD ALS: IMSI="984519856312345",PROV=TRUE,LINE2NUM="1234567890123";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The ALS service can not be provided to a GPRS subscriber.
If the parameter PROV is set to FALSE, this command is used to withdraw the ALS service.
If the parameter PROV is set to TRUE, this command is used to provide the ALS service.
Example:
LST ALS: IMSI="444441234567890";
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD VVDN: IMSI="444441234567890", PROV= TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST VVDN: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= < IMSI Number >,
{ISDN}=< MSISDN Number >,
<VVDN>=<"PROV"|"NOTPROV">
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
MOD RBT: IMSI="444441234567890",PROV= TRUE,RBT=6;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, this command is used to withdraw the RBT service.
If the parameter PROV is set to TRUE, this command is used to provide the RBT service.
Example:
LST RBT: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= < IMSI Number >,
{ISDN}=< MSISDN Number >,
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
MOD ODBPOS: IMSI="984519856312345", ODBPOS=BAPOS,
ODBPOSTYPE=NetworkInit;
Response:
If the operation succeeds, the following success code is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD EMLPP: IMSI="444441234567890",PROV=TRUE, EMLPP_MAX=priorityLevel0,
EMLPP_DEF=priorityLevel0;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST EMLPP: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= < IMSI Number >,
{ISDN}=< MSISDN Number >,
{EMLPP}=<"PROV"|"NOTPROV">
{EMLPP_MAX}=<priorityLevel0|priorityLevel1|priorityLevel2|priorityLevel3|
priorityLevel4>,
{EMLPP_DEF}=<priorityLevel0|priorityLevel1|priorityLevel2|priorityLevel3|
priorityLevel4>;
{EMLPP_COU}=<SUBSCRIBER| OPERATOR>;
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ECATEGORY: IMSI="444441234567890",PROV= TRUE, ECATEGORY =6;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter PROV is set to FALSE, this command is used to withdraw the ECATEGORY and the
ECATOPTION services.
If the parameter PROV is set to TRUE, this command is used to provide the ECATEGORY or the
ECATOPTION service.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ARD: IMSI="444441234567890", PROV=TRUE,UTRANNOTALLOWED=FALSE,
GERANNOTALLOWED=FALSE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter PROV is set to TRUE, the parameters UTRANNOTALLOWED and
GERANNOTALLOWED must be both specified or both unspecified.
Example:
LST ARD: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= < IMSI Number >,
{ISDN}=< MSISDN Number >,
{ARD}=<PROV|NOTPROV>
{UTRANNOTALLOWED}=<FALSE|TRUE>
{GERANNOTALLOWED}=<FALSE|TRUE>
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CARP: IMSI="444441234567890",PROV= TRUE, CARP =6;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST CARP: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= < IMSI Number >,
{ISDN}=< MSISDN Number >,
{CARP}=<1-255|"NOTPROV">
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD RSZI: IMSI="444441234567890", RROption= ONLY_HPLMN;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter RROption is set to RR_TEMPLATE, the parameter RRTPL is mandatory.
Example:
LST RSZI: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= < IMSI Number >,
{ISDN}=< MSISDN Number >,
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD BS: IMSI="444441234567890",BS20=TRUE, BS25=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Example:
MOD EIN: IMSI="460000009123456", OSKPROV=TRUE, OSK=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
Either of the parameters OSKPROV ,TSKPROV, BOSKPROV and EOICKPROV must be specified.
Example:
LST EIN: IMSI="460000009123456";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= < IMSI Number >
{ISDN}=< MSISDN Number >
OSK = <VALUE >
TSK= <VALUE >
BOSK = <VALUE >
EOICK = <VALUE >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD TPLVBS: IMSI="444441234567890",PROV=TRUE, TPLID=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameter TPLID is specified only when the parameter PROV is set to TRUE.
Example:
MOD VBS: IMSI="444441234567890", CAPINTVBSONROAMING = FALSE,
OPTYPE=DELETE, COUNT=1, GROUPID1="1";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter OPTYPE is set to MODIFY, the parameter COUNT must be set to 1 and the parameters
GROUPID and CAPINITVBS must be specified.
If the parameter OPTYPE is set to DELETE, the parameter COUNT must be set to 1 and the parameter
GROUPID must be specified.
Example:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD TPLVGCS: IMSI="444441234567890",PROV= TRUE, TPLID=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameter TPLID is specified only when the parameter PROV is set to TRUE.
Example:
MOD VGCS: IMSI="444441234567890", CAPINTVGCSONROAMING = FALSE,
OPTYPE=DELETE, COUNT=1, GROUPID1="1";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
This command is only applied to the subscriber whose NAM is BOTH or MSC.
If the parameter OPTYPE is set to DELETE, the parameter COUNT must be set to 1.
Example:
LST VGCS: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
{CAPINITVGCSONROAMING}=<CapInitVGCSOnRoaming>
{GROUPID1}=<VGCS GroupID1>
{GROUPID2}=<VGCS GroupID2>
{GROUPID50}=<VGCS GroupID50>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD RMPY: RMNUM="955589", PROV=TRUE, FUNCDESC="funcdesc",
CORSET=COR_2&COR_4&COR_20&COR_22, FFNADDRESS="8613911111";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If the parameter PROV is set to FALSE, the parameters FUNCDESC, CORSET, and FFNADDRESS
need not be specified.
A remote subscriber can add a maximum of 255 initial subscribers and 255 supervisors.
Example:
LST RMPY: RMNUM="955589";
Response:
If the operation succeeds, the format of the returned message is as follows:
{HLRSN}=< HLR Serial No in the redundant HLR center >
{RMNUM} = <specific remote party number>
{FUNCDest} = <Description for Remote party>
{CORSet}= {COR_x1 & COR_x2}
{FFN_Address } = < FFNs Address >
{InitiatingNumber}=< specific Initiating number which is registered to remote party>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD FM: IMSI="123456789", PROV=TRUE, TYPE=Initiating subscriber,
CORSET=COR_3&COR_5&COR_62&COR_164;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST FM: IMSI="123456789";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
{Type} =< Initiating subscriber | Supervisor >
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
SND FMNOTIFY: RMNUM="955589", INITNUM="861386559";
Response:
If the operation succeeds, the following success code is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD AUTHUSER: HLRSN=1, RMNUM="955589", PROV=TRUE, TYPE=Initiating
subscriber, INITNUM="861386559";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST AUTHUSER: RMNUM="955589", TYPE=Initiating subscriber;
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD FMREG: OPTION=Register, RMNUM="955589", INITNUM="861386559";
Response:
If the operation succeeds, the following success code is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD UUS: IMSI="460000009123456", PROV=TRUE, UUS=UUS2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CF:IMSI="123454321234543",CFUPROV=TRUE,OFAID=2,NFS=TRUE,
NCS=TRUE, COU=OPERATOR;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
At least one of the parameters CFUPROV, CFBPROV, CFNRYPROV, and CFNRCPROV must be
specified.
If the parameter CFBPROV or CFNRYPROV is set to TRUE, the parameters NCS, NFS, COU and
OFAID are optional. If the parameter CFUPROV is set to TRUE, the parameters NCS, COU and OFAID
are optional. If the parameter CFNRCPROV is set to TRUE, the parameters NCS, COU and OFAID are
optional.
If the parameters CFUPROV, CFBPROV, CFNRYPROV, and CFNRCPROV are set to FALSE, the
parameters NCS, NFS, COU, and OFAID need not be specified.
Example:
MOD TS: IMSI="444441234567890", TS11=TRUE, TS21=TRUE, TS61=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
At least one of the parameters TS11, TS21, TS22, TS61, and TS62 must be specified.
Example:
MOD ODB: IMSI="460013907550001", ODBSS=TRUE, ODBIC=NOBIC,
ODBOC=BAOC, ODBECT=NOBECT, ODBDECT=TRUE, ODBPOS=NOBPOS,
ODBPOSTYPE=BOTH;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
When providing the ODB-POS service for the subscriber, you must specify the parameters ODBPOS and
ODBPOSTYPE. When modifying the ODB-POS service, you must specify the parameter ODBPOS or
ODBPOSTYPE.
At least one type of the ODB services must be provided or withdrawn.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter CLIP is set to TRUE, the parameter CLIPOVERRIDE must be specified.
If the parameter COLP is set to TRUE, the parameter COLPOVERRIDE must be specified.
If the parameter CLIR is set to TRUE, the parameter CLIRMODE must be specified.
Example:
MOD OSS: IMSI="444441234567890",CWAIT=TRUE,ACTCWAIT=TS1X, HOLD=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
At least one of the parameters CWAIT, HOLD, MPTY, AOCC, AOCI, ECT, CCBS, CCBSTARGET
and ACTDEACWAIT must be specified.
If the parameter CWAIT is set to TRUE, the parameter ACTDEACWAIT is optional and can only be set
to ACT. If the parameter CWAIT is set to TRUE, the parameter ACTDEACWAIT need not be specified.
If the parameter CWAIT is not specified, the parameter ACTDEACWAIT is optional.
If the parameter ACTDEACWAIT is specified, the parameter ACTDEACWAITBSG must be specified. If
the parameter ACTDEACWAIT is not specified, the parameter ACTDEACWAITBSG need not be
specified.
Before providing the MPTY or ECT services for a subscriber, you must provide the HOLD service for the
subscriber first.
The parameters AOCC and AOCI are mutually exclusive. They cannot be set to TRUE at the same time.
Example:
LST OSS: IMSI="444441234567890", DETAIL =TRUE;
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
CWAIT
{BSG}=<Basic Service Group1>
{CWAIT}=<"PROV"|"NOTPROV"|"ACT">
{BSG}=<Basic Service Group2>
{CWAIT}=<"PROV"|"NOTPROV"|"ACT">
{BSG}=<Basic Service Group3>
{CWAIT}=<"PROV"|"NOTPROV"|"ACT">
{BSG}=<Basic Service Group4>
{CWAIT}=<"PROV"|"NOTPROV"|"ACT">
{BSG}=<Basic Service Group5>
{CWAIT}=<"PROV"|"NOTPROV"|"ACT">
{BSG}=<Basic Service Group6>.
{CWAIT}=<"PROV"|"NOTPROV"|"ACT">
{HOLD} = <"PROV"|"NOTPROV">
{MPTY} = <"PROV"|"NOTPROV">
{AOCC} = <"PROV"|"NOTPROV">
{AOCI}= <"PROV"|"NOTPROV">
{ECT}= <"PROV"|"NOTPROV">
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CB: IMSI="444441234567890",BAOC=TRUE, BOIC=TRUE, BOICEXHC=TRUE,
BORO=TRUE, BAIC=TRUE, BICROM=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
At least one of the parameters BAOC, BOIC, BOICEXHC, BORO, BAIC, and BICROM must be
specified.
Example:
MOD CAMEL: IMSI="444441234567890", OCSIPROV=TRUE, OCSITPLID = 1,
TCSIPROV=TRUE, TCSITPLID=1,VTCSIPROV=TRUE,
VTCSITPLID=1,UCSIPROV=TRUE, UCSITPLID=1, SSCSIPROV=TRUE,
SSCSITPLID=1, TIFCSIPROV=TRUE, MCSIPROV=TRUE, MCSITPLID=1,
SMSCSIPROV=TRUE ,SMSCSITPLID=1, GPRSCSIPROV=TRUE ,GPRSCSITPLID=1,
DCSIPROV=TRUE ,DCSITPLID=1, IMOCSIPROV =TRUE , IMOCSITPLID =1,
IMVTCSIPROV =TRUE , IMVTCSITPLID =1;
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
At least one type of the CAMEL services must be provided or withdrawn.
If a CSI service is provided for a subscriber, the corresponding template ID must be specified. If a CSI
service is withdrawn for a subscriber, the corresponding template ID need not be specified.
Example:
CHK CONSY: IMSI="111111111111111";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD SMSCF: IMSI="460000009123456", PROV=TRUE, OFAID=1;
MOD SMSCF:IMSI="460000009123456", PROV= FALSE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
The parameter OFAID is specified only when the parameter PROV is set to TRUE.
Example:
ACT SMSCF: IMSI="460000009123456", ACTIVE=TRUE, FTN="86139998898",
PROPERTY=INTERNATIONAL;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter ACTIVE is set to TRUE, the parameters FTN and PROPERTY are mandatory.
Example:
LST SMSCF: IMSI="460000009123456";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
{OFATPLID} = <OFA template ID>
{FTN} = <Forward to Number>
{STATUS} = <"PROV"|"NOTPROV"|"REG"|"ACT"|"QUICENT">
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD MC: IMSI="460000009123456", PROV=TRUE, NBRSB=3, NBRUSER=3;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter MC is set to FALSE, the parameters NBRSB and NBRUSER need not be specified.
The value of the parameter NBRSB is larger than or equal to that of NBRUSER.
Example:
LST MC: IMSI="460000009123456";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
{MC} = <NOTPROV|PROV >
{NBRSB} = < Maximum of MC attempts allowed >
{NBRUSER} = < User determined maximum MC attempts >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD IST: IMSI="465700000000000", PROV=TRUE, ISTTIMER=20, ISTRSP= EMPTY;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter PROV is set to TRUE, the parameters ISTTIMER and ISTRSP are mandatory for the
IST subscription and are optional for the IST modification.
If the parameter PROV is set to FALSE, ISTTIMER and ISTRSP cannot be specified together.
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
SND ISTCMD: IMSI="984519856312345",MSCNUM="123456789";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD DIC: IMSI="460111111111111", PROV=TRUE, DICLENGTH=DICR_0;
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter PROV is set to TRUE, the parameter DICLENGTH must be specified.
Example:
LST DIC: IMSI="460111111111111";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>,
{ISDN}=<MSISDN number>,
{Provide}=<TRUE|FALSE>
{ ACCLENGTH }=< 0~16|127 >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD MIMSI: IMSI="460111111111111", PROV=TRUE, OPTIONTYPE=ADD,
MIMSITYPE=MultiIMSI, IMSI2="460222222222222", CALL_INDEX2=3;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:The operation is successful.
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST MIMSI: IMSI="460111111111111";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD ROUTECATEGORY: IMSI="460000009123456", PROV=TRUE,
ROUTECATEGORY=4;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:The operation is successful.
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST ROUTECATEGORY: IMSI="460100008001001";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
{ROUTECATEGORY}=< 1 ~ 255 >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD EXEXROUTECATEGORY: IMSI="460000009123456", PROV=TRUE,
EXEXROUTECATEGORY =4;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:The operation is successful.
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST EXEXROUTECATEGORY: IMSI="460100008001001";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= < MSISDN number>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD MIMSIVM: IMSI="460000009123456", PROV=TRUE,
VOICENUMBER="86123456", VOICE_INDEX=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:The operation is successful.
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST MIMSIVM: IMSI="460100008001001";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number>
{VOICENUMBER1}=< Voice number 1>
{VOICE_INDEX}=< 1 | 2 >
{VOICENUMBER2}=< Voice number 2>
{VOICE_INDEX}=< 1 | 2 >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CR: IMSI="460100008001001", PROV=TRUE, CALLREDIRECT =23;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:The operation is successful.
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST CR: IMSI="460100008001001";
Response:
If the operation succeeds, the format of the returned message is as follows:
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD NRBT: IMSI="444441234567890",PROV= TRUE,NRBT=600;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST NRBT: IMSI="444441234567890";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= < IMSI Number >,
{ISDN}=< MSISDN Number >,
{NRBT}=<"PROV"|"NOTPROV">
{NRBTIndex}=< INAP INDEX for National Ring Back Tone service>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD OPTGPRS: IMSI="123456789012345", PROV=ADDPDPCNTX, CNTXID=1,
APNTPLID=3, QOSTPLID=3, PDPTYPE=IPV4,ADDIND=STATIC,
PDPADD="10.64.12.11", VPLMN=TRUE, CHARGE=HOT;
Response:
If the operation succeeds, one of the following success codes is displayed:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter APN_TYPE is set to PS_APN or BOTH, the parameter QOSTPLID is
mandatory..
If the parameter APN_TYPE is set to EPS_APN or BOTH, the parameter EPS_QOSTPLID is
mandatory.
If the parameter ADDIND is set to STATIC and the parameter PDPTYPE is set to IPV4, one of the
parameters PDPADD or PDPADDV4 should be present.and their values should be a IPV4 address.
If the parameter ADDIND is set to STATIC and the parameter PDPTYPE is set to IPV6, the
parameter PDPADD should be present and its value should be a IPv6 address. the parameter
PDPADDV4 should not be present.
If the parameter ADDIND is set to STATIC and the parameter PDPTYPE is set to IPV4IPV6, the
parameter PDPADD should be present and its value should be a IPv6 address.
If the parameter ADD2IND is set to STATIC and the parameter PDPTYPE is set to IPV4IPV6, the
parameter PDPADDIPv4 should be present and its value should be a IPv4 address.
If the parameter ADDIND is set to STATIC and the parameter PDPTYPE is set to IPv4_OR_IPv6,
one or both of the parameters PDPADD or PDPADDV4 should be present. the value of PDPADD
should be a IPv6 address and the value of PDPADDV4 should be a IPv4 address.
If the parameter ADDIND is set to STATIC and the parameter PDPTYPE is set to IPV4_OR_IPV6,
the parameter PDPADD should be present and its value should be a IPv6 address.
If the parameter ADD2IND is set to STATIC and the parameter PDPTYPE is set to IPV4_OR_IPV6,
the parameter PDPADDIPv4 should be present and its value should be a IPv4 address.
If the parameter ADDIND is set to DYNAMIC, the parameter PDPADD should not be present.
If the parameter ADD2IND is set to DYNAMIC, the parameter PDPADDV4 should not be present.
Only one of the CHARGE and STDCHARGE should be present.
Only one of the CHARGE_GLOBAL and SCHARGE_GLOBAL should be present.
Example:
LST OPTGPRS: IMSI="444441234567890";
Response:
If the operation fails, the error codes will be returned. For details on the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD TPLOPTGPRS: IMSI="460000009123456", PROV=TRUE, TPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD MNUG: IMSI="460000009012345", PROV=TRUE, GTYPE=EIMSI,
SIMSI="460000000912345";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST MNUG: IMSI="460000009123456";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= < IMSI number >
{LISDN}= < MSISDN number >
{GTYPE}=< EIMSI >
{ACTIVE}=< Active MSISDN number >
{SISDN}=< MSISDN number >
"Member Number" "TCR" "ID"
{MSISDN number} + { PCALL | NCALL} + {1~9}
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
The Member Number, TCR, and ID parameters are displayed in the command output only for Multi-
MSISDN Multi-Profile subscribers.
Example:
MOD CCBS: IMSI="460000009123456", CCBS=TRUE, CCBSTARGET=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST CCBS: IMSI="460000009012345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= < MSISDN number>
{CCBS}=< PROV| NOTPROV >
{CCBSTARGET}=< PROV| NOTPROV >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CSISTATE: IMSI="4600000000000", CSITYPE=MCSI, CSISTATE=TRUE;
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ACR: IMSI="444441234567890",PROV=TRUE;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST ACR: IMSI="444441234567890";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>
{ISDN}=<MSISDN number>
{STATUS}=<"PROV"|"NOTPROV"|"ACT">
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
DEA ACR: IMSI="444441234567890";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Parameter Description:
Example:
ADD IMSIRTSUB: IMSI="123456", HLRSN ="222";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
MOD IMSIRTSUB: IMSI="123456", HLRSN="222";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
LST IMSIRTSUB: IMSI="123456";
Response
If the operation succeeds, one of the following success codes is displayed:
{IMSI}=<IMSI Number>,
{HLRSN}=< HLR Serial No in the redundant HLR center >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
RMV IMSIRTSUB: IMSI="123456";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
RN String 1-10 RN M
MSCID String 1-15 MSCID C
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
RMV NPOTHERRPT: ISDN="86131075003002";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
MOD NPOTHERRPT: ISDN="86131075003003", RN="1113";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
{ ISDN }=< ISDN Number>,
{ RN }=< RN >,
{ MSCID }=< MSCID >
None.
Example:
ADD NPDONORSUB: IMSI="4601075003001",ISDN="86131075003001", RN="1112";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
RN String 1-10 RN C
MSCNU String 1-15 MSC number C
M
Example:
MOD NPDONORSUB: IMSI="460000009012345", RN="1113";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
RMV NPDONORSUB: ISDN="86138075003001";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST NPDONORSUB: IMSI="460000009012345";
Response
If the operation succeeds, one of the following success codes is displayed:
{ IMSI }=< IMSI Number>,
{ ISDN }=< ISDN Number>,
{ RN }=< RN >,
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
MOD SMSROUTE: IMSI="460000009123456", PROV=TRUE, TPLID=4;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST SMSROUTE: IMSI="460000009123456";
Response
If the operation succeeds, one of the following success codes is displayed:
{ IMSI }=< IMSI Number>,
{ ISDN }=< ISDN Number>,
{ TPLID }=< SMS-ROUTE template ID >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
ACT CFD: IMSI="460000009123456";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
SND UPL: ISDN="86131075003003";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
None.
Example:
MOD NSMSIN: IMSI="460000009123456", SMSINPROV=TRUE,
SCPADD="8613911111", SKEY=1, DP=MO, TAMM=TRUE, ACT= TRUE;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST NSMSIN: IMSI="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>
{ISDN}=<MSISDN number>
{ SCPADD}=< SCPADD >,
{ SKEY}=< 0~2147483647>
{ DP}=< "MO"|"MT"|"SR">
{ TAMM}=< TRUE|FALSE >
{ STATUS }=< NOTPROV|PROV|ACT >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD COMISDN: IMSI="460000009123456", PROV=TRUE,
COMISDN="460000001111111", OVERIDE=TRUE;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST COMISDN: IMSI="460000009012345";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>
{ISDN}=<MSISDN number>
{ COMISDN}=< COMISDN Number >,
{ OVERIDE}=< TRUE/FALSE >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST OWNISDN: ISDN="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
{ IMSI }=< IMSI Number>,
{ MSISDN }=< MSISDN Number>,
{ OWNISDN }=< OWNISDN Number >,
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD DEFAULTOFA: IMSI="460035589300001", DEFAULTOFA_ID=8;
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST DEFAULTOFA: IMSI="460035589300001";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>
{ISDN}=<MSISDN number>
{ DEFAULTOFA_ID}=< 0-65534 >,
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CPP: IMSI="460035589300001", PROV=TRUE;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST CPP: IMSI="460035589300001";
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
1.Provide the NIR service for the subscriber whose IMSI is 460000009123456 with NIR
index set to 22.
MOD NIR: IMSI="460000009123456", PROV=TRUE, NIR=22;
2.Withdraw the NIR service from the subscriber whose IMSI is 460000009123456.
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
Query whether the NIR service is provided for the subscriber whose IMSI is
460000009123456.
LST NIR: IMSI="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
{ IMSI }=< IMSI Number>,
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
ACT ISDN:
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD ELCS: IMSI="460035589300001", PROV=TRUE;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST ELCS: IMSI="460035589300001";
Response
If the operation succeeds, the format of the returned message is as follows:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD IMEIBIND: IMSI="123456789012345", OPTIONTYPE=PROVIDE,
IMEI="12345678901234";
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST IMEIBIND: IMSI="123456789123456";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{IMSIIMEIBIND}=<<NULL> | IMEI number >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If this command is executed for a subscriber whose M2M binding service is automatic binding and the
subscriber's IMSI is not bound with an IMEI, the result of IMSIIMEIBIND is NULL.
Example:
MOD M2MNOTIFY: IMSI="123456789012345", PROV=TRUE;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST M2MNOTIFY: IMSI="123456789123456";
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CA: IMSI="460000009012345", PROV=TRUE, CA1=1, CA2=2;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST CA: IMSI="460000009012345";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>
{ISDN}=<MSISDN number>
{CA1}= <1~9999>
{CA2}= <1~9999>
{CA3}= <1~9999>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The IMSI and MSISDN parameters are optional. Specify only one of them.
Example:
MOD FRAUD: IMSI="444441234567890",PROV= TRUE , TPLID=2;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
This command is only applied to the subscriber whose NAM is BOTH or MSC.
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST FRAUD: IMSI="460035589300001";
Response
If the operation succeeds, the format of the returned message is as follows:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CNAP:IMSI="345126789012345",PROV=FALSE;
MOD CNAP:IMSI="345126789012345",PROV=TRUE,OVERRIDE=FALSE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST CNAP: IMSI="345126789012345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= <MSISDN number>
{STATUS}= <PROV|NOTPROV>
{OVERRIDE}=<TRUE|FALSE>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IP4_HOA_SUPPORTED
ASSIGN_LOCAL_IP
MIP4_SUPPORTED
GTPv2_SUPPORTED
PROVTIMEOUT Boolean TRUE Provide O
FALSE Session
timeout
period
Example:
MOD NONSUB: IMSI="460000009012345", NON3GPPSUPP=FALSE;
MOD NONSUB: IMSI="460000009012345", NON3GPPSUPP=TRUE,
NONARD=WLANNOTALLOWED-1, PROVMIP6=TRUE,
MIP6FEAVEC=MIP6_INTEGRATED;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST NONSUB: IMSI="460000009012345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= <MSISDN number>
{NON3GPPSUPP}= <TRUE|FALSE>
{WLANNOTALLOWED}=<TRUE|FALSE>
{CDMA2000_1XNOTALLOWED}=<TRUE|FALSE>
{HRPDNOTALLOWED}=<TRUE|FALSE>
{UMBNOTALLOWED}=<TRUE|FALSE>
{EHRPDNOTALLOWED}=<TRUE|FALSE>
{MIP6FEAVEC}=<MIP6_INTEGRATED|PMIP6_SUPPORTED|IP4_HOA_SUPPORTED|
ASSIGN_LOCAL_IP | MIP4_SUPPORTED | GTPv2_SUPPORTED >
{SESSIONTIMEOUT}=<1-4294967295>
Example:
ADD CKI: HLRSN=1, IMSI="460000009123456", MSISDN="86131234567",
KIVALUE="1234567890ABCDEF1111111111111111", K4SNO=2, CARDTYPE=SIM,
ALG=COMP128_1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
RMV GPRS: IMSI=123456789;
Response:
If the operation succeeds, the format of the returned message is as follows:
SUCCESS0001: Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD GROUPSIM: GIMSI="460000000000000", GISDN ="861300000000000",
PROV=ADD, HLRSN=1, MSIMTYPE=Sequential, MEMBERISDN1="861311111111111",
If the parameter PROV is set to ADD, the parameters GIMSI GISDN HLRSN MSIMTYPE are
mandatory.
If the parameter PROV is set to RMV or MOD, the GIMSI and GISDN parameters are optional. Specify
only one of them.
The value of the SMS, VOICE, MMS, or LCS cannot be the same as that of the GISDN parameter.
Example:
LST GROUPSIM: GIMSI="460000000000000";
Response
If the operation succeeds, the format of the returned message is as follows:
{GIMSI}= <Group's IMSI number>
{GISDN}=<Group's MSISDN number >
{MSIMTYPE}=< sequential | parallel | parallel preferred >
{ USERTYPE }=< User Type >
{TONETYPE}=< basic tone | intelligent tone>
{CFSUP}=<TRUE|FALSE>
{STIME}=< no answer time for sequential alerting >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The GIMSI and GISDN parameters are optional. Specify only one of them.
Example:
MOD GROUPUSER: GIMSI="460000000000000", PROV= MOD,
MEMBERISDN="861300000000000", ORDER=2;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The GIMSI and GISDN parameters are optional. Specify only one of them.
Example:
MOD EPS: IMSI="460000009123456", PROV=TRUE, AMBRMAXUL=500000,
AMBRMAXDL=100000;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST EPS: IMSI="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}=<MSISDN number>
{ EPS}=< PROV| NOT PROV>
{ AMBRMAXUL}=< UE level MAX Upload Bandwidth >
{ AMBRMAXDL}=< UE level MAX Download Bandwidth >
{ANCHOR}=<TRUE|FALSE>
{VOLTETAG}=<TRUE|FALSE>
{ICSIND}=<TRUE|FALSE>
{MPS}=<TRUE|FALSE>
{TAUTIMER}={0~43200}
{LTEAUTOPROV}=
<TRUE|FALSE|AUTOTPLUSER|AUTOUSER_NN|AUTOTPLUSER_NN>
{RELAY_NODE}=<TRUE|FALSE>
{ RATFREQSELPRIID}=< RAT frequency selection priority ID >
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD LUCSI: IMSI="460000009123456", PROV=TRUE, TPLID=2;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST LUCSI: IMSI="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI number>
{ISDN}=<MSISDN number>
{TPLID}=< Template id>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ICSIND: IMSI="460000009012345", ICSIND=TRUE;
Response
If the operation succeeds, one of the following success codes is displayed:
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST ICSIND: IMSI="460000009012345";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= <MSISDN number>
{ICSIND}= < TRUE|FALSE>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
MOD ANCHOR: IMSI="460000009012345", ANCHOR=FALSE;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST ANCHOR: IMSI="460000009012345";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= <MSISDN number>
{ANCHOR}= <TRUE|FALSE>
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
MOD IMOCSI:ISDN="987654321",PROV=TRUE,TPLID=2;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
MOD IMVTCSI:ISDN="987654321",PROV=TRUE,TPLID=2;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Parameter Description:
Example:
RMV CHANGEDISDN: ISDN="8613772897878";
Response
If the operation succeeds, one of the following success codes is displayed:
Example:
MOD PLMNRSZI: IMSI="444441234567890", PROV = TRUE, PLMNTPLID =1;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST PLMNRSZI: IMSI="444441234567890";
Response
If the operation succeeds, the format of the returned message is as follows:
{PLMNTPLID}=< PLMN TemplateID >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD STNSR: IMSI="460000009123456", PROV =TRUE, STNSR =4601389162252;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI, MSISDN, Name of IMSI file, Name of MSISDN file, IMSI/STNSR file
name, and MSISDN/STNSR file name are optional. Specify only one of them.
If Number of subscribers is specified, IMSI or MSISDN must be specified, but Name of IMSI file or
Name of MSISDN file cannot be specified.
RECORDCOUNT does not need to be specified if the number of subscribers is 1.
IMSIFILE:
This parameter contains multiple inconsecutive IMSIs. Each IMSI occupies one line.
The file name extension is .txt. The file is uploaded to the specified location on the
FTP server using the File Manager provided by the PGW Web LMT.
Example:
Response
If the operation succeeds, the format of the returned message is as follows:
{STNSR}= < Session Transfer Number for SRVCC >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI, MSISDN, Name of IMSI file, Name of MSISDN file, IMSI/STNSR file
name, and MSISDN/STNSR file name are optional. Specify only one of them.
If Number of subscribers is specified, IMSI or MSISDN must be specified, but Name of IMSI file or
Name of MSISDN file cannot be specified.
RECORDCOUNT does not need to be specified if the number of subscribers is 1.
IMSIFILE:
This parameter contains multiple inconsecutive IMSIs. Each IMSI occupies one line.
The file name extension is .txt. The file is uploaded to the specified location on the FTP
server using the File Manager provided by the PGW Web LMT.
ISDNFILE:
This parameter contains multiple inconsecutive MSISDNs. Each MSISDN occupies one
line.
The file name extension is .txt. The file is uploaded to the specified location on the FTP
server using the File Manager provided by the PGW Web LMT.
Example:
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter PROV is set to TRUE, the parameter APNOI should be present.
Example:
LST EPSAPNOI: IMSI="444441234567890";
Response
If the operation succeeds, the format of the returned message is as follows:
{ APNOI }= <UE Level APN Operator Identifier Replacement >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD EPSAMBR: IMSI="460000009123456", AMBRMAXUL =10000, AMBRMAXDL
=10000;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST EPSAMBR: IMSI="444441234567890";
Response
If the operation succeeds, the format of the returned message is as follows:
{ AMBRMAXUL }= < UE Level Max Request Bandwidth of Upload >
{ AMBRMAXDL }= < UE Level Max Request Bandwidth of Download >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD RFPRID: IMSI="460000009123456", RATFREQSELPRIID =10;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST RFPRID: IMSI="444441234567890";
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD DIAMRRS: IMSI="460000009123456", PROV=TRUE, DIAMNODETPL_ID=20;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
If the parameter PROV is set to TRUE, the parameter DIAMNODETPL_ID should be present.
Example:
LST DIAMRRS: IMSI="444441234567890";
Response
If the operation succeeds, the format of the returned message is as follows:
{ DIAMNODETPLID }=< Diameter Roaming TemplateID >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD EGR: IMSI="460030000000001", PROV=TRUE, EGRHLRSN=4;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Example:
LST EGR: IMSI="460030000000003";
Response
If the operation succeeds, the format of the returned message is as follows:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD USERCATEGORY: IMSI="984519856312345",USERCATEGORY=M2M;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST USERCATEGORY: IMSI="984519856312345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{MSISDN}=<MSISDN Number>
{CATEGORY}=<NORMAL|M2M>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD MSIM: IMSI="460000009123456", PROV=TRUE, MSIMTYPE=ActiveByUSSD
Response:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST MSIM: IMSI="460000009123456";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= < MSISDN number>
{MSIMTYPE}=< ActiveByUPL| ActiveByUSSD>
{MTISDN}=< Active MSISDN number >
{ISDN2} = < MSISDN Number 2>
{ISDN3} = < MSISDN Number 3>
{ISDN4} = < MSISDN Number 4>
{ISDN5} = < MSISDN Number 5>
{ISDN6} = < MSISDN Number 6>
{ISDN7} = < MSISDN Number 7>
{ISDN8} = < MSISDN Number 8>
{ISDN9} = < MSISDN Number 9>
Member Number ACTIVE ORDERID
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
The IMSI , ISDN, MSIMTYPE, Member Number, ACTIVE, and ORDERID parameters are displayed
in the command output for enhanced multi-SIM subscribers.
The IMSI , ISDN, MSIMTYPE, MTISDN, and ISDN2~9 parameters are displayed in the command
output for multi-SIM subscribers.
Example:
MOD NTCSI: IMSI="460000009123456", CAMELTYPE=OCSI, PROV=ADD, CAMEL=PHASE1,
OCSIDP=COLLECTINFO, SK=1, GSMSCFADD="158600000", DEFCALL=continueCall,
VLR_NOTSUPPHASE1=AllowLocationUpdateWithMOCall, VLR_NOTSUPPHASE2=ReturnLPO-
CSI, VLR_NOTSUPPHASE3=ReturnLPO-CSI, VLR_NOTSUPPHASE4=ReturnLPO-CSI,
GMSC_NOTSUPPHASE1=AllowMTCall, GMSC_NOTSUPPHASE2=ReturnLP-CSI,
GMSC_NOTSUPPHASE3=ReturnLP-CSI, GMSC_NOTSUPPHASE4=ReturnLP-CSI;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST NTCSI: IMSI="460000009123456";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}= < MSISDN number>
OCSI DATA
{CAMEL}=<PHASE1| PHASE2| PHASE3| PHASE4>
{OCSIDP}=<COLLECTINFO| ROUTESELFAIL>
{SK} = <0-2147483647>
{GSMSCFADD} = <gsmSCF address>
{DEFAULTCALL} = <continueCall | releaseCall>
{VLR_NOTSUPPHASE1} = AllowLocationUpdateWithMOCall|
AllowLocationUpdateWithODBBAOC| DenyLocationUpdate>
OCSI DATA
CAMEL = PHASE3
OCSIDP = COLLECTINFO
SK = 1
GSMSCFADD = 11234
DEFAULTCALL = continueCall
VLR_NOTSUPPHASE1 = AllowLocationUpdateWithODBBAOC
VLR_NOTSUPPHASE2 = AllowLocationUpdateWithODBBAOC
VLR_NOTSUPPHASE3 = AllowLocationUpdateWithODBBAOC
VLR_NOTSUPPHASE4 = AllowLocationUpdateWithODBBAOC
GMSC_NOTSUPPHASE1 = ReturnBAIC
GMSC_NOTSUPPHASE2 = AllowMTCall
GMSC_NOTSUPPHASE3 = ReturnBAIC
GMSC_NOTSUPPHASE4 = ReturnLPT-CSI
TCSI DATA
CAMEL = PHASE3
TCSIDP = TAA
SK = 1
GSMSCFADD = 11234
DEFAULTCALL = continueCall
GMSC_NOTSUPPHASE1 = ReturnBAIC
GMSC_NOTSUPPHASE2 = ReturnLPT-CSI
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD PREMSMS: IMSI="460000009123456", ODBPREMSMS=TRUE,
ODBADULTSMS=TRUE;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST PREMSMS: IMSI="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}=<MSISDN number>
{ ODBPREMSMS}=< TRUE| FALSE>
{ ODBADULTSMS}=< TRUE | FALSE>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ZCLOCK: IMSI="460000009123456", ZCLOCKPROV=TRUE;
Response
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI and ISDN are optional. Specify only one of the them. They cannot be present together .
Parameter Description:
Example:
LST ZCLOCK: IMSI="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}=<MSISDN number>
{ZCLOCKPROV}=< TRUE| FALSE>
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
LST DYNZC: IMSI="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}=<MSISDN number>
{ ZC1}=< Zone Code>
{ ZC2}=< Zone Code>
{ ZC3}=< Zone Code>
{ ZC4}=< Zone Code>
{ ZC5}=< Zone Code>
{ ZC6}=< Zone Code>
{ ZC7}=< Zone Code>
{ ZC8}=< Zone Code>
{ ZC9}=< Zone Code>
{ ZC10}=< Zone Code>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
RESET BINDEDTAI: IMSI="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ALSSUPP: IMSI="460030000000001", PROV=TRUE, ALS_SUPP_TYPE=AOCC;
Response
If the operation succeeds, the format of the returned message is as follows:
RETCODE = 0 SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD ALSODB:IMSI="460000009123456",PROV=TRUE,ALS_ODB_TYPE="ODB-PB1";
Response
If the operation succeeds, the format of the returned message is as follows:
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD PSSER: IMSI="460000009012345", PROV=ADDPDPCNTX, CNTXID=2,
PSAPNQOSTPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Avoid specifying Number of subscribers together with Name of IMSI file or Name of MSISDN file.
Example:
MOD EPSSER: IMSI="460000009123456", PROV=ADDPDNCNTX, CNTXID=2,
EPSAPNQOSTPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST PSSER: IMSI="460000009123456", DETAIL=FALSE;
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}=<MSISDN number>
{ CNTXID}=< CNTXID >
{ APNQOSTPLID }=< APNQOSTPLID >
{ OTHERADDIND }=< OTHERADDIND >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST EPSSER: IMSI="460000009123456", DETAIL=FALSE;
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}=<MSISDN number>
{ CNTXID}=< CNTXID >
{ APNQOSTPLID }=< APNQOSTPLID >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD TPLPSSER: IMSI="460000009123456", TPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI/ISDN and FILE are optional. Specify either of them. They must not be present together.
Number of subscribers cannot be present with IMSI/ISDN and FILE together.
Example:
MOD TPLEPSSER: IMSI="460000009123456", RECORDCOUNT=4, TPLID=3;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI,MSISDN,Name of IMSI file,Name of MSISDN file are optional. Specify only one of them.
Avoid specifying Number of subscribers together with Name of IMSI file or Name of MSISDN file
This command can only be used by subscribers who modify the information of EPS.
Example:
ADD CSPSSUB: HLRSN=1, IMSI="460000009123456", ISDN="460000009012389",
NAM=BOTH, DEFAULTCALL=TS11, CHARGE_GLOBAL=5;
Response:
If the operation succeeds, the following success code is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD TPLEPS: IMSI="460000009123456", EPSUSERTPLID=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI, ISDN, IMSIFILE and ISDNFILE are optional. Specify only one of them.
Avoid specifying Number of subscribers together with Name of IMSI file or Name of MSISDN file.
Example:
RMV CSPSSUB: ISDN="13310911001";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Specify one of the following parameters: IMSI, MSISDN, Name of IMSI file, or Name of MSISDN file.
If you specify Number of subscribers, do not specify Name of IMSI file or Name of MSISDN file.
Similarly, if you specify Name of IMSI file or Name of MSISDN file, do not specify Number of
subscribers.
To run RMV CSPSSUB to delete a CsPs subscriber, the CsPs subscriber must have not subscribed to the
EPS services.
Example:
LST CCGLOBAL: IMSI="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}=<MSISDN number>
{ CHARGE_GLOBAL }=< CHARGE_GLOBAL >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI, ISDN, IMSIFILE, and ISDNFILE are optional. Specify only one of them.
Avoid specifying Number of subscribers together with Name of IMSI file or Name of MSISDN file.
Example:
MOD CCGLOBAL: IMSI="460000009123456", CHARGE_GLOBAL=NORMAL;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI, ISDN, IMSIFILE and ISDNFILE are optional. Specify only one of them.
Avoid specifying Number of subscribers together with Name of IMSI file or Name of MSISDN file.
IMSI/ISDNFILE are optional. Specify either of them. They must not be present together.
Avoid specifying Number of subscribers together with Name of IMSI file or Name of MSISDN file
Name of IMSI/MSISDN file specifies the batch operation file that contains inconsecutive IMSIs and their
associated MSISDNs. The file is used for adding a batch of subscribers.
Example:
ADD TPLUSCSUB: HLRSN=1, IMSI="460000009123456", ISDN="8613484929766",
TPLID=2, SUBID="subinfo", IMPI="impiinfo",
IMPULIST="\"sip:impuinfo_1@huawei.com\"&\"sip:impuinfo_2@huawei.com\"", IRSID=1,
ALIASID=1;
Response
If the operation succeeds, the format of the returned message is as follows:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Parameter Description:
Example:
RMV USCSUB: IMSI="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD CAPL: IMSI="460000009123456", CAPLPROV=TRUE, CAPL=2;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST CAPL: IMSI="460000009123456";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= < IMSI Number >
{ISDN}=< MSISDN Number >
CAPL = <VALUE >
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The parameters IMSI and ISDN are mutually exclusive. Specify only one of them.
Example:
MOD EMMIN: IMSI="1234567", PROV=ADD, DP=12, SCPADDR="1111", SK=12;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Specify one of the following parameters: IMSI, MSISDN, Name of IMSI file, and Name of MSISDN file.
If you specify Number of subscribers, do not specify Name of IMSI file or Name of MSISDN file.
Similarly, if you specify Name of IMSI file or Name of MSISDN file, do not specify Number of
subscribers.
Example:
LST EMMIN: IMSI="1234567";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= < IMSI Number >
{ISDN}=< MSISDN Number >
{CAPL} = <1~15 >
{DP} = <0~255>
{SK} = <0~2147483647>
{SCPADDR} = <SCP Address>
{ACTIVE} = < TRUE| FALSE>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Specify one of the following parameters: IMSI, MSISDN, Name of IMSI file, and Name of MSISDN file.
If you specify Number of subscribers, do not specify Name of IMSI file or Name of MSISDN file.
Similarly, if you specify Name of IMSI file or Name of MSISDN file, do not specify Number of
subscribers.
Example:
MOD IMSIISDN: IMSI="2013521", ISDN="2014521", PROV=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
SUCCESS0002:Already existed, not changed
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMSI = 45000000
ISDN = 2014521
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Specify one of the following parameters: IMSI, MSISDN, Name of IMSI file, or Name of MSISDN file.
If you specify Number of subscribers, do not specify Name of IMSI file or Name of MSISDN file.
Similarly, if you specify Name of IMSI file or Name of MSISDN file, do not specify Number of
subscribers.
Specify one of the following parameters: IMSI, MSISDN, Name of IMSI file, or Name of MSISDN file.
If you specify Number of subscribers, do not specify Name of IMSI file or Name of MSISDN file.
Similarly, if you specify Name of IMSI file or Name of MSISDN file, do not specify Number of
subscribers.
RECORDCOUNT specifies the number of subscribers to be provided with the VoLTE flag at a time.The
parameter value is the total number of consecutive subscriber numbers starting from the specified IMSI or
MSISDN.
Specify this parameter only when you want to configure the VoLTE subscriber flag for
multiple subscribers with consecutive IMSIs or MSISDNs.
IMSIFILE specifies the name of an IMSI file to be used to configure the VoLTE subscriber flag for multiple
subscribers with non-consecutive IMSIs.An IMSI file contains multiple non-consecutive IMSIs. It is in
ANSI format, for example, lstisdn.txt. You can use the file manager function of the PGW Web LMT to
upload an IMSI file to a specified directory. For details about the file content, see IMSI file content.
ISDNFILE specifies the name of an MSISDN file to be used to configure the VoLTE subscriber flag for
multiple subscribers with non-consecutive MSISDNs.An MSISDN file contains multiple non-consecutive
MSISDNs. It is in ANSI format, for example, lstisdn.txt. You can use the file manager function of the PGW
Web LMT to upload an MSISDN file to a specified directory. For details about the MSISDN file content,
see MSISDN file content.
Example:
LST VOLTETAG: IMSI="46000000012345";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{MAINIMSI}=<Main IMSI number>
{ISDN}=<MSISDN number>
{MAINISDN}=<Main MSISDN number>
{VOLTETAG}=<NOT_DEFINED | TRUE | FALSE>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Specify one of the following parameters: IMSI, MSISDN, Name of IMSI file, or Name of MSISDN file.
If you specify Number of subscribers, do not specify Name of IMSI file or Name of MSISDN file.
Similarly, if you specify Name of IMSI file or Name of MSISDN file, do not specify Number of
subscribers.
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST PSAPNOI: IMSI="460000009123456";
Response
If the operation succeeds, the format of the returned message is as follows:
{IMSI}= <IMSI number>
{ISDN}=<MSISDN number>
{PSAPNOITPLID}=< 0~65534>
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Add a KI
Command Name: ADD HKI
Function: This command is used to add a KI data record to the HSS service database. The KI
is a parameter used for AKA authentication.
Parameter Description:
Example:
ADD HKI: IMPI="impiinfo", K="1234567890abcdef1234567890ABCDEF", K4SNO=1,
OPSNO=1, AMFSNO=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Ki and OPC are important parameters used for authentication. You are advised to encrypt the KI and OPC.
If the KI and OPC have been encrypted, run ADD HKI and specify the encryption parameters.
If you enter the command in the command input pane and then specify the related parameters, the KI value
and OPC value are displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the KI value
and OPC value are displayed in plain text.
Remove a KI
Command Name: RMV HKI
Example:
RMV HKI: IMPI="impiinfo";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Modify a KI
Command Name: MOD HKI
Function: This command is used to modify the KI value of the specified KI data record in the
HSS service database. The IMPI is the key parameter used to determine the KI data record to
be modified.
Parameter Description:
Example:
MOD HKI: IMPI="impiinfo", K="abcdef1234567890ABCDEF1234567890", K4SNO=1,
OPSNO=0, AMFSNO=1, OPC="ABCDef1234567890ABCDef1234567890",
OPCK4SNO=1;
Parameters K, K4SNO, OPSNO, and AMFSNO are optional, and you must specify one of them at least.
If you enter the command in the command input pane and then specify the related parameters, the KI value
and OPC value are displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the KI value
and OPC value are displayed in plain text.
List KIs
Command Name: LST HKI
Function: This command is used to query the information of a KI data record in the HSS
service database. The system supports the query of one KI data record at a time. The IMPI is
the key parameter used to determine the KI data record to be queried.
Parameter Description:
Example:
LST HKI: IMPI="impiinfo";
Response:
Success output: Horizontal format
Output:
Parameter description:
K: KI Value
K4SNO: K4 Serial Number
AMFSNO: AMF Serial Number
OPSNO: The Serial Number of OP for MEILEANGE Algorithm
OPCK4SNO: OPC K4 Serial Number
OPC: OPC value if it is applicable
None.
Example:
CHK HKI: IMPI="impiinfo", K="1234567890abcdef1234567890ABCDEF";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0005: Data to be verified is the same as that in the database
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If you enter the command in the command input pane and then specify the related parameters, the KI value
is displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the KI value is
displayed in plain text.
Example:
CHK HOPC: IMPI="impiinfo", OPC="1234567890abcdef1234567890abcdef";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0005: Data to be verified is the same as that in the database
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If you enter the command in the command input pane and then specify the related parameters, the OPC K4
value and OPC value are displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the OPC K4
value and OPC value are displayed in plain text.
Example:
1. ADD HHDAINF: IMPI="impiinfo", HUSERNAME="impiinfo", PWD="pwd";
2. ADD HHDAINF: IMPI="impiinfo", HA1="11112222333344445555666677778888";
The number of IMPIs that are authenticated by the HSS using the HTTP Digest authentication scheme is
specified by the license control item Number of IMPIs adopting the HDA authentication.
Only one HTTP digest authentication data record is allowed for an IMPI.
Do not specify User name and password together withHA1 value for an IMPI.
If you enter the command in the command input pane and then specify the related parameters, the Password
and HA1 value are displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the Password
and HA1 value are displayed in plain text.
To improve the system security, you are advised to set the password by following at least three of the rules
below:
The password must contain upper-case letter.
The password must contain lower-case letter.
The password must contain digits.
The password must contain special characters:`~!@#$%^&*()-_=+\|[{}];:'",<.>/? .
And notice three of the rules below:
Avoid using three or more than three consecutive letters or digits, for example, ABC or
123.
Avoid using account or the account in reverse order as the password.
Avoid using three or more than three same characters, for example, AAA.
Example:
RMV HHDAINF: IMPI="impiinfo";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the specified IMPI supports only HTTP Digest authentication and the IMPI is not used, this command
removes the IMPI.
If the specified IMPI supports other authentication mechanism in addition to HTTP Digest authentication,
this command removes only the HTTP Digest authentication information of the IMPI.
Example:
1. MOD HHDAINF: IMPI="impiinfo", HUSERNAME="impiinfo", PWD="pwd";
2. MOD HHDAINF: IMPI="impiinfo", HA1="11112222333344445555666677778888";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HHDAINF: IMPI="impiinfo";
Response:
Success output: Horizontal format
Output:
Parameter description:
IMPI: IMPI Number
HUSERNAME: User Name
PWD: Password
HA1: HA1 Value
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
CHK HHDAPWD: HUSERNAME="impiinfo", PWD="pwd";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0005: Data to be verified is the same as that in the database
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If you enter the command in the command input pane and then specify the related parameters, the Password
is displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the Password
is displayed in plain text.
To improve the system security, you are advised to set the password by following at least three of the rules
below:
The password must contain upper-case letter.
The password must contain lower-case letter.
The password must contain digits.
The password must contain special characters:`~!@#$%^&*()-_=+\|[{}];:'",<.>/? .
And notice three of the rules below:
Avoid using three or more than three consecutive letters or digits, for example, ABC or
123.
Avoid using account or the account in reverse order as the password.
Avoid using three or more than three same characters, for example, AAA.
Example:
1. ADD HSDAINF: IMPI="impiinfo", HUSERNAME="impiinfo", PWD="pwd",
REALM="huawei.com";
2. ADD HSDAINF: IMPI="IMPIINFOMATION", REALM="huawei.com",
HA1="11112222333344445555666677778888";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
For an IMPI, either only HA1 value or both User name and Password must be specified.
Each IMPI can be configured with only one SIP Digest authentication data record.
The number of IMPIs that are authenticated by the HSS using the SIP Digest authentication scheme is
specified by the license control item Number of HDA IMPIs.
If you enter the command in the command input pane and then specify the related parameters, the Password
and HA1 value are displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the
Password and HA1 value are displayed in plain text.
To improve the system security, you are advised to set the password by following at least three of the rules
below:
The password must contain upper-case letter.
The password must contain lower-case letter.
The password must contain digits.
The password must contain special characters:`~!@#$%^&*()-_=+\|[{}];:'",<.>/? .
And notice three of the rules below:
Example:
RMV HSDAINF: IMPI="impiinfo";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If the IMPI supports only the SIP Digest authentication scheme and the IMPI is not used associated with
any subscription data record, RMV HSDAINF is used to remove the IMPI data record.
If the IMPI supports other authentication schemes in addition to the SIP Digest authentication scheme,
RMV HSDAINF is used to remove only the SIP Digest authentication data record for the IMPI.
Example:
MOD HSDAINF: IMPI="impiinfo", HUSERNAME="impiinfo", PWD="pwd",
REALM="huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
At least one of the parameters User name, Password, HA1 value, and Realm must be specified.
For an IMPI, either only HA1 value or both User name and Password must be specified.
If you enter the command in the command input pane and then specify the related parameters, the Password
and HA1 value are displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the Password
and HA1 value are displayed in plain text.
To improve the system security, you are advised to set the password by following at least three of the rules
below:
The password must contain upper-case letter.
The password must contain lower-case letter.
The password must contain digits.
The password must contain special characters:`~!@#$%^&*()-_=+\|[{}];:'",<.>/? .
And notice three of the rules below:
Avoid using three or more than three consecutive letters or digits, for example, ABC or
123.
Avoid using account or the account in reverse order as the password.
Avoid using three or more than three same characters, for example, AAA.
Example:
1. LST HSDAINF: IMPI="impiinfo";
2. LST HSDAINF: HUSERNAME="impiinfo";
Response:
Success output: Horizontal format
Output:
Parameter description:
IMPI: IMPI Number
HUSERNAME: User Name
PWD: Password
REALM: Realm
HA1: HA1 Value
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
CHK HSDAPWD: HUSERNAME="impiinfo", PWD="pwd";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0005: Data to be verified is the same as that in the database
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If you enter the command in the command input pane and then specify the related parameters, the Password
is displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the Password
is displayed in plain text.
To improve the system security, you are advised to set the password by following at least three of the rules
below:
The password must contain upper-case letter.
The password must contain lower-case letter.
The password must contain digits.
The password must contain special characters:`~!@#$%^&*()-_=+\|[{}];:'",<.>/? .
And notice three of the rules below:
Avoid using three or more than three consecutive letters or digits, for example, ABC or
123.
Avoid using account or the account in reverse order as the password.
Avoid using three or more than three same characters, for example, AAA.
Example:
SET HEIA: IMPI="impiinfo", EIAFLAG=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None..
Example:
LST HEIA:IMPI="impiinfo";
Response:
Success output: Horizontal format
Parameter description:
IMPI: IMPI Number
IMSI: IMSI Number
IPV4ADDR: IPV4 Address
IPV6ADDR: IPV6 Address
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
SET HEAA: IMPI="impiinfo", EAAFLAG=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HEAA: IMPI="impiinfo";
Response:
Success output: Horizontal format
Output:
IMPI IMSI
Parameter description:
IMPI: IMPI Number
IMSI: IMSI Number
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
ADD HNBAINF: IMPI="impiinfo", LINEIDIDX=1, LINEID="huawei";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
RMV HNBAINF: IMPI="impiinfo";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HNBAINF: IMPI="impiinfo";
Response:
Success output: Horizontal format
Output:
LINEIDIDX LINEID
Parameter description:
LINEIDIDX: Line ID Index
LINEID: Line ID
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
SET HTAA: IMPI="impiinfo", TAAFLAG=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If an IMPI is defined and supports only the TAA authentication scheme, you cannot cancel the TAA
authentication scheme of the IMPI. Otherwise, the HSS displays that the operation has failed.
Example:
LST HTAA: IMPI="impiinfo";
Response:
Success output: Horizontal format
Output:
Parameter description:
TAAFLAG: 1 | 0
Remark: 1 represents TRUE, 0 represents FALSE
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
SET HCAA: IMPI="460001234567890@huawei.com", CAVEAKAFLG=TRUE,
UIMID="12345678";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HCAA: IMPI="460001234567890@huawei.com";
Response:
Success output: Horizontal format
Output:
Parameter description:
IMPI: IMPI Number
CAVEAKAFLG: 1 | 0
Remark: 1 represents TRUE, 0 represents FALSE
UIMID: UIMID
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HAUTHINF: IMPI="impiinfo";
Response:
Success output: Horizontal format
Output:
Parameter description:
AKAFLAG: 1 | 0
EAAFLAG: 1 | 0
SDAFLAG: 1 | 0
TAAFLAG: 1 | 0
EIAFLAG: 1 | 0
HDAFLAG: 1 | 0
NBAFLAG: 1 | 0
CAVEAKAFLAG: 1 | 0
Remark: 1 represents TRUE, 0 represents FALSE
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
CHK HHA1: IMPI="impiinfo", HA1="11112222333344445555666677778888";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0005: Data to be verified is the same as that in the database
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If you enter the command in the command input pane and then specify the related parameters, the HA1
value is displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the HA1 value
is displayed in plain text.
Parameter Description:
Example:
1. ADD HSUB: SUBID="subinfo", IMPI="impiinfo", IMPU="sip:impuinfo@huawei.com",
PBXUSERFLAG=FALSE;
2. ADD HSUB: SUBID="subinfo", IMPI="impiinfo", IMPU="tel:+33145297![247].*!",
IMPUTYPE=WIMPU, PBXUSERFLAG=FALSE, SYSNO=10;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMPI is mandatory if the ADD HSUB command is used to define an IMS subscription data record and add
an IMPU for the record.
Example:
1. ADD HHSSSUB: SUBID="subinfo", IMPI="impiinfo",
IMPULIST="\"sip:impuinfo_1@huawei.com\"&\"sip:impuinfo_2@huawei.com\"",
HUSERNAME="hss_user", PWD="pwd", IRSID=1, ALIASID=1;
2. ADD HHSSSUB: SUBID="subinfo", IMPI="impiinfo",
IMPULIST="\"sip:impuinfo_1@huawei.com\"&\"sip:impuinfo_2@huawei.com\"",
HUSERNAME="hss_user", PWD="pwd", REALM="huawei.com", CHARGTPLID=10,
IMPUTPLID=11, IRSID=1, ALIASID=1, SYSNO=10;
3. ADD HHSSSUB: SUBID="subinfo", IMPI="impiinfo", IMPIAUTHTYPE=EAA,
IMSI="460001234567890", ISDN="8613988888888", IMPI2="impiinfo2",
IMPI2AUTHTYPE=TAA, IMPULIST="\"sip:+8613988888888@huawei.com\"&\"tel:
+8613988888888\"&\"sip:impuinfo_1@huawei.com\"&\"sip:impuinfo_2@huawei.com\"",
BARIMPULIST="\"sip:impuinfo_1@huawei.com\"&\"sip:impuinfo_2@huawei.com\"",
CHARGTPLID=0, SPTPLID=1, IMPUTPLID=1, IRSID=1, ALIASID=1,
CONSFLG=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
To improve the system security, you are advised to set the password by following at least three of the rules
below:
The password must contain upper-case letter.
The password must contain lower-case letter.
The password must contain digits.
The password must contain special characters:`~!@#$%^&*()-_=+\|[{}];:'",<.>/? .
And notice three of the rules below:
Avoid using three or more than three consecutive letters or digits, for example, ABC or
123.
Avoid using account or the account in reverse order as the password.
Avoid using three or more than three same characters, for example, AAA.
HUSERNAME:
This parameter is optional when Authentication type of IMPI is HDA or SDA.
This parameter is mandatory when Authentication type of IMPI is not specified. It must be
specified in the MML command line input pane.
PWD:
This parameter is optional when Authentication type of IMPI is HDA or SDA.
This parameter is mandatory when Authentication type of IMPI is not specified. It must be
specified in the MML command line input pane.
To improve the system security, you are advised to set the password according to the rules
described in the Note.
REALM:
This parameter is mandatory when Authentication type of IMPI is SDA.
This parameter is optional when Authentication type of IMPI is not specified. To configure
the HTTP Digest authentication scheme for the IMPI, do not specify Realm. To configure
the SIP Digest authentication scheme for the IMPI, specify Realm in the MML command
line input pane.
This parameter can be set to a string of 32 to 46 characters only when the domain name
suffix is .3gppnetwork.org. If the domain name suffix is in the other format, this parameter
can be only set to a string of a maximum of 31 characters. Because the domain name suffix
3gppnetwork.org is case insensitive, it will be displayed in lowercase letters. For example,
if you set REALM to SOFT300.IMS.mnc001.mcc001.3gPPNETwork.org, the domain
name suffix of the realm is displayed as
SOFT300.IMS.mnc001.mcc001.3gppnetwork.org.
HA1 is optional when Authentication type of IMPI is HDA or SDA.
IMSI is mandatory when Authentication type of IMPI is EAA.
ISDN is optional when Authentication type of IMPI is EAA.
IMPI2:
The IMPI must be in the NAI format and case-sensitive.
Example:
1. RMV HHSSSUB: SUBID="subinfo";
2. RMV HHSSSUB: IMSI="460001234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
RMV HSUB: SUBID="subinfo";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Removing an IMS subscription data record may affect the services provided for the subscriber specified by
the subscription data record. Therefore, make sure this operation serves the intended purpose before
removing an IMS subscription data record.
None.
Example:
LST HSUB: SUBID="subinfo";
Response:
Success output: Horizontal format
Output:
Parameter description:
SUBID: Subscription ID
IMPI: IMPI Number
IMPU: IMPU Number
SHARED: 1 | 0 Remark: 1 represents TRUE, 0 represents FALSE
Example:
LST HSUBDATA: SUBID="subinfo";
Response:
Success output: Horizontal format
Output:
SUBDATA
Parameter description:
SUBDATA: Subscription Data
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
SET HPBXU: SUBID="subinfo", PBXUSERFLAG=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
SUBID PBXUSERFLAG
Parameter description:
SUBID: Subscription ID
PBXUSERFLAG: 1 | 0
Remark: 1 represents TRUE, 0 represents FALSE
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
SET HSUBINFO: SUBID="6290000001", SUBINFO="subinformation";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HSUBINFO: SUBID="6290000001";
Response:
Success output: Horizontal format
Output:
SUBID SUBINFO
Parameter description:
SUBID: Subscription ID
SUBINFO: Subscriber Description
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
SET HCONSFLG: SUBID="subinfo", CONSFLG=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
LST HCONSFLG: SUBID="subinfo";
Response:
Success output: Horizontal format
Output:
SUBID CONSFLG
Parameter description:
SUBID: Subscription ID
CONSFLG: 1 | 0
Remark: 1 represents TRUE, 0 represents FALSE
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
ADD IMSSUB: HLRSN=1, IMSI="123456789", IMPI="impiinfo_1",
IMPULIST="\"sip:impuinf_2@huawei.com\"&\"sip:impuinf_3@huawei.com\"";
SIFCLIST specifies the IDs of the shared iFC templates to be associated with the subscriber. The list
contains 1 to 8 unique shared iFC template IDs, each of which is separated by an ampersand (&). Shared
iFC templates can be added by ADD HSIFCTPL.
Example:
LST IMSSUB: IMSI="123456789";
Response:
If the operation succeeds, the format of the returned message is as follows:
{IMSI}=<IMSI Number>
{ISDN}=<MSISDN Number >
{IMPI}=<IMPI Number>
{IMPU}=<IMPU Number>
{IRSID}=<IRS ID>
{ALIASID}=<Alias Group ID>
{DEFIMPU}=<1 | 0>
Remark: 1 represents TRUE, 0 represents FALSE
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Add an IMPI
Command Name: ADD HIMPI
Function: This command is ADD HIMPI is used when you need to:
Parameter Description:
Example:
1. ADD HIMPI: SUBID="subinfo", IMPI="impiinfo", IMPU="sip:impuinfo@huawei.com";
2. ADD HIMPI: SUBID="subinfo", IMPI="impiinfo", IMPU="tel:+33145297![247].*!",
IMPUTYPE=WIMPU;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Remove an IMPI
Command Name: RMV HIMPI
Function: This command is used to remove an IMPI from the HSS service database.
Parameter Description:
Example:
None.
Modify an IMPI
Command Name: MOD HIMPI
Function: This command is used to modify an IMPI in the HSS service database. The IMPI is
the key parameter used to determine the IMPI record to be modified.
Parameter Description:
Example:
MOD HIMPI: IMPI="impiinfo", NEWIMPI="new_impiinfo";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
1. MOD HHSSIMPI: IMPI="impiinfo", NEWIMPI="new_impiinfo",
NEWIMPIAUTHTYPE=SDA, HUSERNAME="hss_user", PWD="pwd",
REALM="huawei.com";
2. MOD HHSSIMPI: IMPI="impiinfo", NEWIMPI="new_impiinfo",
NEWIMPIAUTHTYPE=TAA;
Response:
If the operation succeeds, one of the following success codes is displayed:
If you enter the command in the command input pane and then specify the related parameters, the KI value,
OPC value, password, and HA1 value are displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the KI value,
OPC value, password, and HA1 value are displayed in plain text.
To improve the system security, you are advised to set the password by following at least three of the rules
below:
The password must contain upper-case letter.
The password must contain lower-case letter.
The password must contain digits.
The password must contain special characters:`~!@#$%^&*()-_=+\|[{}];:'",<.>/? .
And notice three of the rules below:
Avoid using three or more than three consecutive letters or digits, for example, ABC or
123.
Avoid using account or the account in reverse order as the password.
Avoid using three or more than three same characters, for example, AAA.
REALM can be set to a string of 32 to 46 characters only when the domain name suffix is .
3gppnetwork.org. If the domain name suffix is in the other format, this parameter can be only set to a string
of a maximum of 31 characters. Because the domain name suffix 3gppnetwork.org is case insensitive, it
will be displayed in lowercase letters. For example, if you set REALM to
SOFT300.IMS.mnc001.mcc001.3gPPNETwork.org, the domain name suffix of the realm is displayed as
SOFT300.IMS.mnc001.mcc001.3gppnetwork.org.
Add an IMPU
Command Name: ADD HIMPU
Function: This command is used to add an IP Multimedia Public Identity (IMPU) data record
for an existing IP Multimedia Private Identity (IMPI) to the Home Subscriber Server (HSS)
database.After an IMPU data record is added for the IMPI, the subscriber identified by the
IMPI can use the IMPU to connect to the IP Multimedia Subsystem (IMS) network.
Parameter Description:
Example:
1. ADD HIMPU: IMPI="impiinfo", IMPU="sip:impuinfo@huawei.com";
2. ADD HIMPU: IMPI="impiinfo", IMPU="tel:+33145297![247].*!", IMPUTYPE=WIMPU;
Response:
None.
Remove an IMPU
Command Name: RMV HIMPU
Function: This command is used to remove an IP Multimedia Public Identity (IMPU) data
record from the Home Subscriber Server (HSS) database.
Parameter Description:
Example:
RMV HIMPU: IMPU="sip:impuinfo@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Removing an IMPU data record will deregister the subscriber identified by the IMPU. In this case, the
subscriber will experience service failure. Therefore, make sure this operation serves the intended purpose
before removing an IMPU data record.
Modify an IMPU
Command Name: MOD HIMPU
Function: This command is used to modify an IP Multimedia Public Identity (IMPU) data
record in the Home Subscriber Server (HSS) database. The IMPU parameter uniquely
identifies an IMPU data record. This command is executed when the subscriber identified by
the IMPU changes the IMPU while retaining the IMPI and the services defined in the IMPI.
Parameter Description:
Example:
1. MOD HIMPU:IMPU="sip:impuinfo@huawei.com",
NEWIMPU="sip:new_impuinfo@huawei.com";
2. MOD HIMPU:IMPU="sip:impuinfo@huawei.com", NEWIMPU="tel:+33145297!
[247].*!", NEWIMPUTYPE=WIMPU;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Modifying an IMPU data record will deregister the subscriber identified by the IMPU. In this case, the
subscriber will experience service failure. Therefore, make sure this operation serves the intended
purpose before modifying an IMPU data record.
Check an IMPU
Command Name: CHK HIMPU
Function: This command is used check whether an IMPU and an IMPI associate with the
same subscription ID.
Parameter Description:
Example:
CHK HIMPU: IMPI="impiinfo", IMPU="sip:impuinfo@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
None.
Example:
SET HIMPUSHARE: IMPU="sip:impuinfo@huawei.com", SHARED=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The IMPU cannot be shared when only one IMPI exists in the IMS subscription to which the IMPU
belongs.
The sharing attribute of the default IMPU of an IRS cannot be set.
If an IMPU belongs to an IRS but it is not the default IMPU, the IMPU automatically disengages from the
IRS after the sharing attribute of the IMPU is changed. At the same time, if only one IMPU exists in the
IRS, the IRS is deleted consequently.
Example:
ADD HPSI: PISI="pisiinfo", PUSI="sip:pusiinfo@huawei.com", PUSITYPE=DPUSI,
SYSNO=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
RMV HPSI: PISI="pisiinfo";
Example:
LST HPSI: PISI="pisiinfo";
Response:
Success output: Horizontal format
Output:
Parameter description:
PISI: PISI Number
PUSI: PUSI Number
IRSID: IRS ID
PUSITYPE: 1 | 2
Remark: 1 represents DISTINCT, 2 represents WILDCARDED
SYSNO: System Serial Number
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Set an IRS
Command Name: SET HIRS
Function: This command is used to set an Implicitly Registered Set (IRS) for multiple IP
Multimedia Public Identities (IMPUs) or Public Service Identities (PUSIs) in the Home
Subscriber Server (HSS) database. Run SET HIRS when you need to:
Add an IRS.
Add IMPUs or PUSIs to an existing IRS.
Remove IMPUs or PUSIs from an existing IRS or remove an IRS.
The IMPUs or PUSIs in the same IRS share the same registration or unregistration
permissions. The default IMPU in the new IRS is the first IMPU in the IMPU list. You can
also run SET HDEFIMPU to set the default IMPU for an existing IRS.
Parameter Description:
Example:
1. SET HIRS: IRSID=1,
IMPULIST="\"sip:impuinfo_1@huawei.com\"&\"sip:impuinfo_2@huawei.com\"&\"sip:imp
uinfo_3@huawei.com\"";
2. SET HIRS: IRSID=1, IMPULIST="\"sip:impuinfo_4@huawei.com\"";
3. SET HIRS: IRSID=0,
IMPULIST="\"sip:impuinfo_1@huawei.com\"&\"sip:impuinfo_2@huawei.com\"&\"sip:imp
uinfo_3@huawei.com\"";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
SET HDEFIMPU: IRSID=2, IMPU="sip:impuinfo@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Add an IMSI
Command Name: ADD HIMSI
Example:
ADD HIMSI: IMSI="460001234567890", ISDN="8613988888888";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If the IMPI is specified, the IMPI cannot associate other IMSIs. Otherwise, the HSS displays that the
operation has failed.
If the IMPI is specified, an IMSI-IMPI mapping is added in the operation.
If the IMPI is not specified, only the IMSI is added in the operation.
Remove an IMSI
Command Name: RMV HIMSI
Function: This command is used to remove an IMSI data record from the HSS service
database.
Parameter Description:
Example:
RMV HIMSI: IMSI="460001234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
None.
Modify an IMSI
Command Name: MOD HIMSI
Function: This command is used to modify an IMSI data record in the HSS service database.
The IMSI is the key parameter used to determine the data record to be modified.
Parameter Description:
Example:
MOD HIMSI: IMSI="460001234567890", NEWIMSI="460001234567891";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
MOD HHSSIMSI: IMPI="impiinfo", IMPU="sip:impuinfo@huawei.com",
NEWIMPI="new_impiinfo", NEWIMPIAUTHTYPE=EAA, IMSI="460001234567890",
ISDN="8613977777777", NEWIMPU="sip:new_impuinfo@huawei.com",
IMPI2="impi2info", IMPU2="sip:impu2info@huawei.com", NEWIMPI2="new_impi2info",
NEWIMPI2AUTHTYPE=TAA, NEWIMPU2="sip:new_impu2info@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
IMPI, IMPU, IMPI2, and IMPU2 must be associated with the same subscriber.
Specify both IMPU and NEWIMPU or neither of them. Similarly, specify both IMPU2 and NEWIMPU2
or neither of them.
Assign different values to the following parameters:
IMPI and IMPI2
IMPU and IMPU2
NEWIMPI and NEWIMPI2
NEWIMPU and NEWIMPU2
When setting parameter IMPU, note the following:
The IMPU must be in SIP URI or TEL URI format.
The IMPU must be a distinct IMPU.
Add an MSISDN
Command Name: ADD HISDN
Function: This command is used to add an MSISDN data record to the HSS service database
and build an association between the MSISDN and the specified IMSI. The data record may
be used during 2G subscriber authentication.
Parameter Description:
Example:
ADD HISDN: IMSI="861381234567890", ISDN="861381234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Remove an MSISDN
Command Name: RMV HISDN
Example:
RMV HISDN: ISDN="861381234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Modify an MSISDN
Command Name: MOD HISDN
Function: This command is used to modify an MSISDN data record in the HSS service
database. The MSISDN is the key parameter used to determine the data record to be modified.
Parameter Description:
Example:
MOD HISDN: ISDN="8613988888888", NEWISDN="8613977777777";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD HHSSTN: ISDN="8613988888888", NEWISDN="8613977777777",
IMPU="sip:impuinfo@huawei.com", NEWIMPU="sip:new_impuinfo@huawei.com",
IMPU2="sip:impu2info@huawei.com", NEWIMPU2="sip:new_impu2info@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
MSISDN, IMPU, and IMPU2 must be associated with the same subscriber.
Set different values for IMPU and IMPU2 as well as NEWIMPU and NEWIMPU2.
Specify both IMPU and NEWIMPU or neither of them. Similarly, specify both IMPU2 and NEWIMPU2
or neither of them.
When setting parameter IMPU, note the following:
The IMPU must be in SIP URI or TEL URI format.
The IMPU must be a distinct IMPU.
When setting parameter NEWIMPU, note the following:
The NEWIMPU must be in SIP URI or TEL URI format.
The NEWIMPU must be a distinct IMPU.
Example:
LST HMSID: IMSI="8613988888888";
Response:
Success output: Horizontal format
Output:
Parameter description:
IMPI: IMPI Number
IMSI: IMSI Number
ISDN: MSISDN Number
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
ADD HASSOC: IMPI="impiinfo", IMSI="460001234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
RMV HASSOC: IMPI="impiinfo", IMSI="460001234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HASSOC: IMPI="impiinfo";
Response:
Success output: Horizontal format
Output:
IMPI IMSI
Parameter description:
IMPI: IMPI Number
IMSI: IMSI Number
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD HMSIM: IMSI="1234567891", MASTERFLAG=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
LST HMSIM:SUBID="subinfo";
Response:
Success output: Mixed format
Output:
{SUBID}=< Subscription ID >
IMSI MASTERFLAG
Parameter description:
Example:
1.LST HSUBBAT:;
2.LST HSUBBAT: FUZZYIMPU="+86134";
Response:
Success output: Horizontal format
Output:
Parameter description:
SUBID:Subscription ID
IMPI:IMPI Number
IMPU:IMPU Number
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
SET HMOCAP: SUBID="subinfo", MCAP="1&2", OCAP="3&4";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HMOCAP: SUBID="subinfo";
Response:
Success output: Horizontal format
Output:
MCAP OCAP
Parameter description:
MCAP: Mandatory Capability Set
OCAP: Optional Capability Set
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD CAP: IMSI="123456789", MCAP="1&2", OCAP="3&4",
SCSCFLIST="\"sip:scscf1.huawei.com\"&\"sip:scscf2.huawei.com\"";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
ADD HCAPSCSCF: SUBID="subinfo", SCSCF="sip:scscf@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
RMV HCAPSCSCF: SUBID="subinfo", SCSCF="sip:scscf@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
SCSCF
Parameter description:
SCSCF: S-CSCF Name
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
SET HCHARGID: IMPI="impiinfo", CHARGTPLID=10;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HCHARGID: PISI="pisiinfo";
Response:
Success output: Horizontal format
Output:
CHARGTPLID
Parameter description:
CHARGTPLID: Charging Address Template ID
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
SET HREGAUTH:IMPU="sip:impuinfo@huawei.com", REGAUTH=FALSE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The IMPU value must be in SIP URI or TEL URI format. The value of the parameter is case-sensitive.
Example:
LST HREGAUTH: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
REGAUTH
Parameter description:
REGAUTH: 1 | 0
Remark: 1 represents TRUE, 0 represents FALSE
The IMPU value must be in SIP URI or TEL URI format. The value of the parameter is case-sensitive.
Example:
SET HVNCFLAG: IMPU="sip:impuinfo@huawei.com", VNCFLAG=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The IMPU value must be in SIP URI or TEL URI format. The value of the parameter is case-sensitive.
Example:
LST HVNCFLAG: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
VNCFLAG
Parameter description:
VNCFLAG: 1 | 0
Remark: 1 represents TRUE, 0 represents FALSE
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The IMPU value must be in SIP URI or TEL URI format. The value of the parameter is case-sensitive.
Example:
SET HVNTPLID: IMPU="sip:impuinfo@huawei.com", VNTPLID=10;
Response:
If the operation succeeds, one of the following success codes is displayed:
The IMPU value must be in SIP URI or TEL URI format. The value of the parameter is case-sensitive.
VNTPLID specifies a visited network template ID. If Visited network template ID is set to 255, the original
roaming authority for the specified IMPU is disabled. The parameter must be defined by running ADD
HVNTPL before being referenced here.
Example:
LST HVNTPLID: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
TPLID
Parameter description:
TPLID: Visited Network Template ID
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The IMPU value must be in SIP URI or TEL URI format. The value of the parameter is case-sensitive.
Example:
SET HNNCFLAG: IMPU="sip:impuinfo@huawei.com", NNCFLAG=ACTIVE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
LST HNNCFLAG: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
Parameter description:
NNCFLAG: 1 | 0
Remark: 1 represents ACTIVE, 0 represents DEACTIVE
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
1. SET HNATPLID: IMPU="sip:impuinfo@huawei.com", NATPLID=10;
2. SET HNATPLID: IMPU="sip:impuinfo@huawei.com", TPLNAME="07550011";
3. SET HNATPLID: IMPU="sip:impuinfo@huawei.com", NATPLID=255;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HNATPLID: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
NATPLID TPLNAME
Parameter description:
NATPLID: NASS Nomadism Template ID
TPLNAME: NASS Nomadism Template Name
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If the NASS nomadism template data record identified by the specified IMPU does not exist, the HSS does
not display any information.
Example:
SET HSPSHARE: BASEIMPU="sip:impuinfo_base@huawei.com",
IMPU="sip:impuinfo@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The IMPU and base IMPU must have been defined and associated with the same IMS subscription.
If a service profile associated with a specified IMPU is not shared by other IMPUs, the service profile is
removed after SET HSPSHARE is executed to associate this IMPU with the same service profile as the
base IMPU.
Example:
1. RMV HSPSHARE:
IMPULIST="\"sip:impuinfo_1@huawei.com\"&\"sip:impuinfo_2@huawei.com\"";
2. RMV HSPSHARE:
IMPULIST="\"sip:impuinfo_1@huawei.com\"&\"sip:impuinfo_2@huawei.com\"";
Response:
After the service profile shared by one or more IMPUs is unshared, the IMPUs will be automatically
associated with a new service profile. The new service profile includes the same subscription data as the
originally shared service profile.
To automatically associate the IMPUs whose service profiles are unshared with different service profiles,
run RMV HSPSHARE with only one IMPU specified for IMPU list each time.
Example:
LST HSPSHARE: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
IMPU
Parameter description:
IMPU: IMPU Number
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
ADD HNNRLI: IMPU="sip:impuinfo@huawei.com", RLINDEX=1, RLI="shenzhen",
RLT=IEEE-802.11;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The IMS-HSS includes location reference information of an IMPU in an SAA sent to the S-CSCF only after
checking that:
The RLI deliver switch software parameter is set to 1.
The IMPU is the default IMPU in an implicitly registered set (IRS).
Example:
1. RMV HNNRLI: IMPU="sip:impuinfo@huawei.com", RLINDEX=1;
2. RMV HNNRLI: IMPU="sip:impuinfo@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
After the reference location information of an IMPU is removed, the IMS-HSS does not send the reference
location information to the S-CSCF, resulting in failures to provide location services for the fixed-line
subscriber. Exercise caution when deciding to run this command.
The default reference location data record cannot be removed. (To query the default reference location data
record, run LST HNNRLI. The reference location data record whose DEFRLI is 1 in the output is the
default reference location data record.)
Example:
MOD HNNRLI: IMPU="sip:impuinfo@huawei.com", RLINDEX=1, RLI="huawei",
RLT=IEEE-802.11b;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
1. LST HNNRLI: IMPU="sip:impuinfo@huawei.com";
2. LST HNNRLI: IMPU="sip:impuinfo@huawei.com", RLINDEX=1;
Response:
Success output: Horizontal format
Output:
Parameter description:
RLINDEX: Reference Location Index
RLI: Reference Location Information
RLT: 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |11 | 12 | 13
Remark: 0 represents IEEE-802.11, 1 represents IEEE-802.11a, 2 represents IEEE-802.11b, 3
represents IEEE-802.11g, 4 represents ADSL, 5 represents ADSL2, 6 represents
ADSL2+, 7 represents RADSL, 8 represents SDSL, 9 represents HDSL, 10
represents HDSL2, 11 represents G.SHDSL, 12 represents VDSL, 13 represents
IDSL
None.
Example:
SET HBAR: IMPU="sip:impuinfo@huawei.com", BAR=TRUE;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HBAR: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
BAR
Parameter description:
BAR: 1 | 0 Remark: 1 represents TRUE, 0 represents FALSE
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
SET HMEDIAID: PUSI="sip:pusiinfo@huawei.com", MEDIAID=4294967293;
Example:
LST HMEDIAID: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
MEDIAID
Parameter description:
MEDIAID: Subscribed Media Pofile ID
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Add an iFC
Command Name: ADD HIFC
Example:
ADD HIFC: IMPU="sip:impuinfo@huawei.com", PRIORITY=1, PARTIND=REGISTERED,
SERVER="sip:server1@huawei.com", DEFHND=SESSION_CONTINUED,
SERVINFO="Service Information", INCLUDEREGREQ=NO, TRIGPT="Triffer point";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Remove an iFC
Command Name: RMV HIFC
Function: This command is used to remove the initial filter criteria (iFC) of the specified
priority from the service profile of the specified IMPU or PUSI in the HSS service database.
Parameter Description:
Example:
RMV HIFC: IMPU="sip:impuinfo@huawei.com", PRIORITY=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Modify an iFC
Command Name: MOD HIFC
Function: This command is used to modify the initial filter criteria (iFC) information to be
inclusive in the service profile of the specified IMPU or PUSI in the HSS service database.
Parameter Description:
Example:
MOD HIFC: IMPU="sip:impuinfo@huawei.com", PRIORITY=1, NEWPRI=3;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
List iFCs
Command Name: LST HIFC
Function: This command is used to query the initial filter criteria (iFC) information inclusive
in the service profile of the specified IMPU or PUSI in the HSS service database. You can
fulfill either of the following tasks using the operation:
Example:
LST HIFC: IMPU="sip:impuinfo@huawei.com", PRIORITY=1;
Response:
Success output: Horizontal format
Output:
Parameter description:
PRIORITY: Priority
PARTIND: 0 | 1 | 2
Remark: 0 represents REGISTERED, 1 represents UNREGISTERED, 2 represents
PARTIND_DEFAULT
SERVER: AS Address
DEFHND: 0 | 1 | 2
Remark: 0 represents SESSION_CONTINUED, 1 represents SESSION_TERMINATED, 2
represents DEFHANDLING_DEFAULT
SERVINFO: Service Information
INCLUDEREGREQ: 0 | 1 Remark: 1 represents YES, 0 represents NO
TRIGPT: Trigger Point
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
RMV HALLIFC: IMPU="sip:impuinfo@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The IMPU value must be in SIP URI or TEL URI format. The value of the parameter is case-sensitive.
Example:
RMV HASIFC: IMPU="sip:impuinfo@huawei.com", SERVER="sip:as@huawei.com";
Response:
None.
Example:
ADD HSIFC: IMPU="sip:impuinfo@huawei.com", SIFCID=10;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Each IMPU or PUSI can be configured with a maximum of eight shared iFC templates.
Either IMPU or PUSI must be specified.
When setting parameter SIFCID, note the following:
The shared iFC template ID must be different from any existing shared iFC template ID
associated with the IMPU or PUSI.
The parameter must be defined by running ADD HSIFCTPL before being referenced.
Example:
RMV HSIFC: IMPU="sip:impuinfo@huawei.com", SIFCID=10;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD HSIFC: IMPU="sip:impuinfo@huawei.com", OSIFCID=10, NSIFCID=11;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
SIFCID
Parameter description:
SIFCID: Shared iFC Template ID
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
ADD HSERPRV: IMPU="sip:impuinfo@huawei.com", SERPRVID="huawei";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
RMV HSERPRV: IMPU="sip:impuinfo@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
MOD HSERPRV: IMPU="sip:impuinfo@huawei.com",
SERPRVID="huawei";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HSERPRV: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
SERPRVID
Parameter description:
SERPRVID: Service provider ID
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
SET HUSRPRIOR: IMPU="sip:impuinfo@huawei.com",
USRPRIOR=HIGH;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HUSRPRIOR: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
USRPRIOR
Parameter description:
USRPRIOR: 0 | 1 | 2
Remark: 0 represents HIGH, 1 represents MIDDLE, 2 represents LOW
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
1. SET HSTDPRIOR: IMPU="sip:impuinfo@huawei.com", STDPRIOR=MIDDLE-
PRIORITY, NAMESPACE=WPS, EXTPRIOR=2;
2. SET HSTDPRIOR: IMPU="tel:+123", NAMESPACE=WPS, EXTPRIOR=255;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HSTDPRIOR: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Mixed format
Output:
STDPRIOR
Parameter description:
STDPRIOR: 0 | 1 | 2 | 3 | 4
Remark: 0 represents HIGHEST-PRIORITY, 1 represents HIGH-PRIORITY , 2 represents
MIDDLE-PRIORITY, 3 represents LOW-PRIORITY, 4 represents LOWEST-PRIORITY
NAMESPACE:0 Remark: 0 represents WPS
EXTPRIOR:Extended Priority
CNAMESP:Custom-built Priority Namespace
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
SET HLRI: IMPU="sip:impuinfo@huawei.com",
LRI=LOOSE_ROUTE_REQUIRED;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HLRI: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
LRI
Parameter description:
Example:
ADD HASSPID: IMPU="sip:impuinfo@huawei.com", ASSPID=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
RMV HASSPID: IMPU="sip:impuinfo@huawei.com", ASSPID=10;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If AS service profile ID is not specified, all the AS service profile IDs associated with the IMPU or PUSI
are removed.
Only one of the parameters IMPU and PUSI must be specified.
Example:
LST HASSPID: IMPU="sip:impuinfo@huawei.com";
Response:
ASSPID
Parameter description:
ASSPID: AS Service Profile ID
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
1. SET HALIASPU: ALIASID=1,
IMPULIST="\"sip:impuinfo_1@huawei.com\"&\"sip:impuinfo_2@huawei.com\"";
2. SET HALIASPU: ALIASID=1,
IMPULIST="\"sip:impuinfo_3@huawei.com\"&\"sip:impuinfo_4@huawei.com\"";
3. SET HALIASPU: ALIASID=0, IMPULIST="\"sip:impuinfo_4@huawei.com\"";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
1. SET HREPDATA: IMPU="sip:impuinfo@huawei.com", SERVICEID="3",
SERVICEDATA="SH_RSI_DATA", REPTYPE=REPDATA;
2. SET HREPDATA: IMPU="sip:impuinfo@huawei.com", SERVICEID="3",
SERVICEDATA="SH_STR_DATA", REPTYPE=REPDATA;
Example:
LST HREPDATA:IMPU="sip:impuinfo@huawei.com", REPTYPE=ALIASREPDATA,
SRVIND="10";
Response:
Success output: Horizontal format
Output:
Parameter description:
REPDATA: Repository data
REPTYPE: 0 | 1 Remark: 0 represents ALIASREPDATA, 1 represents REPDATA
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
The extended service data is encrypted before it is stored in the database. Therefore, the extended service
data stored in the database is different from the actual input data.
Example:
RMV HPREPDATA:IMPU="sip:impuinfo@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
MOD HPREPDATA: IMPU="sip:impuinfo@huawei.com",
IMSI="400612345678";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HPREPDATA: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
Parameter description:
IMPU: IMPU Number
IMSI: IMSI Number
SELFSERVICE: 1 | 0
Remark: 1 represents TRUE, 0 represents FALSE
SMSCADDRESS: SMSC Address
LOCATIONINFORMATION: Location Information
NPINDICATOR: 1 | 0
Remark: 1 represents TRUE, 0 represents FALSE
CICINDICATOR: 1 | 0
Remark: 1 represents TRUE, 0 represents FALSE
BINDINDICATOR: 1 | 0
Remark: 1 represents TRUE, 0 represents FALSE
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If the result report of this command is "decrypted failed", it This parameter indicates that the data is
repository data, and use LST HREPDATA command to query.
Example:
LST HSRVIND: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
SRVIND REPTYPE
Parameter description:
SRVIND: Service Indication
REPTYPE: 0 | 1 Remark: 0 represents ALIASREPDATA, 1 represents REPDATA
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
LST HAS: PUSI="sip:pusiinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
AS
Parameter description:
AS: AS Address
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
SET HCSI: IMSI="125353", ISDN="86137565425", CSITYPE=O-CSI, CSITPLID=10;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
LST HCSI: IMSI="125353", CSITYPE=O-CSI;
Response:
Success output: Horizontal format
Output:
Parameter description:
IMSI: IMSI Number
ISDN: MSISDN Number
CSITYPE: 0 | 1 Remark: 0 represents O-CSI , 1 represents T-CSI
CSITPLID: CSI Template ID
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
LST HDALI: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Parameter description:
IMSALI: IMS Access Location Information
NASSALI: NASS Access Location Information
IPV4ADDR: IPV4 Address
None.
Example:
LST HASSUBDATA: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
Parameter description:
SUBASID: The ID of an AS
DATATYPE: 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7
Remark: 0 represents IMSUserState, 1 represents S-CSCFName, 2 represents
InitialFilterCriteria, 3 represents RepositoryData, 4 represents PSIActivation, 5 represents
AliasesRepositoryData,6 represents AliasesIMPU, 7 represents IMSI
ASNAME: AS Name
Only one of the two parameters IMPU and PUSI needs to be specified.
Parameter description:
IMPI: IMPI Number
IMPU: IMPU Number
IMSUSERST: 0 | 1 | 2
Remark: 0 represents NOTREGISTERED, 1 represents UNREGISTERED, 2 represents
REGISTERED
PENDINGFLAG: 0 | 1
Remark: 0 represents FALSE, 1 represents TRUE
SERVER: Current SCSCF Name
ISEXISTRESTOREDATA: 0 | 1 | 2 | 3
Remark: 0 represents NODATA, 1 represents STDDATA, 2 represents PRVTDATA, 3
represents STDPRVTDATA. Furthermore,
0: S-CSCF Restoration Information does not exist.
1: 3GPP-defined S-CSCF Restoration Information exists.
2: Huawei proprietary S-CSCF Restoration Information exists.
3: Both 3GPP-defined and Huawei proprietary S-CSCF Restoration Information exists.
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HPSIDYND: PUSI="sip:pusiinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
Parameter description:
PISI: PISI Number
PUSI: PUSI Number
ACTSTATE: 0 | 1
Remark: 0 represents INACTIVE, 1 represents ACTIVE
REGSTATE: 0 | 1
Remark: 0 represents NOTREGISTERED, 1 represents UNREGISTERED
SERVER: Current SCSCF Name
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If only PISI is specified, the dynamic data of all the PUSI-PISI pairs is queried.
If only PUSI is specified, the dynamic data of the PUSI-PISI pair is queried.
If PISI and PUSI are specified, the dynamic data of the PUSI-PISI pair is queried.
Deregister Subscribers
Command Name: DRG HUSER
Function: This command is used to enable the Provisioning System to send a deregistration
notification. The operation applies to a single user or a group of users.
Parameter Description:
Example:
SET HESRN: IMPU="sip:impuinfo@huawei.com", ESRN=shenzhenbantian;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If ESRN is not specified, all the ESRN associated with the IMPU is removed.
Example:
LST HESRN: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
ESRN
Parameter description:
ESRN: Emergency Service Routing Number
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
ADD HONEKEY: IMPU="sip:impuinfo@huawei.com", WUSERNAME="WUSERNAME",
HTOKEN="HTOKEN", AP="AP";
None.
Example:
RMV HONEKEY: IMPU="sip:impuinfo@huawei.com";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
MOD HONEKEY: IMPU="sip:impuinfo@huawei.com",
WUSERNAME="WUSERNAME", HTOKEN="HTOKEN", AP="AP";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
At least one of the parameters Web user name, HTTP token, and Aggregation proxy must be specified.
Example:
LST HONEKEY: IMPU="sip:impuinfo@huawei.com";
Response:
Success output: Horizontal format
Output:
WUSERNAME HTOKEN AP
Parameter description:
WUSERNAME: Web User Name
HTOKEN: HTTP Token
None.
Example:
ADD HGUSS: IMPI="impiinfo", GSID=PKI-PORTAL, GAAAUTHFLAG=1,
NAFGROUP="nafgroup";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
RMV HGUSS: IMPI="impiinfo", GSID=PKI-PORTAL;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
To delete GUSS of a specified GAA service type, specify GAA Service Identifier.
To delete GUSS of all GAA service types, do not specify GAA Service Identifier.
The IMPI must be in NAI format. The value of this parameter is case-sensitive.
Example:
Example:
LST HGUSS: IMPI="impiinfo";
Response:
Parameter description:
GSID: 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13
Remark: 0 represents UNSPECIFIC_SERVICE, 1 represents PKI-PORTAL, 2 represents
AUTHENTICATION_PROXY, 3 represents PRESENCE, 4 represents MBMS, 5
represents LIBERTY_ALLIANCE_PROJECT, 6 represents UICC-
TERMINAL_KEY_ESTABLISHMENT, 7 represents TERMINAL-
REMOTE_DEVICE_KEY_ESTABLISHMENT, 8 represents ANDSF, 9
represents GBA_PUSH, 10 represents IMS_BASED_PSS_MBMS, 11 represents
OPENID_GBA_INTERWORKING, 12 represents GENERIC_PUSH_LAYER, 13
represents OPENID_INTERWORKING
GAAAUTHFLAG: GAA Authorization Flag
NAFGROUP: NAF Grouping
UICCTYPE: 0 | 1
Remark: 0 represents GBA, 1 represents GBA_U
KEYCHOICE: 0 | 1 | 2
Remark: 0 represents ME-based-key, 1 represents UICC-based-key, 2 represents ME-UICC-
based-keys
TIMESTAMP: Time stamp
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
The IMPI must be in NAI format. The value of this parameter is case-sensitive.
Example:
ADD HRCSSERVICE: IMSI="460009876543210", ISDN="8613955555555",
WHOLESALEID="1234", SEGMENTID=0, ACPTTERMSTATUS=TCACCEPTED;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Before running ADD HRCSSERVICE to add RCS data for an IMS subscriber, run ADD HSIFCTPL to add
shared iFC templates with IDs 4097, 4099, 4353, and 4609.
All the IMPUs of the subscriber must be configured to share a service profile by running SET HSPSHARE.
Before running ADD HRCSSERVICE to add RCS data for an IMS subscriber, run ADD HIMSI and ADD
HISDN to associate the subscriber's IMSI and MSISDN with their IMPI.
The subscriber's IMPI must be registered with the SIP Digest authentication scheme using a user name and
a password by running ADD HSDAINF.
Example:
MOD HRCSSTATUS: IMSI="460009876543210",
ACPTTERMSTATUS=NOTPROCESSED;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
LST HRCSSERVICE: IMSI="460009876543210";
Response:
Success output: Horizontal format
Output:
DEVICESATTR_CN DEVICESATTR
Parameter description:
IMSI: IMSI Number
ISDN: MSISDN Number
IMPROVISIONINGSTATUS: Whether the subscriber is provided with the chat service
IMACTIVATIONSTATUS: Whether the chat service is active for the subscriber
FSPROVISIONINGSTATUS:Whether the subscriber is provided with the file share service
Example:
SET HSMSCADDR: ISDN="4600000091234", SMSCADDR="1234567890";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
RMV HSMSCADDR: ISDN="4600000091234";
Response:
If the operation succeeds, one of the following success codes is displayed:
After the SMSC address of a subscriber is deleted, the HSS will not include the SMSC address in UDA
messages sent to the AS.
Example:
LST HSMSCADDR: ISDN="4600000091234";
Response:
Success output: Horizontal format
Output:
ISDN SMSCADDR
Parameter description:
ISDN: MSISDN Number
SMSCADDR: Short Message Center Address
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
ADD HTPLKI: IMPI="impiinfo", K="1234567890abcdef1234567890ABCDEF ",
AKATPLID=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
If you enter the command in the command input pane and then specify the related parameters, the KI value
is displayed as a string of asterisks (*).
If you enter the command with the related parameters in the MML command line input pane, the KI value is
displayed in plain text.
Example:
1. ADD HTPLSUB: SUBID="subinfo", IMPI="impiinfo",
IMPU="sip:impuinfo@huawei.com", CAPTPLID=1, CHARGTPLID=1, SPTPLID=1,
IMPUTPLID=1, PBXUSERFLAG=TRUE;
2. ADD HTPLSUB: SUBID="subinfo", IMPI="impiinfo", IMPU="tel:+33145297![247].*!",
IMPUTYPE=WIMPU, CAPTPLID=1, CHARGTPLID=1, SPTPLID=1, IMPUTPLID=1,
PBXUSERFLAG=TRUE, SYSNO=10;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
When Service profile template ID or IMPU template ID is specified, IMPU must be specified.
When Charging template ID, Capability template ID, or IMPU is specified, IMPI must be specified.
Example:
1. ADD HTPLIMPI: SUBID="subinfo", IMPI="impiinfo",
IMPU="sip:impuinfo@huawei.com", CHARGTPLID=1, SPTPLID=1, IMPUTPLID=1;
2. ADD HTPLIMPI: SUBID="subinfo", IMPI="impiinfo", IMPU="tel:+33145297![247].*!",
IMPUTYPE=WIMPU, CHARGTPLID=1, SPTPLID=1, IMPUTPLID=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
When Service profile template ID or IMPU template ID is specified, IMPU must be specified.
Example:
None.
Example:
ADD HTPLPSI: PISI="pisiinfo", PUSI="sip:pusiinfo@huawei.com", PUSITYPE=DPUSI,
CAPTPLID=1, CHARGTPLID=1, SYSNO=1;
Response:
None.
Example:
ADD HTPLPUSI: PISI="pisiinfo", PUSI="sip:pusiinfo@huawei.com", PUSITYPE=DPUSI,
SPTPLID=1, PUSITPLID=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
None.
Example:
ADD HTPLIFC: IMPU="sip:impuinfo@huawei.com", IFCTPLID=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
ADD TPLIMSSUB: HLRSN=1, IMSI="460001234567890", IMPI="impiinfo",
IMPULIST="\"sip:impuinfo_1@huawei.com\"&\"sip:impuinfo_2@huawei.com\"",
VOLTETAG=TRUE, IMSTPLID=1;
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
1. SET HESRNBAT: ESRN="shenzhenbantian", BATTYPE=CONTINUOUS,
IMPU="sip:hello![0-9]{2}!@huawei.com";
2. SET HESRNBAT: ESRN="shenzhenbantian", BATTYPE=DISCONTINUOUS,
IMPUFILE="impu.txt";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
1. MOD HSIFCBAT: OSIFCID=1, NSIFCID=2, BATTYPE=CONTINUOUS,
IMPU="sip:hello![0-9]{2}!@huawei.com";
2. MOD HSIFCBAT: OSIFCID=1, NSIFCID=2, BATTYPE=DISCONTINUOUS,
IMPUFILE="impu.txt";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
1. RMV HSUBBAT: BATTYPE=CONTINUOUS, SUBID="test![0-9]{2}!";
2. RMV HSUBBAT: BATTYPE=DISCONTINUOUS, SUBIDFILE="SUBID_LIST.txt";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
Example:
1. RMV HSDABAT: BATTYPE=CONTINUOUS, IMPI="test![0-9]{2}!";
2. RMV HSDABAT: BATTYPE=DISCONTINUOUS, IMPIFILE="IMPI_LIST.txt";
Response:
If the operation succeeds, one of the following success codes is displayed:
SUCCESS0001:Operation is successful
If the operation fails, the error codes will be returned. For details of the above error codes, see
11"Summary of Error Codes".
ODBBOC
ODBROAM
NOBAR 0 No Barring
BROHPLMN 1 Barring of roaming outside the home PLMN
BROHPLMNC 2 Barring of roaming outside the home PLMN country
BROHPLMNCG 3 Barring GPRS of roaming outside the home PLMN country
PRS
provisioned 0 -
active 1 -
10.21 PrivacyException1-ExceptionClientList1-GMLC-
Restrict(LCSPGMLCR) Enumeration
Name Value Description
provisioned 0 -
active 1 -
UNKNOWN 0x00 -
FRENCH 0x01 -
ENGLISH 0x02 -
GERMAN 0x03 -
RUSSIAN 0x04 -
SPANISH 0x05 -
SPECIAL1 0x06 -
SPECIAL2 0x07 -
SPECIAL3 0x08 -
RESERVE 0x09 -
COMMON 0x0a -
SUPERIOR 0x0b -
DATACALL 0x0c -
TESTCALL 0x0d -
SPARE 0x0e -
PAYPHONE 0x0f -
16 0x10 -
17 0x11 -
31 0x1f -
COIN 0x20 -
33 0x21 -
254 0xfe -
MNP 0xff
1K 1 1Kbps
2K 2 2Kbps
3K 3 3Kbps
4K 4 4Kbps
5K 5 5Kbps
6K 6 6Kbps
7K 7 7Kbps
8K 8 8Kbps
9K 9 9Kbps
10K 10 10Kbps
11K 11 11Kbps
12K 12 12Kbps
13K 13 13Kbps
14K 14 14Kbps
15K 15 15Kbps
16K 16 16Kbps
17K 17 17Kbps
18K 18 18Kbps
19K 19 19Kbps
20K 20 20Kbps
21K 21 21Kbps
22K 22 22Kbps
23K 23 23Kbps
24K 24 24Kbps
25K 25 25Kbps
26K 26 26Kbps
27K 27 27Kbps
28K 28 28Kbps
29K 29 29Kbps
30K 30 30Kbps
31K 31 31Kbps
32K 32 32Kbps
33K 33 33Kbps
34K 34 34Kbps
35K 35 35Kbps
36K 36 36Kbps
37K 37 37Kbps
38K 38 38Kbps
39K 39 39Kbps
40K 40 40Kbps
41K 41 41Kbps
42K 42 42Kbps
43K 43 43Kbps
44K 44 44Kbps
45K 45 45Kbps
46K 46 46Kbps
47K 47 47Kbps
48K 48 48Kbps
49K 49 49Kbps
50K 50 50Kbps
51K 51 51Kbps
52K 52 52Kbps
53K 53 53Kbps
54K 54 54Kbps
55K 55 55Kbps
56K 56 56Kbps
57K 57 57Kbps
58K 58 58Kbps
59K 59 59Kbps
60K 60 60Kbps
61K 61 61Kbps
62K 62 62Kbps
63K 63 63Kbps
64K 64 64Kbps
72K 65 72Kbps
80K 66 80Kbps
88K 67 88Kbps
96K 68 96Kbps
104K 69 104Kbps
112K 70 112Kbps
120K 71 120Kbps
128K 72 128Kbps
136K 73 136Kbps
144K 74 144Kbps
152K 75 152Kbps
160K 76 160Kbps
168K 77 168Kbps
176K 78 176Kbps
184K 79 184Kbps
192K 80 192Kbps
200K 81 200Kbps
208K 82 208Kbps
216K 83 216Kbps
224K 84 224Kbps
232K 85 232Kbps
240K 86 240Kbps
248K 87 248Kbps
256K 88 256Kbps
264K 89 264Kbps
272K 90 272Kbps
280K 91 280Kbps
288K 92 288Kbps
296K 93 296Kbps
304K 94 304Kbps
312K 95 312Kbps
320K 96 320Kbps
328K 97 328Kbps
336K 98 336Kbps
344K 99 344Kbps
352K 100 352Kbps
360K 101 360Kbps
368K 102 368Kbps
376K 103 376Kbps
384K 104 384Kbps
392K 105 392Kbps
400K 106 400Kbps
408K 107 408Kbps
416K 108 416Kbps
424K 109 424Kbps
NOExtend 0 NOExtend
8700K 1 8700Kbps
8800K 2 8800Kbps
8900K 3 8900Kbps
9000K 4 9000Kbps
9100K 5 9100 bps
9200K 6 9200Kbps
9300K 7 9300Kbps
9400K 8 9400Kbps
9500K 9 9500Kbps
9700K 11 9700Kbps
9800K 12 9800Kbps
9900K 13 9900Kbps
10000K 14 10000Kbps
10100K 15 10100Kbps
10200K 16 10200Kbps
10300K 17 10300Kbps
10400K 18 10400Kbps
10500K 19 10500Kbps
10600K 20 10600Kbps
10700K 21 10700Kbps
10800K 22 10800Kbps
10900K 23 10900Kbps
11000K 24 11000Kbps
11100K 25 11100Kbps
11200K 26 11200Kbps
11300K 27 11300Kbps
11400K 28 11400Kbps
11500K 29 11500Kbps
11600K 30 11600Kbps
11700K 31 11700Kbps
11800K 32 11800Kbps
11900K 33 11900Kbps
12000K 34 12000Kbps
12100K 35 12100Kbps
12200K 36 12200Kbps
12300K 37 12300Kbps
12400K 38 12400Kbps
12500K 39 12500Kbps
12600K 40 12600Kbps
12700K 41 12700Kbps
12800K 42 12800Kbps
12900K 43 12900Kbps
13000K 44 13000Kbps
13100K 45 13100Kbps
13200K 46 13200Kbps
13300K 47 13300Kbps
13400K 48 13400Kbps
13500K 49 13500Kbps
13600K 50 13600Kbps
13700K 51 13700Kbps
13800K 52 13800Kbps
13900K 53 13900Kbps
14000K 54 14000Kbps
14100K 55 14100Kbps
14200K 56 14200Kbps
14300K 57 14300Kbps
14400K 58 14400Kbps
14500K 59 14500Kbps
14600K 60 14600Kbps
14700K 61 14700Kbps
14800K 62 14800Kbps
14900K 63 14900Kbps
15000K 64 15000Kbps
15100K 65 15100Kbps
15200K 66 15200Kbps
15300K 67 15300Kbps
15400K 68 15400Kbps
15500K 69 15500Kbps
15600K 70 15600Kbps
15700K 71 15700Kbps
15800K 72 15800Kbps
15900K 73 15900Kbps
16000K 74 16000Kbps
17M 75 17Mbps
18M 76 18Mbps
19M 77 19Mbps
20M 78 20Mbps
21M 79 21Mbps
22M 80 22Mbps
23M 81 23Mbps
24M 82 24Mbps
25M 83 25Mbps
26M 84 26Mbps
27M 85 27Mbps
28M 86 28Mbps
29M 87 29Mbps
30M 88 30Mbps
31M 89 31Mbps
32M 90 32Mbps
33M 91 33Mbps
34M 92 34Mbps
35M 93 35Mbps
36M 94 36Mbps
37M 95 37Mbps
38M 96 38Mbps
39M 97 39Mbps
40M 98 40Mbps
41M 99 41Mbps
42M 100 42Mbps
43M 101 43Mbps
44M 102 44Mbps
45M 103 45Mbps
46M 104 46Mbps
47M 105 47Mbps
48M 106 48Mbps
49M 107 49Mbps
50M 108 50Mbps
51M 109 51Mbps
52M 110 52Mbps
53M 111 53Mbps
54M 112 54Mbps
55M 113 55Mbps
56M 114 56Mbps
57M 115 57Mbps
58M 116 58Mbps
59M 117 59Mbps
60M 118 60Mbps
61M 119 61Mbps
62M 120 62Mbps
63M 121 63Mbps
64M 122 64Mbps
65M 123 65Mbps
66M 124 66Mbps
67M 125 67Mbps
68M 126 68Mbps
69M 127 69Mbps
10 OCT 1 10 OCTETS
20 OCT 2 20 OCTETS
30 OCT 3 30 OCTETS
40 OCT 4 40 OCTETS
50 OCT 5 50 OCTETS
60 OCT 6 60 OCTETS
70 OCT 7 70 OCTETS
80 OCT 8 80 OCTETS
90 OCT 9 90 OCTETS
100 OCT 10 100 OCTETS
110 OCT 11 110 OCTETS
120 OCT 12 120 OCTETS
130 OCT 13 130 OCTETS
140 OCT 14 140 OCTETS
150 OCT 15 150 OCTETS
160 OCT 16 160 OCTETS
170 OCT 17 170 OCTETS
180 OCT 18 180 OCTETS
190 OCT 19 190 OCTETS
200 OCT 20 200 OCTETS
210 OCT 21 210 OCTETS
220 OCT 22 220 OCTETS
230 OCT 23 230 OCTETS
240 OCT 24 240 OCTETS
250 OCT 25 250 OCTETS
260 OCT 26 260 OCTETS
270 OCT 27 270 OCTETS
280 OCT 28 280 OCTETS
290 OCT 29 290 OCTETS
300 OCT 30 300 OCTETS
310 OCT 31 310 OCTETS
320 OCT 32 320 OCTETS
0.05 1 0.05
0.01 2 0.01
0.005 3 0.005
0.004 4 0.004
0.001 5 0.001
0.0001 6 0.0001
0.00001 7 0.00001
0.000001 8 0.000001
0.00000006 9 0.00000006
0.01 1 0.01
0.007 2 0.007
0.001 3 0.001
0.0001 4 0.0001
0.00001 5 0.00001
0.000001 6 0.000001
0.1 7 0.1
10MS 1 10MS
20MS 2 20MS
30MS 3 30MS
40MS 4 40MS
50MS 5 50MS
60MS 6 60MS
70MS 7 70MS
80MS 8 80MS
90MS 9 90MS
100MS 10 100MS
110MS 11 110MS
120MS 12 120MS
130MS 13 130MS
140MS 14 140MS
150MS 15 150MS
200MS 16 200MS
250MS 17 250MS
300MS 18 300MS
350MS 19 350MS
400MS 20 400MS
450MS 21 450MS
500MS 22 500MS
550MS 23 550MS
600MS 24 600MS
650MS 25 650MS
700MS 26 700MS
750MS 27 750MS
800MS 28 800MS
850MS 29 850MS
900MS 30 900MS
950MS 31 950MS
1000MS 32 1000MS
1100MS 33 1100MS
1200MS 34 1200MS
1300MS 35 1300MS
1400MS 36 1400MS
1500MS 37 1500MS
1600MS 38 1600MS
1700MS 39 1700MS
1800MS 40 1800MS
1900MS 41 1900MS
2000MS 42 2000MS
2100MS 43 2100MS
2200MS 44 2200MS
2300MS 45 2300MS
2400MS 46 2400MS
2500MS 47 2500MS
2600MS 48 2600MS
2700MS 49 2700MS
2800MS 50 2800MS
2900MS 51 2900MS
3000MS 52 3000MS
3100MS 53 3100MS
3200MS 54 3200MS
3300MS 55 3300MS
3400MS 56 3400MS
3500MS 57 3500MS
3600MS 58 3600MS
3700MS 59 3700MS
3800MS 60 3800MS
3900MS 61 3900MS
4000MS 62 4000MS
Basic_Tone 1 the same ringback tone is played when the group members are
alerted simultaneously
Intelligent_To 2 the ringback tone of each group member is played when the
ne group members are alerted simultaneously
ALLSM 7 query all the dynamic information related to the short message
ALL 6 send to the VLR, Gn/Gp SGSN, MME, S4 SGSN, and AAA at
the same time
10.63 PROV(Operation)Enumeration
Name Value Description
HPLMN 0 HPLMN
FPLMN 1 FPLMN area
INTERNATIONAL 4 INTERNATIONAL area
HPLMNC 3 HPLMNC area
ALL_PLMN 2 ALL_PLMN area
Error codes can either contain RETCODE = <error code> or ERR, or contain both of them.
3067 ERR3067 Database updated but network update failure for NLR.
Suggestion: Delete GSM/GPRS location information in
previous GSM HLR.
3068 ERR3068 Service conflict with NLR
3069 ERR3069 OP serial number not defined
3090 ERR3090 Overlapping between the new one and the old ones
3092 ERR3092 Unmatched HLR serial number
3094 ERR3094 FTP service has not been provided
3095 ERR3095 FTP User cannot log in
3096 ERR3096 Template could not be empty
3097 ERR3097 HLR serial number not defined
3098 ERR3098 The data to be verified is different from that in the HLR
database
3099 ERR3099 MAP version in NCC configuration could not be higher
than that in system MAP configuration
3100 ERR3100 Database updated but network update failure. And HLR is
re-updating network once
3115 ERR3115 COR in use
3117 ERR3117 FFNAddress not allowed to change
3118 ERR3118 Unknown remote party
3122 ERR3122 Remote party already registered to an initiating subscriber
3125 ERR3125 Service conflict
3126 ERR3126 Initiating subscriber not reachable
3128 ERR3128 Camel parameter values conflict
3129 ERR3129 Parameters of COR for subscriber cannot exceed five
3130 ERR3130 Record already exists
3131 ERR3131 Record not defined
3132 ERR3132 Support for MAPV2
3133 ERR3133 COR not subscribed
3136 ERR3136 The number of defined subscribers reaches the maximum
License capacity of the HLR
3137 ERR3137 The number of OCSI subscribers reaches the maximum
License capacity of the HLR
900003270 ERR900003270 The IMPI associated with the IMSI already supports
EAA,EIA or CAVEAKA
900003271 ERR900003271 The IMPI is not defined
900003275 ERR900003275 The number of IMPIs supporting the TAA authentication
exceeds the upper threshold of License
900003279 ERR900003279 The value to be specified for the IMPI is already used by a
PISI
900003280 ERR900003280 The value to be specified for the PISI is already used by an
IMPI
900003281 ERR900003281 The value to be specified for the IMPI is already used by
an IMPI or PISI
900003282 ERR900003282 The value to be specified for the PISI is already used by a
PISI or IMPI
900003283 ERR900003283 The IMSI already exists
900003284 ERR900003284 The MSISDN already exists
900003285 ERR900003285 The loose route indication of the IMPUs are not the same
900003286 ERR900003286 The IMPU format does not match with IMPU type
900003288 ERR900003288 The IMPI already supports the SIP Digest authentication
scheme
900003289 ERR900003289 The IMPI does not support the SIP Digest authentication
scheme
900003287 ERR900003287 The IMPU is not associated with the specified shared iFC
900003291 ERR900003291 The SiFC template ID does not exist
900003292 ERR900003292 The IMPU already associate with the specified shared iFC
900003295 ERR900003295 The number of shared iFC sets assigned to an IMPU or
PUSI reaches the maximum
900003296 ERR900003296 The one key information of IMPU does not exist
900003298 ERR900003298 The IMPU is not associated with the specified iFC
900003299 ERR900003299 Invalid IMPI format, only IMPI derived from IMSI is
allowed
900003301 ERR900003301 UIMID must exist when CAVEAKAFLG is True
900003302 ERR900003302 The IMPI associated with the IMSI already supports EAA
or EIA
900003303 ERR900003303 The IMPI does not support the Cave AKA authentication
scheme
900003420 ERR900003420 The IMPU or PUSI already associate with the specified
shared iFC
900003422 ERR900003422 The USERTYPE of IMPU or PUSI is different from that in
the database
900003423 ERR900003423 The IMPU or PUSI is not associated with the specified
shared iFC
900003426 ERR900003426 The number of records reaches the maximum
900003427 ERR900003427 The number of wildcard IMPU or PUSI records reaches
the maximum
900003428 ERR900003428 The wildcard IMPU or PUSI overlaps with an existing
wildcard IMPU or PUSI
900003429 ERR900003429 ENDIP must be higher than or equal to BEGINIP for the
address of the NASS nomadism template
900003430 ERR900003430 IP address segments of the NASS nomadism template
conflict
900003476 ERR900003431 The parameter used to specify the NASS nomadism
address is inconsistent with MATCHTYPE in the NASS
nomadism template
900003432 ERR900003432 The number of PSI subscribers exceeds the upper threshold
of License
900003434 ERR900003434 Not allowed to modify MATCHTYPE from IPsegment to
Back or Front
900003435 ERR900003435 Several NASS nomadism templates have identical names.
Please use template IDs to identify the templates
900003440 ERR900003440 Database updated but network update failure because of
system error
900003441 ERR900003441 Database updated but network update failure because of
subscriber data error
900003442 ERR900003442 The barred IMPU could not be found in IMPULIST
900003443 ERR900003443 The IMPI2 is already allocated to another subscription
900003444 ERR900003444 The value to be specified for the IMPI2 is already used by
a PISI
900003445 ERR900003445 The IMPI2 is not defined but have authentication data
900003446 ERR900003446 The IMPI2 is not defined but associated with the IMSI
900003447 ERR900003447 The IMSI2 already exists
900003448 ERR900003448 The MSISDN2 already exists
12 Abbreviations:
CLI Client
OFFICE Office
LOK Lock UI
RECON Reconnect
PRO Process
PAR Parameter
GEN Generative
CB Call Barring
CF Call Forwarding
CW Call Waiting
AS Application Server