Basic Troubleshooting

and Maintenance for CS

core

Pre-requisite
Basic

knowledge of R99 networking

(GSM) structure.

Terms

H.248 link - link between the MSC-Server and the Media Gateway
with the use of SCTP.

Media Gateway- handles the media, or bearer, interface. It

converts media from the format used in one network to the format

required in another network.

MGC Another name for MSC Server.
MSC Server Control Layer of the MSC in the R4 network to realize
mobility management, call control and media gateway control.
SCTP (Stream Control Transmission Protocol) a SigTran transport
protocol used for the H.248 link. A transport protocol which carries
SS7 application messages over IP with high-reliability.

R4 Networking

MSC is divided into two network elements which

handles corresponding layers
MSC Server handles the control layer (signaling)
Media Gateway handles the bearer layer (voice,
data and other media stream). It also has the
function of a signaling gateway (STP).

R5 Networking
Inherit

all R4 features
Introduce IP multimedia subsystem
Introduce HSDPA
Iu Interface ( Interface between MSS
and RNC ) can be IP based or ATM
based.

Summary:
Introduction

of R4 and R5 evolution
Our emphasis on the CS Core training
is the R4 networking.

Signaling and SS7

Terms

ACM a SS7 (ISUP) signaling message which indicates that the IAM from the originating
switch has reached the destination switch and was properly analyzed. The latter then
sends back a ring back tone or play an announcement.
ANM a SS7 (ISUP) signaling message which indicates that the destination switch of the
called party has answered the requested call.
BICC - (Bearer Independent Call Control) developed based on the ISUP protocol. The
session and bearer are separated through the BICC protocol; thus the call service function
(CSF) and bearer control function (BCF) are independent. Voice circuits are established
between MSS and does not require the function of a MGW.
CAP a signaling protocol used in GSM between a Service Switching Point (MSC) and a
Service Control Point ( IN, HLR etc.). Used for prepaid, special services etc.
Global Title (GT) an international title given to a network element for the purpose of
interworking with other network elements with or without direct signaling interconnection.
IAM a SS7 (ISUP) signaling message which indicates an initial transaction being queried
by originating switch to the destination switch. The message contains the A and B
number, number of trunk circuit that is initially used and other information beyond the
scope of this explanation.
ISUP (ISDN User Part) a SS7 protocol used in the establishment and tear down of voice
and data calls between two switches.

Link logical interconnection between two network elements where signaling

messages are sent and received.
Link Set - a set of signaling links between two network elements.
M2PA (MTP level 2 peer to peer adaptation) a SigTran protocol to realize the SS7
function of MTP2 over IP. Similar to M2UA, the difference is that both NE associated
with this type of protocol requires a signaling point code. Used between STPs in our
network
M2UA - (MTP level 2 user adaptation layer) a SigTran protocol to realize the SS7
function of MTP2 over IP. Used commonly when interworking with BSCs.
M3UA - (MTP level 3 user adaptation layer) a Sigtran protocol to realize the SS7
function of MTP3 over IP. Used between MSS to MSS and MSS to STP connection in our
network.
MAP (Mobile Application Part) a protocol used in GSM for subscribers services,
profiles, mobility management and call control.
MSISDN (Mobile Station Integrated Services Digital Network) the mobile subscribers
directory number. The number that is known to a common subscriber.
MSRN (Mobile Station Roaming Number) is a temporary number allocated to a
called subscriber by its serving VLR/MSC.
Point Code an identifier of a network element in a SS7 network.
REL an SS7 (ISUP) message sent by the called switch to the originating switch to
indicate that the call has been released.
SCCP (Signaling Connection Control Part) The SCCP provides additional network layer
functions to provide transfer of noncircuit-related (NCR) signaling information, application
management procedures and alternative and more flexible methods of routing.

Signaling exchange of call components between network elements required to

provide and maintain service.
STP (Signaling Transfer Part) a network element which receives and routes signaling
messages towards the proper destination.

Current DMPI Architecture

FINAL SIGNALING NETWORK STRUCTURE PHASE 8A

SGSN

INSCP

SMSC

RCP 1

AIP

USSD GEMPLUS RCP

5/6

STARHOM
E

HLR

SG3/4

VSIMIN MSC

SG1/2

GMSC

NLZ MSC

SLZ MSC

NCR MSC

Call Flow
Mobile

to Mobile Call
Mobile to Mobile Call (PRBT sub)
Mobile (prepaid) to Mobile call
Mobile to PSTN
PSTN to Mobile
SMS MO and MT

Summary
Introduction

to SS7 and Signaling

How SS7 is applied in our current
network
How SS7 messages are used in a call
flow

Introduction to LMT tool and basic command

handling

Steps for using trace message

After logged on the desired MSS, click on the maintenance tab at the
lower left of the window.
Select what type of trace is to be conducted. Most of the time, User
message trace is selected. Double click on User Message trace, a pop
up window should appear on the center of the screen.
On the pop up window, Select MSISDN number for User Input box (if
tracing in VMSC) and type the mobile number being traced in the
MSISDN box. For the Combination, choose select all meaning all
interfaces that were used by the call flow will be traced.
On the pop up window, Select PSTN number for User Input box (if
tracing in TMSC) and type the number sent by the originating
MSS in the IAM message, being traced in the PSTN box. For the
Combination, choose select all meaning all interfaces that were used
by the call flow will be traced.

Most encountered problems

Sun

cannot call landline numbers

Suntel cannot call landline numbers

Procedures

Trace first the caller of the roaming VMSC, then call the unreachable
landline number.
Note in the trace message, blue lines indicate messages being sent by
the switch being traced while black lines indicate replies of interacting
NEs.
Check in the trace message for the BICC_TYPE_IAM message.

All calls of SUN to other PSTN numbers are routed towards TMSC1H and 2H
while TMSC1H only for Suntel.
If BICC_TYPE_IAM message is present, And the called and the calling number
is in the correct format, the next step is to trace in TMSCs.
If the BICC_TYPE_IAM message is not present and the DISCONNECT message
is present in the trace rather, then the problem is in that VMSC.
In the MML command line, run the command LST CNACLD, check for the
longest prefix defined in the VMSC that matches the called number (if the
caller is SUN, check for DN SET=0, if Suntel check for DN SET=88)
If there is no call prefix that does not match the called number, even a single
digit, then definition should be done by NACM.
If there is a call prefix that matches the called number but has wrong
parameters, then modification should be done by NACM.

TMSC trace
BICC_TYPE_IAM message should be sent by the VMSC
If IAM message is sent to our switch counterpart which has direct
interconnection to Huawei Transit MSS (e.g. GCCT7, BNLN7, BALS7, GLOB,
IGF1, IGF2, IGF3, ETP07, BYNT7), and ACM is not received and REL message is
received rather.
- Check in the IAM message if TMSS can send the correct A and B number
format.
- If correct, then the problem is in our switch counterpart.
- If incorrect, then modification should be done by NACM.

If IAM message is sent to our Alcatel Gateways and ACM is not received and
REL message is received rather.
- Check in the IAM message if TMSS can send the correct A and B number
format.
- If correct, then the problem should be endorsed to Core OPTI group since
they are capable in tracing messages in Alcatel gateways.

Immediate Data Modification

Rerouting of Traffic
Prerequisite the secondary switch, where the traffic is to be rerouted, allows,
can process and route the call to the same operator, with their Gateway
switch
Steps:
1. Backup existing data. Run LST CNACLD
2. Check for the route of the original and the secondary route to be used. Run
LST RTANA.
3. Modify the route of the call prefixes. Run MOD CNACLD.

Signaling Link Reallocation for BSCs

Terms

CIC (Circuit Identity Code) a SS7 code used to identify a unique voice circuit
between two offices
Integer Interface ID a identifier parameter of the M2UA link when
interworking with MSS and MGW.
SLC (Signaling link Code) a SS7 code used to identify a unique signaling link
between two offices.
TID (Terminal Circuit ID) unique circuit ID that identifies a voice circuit in a
MGW
Office - a network element which has voice circuits.

Steps

Identify which CIC will cater the reallocated signaling link. The CIC that will
cater the reallocated signaling link should be the same in MSC and BSC
In MSS, run LST OFCTKC put in the office direction name parameter the office
name of the NE that needs reallocation. Check the TID of the corresponding
CIC.
In MGW run LST TDMTID, put the TID value in the TID(DEC) parameter, it will
display the hardware position of the device (Frame no., Slot no., port no.)
Go to the device panel and search for the position given by the above
command. Get the board no.
After getting the board no and the port no, run DSP CFG to check the existing
configuration of the desired link to be reallocated.
To modify the link run RMV MTP2LNK then ADD MTP2LNK, obtain all
parameters the same except for the board no and port no.
After modification done check the status of the link in MSS. Run DSP N7LNK,
the status should be healthy and in use.

Trunk Test Call for BSCs

Needs

Prior to commercialization of additional A interface circuits,

(E1 circuits between MSC and BSC) it should have excellent
voice quality
To test E1s with possible echo and crosstalk

Procedures

Get the CICs of the E1 circuits to be tested.

Check for the location of the A and B number to be used as
test numbers. Both of them should be catered by the same
BSC where the circuits are to be tested.****
Decide how many test calls should be made per E1 ( 2 test
calls are being done most of the time )
Run the command ADD TKTEST
Open a user message trace and enter the MSISDN of the A or
B number. A number should dial 139*(b number w/o 0) Check
the message CC_Refresh_Test_Task, the CIC of the test call
made should be displayed.
Continue the test call until all E1s are tested.