KCELL OCS Interface Debit CDR

The table below displays the CDR fields for when a debit request is made by the Online Charging Service (OCS) Interface.

Field Name Description

1

msisdn

The subscriber’s MSISDN.

This is in Tango format.

2

service ID

The CDR service ID which is 104 for this CDR.

3

transaction type

Specifies the transaction type:

values

  • 0 = debit request

  • 1 = remove service

  • 2 = eligibility check performed

4

CDR generation date

The date on which the CDR was generated. Format: DD/MM/YYYY.

5

CDR generation time

The time at which the CDR was generated. Format: hh:mm:ss.

6

debit ICI cause code

The ICI cause code for the debit operation.

values

  • -1 = successful debit request

  • 0 = undefined error

  • 53 = insufficient funds

  • 54 = protocol error; unable to parse debit request from the OCI server

  • 1006 = one of the 3 requests to the external OCS failed

7

MSISDN

The subscriber’s MSISDN in international format.

This is a standard MSISDN without any special encoding.

8

debit request session ID

The debit request session ID from the OCI.

9

debit request charge amount

The charge amount received from the OCI.

10

debit request productId

The productId that comes from the OCI.

11

adjusted charge amount

The value sent to the external server after applying the configured exponent.

12

debit request response time

The time taken to complete the debit request (in milliseconds).

13

retrieve attribute status code

The SOAP status codes.

values

  • -1 = connection error

  • -2 = connection timeout

14

retrieve attribute error reason

Denotes the SOAP fault reason or exception cause.

15

retrieve attribute response

The value returned from the external server.

16

retrieve attribute operation result

A value that indicates if the operation is considered successful or not when handling a debit request.

values

  • 0 = successful

  • 1 = failed

17

retrieve attribute response time

The amount of time it took to complete the retrieve attribute request (in milliseconds).

18

charging status code

Specifies the HTTP status code.

These are standard HTTP status codes.

19

charging error reason

Specifies the reason for the charging error.

20

charging operation result

The outcome of the charging operation.

values

  • 0 = successful

  • 1 = failed

21

charging response time

The amount of time it took to complete the charging request (in milliseconds).

22

add service status code

The fault code for the add service request.

values

  • versionMismatch = Represents an invalid namespace for the SOAP Envelope element.

  • mustUnderstand = Occurs when an immediate child element (of the Header element) was not understood.

    Occurs only when the mustUnderstand attribute is set to 1.

  • client = The message was incorrectly formed or contained incorrect information.

  • server = The message did not proceed as there was a problem with the server.

23

add service error reason

Add service error reason or exception cause.

24

add service response

The value returned from the external server for an add service request.

25

add service operation result

The outcome of the add service operation.

This will always be 0 as charging would have occurred and hence, the service added.

26

add service response time

The amount of time it took to complete the add service request (in milliseconds).

27

remove service status code

The fault code for the remove service request.

values

  • versionMismatch = Represents an invalid namespace for the SOAP Envelope element.

  • mustUnderstand = Occurs when an immediate child element (of the Header element) was not understood.

    Occurs only when the mustUnderstand attribute is set to 1.

  • client = The message was incorrectly formed or contained incorrect information.

  • server = The message did not proceed as there was a problem with the server.

28

remove service error reason

Remove service error reason or exception cause.

29

remove service response

The value returned from the external server for an remove service request.

30

remove service operation result

The outcome of the remove service operation.

  • 0 = okay

  • -1 = remove service request was not executed because the plan was not chargeable

31

remove service response time

The amount of time it took to complete the remove service request (in milliseconds).

OCS Interface Debit CDR sample

This section contains a successful sample for the OCS Interface Debit CDR.

77010325296,104,0,20/02/2020,12:34:48,-1,1234567,8787,2400,4550303,24.0,28,,,Y,0,7,200,,0,12,,,57297504,0,9,,,,,