877.245.5629
sales@billmax.com
|
BillMax Billing Solutions 877.245.5629 sales@billmax.com |
| Examples of Setting up Resources, Terminal Servers and Service Definitions | ||
|---|---|---|
 |
Chapter 2. Preliminary BillMax Configuration | 
|
For a complete description on configuring Service Definitions, please see Configuring a Service Definition. The Resource Set for a particular Service Definition is configured in the same manner as for a Terminal Server when accessing the Service Definition page.
The following examples will describe how Resources, Terminal Servers and Service Definitions relate with respect to Resource Sets. Unless otherwise noted, the following examples assumes that duplicate values for service.d01 in a namespace are not allowed. service.d01 is the where the login name for a Service is stored.
Example 2.1. Single Name Space, Duplicate Values Allowed.
As duplicate values are allowed for service.d01, do not configure any Resources.
Example 2.2. Single Name Space
As duplicate values are not allowed for service.d01, configure a Resources and use that Resource when creating a Service Definition
Example 2.3. Single Name Space with Terminal Servers
As duplicate values are not allowed for service.d01, configure a Resources and use that Resource when creating a Service Definition. Do not configure any Terminal Servers. Instead, use the -M option to radiusd or the -m to radparse to specify that the RADIUS accounting data should match the Services created from the Service Definition. For example, if the the fourth place holder is used to specify the RADIUS resource, then start radiusd with "-M 8". In addition, name any RADIUS related Resource with the string "radius" in the name.
This is the simplest setup. It requires all Service login names (service.d01) to be unique. This is generally accomplished by adding number to the login name (e.g. John1, John4) and/or making the login name a fully qualified login name (ex. John@mybillmax1.com, John@mybillmax2.com).
Example 2.4. Two Name Spaces with 4 Terminal Servers
The key to this setup is that the service.d01 fields may have two duplicate value pairs, but the duplicates belong to different namespaces.
Configure two Resources. For this example, radius1 and radius2 will be used.
Configure two Terminal Servers (A and B) for radius1. Configure two Terminal Servers (C and D) for radius2.
Configure one Service Definition for radius1. Configure one Service Definition for radius2.
Assume that there are two "Bob"s. Then there are two different Services, each with service.d01 equal to "Bob", one created from the radius1 Service Definition and the other created from the radius2 Service Definition. If a "Bob" access the service using either Terminal Server A or B, the RADIUS data will be associated with the radius1 Service. If "Bob" access the service using either Terminal Server C or D, then radius data will be associated withe the radius2 Service.
|
|
 |
|
| Configuring Terminal Servers |  |
Chapter 3. Configuring BillMax Billing Parameters |
