...
| Warning |
|---|
BlackBerry platform does not support Emoji and thus cannot use them both for writing or reading. This is an operating system limitation and it's not recoverable. |
The maximum length of a single message is 160 character, so the input box refuses to let you write more than 160 chars.
| Note |
|---|
Please note there's no concatenation for Secure Messages. If you need to send a message that is longer than 160 characters, then you need to split it in more than one message by yourself. |
How does a Secure Message work?
...
| Icon | Description | Meaning | Timeouts |
|---|---|---|---|
Sending Message | PrivateGSM is actually trying to send the Secure Message to its PrivateServer | ||
 | Message Enqueued | PrivateGSM was able to send the Secure Message which now is in the queue of PrivateServer waiting to be delivered to its destination | PrivateServer keep a message queue for received messages. Every received message through REST api is stored on DB and the server periodically tries to send messages to proper recipient, if connected via SIP. If delivery is not possible because the peer if offline, PrivateServer should retry as soon as recipient registers for up to an expiration period (72h), before removing them definitely from the database. If the user is online but there is a network issue, the server try to deliver the message 5 times every 30 seconds. Those parameters must be configurable at runtime using the internal settings table. If at the fifth attempt the network issue is still present, the retry procedure will be stopped and the message will be sent when the user will return online. |
| Message Delivered | PrivateServer was able to deliver the Secure Message to its receiver. The message could be read as not. | ||
| Error sending Message | This status is a fall back for any other one and it's triggered both by timeouts and error responses. |
...