<AuthBy RODOPI> provides authentication and accounting using the
popular Rodopi ISP billing package. It is available on
Rodopi website. The
combination of Radiator and Rodopi provides a very powerful and easy to
use ISP billing and user management system. You will be able to add users
to Rodopi, and they will be able to log in immediately. Changing their
password takes effect immediately, and all user logins details are
available as soon as they are completed: no need to import accounting
files.
Rodopi uses Microsoft SQL Server for its user database, so in order to
make Radiator work with Rodopi on Windows, you will usually need to
install an ODBC driver, plus the Perl DBD-ODBC module. On Unix, you will
need to install DBD-Sybase and the Sybase client library to allow Radiator
to connect to Microsoft SQL Server.
During authentication, Radiator checks the password in the Rodopi
“Logins” table. It also gathers radius check and reply attributes from the
RadiusUsers table.
<AuthBy RODOPI> will connect to the Rodopi database as the user
you specify in the DBUsername parameter. The default user name that Rodopi
installs is “Rodopi”, with password “rodopi”.
During accounting, Radiator logs call details from each Accounting
request to the Rodopi “UsageOnlineHours” table.
<AuthBy RODOPI> automatically handles Cisco VOIP authentication
and Accounting with the Rodopi 5.4 or later Cisco VOIP support. RADIUS
requests that contain the cisco-h323-conf-id attribute are handled with
the VOIP stored procedures. All other requests are handled with the
non-VOIP procedures.
There is an example Radiator configuration file for Rodopi in
goodies/rodopi.cfg. You should use this as the
starting point for configuring Radiator to work with Rodopi.
<AuthBy RODOPI> understands exactly the same parameters as
<AuthBy SQL>. For more information, see
Section 3.41.
# Authenticate everyone with Rodopi using the ODBC
# DSN called "Rodopi"
<Realm DEFAULT>
<AuthBy RODOPI>
DBSource dbi:ODBC:Rodopi
DBUsername Rodopi
DBAuth rodopi
</AuthBy>
</Realm>