OCI server CDR
The Open Charging Interface (OCI) Server CDRs are generated when a subscriber purchases a data plan using the PCC platform.
Field | Name | Description | ||||
---|---|---|---|---|---|---|
1 |
|
The MSISDN of the subscriber. |
||||
2 |
|
The Tango Service ID. This is set to 30 for the OCI Server. |
||||
3 |
|
The OCI transaction type. possible values
|
||||
4 |
|
Alphanumeric string that displays the ID of the network operator for which the CDR was produced. |
||||
5 |
|
If successful, this is 0. Otherwise see OCI Server Result Codes. |
||||
6 |
|
The date the CDR was generated. Format: |
||||
7 |
|
The time the CDR was generated. Format: |
||||
8 |
|
The method of payment that was used. possible values
|
||||
9 |
|
The Tango Internal Charging Interface (ICI) session ID. |
||||
10 |
|
The IMSI of the subscriber who is charged. |
||||
11 |
|
Location information on the subscriber such as roaming status. |
||||
12 |
|
Additional information regarding the event that triggered the payment such as Plan Name, Plan ID, and Plan Booster Amount if applicable. The values are separated by a vertical delimiter. This field is empty if not provided by the client.
|
||||
13 |
|
The percentage added to the charge due to VAT.
|
||||
14 |
|
The unit type of the transaction. possible values
|
||||
15 |
|
The number of units reserved or charged. This is the exact value received by the OCI client. |
||||
16 |
|
The value sent to the OCS after any VAT has been applied but before the |
||||
17 |
|
The amount charged to the subscriber’s loan amount. |
||||
18 |
|
The number of times a direct debit retry was attempted. |
||||
19 |
|
The value sent to the OCS after any VAT has been applied and after the |
||||
20 |
|
The transaction ID is a value returned by the charging client when a plan is purchased successfully via a direct debit request.
|
||||
21 |
|
The
|
Sample
00041000080701020304050607,30,3,VodafoneIE,0,23/01/2021,12:20:35,1,0,1234567,,TEST_1MB_1MIN_REC|282904|,50,100,100,0,,,
OCI Server Result Codes
Code | Description | ||
---|---|---|---|
|
Protocol error detected by the charging gateway. |
||
|
Protocol error detected by charging handler. |
||
|
Release call issue by prepaid platform. |
||
|
Subscriber has zero balance or balance has expired. |
||
|
Unknown subscriber announcement received. |
||
|
Prompt and collect user information.
|
||
|
Protocol error detected in SINAP/INAP/CAP server. |
||
|
No data usage for a defined period of time. |
||
|
Subscriber barred announcement played before release. |
||
|
Subscriber barred announcement played before release. |
||
|
An undefined announcement played before release. |
||
|
Timeout waiting for the prepaid platform. |
||
|
Failue in looking up subscriber database. |
||
|
Invalid B-number. |
||
|
Tariff not found. |
||
|
Date proxy close received. |
||
|
Failure to find suitable rating entry. |
||
|
Insufficient balance. |
||
|
Reserve request amount exceeded. |
||
|
Error in indicated volume parameter. |
||
|
Error in indicated charging information parameter. |
||
|
Charging interface configurably blocked. |
||
|
Reservation has expired. |
||
|
Undefined network error. |
||
|
Undefined subscriber error. |