Cisco Cisco Access Registrar 3.5 - Manual (Page 61)

6-7
Cisco Access Registrar 3.5 Concepts and Reference Guide
OL-2683-02
Chapter 6 Prepaid Billing Solution
Generic Call Flow
In Flow 4s, the Cisco AR 3.5 server converts the quota array received into VSAs and sends an
Access-Accept with the assembled VSAs to the AAA client.
Table 6-5 lists the prepaid-specific VSAs
that might be included in the Access-Accept response message sent to the AAA client. For more detailed
information about the VSAs, refer to
Vendor-Specific Attributes, page 6-10 .
Flows 3c through 4s are repeated for every service started or restarted by the AAA client.
However, if the return parameters indicate that the authorization is rejected, an Access-Accept message
is generated and sent to the client as shown in
Table 6-6 . When this type of error condition occurs, no
other VSA is included in the Access-Accept message.
Accounting Start
In Flow 5c, the AAA client sends the Accounting Start. In Flow 6s, the Cisco AR 3.5 server replies with
the Accounting-Response.
Data Flow
At this point, the data transfer begins. The AAA client monitors the subscriber’s allocated quotas for
metering parameters. A subscriber’s Reauthorization request is generated when a quota for at least one
of the metering parameters, is depleted.
Table 6-5 Attributes Sent to AAA client in Access-Accept (Authorization)
Attribute
Number
Attribute Name
26, 9 CRB_DURATION
26, 9 CRB_TOTAL_VOLUME
26, 9 CRB_UPLINK_VOLUME
26, 9 CRB_DOWNLINK_VOLUME
26, 9 CRB_TOTAL_PACKETS
26, 9 CRB_UPLINK_PACKETS
26, 9 CRB_DOWNLINK_PACKETS
Table 6-6 Attribute Sent to Report Error Condition to AAA client
Attribute
Number
Attribute Name Description Notes
26, 9 CRB_TERMINATE_CAUSE Identifies why a
subscriber failed
authentication:
1. Exceeded the balance
2. Exceeded the overdraft
3. Bad credit
4. Services suspended
5. Invalid User
Conditional; rejection
might be returned with
Access-Accept and zero
(0) quota