You are on page 1of 9

-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 M NA ANRES

60203 5-2011 4 OBA-30


BO-17
OWNMS
NATMS
PLMN-0
STALL
MAPVER-2
INOPER-2
CBA-55
CBAZ-0
CAMEL-3
ADD END
<exrop:dety=min;
ROUTE DATA
R ROUTE PARAMETERS
MINORIG DETY=MIN FNC=9 MIS1=1 MIS2=2 BO=25
RO=0 CO=0 MIS5=1

MSNAN block
MTV block INOPER-2
Subscriber with CAMEL-3
CAMEL information MAP-2

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
TRD=150
-3-

<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 STATE SES PID LEVEL EPO EPSTATE


SSFTRAM N MAX ACT 5806 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
EA 0 0 0
INS 0 0 0
ISA 0 0 0
-4-
ISB 0 0 0
MST 0 0 0
OCO 2 0 0
OTA 0 0 0
PLMN 0 0 0
PR 0 0 0
RCP 0 0 0
RDC 0 0 0
RO 0 0 0
ST 0 0 0

END

 Now we start in triggering table (to construct IDP and route this IDP)
1- SHIST
SHIST
BCSMTYP
<dbtsp:tab=shIST,ist=1; DISCONI
DATABASE TABLE IST
IST=
MIDCALI
BLOCK TAB TABLE WRAPPED 1
SHTD4 SHIST YES NUMDIG
REANSI
IST BCSMTYP DISCONI MIDCALI NUMDIG REANSI SUSPNDI SSFTYPE
1 ORIG - - 3 - - I
SSFTYPE
TNSID SUSPNDI
1 TNSID
END

IST: IN Service trigger (from MIN block) TNSID=1


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 ISCC
BRISRID OSBCC
BROSRID OSDCC
CLIDTYP SCFIDTY
DRISRID ROUTTYP
DROSRID
SHTD4

<dbtsp:tab=shtns,tnsid=1;
DATABASE TABLE

BLOCK TAB TABLE WRAPPED


SHTD4 SHTNS 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
- 1 1 2 8 YES 1 1
ROUTTYP SCFIDLT SCFIDST SCFIDTY SHREQ
DR - - 0 S
-5-

END

DRISRID: direct route incoming SSF route ID ----- 1


DROSRID: direct route outgoing SSF route ID ------2 Equal to RINDEX in
ROUTTYP: route type ----- Direct 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

SHEXTRANS
SHEXLIST
CRIT REQ AMTAG
PROTI DEF
ELISTID EXTTYPE EXTTYPE DIR
PROTI
EXTNO
Diagram of triggering tables EXTTYPE
ELISTID
SHISTTOTDP
IST
SHTDP SHTDPS
CLISTID CCTR SFI
TDPID CG SHR SHTSD
TDPNO CSK CL SHS TSDID GTNOA
CTINSID CESS SK
TDPID TSDID DSTNAME GTTRAN
DIAGTYP CGENC TEI DGLT SNS
PROTI CTMP TRIG
SNMADD SSN
TDPSID TDPSID TDPSID TSDID
DPC SNMDEL
TINSID EVTYPE TSOID
IPCAP LIF1 FDSTADR
TLISTID
LIF2 GTNAPI
TDPID
USI

SHTSO
SHINS TSOID
ACGN CGCAT GNS RO FORGADR
BCAP CPN HLC RDI OGLT
TINSID BGVNS CUGCI NSID SII
OGTNAPI
CAUSE FGVNS LN OGTNOA
CUGIC FWCI OCDN OGTTRAN
CDN GDS RGN ORGNAME
TSOID
-6-

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

BLOCK TAB TABLE WRAPPED


SHTD5 SHISTTOTDP NO

IST TDPNO TDPID


1 DP2 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 WRAPPED
SHTD6 SHTDP YES

TDPID CLISTID CSK CTINSID DIAGTYP PROTI TDPSID


1 - - - 3 2 1
TINSID TLISTID CCH
1 - -
END

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 FGVNS FWCI
1 OPT OPT NO NO OPT OPT OPT NO NO 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
-7-
GNS =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 TABLE WRAPPED


SHTD8 SHTSD YES

TSDID DSTNAME DGLT DPC FDSTADR


1 SCS01 - - 7
GTNAPI GTNOA GTTRAN SNMADD SNMDEL
- - 0 - -
SNS SSN DPCLTH
- - -

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:
-8-
Hold the information of SSF function (GT, address nature and number plan)

<dbtsp:TAB=SHTSO,TSOID=1;
DATABASE TABLE

BLOCK TAB TABLE WRAPPED


SHTD8 SHTSO YES

TSOID FORGADR OGLT OGTNAPI OGTNOA


1 2 20112008001 1 4
OGTTRAN ORGNAME OPCLTH
0 SMS01 -

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 TABLE WRAPPED


SHTD3 SHEXTLIST NO

ELISTID EXTNO CRIT EXTTYPE GSIS PROTI REQ


189 3 ABT 33 0 1 OPT
100 3 IGN 5 0 1 OPT
2 2 ABT 5 0 1 OPT
201 3 ABT 33 0 1 OPT
101 3 IGN 5 0 1 OPT
END
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 TABLE WRAPPED


SHTD1 SHEXTRANS NO

EXTTYPE PROTI DEF DIR AMTAG


33 1 0 FORW VLRN
6 1 0 FORW VLRN
5 1 0 FORW INCI3
1 1 0 FORW ASI
-9-

END

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.