Here we describe the Messaging functionality with all options that can be set by an Certified Alarm server and how it is displayed to the user.
1. Full screen message |
An DECT handset that is in IDLE mode when receiving an Message (Not for prio 9) will show this full screen on the handset display.
1 Message title | |
2 Message icon | |
3 Paragraph Contains the main content of the message (text only), multiple lines/paragraphs are supported | |
4 Reply options By the message server defined Softkeys, when pressed will send an feedback to the messaging server |
2. Message list |
The Message list can be opened by pressing the blinking MWI key .
This list contains Messages:
Messages where TTL time has passed will be removed from the message list automatically.
1 Message list headline Fixed text when opening the message list, newest message is on top | |
2 Message title | |
3 Message list body starter Message body starter text send by the message server to describe the message using limited number of characters | |
4 Date/time The date/time stamp when the message is received | |
5 Status information | |
6 Softkeys | |
7 Message list icon Icon to indicate the message type |
3. Message priority |
Every message has it's own priority, set by the Alarm server. Below the overview about the priority behavior.
Prio | Type | Intrude active VoIP Call | Play ringtone | IDLE screen | Interrupt local menu | Interrupt online menu | Increase MWI message counter | Description |
---|---|---|---|---|---|---|---|---|
1 | Call based | • | • | • | • | • | • | Prio 1/3/6 are call based messages. When using call based messages, you have to look at the maximum parallel call system capacity. For example and N870 can handle up to 60 parallel calls, this means that when no handset is in a call, up to 60 messages can be send. If handsets are in a call, these have to be counted in the maximum signaling of messages. By using an Integrator it is easy to increase the number of parallel calls. Prio 2/4/5/7 are not defined and could be used in the future if more prio levels are needed. |
2/3/4=3 | Call based | - | • | • | • | • | • | |
5/6/7=6 | Call based | - | • | • | • | - | • | |
8 | IDLE display | - | "toc","toc" | • | - | - | • | Prio 8 messages are shown when the handset is in IDLE and does not occupy an DECT channel during signaling but briefly occupies an DECT channel during start of signaling. |
9 | Broadcast | - | "toc","toc" | - | - | - | • | Prio 9 messages, you need to open the message list to read the message. Occupies briefly an DECT channel during start of signaling |
4. Message ringtones |
Click here to see the list with available ringtones:
|
5. Message title |
The "title" is the
The title:
6. Message icons |
Message icons type R700H/S700H/SL800H:
Message icons type/color:
Up to 5 colors are supported:
7. Message paragraph |
Message Call (prio 1-7) | Info Display (prio 8) | Message list (prio 9) | |
---|---|---|---|
line of text | multiple | max 3 line of text | multiple |
paragraph | 2 | 1 * | 2 |
scrollable | yes | no | yes |
decoration (blink/underline/bold/align) | yes | no | Yes |
alignment | depends of decoration (default left) | center | depends of decoration (default left) |
8. Message reply options |
9. Message list body starter |
10. Message list status |
Supported icons:
11. Message list icons |
12. Local ignore |
The messaging server can send an "local_ignore" "yes/no" via the MQTT interface. (Example: "local_ignore":"yes",)
"Local_ignore" is "yes" | On incoming prio 1/3/6 message can be stopped the user by pressing the on-hook key. The handset goes to IDLE screen |
"Local_ignore" is "no" | A user can not stop the prio 1/3/6 message by pressing the on-hook key. The user needs to use the reply softkeys. When pressing the on-hook key the ringtone will stop but the message is still visible on the display. |
13. Presentation timer |
The presentation timer is the time that the message will be signaled on the handset:
14. Time To Live (TTL) |
The TTL timer defines how long (seconds) a Message will stay in the system.
15. Overrule silencing |
If allowed by the administrator, the user can change the handset settings, that can cause incoming alarm messages not signaled in a proper way.
Via a new MQTT command, the following user settings can be overruled.
Requirement:
MQTT command |
---|
"overrule_silencing":"yes", |
16. Overrule vibration |
If allowed by the administrator, the user can disable the handset vibration setting.
Via a new MQTT command, the vibra can be activated to signal the incoming message. The vibra setting itself is not changed.
Requirement:
17. Overrule message ringtone volume |
If allowed by the administrator, the user can change the message ringtone volume.
Via a new MQTT command, the ringtone volume of the incoming message can be changed from 00% to 100% . The ringtone volume setting itself is not changed.
Requirement:
The following handset settings can be overruled with this MQTT command
18. Delete messages from the message list |
If allowed by the administrator, the user can delete messages from the message list.
Via a new MQTT command, the user is allowed (or not) to delete messages from the message list.
Open the message list, select the message, click on Options and depends on the message option send by the AML server, the message can be deleted yes or no.
Requirement:
19. Documentation |