Hotspot login popup

Hi,
What I’m trying to do is:

I have a hotspot and user connects to it by http-chap.

I want after some time to pop up the user thelogin page.

On mobile phones it can be done only in browsers, when kill the user from hotpot / hosts. In browsers it imediately shows the login page.

But at the ather apps like facebook or viber it show that there is no network connectivity and in hotspot / hosts the user is H (dhcp). The login page is not poped up until opening the browser.

The only turnaroud is after killing the user from hotspot / hosts, to kill the registration from the wireless table too and after that the popup login is displayed in other apps too.

But I have to use many devices that are not mikrotik and can’t kill the wireless registration on them.

I have tried to manage the hotspot flow: http://wiki.mikrotik.com/wiki/Manual:Customizing_Hotspot
I what I found is that the difference between the initial connection to the wireless, the NAT Rules that “have packets” are 0,1,2,4,6,8 . When I kill the user from hotspot / hosts receives packets only rules 0,1,2,6,11. When I start Chome and rules 4,8 generates packets too.

The difference in Filter rules are: new connection → 2,4,5,6 After killing the user → 0,2,4,6,8

Can I popup the login page in other apps that browsers, without dropping the wireless registration?

I could’n find any hotspot flow diagram.
Any help will be appreciated!
Thanks in advance!

After some testing, research, packet sniffing found that when a phone/tablet (tested only with iOS), connects for the first time or reconnects after being killed from wireless registration table it check by HTTP one of the following addresses:
www.airport.us
www.thinkdifferent.us
www.appleiphonecell.com
captive.apple.com
www.itools.info
www.ibook.info

If the address retunt “success” the login popup is not shown.

But if returns Error 302 login is required, the the popup shows.

After killing the active host from the hotspot and the user is using app like viber, it can’t understand that need to login again, because tries to make some ssl connection to another hosts.

When returns to browser and make some page request the browser receives Error 302 and open the login page.