SUPPORT - FAQ - PREVIOUS
VERSIONS
Microsoft SQL 6.5 or 7.0
Service Pack 5 for 6.5 or Service Pack 2 for 7.0
Microsoft Data Access Components 2.1 or 2.5
Microsoft Windows Scripting Host
Top
of the page
No , you can't. You must call RODOPI support to assist
you.
Top
of the page
It looks like your billing date is behind First you
need to check the current billing date with a following SQL script in
the AbacBill database:
select billingdate from commondata
Then run the RODOPI Daily Billing Procedure once for EVERY day that is
Missing
For SQL Server v6.5:
Server | Scheduled Tasks Right Mouse Click on RODOPI Daily Billing |
Run
For SQL Server v7.0:
Go to Management | SQL Server Agent | Jobs Right Mouse Click on RODOPI
Daily Billing | Start Job
DO NOT run more than one instance of the Rodopi Daily
Billing procedure at a time.
Top
of the page
If you like to get rid of some customer, simply change
his/her first and last name to "test", then perform the next
steps:
1. From the SQL Enterprise Manager open SQL Query Tool
from the Tools menu ( or for version 7.0 open SQL Query Analizer).
From the list box at the top of the Query window select the AbacBill
database.
2. Type the following command in the query window. It will completely
delete all Customers with first and last name that begin with
"test" (like "Test X. Tester"):
-----------
execute Admin_DoNotUse_DelTestCust 'qwerTy'
-----------
3. Then press Ctrl+E to execute the command.
Top
of the page
If you see this error when accessing any of the RODOPI
Subscription or Maintenance or Administration pages then:
To configure the connection between the web
interface and the database as well as between the "RODOPI
Server" service and the database you need to run "RODOPI
Configuration Utility". Go to Start / Programs / RODOPI /
RODOPI Server Configuration. You will see the directory where RODOPI
is installed. The SQL Server will be the Windows name of the
computer, network library will be named pipes, username 'RODOPI'
with password 'RODOPI'. Click save. You should receive message
"Data saved successfully". After this you will be able to
access the RODOPI database through the web interface.
You can use also TCP/IP sockets for network library,
the SQL Server will be the IP address of the SQL Server. In this
case you need to setup first the SQL Server to listen for TCP/IP
sockets connections. Start SQL Setup and select change network
support. Add TCP/IP sockets. Restart the SQL Server from Control
Panel Services or from the SQL Enterprise manger.
If the error is in the Ticket System or the knowledge
base module:
Not enough permissions in inettech sub-directory
will cause this error. Everyone full control may confuse the web
server. Try to set permissions for the anonymous internet account
which is IUSR_COMPUTERNAME. This user should have read and execute
access to all files and directories in the InetTech directory. For
more information you can look here: http://support.microsoft.com/support/kb/articles/q190/0/06.asp
Top
of the page
If for some reason the Daily Billing task is
not running you will have some billing days missing. The reason for
this can be that the SQL Executive service is not running or the
scheduled task RODOPI Daily Billing is not enabled or the task
is failed (you will see the reason in the history of the scheduled
task). Indications that the Daily Billing task is not running
can be that there are no rows in the statements of the new customers.
Also there will be no automatic credit card charges and no recurring
charges will be calculated.
To find what is the current internal billing date just
find some customer in Filter Search , then click on the
radius button near to the customer and click Transactns.
Select payment type Credit Adjustment. Type amount $1. Type
the password for Credit Adjustment. Click Apply. The
new statement will show one new row with:
|
Feb 22, 1999
|
Credit Adjustment -- -- Thank You
|
1.00
|
CR
|
|
If the date on the left is not the current date then
you have missing billing days. To remove the test row just apply Undo
Last Transaction payment type for $1 and password for Credit
Adjustment.
To correct the billing date you need to run the task RODOPI
Daily Billing once for every missing day. If you need to run this
task more than once (you missed more than one day of billing) you need
to run the task , wait until it finishes and check the history
(status). If successful run it again. DO NOT run two
instances of the task at the same time, because double billing can
occur. When you receive message in the history: "Invalid Billing
time" this will mean that the billing date is correct and the
task will not start for future dates. For more information look
here:
If the Billing date is correct (when you apply payment
you see the today date), but when customers subscribe invoices are
still not generated then the problem is that you have broken
identities in one or more database tables. To correct this run the
script that will fix it. Follow the instructions here:
Top
of the page
The SQL Server reads the invoices and the statements
from the web server and then sends them via your SMTP server to the
customers using their contact email from the customer information. You
need to specify valid URL to your web server in
Administration/Configuration, section Internet Settings, field
"This WWW Server". Valid values are:
http://computername.yourdomain.com
or
http://265.23.4.34
or
http://computername:portnumber
To test the connection, go to the SQL Server computer
and open internet explorer. Type the value from "This WWW
Server" and add /cgi-bin/olsplus/invoices.exe?invoicenum=1 , then
press enter. You should NOT be asked for username and
password and the result should be something like:
|
Invoice
number! : Authorization failed.
|
|
If you have this result, it is OK. This means that the
SQL Server can connect to the Web server.
Other test you can make with this SQL Script:
----------------------------------------------------------------------------
Use Abacbill
declare @url varchar(255)
declare @ret int
select @URL = ThisWWWServer + '/cgi-bin/olsplus/invoices.exe?InvoiceNum=1'
from setupdata5
select @URL
exec @ret = Comp_CheckURL @URL = @URL, @Check = 'Invoice number!'
if @ret = 0 select 'success'
else select 'error'
------------------------------------------------------------------------------
If the result is success then the SQL Server
can read the invoices and statements from the Web Server.
Also the field "SMTP Server:" in
Administration/Configuration, section Internet Settings should
be correct. The SQL server is using this SMTP Server to send the
emails.
Top
of the page
Yes, See RODOPI
5.0 Online Help
Error 202 means that the URL to the directory where
the event script should be uploaded is not correct. Check all URLs of
the event scripts. Copy and paste them in internet explorer for test.
Top
of the page
These instructions assume that the old SQL Server and
the new SQL Server are the same version. In case you need to upgrade
from SQL 6.5 to SQL 7 computer you need to use the Microsoft upgrade
wizard.
The transfer can be done with backup of the RODOPI
databases AbacBill , AbacPay from the first machine then restore on
the second machine.
The following SQL statement will do the backup:
---------
exec abacbill..Util_maintRodopi 3
--------
You will find the backup files in the \RODOPI\Backup
directory. They
will have names like:
AbacBill_db_dump.199811080003
AbacPay_db_dump.199811080005
INetTech_db_dump.199811080005
Look for the last created files.
Before the transfer, on the second machine you need to
install RODOPI database only (from the installation file - select
custom install -> New Database) Copy the backup files on the new
machine and restore the databases. You can do this from the SQL
Enterprise Manager. Right click on the database that you need to
restore and click backup/restore. Click restore. Check the Enterprise
Manager documentation for more information how to restore from backup.
NOTE*
You may receive error
message when you try to restore: "[SQL Server]
Database is in use. System Administrator must have exclusive use of
database to run load." To fix this you need to stop
all SQL processes attached to the AbacBill database.
Go to Server/Scheduled Tasks and disable the "RODOPI
Procedures" task. Go to Control Panel / Services
and Stop the RodopiServer Service. Restart the SQL Server
from Services or From the SQL Enterprise Manager. Connect to the SQL
Server with the Enterprise Manager and try to restore again. When
successfull enable the Scheduled task "RODOPI
Procedures" and Start the RodopiServer Service.
After you restore the databases run the following script to set the
new backup directories.
-------------------------
update abacbill..setupdata
set BackupDir='E:\Rodopi\Backup\', LogDir='E:\Rodopi\Log\'
-------------------------
Replace 'E:\Rodopi\Backup\' and 'E:\Rodopi\Log\' with
your data.
Go to the web server ( where RODOPI web interface is
installed) and set it to connect to the new SQL Server . It is in
Start / Programs / RODOPI / RODOPI Server Configuration, then change
the SQL Server name. Click Save. Go to Administration / Configuration
and check the data.
Top
of the page
First check for error messages in Rodopi Main Menu /
Filter Search. Select "Procedures" from the dropdown box
"Search Criteria" and and hit the "Search"
button. The result should be like:
Top
of the page
When your database begins to grow you will need to
expand the Rodopi database AbacBill. First you need to expand the
database devices, then the database size and the transaction log on
the devices. For Rodopi you need to expand the database devices
RodopiData.dat and RodopiLog.dat. You can do this from the SQL
Enterprise Manager. Open The SQL Server and go to "Database
Devices". Open the RodopiData device. Expand. Open the RodopiLog
device. Expand. Go to "Databases". Open AbacBill database.
Click Expand. For data device select
RodopiData. For log device select RodopiLog. Click Expand
Now.
From the SQL Enterprise Manager you can see how much space is
available for the data segment and for the log segment. To do this go
to databases and double click on the AbacBill database. Look at
"Data Space Available" and "Log Space Available".
If it is near 0 you need to expand it.
Top
of the page
You need to truncate the transaction log or expand it
if you have many customers and the default size of 30MB is not enough.
* To truncate the transaction log go to Databases and
double click on AbacBill database. Click Truncate. Check the Log
Space Available. If still 0 click on Recalculate. Check
again the Log Space Available. If still 0 close this window
and go to Tools / SQL Query Tool. Select the AbacBill database. Type
command:
DBCC CHECKDB
Execute with ctrl-e. Go back to databases and truncate
the transaction log again and press Recalculate. It should be
OK.
* To expand the transaction log go to database
devices. Double click RodopiLog device. Expand. Go to databases.
Double click on AbacBill database. Click Expand.
Select Log Device: RodopiLog. The maximum size is on the
left, you can change it or leave it. Click Expand now.
Top
of the page
Sometimes when you shutdown your SQL Server not
properly (power failure for example) and the SQL Server Service is not
stopped gracefully on shutdown you will have some tables identities
corrupted. You will receive error messages with the web interface and
not only similar to:
"Violation of %s constraint '%.*s': Attempt
to insert duplicate key in object '%.*s'."
To correct this run the script in SQL query tool from
the SQL Enterprise Manager for all corrupted databases. At least you
should run the script in AbacBill , AbacPay and InetTech databases.
---------------
DECLARE @tblname varchar(50)
DECLARE CurIDTables CURSOR FOR
SELECT sysobjects.name
FROM syscolumns
JOIN sysobjects ON syscolumns.ID = sysobjects.ID
WHERE (syscolumns.status & 128) = 128 AND sysobjects.type =
"U"
OPEN CurIDTables
FETCH NEXT FROM CurIDTables INTO @tblname
WHILE (@@FETCH_STATUS = 0)BEGIN
DBCC CHECKIDENT (@tblname)
FETCH NEXT FROM CurIDTables INTO @tblname
END
CLOSE CurIDTables
deallocate CurIDTables
-----------------
Top
of the page
Web Server security:
You have to secure the following physical
sub-directories in the main Rodopi directory on the Web Server (usualy
C:\Rodopi):
-- olsmaint
-- olsmaint-cgi
-- olsadmin-cgi
You can set Administrators access only for the 'olsadmin-cgi'
folder. Administrators and Billing for the 'olsmaint'
and 'olsmaint-cgi' folders. Administrators
should have "Full Controll" and the Billing users
needs only "Read&Execute". You can apply
secutity only on NTFS drives.
You have to allow anonymous access to the following physical
sub-directories:
-- olsplus,
-- olsplus-cgi,
-- usage-cgi,
-- inettech
If the annonymous user (usually IUSR_COMPUTERNAME) does not have
access to 'olsplus-cgi' then the SQL Server will not be able to send
invoices and statements by email.
The following physical sub-directories are not
published from the WEB
server and they may have Everyone "Full Control":
-- backup
-- log
In this directories the SQL Server is doing backups so make sure that
the system account have full control.
The main Rodopi folder ( i.e C:\Rodopi ) and the files
in this main folder should have Everyone Read&Execute, because the
DLL's are accessed from the CGI's and the Rodopi Server service is
running from this folder.
For security reasons do not allow any web hosting or
shell access on the computer where Rodopi is installed.
SQL Server security:
You need to change the password for the SQL login
rodopi. To do this you need to go to the SQL Enterprise Manager,
open your SQL Server, open Logins, double click on the rodopi
login and change the password. After this you need to go to your Web
Server computer and open the Rodopi Server Configuration Utility.
Change the password with the new one. Save. You need to do this also
on the computer where the 'Rodopi Server' component is instaled if it
is on different machine.
Also make sure that the Sa login in the SQL Server is not
with empty password. The default SQL Server installation will create Sa
login with empty password, so you need to change it later.
Top
of the page
First check the URLs in Administration / On-line Usage
URLs. All URLs should be correct. If the URL is:
ftp://login123:password123@authentication-server/directory/details-file
Then you should be able from the SQL Server computer
to open Command Prompt and ftp to the specified location using the
same username and password.
If you can execute all this commands from the command
prompt of the SQL Server machine then your URL is correct and Rodopi
can import the usage.
The usage is imported when the daily procedure starts.
If you don't want to wait you can force the importing of the usage.
Go to the SQL Server and open your SQL Server. Open SQL Query Tool and
select the AbacBill database. In the Query Window type:
exec Usage_OnlineHours
To execute click the green arrow or press ctrl-e. This
command does not produce output and the result will be: 'This
command did not return data, and it did not return any rows'. If
your detail files are very large it can take longer for the procedure
to finish the execution. To find what is imported in the database use
the SQL statement:
select * from AbacBill..UsageOnlineHours
After your detail files are imported they will be
renamed to something like:
old_detail_19992342345324
If they are not then they are not imported and you need to check the
URLs. For more information check
here:
Top
of the page
First prepare the email from the Administration /
Letters / Select letter type: Miscellaneous:
| Miscellaneous |
|
|
| |
| |
|
|
| Subject: New
phone numbers |
Dear customer
...
...
|
|
|
Next go to Managerial / Marketing Reports. Select
"Plan Status" from Reports drop-down box. Select start date
something in the past, for example: 01/01/1981. Click Generate.
You will receive the number of all your active
customers. Click on the radio button near "Count" and click
"Add". This operation will add the customers to the Pool.
For more information about the Pool look
here.
Specify Reply To Name, Reply To Address,
E-mail Subject and type the password for sending emails. The
password can be set in Administration / Configuration section
"Other" - Send Letters Password.
Click "Send". The email will be send at
night when the "Daily Billing Procedure" starts.
Top
of the page
There are two ways to create tickets from email in
Rodopi:
1. Use the Ticket Service that is integrated in
Rodopi. How to setup this service? Look
here.
2. Rodopi can import email tickets from Unix mail server like
sendmail or other that supports .forward file with pipe command. You
will need to install the packet es02d.tgz
with the event scripts for Unix. If you are already using it begin
with b).
a) Download es02d.tgz
and README
files. Follow the instructions in the README file. Here you will find
installation instructions how to setup Mail Scripts on your Unix
machine.
b) Download Event_Message_Import.exe
Save in the \Rodopi\usage-cgi\ folder.
c) Download and execute SQL script in your
Rodopi database. The script is here.
d) Here you have the packet with the event scripts
installed.
This line should be put in the ~username/.forward
file for the account you want logged:
|/usr/local/rodopi/lib/message_logger.pl
Now when the user username receives
email, the message will go thru the perl filter and will generate xml
document in the /usr/local/rodopi/logs/messages directory.
Look in the body of message_logger.pl if you
have perl experiences and you want to find how it works. Next step is
to configure the usage filter from the Rodopi web interface.
e) Go to Rodopi Administration|Tech Support|Tickets
from Email. Add Email Address to which your customers will send
support email messages and define the support user to whom the Ticket
System will assign tickets created from this e-mail. For
example, in the table below, tickets created from support@yourdomain.com
address will be assigned to the ticket system user demouser:
|
Email Address
|
Description
|
Assign to user
|
|
|
support@yourdomain.com
|
Company Support Email
|
demouser
|
|
f) Go to Administration|Usage Filters|Filter
Installations. To the Default Usage Filter add Usage Filter
Installation URL: http://MyRodopiServerIPaddressOrName/cgi-bin/usage/Event_Message_Import.exe.
This is the default place where the Filter is installed. Then click on
the Logs button next to this installation. New window - Usage
Logs will come and there click the Add button to add log
file URL. Example:
ftp://rodopi:secret@mailserver.yourdomain.com/usr/local/rodopi/logs/messages
For Mask type *.xml, for
Delay parameter choose preferred time interval (30 minutes), for Next
Run choose 1/1/99 so it will run
immediately. For Parameters define LogFileType – MESSAGES, and
MaxCount – 100. Leave CommonIPHost Field empty. Save changes.
See following example:
|
Filter Description:
|
Default Usage Filter
|
|
Filter Installation URL:
|
http://MyRodopiServerIPaddressOrName/cgi-bin/usage/Event_Message_Import.exe
|
|
|
|
|
Parameters:
|
|
Name
|
Value
|
|
CommonIPHost
|
|
|
LogFileType
|
|
|
MaxCount
|
|
|
|
Top
of the page
Yes, you can integrate Rodopi with your MS DNS Server.
Rodopi supports the two main standards for the DNS boot file (BIND 4
& BIND 8). You need to configure your MS DNS Server to use boot
file instead of using the Registry. Then you have to set Rodopi to
upload file in BIND 4 format with name and location:
%SystemRoot%\system32\dns\boot
You can make your Microsoft DNS service boot from the text files
rather than from information stored in the registry by following these
steps:
Use REGEDIT.exe or REGEDT32.exe
to edit the registry.
Go into the registry to the value:
HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Services
DNS
Parameters
EnableRegistryBoot
Change the EnableRegistryBoot value from 1
to 0. The DNS service will now use the text file BOOT to initialize
the MS DNS service.
Top
of the page
When trying to create the RADIUS file you may get an
error and here is what you can see in Filter Search under Procedures:
Create RADIUS file 08/02
00:01:01 OLE Error -101! Description: Invalid
class string
For some reason the AbacBill.dll is not (or not
properly) registered. Please go to the computer where the SQL Server
is installed and open Command Prompt. Go to the Rodopi folder and
execute:
regsvr32.exe AbacBill.dll
You should receive message "Registered
Successfully".
Top
of the page
Common operation is to create a virtual domain in your
web server for a customer with a web hosting plan. Also you will
create a shell account on the same server and grant permissions for
this shell name to update the files for this domain.
This customer in Rodopi will be presented with a plan
that has 1 domain , 1 shell and optional number of emails:
Now when the customer is in Rodopi you may want to
have domain insert script and shell insert script to automatycally add
the user and the web domain to your web hosting server.
The domain insert event script has the following
keywords:
@New_EmailAddress@, @New_Password@, @New_RealName@, @New_PopName@
The shell insert event script has the following
keywords:
@New_UserName@, @New_Password@
The problem here is the there is not shell username in
the domain script and no domain name in the shell script. If you want
to use the username in the domain script you will need to get it from
somewhere else , not from a keyword and this is what we will do.
In addition to the keywords specific to the event in
all the scripts you can use these common keywords:
@PlanInfoId@, @PlanId@, @RegNumber@
The @PlanInfoId@ keyword will give you the planinfo
number. For example if you have plan "Unilimited dialin"
|
ID
|
Description
|
Setup
|
Price
|
L
|
S
|
E
|
D
|
Visible
|
|
|
12
|
Unilimited dialin
|
5.00
|
5.00
|
0
|
0
|
1
|
0
|
yes
|
|
|
2
|
Sample Unlimited Basic Dialin (1 login, 1
email)
|
10.00
|
20.00
|
1
|
0
|
0
|
0
|
yes
|
|
|
3
|
Sample Unlimited Business Dialin (1 login, 5
emails)
|
15.00
|
30.00
|
1
|
0
|
4
|
0
|
yes
|
|
|
4
|
Sample Unlimited ISDN
|
20.00
|
40.00
|
1
|
0
|
4
|
0
|
yes
|
|
|
6
|
Sample Web Hosting
|
35.00
|
50.00
|
0
|
1
|
1
|
1
|
yes
|
|
|
1
|
Radius Profiles
|
0.00
|
0.00
|
255
|
0
|
-255
|
0
|
no
|
|
This PlanInfoID number is always 12 in this
configuration. We don't need this number for our case. It is explained
only to prevent from using it for wrong purposes.
The @PlanID@ keyword is the internal number of the
customer plan (that we need). For example when customer subscribe for
a plan "Unlimited Dialin" with @PlanInfoId@ = 12 the @PlanID@
keyword wil be integer number that will be the same for all the event
scripts executed for this plan.
The @PlanID@ keyword is what we need to retreive the
shellname and use it in the domain insert script.
Let say we have two scripts. One shell insert script
and one domain insert script. The customer subscribes to a web hosting
plan that has 1 shell and 1 domain. In this case two scripts will be
fired for this plan. We will show example for windows NT environment:
The most interesting line here is:
echo @New_UserName@ > %TEMP%\@PlanID@.dat
This way the first script will create the account and
will save the shellname for later use from other scripts coming from
the same plan. The username will be in file in the temp folder with
name for example:
C:\TEMP\1230.dat
Next we will create the domain insert script:
The file called grantperm.bat
can be this:
The file called mkftpdir.bat
can be this:
This way with the @PlanID@ keyword we
can exchange parameters between event scripts. The order of running
the scripts is important in this case. Rodopi should upload first the
shell script then the domain script. To acheive this we specified
order 1 for the shell script and order 10 for the domain script The
process of your other server that is executing all uploaded scripts
should execute first the shell scripts then the domain scripts.
Simular scripts you can use for Unix servers.
Note: The
sample scripts are presented here only to explain the programing
technics. We did not tested the scripts in production enviroinment and
they may need modifications to work on your server.
Top
of the page
In this article we will explain how Rodopi interacts
with various Radius servers. How to configure Rodopi with your Radius
and how to use different Radius Profiles for different services ( PPP
dialin, ISDN dialin, Static IP dialin, etc...).
Rodopi as billing software for Internet Providers
interacts very actively with the Radius Server. First we will explain
how Rodopi comunicates with different Radius Servers and next we will
explain how to set different Radius Templates.
1. Radius Servers
a) Livingston compatible Radius Server.
In case of Livingston compatible Radius server Rodopi
will generate plain text users file and will save it to FTP of
local disk location specified by you. The radius Server will use this
users file for authentication.
The location of the users file is set in the
Administration/Configuration page in the section Radius Settings:
If you need more help how to specify the location or
if you need each field explained look
here:
This is sample users file:
# 930501103 -- James Bond
jamese Password = "65gg78"
User-Service = Framed-User,
Framed-Protocol = PPP,
Ascend-Shared-Profile-Enable = Shared-Profile-No,
Ascend-Maximum-Channels = 1
# 871836979 -- James Martin
jamesm Password = "jjhf45"
User-Service = Framed-User,
Framed-Protocol = PPP,
Ascend-Shared-Profile-Enable = Shared-Profile-No,
Ascend-Maximum-Channels = 1
# 916933098 -- James Nooiu
jamesn Password = "ncdhjvf"
User-Service = Framed-User,
Framed-Protocol = PPP,
Ascend-Shared-Profile-Enable = Shared-Profile-No,
Ascend-Maximum-Channels = 1
The first line with the # sign is a comment. The
Radius Server will ignore it. Rodopi will put the customer RegNumber
and first and last name there. Next line begins with username. On the
same line are all the CHECK items. All the REPLY items are listed
next, each on separate line. Two new line characters separate the
users profiles.
Any Livingston compatible Radius server will be able
to authenticate from this users file.
b) Vircom Radius Server
With the Vircom Radius server Rodopi is directly
integrated. The Vircom Radius will directly authenticate from the
Rodopi database and will log accounting directly in the Rodopi
database with ODBC. No files are used. The Vircom will read also the
Radius Template for each dialin from the Rodopi Database.
You do NOT need to specify location, password mask or
Radius users file history in the Administration/Configuration page in
the section Radius Settings because they are not used. Only you need
to specify "Online Usage History".
c) Steel Belted Radius Server
With the Steel Belted Radius Rodopi is also directly
integrated. The Steel Belted Radius will authenticate directly from
the Rodopi database and Steel Belted Radius can directly log
accounting into the Rodopi database. The Steel Belted radius will NOT
read the radius Attributes from the Rodopi database. Only the Profile
name will the received from the Rodopi database. The Attributes for
this Profile are be defined in the Steel Belted configuration.
You do NOT need to specify location, password mask or
Radius users file history in the Administration/Configuration page in
the section Radius Settings because they are not used. Only you need
to specify "Online Usage History".
d) Other Radius Servers
In case you have Radius Server that is not Livingston
compatible and is not Vircom or Steal Belted you still may be able to
use it with Rodopi. You can automate the dialin account creation with
event scripts. We have example in our event scripts sample library how
to use Rodopi with the NT RAS here
2. Radius Templates
a) What are Radius Templates in Rodopi?
Rodopi comes with 3 predefined Templates: TemplateDefault,
PPPDefault, RouterDefault.
For every Service Plan ( Plan Info) you can assign one
template. This way when the customer is subscribed for this Service
Plan, all his/her dialins will automatycally inherit attributes from
the Template assigned to this Plan. The Templates can be assigned to a
Service Plan from the "Administration / Service Plans / Plan Info
/ List Plans and their profiles":
b) How to assign attributes to a Radius
Template in Rodopi?
First make sure that all radius Attributes that you
will need are in Rodopi. To check this go to the
"Administration/RADIUS Attributes" page. In the table you
should find all attributes that you will need. If some attribute are
missing just add by using Add button on the upper right corner of the
table. For every attribute you can specify check item and/or value in
quotes.
Next step is to assign attributes to Templates. Go to
the Rodopi Main Menu and click on the link "Radius Attributes
Editor" from the "Maintenance" section. Click on the
Default Template tab to see a list of default profiles in Rodopi. Then
click Edit if you want to edit existing profile or Add if you want to
edit a new one :
|
Radius Attributes Editor - Edit
Template
|
Help
|
|
This way you can add or remove attributes from the
Profile.
If you need to assign individual attributes to
special dialin just click on the Individual Profile tab from Radius
Attribute Editor page. Then enter login username in the Login
field and click Load button. Individual profile for the user will be
loaded in "Radius Attributes Editor" page and you can edit
the attributes of this profile.
Note*
You can not specify attributes in Rodopi if you are using Steel
Belted or non compatible Radius server that is integrated with event
scripts. In this case you need to specify the attributes in the
Radius Server configuration.
Top
of the page
You will need the domain name in case you integrate
Imail mail server with event scripts. This is how the insert email
script can be created:
File Script, AccountType: Email, Event Type:
Inserted:
C:\IMAIL\adduser -u @New_PopName@ -h
readyconnect.com -n "@New_RealName@" -p @New_Password@
The script is sent via FTP to the mail server where it is executed
to add a new user.
The problem comes from the fact that the adduser.exe command
requires the -h (hostname) parameter (in the example hardcoded:
readyconnect.com) which doesn't have own keyword.
Look like we need to extract the domain name .from
the email address only. And we are using command script. There is
easy way to extract the domain name from the email address using
only some commands from command script. Example:
echo @New_EmailAddress@ > %TEMP%\tmpdom.tmp
for /F "tokens=2 delims=@@" %%i in (%TEMP%\tmpdom.tmp) do
SET HOSTDOMAIN=%%i
C:\IMAIL\adduser -u @New_PopName@ -h %HOSTDOMAIN% -n "@New_RealName@"
-p @New_Password@
Note*:
You see two @s (@@) in the script near delims because the Rodopi
will remove one of them when saving the script to the remote
location. The script executed will have only one @.
Note**:
Imail Mail server can be setup tp authenticate directly from the
Rodopi database with ODBC and SQL view. In this case you don't need
event scripts.
Top
of the page
To email support: support@rodopi.com
