• User
  • Downloaded 685 times
  • Metalink
  • QR


Number of files: 1


Allot-RODOPI 5.2.

Billing Integration.

Installation and Configuration Guide.

Author Kaputkin Evgeny

Document Type

Date Created July/30/2001

Date Modified

Version 1.0

Status First Draft

Security Company Confidential


Table of Contents






5.1 Hardware 6

5.2 Software 6

5.3 Configuration 6

5.4 Billing Interfaces 6



7.1 Microsoft SQL Server 2000. 8

7.1.1 SQL SERVER 2000 8

7.2 RODOPI 5.2 9

7.3 Bandwidth Manager 9

7.4 Defining ODBC Data Sources: 11


8.1 RODOPI 5.2 Configuration 14

8.1.1 Licensing. 15

8.1.2 Service Plans Creation. 16

8.1.3 Event Scripts. 23

8.1.4 LDAP Server Configuration. 26

8.1.5 Creating New Account. 26

8.2 NetEnforcer Configuration 31

8.2.1 NetEnforcer LDAP Server Configuration. 31

8.2.2 NetEnforcer RADIUS Configuration. 33

8.3 LDAP Configuration 33

8.4 RADIUS Server Configuration 33





1 History

Rev Date By What


2 References

Name Version Comment

Netscape LDAP Server installation guide.doc Installing and customizing LDAP server for the NetEnforcer’s billing tasks.

Steel-Belted Radius installation guide.doc Installing and customizing the Steel-Belted Radius server for the NetEnforcer’s billing tasks.


3 Purpose

This document will describe in details the installation and configuration of “RODOPI 5.1.” Billing System (from RODOPI SOFTWARE) and configuration against Allot’s NetEnforcer to provide complete end-to-end billing solution.

It’s dedicated to all developers/system integrators/QA personnel that handle with Allot/RODOPI billing integration.

4 General

The term “Integration” with Customer Care & Billing Systems (CC&B) means to provide easy working interface between NetEnforcer and CC&B in both directions:

· Accounting of traffic (usage) data from NetEnforcer to the Billing System side for rating and billing the customers.

· Provisioning (activating)/updating of the new customers (accounts) and services from the Billing system side to the NetEnforcer.

5 Software and Hardware Requirements

This document was created as a result of a real integration, which was done by Allot and Rodopi engineers for Rodopi 5.2 and Rodopi Bandwidth Manager  (for RODOPI 5.2) (Windows NT version).

5.1 Hardware

Any Pentium III PC running Windows NT Server.

5.2 Software

Operating System: Windows 2000 Server.

Web Server: Microsoft IIS 4.0 (or later) Web Server

Web Browser: Microsoft Internet Explorer 5.0

Database: Microsoft SQL Server 2000

Billing System: RODOPI v. 5.2

Additional integration

modules from “RODOPI”: Bandwidth Manager for RODOPI 5.2

RADIUS Server: Steel-Belted RADIUS Server v. 2.27 (Funk Software)

Directory Server: Netscape 4.0 Directory Server (LDAP).

5.3 Configuration

Current implementation is based on local configuration where all system components are running on the same host.

5.4 Billing Interfaces

There are two directions to interface between the Allot NetEnforcer and RODOPI Customer Care & Billing System (CC&B):

1. Account activation in CC&B and automatic customer provisioning in the NetEnforcer.

For these purpose LDAP server is used as an intermediate repository between the CC&B and the NetEnforcer.

2. Collecting of the customer usage data from the NetEnforcer into the CC&B.

An export of the customer usage data is implemented by the use of RADIUS Server that will export this data in the near real time from the NetEnforcer to the CC&B

6 Assumptions

This document is mostly dedicated to the installation and configuration of all required system components except of the Steel-Belted Radius Server and  Netscape 4.0 LDAP Server installation and configuration.

These issues are deeply covered in the following documents:

”Netscape LDAP Server installation guide.doc”

“Steel-Belted Radius installation guide.doc”

These documents are also provided for the personnel handling the Billing Integration issues.


There is no need to install Microsoft IIS (Information Server). While you working with Windows2000 Server Microsoft IIS is coming as part of that is already preinstalled.

This document doesn’t cover Billing System functionality, or any pricing or billing issues.

Any problems/questions related to RODOPI functionality should be forwarded to RODOPI Online Documentation or to RODOPI customer support representatives. (


7 Installation

As it was mentioned in paragraph 5.2 the complete Billing Integration solution requires different software component that should be installed on your system.

This document will cover the installation of all required components except Netscape 4.0 Directory Server and Steel-Belted Radius Server that is covered in additional installation documents that are also provided.


Before you start to install your RODOPI 5.2 Billing Software you need to install Microsoft SQL Server 2000.

Note: Currently RODOPI supports only Steel Belted Radius Server (from FUNK Software).

7.1 Microsoft SQL Server 2000.

7.1.1 SQL SERVER 2000

This section covers Microsoft SQL Server 2000 in step-by-step instructions.

The basic installation is coming from MSDN set (disc 120).

1. Insert the installation CD into your PC.

2. Go to X:\ENGLISH\DEVELOPER\X86\SETUP (where X is your CD drive)

Double click on SETUPSQL icon.

3. In the “Welcome” dialog click “Next”.

4. In the “Computer Name” dialog choose “Local Computer”.

Click “Next”.

5. In the “Installation Selection” dialog choose ”Create New Instance of SQL server or Install Client tools”.

Click “Next”.

6. In “User Information” enter your name and company name.

Click “Next”.

7. In “Installation Definition” dialog choose “server And Client Tools” option.

Click “Next”.

8. In the “Instance Name” dialog choose “Default” check box.

Click “Next”.

9. In the “Setup Type” dialog choose “Typical” and for “Destination Folder” leave the default destination folder or change it to another drive.

Click “Next”.

10. In the “Services account’ dialog leave the default settings:

”Use the same account for each service. Auto Start SQL Service”.

Choose “Use a Local User Account” option.

Leave the password for user “Administrator” empty.

Click “Next”.

11. In the “Authentication Mode” dialog choose “Mixed Mode” and specify the password for SA (System Administrator) login.

Click “Next”.

12. In “Start Copying Files” dialog click “Next”.

13. In the “Setup Complete” dialog click “Finish”.

You’re done SQL Server 2000 is installed.

After you finished your installation you should be able to start the following services:



Now it’s time to install RODOPI 5.2 Billing system.

7.2 RODOPI 5.2


For some reasons (Rodopi Software is investigating it) you MUST install Microsoft Office 2000 before RODOPI 5.2 installation.

1. Double Click on “RODOPI-52.EXE”.

2. In the “Choose Destination Location” dialog choose your destination folder where you want to install RODOPI 5.2 or leave the default destination folder.

Click “Next”.

3. In the “Select Components” dialog choose all components:


-RODOPI Services

-Web Interface

Click “Next”.

4. In the “Database Setup” dialog specify the password for SA (System Administrator) .You must know the SA password that you specified during SQL Server installation.

5. In the “Setup the Web Site” dialog specify “Default Web Site”.

Click “Next”.

6. In the “Select Program Folder” dialog leave the default name.

Click “Next”.

7. In “Start Copying Files” dialog click “Next”.

8. In the “Install Shield Wizard Complete” dialog click “Finish”.

You’re done. RODOPI 5.2 is installed.

After you finished your installation you should be able to see the created shortcut.

Go to “Start”->”Programs”->”Administrative Tools”->”RODOPI”->”Main Menu”.

RODOPI Main Menu should open in the web browser.

The full check list for the RODOPI functionality checks are beyond the scope of the current document.

Now it’s time to install RODOPI’s Bandwidth Manager 2.1.

7.3 Bandwidth Manager

1. Double Click on “Rodopi52_Allot23_t.EXE”.

2. You’ll be prompted with the confirmation dialog.

Click “Yes”.

3. In the Install Shield “Welcome” dialog click “Next”.

4. In the “Choose Destination Location” dialog leave the default destination folder.

Click “Next”.

5. In the “Select Components” dialog leave all components checked (“ODBC Usages”, ”Database”, ”RADIUS Usages”).

Click “Next”.

6. In the “Database Setup” specify the password for “sa”.

Click “Next.”

7. In the “Start Copying” files dialog click “Next”.

8. In the “Install Shield Wizard Complete” dialog click “Finish”.


Because of the currently existing bugs in RODOPI 5.2 release you must apply the following script against AbacBill database (RODOPI billing database).

Perform the following steps:

· Open the SQL Query Analyzer.

Go to “Start”->”Programs”->”Microsoft SQL Server ”->” Query Analyzer”

· In the “Connect To SQL” dialog enter the password for “sa” user.

Click “O.K”

· In the “Query” dialog select “AbacBill” for DB (at the upper right corner of the dialog).

· You should run the script called “Ipaddr_update_script.sql” that is supplied with the installation.

· Go to “File”->”Open”.

Open this script from your location.

· To run the script go to “Query”->”Execute”.


Make the following step only in case when Steel-Belted Radius is already installed on you system.

Copy NetEnfor.dct and RodopiAllot.act from X:\RODOPI\Radius to X:\Radius\Service

where X is your hard drive where you installed RODOPI and Steel-Belted Radius.

You’re done. RODOPI’s Bandwidth Manager  is installed.


7.4 Defining ODBC Data Sources:

Now when you installed RODOPI system it’s time to define ODBC Data Sources for RODOPI database.

1. Go to “Start”->”Settings”->”Control Panel”->”Administrative Tools”->”Data Sources(ODBC)”.

2. In the “ODBC Data Source Administrator” dialog click on “System DSN” folder.

Click “Add” button.

3. In the “Create New Data Source” dialog select “SQL Server” for a driver for which you want to set data source.

Click “Finish”.

4. In the “Create a new data source to SQL Server” dialog  use the following picture as example:


Click “Next”.

5. In the next dialog specify the password for “sa”.


Click “Next”.


You MUST know the password for “sa” user.

To change the password for “sa” user look at section 7.1.2 (step 13).

6. In the next dialog you need to specify your database.

Choose AbacBill from the combo box.

Leave all other settings as default:


Click “Next”.

7. In the next dialog that appears leave the default settings:


Click “Finish”.

8. In the final dialog that appears you should check your created data source.

Just press on button “Test Data Source”.

You should receive the following result:


Click “O.K”.

You’re done. ODBC data source is created.

What’s next?

If you are ready it’s time to start to configure your system.

8 Configuration against NetEnforcer

There are 4 places where you need to configure the system:

o At RODOPI 5.2

o At the NetEnforcer

o In the LDAP Directory

o In the RADIUS Server

8.1 RODOPI 5.2 Configuration

It’s time to start to configure your RODOPI system.

Basically what you need to do is to create an account (make customer activation) in your RODOPI system that want to buy Bandwidth Management Services (QoS services).

After this account will be created in the Billing System (RODOPI 5.2) it will be exported to the intermediate repository (LDAP Server in our case) and then from the LDAP it will be populated into the NetEnforcer Host Catalog.

After you did this you need to simulate the traffic related to this customer that will pass through the NetEnforcer and will be exported in the near real time to the RADIUS Server (Steel-Belted in our case).

Now RODOPI 5.2 is connected to the RADIUS server and the customer usage data passed from the NetEnforcer will be inserted into RODOPI database and will be rated.

Finally the customer that we created will be billed for his network usage according to the QoS that he bought.


The following picture will illustrate the process described above:

So, it’s time to start.

On the first step you need to create a few new service plans that will include QoS service levels. Then you will activate the customers for these rate service plans.

8.1.1 Licensing.

You cannot start to work with RODOPI until you’ll have the valid license for it. Basically the license configuration mechanism is based on the license request that you should send from your RODOPI Server to the RODOPI License Server.

1. Run the RODOPI Administration Menu.

From Windows “Start”->”Programs”->”RODOPI”->” Administration Menu”.

RODOPI Main Menu will open in the web browser.

2. Click on “License Configuration”.

The first time you enter the “License Administration” dialog you’ll see the title at the top of the screen “Invalid License Signature” marked by red.

3. Click on “License Configuration”.

The “License Configuration” dialog will open.

In the “Reg. Number” enter the registration number that you received while registering you RODOPI 5.2.

For password specify “1”.

Press “Save”.

4. You are back at “License Administration” dialog.

Click on “Download License”.

5. In the “Download License” dialog click “Download” when prompted with “Are you sure you want to connect to RODOPI License Server to renew your license?”

6. You should receive the following response: ”Your RODOPI license has been successfully renewed and saved in the database”.


The license response that you received from the RODOPI license Server is based per MAC address of the PC where RODOPI was installed.

This means that you cannot use the same license on different PC with the same RODOPI 5.2 installation.

For the customer support use only.

There is another way for RODOPI 5.2 licensing for demo installations.

Rodopi Software supplied Allot with the “license response” (encrypted license confirmation” that is not MAC address dependent.

All you have to do is:

1. Go to “License Administration”->”Save License Response”.

2. In the “License Response” dialog just paste the content of the file “demo_license_response.txt” in the text box for license response”.

Click “Save”.

3. You’ll get the valid licenses.

The final dialog box for licensing should looks as following:


8.1.2 Service Plans Creation.

Service plans creation consists of the following steps that must be done in the order specified in the current document:

· Detail Item definition

· Plan Details definition

· Usage Info

· Plan Info definition Detail Item.

1. Run the RODOPI Main Menu.

From Windows “Start”->”Programs”->”RODOPI”->”Rodopi Main Menu”.

RODOPI Main Menu will open in the web browser.


2. Go to “Administration”->”Service Plans”->”Detail Items”.

If you installed “Bandwidth Manager 2.1” you already have predefined “BW_QoS” (Bandwidth Management QoS) item.



RODOPI 5.2 is coming with already predefined 3 value of BW_QoS detail item: Gold, Silver and Bronze. If you wish to add any other values (“Platinum” for example) here is the way to do it.

3. Go to “Administration”->”Service Plans”->”Detail Items”.

At the right side there is an “edit” button that is server to edit the item.

Click on it.

“Add/Edit Detail Item” dialog will open.


At the bottom of the screen you’ll the Visual Format: Drop Down Box

This is the place where you specify different values for different QoS.

“Gold” value is coming predefined.

4. To add “Platinum”, etc you need to:

Click on the “Add” button.

Additional line for the entry will open.

Specify the next label and value:


5. Press “Save”.

6. Repeat the same steps (4,5) for any other label/values you want to add. Plan Details.


Bandwidth Manager for RODOPI 5.2 is coming with 3 predefined plan details for “Gold”, Silver” and “Bronze” detail items

1. Run the RODOPI Main Menu.

From Windows “Start”->”Programs”->”RODOPI”->”Rodopi Main Menu”.

RODOPI Main Menu will open in the web browser.

2. Go to “Administration”->”Service Plans”->”Plan Details”

If you already installed “bandwidth Manager 2.1” you already have predefined the plan detail for the “Gold”, “Silver” and “Bronze” value of the Bandwidth Management detail items.


If you want to edit click on the “Edit” button on the right side.

The “Add/Edit Plan Detail” dialog will opens.


Use the definitions “BW_Gold” Plan detail as an example to create “BW_Platinum” or any other plan detail that you want to create.

3. To create Plan these details :

Go to “Administration”->”Service Plans”->”Plan Details”.

Press on the “Add” button on the  right side of the dialog.

4. Use “BW_Gold” as an example.


The important thing is when creating the plan detail for “platinum” level you choose “platinum” value from the combo box for the default value. Usage Info.

1. Run the RODOPI Main Menu.

From Windows “Start”->”Programs”->”RODOPI”->”Rodopi Main Menu”.

2. Go to “Administration”->”Service Plans”->”Usage Info”.

Here is the place where we should define the usage info that should be rated.

You need to create “Net Traffic” usage info that will be used for the NetEnforcer integration.

3. Click on the “add” button on the right side of the dialog..

Specify the following values (see the picture below).



When you specify “Monthly” for “Period” this impacts on the invoice generation. This means that for “Monthly” period invoices for “Net Usage” would be generated once a month. If you specify “Daily”, each day the invoice for Net Usage will be generated.

4. Click on the “Save Usage” button. Plan Info.

1. Run the RODOPI Main Menu.

From Windows “Start”->”Programs”->”RODOPI”->”Rodopi Main Menu”.

2. Go to “Administration”->”Service Plans”->”Plan Info”.

Here is the place where we should define the Service Plans that should include our QoS items and details created at the above steps.

3. Click on “Add New Plan Info”.

4. “Add/Edit Plan Detail Info” will open.

5. The picture below serves as an example how to specify the Service Plan for Gold QoS.

Important Note:

In the “Plan Visible To” section you MUST select the “All Providers” option from the selection list.


6. After you finished to specify “Plan Details” press on the “Create” button.

7. Repeat the steps from 3 to 6 to create other service plans for different QoS levels.

Important note:

You may vary your descriptions or prices.

What is important is that for example for “Silver” Service plan you MUST choose

“Bandwidth management Silver QoS” from the Detail combo box (see the picture above).

So we created all required Service Plans (that includes QoS services) .

This Service Plans will be assigned to Allot/RODOPI customers during the account creation.

But before you start to create accounts you need to define your LDAP scripts that RODOPI 5.2 will activate after the account was successfully created.

8.1.3 Event Scripts.


To run your event screen you should check that the following Services is up and running:


RODOPI Procedures Server



Event Scripts is one of the most powerful mechanisms of RODOPI that enable to run some activity (in most cases execute scripts (LDAP, FTP, etc…)) as a result of some event that occurred in the RODOPI system.

For Allot/RODOPI billing integration Event scripts mechanism is used to run LDAP queries against an external LDAP Server.

These queries will be triggered as a reaction for different customer handling activity (Customer (account) Creation/Update/Suspension, etc).

For each LDAP script that you are going to create you need to specify:

- Destination where the LDAP Server is running (IP, LDAP User/Password, LDAP port).

- The body of the script where you need to specify:

 -location in the tree where the entry should be created

-Operation (add/delete/modify, etc)

-The attributes that you are going to export to the LDAP


The list of the customer attributes that are going to be exported to the LDAP

Server is fixed.

They are:




If you need to add any additional attributes it will require changes in RODOPI

software that is beyond the scope of the current document.

The following steps will serve as an example of the LDAP script creation that’s going to be triggered for “Gold” customer creation.

These steps will include some remarks and explanation in order to explain how to create the scripts for any other QoS details or customer handling activities.

1. Run the RODOPI Main Menu.

From Windows “Start”->”Programs”->”RODOPI”->”Rodopi Main Menu”.

2. Go to “Administration”->”Event Scripts”->”Event Script Administration”.

You are at the Event Script Administration Main Page.

As you can see at the picture below there are 3 combo boxes:

-Script Type


-Event Type



3. These combo boxes is used to specify what kind of scripts you are going to define.

As it was mentioned, for Customer Provisioning, LDAP scripts will be used. That’s why for “Script Type”, chosen LDAP.

”Detail” will specify the detail for which the script will be triggered.

For example if we are going to trace all “Gold” customer status changes in the Billing System we should choose “Bandwidth Gold QoS” for Detail.

”Event Type” will specify the kind of account/customer handling activity that we want trace by activating the script.

Event Type could be:

-Inserted (for customer/account creation)

-Deleted (for customer/account deletion)

-Updated (for changing customer/account details)

-Suspended (for customer/account suspension (temporary deactivation))

-Released (for customer/account release after suspension)

So in our example for Account Creation we need to choose “Inserted” for Event Type.

There are some default scripts that are coming together with RODOPI installation that although MUST BE MODIFIED.

So if you choose “LDAP” for Script Type, “Inserted” for Event Type and “Bandwidth Gold QoS” for Detail you’ll see the following default script:


4. Click on the “Edit” button.

5. Specify Address that should have the following structure:

ldap://<ldap user name>:<ldap password>@<ldap host name>:<ldap port>

6. Specify dn (distinguished name) that is pointed on the location in the LDAP directory tree where the entry should be created.

7. Change type should be “add” in our example because we are creating the script that is going to be triggered when the customer is created.

8. cn, servicelevel,iprange attributes leave as they are defined.


These attributes MUST exist in the Object Class (AllotBWCustomer) that was created in the LDAP server. (I.E. 0 customizing LDAP according to our installation guide.)

9. For objectClass specify AllotBWCustomer or any other name that must be exactly the same as the name you defined for the object class in the LDAP.

10. Click “Save”.

You will the script you created:



As it was mentioned (step 5) “Address” can be treated as following:

cn=Directory manager – is an LDAP User Name

allotcom – is a password for this user.

billing  -  is the host name where an LDAP Server is running.

389      - is an LDAP port

11. You need to repeat the whole procedure (steps from 3 to 10) for all event types and details that you need.

So, for example for Detail “Bandwidth Gold QoS” you will have 5 scripts (inserted, deleted, updated, suspended, released).

If you want to trace the Silver customers (“Bandwidth Silver QoS” detail) you’ll also need to create these 5 scripts.

And so on for any created detail.

We’re done.

Now we can test account creation and see how RODOPI will populate the LDAP Server.

8.1.4 LDAP Server Configuration.


We are assuming that on this step you are already configured and installed your LDAP Server.

Complete installation and configuration instructions for Netscape 4.0 LDAP are covered in the separate document.

(“Netscape 4.0 LDAP Server.Installation And Configuration Guide”).

8.1.5 Creating New Account.


Before you start creating new account you must check that the following services is up and running:


RODOPI Procedures Server



1. Run the RODOPI Main Menu.

From Windows “Start”->”Programs”->”RODOPI”->”Rodopi Main Menu”.

Click on “Create New Account”.

2. “Subscription – Customer Info” screen will open.

Fill the fields for the customer details.


Click “Next”

3. “Subscription Service Plans” screen will open.

For Select Account, specify “Personal”.

For “Select Service” specify “All”.

Choose a plan from the combo box (“Bandwidth Management Gold QoS” for example) and click on “Add” button.


Click “Next”.

4. “Subscription Account Info” screen will open.

There is nothing to specify here.

Click “Next”.

5. “Subscription Payment Info” screen will open.

Specify an e-mail address.

Choose “Check” for the payment type.

Click “Next”.

6. In “Subscription – Sales, Marketing survey etc” specify how do you want receive statement/invoices.

Choose for example (by e-mail).

Specify and confirm the password.

Click “Finish”.

7. You must receive “Subscription Confirmation” screen.

8. Now you should assign an IP address to this customer.

Go to “Start”->”Programs”->”RODOPI”->”Rodopi Main Menu”.->”Filter Search”.

”Filter Search” screen will open.

Specify your search criteria and press “Search Button”.

The following picture serves as an example for customer search (activated between (15/04/2001-18/04/2001):


9. Mark the radio button for the customer you want to assign an IP address and press on the “Plans” button.

10. “Plans” dialog will open.

Press on the “+” button left to the “Plan Description”.

You’ll receive the following picture:


Click on the “Edit” button right to the “Bandwidth QoS”.

11. “Edit Bandwidth Gold QoS” screen will open.

In the IP range field you should specify IP address that you want to assign to the customer.


Allot/RODOPI Billing Integration currently supports 4 types for IP address specifying:

1.Network Address with subnet mask.

For example:

1: (1-type, address, 32-subnet mask)

2.IP Range (from IP to IP)

For example:

2:, from to

3.Any Address


4.Host Name

For example: (4-type, name)

So, according to this convention specify an IP address for the customer.


Press “Save” button.

You’re done.

The new account is created.


As you see we assigned an IP address to the already existing customer. This is the way that it works in RODOPI. You can assign (and off course update) an IP address only for already created account.

You need a separate LDAP Event Script for “Update”.

You need to check if a proper entry, corresponding to this new account entry, was created in the LDAP Server:

o Log in into your LDAP Server.

We are assuming that you are using Netscape LDAP 4.0 Directory Server.

o In the Directory tree, under domain allot you will see your dc container, that you created while configuring your LDAP Server.

o You should see the following picture:



Now you can activate, update or suspend customers.

8.2 NetEnforcer Configuration

There are two Billing Interfaces that you need to configure in the NetEnforcer:

· Towards the LDAP Server

· Towards RADIUS Server.

8.2.1 NetEnforcer LDAP Server Configuration.

We are assuming that NetEnforcer or NetPolicy are already connected to the LDAP Server.

What we need to do is to create in the NetEnforcer “Host Catalog” a LDAP based host group entries that will retrieve their actual values from the LDAP Server, using queries.

You can define these host groups using different criteria but this current implementation is based on creating the groups of hosts (customers) based on their servicelevel that was assigned to them in the Billing System (RODOPI 5.2).

So if will work with three service levels (gold, silver, bronze) we should create 3 different LDAP based host groups (let’s name them GoldCustomers, SilverCustomers and BronzeCustomers).

As an example let’s create in the NetEnforcer host catalog entry for the GoldCustomers.

1. Log into the NetEnforcer.

2. Open the VC editor.

3. Open the “Host Catalog”

4. Create new LDAP based catalog entry as you can see from the screen shot:

For the Directory sub tree root specify:



5. Click on “Fetch & view contents…”

You will see the customer that we created in RODOPI at step 8.1.4:


6. Create the similar Host Catalog entries for “SilverCustomers” and “BronzeCustomers”.

The only difference should be in LDAP directory selection filter where you should specify (servicelevel=silver) for “SilverCustomers” and (servicelevel=bronze) for “BronzeCustomers”.


Your LDAP provisioning Billing Interface is working.


8.2.2 NetEnforcer RADIUS Configuration.

We are assuming the Steel-Belted RADIUS Server is already installed and configured on your system.

See section 6.1 in the “Steel-Belted RADIUS Server Installation and Configuration Guide”.

8.3 LDAP Configuration

As it was stated above LDAP installation and configuration is beyond the scope of the current document. It is fully covered in the separate document called “Netscape 4.0 LDAP Server. Installation And Configuration Guide”.

8.4 RADIUS Server Configuration

Steel-Belted Radius installation and configuration is beyond the scope of the current document. It is fully covered in the separate document called “Steel-Belted RADIUS Server. Installation And Configuration Guide”.

9 Testing The Whole System.

Now it’s time to test your entire system.

What you need to do is to see how your customers activated in Billing System (RODOPI 5.1) starts to use the network, their traffic are passing through the NetEnforcer and their usage data finally is delivered to the Billing System through the RADIUS accounting.

For each group of customers you should define dedicated Virtual Channel and then see how their usage data in RODOPI.

So, let’s start.

1. Log into the NetEnforcer.

2. Open the VC editor.

3. Define 3 Virtual Channels (Gold, Silver, Bronze) for the customers grouped by the service level they purchased from RODOPI.

The following screen shot will illustrate this.


Host Catalog entries GoldCustomers, SilverCustomers and BronzeCustomers were defined at step 8.2.1 (NetEnforcer LDAP Server Configuration).

4. Now, start to generate traffic that will fall on these virtual channels (Gold, Silver, Bronze).

You can use any type: pinging, using ftp or web usage for example.

5. In a short period of time you should see that your Radius accounting is working.

Open Steel-Belted Radius administrator tool.

Click on “Connect” check box.

Click on “Statistics” check box.

Click on “Accounting” folder.

You should see that you receive Start and Stop accounting packets dynamically.

This proves that your RADIUS Server is receiving accounting data from the NetEnforcer.

If everything till now was installed and configured correctly you should see this usage data in RODOPI.


6. Open your RODOPI “Main Menu”.

7. Click on “Filter Search”.

8. In the “Filter search” screen specify your search criteria for the customers you are looking.

9. After you’ll receive the search results, mark the specific customer (for which you simulated the network usage.

Click on “more” to get additional details.

10. Click on the “Net Use” button.

11. The “Net Traffic screen will opens”.

12. Specify the period for which you want to see the report about customers network usage.

Click on “Submit” button.

13. You should receive the report similar to the picture below:


14. Invoice generation.


To successfully generate the invoices the following services MUST BE UP:

SQL Server Agent

RODOPI Procedures Server

Invoice generation is an automatic process in RODOPI. There are several types of invoices that will be generated automatically.

The first type is the invoice that will be generated immediately when you created the customer account. It would include an “activation fee” (this means the fee you defined in the service plan that was assigned to this customer. For example in our example for the “Bandwidth Gold QoS” service plan  two “activation” fees were defined: ”Subscription Fee – $ 30.00 for 12 months” and “Ongoing Fee - $ 15.00 for every month”.

So, as it was stated above immediately after account creation you should see the invoice generated that includes these fees.

To see this do following:

Follow the same procedure (“Filter Search”) to find the customer you are interesting.

When the customer found mark the check box click on “Invoices” button.


The following screen will open:

 The customer “Gold Customer_1” was activated on July 17 2001.So the first invoice in the list will include only “activation” fee.

The rest of the invoices include the Net Usage fee. Because of the fact that the “Net Usage Mb” usage was defined on the Daily basis the invoice will be generated every day. As it was stated, to generate the invoices once a month you nee to define the usage on the Monthly basis.

To see it simply click on the invoice number.

The following picture is showing the invoice including “activation” fees generated automatically after account creation.


The invoice including Net Usage fee should look like:

 Important Notes:

Invoicing in RODOPI 5.2 is an automatic process managed and activated and scheduled by the Microsoft SQL Server jobs mechanism. In the normal situation there is no need to manual interaction into the billing (invoice generation) procedures.

Although if any purposes you need to activate the daily billing you do it the following way:

Open Microsoft SQL Server.

Go to the Management->Jobs section, you should see the following picture:

 On the right side there is an icon representing “RODOPI daily billing” job. As it was stated this job is activated automatically.

If you want to run it immediately just right click on the icon and click on the “Start Job” from the pull down menu: Click “Start”. The “RODOPI Daily Billing” will be activated.

If you still don’t see the invoices you can check the status of the last RODOPI Daily Billing job through the RODOPI 5.2 interface

Go to “RODOPI”->”Administration”->”System State”. The “System State” dialog will opens. Here you will see the result of the “Daily Billing”.

The following picture illustrates this:


10 Troubleshooting

This section contains the list of the problems with it solutions that could occur during the installation/integration process.


No. Problem Possible reasons that cause the problem.

1 After creating an account in Rodopi 5.2 the corresponding entry is not created in the LDAP server and as a result of this the entry is not created in the NetEnforcer Host Catalog. Check that the following services are up and running:RODOPI ServerRODOPI Procedures ServerMSSQLServerSQLServerAgent



















11 Open issues




If you have additional questions/comments, please contact:

Allot Communications

Kaputkin Evgeny

tel: (+972) –9-7619309


List of files

Link: Code for blog or website: Link for forum: