Transaction Diameter Server CDR
The Transaction Diameter Server CDR is generated when a request is made to the Diameter server.
1 |
|
A unique ID number for the service. This is set to 50 for Content Retail Service service logic. |
||
2 |
|
Specifies the transaction type. values
|
||
3 |
|
The date on which the CDR was generated in the format YYYY-MM-DD. |
||
4 |
|
The time at which the CDR was generated in the format hh:mm:ss. |
||
5 |
|
A string allowing all the CDRs for this session to be correlated.
|
||
6 |
|
The MSISDN of the account holder to be debited.
|
||
7 |
|
The Transforma Diameter Server result code. values
|
||
8 |
|
The Diameter result code sent from the OCS. |
||
9 |
|
The interface used for charging the OCS.
|
||
10 |
|
Specifies the currency code. |
||
11 |
|
The requested unit exponent. |
||
12 |
|
Indicates the number of units requested from the Diameter server. |
||
13 |
|
The granted unit exponent. |
||
14 |
|
Indicates the number of units granted by the Diameter server. |
||
15 |
|
The used unit exponent. |
||
16 |
|
Indicates the number of used units since the start of the Diameter session. |
||
17 |
|
The requested time unit. |
||
18 |
|
The granted time unit. |
||
19 |
|
The used time unit. |
||
20 |
|
The requested service specific units. |
||
21 |
|
The granted service specific units. |
||
22 |
|
The used service specific units. |