Installation and configuration
The application can be installed using any MDMMobile Device Management platform or manually by installing a generated .apk file from the mobile device’s file system.
After installation, all required permissions must be granted when the application is first run.
PhoneServices URL configuration
The Phone Services URL needs to be set up. This service provides the possibility to list the alarm history of groups which the mobile device is part of.
The PhoneServices URL can be setup either by using the MDM tool or by providing it manually. Manual setup is recommended in cases where the application is used for testing purposes. If the phone is part of an MDM system, the MDM configuration is evaluated with higher priority and overwrites any manual configuration.
Cruise Alarming Mobile implements managed configuration settings, so the URL can be setup by setting the service_address attribute via the MDM IT admin console. In case of the MDM console being unable to read the configuration schema, the SET_HOST_ADDRESS intent can be fired using the service address as parameter.
Example: Set the PhoneServices URL using SOTI MDM:
sendintent -b "intent:#Intent;action=com.callistocruise.alarming.intent.action.SET_HOST_ADDRESS;S.service_address=http://<callisto>/Applications/Inbound/Alarm%20Service/src/PhoneListAlarms.asp?version=2;end";
Set the PhoneServices URL using VMWare Workspace ONE MDM:
mode=implicit,broadcast=true,action=com.callistocruise.alarming.intent.action.SET_HOST_ADDRESS,extraString=service_address=http://<callisto>/Applications/Inbound/Alarm%20Service/src/PhoneListAlarms.asp?version=2
In both cases, <callisto> is a placeholder for the IP address or domain name of the Callisto installation.
Hint: Adding the parameter version=2 to the basic URL enables the Alarm Groups Log In/Out feature.
It is crucial that the entered URL is valid, otherwise the application will not be usable.
Always play alarms
The application also provides the possibility to play sounds even when the mobile device is in vibrate or mute mode. This functionality is also available for the do not disturb mode if alarms are allowed to override it (by default, alarms do not override do not disturb mode). This option can be set via the admin console by setting the always_play_sound attribute. It can also be enabled by firing the SET_ALWAYS_PLAY_SOUND intent using always_play_sound as parameter.
Example: Always activate alarms using SOTI MDM:
sendintent -b "intent:#Intent;action=com.callistocruise.alarming.intent.action.SET_ALWAYS_PLAY_SOUND;B.always_play_sound=true;end;"
Always activate alarms using VMWare Workspace ONE MDM:
mode=implicit,broadcast=true,action=com.callistocruise.alarming.intent.action.SET_ALWAYS_PLAY_SOUND,extraBoolean=always_play_sound=true
Important: Activation of the Always play sound option has no effect if the user has turned off Show notifications for the Cruise Alarming Mobile application or if the alarms exception for Do not disturb mode is disabled in the mobile device’s system settings.
Notification sound volume
The sound volume for notifications is can be configured by firing the NOTIFICATION_SOUND_VOLUME intent using the notification_sound_volume parameter. The excepted value is an integer between 0 (lowest volume) and 15 (highest volume).
Example: Set the notification sound volume to 15 using SOTI MDM:
sendintent -b "intent:#Intent;action=com.callistocruise.alarming.intent.action.NOTIFICATION_SOUND_VOLUME;i.notification_sound_volume =15;end;"
Set the notification sound volume to 15 using VMWare Workspace ONE MDM:
mode=implicit,broadcast=true,action=com.callistocruise.alarming.intent.action.NOTIFICATION_SOUND_VOLUME,extraInt=notification_sound_volume=15
Save logs
This function allows log files to be saved on the device for debugging and troubleshooting purposes.
Usually, the logs are saved under the following path:Android\data\com.callistocruise.alarming\files\AlarmSMS\log
Important: Be aware that the actual path can vary depending on the device.
Example: Activate the saving of log files using SOTI MDM:
sendintent -b "intent:#Intent;action=com.callistocruise.alarming.intent.action.SET_SAVE_LOGS;B.save_logs=true;end;"
Activate the saving of log files using VMWare Workspace ONE MDM:
mode=implicit,broadcast=true,action=com.callistocruise.alarming.intent.action.SET_SAVE_LOGS,extraBoolean=save_logs=true
Configuring multiple parameters
All of the listed parameters can be set up using the managed configuration or using Intents. Parameters set within the managed configuration have a higher priority and their values cannot be changed using Intents.
Example: Set up all of the listed parameters using the managed configuration with VMWare Workspace ONE MDM, using custom settings.
<characteristic type="com.airwatch.androidwork.app:com.callistocruise.alarming " uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="service_address" vaule=http://192.168.100.109/Applications/Inbound/Alarm%20Service/src/PhoneListAlarms.asp?version=2 type="string">
<parm name="always_play_sound" vaule="True" type="boolean">
<parm name="notification_sound_volume" vaule="10" type="integer">
<parm name="save_logs" vaule="True" type="boolean">
</characteristic>
Start and stop the service
To be able to receive alarms from Callisto, Cruise Alarming Mobile is active nonstop after the application is launched for the first time. The service is also started automatically after a system reboot. On Android 10 and later, the permission Appear on top must be granted.
The service can be stopped by accessing the system settings and using Force Stop on the Cruise Alarming Mobile application.
