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
22
45
44
43
42
41
24
23
22
21
74
36
33
74
35

Bureau Name
RIYHSS
JEDHSS
JEDGWF
JEDPCSCF
JEDICSCF
JEDSCSCF
RIYGWF
RIYPCSCF
RIYICSCF
RIYSCSCF
JEDCG
JEDMGW
JEDMGCF
RIYCG
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 dont 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

7
7
7

CCM
CCM1
NCC

the agents related

numbers
0811146XXX
081113711XX
8001110000

Module number 11(RIYACC, JEDSCSCF and JEDPCSCF) related offices

configuration, see below table:

Module Number

The destination agent

11
11

RIYACC
JEDSCSCF
JEDPCSCF

The agent related

numbers
8001111222
JEDSCSCF 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

12
12

PRONTO
RIYSS

12

JEDSS

The agent related

numbers
081113700XX
Make sure that the
terminal registered in
RIYIMS then call any
International number
N/A

Module number 8 (RIYSCSCF, RIYICSCF, RIYPCSCF and NGCC) related

offices configuration, see below table:
Module Number

The destination agent

8
8

NGCC
RIYSCSCF
RIYICSCF
PCSCF

The agent related

numbers
08111223344
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 group

OG -- IC

71

RIYHUTT_1

RIYADH

2&1

73

RIYMAT1_1

RIYADH

3&4

75

RIYTSR1-1

RIYADH

6&7

83
53

RIYZAINMSCS
KHBTSD1_1

RIYADH
DAMMAM

15&16
31&30

RELATED No.
1201,1468,1469,
1470,1485,1487,
1488,1489,1526,
1724,905,980,
1213,1287,1410
1411,1438,14722840,
1474,1495,1874
1209,1210,1216
,1276,1277,1278
,661,665,6661,700
,800,989,999
053,055,050
051(bravo)
059
3332,3346,3347
360,361,3816,3818

52

KHBDAM4_1

DAMMAM

29&28

51

KHBKHB3_1

DAMMAM

27&26

71

JEDMUJA_1

JEDDAH

2&1

73

JEDROW3_1

JEDDAH

4&3

75
83
93
93

JEDTSJ1_2
JEDZAIN
JEDMOBILY_TSCS_2
RIYMOBILY_TSC_S_1

JEDDAH
JEDDAH
JEDDAH
RIYADH

6&5
15&16
11&12
11&12

,4629,463,464,465
3348,3349,3350,
3378,3815,3843
3844,3878,3880
3331,3563,3564
3833,3834,3835
3898,3899
2229,2261,2264
2265,2270,2271
2272,2283,2677
2678,2679,2693
2221,2223,2251
2252,2256,2257,
907
2211,2622,2691
4326,43$7,75,7791
7792,800,997,998
999,012,014
055,053,050
059
054,056
054,056

Physical link related alarm (IPI board)

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

NE Type
ICSCF
172.26.32.50

Destination
NE
HSS
172.26.32.110

GWF
OCS
172.26.32.111 172.16.64.65

Related
service
Registration
And calls

Billing

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
Force the
terminal to
register in riy

SCSCF
172.26.32.10

HSS
Billing
172.26.32.110

IMS and then

make a test to
GO number
if the IP
172.17.64.65
register in
JEDIMS and
then make a
test to GO
number
Force the
terminal to
register in riy
IMS and then
make a test to
GO number
if 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 elements

This alarm is not service impact