Manual

Cisco Packet Data Serving Node (PDSN) Release 2.0
Resource Management
14
12.3(11)T
The Ballot version mentions that a Disconnect Request can be received at the Home Agent (HA,) but
details on the action to be taken in such an event is not detailed. Hence the approach followed is to
terminate a specific binding if Framed-IP-Address attribute is received along with NAI, or terminate all
bindings for the NAI, if only NAI attribute is received in the Disconnect Request.
The following restrictions are present for this feature:
• Enabling and Disabling of Radius Disconnect support is allowed only when there are no sessions on
PDSN. This will be removed when tracking the STC per session is implemented.
• All Dormant NVSE are not supported.
The command line interface for this feature will be standard AAA interfaces.
The NAS global AAA command to enable listening for POD packets is:
• aaa pod server key word
where word is the shared key. The full syntax for this command is:
• aaa pod server [clients ipaddr1 [ipaddr2] [ipaddr3] [ipaddr4]] [port port-number] [auth-type
{any | all | session-key}] server-key [encryption-type] string
The following debug command is also available:
• debug aaa pod
Restrictions for RADIUS Disconnect
• RADIUS Disconnect capability configuration is allowed only when there are no sessions on the
PDSN.
• All Dormant NVSE is not supported.
• MIB support is not currently planned.
• STC attribute received in an Access-Accept message from AR will not be used to enable or disable
the Radius disconnect capability per user.
• Processing of a RADIUS Disconnect message with only NAI present must be configured for
compliance to IS 835-C.
• RADIUS Disconnect Feature is not redundancy aware.
IS-835 Prepaid Support
The Cisco PDSN 2.0 software release provides real-time monitoring and rating of data calls for prepaid
users. The prepaid billing solution for the PDSN is based on the RADIUS (AAA) server, and takes
advantage of the existing flow-based accounting functionality. The prepaid billing feature requires the
RADIUS server to interface with a Prepaid Billing Server (PBS) to relay real-time billing information
between the PDSN and the PBS. A third-party Prepaid Billing Server controls the real-time rating of data
calls and maintains balances in users’ accounts. Cisco does not supply the PBS.
The following three types of Prepaid service are available in PDSN Release 2.0:
• Volume-based Prepaid data service
• Volume-based Prepaid data service with tariff switching
• Duration-based Prepaid data service
Prepaid functionality is supported on PDSN for the following type of data sessions:
• Simple IP sessions with authentication and authorization performed at AAA.