Set up automatic check-ins
To set up automatic check-in functionality, you must also configure the accounting data collected by your infrastructure to be sent to IronWiFi. This feature is called RADIUS accounting and allows you to configure where the accounting data captured from the network devices is sent.
Please note that not all network gear has it, and your devices may not be able to enable automatic check-ins based on WiFi.
As this configuration is done in your network devices, it varies from vendor to vendor. Generally, you must configure one more host, port, and secret, so that this data is sent over.
Verify the configuration
To verify if you've set up the accounting feature correctly, do the following:
Log in to the WiFi network with a new user who has received access through the OfficeRnD integration.
Go to the Users list in the IronWiFi console (Users / Users) and verify if the users last seen have been changed.
Go to the Accounting Data report in the IronWiFi console (Reports / Accounting Data).
Verify if a new record for the same user appears there.
Here are instructions on how this is done in Cisco Meraki.
If the record in the report is missing, the accounting data is not actually received in IronWiFi, and you will have to troubleshoot the problem. In such a case, please contact IronWiFi support for assistance.
Set up location-specific check-ins
Location-specific check-ins allow administrators to enable per-location presence tracking that utilizes the IronWiFi integration.
To enable the functionality, admins must go to the Location tab of the integration settings and map each location (OfficeRnD entity) to all the access points (IronWiFi entity) associated with the respective location.
Location rules
Each location can be selected only once.
Each access point can 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. If the mapping is not done or some locations do not have access points associated with them, members will be checked in against their home location.
Check-in and check-out latency
Check-in & Check-out latency allows administrators to define how long a member should be connected or disconnected from the Wi-Fi Network before check-in or a check-out is registered. The settings could be useful if admins don't want to charge day passes for customers who are passing by to pick up something or do not spend more than 30 min in the building.
How it works
The check-in/check-out information is updated every 15 min. In each update, the time the user has been connected to Wi-Fi is compared to the settings defined in the Check-ins tab. A check-in/check-out is recorded only if it matches the settings.
Rules for settings
Both settings can be configured with values between 5 and 30 min.
The default value for a newly activated integration is set to 5 min.
Note: The Check-ins Latency setting should not be confused with when it will take OfficeRnD to make the check-in/check-out visible in the system. There is no relation between the automatic 15-minute schedule and the latency settings.