Understanding the AVPs for each of
these messages helps to understand the information available within the DIAMETER
protocol.
The originator of the ACR message is the network element (see Table 7.1). Specifically,
the CTF within the network entity creates the ACR when a billable event has occurred.
What is billable and what is not billable is determined by local policy. The destination
of this message is the offline billing system through the CGF. The CGF is responsible
for correlating all of the related CDRs and sending them on to the billing system.
176 Chapter 7
Parameter Status
Session-ID Mandatory, fi xed
Origin-host Mandatory
Origin-realm Mandatory
Destination-realm Mandatory
Accounting-record-type Mandatory
Accounting-record-number Mandatory
Acct-application-ID Optional
Vendor-specifi c-application-ID
Vendor-ID
Auth-application-ID (mandatory)
Acct-application-ID (mandatory)
Optional
User-name Optional
Accounting-sub-session-ID Optional
Accounting-RADIUS-session-ID Optional
Acct-multi-session-ID Optional
Acct-interim-interval Optional
Accounting-realtime-required Optional
Origin-state-ID Optional
Event-timestamp Optional
Proxy-info
Proxy-host
Proxy-state
Optional
Route-record Optional
AVP Optional
Event-type Optional
Role-of-node Optional
User-session-ID Optional
Calling-party-address Optional
Called-party-address Optional
Time-stamps Optional
Application-server
Application-servers-involved
Application-provided-called-parties
Optional (IMS S-CSCF only)
Application-provided-called-party-address Optional (IMS S-CSCF only)
Inter-operator-identifi er
Originating-IOI
Terminating-IOI
Optional
IMS-charging-identifi er Optional
TABLE 7.
Pages:
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362