Cisco BBSM 5.3 SDK Developer Web Page Guide - 3 - Creating Custom Page Sets [Cisco Building Broadband Service Manager]

Table Of Contents

Creating Custom Page Sets

Creating Your Page Set

Before You Start

Page Set Creation Procedure

Supplemental ASP Pages

Using the CommonSubroutines Page

System and Error Messages

Creating Custom Page Sets

This chapter describes how to create a custom page set manually without using the Page Set Wizard. We recommend that you read this entire chapter before attempting to create your new page set. Refer to these sections:

•Creating Your Page Set

•Before You Start

•Page Set Creation Procedure

Refer to "ActiveX Server Component API Reference" for descriptions of the objects, methods, and functions that can be used in page sets.

For information on creating PDA page sets, refer to "Creating Custom PDA Page Sets."

Creating Your Page Set

This section describes how to create a custom BBSM page set. You can use the BBSM page set templates that ship with BBSM as the starting point for your custom page set.

Create your page sets based on the kinds of changes that you need to make to the page set templates:

1. If you need to make minor modifications to the DailyHotel page set, such as adding a graphic and logo, you can probably use the Page Set Wizard. For instructions, refer to the section on using the wizard in the Cisco BBSM 5.3 SP1 Configuration Guide.

2. If you need to make additional minor modifications, you can probably make these changes by following the procedure in the section on creating custom page sets in the Cisco BBSM 5.3 SP1 Configuration Guide. This procedure gives basic instructions for modifying a page set. These instructions are also provided in this guide in "Creating Custom Page Sets." This chapter also provides instructions for more complex changes.

3. If you need to make more extensive changes, use the instructions provided in "Creating Custom Page Sets."

If you do not want to give your web developer access to your BBSM server, you can copy the page set templates from the c:\atcom\ekgnkm directory on your BBSM server and give them to your web developer.

Note Although you can make these changes yourself, we recommend that you hire a web developer.

If you are developing a page set that requires the end user to enter sensitive information, such as RADIUS or credit card information, refer to the chapter in the interface SDK on installing a test certificate.

Before You Start

Please read the following information before beginning to create your page set:

•Use Microsoft Notepad or another text editor to edit the ASP files that control the page set parameters. This procedure assumes that you are using Notepad.

•Give your customized page set a new name. The BBSM default page sets are provided only as templates. If you do not rename your customized page sets, they can be removed or replaced when a BBSM patch or service pack is installed.

•Page sets include the following ASP files (pages):

–Start pages—Defines the first page that the end user sees

–Post pages—Displays the Connecting... message. It calls the functions needed to connect the end user.

–Package files—Stores the settings for the page set.

–GIF files—Define the graphical representation of the page set.

•If you want to debug ActiveX server components in page sets, you can develop your page set on a server that has the development environment installed and use Microsoft Visual Studio as an editor.

•You must add the new page set to the BBSM server at the end of the procedure. (You must have administrator privileges to use WEBconfig to add your page set to BBSM.)

Page Set Creation Procedure

Follow this procedure to create your page set. In this example, we create a custom page set using the DailyHotel page set parameters for an example in the package ASP file.

Step 1 Determine the access and accounting policies that meet your requirements. For detailed descriptions of the BBSM policies, refer to the chapters on creating access and accounting policies in the Cisco BBSM 5.3 Interface SDK Developer Guide.

•If you have written your own access policy, you only need to determine which accounting policy to use.

•If you have written your own accounting policy, you only need to determine which access policy to use.

•If you want the end user to have a choice of access or accounting policies, refer to the detailed description in the "Mega and MegaClear" section for an example.

Step 2 Within the c:\atcom\ekgnkm folder (where the BBSM page set files are located), create a subdirectory, such as c:\atcom\ekgnkm\YourNewDirectory, for your new page set files. (Although new files can be created in c:\atcom\ekgnkm, we recommend saving them in a separate folder.)

Note If you have installed a BBSM service pack and inadvertently overwritten a custom page set, the previous page set can be retrieved. A backup of all previous page sets is located in the c:\atcom\patch directory. Look for the folder named Backup####, where #### is the patch number that corresponds to your patch or service pack (found on WEBpatch).

When you find your original page set, do not copy it directly back to the ekgnkm directory. Instead, you must integrate your custom page set with the new page set that was installed with the service pack. We recommend that you cut and paste changes that you made to the custom page set into the new page set so you are using the most up-to-date page set with your new service pack.

Step 3 Choose the page set template that is closest in functionality to the custom page set you are creating. For example, if you plan to use credit card billing use an ICS page set. If you plan to offer Internet access by the day, use a Daily page set.

Step 4 Copy all of the page set template's ASP and GIF files (for example, those for DailyHotelxxx.asp) from the c:\atcom\ekgnkm directory into your new subdirectory. Most page sets include start, post, and package files and any other appropriate pages, such as fail or error pages:

1. Be sure that you have a post page in your new directory because it is a critical file that calls the SendActivateSession method to activate the end user's session.

2. Create any additional pages, such as a fail or error pages, and save them in this new directory.

Step 5 Change the write permissions for all ASP files that you will be editing, as shown below:

1. Right-click the file and select Properties.

2. Uncheck the Read-only check box and click OK.

Step 6 Rename each file with your new page set name. We recommend using a naming convention such as NewNameStart.asp.

Caution Be sure to give your custom page set a new name. The BBSM page sets are to be used as templates only. If you do not rename your new page sets, they can be removed or replaced when a BBSM patch or service pack is installed.

Step 7 Change the default portal, which is the home page to which the end user is directed when he or she accesses the Internet:

a. Using Microsoft Notepad, open the NewNamePost.asp file.

b. Change the default home page, www.cisco.com, to a new default URL.

c. Save the file and close Notepad.

Note Alternatively, you can opt to send the user to his or her originally requested URL when he or she gets connected. To do this, set the strPortal string as follows (refer to SubscriptionHomeActivate.asp for an example): strPortal = obj.GetOriginalURL();

Step 8 Review steps 9 through 11 for supplemental changes that you may want to make to your page set:

•Displaying/hiding the BBSM Toolbar and its buttons—Step 9

•Enabling/disabling Bandwidth Manager—Step 10

•Enabling/disabling Public-Private IP Addressing—Step 11

If you do not want to use any of these options, go to Step 12.

Step 9 Displaying the BBSM Toolbar and the Disconnect, Print, and/or Bandwidth Boost utility buttons—Use the iport_tools ASP file, located in the c:\atcom\ekgnkm folder on BBSM, to display the toolbar and its buttons. The page is invoked as a web page toolbar that sits on top of the selected web page. (Note that the Bandwidth Boost cannot be used with the RADIUSUBand and RADIUSUBandClear page sets.) To change the display characteristics of the page, you modify the xxxPost page.

Regarding the iport_tools page and the invoked BBSM Toolbar, you can modify the following:

•Display the BBSM Toolbar and its buttons

All of the page sets that ship with BBSM, except for the DailyHotel page set, load the iport_tools page when the end user activates a session. On these page sets, the xxxPost page calls the iport_tools page that invokes the BBSM Toolbar. It displays the Disconnect button that enables the end user to disconnect from the session. When the user clicks Disconnect, disconnect.asp is invoked as a pop-up window stating, You are now disconnected. The window closes automatically after 5 seconds.

When the RADIUSUBand or RADIUSUBandClear page sets are being used and Bandwidth Manager is enabled, the disconnect window provides an estimated summary of the session time and charges and does not close automatically.

When an end user uses a prepaid RADIUS account or an access code by duration, the BBSM Toolbar (with the Disconnect button loaded) shows the number of minutes remaining until the session ends. At the end of the session, the toolbar displays that the user is out of time, and the session terminates.

When the DailyHotel page set is being used, the iport_tools page is not loaded and therefore is not displayed.

To display or not display the BBSM Toolbar and enable or disable its utility buttons, you make modifications on these pages:

–Modify the xxxPost page to display or not display the BBSM Toolbar.

–Modify the iport_tools page to enable or disable the toolbar buttons.

For an example of modifying the DailyHotelPost page to display the iport_tools page and enable the Disconnect button, refer to the "DailyHotelPost.asp" section.

•Display characteristics—Modify the xxxPost page to change the display characteristics of the BBSM Toolbar. For example code, refer to the "DailyHotelPost.asp" section.

Step 10 Enabling/disabling Bandwidth Manager—Use the GetManageBandwidth method of the NotifyBilling object to add or remove support for bandwidth management in your page set. This feature enables the end user to select the session's bandwidth policy. The bandwidth and pricing options are defined in the page set's package file (for example, DailyHotelPackage.asp). Refer to the "GetManageBandwidth Method" section.

Step 11 Enabling/disabling Public-Private IP Addressing—Use the IsNetworkMultinet method of the NotifyBilling object to add or remove support for public-private IP addressing in your page set. This feature enables the end user to select a public or private IP address type for the session. The page set ties each IP type or IP type and bandwidth policy to a package price available in the page set, as defined in the page set's package file. Refer to the "IsNetworkMultinet Method" section.

Step 12 To configure or change the other page set parameters in the package file, refer to the section on the page set that you are customizing in the "BBSM Template Page Sets." The following steps describe how to configure the package file. The DailyHotel page set parameters are used as an example:

a. Using Microsoft Notepad, open the NewNamePackage.asp file.

b. Note the following default code that will be changed in this example:

–Change the page set name so the end user can view only the pages he or she is supposed to view.

–Change the end time for the billing cycle from 24 hours after start of session to 4:30 p.m.

–Post charges at the end of the session instead of the beginning.

–Allow user to continue his or her session at the end of the session boundary instead of disconnecting him or her.

–Welcome back any client on the port instead of welcoming back the initial client on any port in the property.

–Change the pricing for package 1 from 9.95 to 10.95.

We are also removing several bandwidth options. Refer to the "DailyHotelPackage.asp" section for additional detail about each variable.

<%
var strPageToCheck = "DailyHotel";

// Use the strSessionBoundary variable to control the checkin-to-checkout
// cycle. The daily access policy uses this variable to determine when a
// session boundary occurs. You can leave it blank for the session boundary
// to be 24 hours from the start of the session. If you specify a time, the
// session boundary occurs at that time, regardless of session start time.

var strSessionBoundary = "";

// Use the bPostAtStart variable to control when the daily access policy
// performs the accounting function for the session. If this variable is
// true, the daily access policy will perform the accounting function at
// the start of the session and at each session boundary. If this variable
// is false, the daily access policy will perform the accounting function
// at each session boundary and at the end of the session.

var bPostAtStart = true;

// Use the bRenewSession variable to control what happens to a session at
// a session boundary. The daily access policy will renew the session if
// this variable is true. Otherwise, the daily access policy will kill the
// session.

var bRenewSession = false;

// Use the bWelcomeBackMAC variable to control how the daily access policy
// records information to implement the welcome back feature. The daily
// access policy will record information about the specific MAC address
// and welcome back that MAC address on any port if this variable is true.
// If the variable is false, the daily access policy will welcome back any
// MAC address on this port only.

var bWelcomeBackMAC = true;

var PackagePublicPrivateIPArray = new Array
(
1, // package 1, multinet 1
1, // package 2, multinet 1
1, // package 3, multinet 1
2, // package 4, multinet 2
2, // package 5, multinet 2
2 // package 6, multinet 2
)

var PackagePriceArray = new Array
(
9.95, // package 1, 9.95
7.95, // package 2, 7.95
1.95, // package 3, 1.95
10.95, // package 4, 10.95
8.95, // package 5, 8.95
2.95 // package 6, 2.95
);
var PackageKbpsArray = new Array
(
0, // package 1, full speed
512, // package 2, 512 Kbits/sec
64, // package 3, 64 Kbits/sec
0, // package 4, full speed
512, // package 5, 512 Kbits/sec
64 // package 6, 64 Kbits/sec
);
%>
<% // BBSM ProductVersion 5.3.0 %>

Step 13 To change the strPageToCheck parameter to ensure that the end user can view only the web pages that he or she is allowed to view, replace the default page set name, as in the above example, with the name of your new page set. BBSM stores a page set name per port, which allows the page set to verify if an end user is permitted to view the page. These pages implement this control by using the CheckPage method. Refer to the "CheckPage Method" section.

Note Later in the procedure you will also change the name of the page set in the Windows registry. The strPageToCheck name in the package file and the name in the registry must be the same. The name is not case sensitive, so DailyHotel is the same as dailyhotel.

c. To configure or change strSesssionBoundary parameter so that the end time for your billing cycle changes 24 hours after the start of the session to 4:30 p.m., enter 16:30 between the quotes. The following rules apply to this parameter::

–Use a string of the form HH:MM, where HH = the hours in the range 0 through 23 (0 means midnight, 12 means noon, and 23 means 11 p.m.) and MM = the minute in the range 00 through 59.

–The following example shows the system default session boundary of noon. As shown, placing a space between the quotation marks also sets the system default to noon:

var strSessionBoundary = "12:00"
var strSessionBoundary = " "

–This example shows an example session boundary of 2:30 p.m.:

var strSesssionBoundary = "14:30"

Note If a customer activates shortly before the time set for the session boundary, the session could end very soon after it starts. For example, if the session boundary is set for 12 a.m. (midnight) and a customer activates a session at 11:30 p.m., the session terminates at 12 a.m. (1/2 hour later). However, if another customer activates a session at 12:30 a.m., the session terminates at 12 a.m. the next day.

–To set the time so that the session ends 24 hours after activation, modify the line to specify an empty string for the session boundary (with no space between the quotation marks); for example, as follows:

var strSesssionBoundary = ""

d. To configure or change the bPostAtStart parameter to post charges at the end of the session, change it to false.

e. To configure or change the bRenewSession parameter to deactivate an end user at the end of a session so that he or she can continue their internet session and be automatically charged, change it to true.

f. To configure or change the bWelcomeBackMAC parameter, refer to the following information about how the parameter works:

–Setting the parameter to true—After the end user authenticates, he or she can reconnect until the session boundary without being charged. The user can log in from anywhere on the property (any port).

–Setting the parameter to false—After the end user authenticates, that room (port) will now allow anyone to reconnect until the session boundary. This includes the original user that authenticated as well as anyone else that enters the room. No other ports on the property will allow the original user to reconnect, only that one port.

g. To configure or change the PackagePriceArray pricing of package 1 from 9.95 to 10.95, change 9.95 to 10.95 at the beginning of the line. We recommend that you change the corresponding dollar amount following the // comment mark to the same figure. You can add or remove pricing packages as you want. You must also remove the corresponding PackageKbpsArray lines.

h. To remove 64 kbps and 128 kbps PackageKbpsArray pricing packages, remove the appropriate lines in the code. Then you need to remove the corresponding PackagePriceArray and PackagePublicPrivateIPArray lines. Be sure to remove the trailing comma from the last entry in each array.

Note If items are removed from the price and kbps arrays, you also need to change the PackagePublicPrivateIPArray (multinet) array. All arrays should have the same number of elements.

i. Note that your parameters have changed to the following:

<%
var strPageToCheck = "NewName";
(
strSessionBoundary = "16:30";
bPostAtStart = false;
bRenewSession = true;
bWelcomeBackMAC = false;

var PackagePriceArray = new Array
(
10.95, //package 1, $10.95
7.95, //package 2, $7.95
5.95 //package 3, $5.95
);
var PackageKbpsArray = new Array
(
0, //package 1, full speed
512, //package 2, 512 Kbits/sec
256 //package 3, 256 Kbits/sec
);
var PackagePublicPrivateIPArray = new Array
(
1, //package 1, multinet 1
1, //package 2, multinet 1
2, //package 3, multinet 2
);
%>

j. Save your changes and exit Notepad.

Go to the following steps as needed for your new page set:

•If you created a custom access policy, go to Step 14.

•If you created a custom accounting policy, go to Step 15.

•If you are not using a custom access or accounting policy, proceed to Step 16.

Step 14 If you are using a custom access policy that you created using the BBSM interface SDK, you must modify the post page of your page set to invoke your new access policy. Each default template page set contains a post page that invokes the SendActivateSession method provided by the web interface object of the access policy. For example, if the page set uses the Daily access policy, the page set calls SendActivateSession using the AccessPolicyDailyASP web interface, as shown below:

AccessPolicyDaily = Server.CreateObject
("AccessPolicyDailyASP.WebInterface.1");
strErrorURL = AccessPolicyDaily.SendActivateSession ("Hotel", "Internet
Session",
obj.ExpandURL("http://%iport%/ekgnkm/iporterror.asp?msg=Accounting+Denied"),
obj.ExpandURL("http://%iport%/ekgnkm/iporterror.asp?msg=SendActivateSession+
failed"),
PackagePriceArray [intPackage - 1], PackageKbpsArray [intPackage - 1],
strSessionBoundary, bPostAtStart, bRenewSession, bWelcomeBackMAC);

To customize this for your access policy, change the name of the class passed to the Server.CreateObject function to use your access policy's ActiveX server component. For example:

AccessPolicyNew = Server.CreateObject ("AccessPolicyNewASP.WebInterface.1");

Change the call to SendActivateSession to use your ActiveX server object. For example:

strErrorURL = AccessPolicyNew.SendActivateSession ("Hotel", "Internet Session",
obj.ExpandURL("http://%iport%/ekgnkm/iporterror.asp?msg=Accounting+Denied"),
obj.ExpandURL("http://%iport%/ekgnkm/iporterror.asp?msg=SendActivateSession+
failed"),
PackagePriceArray [intPackage - 1], PackageKbpsArray [intPackage - 1],
strSessionBoundary, bPostAtStart, bRenewSession, bWelcomeBackMAC);

If your access policy requires different parameters in the SendActivateSession method, modify the call to SendActivateSession so it conforms with your access policy.

If you are using the standard BBSM accounting policy in the page set that you are customizing then there are no more changes required to your post page and you can skip to step 16.

Step 15 If you are using a custom accounting policy that you created using the BBSM interface SDK, you will need to modify the parameters passed to SendActivateSession to support your new accounting policy.

strErrorURL = AccessPolicyNew.SendActivateSession (<your-accounting-policy>,
<your-accounting-info>,
obj.ExpandURL("http://%iport%/ekgnkm/iporterror.asp?msg=Accounting+Denied"),
obj.ExpandURL("http://%iport%/ekgnkm/iporterror.asp?msg=SendActivateSession+
failed"),
PackagePriceArray [intPackage - 1], PackageKbpsArray [intPackage - 1],
strSessionBoundary);

The first parameter passed to the SendActivateSession method is usually the name of the accounting policy, and the second parameter is the accounting info parameter. In the DailyHotel example in Step 14, the accounting policy is Hotel and the accounting info is Internet Session. The Hotel accounting policy uses the Internet Session string to indicate the call type to post to the PMS. If you have created a custom accounting policy, you may have custom accounting information that the user entered and that needs to be passed into your accounting policy. For example, the DailyICS page set prompts the end user for his or her credit card information and then formats the information into a string that looks like this (refer to DailyICSPost.asp):

<CCard>
<Name>John Doe</Name>
<Acct>1234123412341234</Acct>
<ExpYr>2002</ExpYr>
<ExpMo>10</ExpMo>
<Addr>6195 Lusk Boulevard</Addr>
<City>San Diego</City>
<St>CA</St>
<ZIP>92121</ZIP>
<Cntry>US</Cntry>
<Ph>858-526-1000</Ph>
</CCard>

This data is passed as a string in the accounting info parameter of the SendActivateSession method. You can define your own tagged parameters and data elements if needed for your accounting policy.

To remove accounting from your post page, simply pass in a value of Null for the accounting policy name. In this case the accounting info string would be an empty string ("").

Step 16 Change all references to the name of your new page set in all ASP files, such as NewNamePost.asp.

Step 17 In your new subdirectory, replace the default GIF files with any new graphics:

a. Replace background colors with your customized colors.

b. Replace the text and font displayed to the end user with your customized text.

c. Replace graphical references in the ASP files to the names of you new GIF files.

d. If you are not already on a BBSM server, copy the new ASP and GIF files to your BBSM server.

Note The following steps require a BBSM server.

Step 18 Register your page set and add it to the list of BBSM available page sets.

a. From the BBSM Dashboard, click WEBconfig. The BBSM Server Settings web page appears.

b. In the NavBar, select the Custom Page Sets web page. The Custom Page Sets web page appears. (See Figure 3-1.)

Figure 3-1 Custom Page Set Web Page

c. Add the custom page set to BBSM based on the information shown in Table 3-1 and click Save.

Table 3-1 Custom Page Set Options

Field

Description

Page Set

Enter the name of the page set.

Start Page

Enter the complete URL of the Start page for your page set. The URL must be in the form http://%iport%... because BBSM translates %iport% to be either the BBSM internal IP address or the BBSM domain name, if applicable. For example, if you saved your page set in a new directory within the c:\atcom\ekgnkm directory, type the following: http://%iport%/ekgnkm/YourNewDirectory/NewNameStart.asp

The %iport% is automatically expanded to the IP address or domain name of the BBSM server.

Caution If your Start page requests sensitive information from the end user, you should use SSL, and the protocol part of the URL will be https, instead of http.

Buttons

New

Adds a new page set. A new blank web page appears so the page set and Start page can be added.

Requery

Refreshes the web page (before saving the changes).

Save

Saves the changes made to the web page.

Delete

Deletes this page set.

Step 19 Test your new page set:

a. Physically connect a client to a port.

b. From the BBSM Dashboard, click Port Control. The Port List web page appears.

c. In the left-hand column, check the port that the client is connected to and then click Port Settings. The Port Settings window pops up.

d. From the Page Set drop-down menu, choose your page set. The Start Page text box automatically populates with the URL of your Start page. Click Save.

e. Open the browser on the client. Your Start page should be displayed. If BBSM displays error messages, refer to the "System and Error Messages" section for an explanation of these messages.

Note If your page set uses SSL, you must have a valid certificate installed on your server to test your pages. If you do not have a certificate installed, you will be unable to view the secure pages when you connect a client. For testing purposes, you can make your BBSM a certificate authority and then sign your own certificate. This procedure should be used only on a development server and never on a release server. You cannot use this method to install a valid certificate on your server. For detailed instructions, refer to the appendix on installing an SSL certificate in the Cisco BBSM 5.3 Interface SDK Developer Guide.

f. Verify that your changes were made.

g. If you want to debug the ActiveX server components used in your pages, install the Microsoft development environment on your BBSM server and refer to the section on standalone debugging of ActiveX server components in the Cisco BBSM 5.3 Interface SDK Developer Guide.

Supplemental ASP Pages

These sections describe one ASP file that you can use to change your page set's functionality and the ASP files that report system and error messages.

Using the CommonSubroutines Page

BBSM provides the following functions that are tools to help ensure that the interface you create is consistent with the interface contained in the BBSM page set templates. Although most of these functions already exist by default in the page set templates, they are listed here only so that you will be familiar with them in case you need to use them in your new page set.

These tools are provided in the CommonSubroutines page, which is located in the c:\atcom\ekgnkm folder. To modify an ASP file, you would include the CommonSubroutines page and modify the appropriate functions. For details about the functions, refer to the "Commonly Used JScript Functions" section. They are briefly described below:

•FormatPrice—Displays a price to an end user, administrator, operator, or reports viewer. Using this function ensures that every price has the same format.

•FormatDuration—Formats the duration of a session.

•BandwidthKbpsToString—Converts a numeric bandwidth value into a user-readable string (complete with units and handling the special case of zero, which means full-speed or unrestricted).

•GenerateComboBox—Generates an HTML SELECT tag of bandwidth/price packages.

•MDSubGenerateComboBox—Generates an HTML SELECT tag of bandwidth/price/days packages for a bandwidth upgrade for the Single/Multiple Day Subscription page set.

•MDSubGenerateNBComboBox—Generates an HTML SELECT tag of price/days packages for the Single/Multiple Day Subscription page set.

•GenerateUpgradeComboBox—Generates an HTML SELECT tag of bandwidth/price packages for a bandwidth upgrade.

•OutputYear—Generates an HTML SELECT tag of years that always includes the current year and several years into the future.

•FormatPublicPrivateIP—Specifies the explanatory text associated with each of the two multinets; for example, Private for multinet 1 and Public for multinet 2.

•GenerateMultinetComboBox—Generates an HTML SELECT tag of bandwidth/multinet/price packages.

•PackageEnabled—Used by the combo box generation methods to determine which multinet packages can be presented to the client.

System and Error Messages

This section describes the ASP files that display system and error messages to the end user. BBSM uses these ASP files, located in the c:\atcom\ekgnkm folder, to report system and error messages to the end user. The ASP files can be modified to a certain extent, as necessary, by following the guidelines shown in this guide. Table 3-2 describes the function of these ASP files.

Table 3-2 BBSM System Message ASP Files and Error Messages

ASP File

Function

default.asp

Displays an error message when the client is already connected but a specified URL cannot be returned; for example, if the Domain Name System (DNS) cannot be resolved.

iporterror.asp

Displays a number of error messages that BBSM returns. These are three example error messages:

•CheckPage failed—The page set name that is set with the strPageToCheck variable on the package page does not correctly match the page set name that is set on the Page Sets web page in WEBconfig. Check both places to ensure that they match. This mismatch can also occur if an end user tries to manually type a Start page URL into the browser address that they are not permitted to access.

•Invalid package—The price, bandwidth, and/or multinet package is not being set correctly. If you are using a custom page set, make sure the strPackage variable is still being used and is spelled correctly in your Start page. Verify that the CommonSubroutines.asp is still being listed as an include file at the top of your Start page and check your package page to make sure that PackagePriceArray, PackageKbpsArray, and PackagePublicPrivateIP Array have an equal number of array members.

•SendActivateSession failed—An error occurred while BBSM was trying to authenticate and approve an end user for an Internet session.

searching.asp

Displays the Searching for Client message. This page generally occurs when there is a delay in determining the correct configuration for the client after the end user requests an Internet session. BBSM returns one of these messages: an error message, such as authentication failed, an error stating that the maximum user capacity has been reached, or a message that the system will continue searching.

terms.asp

A link to this page is displayed on the Start page. This ASP page is used to display to the terms and conditions of accessing the Internet at this property.

trouble.asp

A link to this page is displayed on the Start page. This ASP page is used to display error information to the end user when the end user cannot connect to the service and clicks the Having trouble viewing this page? link.

unavailable.asp

Displays an error message when the AtDial service is suspended due to configuration changes through WEBconfig. Any changes using WEBconfig require that the service is stopped and then restarted for the changes to take place. While in this transition phase, this page is displayed to users attempting to connect.