Event Reporting

Explained

General

• This document describes some of signaling events commonly happens in the network.

• Signaling events are not necessarily errors in the network , they are generated due to abnormalities detected in the network. These abnormalities can happen due to local, remote or in the intermediate nodes , due to transmission problems, or due to abnormal subscriber behaviour.

• This document is not a replacement of any operation and maintenance document and should be use as a reference only.

• For detailed information see ITU Q.775, Q.774, Q.773, Q.772, Q.771,Q716, Q715, Q714, Q713, Q712, Q711,Q764, TS 29.002 specification documents.

Comandos de AXEPrint Event Reporting SpecificationERESP:ENUM=enum;ERESP:ENUM=all;

Print Event Report

EREPP:ENUM= enum;EREPP:ENUM= all;

Impresos de AXEEVENT REPORTING RESULTENUM HEADER BLOCK DATE TIME

info1 info2 info3 info4 info5 info6

La interpretacion del header y de los datos en los campos infox se encuentra en la Application Information del bloque funcional, en la seccion SUPERVISION DATA

Comandos de AXEReset Event Reporting AlarmEREAR:ENUM=enum;EREAR:ENUM=all;

End Event Report

EREPE:ENUM= enum;EREPE:ENUM= all;

Initiate Event Report

EREPI:ENUM= enum;EREPI:ENUM= all;

Comandos AXE

• C7ERE: CCITT7, Event Reporting, End

• C7ERI: CCITT7, Event Reporting, Initiate

• C7ERP: CCITT7, Event Reporting, Print

• C7ERR: CCITT7, Event Reporting, Reset

• C7ESC: CCITT7, Event Reporting Specification, Change

• C7ESP: CCITT7, Event Reporting Specification, Print

MTP events 0 - 390 C7DP2 User Part Unavailable. MSU received1 C7DP2 Transfer Control received2 C7DR2 MSU discarded due to a routing error3 C7DR2 MSU discarded due to a distribution error4 C7SL2 SL Failure, all reasons5 C7SL2 SL Failure, Abnormal FIBR/BSNR (Forward Indicator Bit

Received / Backward Sequence Number Recieved)6 C7SL2 SL Failure, Excessive Delay of Acknowledgements7 C7SL2 SL Failure, Excessive Error Rate8 C7SL2 SL Failure, Excessive Duration of Congestion18SL Congestion Event Resulting in lossos MSUs Level 119SL Congestion Event Resulting in lossos MSUs Level 220SL Congestion Event Resulting in lossos MSUs Level 3

SCCP event 100 - 145• 100 Routing Failure, No Translation for Addres of such nature• 101 Routing Failure, No Translation for this specific address• 102 Syntax Error detected in SCCP routing part, unknown SCCP message received• 103 Routing Failure, Subsystem error• 104 Routing Failure, Unequipped user• 105 Routing Failure, Network failure• 106 Routing Failure, Network congestion• 107 Routing Failure, reason unqualified• 108 Routing Failure, hop counter violation• 109 Routing Failure, Local subsystem Manually Prohibited• 110 Resource linit reached in SCCP routing control part• 115 Syntax and logical errors detected in SCCP connetion oriented control part• 117 Connection refused (CREF) received• 118 Protocol data unit error (ERR) received• 119 Connection establishment time-out• 120 Resource limit reached in SCCP connection oriented control part• 130 Syntax error detected in SCCP connectionless control part • 132 Resource limit reached in SCCP connectionless control part• 146 Routing failure own global tittle address not defined• 147 routing failure local subsystem out of service.

TCAP Event 200 - 209

• 200 ABORT received • 201 ABORT detected• 202 TCAP REJECT received• 203 TCAP REJECt sent• 204 Protocol error detected• 205 TC-User REject received• 206 TC-User REject sent• 207 Resource limit reached• 208 Operation Timeout Class 1• 209 Operation Timeout Class 3

For GCP the event numbers can be found in AI for GCPH.

• In the Mobile Softswitch Solution the function block GCPH(Gateway Control Protocol Handler) is of special interest. It provides the services to send and receive Gateway Control Protocol (GCP)messages in the MSC Server. Available event numbers for this function block are listed below

• − 1009 MGW DETECTED ERROR • (MGW Detected Error) is reported when a transactionhas been received from a M-MGw with an error descriptor• − 1010 GCP PROTOCOL ERROR • (GCP Protocol Error) is reported when a protocol error is detected during message encoding/decoding or

message validity checking.• − 1011 GCP TRANSACTIONREPLY NOT RECEIVED• (GCP TransactionReply Not Received) is reported whena transaction reply has not been received from the M-

MGw after anumber of retransmissions of the transaction request (specified by an AXE parameter in parameter set GCPHC , depending on the GCPcommands in the transaction request).

• − 1012 GCP RESOURCE LIMITATION• (GCP Resource Limitation) is reported when limitedresources are preventing the processing of GCP messages.• − 1018 GCP TRNX PENDING LIMIT EXCEEDED• (GCP TRNX Pending Limit Exceeded) is reported whenthe number of outgoing pending messages for a

transaction exceedsthe limit set by an AXE parameter in parameter set GCPHC• − 1048 GCP HANDLER DETECTED ERROR • (GCP Handler Detected Error) is reported when a transaction (incoming transaction request or reply to an

outgoing transaction) has timed-out while waiting for either the RP or the GCPH user to respond

SIGTRAN related events• Print the IP related events• EREPP: ENUM=1017&1019&1020;• AI for IP block

• Print the SCTP layer related events• EREPP: ENUM=1014&1015&1016&1046&1047;• AI for SCTP

• Print the M3UA layer related events• EREPP:

NUM=1023&1025&1027&1029&1030&1032&1034&1035&1036&1040&1041&1042&1043&1083&1084;

• AI for M3UADR

M3UA events • Event 1023, M3UA ERROR Message Received• Event 1025, M3UA SCTP Send Failure• Event 1026, M3UA Routing Error (ANSI)• Event 1027, M3UA Routing Error (ITU-T)• Event 1028, M3UA Distribution Error (ANSI)• Event 1029, M3UA Distribution Error (ITU-T)• Event 1030, M3UA Local Congestion• Event 1031, M3UA SCON Message Sent (ANSI)• Event 1032, M3UA SCON Message Sent (ITU-T)• Event 1033, M3UA SCON Message Received (ANSI)• Event 1034, M3UA SCON Message Received (ITU-T)• Event 1035, M3UA DUPU Message Sent (MPT)• Event 1036, M3UA DUPU Message Received (ITU-T)• Event 1037, M3UA Lower Priority Message Discarded (ANSI)• Event 1040, M3UA Message Received for an Unspecified Association Protocol• Event 1041, M3UA Message Syntax Error• Event 1042, M3UA Message Received In An Unacceptable Association State• Event 1043, M3UA Message Received In An Invalid Stream• Event 1083, M3UADR Buffer Congestion• Event 1084, M3UADR Buffer Congestion Ceased

PROTOCOL DISTURBANCE• The protocol disturbance recording function provides the ability to collect detailed

information on protocol disturbances, either for a specified period or continuously. • This information is stored in a buffer and can be printed. It is also possible to print the

recording data for the routes that have the recording function activated. When the receiving buffer is full, an alarm PROTOCOL DISTURBANCE RECORDING FAULT i|s initiated and no further recording takes place for that route.

• The disturbance recording function provides the ability to record protocol disturbances on routes.

• Routes of interest: BICC routes (incoming and outgoing)• PODRI:R=BIA600O,DTYPE=ALL;• PODRI:R=BIA600I,DTYPE=ALL;• The command PODRI initiates the protocol disturbance recording. Up to sixteen routes can

be recorded at the same time. The recording begins immediately if a start date and time are not included in the command. The parameter DTYPE and the results are described in the AI for the route owning block. Example for block BID: DTYPE 1 = Unrecognized Information

• Get the recorded result• PODRE:R=BIA600I;• PODRP;• PODBP:R=route/all; • Protocol Disturbance Supervision Data• PODSI // PODSE // PODSP

Event Number 1

ENUM HEADER BLOCK DATE TIME1 TRANSFER CONTROL RECEIVED C7DP2 051221 182901400

NI DPC OPC SPC CONG3 3384 3944 2640 1

Explanation:• When MSUs are sent to a signalling point over an STP and the link to the destination signalling point

is congested, a TFC is sent from the STP to the originating signalling point with the congestion level. A TFC message sent from ISUP when congestion is indicated in the own signalling point will not be reported. The event is reported per network indicator listing the originating point, destination point and the signalling point where the TFC message is generated. The congestion level is also reported.

Probable Reasons:• Networking Dimensioning , High load on Link due to link restoration after stoppage, Transmission

fault. Etc.

What to do?• Monitor network disturbance C7SNI command can be used . • C7 traffic measurement. • Transmission

Event Number 2

ENUM HEADER BLOCK DATE TIME2 C7DP2 051221 182901400

NI DPC OPC SPC CONG

Explanation:

Probable Reasons:

What to do?

Event Number 3ENUM HEADER BLOCK DATE TIME

3 MSU DISCARD -DISTRIBUTION ERROR C7DR2 051221 180251800

NI DPC OPC SI

3 384 2592 3

Explanation: An MSU is discarded when either an MSU is received for which the destination point code does not exist at the own signalling point, or a non-terminating MSU is received at

a signalling end point

SI (Service Indicator)• = 0 SIGNALLING NETWORK MANAGEMENT MESSAGES• = 1 SIGNALLING NETWORK TESTING AND MAINTENANCE MESSAGES• = 2 SPARE • = 3 SCCP• = 4 TELEPHONE USER PART • = 5 ISDN USER PART• = 6 DATA USER PART (CALL AND CIRCUIT-RELATED MESSAGES) • = 7 DATA USER PART (FACILITY REGISTRATION AND CANCELLATION MESSAGES)• = 8 RESERVED FOR MTP TESTING USER PART • = 9 BROADBAND ISDN USER PART• =10 SATELLITE ISDN USER PART • =11 SIGNAL PROCESSING NETWORK EQUIPMENT USER PART• =12 AAL2 • =13 BICC• =14 GCP

Probable Reasons: Signalling Point Code not defined

What to do? Check with command C7SPP, C7RSP .

Monitor network disturbance C7SNI command can be used

Eventos en MGW

• Lge• Lga