Mitel Forums - The Unofficial Source
Mitel Forums => Mitel Software Applications => Topic started by: sunspark on April 05, 2018, 06:07:35 AM
-
Hi guys ,
I have Micollab in lan mode with two Mbg in Dmz.
Micollab :in the last release 8.0.2.10 and Mbg in the last release 10.0.2.14.
when the micollab run in background i can't receive calls .
Any idea ?
Thanks
-
Hi guys ,
I have Micollab in lan mode with two Mbg in Dmz.
Micollab :in the last release 8.0.2.10 and Mbg in the last release 10.0.2.14.
when the micollab run in background i can't receive calls .
Any idea ?
Thanks
Any device, or only some devices? We have found that low RAM or "budget" Android devices, or ones with significant other stuff loaded, that when MiCollab is running in the background it can get auto-killed by the Android kernel's RAM management. You can tell this because when you try to bring to the foreground, the app appears to be restarting and not just moving to the foreground. I really would recommend a minimum of 2GB of RAM for any Android device running MiCollab, 3GB is preferred, not that MiCollab needs it but it prevents the OS from killing it when multitasking to free up RAM when it thinks it's not being used.
Also, some devices and optimization or battery saver apps will disable data connection when the screen is off sometimes, that causes a real problem.
We have also seen some Android 7+ devices where deep sleep mode causes MiCollab softphone to not ring, going to Settings - Battery - Battery Optimization, All Apps, and setting MiCollab to Don't Optimize can correct this issue. (Settings menu location may vary by device)
We have not seen this issue on Apple devices at all.
Might not be your issue, but just went through some of this a few months ago... just thought I would throw this out there.
-
Hi Ace ,
I have the issue with all device.
I dont' know if the issue because i use 2 MBG with custom DNS SRV.