Show Posts
1
Mitel Software Applications / MiCollab Mobile Client Android issue
« on: August 18, 2015, 04:36:15 AM »
The situation we see is as follows. The MiCollab Mobile Client is used by both android and ios users, connecting to the same fqdn from within the company (wireless, internal network) and outside over mobile networks. When changing from mobile network to wifi, the ios users have no issue and connect instantly (almost) to the internal address of our communication server, but the android phones keep trying to connect to the external ip address of the concerning fqdn.
When checking from the phone itself, it has the correct internal ip address on the wifi, the correct dns servers and does resolve the fqdn to the correct internal ip address. The application however persists, and keeps connecting to the external address on 36008 and 443. We have checked this by using both the concerning firewall and multiple apps (wireshark) to confirm this behaviour. When waiting long enough, the client does connect, but this can take up to 10 minutes. Rebooting the phone and leaving the wifi on does solve it, but this is no solution. It is as if there is some kind of DNS cache in the application that does not get refreshed on the network change.
Is this familiar to anyone and is this a known problem for the Android version? The android phones all seem to have this problem (different versions of android, both 4 and 5 and different brands of phone).
Any help would be appreciated.
When checking from the phone itself, it has the correct internal ip address on the wifi, the correct dns servers and does resolve the fqdn to the correct internal ip address. The application however persists, and keeps connecting to the external address on 36008 and 443. We have checked this by using both the concerning firewall and multiple apps (wireshark) to confirm this behaviour. When waiting long enough, the client does connect, but this can take up to 10 minutes. Rebooting the phone and leaving the wifi on does solve it, but this is no solution. It is as if there is some kind of DNS cache in the application that does not get refreshed on the network change.
Is this familiar to anyone and is this a known problem for the Android version? The android phones all seem to have this problem (different versions of android, both 4 and 5 and different brands of phone).
Any help would be appreciated.