The General Settings tab of the integration could be mainly used for informational purposes as well as updating the API Key Token used for connecting the integration. The properties available on it are:
- API Key Token: holds the API Key Token used for connecting the integration.
- Region: The Region used for the IronWiFi account.
- Primary IP: used when configuring the Wi-Fi infrastructure to work with IronWiFi.
- Backup IP: used when configuring the Wi-Fi infrastructure to work with IronWiFi.
- Authentication Port: used when configuring the Wi-Fi infrastructure to work with IronWiFi.
- Accounting Port: used when configuring the Wi-Fi infrastructure to work with IronWiFi.
Location-specific check-ins provide a way for operators to enable per-location presence tracking that utilizes the IronWiFi integration.
To enable the functionality, operators need to go to the Location tab of the integration settings and map each of their locations (OfficeRnD entities) to all the access points (IronWiFi entities) that should be associated with the respective location. The following rules apply:
- Each location could be selected only once.
- Each access point could be mapped to only 1 location.
Once the mapping is done members will be checked into the location associated with the access point they connect to.
Check-in & Check-out latency
Check-in & Check-out latency allows operators to define the amount of time a member should be connected or disconnected from the Wi-Fi Network before check-in or a check-out is registered.
The setting could be useful if operators don’t want to charge a day pass customers who are passing by just to pick up something or do not spend more than 30 min in the building for some reason.
- Both settings could be configured with values between 5 and 30 min.
- The default value for a newly activated integration would be set to 5 min.
Important: The Check-ins Latency setting should not be confused with the time it will take OfficeRnD to make the check-in/check-out visible in the system. We are using a 15 min schedule to update the check-in and check-out information and there is no relation between the schedule and the check-in latency setting.
The way the check-in latency works is that with every 15 min scheduled, we are comparing the time that the user has been connected to the Wi-Fi and record a check-in/check-out only if the condition from the setting is met.
Please sign in to leave a comment.