3GPP Transaction Diameter Server CDR
The 3GPP Transaction Diameter Server CDR is generated when a request is made to the Diameter server.
1 |
|
The MSISDN of the subscriber. |
||
2 |
|
A unique ID number for the service. This is set to 50 for Content Retail Service service logic. |
||
3 |
|
Specifies the transaction type. values
|
||
4 |
|
The Diameter result code. |
||
5 |
|
The date on which the session started in the format YYYY/MM/DD. |
||
6 |
|
The time at which the session started in the format hh:mm:ss. |
||
7 |
|
The date on which the CDR was generated in the format YYYY/MM/DD. |
||
8 |
|
The time at which the CDR was generated in the format hh:mm:ss. |
||
9 |
|
Incremented for each CDR output for a given Diameter session.
|
||
10 |
|
The unique ID for the Diameter session. |
||
11 |
|
The host name of the Diameter client as defined in the Diameter Client configuration file.
|
||
12 |
|
The host name of the Diameter server as defined in the Diameter Client configuration file.
|
||
13 |
|
Specifies the Diameter termination code. codes
|
||
14 |
|
Indicates if the granted units are the final units in the subscriber account. values
|
||
15 |
|
Specifies the currency code. |
||
16 |
|
The requested unit exponent. |
||
17 |
|
Indicates the number of units requested from the Diameter server. |
||
18 |
|
The granted unit exponent. |
||
19 |
|
Indicates the number of units granted by the Diameter server. |
||
20 |
|
The used unit exponent. |
||
21 |
|
Indicates the number of used units since the start of the Diameter session. |
||
22 |
|
The requested time unit. |
||
23 |
|
The granted time unit. |
||
24 |
|
The used time unit. |
||
25 |
|
The requested service specific units. |
||
26 |
|
The granted service specific units. |
||
27 |
|
The used service specific units. |
||
28 |
|
The unique service context ID. |
||
29 |
|
A string allowing all the CDRs for this session to be correlated.
|