COMPLETE SIGALLIG FLOW FOR A SUCCESSFUL

VOICE MO CALL O CAMEL V2

 OPERATIOS:

1) IDP (IITIAL DETECTIO POIT) : SSF > SCF

Component:
invoke{161,124}:
invokeID{2,1}: 0
operationCode{2,1}: initialDP{0}
InitialDPArg{48,116}:
serviceKey{128,1}: 80
callingPartyNumber{131,7}:
NA{3}: national significant number
Odd/even indicator{0}: even number of address signals
Screening indicator (for calling number){3}: network provided
Address presentation (for calling number){0}: presentation allowed
NP{1}: ISDN numbering plan (E.164)
INN indicator (for called number){0}: routing to internal network allowed
NI indicator (for calling number){0}: number complete
Number: 9475500033
callingPartysCategory{133,1}:
H'[0A]
locationNumber{138,8}:
NA{4}: international number
Odd/even indicator{0}: even number of address signals
Screening indicator (for calling number){3}: network provided
Address presentation (for calling number){0}: presentation allowed
NP{1}: ISDN numbering plan (E.164)
INN indicator (for called number){1}: routing to internal network not allowed
NI indicator (for calling number){1}: number incomplete
Number: 919433999995
bearerCapability{187,5}:
bearerCap{128,3}:
H'[80,90,A3]
eventTypeBCSM{156,1,[2]}: collectedInfo
iMSI{178,8}: 404741170548805.
locationInformation{180,23}:
ageOfLocationInformation{2,1}: 0
vlr-number{129,7}:
NP{1}: ISDN/Telephony Numbering Plan (Rec CCITT E.164)
NA{1}: international number
Number: 919433999995
cellGlobalIdOrServiceAreaIdOrLAI{163,9}:
 cellGlobalIdOrServiceAreaIdFixedLength{128,7}:
404-81-60-20051

ext-basicServiceCode{181,3}:
ext-Teleservice{131,1}: telephony
callReferenceNumber{182,5}:
H'[67,08,A6,00,01]
mscAddress{183,7}:
NP{1}: ISDN/Telephony Numbering Plan (Rec CCITT E.164)
NA{1}: international number
Number: 919433999995
calledPartyBCDNumber{184,6}:
Numbering plan indicator{1}: ISDN/telephony numbering plan (Rec. E.164/E.163)
Type of number{0}: unknown
Number: 9748418613
timeAndTimezone{185,8}:
Year/Month/Day: 2009/03/31
Hour:Minute:Second: 16:13:29
Timezone{0}: GMT+0 hour(s)

End-of-contents octets: [0,0]

Extra octets:
[0,0]

(i) Service key : 80 :: The service keys are used to identify and trigger services in the SCF. The SCF then
starts the service script corresponding to the received service key value. The service keys can also be used
for routing to the correct SDP when multiple SDP's are used.

(ii) Calling Party Number : 9475500033 :: The term Calling Party Number refers to the number that initiates a
call.

(iii) Calling Partys Category : H'[0A] :: This specifies the information sent in the forward direction indicating
the category of the calling party.

CAT SUBSCRIBER CATEGORY 0-255 - L/P/S/D

0 = Calling party is unknown at this time
1 = Operator, language French
2 = Operator, language English
3 = Operator, language German
 4 = Operator, language Russian
5 = Operator, language Spanish
6 = Available to administrations for selecting a particular language by mutual agreement
7 = Available to administrations for selecting a particular language by mutual agreement
8 = Available to administrations for selecting a particular language by mutual agreement
9 = Reserved
10 = Ordinary calling subscriber
11 = Calling subscriber with priority
12 = Data call (voice band data)
13 = Test call
14 = Not used
15 = Payphone
16-223 = Not used
224-254 = National use
255 = Not used

(iv) Location Number : 919433999995 :: A location number is a number which defines a specific location
within a GSM PLMN. The Location number is formatted according to CCITT Recommendation E.164, as
shown in figure. The Country Code (CC) and National Destination Code (NDC) fields of the location
number are those which define the GSM PLMN of which the location is part.

The structure of the locally significant part (LSP) of the location number is a matter for agreement between
the PLMN operator and the national numbering authority in the PLMN's country.

(v) Bearer Capability: H'[80,90,A3] :: Used by the calling party to specify the kind of channel that is being
requested. It is one of the important fields of setup message.

Format of the parameter Bearer Capability

7 6 5 4 3 2 1
8
1 ext Coding standard Information transfer capability BC 1
0/1 ext Transfer mode Information transfer rate BC 2
0/1 ext Structure Configuration Establishment BC 2a
NOTE 1
1 ext Symmetry Information transfer rate (destination to origination) BC 2b
NOTE 2
1 ext Rate multiplier BC 2.1
0/1 ext L1 identity User information Layer 1 protocol BC 3 NOTE
3
0/1 ext Synch Nego-tiation User rate BC 3a
Async NOTE 4
0/1 ext Intermediate rate NIC on TX NIC on RX Flow cont. Flow cont 0 Spare BC 3b
on TX on RX NOTE 5
0/1 ext Hdr / no Multi frame Mode LLI nego- Assi- gnor/ Inba- nd / 0 Spare BC 3b
Hdr supp. tiation Assi- gnee Out- band NOTE 6
0/1 ext Number of stop bits Number of data bits Parity BC 3c
NOTE 4
 1 ext Dupl. mode Modem type BC 3d
NOTE 4
1 ext L2 identity User information Layer 2 protocol BC 4 NOTE
3
1 ext L3 identity User information Layer 3 protocol BC 5 NOTE
3

----------------------- Bearer Capability 80,90,A3 --------------------------------------------------

|10000000 |Tag |(CONT P [0]) |
|00000011 |Length |3 |
|10000000 | ---------------------------------------------------------------------------------|------>80
|1------- |Extension Ind (BC 1) |Last octet |
|-00----- |Coding Standard |ITU-T |
|---00000 |Info Transfer Capability |Speech |
|10010000 | ---------------------------------------------------------------------------------|------>90
|1------- |Extension Ind (BC 2) |Last octet |
|-00----- |Transfer Mode |Circuit mode |
|---10000 |Information Transfer Rate |64 kbit/s |
|10100011 | ---------------------------------------------------------------------------------|------>A3
|1------- |Extension Ind (BC 3 ) |Last octet |
|-01----- |Layer Identification |User info layer 1 protocol |
|---00011 |User Info Layer 1 Protocol |Rec. G.711, A-law |

(vi) eventTypeBCSM : [2] : collected info :: eventBCSM DP2 is armed in this case.
(vii) iMSI : 404-74-1170548805 :: An International Mobile Subscriber Identity or IMSI is a unique
identification associated with all GSM and UMTS network mobile phone users. It is stored as a 64 bit field
in the SIM inside the phone and is sent by the phone to the network. It is also used for acquiring other
details of the mobile in the Home Location Register (HLR) or as locally copied in the Visitor Location
Register.

IMSI is composed of three parts:

• Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of
domicile of the mobile subscriber;

• Mobile Network Code (MNC) consisting of two or three digits for GSM applications. The MNC identifies
the home GSM PLMN of the mobile subscriber. The length of the MNC (two or three digits) depends on
the value of the MCC. A mixture of two and three digit MNC codes within a single MCC area is not
recommended and is outside the scope of this specification.

• Mobile Subscriber Identification Number (MSIN) identifying the mobile subscriber within a GSM PLMN.

(viii) Location Information ::

• vlr-number : 919433999995

• cellGlobalIdOrServiceAreaIdOrLAI : 404-81-60-20051 :: The Cell Global Identification is the

concatenation of the Location Area Identification and the Cell Identity. Cell Identity must be unique within
a location area.
• Mobile Country Code (MCC) identifies the country in which the GSM PLMN is located. The value of the
MCC is the same as the three digits MCC contained in international mobile subscriber identity (IMSI).

• Mobile Network Code (MNC) is a code identifying the GSM PLMN in that country. The MNC takes the
same value as the two or three digit MNC contained in IMSI.

• Location Area Code (LAC) which is a fixed length code (of 2 octets) identifying a location area within a
GSM PLMN.

• The BSS and cell within the BSS is identified within a location or routing area by adding a Cell Identity
(CI) to the location or routing area identification.

(ix) ext-basicServiceCode : telephony :: TS10

DBSG DEFAULT BASIC SERVICE GROUP 1-6 - L/P/S

1 = All Speech Transmission Services : (TS10)
2 = Not used
3 = All Facsimile Transmission Services : (TS60)
4 = Not used
5 = All Data Circuit Asynchronous Services : (BS20)
6 = All Data Circuit Synchronous Services : (BS30)

(x) callReferenceNumber : H'[67,08,A6,00,01] :: It is used to correlate different messages between SCP and
SSF during a complete call.

(xi) mscAddress : 919433999995 :: MSC Global Title

(xii) calledPartyBCDNumber : 9748418613 :: This contains the number used to identify the called party in the
forward direction. The number contained in this IE shall be identical to the number received over the access
network. It may e.g. include service selection information, such as * and # digits, or carrier selection
information dialed by the subscriber.

(xiii) timeAndTimezone :: Comes from the SSF in IDP , in some SCFs like Ericsson CCN there is a function to
overwrite the time zone with SCF time Zone .

Time : Year/Month/Day
Hour:Minute:Second

Timezone : [0] :: GMT+0 hour(s)

2) RRB (REQUEST REPORT BCSM) : SSF < SCF

Component:
invoke{161,31}:
invokeID{2,1}: 1
operationCode{2,1}: requestReportBCSMEvent{23}
RequestReportBCSMEventArg{48,23}:
bcsmEvents{160,21}:
 BCSMEvent{48,6}:
eventTypeBCSM{128,1,[10]}: oAbandon
monitorMode{129,1,[1]}: notifyAndContinue
BCSMEvent{48,11}:
eventTypeBCSM{128,1,[9]}: oDisconnect
monitorMode{129,1,[0]}: interrupted
legID{162,3}:
sendingSideID{128,1}: 1

(i) RRB EventTypeBCSM :

• Event Armed : [10] : oAbandon :: Indication that a disconnect indication is received from the originating
party during the call establishment procedure,
Monitor mode : [1] : notify and continue

• Event Armed : [9] : oDisconnect :: A disconnect indication is received from the originating party ,
Monitor mode : [0] : interrupted

(ii) Monitor mode :

[1] : NOTIFY AND CONTINUE
[0] : INTERRUPTED

NOTIFY AND CONTINUE : Whenever the event is armed , it will notify to SCF and automatically
continue the processing.
INTERRUPTED : Whenever the event is armed , it will be interrupted and wait for the further instruction
from SCF

(iii) LegID :: sendingSideID : [1] :: Calling Party

• LegID : LEG_ID_RECEIVING_SIDE : [2]

LEG_ID_SENDING_SID : [1]
LEG_TYPE_CALLED_PARTY : [2]
LEG_TYPE_CALLING_PARTY : [1]

3) FI (FIRST ITERROGATIO) : SCF > SDP

Component:
invoke{161,75}:
invokeID{2,1}: 1
operationCode{2,1}: Retrieve{16}
RetrieveArg{49,67}:
operationID{129,2}:
H'[01,00]
applicationID{130,1,[120]}:
FirstInterrogation, version 12
dataItemID{163,58}:
trafficCase{128,2,[7]}:
Originating outside HPLMN, CAP v.2
teleServiceCode{129,2,[0]}:
Voice
calledPartyNumber{130,10}:
NA{2}: unknown (national use)
Spare bit(O1/H){0}: 0
Screening indicator (for calling number){0}: user provided, not verified
Address presentation (for calling number){0}: presentation allowed
NP{1}: ISDN numbering plan (E.164)
INN indicator (for called number){0}: routing to internal network allowed
NI indicator (for calling number){0}: number complete
Number of Digits{10}: 10
Filler octet(O4){0}: 0
Number: 9748418613
Filler: 00
callingPartyNumber{133,10}:
NA{3}: national significant number
Spare bit(O1/H){0}: 0
Screening indicator (for calling number){3}: network provided
Address presentation (for calling number){0}: presentation allowed
NP{1}: ISDN numbering plan (E.164)
INN indicator (for called number){0}: routing to internal network allowed
NI indicator (for calling number){0}: number complete
Number of Digits{10}: 10
Filler octet(O4){0}: 0
Number: 9475500033
Filler: 00
originatingLocationInformation{135,10}:
Unused octets(O1,O2): H'[04,13]
Number of Digits{12}: 12
Filler octet(O4){0}: 0
Number: 919433999995
triggerTime{140,12}:
Frame information (not used): H'[02,10]
Number of digits{16}: 16
Filler octet(O4){0}: 0
Year/Month/Day: 2009/03/31
Hour:Minute:Second: 16:13:29
Timezone{0}: GMT+0 hour(s)
(i) operation ID : The retrieve operation towards the SDP carries the interrogation parameters inside the
packet having the below structure .

Operation ID :: H’ 01,00 for interrogation

H’ 01,00,01 for interrogation results.

AID:- Application ID, see below for the details.

(ii) applicationID :: [120] : FirstInterrogation, version 12

This parameter identifies the Ch.Sys. operation and version.
Data type: ApplicationID

(iii) trafficCase:: [7] : Originating outside HPLMN, CAP v.2

The purpose of Traffic Cases is to describe overall signaling paths for different traffic cases in Charging
System.

(iv) teleServiceCode :: [0] : Voice

The possible positive result values of the TeleServiceCode determination are:
• speech
• data
• fax
• video telephony
• video conference
• non_speech
• unknown

(v) calledPartyNumber : 9748418613 :: This number identifies the called party .

(vi) callingPartyNumber : 9475500033 :: This identifies the calling party or the origin of the call.

(vii) originatingLocationInformation :: vlr-number : 919433999995

(viii) triggerTime :: Year/Month/Day: 2009/03/31

Hour:Minute:Second: 16:13:29
Timezone{0}: GMT+0 hour(s)

The local time when the service was triggered.

Data type: Date And Time.
IDP trigger time/Time Zone is carried into this FI , as stated earlier CCN has the capability to overwrite this time
zone with its own time zone.
4) FIR (FIRST ITERROGATIO RESULT) : SCF < SDP

Component:
returnResultLast{162,{indefinite,59}}:
invokeID{2,1}: 1
result{48,{indefinite,52}}:
operationCode{2,1}: Retrieve{16}
RetrieveResultArg{48,45}:
operationreturnID{129,3}:
H'[01,00,01]
dataItemInformation{162,38}:
firstInterrogationResultCode{128,2,[2,0]}:
Result code{2}: Call Allowed - More money available
Fault code{0}: No Fault code or Reason code provided
correlationId{129,4,H'[BA,C3,96,1D]}:
496419770
endTimeMoment{133,2}:
180 seconds (00:03:00)
endTimeMoment100ms{134,4}:
180.0 seconds (00:03:00.0)
cDRRequested{147,2,[1]}: True
serviceClass{148,2}: 7002
accountValueBeforeCall{149,8}:
Frame information (not used): H'[20,00]
Number of digits(including Price frame){7}: 7
Filler octet(O4){0}: 0
Price frame{42}:
Currency{10}: Local currency
Decimals{2}: Two decimals
Sign{0}: Positive value
Number: 146.60
Filler digit: 0

(i) operationreturnID : H’ 01,00,01 for interrogation results

(ii) firstInterrogationResultCode :: [2,0] : Result code[2]: Call Allowed - More money available
Fault code[0]: No Fault code or Reason code provided

• Indicates how the SCF shall handle the call and how other data sent in the operation shall be processed by
SCF.
Data type: FirstInterrogationResultCode.

• FirstInterrogationResultCode - (0) Call Allowed- Short Call,

(1) Call Allowed - Medium Call,
 (2) Call Allowed - More Money Available,
(3) Call allowed - Toll free.

(iii) correlationId : 496419770 :: Correlation id that the SDP uses to correlate a reservation with a specific call.
Data type: LongInteger.

(iv) endTimeMoment : 180 seconds (00:03:00) :: Time (measured from moment when call becomes active)
when end announcement shall be played and call shall be released, or Intermediate Interrogation shall be
sent.
Data type: Seconds.

(v) endTimeMoment100ms : 180.0 seconds (00:03:00.0) :: Time (measured from last endTimeMoment100ms)
when end announcement shall be played and call shall be released, or IntermediateInterrogation shall be
sent.
Data type: MilliSecond100.

(vi) cDRRequested : [1] : True :: Indicates whether CDR’s should be created in the SCF or not.
Data type: Flag.

(vii) serviceClass : 7002 :: A Service Class is a set of data for a group of accounts. Service Class data is
logically divided into two parts - Account Service Class data and Subscriber Service Class data. The
account Service Class data describes charging and limitations of a Charging System account. The
subscriber Service Class data describes toll-free numbers and announcements.
A number of events such as administration of usage accumulators, Service Class change, supervision of
negative balance, service fee deduction, (ID:02742) periodic adjustments of accounts (ID:02742) and
expiry dates are related to the Service Class.
Data type: Integer.

(viii) accountValueBeforeCall : 146.60 :: Indicates the present account balance for the main account of the
subscriber (without taking into account the cost for the current call).
Data type: Price.

5) RRB + CUE ( Request Response BCSM + Continue) : SSF < SCF

Component:
invoke{161,55}:
invokeID{2,1}: 2
operationCode{2,1}: requestReportBCSMEvent{23}
RequestReportBCSMEventArg{48,47}:
bcsmEvents{160,45}:
BCSMEvent{48,6}:
eventTypeBCSM{128,1,[4]}: routeSelectFailure
monitorMode{129,1,[0]}: interrupted
BCSMEvent{48,6}:
eventTypeBCSM{128,1,[5]}: oCalledPartyBusy
monitorMode{129,1,[0]}: interrupted
 BCSMEvent{48,6}:
eventTypeBCSM{128,1,[7]}: oAnswer
monitorMode{129,1,[0]}: interrupted
BCSMEvent{48,11}:
eventTypeBCSM{128,1,[9]}: oDisconnect
monitorMode{129,1,[0]}: interrupted
legID{162,3}:
sendingSideID{128,1}: 2
BCSMEvent{48,6}:
eventTypeBCSM{128,1,[6]}: oNoAnswer
monitorMode{129,1,[0]}: interrupted

Component:
invoke{161,6}:
invokeID{2,1}: 3
operationCode{2,1}: continue{31}

RRB BCSM Events :

(i) Event Armed : [4] : routeSelectFailure :: Indication that the call establishment failed
Monitor mode : [0] : interrupted :: the event is armed , it will be interrupted and wait for the further
instruction from SCF.

(ii) Event Armed : [5] : oCalledPartyBusy :: Indication that:

• a busy indication is received from the terminating party,
• a not reachable event is determined upon a cause IE in the ISUP release message
Monitor mode : [0] : interrupted :: the event is armed , it will be interrupted and wait for the further
instruction from SCF.

(iii) Event Armed : [7] : oAnswer :: Indication that the call is accepted and answered by the terminating party.
Monitor mode: [0] : interrupted :: the event is armed , it will be interrupted and wait for the further
instruction from SCF.

(iv) Event Armed: [9] : oDisconnect :: A disconnect indication is received from the originating party or from
the terminating party.
Monitor mode: [0] : interrupted :: the event is armed , it will be interrupted and wait for the further
instruction from SCF.
sendingSideID: [2] : Called Party :: The sending side ID is provided in this case to distinguish the message
from the first RRB oDisconnect eventtypeBCSM.

(v) Event Armed: [6] : oNoAnswer :: Indication that an application timer associated with the O_No_Answer
DP expires.
Monitor mode: [0] : interrupted :: the event is armed , it will be interrupted and wait for the further
instruction from SCF.
 A continue operation is invoked in this step to allow SSF to continue call processing .

6) ERB (Event Report BCSM) : SSF > SCF

Component:
invoke{161,21}:
invokeID{2,1}: 1
operationCode{2,1}: eventReportBCSM{24}
EventReportBCSMArg{48,13}:
eventTypeBCSM{128,1,[7]}: oAnswer
legID{163,3}:
receivingSideID{129,1}: 2
miscCallInfo{164,3}:
messageType{128,1,[0]}: request

(i) ERB EventReportBCSM :

• Event Armed: [7] : oAnswer :: an Event Report BCSM operation to the SCF indicating that the Called
Party has answered.

(ii) receivingSideID: [2] : Called party

(iii) messageType: [0] : request :: to request an Apply Charging on the call duration.

7) ACH + CUE (Apply Charging + Continue) : SSF < SCF

Component:
invoke{161,21}:
invokeID{2,1}: 4
operationCode{2,1}: applyCharging{35}
ApplyChargingArg{48,13}:
aChBillingChargingCharacteristics{128,6}:
CAMEL-AChBillingChargingCharacteristics:
timeDurationCharging{160,4}:
maxCallPeriodDuration{128,2}: 1800

partyToCharge{162,3}:
sendingSideID{128,1}: 1

Component:
 invoke{161,6}:
invokeID{2,1}: 5
operationCode{2,1}: continue{31}

(i) maxCallPeriodDuration : 1800 = 180 sec : It is the maximum time that is reserved for one interval by the
SDP. When the call is of duration exceeding the maxCallPeriodDuration, then ACR(apply charging result)
is sent to the SCF from SSF, which inturn performs the intermediate interrogation to the SDP and reserves
a new grant time.

maxCallPeriodDuration is measured in 100 millisecond units.

(ii) partyToCharge :: sendingSideID : [1] : Calling Party

In the last step an ERB event has been armed in an interrupted mode. The event is now in the WFI
(Waiting For Instruction) state. Hence, a continue operation is invoked in this step to continue the further
processing.

8) ACR (Apply Charging Result) : SSF > SCF

Component:
invoke{161,23}:
invokeID{2,1}: 2
operationCode{2,1}: applyChargingReport{36}
ApplyChargingReportArg{4,15}:
CAMEL-CallResult:
timeDurationChargingResult{160,13}:
partyToCharge{160,3}:
receivingSideID{129,1}: 1
timeInformation{161,3}:
timeIfNoTariffSwitch{128,1}: 43
legActive{130,1}: FALSE

(i) partyToCharge :: receivingSideID : [1] : Calling Party

(ii) timeInformation : 43

Counter = 43

Time Interval of each interval = 100 ms

Net Effective chargeable time = 43 x 100 ms = 4.3 sec.

(iii) legActive : False :: It denotes that no leg i.e. calling party as well as the called party is not active.

9) ERB (Event Report BCSM) : SSF > SCF

 Component:
invoke{161,29}:
invokeID{2,1}: 3
operationCode{2,1}: eventReportBCSM{24}
EventReportBCSMArg{48,21}:
eventTypeBCSM{128,1,[9]}: oDisconnect
eventSpecificInformationBCSM{162,6}:
oDisconnectSpecificInfo{167,4}:
releaseCause{128,2}:
H'[80,90]

legID{163,3}:
receivingSideID{129,1}: 1
miscCallInfo{164,3}:
messageType{128,1,[0]}: request

(i) ERB eventTypeBCSM :

• Event Armed: [9] : oDisconnect :: A disconnect indication is received from the originating party or from
the terminating party.

(ii) releaseCause: H'[80,90] :: the second octet value represents the cause and the reason for releasing the call.

(iii) legID :: receivingSideID: [1] : Calling Party

(iv) messageType :: [0] : request :: request SCF to initiate the final report.

10) FR (Final Report) : SCF > SDP

Component:
invoke{161,121}:
invokeID{2,1}: 1
operationCode{2,1}: Retrieve{16}
RetrieveArg{49,113}:
operationID{129,2}:
H'[01,00]
applicationID{130,1,[122]}:
FinalReport, version 12
dataItemID{163,104}:
trafficCase{128,2,[7]}:
Originating outside HPLMN, CAP v.2
teleServiceCode{129,2,[0]}:
Voice
calledPartyNumber{130,10}:
NA{2}: unknown (national use)
Spare bit(O1/H){0}: 0
Screening indicator (for calling number){0}: user provided, not verified
Address presentation (for calling number){0}: presentation allowed
NP{1}: ISDN numbering plan (E.164)
INN indicator (for called number){0}: routing to internal network allowed
NI indicator (for calling number){0}: number complete
Number of Digits{10}: 10
Filler octet(O4){0}: 0
Number: 9748418613
Filler: 00
callingPartyNumber{133,10}:
NA{3}: national significant number
Spare bit(O1/H){0}: 0
Screening indicator (for calling number){3}: network provided
Address presentation (for calling number){0}: presentation allowed
NP{1}: ISDN numbering plan (E.164)
INN indicator (for called number){0}: routing to internal network allowed
NI indicator (for calling number){0}: number complete
Number of Digits{10}: 10
Filler octet(O4){0}: 0
Number: 9475500033
Filler: 00
originatingLocationInformation{135,10}:
Unused octets(O1,O2): H'[04,13]
Number of Digits{12}: 12
Filler octet(O4){0}: 0
Number: 919433999995
triggerTime{139,12}:
Frame information (not used): H'[02,10]
Number of digits{16}: 16
Filler octet(O4){0}: 0
Year/Month/Day: 2009/03/31
Hour:Minute:Second: 16:13:29
Timezone{0}: GMT+0 hour(s)
correlationId{141,4,H'[BA,C3,96,1D]}:
496419770
startOfCall{142,12}:
Frame information (not used): H'[02,10]
Number of digits{16}: 16
Filler octet(O4){0}: 0
Year/Month/Day: 2009/03/31
 Hour:Minute:Second: 16:05:06
Timezone{34}: GMT+5 1/2 hour(s)
durationOfLastPeriod100ms{144,4}:
5.0 seconds
finalChargableDuration100ms{146,4}:
5.0 seconds
accountValueBeforeCall{148,8}:
Frame information (not used): H'[20,00]
Number of digits(including Price frame){7}: 7
Filler octet(O4){0}: 0
Price frame{42}:
Currency{10}: Local currency
Decimals{2}: Two decimals
Sign{0}: Positive value
Number: 146.60
Filler digit: 0
callSetUpResultCode{149,2,[1]}:
Successful - Disconnect by calling party

(i) operationID : H’ 01,00 for interrogation

(ii) applicationID :: [122] : FinalReport, version 12

Identifies the Ch.Sys. operation and version.

Data type: ApplicationID.

(iii) trafficCase :: [7] : Originating outside HPLMN, CAP v.2

The purpose of Traffic Cases is to describe overall signaling paths for different traffic cases in
Charging System.
• 0 Originating Inside HPLMN
• 1 Forwarded Inside HPLMN
• 2 Terminating Inside HPLMN
• 3 Originating Outside HPLMN, using CAP v.1
• 4 Forwarded Outside HPLMN using CAP v.1
• 5 Terminating Outside HPLMN using CS1+
• 6 USSD Call-Back
• 7 Originating Outside HPLMN using CAP v.2
• 8 Forwarded Outside HPLMN using CAP v.2
• 9 Terminating Outside HPLMN using CAP v.2
• 10 Originating outside HPLMN, CAP v.3
• 11 Not used
• 12 Terminating outside HPLMN, CAP v.3
• 13 - 19 Not used
• 20 Originating service charging (pull)
• 21 Terminating service charging (push)

(iv) teleServiceCode :: [0] : Voice

 The possible positive result values of the TeleServiceCode determination are:
• 0 Voice
• 1 Fax
• 2 Data
• 3 Unknown
• 4 SMS
• 5 GPRS
• 6 Content
• 7 Video Telephony
• 8 Video Conference

(v) calledPartyNumber : 9748418613 :: This number identifies the called party.

(vi) callingPartyNumber : 9475500033 :: This identifies the calling party or the origin of the call.

(vii) originatingLocationInformation :: vlr-number : 919433999995

(viii) triggerTime :: Year/Month/Day: 2009/03/31

Hour:Minute:Second: 16:13:29
Timezone{0}: GMT+0 hour(s)

The local time when the service was triggered. The same information which was sent in the FI operation .
Data type: Date And Time.

(ix) correlationId : 496419770 :: Correlation id that the SDP uses to correlate a reservation with a specific call.
Data type: LongInteger.

(x) startOfCall :: Year/Month/Day: 2009/03/31

Hour:Minute:Second: 16:05:06
Timezone{34}: GMT+5 1/2 hour(s)

The time when call started, i.e. when speech connection between calling and called party
was established. Sent if call set up is successful. Here is it SCF local time , in the current trace the SSF and
the SCF time and time zone were not in sync.
Data type: DateAndTime.

(xi) durationOfLastPeriod100ms : 5.0 seconds :: Chargeable duration of last period.

Data type: MilliSecond100.

(xii) finalChargableDuration100ms : 5.0 seconds :: It is the final chargeable duration.

Data type: MilliSecond100.

(xiii) accountValueBeforeCall : 146.60 :: The account balance before call at the dedicated account given by the
dedicatedAccountId parameter.
Data type: Price.

(xiv) callSetUpResultCode :: [1] : Successful - Disconnect by calling party.

11) FRR (Final Report Result) : SCF < SDP

 Component:
returnResultLast{162,{indefinite,45}}:
invokeID{2,1}: 1
result{48,{indefinite,38}}:
operationCode{2,1}: Retrieve{16}
RetrieveResultArg{48,31}:
operationreturnID{129,3}:
H'[01,00,01]
dataItemInformation{162,24}:
finalReportResultCode{128,2,[0,0]}:
Result code{0}: Operation ok
Fault code{0}: No fault code provided, operation ok
finalChargeOfCall{129,8}:
Frame information (not used): H'[20,00]
Number of digits(including Price frame){5}: 5
Filler octet(O4){0}: 0
Price frame{42}:
Currency{10}: Local currency
Decimals{2}: Two decimals
Sign{0}: Positive value
Number: 1.20
Filler digit: 0
Filler octets: [0]
accountValueAfterCall{130,8}:
Frame information (not used): H'[20,00]
Number of digits(including Price frame){7}: 7
Filler octet(O4){0}: 0
Price frame{42}:
Currency{10}: Local currency
Decimals{2}: Two decimals
Sign{0}: Positive value
Number: 145.40
Filler digit: 0

(i) operationreturnID : H’ 01,00,01 for interrogation results.

(ii) finalReportResultCode :: [0,0] : Result code : [0] : Operation ok

Fault code : [0] : No fault code provided, operation ok
(iii) finalChargeOfCall : 1.20 :: Final cost for call.
Data type: Price.

(iv) accountValueAfterCall : 145.40 :: The account balance after call at the dedicated account given by the
dedicatedAccountId parameter.
Data type: Price.

12) CUE (Continue) : SSF < SCF

Component:
invoke{161,6}:
invokeID{2,1}: 6
operationCode{2,1}: continue{31}

A continue operation is invoked in this step to change the state from WFI (Waiting For Instruction) state
to continue further processing. As per CAMEL specification SCF is allowed to send either release or
continue in this state. In Ericsson implementation SCF [CCN] sends continue and the SSF in turn releases
the resources consumed for this call.