MAP Protocol Error codes and Supplementary Service codes

-

MAP Protocol Error codes and Supple Service codes


 MAP Protocol Error Codes

 Generic errors

    34 System failure

    35 Data Missing

    36 Unexpected Data Value

    21 Facility Not Supported

    28 Incompatible Terminal

    51 Resource Limitation

 Identification and Numbering Errors

    01 Unknown Subscriber

    144 Number Changed

    03 Unknown MSC

    05 Unidentified Subscriber

    07 Unknown Equipment

 Subscription Errors

    08 Roaming Not Allowed

    09 Illegal Subscriber

    12 Illegal Equipment

    10 Bearer Service Not Provisioned

    11 Teleservice Not Provisioned

Handover Errors

    25 No Handover Number Available

    26 Subsequent Handover Failure

    42 Target Cell Outside GroupCall Area

    Operation and Maintenance Errors

    40 tracingBufferFull

Call Handling Errors

    39 No Roaming Number Available

    27 Absent Subscriber

    45 Busy Subscriber

    46 No Subscriber Reply

    13 Call Barred

    14 Forwarding Violation

    47 Forwarding Failed

    15 CUG Reject

    48 OR Not Allowed

Any Time Interrogation Errors

    49 ATI Not Allowed

Any Time Information Handling Errors

    60 ATSI Not Allowed

    61 ATM Not Allowed

    62 Information Not Available

Supplementary Service Errors

    16 Illegal SS Operation

    17 SS Error Status

    18 SS Not Available

    19 SS Subscription Violation

    20 SS Incompatibility

    71 Unknown Alphabet

    72 USSD Busy

    37 PW Registration Failure

    38 Negative PW Check

    43 Number of PW Attempts Violation

    29 ShortTerm Denial

    30 LongTerm Denial

Short Message Service Errors

    31 Subscriber Busy For MT SMS

    32 SM Delivery Failure

    33 Message Waiting List Full

    06 Absent Subscriber for SM

Group Call errors

    50 No GroupCall Number Available

    22 Ongoing GroupCall

Location Service Errors

    52 Unauthorized Requesting Network

    53 Unauthorized LCS Client

    54 Position Method Failure

    58 Unknown or Unreachable LCS Client

    59 MM Event Not Supported

supplServiceCode

    00 All supplementary services

    10 All line identification services

    11 Calling number identification presentation

    12 Calling number identification restriction

    13 Connected number identification presentation

    14 Connected number identification restriction

    20 All call forwarding

    21 Call forwarding unconditional

    28 All conditional Call Forwarding

    29 Call forwarding on mobile subscriber busy

    2A Call forwarding on no reply

    2B Call forwarding on subscriber not reachable

    30 All call offering services

    31 Call transfer

    40 All call completion services

    41 Call waiting

    42 Call hold

    43 Completion of calls to busy subscribers

    50 All multi party services

    51 Multi party service

    60 All community of interest services

    61 Closed user groups

    70 All charging supplement services

    71 Advice of charge (charging)

    72 Advice of charge (information)

    80 All additional info transfer services

    81 User to user signalling

    90 All call barring

    91 All Barring of outgoing Call Services

    92 Barring of all outgoing calls

    93 Barring of all outgoing international calls

    94 Barring of all OG international except HPMN

    99 All Barring of incoming Call Services

    9A Barring of all incoming calls

    9B Barring of all IC calls when outside HPMN

    FF USSD Message

Error CodeContextSeverity LevelValidation Description
30

SS

Severe

Mandatory item Supplementary Service Code missing within group.
31
SS
Severe
Mandatory item Action Code missing within group.
32
SS
Warning
Item Supplementary Service Parameters present when Supplementary Service is not for call forward registration.
33
SS
Warning
Item Supplementary Service Parameters not present when Supplementary Service is for call forward registration.
34
MOC
Warning
Item Supplementary Service Parameters present when Supplementary Service is not for ECT invocation.
35
MOC
Warning
Item Supplementary Service Parameters not present when Supplementary Service is for ECT invocation.
36
SS
Severe
Item Charging Timestamp missing within group.
37
MOC,MTC
Warning
Mandatory item Supplementary Service Code missing within group.
38
MOC,MTC
Warning
Mandatory item Action Code missing within group.
100
MOC,MTC
Warning
Non transferable Supplementary Service Code and Action Code combination present within group.

Comments

Post a Comment

Popular posts from this blog

LTE attach Procedure

-
In this series of Log Analysis, we are explaining about the LTE attach procedure, below is the detailed summary : Step Direction Channel Message 1 UE <---- NW BCCH -> BCH , No MAC Header , RLC TM, No PDCP MIB [0xB0C1] LTE MIB Message Log Packet Version = 2 Physical cell ID = 378 FREQ = 1276 SFN = 320 Number of TX Antennas = 2 DL Bandwidth = 5 MHz (25) Step Direction Channel Message 2 UE <---- NW BCCH -> DL SCH , No MAC Header , RLC TM, No PDCP SIBs 0xB0C0  LTE RRC OTA Packet  --  BCCH_DL_SCH / System   Information value BCCH-DL-SCH-Message :: { message c1 : systemInformation :       { criticalExtensions systemInformation-r8 :           { sib-TypeAndInfo             {   sib2 :        ...
Read more

Cause Codes From Network

-
C AUSE CODES   FROM   NETWORK   Reference : 3GPP TS 24.008 10.5.3.6 and Annex G. Cause  No  1  :    “unassigned (unallocated) number” (UMTS specific cause values for call control) This cause indicates that the destination requested by the mobile station cannot be   reached  because, although the number is in a valid format, it is not currently assigned (allocated). Cause value = 2  : IMSI unknown in HLR (Causes related to MS identification) This cause is sent to the MS if the MS is not known (registered) in the HLR. This cause code  does not affect operation of the GPRS service, although is may be used by a GMM procedure. Cause value = 3  :   Illegal MS (Causes related to MS identification)   This cause is sent to the MS when the network refuses service to the MS either because an  identity of the MS is not acceptable to the network or because the MS does not pass the authenticat...
Read more

MCC-MNC Codes for India

-
S. No. MCC-MNC OPERATOR Circle 1 INA 00 404-00 SISTEMA SHYAM Rajasthan 2 INA 01 404-01 Vodafone Haryana 3 INA 02 404-02 Airtel Punjab 4 INA 03 404-03 Airtel Himachal Pradesh 5 INA 04 404-04 Idea Delhi 6 INA 05 404-05 Vodafone Gujarat 7 INA 07 404-07 Idea Andhra Pradesh 8 INA 09 404-09 Reliance Telecom Assam 9 INA 10 404-10 Airtel Delhi 10 INA 11 404-11 Vodafone Delhi 11 INA 12 404-12 Idea Haryana 12 INA 13 404-13 Vodafone Andhra Pradesh 13 INA 14 404-14 SPICE Punjab 14 INA 15 404-15 Vodafone Uttar Pradesh (East) 15 INA 16 404-16 Airtel North East 16 INA 17 404-17 Aircel West Bengal 17 INA 18 404-18 Reliance Telecom Himachal Pradesh 18 INA 19 404-19 IDEA Kerala 19 INA 20 404-20 Vodafone Mumbai 20 INA 21 404-21 LOOP Mumbai 21 INA 22 404-22 IDEA Maharashtra 22 INA 24 404-24 IDEA Gujarat 23 INA 25 404-25 Aircel Bihar 24 INA 27 404-27 Vodafone Maharashtra 25 INA 28 404-28 Aircel Orissa 26 INA 29 404-29 Aircel Assam 27 INA 30 404-30 Vodafone Kolkata 28 INA 31...
Read more

WCDMA Attach Procedure

-
WCDMA Attach Procedure WCDMA initial attach to the network, step by step messages from Network <=> MS 1. [0x412F/004/007] OTA LOG  BCCH-BCH DL/Complete SIB List [0x412F] WCDMA Signaling Messages Channel Type = DL_BCCH_BCH , Radio Bearer ID = 40, Uarfcn = 10807, Psc = 404, Message Length = 31 Interpreted PDU: value BCCH-BCH-Message ::= { message { sfn-Prime 106, payload completeSIB-List : { sib-Type systemInformationBlockType1, sib-Data-variable '11100110 00110011 11100001 00001000 010 ...'B } 2. [0x412F/254/001] OTA LOG BCCH-BCH DL/System Information Block Type 1 [0x412F] WCDMA Signaling Messages Channel Type = Complete SIB (254)  , Radio Bearer ID = 40, Uarfcn = N/A, Psc = N/A, Message Length = 20 Interpreted PDU: value SysInfoType1 ::= { cn-CommonGSM-MAP-NAS-SysInfo '8CF8'H, cn-DomainSysInfoList { { cn-DomainIdentity cs-domain, cn-Type gsm-MAP : '0A01'H, cn-DRX-CycleLengthCoeff 6 }, ...
Read more

GSM Device and Network Error Codes

-
GSM Device  and Network Error Codes     ERROR's (GSM Device  related codes)    ERROR: 0 Phone failure    ERROR: 1 No connection to phone    ERROR: 2 Phone adapter link reserved    ERROR: 3 Operation not allowed    ERROR: 4 Operation not supported    ERROR: 5 PH_SIM PIN required    ERROR: 6 PH_FSIM PIN required    ERROR: 7 PH_FSIM PUK required    ERROR: 10 SIM not inserted    ERROR: 11 SIM PIN required    ERROR: 12 SIM PUK required    ERROR: 13 SIM failure    ERROR: 14 SIM busy    ERROR: 15 SIM wrong    ERROR: 16 Incorrect password    ERROR: 17 SIM PIN2 required    ERROR: 18 SIM PUK2 required    ERROR: 20 Memory full    ERROR: 21 Invalid index    ERROR: 22 Not found    ERROR: 23 Memory failure ...
Read more

GSM Attach Procedure

-
GSM Attach Procedure GSM initial attach to the network, step by step messages from Network <=> MS 1. [0x5B2F/002/129] | OTA LOG | 07:21:52.178 | GSM DSDS RR Signaling Message Channel Type = RACH (2) Direction = Uplink Message Type = Open Loop CMD ACK (129) Message Length in bytes = 24 L3 Message in Hex:   17 49 06 1B 3E 46 04 F4 94 00 2A C8 00 0A 14 65 4A B8 00 00 81 00 05 9B Decoded Message: prot_disc = 7 (0x7) (GSM_EPS_MOB_MANAGEMENT) msg_type = 73 (0x49) 2.0 0x5B2F/002/129] | OTA LOG | 07:21:52.178 | GSM DSDS RR Signaling Message Channel Type = BCCH (1) Direction = Uplink Message Type = System Information Type 9 (4) Message Length in bytes = 19 L3 Message in Hex:   12 06 15 AB EB 7E 00 00 00 00 00 00 00 00 00 00 00 00 00 Decoded Message: prot_disc = 6 (0x6) (GSM_RR_MANAGEMENT) msg_type = 21 (0x15) MEASUREMENT_REPORT BA_USED = 1 (0x1) DTX_USED = 0 (0x0) RXLEV_FULL_SERVING_CELL = 43 (0x2b) 3G_BA_USED = 1 (0x1) ME...
Read more

LTE IMS MO Call

-
LTE IMS MO Call 0x1832  IMS Registration Version = 1 Registration Type = Initial Call Id Length = 59 Call Id = 3512047382_2335928920@2405:204:6c09:13b:ed63:680a:633:8ab7 Request Uri Length = 38 Request Uri = sip:ims.mnc861.mcc405.3gppnetwork.org To Length = 56 To = <sip:405861002372445@ims.mnc861.mcc405.3gppnetwork.org> Result = OK 0x156E  IMS SIP Message  --  IMS_SIP_REGISTER/INFORMAL_RESPONSE Version = 1 Direction = UE_TO_NETWORK SDP Presence = 0 SIP Call ID Length = 59 SIP Message Length = 2506 SIP Message Logged Bytes = 2507 Message ID = IMS_SIP_REGISTER Response Code = INFORMAL_RESPONSE (0) CM Call ID = 255 SIP Call ID = 3512047382_2335928920@2405:204:6c09:13b:ed63:680a:633:8ab7 Sip Message = REGISTER  sip:ims.mnc861.mcc405.3gppnetwork.org SIP/2.0 0x156E   IMS SIP Message  --  IMS_SIP_REGISTER/OK Version = 1 Direction = NETWORK_TO_UE SDP Presence = 0 SIP Call ID Length = 59 ...
Read more

SIP Response Codes

-
List of SIP response codes The Session Initiation Protocol (SIP) is a signalling protocol used for controlling communication sessions such as Voice over IP telephone calls. SIP is based around request/response transactions, in a similar manner to the Hypertext Transfer Protocol (HTTP). Each transaction consists of a SIP request (which will be one of several request methods), and at least one response. Contents 11xx—Provisional Responses 22xx—Successful Responses 33xx—Redirection Responses 44xx—Client Failure Responses 55xx—Server Failure Responses 66xx—Global Failure Responses 1xx—Provisional Responses 100 Trying Extended search being performed may take a significant time so a forking proxy must send a 100 Trying response. 180 Ringing Destination user agent received INVITE, and is alerting user of call. 181 Call is Being Forwarded Servers can optionally send this response to indicate a call is being forwarded. 182 Queued Indicates that the destination was temporarily unavai...
Read more