Configuration

1. Company Information.

2. Billing Configuration.

3. Internet Configuration.

4. Domain Name Configuration.

5. Miscellaneous.

6. CC Processing.

7. Payment modules configuration.

8. Radius Server Configuration.

9. Ticket Service Configuration

1. Company Information.

Enter here the information about your company. It will show on the customer's statements, invoices, etc.
Support E-mail Address and Support E-mail Name are the "From" name and address in the e-mails sent to customers using the pool. 

 return to top

.2. Billing Configuration

        Billing Information

• Billing Starts in At Least
  The billing procedure maintains an internal billing date. It is incremented by 1 day each time the procedure has been run successfully. The procedure won't run more than once for the same billing date. It also won't run for future dates. With this parameter you can ensure that it won't run before the specified hours have passed from midnight of the actual date. For example, if you want to run your daily billing procedure at 10 PM you must schedule the "RODOPI Daily Billing" scheduled task at 22:01 and enter 22 in this field. If you want to run it at 2 AM, you must schedule the procedure at 2:01 and enter 26 in this field. By default the task will run at midnight.
  IMPORTANT: If for some reason the procedure has not been run for several days, you can run it several times one after another and it will do the billing for the missing days.
• Password for Changing Plans
  RODOPI will ask for this password when someone tries to change customer's plan.
• Billing E-mail Address and Billing E-mail Name
  This will be the "From" name and address in the e-mails sent to customers for instance: Invoices, Statements, Late Payment Letters, Pre payment letters.
• Default Anniversary
  This is the Default Anniversary Day of the month. Rodopi will use this date when subscribing or upgrading customers for a given plan that has Auto change to default on subscription or upgrade option selected to change Customers' anniversary date to this date.  For example if someone has subscribed on 21th of march for a plan that uses this option. and Billing Day is 1st, his next billing date will be 1st of April instead of 21th of April.

        Billing Policies

• Money Back Guarantee
  If a plan is closed before the days specified in this field, the customers account will be automatically credited for the price of the plan. If he has already paid by credit card you have to manually apply a refund transaction. Put here: -1 to disable this feature, 0 means the same day, 1 - next day, etc.
• Charge Suspended Plans
  When a plan is suspended, the customer doesn't use any services, so you may prefer not to bill the customer's account.
• Refund Never Activated Plans
  When a plan has never been activated, it means that the customer had never used your services at all. In this case you may prefer not to bill his account.
• Accrual accounting for Recurring Sales
  When this option is enabled all recurring sales will be calculated on reports using Accrual Accounting method.
• Late Payment Fee
  This is the amount that customer will be charged if  he/she has not paid his full balance till his anniversary date.
• Fee for mailed statement/invoice
  This is the amount that customer will be charge for receiving statements/invoices by mail.
• Charge for Roaming
  When checked the roamers will be charged the way you specified in the "Roaming Prices" page. Otherwise the on-line hours of the roamers will be added to the regular on-line hours and the customer will be billed accordingly.
• Put On Hold Plans
  Putting customer's plan "on hold" (suspend it) will remove the customer's dial-in accounts from the RADIUS file exported by RODOPI and will generate "Suspended" event (see Event Scripts). You can enable this feature for each major payment type separately.
• Until First Payment
  These three flags let you suspend the service for new subscribers until you receive the first payment.
• After Payment Delayed For
  Enter here the amount of time (in days) you are willing to wait for payment before you suspend the service for delayed customers
• Advanced Billing
  You may need to bill your customers in advance. This way Rodopi will generate invoices and statements and will charge credit cards in advance. In this table you can specify the number of advanced billing days for the main payment types.
  For example credit card customer signup on 10/1/98. The same day (when the billing procedure starts) his credit card is charged for ongoing fee for service from 10/1/98 to 11/1/98. If you have specified advanced billing for credit card customers 0 days the customer will be charged again on 11/1/98 for service from 11/1/98 to 12/1/98. If you have specified advanced billing 15 days his credit card will be charged on 10/16/98 for service from 11/1/98 to 12/1/98.
  The prepayment letters will be send based on the next billing date that is NOT the advanced date.
  The date when the plan will be suspended for late payment does not depend of the advanced billing settings either.
  

• When you check Use Multi Currency Rodopi will be able to calculate the "Amount due" on the invoice in second currency specified from you.
• Primary Currency is the sign that will show first on the invoice and all internal billing is done in the primary currency.
• Secondary Currency will show on the invoice as second line. The amount will be calculated from the amount due of the primary currency and the current rate for the day.
• Use fixed rate. If the rate does not change very often you can check this field. Then Rodopi will calculate the secondary currency amount using the last rate.
  

return to top

• Default Mail Domain
  Used for assigning e-mail addresses to customers on subscription.
• SMTP Server
  Used for sending e-mails (invoices, statements, etc.) to the customers. 
• Incoming Mail Server
  Enter here the name of POP3 server, where your customers will download their emails from.
• News Server 
  Enter news server name, if you are going to run a newsgroup in your ISP to help your customers with support, news, useful information etc.
• This WWW Server
  The name you enter here will be used for generation of attached HTML Invoices and Statements.
• DNS Hostname's and DNS IP Addresses
  Used in the domain registration process. 
• Automatically add "In DNS"
  Check this option if you want the domain(s) entered by customer on subscription automatically to be added in DNS file.
  

return to top

• Whois Server: Should be whois.crsnic.net
• Timeout: Should be 60
• Type of Domain Names Registration: In case you are a partner "Submit to registrar - charge the ISP" should be selected. If you only send or refer customers to names4ever "Submit to registrar - charge the customer" should be selected. If you don't want to submit domains select "Disabled".
• Registrar's submit page URL: Should be:
      https://www.names4ever.com/cgi-bin/Names4Ever_Subscribtion.exe
• Account # with Registrar: The registration number for the partners program. You will receive it from names4ever.com
• Password for submitting to Registrar: The password for the partners program. You will receive it from names4ever.com
• Plan # provided by Registrar: By default is 7. You may receive other value from names4ever.com
  

return to top

5. Miscellaneous.

• Plan Details Log History
  The changes in the plan details (dial-ins, shells, e-mails etc.) are logged. This field specifies how many days to keep the log of these changes.
• System State Log History
  The changes in the RODOPI subsystem states are logged. This field specifies how many days to keep the log of these changes. Click here for details
• Usage History 
  The changes in the RODOPI usages are logged. This field specifies how many days to keep the log of these changes.
• Send Letters Password
  Enter here the password that will be used when sending letters from the pool.
• Customer Support Admin Password
  Enter here the password which will be used for login into Customer Support area. You (the ISP) can give this password to your support staff who do not have access to the Maintenance Section of Rodopi.
• Show passwords in plain text
  Check the box if you want passwords in this area to be shown in plain text. Otherwise asterisks will be shown.
• By default expand all active plans
  Check this box if you want to have all active plans in Filter Search / Plans page expanded. You may use this option if your customers have small number of plans. Otherwise if you have large number of plans for your customers it will be faster to load the Plans page. If this is so, uncheck this box. 
• By default show only similar plan info
  This setting reflects on the content of the Plan Info dropdown box in the Plan Information section. Click here for details
• Customer can change his E-mail
  Reflects on Customer Support / Change Customer E-mail section. When checked, customers are allowed to change his contact e-mail addresses.
• Plans per page to show
  Show this number of plans on every page when listing customers plans. 
• Netscape Navigator Dial-Up Kit
  If you enable this option when the customer subscribes with Netscape browser, on the confirmation page of the subscription there will be a link that will configure customer's internet settings according to "NETSCAPE NAVIGATOR DIAL-UP KIT 3.0" documentation. To customize which phone numbers are send to the customer, change "netscape.ins" file from "olsplus-cgi" sub-directory.
• NetFlow IP
  Here you have to enter the IP address of the machine where the Net Traffic Program is running. Click here for details
• CNetFlow Config. Port
  This is the port where Net Trafic Program is running. 
• Synchronize popname with email address
  Check this when you are using Vircom VOP mail. This will allow to your customers to enter just email address on subscription. Popname will be the same as email name.
• Short Date Format
  Specify the format of the short date for RODOPI interface.
• Long Date Format
  Specify the format of the long date for RODOPI interface.
  

 return to top

• Enable: When ON, Rodopi will try to charge automatically all customers with payment type "credit card" at daily billing task.
• Ext merchant# is parameter for flexible connection with external CC processing software packages. It will show you for example which ICVerify SET file Rodopi will use. If the value is 0001 the SET file used will be ICVE0001.SET in the SYSTEM32 folder. The Rodopi merchant# will show you what Rodopi merchant is assigned for this Rodopi installation. It is usually 1001. This value connects XXXXBill database(s) and AbacPay database. These values should not be changed.
  RODOPI v5.2 change: This option makes sense only if Payment Module is not configured.*
• Charge CC one by one: This option is for compatibility with some old CC software and some old fashioned CC processors. When ON, Rodopi will dial to the bank processor for each transaction when using ICVerify. Will work with all ICVerify installations and processors. With Authorize.Net module it should be OFF.
  RODOPI v5.2 change: This option makes sense only if Payment Module is not configured.*
• Charge CC in Multi Trans mode: If you are using ICVerify with this option set, it will dial to the bank processor only once and will charge all credit cards. This method is about 6 times faster than the previous one. Not supported by all CC processors. Check this with your bank processor if this method is supported and enable this option in your ICVerify SET file. With Authorize.Net module it should be ON.
  RODOPI v5.2 change: This option makes sense only if Payment Module is not configured.*
• Charge CC with Forced payment: If there is authorization code obtained on subscription (see Credit Card Authorization option), it will be used with "Forced sale" transaction when collecting money at daily billing task. Else, "Sale" transaction will take place. The other name for "Forced payment" is "Capture funds only" and authorization code for the exact amount should be provided (this happens internally in RODOPI). The other name for "Sale" is "Authorize and Capture funds"- card is first authorized and then captured (happens atomically). This option makes sense to be ON if you turn ON Credit Card Authorization option.
• Credit Card Authorization: When ON, RODOPI will authorize customer's CC (if payment method is CC) on subscription for the amount of services he/she subscribes for. If authorization is obtained successfully, this guarantees credit card is valid and cardholder is in good standing. If you turn ON Charge CC with Forced payment option this one also should be turned ON.
• Credit Card Address Verification: When RODOPI authorizes the credit card with this option turned ON, the zip code address verification will occur. If the customer fail to provide correct zip code the subscription will be denied. This option makes sense to be ON when Credit Card Authorization option is ON.
• Letter to send before CC expiration
  Select the letter which will be send to your customers who credit cards will expire.
  To choose the number of days the letter will be send before expiration and to create the body of the letter go to Administration / Letters Section of Rodopi.
  

RODOPI v5.2 change: RODOPI v5.2 uses new and more flexible approach for charging CC using different providers with different configuration for each installation. Refer to Payment modules configuration for more information.
* This option is left for compatibility and makes sense only in case you are doing upgrade and have ICVerify configured with previous version of RODOPI. This option will make sense only for MISP's without payment module configured. Keep in mind that you have to change to payment modules to be ready for next version of RODOPI. If you are doing brand new installation, refer to Payment modules configuration for more information about how to install, register and configure RODOPI. to use payment module desired. Is there module configured and which one, can be checked under Administration | Configuration | Payment modules configuration.
RODOPI 5.2 upgrade will preserve all the configuration and will continue to work as previosly configured. That means, that if you have previosly using ICVerify, it will continue to work in old fashioned way. Also, if there is no module configured for particular MISP, RODOPI will continue to work by the old way, trying to use ICVerify. RODOPI v5.2 install/upgrade will copy payment module for ICVerify (filename: rpmicverify.exe) into main \RODOPI directory on the WEB server, but you need to move it to the SQL server (only if you are using separate WEB server and SQL server machines) and register it. You need only one file for all the MISP's using this module.

Our suggestion is to migrate to the payment modules, because the old fashioned way will become obsolete in the next versions.

return to top

7. Payment modules configuration.

The module vendor (most often RODOPI Software) should provide the CLSID to you and/or instructions how to register the COM object. Usually the registration will be done as part of the installation, so you don't have to worry about that. In any case, if you get "Class not registered !" error or want by any reason to unregister some module, you can do that yourself by opening a command prompt window, changing the current directory to where COM container is located and following next rules:

To configure RODOPI to use particular module, go to RODOPI home page/Administration / Configuration / Payment modules configuration and type or paste the CLSID of the module. Click Add button. RODOPI will try to recognize the module and obtain settings it needs in order to work and if successful, the module will appear as a choice for Rodopi merchants listed below at the same page. Each module needs different specific settings depending on communication method it uses and provider requirements. To configure particular Rodopi merchant to use particular module, select the module from the merchant's list box, and click Continue button. The next page will look different for each module. It is possible to experience "Access denied" error message when you try to add module. The reason is that your SQL server is running with different than "System" account, and the account it is using is not granted the right of instantiating and/or using all or particular COM objects. You can check and/or change this in Control Panel / Services / MSSQLServer / Startup . You should make appropriate administrative settings to grant MSSQLServer account the right to instantiate and use COM objects, or just switch the SQL server to run with "System" account.

For RODOPI Service Bureau (RSB) module, the configuration fields should be set as follow:

Merchant ID: Type here your MerchantID with RSB Gateway.
Merchant password: Type here your password with RSB Gateway.
Server address:secure.rsb-gateway.com
URL:/gateway/rsb.dll?

CLSID of RSB module is 9F110174-F7B3-11D4-B3E5-00104B6C4FA3

Example:

Note: Server address and URL should contain exactly: "secure.rsb-gateway.com" and "/gateway/rsb.dll?" without the quotation marks not or spaces. Don't forget question mark in URL- it is extremely important !

For ICVerify module, the configuration fields should be set as follow:

Windows system32 directory: Type here the path for Windows\system32 directory. ICVDLL32.DLL, all the .SET files and DATA directories should be in this directory as described in Credit Card Processing.
Merchant ID: Type here the four digits from the name of the .SET file you want this installation to use.

CLSID of ICVerify module is C7D334E3-F92F-11D4-B3E6-00104B6C4FA3

Example:

When using ICVerify through payment module, it will work in auto multi transaction mode, which means that it will hold line for about 10 seconds after end of the current transaction. If another transaction occur in this time to the same CC processor (and the same phone number), it will be processed without hanging up. If this timeout expires or request to another CC processor (and another phone number) occurs, ICVerify will hang up current connection and will dial the new number.
NOTE: This module obsoletes only ICVOLE32.EXE. All other installation instructions about ICVerify remain in charge as described in Credit Card Processing.

For Authorize.Net module, the configuration fields should be set as follow:

Merchant ID: Type here your user name with Authorize.Net. Same you use for the web interface.
Merchant password: Type here your password with Authorize.Net. Same you use for the web interface.
Server address:secure.authorize.net
URL:/gateway/transact.dll?

CLSID of Authorize.Net module is 372032A0-F882-11D4-B3E5-00104B6C4FA3

Example:

Note: At the time of this document, Server address and URL should contain exactly: "secure.authorize.net" and "/gateway/transact.dll?" without the quotation marks not or spaces. But don't forget question mark in URL- it is extremely important. If Authorize.Net decide to change these settings, you should contact them and ask about Server address and URL for "Automated Direct Connect/Direct Response" connection method.

There are few settings you have to adjust in your Authorize.Net account to allow RODOPI module for Authorize.Net to process transactions. Log into authorize.net / Merchant login using your user name and password and adjust the following options:
1.1. Settings / General Merchant Settings / Test Mode - It's very important this option to be turned OFF (unchecked). If this option is ON, all transactions your RODOPI will send to Authorize.Net will be treated as TEST transactions and successful response will be issued without actually doing anything.
2.1. Settings / ADC Direct Response Settings / Delimited Response = YES
2.2. Settings / ADC Direct Response Settings / Default Field Separator = ,(comma)
2.3. Settings / ADC Direct Response Settings / Default Field Encapsulation Character = NONE
3.1. Settings / Manage URLs - there should not be any URL's set.
4.1. Settings / Payment Form Receipt Settings / Payment Form Weblink Field Settings, "Required" column: All checkboxes should be in UNCHECKED state.
4.2. Settings / Address Verification System Settings , "Reject Transaction" column: All checkboxes should be in UNCHECKED state.

Also, you have to adjust the options under Administration / Configuration / Common Configuration / CC processing in your RODOPI.

For PCAuthorize*Hub module, the configuration fields should be set as follow:

Merchant ID: as configured in PCHub "Merchants" section
Hub IP address or Host name: as configured in PCHub "Workstations" section
Hub port: as configured in PCHub

CLSID of PCAuthorize*Hub module is 64B6D2CE-6816-4907-AC6E-8561D7E22F39

Example:

There are few settings you have to adjust in your PCAuthorize*Hub to allow RODOPI module to process transactions.
Show "Merchants" and Workstations" windows as shown. At first, create a merchant, for example RODOPI as shown, then add as a workstation DNS name or IP address of the machine from which RODOPI will request transactions and set as merchant for this workstation RODOPI or whatever is configured in previous step. These settings are required to let PCHub know that RODOPI will send transaction requests.

It is mandatory when setting merchant's parameters, to set "Authomatically Settle" option as shown below. It is not mandatory, but it would be good settlement time to be some time when RODOPI billing task is not active. For example 10PM - 2 hours before RODOPI billing task to start.

For CommSecure module, the configuration fields should be set as follow:

Merchant ID: Type here the MerchantID as provided by CommSecure.
Merchant password: Type here the password as provided by CommSecure.
Server address:Host name or IP address of the NodeBox.
Port:Port number the NodeBox is listening on.

CLSID of CommSecure module is 67E47EB7-0E9C-402D-8861-973E9864CA6E

Example:

With any module used, you have to adjust the options under Administration / Configuration / Common Configuration / CC processing in your RODOPI.

return to top

• RADIUS Users File URL
  This is the location of the users file of your RADIUS authentication server. RODOPI will upload the generated file via FTP to the URL specified. The users file is in standard LIVINGSTON format. You may create a special account for RODOPI on your authentication server. The URL must be in the form: 
  
      ftp://uploadlogin:password@authentication-server/directory/users-file
  
  For example:
      
      ftp://radusr:hjYRT65@radius1.netdomone.net/usr/local/radius/users.txt
  
  Make sure there are no spaces or special character in the URL. Use password with letters and digits only. The directory is relative to the root directory NOT to the users home directory. The user default directory is not supported.
  
  Rodopi will NOT read any data from the users file in the specified location. Rodopi will upload new users file every time some dialin account is changed (inserted , deleted, suspended, released, modified). You need to have all your customers in the Rodopi database to have them all in the users file.
  
  To check the status of the procedure that uploads the users file go to Filter Search, select Procedures from Search Criteria and click Search. Look at the Last Activity and Last Message/Error. You can run the procedure manually from there. Click on the radio button near to "Create RADIUS file" and click on the "Run" button on the left.
  If you have error 202 this means that the URL to the users file is not correct. Sometimes not enough permissions will cause this error. The user in the URL should have permissions to create, rename, delete files in the specified location.
• Password Mask
  If you enter here something different from spaces, next time when RODOPI generates RADIUS users file all passwords with be replaced with "Password Mask" value.
• RADIUS Users File History
  RODOPI will keep the RADIUS users files which are not older than the number of days specified here. The value of 0 means that it will keep only today's files. Value -1 means that no backup copies of the users file will be kept.
• Online Usage History
  Number of days to keep the on-line usage details. This period should be long enough to cover your longest plans that include usage-based billing. Usually 2 months history is enough. Please note that keeping too much history will result in quick growth of your database. You can change the URLs of the usage detail files from the "On-line Usage URLs" administration page.
  

return to top
   

9. Ticket Service Configuration.

(Follow the links Administration / Configuration / Ticket Service Configuration from main Rodopi page to get to the Ticket Service Configuration page)

In Rodopi 5 and later you have the possibility to create trouble tickets using direct connection to POP3 (mail) server. Here are the fields that you need to fill in order to use the ticket service:

• POP3 Server
  Name of the server that will receive support emails. For example "mail.isp.com". Standard Port for POP3 servers is 110.

• Timeout
  The time in seconds used from Rodopi to connect to POP3 Server

• Login
  Valid for this POP3 server account name

• Password
  Valid password for the above account name

• Max. Message Length
  Specify the maximum length of the message in bytes.

• Delay
  The period of time in minutes after which Rodopi will try to connect to this POP3 server and get support emails.

return to top