FAQ - AML: Notification

1. DECT Manager and or DECT Base - Push notification

Scroll to top

By default, the system will notify the Alarm server if an DECT Manager and/or DECT base is down after 9 minutes outage. This value can be changed via auto-provisioning.

2. How to subscribe for notifications

Scroll to top

If you want to receive this information, the alarm server need to subscribe to the MQTT topic.

Example of subscription for any notification.

Example of subscription for notification regarding status of base stations

Example of subscription for notification regarding status of dect managers

Example of subscription for notification regarding the handset status

Where:

-u user needs to be added to external client list (webui settings/online-services/application-servers)

--psk is external client password

-p is psk port

-h is ip address of the device

If the AML server subscribes on the required topic, the system will answer with the status

3. How to request the current DM and Base station status

Scroll to top

With each (new) subscribe or re-subscribe to the above MQTT topic ("Any"), the system will respond with the actual status of the DECT managers and Base stations.

4. DECT Handset - Push notification in/out of charger

Scroll to top

Power status information contains the following elements:

"charger":

Contains info about status about in charger ("in") or out of charger ("off").

"battery_level":

Contains battery charge level in percent (valid values are 0 to 64 hexadecimal), Value 7f indicates that battery charge level is not available for some reason.

For this feature you need:

• DECT system software version 2.53 or higher
• S700H / R700H / SL800H with software release 12 or higher

How to enable this feature:

1. First you need to enable this feature per handset, this is done via the following MQTT command.
   Below an example to activate this feature for handset "1013"

   mosquitto_pub -t 'as1/hs_status/sip_id/1013/req/hs_status' -m '{"msgId": "hs_status_1013","params": {"sip_id":"1013","hs_status":{"power_status":"on"}}}' 

2. If operation was successful, response will be sent with current status:
   

   dm1/1013/as1/hs_status/res/hs_status {"msgId":"hs_status_1013","payload":{"hs_status":{"power_status":"on"},"sip_id":"1013"}} 

   
   

3. If HS does not support sending power status, proper reject reason will be sent:
   

   dm1/1013/as1/hs_status/res/hs_status {"msgId":"hs_status_1013","payload":{"hs_status":{"rej_reason":"feature_not_supported"},"sip_id":"1013"}} 
4. To activate power status notifications, the user needs to power cycle the HS (turn it off and on again) or wait up to 3 hours for next automatic location registration.
   
   
5. After successful activation of power status, notifications will be sent when:
   
   1. HS is put in/out of charger
   2. After location registration (e.g. when HS roams into given DM, when attaching HS after system bootup, automatically every 3 hours)
      
      

6. It will contain status of charging and current battery level (in hex value), e.g.:
   

   dm1/1013/as/hs/noti/hs_status {"msgId":"hs_status_1013","payload":{"power_status":{"battery_level":"5a","charger":"off"},"sip_id":"1013"}}

   
   

5. Documentation

Scroll to top