Table of Contents Table of contents: Radiator® AAA Server <AuthBy FIDELIO> 3.82 - <AuthBy FIDELIO> <AuthBy FIDELIOHOTSPOT> 3.84 - <AuthBy FIDELIOHOTSPOT>

3.83. <AuthBy HOTSPOTFIDELIO>

<AuthBy HOTSPOTFIDELIO> combines <AuthBy HOTSPOT> and <AuthBy FIDELIO> to an easy way to integrate WiFi hotspots and captive portals with Opera hotel Property Management System from Micros Fidelio Opens in new window.
It uses a service database to keep track of prepaid access time blocks for Opera guests and tracks ongoing sessions with a session database. It authenticates new sessions with the guest's room number and guest number (as with <AuthBy FIDELIO>), creates new prepaid blocks (and posts the charge to Opera). Time-limited prepaid plans are supported.
<AuthBy HOTSPOTFIDELIO> understands also the same parameters as <AutBy HOTSPOT> and <AuthBy FIDELIO>. For more information, see Section 3.81. <AuthBy HOTSPOT> and Section 3.82. <AuthBy FIDELIO>. <AuthBy HOTSPOTFIDELIO> supports also all the common SQL configuration parameters. For more information about the SQL configuration parameters, see Section 3.8. SQL configuration.
For a configuration sample, see files goodies/README.hotspot-fidelio and goodies/hotspot-fidelio.cfg. The sample configuration provides also an example of dynamically changing user sessions when they exceed their parameters, such as prepaid quota limits.

Figure 3. AuthBy HOTSPOTFIDELIO with dynamic authorization

radiator-hotspotfidelio.jpg

3.83.1. BlockDuration

Specifies a number of seconds a prepaid block of time will last for, from the time it is first purchased. Defaults to 86400 (1 day).

3.83.2. BlockPrice

Specifies a number of cents a prepaid block of time costs. Defaults to 900 cents ($9.00). This cost will be posted to Opera whenever a new block is purchased.

3.83.3. PostSendQuery

This optional string defines the exact form of the insert query that is used to insert posting records.

3.83.4. PostSendQueryParam

This optional string array enables the use of SQL bind variables with PostSendQuery. Set PostSendQuery using the SQL bind variables or without them. If you use the SQL bind variables, you must specify all query parameters with respective PostSendQueryParams. Here is an example of using the SQL bind variables:
PostSendQuery INSERT INTO posts (roomNumber, guestNumber, macAddress, postNumber, 
      posted, cost) VALUES (?, ?, ?, ?, ?, ?)
PostSendQueryParam %0
PostSendQueryParam %1
PostSendQueryParam %2
PostSendQueryParam %3
PostSendQueryParam %4
PostSendQueryParam %5
The same query without the SQL bind variables looks this:
PostSendQuery INSERT INTO posts (roomNumber, guestNumber, macAddress, postNumber, 
      posted, cost) VALUES (%0, %1, %2, %3, %4, %5)
For more information about SQL bind variables, see Section 3.8.1. SQL bind variables.

3.83.5. PostAnswerQuery

This optional string defines the exact form of the insert query that is used to insert Posting Answer (PA) data.

3.83.6. PostAnswerQueryParam

This optional string array enables the use of SQL bind variables with PostAnswerQuery. Set PostAnswerQuery using the SQL bind variables or without them. If you use the SQL bind variables, you must specify all query parameters with respective PostAnswerQueryParams. Here is an example of using the SQL bind variables:
PostAnswerQuery INSERT INTO postacks (roomNumber, postNumber, transactionNumber, received) 
      values (?, ?, ?, ?)
PostAnswerQueryParam %0
PostAnswerQueryParam %1
PostAnswerQueryParam %2
PostAnswerQueryParam %3
The same query without the SQL bind variables looks this:
PostAnswerQuery INSERT INTO postacks (roomNumber, postNumber, transactionNumber, received) 
      values (%0, %1, %2, %3)
For more information about SQL bind variables, see Section 3.8.1. SQL bind variables.
Table of Contents Table of contents: Radiator® AAA Server <AuthBy FIDELIO> 3.82 - <AuthBy FIDELIO> <AuthBy FIDELIOHOTSPOT> 3.84 - <AuthBy FIDELIOHOTSPOT>