We have installed a wifi system in a great customer, we are expecting a problem with iphone mobiles, but not with android mobiles. When iphones are connected to the wifi, after pressing the sleep/weak bottom (the screen protector bottom) after 5 minutes without touch anything , when user unblock the mobile again, the iphone has closed the wifi session, and users must to click a "accept" in the official redirected webpage.
in the android mobiles it does not occur, just unblock the mobile and they can keep on navigating in internet.
May be it could be a lost packet in IOS? or something else?
The configuration is a web policy with web passthrough and open wifi.
Yes, this is to be expected of iPhone and iPad. It doesn't matter if you're connecting to an OPEN SSID with Web Redirect or a full authentication server, if the iDevice goes to "sleep" (either you trigger the on/off switch to go to sleep, you leave the iDevice unattended and it goes to sleep, or after 20 minutes), when you "wake it up", it will go through the motion of re-authenticating to the wifi network.
If you configure the user idle timeout on the controller past 300 seconds (5 minutes) the controller will keep the ipad record. The issue is the idevices sleep and don't send any frames. The controller thinks it walked off and deletes the record. This is why you get the screen. Hope this helps.
Sent from Cisco Technical Support iPad App
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
If the app pauses or moves to the background for more than 10 seconds, the next time the app runs, Flurry agent will automatically create a new session and end the previous session. Otherwise, Flurry agent will continue the same session. If the app is terminated, a new session will be created when the app runs again.
Enter a value for Sleeping Client Timeout, which is the timeout for sleeping clients.Sleeping clients are clients with guest access that have had successful web authentication that are allowed to sleep and wake up without having to go through another authentication process through the login page.This sleeping client timeout configuration overrides the WLAN-specific sleeping client timeout configuration.