IMS fault analysis

This document describes the process for NOC surveillance to follow when need to escalate a

technical issue or Fault incident

Example of issues that required to be mentioned in the escalation Email is as follows:

- The Trouble Ticket number (describe the status of the TT assigned, in progress, pending)- The office name - Details regarding the issue that is being escalated- The impact of the incident- End to end testing result as below

-

End to end testing

The following is the basic testing and troubleshooting that grantee the service stability.

In order to make the alarm escalation more efficient use below table to escalate the Faults

Bureau ID Bureau Name22 RIYHSS45 JEDHSS44 JEDGWF43 JEDPCSCF42 JEDICSCF41 JEDSCSCF24 RIYGWF23 RIYPCSCF22 RIYICSCF21 RIYSCSCF74 JEDCG36 JEDMGW33 JEDMGCF74 RIYCG35 RIYMGW

34 RIYMGCF

1- SIP Link status changed to error

Alarm description:

With reference to the module number locate the related office description

SIP links been configured to send heartbeat massages (OPTION) to check the connectivity as per the SIP standard.

The Agent due to unknown reasons don’t respond the heartbeat (OPTION)

Alarm troubleshooting and service testing:

Module number 7 (PRONTO, CCM and NORTEL call center) related offices configuration, see below table:

Module number the destination agent the agents related numbers

7 CCM 0811146XXX7 CCM1 081113711XX7 NCC 8001110000

Module number 11(RIYACC, JEDSCSCF and JEDPCSCF) related offices configuration, see below table:

Module Number The destination agent The agent related numbers

11 RIYACC 800111122211 JEDSCSCF

JEDPCSCFJEDSCSCF and JEDPCSCF test, force the terminal to register in JEDIMS then make a test call?To force a terminal to registered in JED IMS (configure Jed SBC IP in SoftDA)

Or call JED related number that starts with 081111XXXXX

Module number 12 (RIYSS, JEDSS and PRONTO) related offices configuration, see below table:

Module Number The destination agent The agent related numbers

12 PRONTO 081113700XX12 RIYSS Make sure that the

terminal registered in RIYIMS then call any International number

12 JEDSS N/A

Module number 8 (RIYSCSCF, RIYICSCF, RIYPCSCF and NGCC) related offices configuration, see below table:

Module Number The destination agent The agent related numbers

8 NGCC 081112233448 RIYSCSCF

RIYICSCFPCSCF

force the terminal SoftDA to register in RIYIMS then make end to end test calls

Make end to end test calls.If the test call gets drop immediately escalate it to support team

The interconnect alarms

-MTP3 office inaccessible -MTP3 office inaccessible unavailable -M3UA office inaccessible

Alarm description:

The OLOs (STC, ZAIN, MOBILY and PRAVO) are connected to the IMS through the SGW (MGCF in riy and jed)

Alarm troubleshooting and service testing:

With reference to the office name, ID and the trunk group ID find the configured numbers as below:

Office ID OFFICE NAME LOCATION Truck groupOG -- IC

RELATED No.

71 RIYHUTT_1 RIYADH 2&1 1201,1468,1469,1470,1485,1487,1488,1489,1526,1724,905,980,

1213,1287,1410 1411,1438,14722840,

1474,1495,187473 RIYMAT1_1 RIYADH 3&4 1209,1210,1216

,1276,1277,1278,661,665,6661,700

,800,989,99975 RIYTSR1-1 RIYADH 6&7 053,055,050

051(bravo)83 RIYZAINMSCS RIYADH 15&16 05953 KHBTSD1_1 DAMMAM 31&30 3332,3346,3347

360,361,3816,3818

,4629,463,464,46552 KHBDAM4_1 DAMMAM 29&28 3348,3349,3350,

3378,3815,38433844,3878,3880

51 KHBKHB3_1 DAMMAM 27&26 3331,3563,35643833,3834,3835

3898,389971 JEDMUJA_1 JEDDAH 2&1 2229,2261,2264

2265,2270,22712272,2283,26772678,2679,26932221,2223,22512252,2256,2257,

90773 JEDROW3_1 JEDDAH 4&3 2211,2622,2691

4326,43$7,75,77917792,800,997,998

999,012,01475 JEDTSJ1_2 JEDDAH 6&5 055,053,05083 JEDZAIN JEDDAH 15&16 05993 JEDMOBILY_TSCS_2 JEDDAH 11&12 054,05693 RIYMOBILY_TSC_S_1 RIYADH 11&12 054,056

Physical link related alarm (IPI board)

NE Type: (ICSCF, GWF and HSS) related offices configuration, see below table:

NE Type Destination NE

Related service

ICSCF172.26.32.50

HSS172.26.32.110

Registration And calls

Force the terminal to register in riy IMS and then make a test to GO number, if the IP 172.27.32.50 force the terminal to register to JEDIMS

GWF172.26.32.111

OCS172.16.64.65

Billing Force the terminal to

register in riy IMS and then make a test to GO numberif the IP 172.17.64.65 register in JEDIMS and then make a test to GO number

SCSCF172.26.32.10

HSS172.26.32.110

Billing Force the terminal to register in riy IMS and then make a test to GO numberif the IP 172.27.32.10 force the terminal to register to JEDIMS

This alarm is service impacting immediate action should be taken.

When restart the OMC server for any of IMS elementsThis alarm is not service impact