Wazo Mobile uses Push Notifications to enable receiving calls and text notifications when the mobile application is not in the foreground.
Context :
Previously, this had to be configured via the Google Firebase API, but this is no longer the case.
However, as this API is being discontinued (final termination in June 2024), Wazo now has its own Push Notifications tool for Android mobile devices.
Limitations :
- Your stack must be on version >= 23.17 (see documentation on Updating your E-UC Stack).
Actions to be performed on each site (tenants) that have external authentication of the Mobile type.
Manual Migration
In the location menu (tenant), browse to Seetings > Credentials > External Auth. And delete source type "Mobile".
We advise you to disconnect/reconnect users from their Wazo Mobile application.
Automated migration
Install the stack plugin that will allow you to modify the external authentication configuration across all Tenants in your Stack.
Pre-requisite:
-
Stack must be at least 23.17 or onward.
-
Paquet
wazo-plugind-cli
must be installed
Check the installation status using wazo-plugind-cli --help
if no error comes out then everything is ok.
Otherwise, use :apt install wazo-plugind-cli
Once done, you can launch the plug in installation (see below)
Note:
Warning !!
Mobile users will need to restart their mobile application for the migration to be complete and for push notifications and calls to function properly. Calls received after the migration and before the application restart will be lost.
If the mobile application is already active and in the foreground at the time of migration, the application will need to be closed and reopened for push notifications and calls to work.
This plugin will send a notification to each mobile user on the server before performing the migration. The migration is done tenant by tenant.
Plugin installation
wazo-plugind-cli -c "install git https://github.com/wazo-communication/wazo-android-push-proxy-migration-plugin"
During the plugin execution, you can check the logs in : /var/log/wazo-android-push-proxy-migration.log
Services will not reboot using the plugin.
The installation may take some time for Stacks with many users or tenants, approximately 1 minute for every 1500 tenants, plus 1 minute for every 200 users. This means around 11 minutes for 2000 users across 1500 tenants.
Remove the plugin from the Stack
Once the migration is completed, we advise you to remove the plugin as it will serve no purpose on the Stack. This action will not impact the configuration.
wazo-plugind-cli -c "uninstall wazocommunication/wazo-android-push-proxy-migration"