-1-

CAMEL Call scenario

Below are the messages between blocks for CAMEL origination call:

First: let us assume we have MO CAMEL Call in Etisalat network for Local subscriber:
From below analysis we need to (routing of Call and Construct IDP message)
This also will include internal routing between blocks till SSF
Subscriber with CAMEL profile make location update in VLR
As this subscriber is local subscriber (60203), from MSNAN block (MGISP) we check this parameter
(INOPER-2)
These 2 parameters input to MIN block to get the route, below the print out got from MSC

-2<mgisp: IMSIS=60203;
MT IMSI NUMBER SERIES ANALYSIS DATA
OPERATING TABLE
IMSIS

60203

5-2011

NA ANRES
4 OBA-30
BO-17
OWNMS
NATMS
PLMN-0
STALL
MAPVER-2
INOPER-2
CBA-55
CBAZ-0
CAMEL-3
ADD

<exrop:dety=min;
ROUTE DATA
R
ROUTE PARAMETERS
MINORIG DETY=MIN
FNC=9
RO=0
CO=0
MIS5=1

MIS1=1

END

MIS2=2

BO=25

MSNAN block
INOPER-2
CAMEL-3
MAP-2

MTV block
Subscriber with
CAMEL information

MIN block
MIS2=2
FNC=9

From above printout we can got MIS5=1-----------> IST (IN Service Trigger)
MIS1=1 -------- tell us if we will use new BO, CO and RO (here mean we will use new BO 25)
Here the MTA block will seize TRAM (Transit application module) by sending OIP IAM message
using APC link , MO APC link connect MOIPHO to TRACO
<arldp:apclnk=moc;
APPLICATION PROTOCOL CARRIER LINK DATA
APCLNK SYS SMAX STATE SES
PID LEVEL EPO EPSTATE
MOC N MAX ACT 5596 30 BAS MOIPHO ACT
TRAMOI ACT
END

In the block TRACO here the analysis start using new BO got (BO=25) we can find RC (routing case)
from B Number analysis if we assumed the subscriber dial 011xxxxxxx, the new B number will be IST+
number series (1011xxxxxxx)
And from RC we can find route to SSF AM

<anbsp:b=25;
B-NUMBER ANALYSIS DATA
OPERATING AREA
B-NUMBER
MISCELL F/N ROUTE
CHARGE L
A
25-10
RC=25 CC=1 L=3-15
D=4-0

-3TRD=150
<anrsp:rc=25;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR
ROUTING
SP DATA
25 YES ISTI-0 P01=1 ES=114
ISTI-1 P02=1 R=SSFDJ1O MM1 COT EST SI ESS ESR
0
0 1
0
BNT RN SPR OLI OLI2
00 0
ISC FCP D
0
END

<exrop:r=SSFDJ1O;
ROUTE DATA
R
ROUTE PARAMETERS
SSFDJ1O DETY=TRACO FNC=3
R=SSFDJ1I
APCLNK=SSFTRAM
END

Here from EXROP we can find the APC link where OIP IAM sent from TRACO to SHCM (Service
Switching call and connection Manager) where the IDP is constructed in triggering tables.
<arldp:apclnk=ssftram;
APPLICATION PROTOCOL CARRIER LINK DATA
APCLNK SYS SMAX
SSFTRAM N MAX

STATE SES
ACT 5806

PID LEVEL EPO EPSTATE

30
BAS TRACO ACT
SHCM ACT

END

Now in SSF we can print the route parameter data that will be used later.

<shrsp:osr= OUTGOINGROUTE1;
SERVICE SWITCHING NODE SSF ROUTE DATA
OPERATING AREA
OSR
RINDEX APC
OUTGOINGROUTE1
2
SSFTRAM
PAR VAL SCAP DIST
ASI
0 0
0
BO
100 1
0
CBI
0 0
0
CHP
0 0
0
CO
0 0
0

-4EA
0 0
INS
0 0
ISA
0 0
ISB
0 0
MST
0 0
OCO
2 0
OTA
0 0
PLMN 0 0
PR
0 0
RCP
0 0
RDC
0 0
RO
0 0
ST
0 0

0
0
0
0
0
0
0
0
0
0
0
0
0

END

Now we start in triggering table (to construct IDP and route this IDP)

1- SHIST
<dbtsp:tab=shIST,ist=1;
DATABASE TABLE
BLOCK TAB
SHTD4 SHIST
IST
1

TABLE

IST=
1

WRAPPED
YES

BCSMTYP DISCONI MIDCALI NUMDIG REANSI SUSPNDI SSFTYPE

ORIG
3
I
TNSID
1

SHIST
BCSMTYP
DISCONI
IST
MIDCALI
NUMDIG
REANSI
SSFTYPE
SUSPNDI
TNSID

END
TNSID=1

IST: IN Service trigger (from MIN block)

BCSMTYPE: basic call state model type (Originating)
NUMDIG: number of digits received before TD2 trigger
SSFTYPE: Initiation
TNSID: trigger network signaling ID ------ will trigger SHTNS table

2- SHTNS

SHTNS
TNSID=1

TNSID
BRISRID
BROSRID
CLIDTYP
DRISRID
DROSRID
SHTD4

ISCC
OSBCC
OSDCC
SCFIDTY
ROUTTYP

<dbtsp:tab=shtns,tnsid=1;
DATABASE TABLE
BLOCK TAB
SHTD4 SHTNS

TABLE

WRAPPED
YES

TNSID
BRISRID BROSRID BSIND CDPNPAD CHOIIN CHOIOUT CLIDATA CLIDLTH
1
1
2
0
0
YES
YES
1
CLIDST CLIDTYP DRISRID DROSRID ISCC OINTA OSBCC OSDCC

-51
1
2
8
YES
ROUTTYP SCFIDLT SCFIDST SCFIDTY SHREQ
DR
0
S

END
DRISRID: direct route incoming SSF route ID ----- 1
DROSRID: direct route outgoing SSF route ID ------2
ROUTTYP: route type ----- Direct

Equal to RINDEX in
SHRSP

Note: To complete number analysis for (Continue message from CCN) The BO can be got from SHRSP:OSR=all; and match the
record where the Route Index = DRISRID

SHTNS ----- hold the default data for SSF routes and charging cases
SHTNS & SHIST ----- associate the network and charging data with IN service

Diagram of triggering tables

SHISTTOTDP
IST
TDPID
TDPNO
TDPID

SHTDP
CLISTID
CSK
CTINSID
DIAGTYP
PROTI
TDPSID
TINSID
TLISTID
TDPID

SHEXLIST
CRIT
REQ
PROTI
ELISTID EXTTYPE
EXTNO
ELISTID

SHEXTRANS

EXTTYPE

AMTAG
DEF
DIR
PROTI
EXTTYPE

SHTDPS

TDPSID

CCTR
CG
CL
CESS
CGENC
CTMP
TDPSID
EVTYPE
IPCAP
LIF2
USI

SFI
SHR
SHS
SK
TEI
TRIG
TSDID
TSOID
LIF1

SHINS
ACGN
CGCAT GNS
RO
BCAP
CPN
HLC
RDI
TINSID BGVNS CUGCI NSID SII
CAUSE
FGVNS LN
CUGIC
FWCI
OCDN
CDN
GDS
RGN

SHTSD
TSDID

TSOID

TSDID
DSTNAME
DGLT
SNMADD
DPC
FDSTADR
GTNAPI

SHTSO
FORGADR
OGLT
OGTNAPI
OGTNOA
OGTTRAN
ORGNAME
TSOID

GTNOA
GTTRAN
SNS
SSN
SNMDEL

-63- SHISTTOIDP
This table used to associate TDPID with IST
<dbtsp:tab=SHISTTOTDP,IST=1;
DATABASE TABLE
BLOCK TAB
TABLE
SHTD5 SHISTTOTDP
IST
1

TDPNO
DP2

WRAPPED
NO

TDPID
1

END
TDPNO: trigger detection point No----- DP2
TDPID: 1

4- SHTDP
This table used to associate SHINS (parameter in IDP message) and SHTDPS (routing for
message) with TDPID
<dbtsp:tab=SHTDP,TDPID=1;
DATABASE TABLE
BLOCK TAB
TABLE
SHTD6 SHTDP
TDPID
CLISTID CSK
CTINSID
1
TINSID TLISTID CCH
1
END

WRAPPED
YES
DIAGTYP PROTI TDPSID
3
2
1

ELISTID: Extension List ID (used if there is any extension field will be sent in IDP)
DIAGTYP: dialog type =3 ----- white
PROTI: protocol identifier =2 ----- CAP
TDPSID: Trigger detection point service data ID =1
TINSID: Trigger invoke signaling ID =1

5- SHINS
Identify which parameters (optional or mandatory) will be used in construct the IDP
<dbtsp:tab=SHINS,INSID=1;
DATABASE TABLE
INSID ACGN BCAP BGVNS CAUSE CDN CGCAT CPN CUGCI CUGIC
1
OPT
OPT
NO
NO
OPT
OPT
OPT
NO
NO
GDS GNS HLC LN
OCDN RDI RGN RO SII
NO
NO
OPT OPT OPT OPT OPT
NO NO
END

ACGN = Additional Calling Party Number

BCAP =Bearer Capability = TMR
BGVNS = Backward Global Virtual Network Service
CAUSE = ISUP Cause Indicator
CDN = Called Party Number
CGCAT = Calling Party Category
CPN = Calling Party Number
CUGCI = Closed User Group Call Indicator
CUGIC = Closed User Group Interlock Code
FGVNS = Forward Global Virtual Network Service
FWCI =Forward Call Indicators
GDS =Generic Digits Set

FGVNS FWCI
NO
NO

-7GNS =Generic Number Set

HLC =High Layer Compatibility
LN =Location Number
OCDN =Original Called Number
RDI =Redirection Information
RGN =Redirecting Number
RO =Route Origin
SII = Service Interaction Indicators

6- SHTDPS
Hold the detection point data, also it is indicates if the specific parameter that will be included
in IDP
<dbtsp:tab=SHTDPS,TDPID=1;
DATABASE TABLE
BLOCK TAB
TABLE
WRAPPED
SHTD7 SHTDPS
YES
TDPSID CCTR CG CL CESS CGENC CTMP EVTYPE IPCAP LIF1 LIF2
1
0 0 CSI
NO
CSI
YES
NO
1
1
SFI SHR SHS SK TEI TRIG TSDID TSOID USI
NO 1
1
1
1
CSI
END

CESS: control essential, specifies if SCF control for the call is essential
EVTYPE: if Basic call statue model include in IDP or not
TSDID: trigger service destination identity
TSOID: trigger service origination identity

7- SHTSD:
Hold the information used for routing to SCF, which include the address of SCF, number plan and
address nature.
<dbtsp:TAB=SHTSD,TSDID=1;
DATABASE TABLE
BLOCK TAB
SHTD8 SHTSD

TABLE

TSDID
DSTNAME
DGLT
1
SCS01
GTNAPI GTNOA
GTTRAN
0
SNS
SSN
DPCLTH
-

WRAPPED
YES
DPC
SNMADD
-

FDSTADR
7
SNMDEL
-

END

DSTNAME = Destination service Name

DGLT = Destination Global Title
DPC =
Destination Point Code
FDSTADR = Format of Destination Address
GTNAPI = Global Title Numbering Plan
GTNOA = Global Title Nature of Address
GTTRAN = Global Title Translation Type
SNMADD = Service Number Modification Addition
SNMDEL = Service Number Modification Deletion
SNS =
Service Number Selection
SSN =
Subsystem Number
DPCLTH = Destination Point Code Length

8- SHTSO:

-8Hold the information of SSF function (GT, address nature and number plan)
<dbtsp:TAB=SHTSO,TSOID=1;
DATABASE TABLE
BLOCK
SHTD8

TAB
SHTSO

TABLE

WRAPPED
YES

TSOID
FORGADR
OGLT
1
2
20112008001
OGTTRAN
ORGNAME
OPCLTH
0
SMS01
-

OGTNAPI
1

OGTNOA
4

END

FORGADR = Format of Origin Address = Global Title and SSN

=2
OGTNAPI = Own Global Title Numbering Plan Indicator = 1 (ISDN number plan)
OGTNOA = Own Global Title Nature of Address = 4 (international number)
OGTTRAN = Own Global Title Translation Type
=0
ORGNAME = Origin Name
OPCLTH = Originating Point Code Length

There are 2 tables used to Extensions fields (EX: VLR number, ORCLD number )

9- SHEXTLIST:
List the extension field and has index for these extension fields
<dbtsp:TAB=SHEXTLIST;
DATABASE TABLE
BLOCK
TAB
SHTD3 SHEXTLIST
ELISTID
189
100
2
201
101
END

EXTNO
3
3
2
3
3

TABLE

CRIT
ABT
IGN
ABT
ABT
IGN

WRAPPED
NO

EXTTYPE GSIS PROTI REQ

33
0
1
OPT
5
0
1
OPT
5
0
1
OPT
33
0
1
OPT
5
0
1
OPT

EXTNO = Extension field Number. Specifies the number of the extension field into which the parameter is placed.
CRIT =
Criticality. (the action of SCF Abort or Ignore)
EXTTYPE = Extension Type. Specifies a protocol extension type
GSIS = Generic Signalling Information Source. Specifies the set of ISUP messages.
PROTI = Protocol Identifier = 1 (INAP CS1+ protocol)
REQ =
Required for triggering. Specifies if this extension field is mandatory or optional

10- SHEXTRANS:
Used to define the parameter of the Extension type (the source of the extension field)
<dbtsp:TAB=SHEXTRANS;
DATABASE TABLE
BLOCK TAB
SHTD1 SHEXTRANS
EXTTYPE
33
6
5
1

PROTI
1
1
1
1

TABLE
DEF
0
0
0
0

DIR
AMTAG
FORW VLRN
FORW VLRN
FORW INCI3
FORW ASI

WRAPPED
NO

-9END

EXTTYPE = Extension Type. Specifies a protocol extension type.

PROTI = Protocol Identifier. Specifies the protocol to be used = 1 (Ericsson INAP CS1+)
DEF =
Data Encoding Format = 0 (Integer)
DIR =
Direction indicator. Specifies in which = FORW (Forward)
AMTAG = ISUP Parameter Tag. Specifies the ISUP, ISDN User Part protocol, identity of a parameter (VLRN: VLR
number.)

After Construct the IDP message, then the message is routed to SCF using SCCP layer

C7GSP: TT=0, NP=1, NA=4, NS= xxxxxxxxxx;

Then from routing case GTRC, we can find the PC where the message is routed.