Cisco Cisco Access Registrar 5.0 Guía De Información

Page 2 of 4

These methods also allow either offline transfers or direct feeds of accounting records into a billing server.

Cisco Access Registrar provides a special billing interface, allowing billing vendors to integrate their systems into Cisco Access

Registrar for prepaid functionality.

What are Cisco Access Registrar extensions?

Cisco Access Registrar provides a number of extension points where customers or system integrators may extend the logic of the

product via C/C++ shared libraries, Java, or TCL scripts. These extension points allow access to incoming and outgoing RADIUS

packets for complete processing control. Extension points also support the integration of completely proprietary authentication,

authorization, and accounting (AAA) services with a RADIUS front end.

Is Cisco Access Registrar compatible with equipment from other vendors?

Yes. Cisco Systems

maintains compatibility with the latest RADIUS standards to help ensure that Cisco Access Registrar is

interoperable with any RADIUS-compliant client, regardless of vendor. In addition, Cisco Access Registrar’s attribute dictionary

comes predefined with the attributes of many third-party vendors. Cisco Access Registrar’s dictionary is extensible•new attributes can

new attributes can

be added at any time.

Will Cisco Access Registrar support new AAA protocols such as Diameter?

Cisco monitors AAA standards progress, and participates in developing new AAA standards. Cisco aims to be at the forefront of AAA

technology and will consider supporting new protocols such as Diameter if it will benefit customers.

What, if any, additional software is needed to use Cisco Access Registrar?

Apart from a fully patched and supported version of the operating system, Cisco Access Registrar is fully self-contained. It has a fast,

built-in database that stores the server configuration and user information. No extra software is required to enforce user or group

session limits, allocate IP addresses from IP pools defined in Cisco Access Registrar, configure Cisco Access Registrar to act as a

RADIUS proxy, or to use the configuration replication feature.

Can Cisco Access Registrar process RADIUS requests differently based on attributes in the request?

Yes. Cisco Access Registrar can be configured to dynamically decide how to process requests based on any attribute in the packet,

including but not limited to, username prefix or suffix, dialed number, or calling number. An access request can be processed locally

using information in a Lightweight Directory Access Protocol (LDAP) directory server or an Oracle or MySQL database, forwarded to

another RADIUS server, or through a combination of these methods. An accounting request can be processed locally into a file,

forwarded to another RADIUS server, written to a database, or a combination of these methods.

Can Cisco Access Registrar be configured to modify attributes in a RADIUS packet?

In addition to the authorization process where attributes stored in Cisco Access Registrar’s internal database or external database are

returned in an access-accept packet, Cisco Access Registrar allows attributes in a RADIUS request, response, or proxy packet to be

added, modified, or deleted.

What session-management features does Cisco Access Registrar have?

Cisco Access Registrar is able to track user sessions. By tracking these sessions, Cisco Access Registrar can enforce session limits on

a per-user or group basis. It can also manage shared resources, including IP addresses, home-agent assignment, and on-demand

address pools (for Multiprotocol Label Switching [MPLS] VPNs).

Cisco Access Registrar maintains an in-memory table of active user sessions. It can be configured to store RADIUS attributes in the

session table. Cisco Access Registrar allows applications on the network to query this session table using either RADIUS or

Extensible Markup Language (XML) queries from the 4.1 release.