Application Assurance (AA) Accounting
Page 216 7750 SR RADIUS Attributes Reference Guide
Table 66: Application Assurance Accounting (limits)
Attribute ID Attribute Name Type Limits SR OS Format
1 User-Name string 32 chars # format varies with the aa-sub type
For example:# sap formataa-sub : 1/1/6:61.2# spoke-
sdp formataa-sub : 4:100# esm or transit formataa-sub
: user1@domain1.com
4 NAS-IP-Address ipaddr 4 Bytes For example:# ip-address 10.1.1.1NAS-IP-Address
0a010101
32 NAS-Identifier string 32 chars For example:NAS-Identifier = PE1-Antwerp
40 Acct-Status-Type integer 4 1=Start, 2=Stop, 3=Interim Update, 7=Accounting-
On, 8=Accounting-Off
44 Acct-Session-Id string 22
Bytes
<subscriber-type>|<Alc-Subsc-ID-str>where
<subscriber-type> = esm or transit
For example: Acct-Session-Id = esm|ipoe_sub_08
49 Acct-Terminate-Cause integer 4 Bytes # Supported causes: 1=User-Request, 2=Lost-Carrier,
3=Lost-Service, 4=Idle-Timeout, 5=Session-Timeout,
6=Admin-Reset, 8=Port-Error, 10=NAS-Request,
15=Service-Unavailable# See table Acct Terminate
Cause for complete overview
For example:Acct-Terminate-Cause = User-Request
55 Event-Timestamp date 4 Bytes For example:# Jul 6 2012 17:28:23 CEST is reported
as 4FF70417Event-Timestamp = 4FF70417
26-6527-11 Alc-Subsc-ID-Str string 16 char <aa-subscriber text name>
For example: Alc-Subsc-ID-Str = ipoe_sub_08
26-6527-19 Alc-Acct-I-Inprof-
Octets-64
octets 10
Bytes
<Type of second byte 1 Byte><export-id 1 Byte><8
Byte value>
Where:
<Type of second byte> = 0x40 indicates byte 2 is AA
charging-group export-id
<Type of second byte> = 0x50 indicates byte 2 is AA
app-group export-id
<Type of second byte> = 0x60 indicates byte 2 is AA
application export-id
<export-id> =<1..255>
For example: 500 bytes reported in CG id 2
Alc-Acct- I-Inprof-Octets-64 =
0x400200000000000001f4