...
| Typing a new Secure Message in history view (BlackBerry) | Typing a new Secure Message in history view (iPhone) | Typing a new Secure Message in history view (Android) | |||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
...
| Info |
|---|
Please note that by convention your outgoing communications are placed on the right side of the screen, as the incoming ones by the chosen number are placed on the left of the screen. |
| "Send" button | Platform | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| iPhone | |||||||||
| BlackBerry | |||||||||
| Android |
You can send your new message pressing the proper "Send" button in the User interface if you're on Android or iPhone, else on BlackBerry you just use the "Enter" key in your keyboard.
Sending Secure Messages from "Contacts"
As stated before, Secure Messages are also available from "Contacts" view which is probably the best way to start a conversation via text messages. Obviously first thing it to reach the contact you want to write to. Please refer to Performing a secure call with PrivateGSM.
Central button on theBlackBerry keyboard | "info" icon in iPhone | "info" icon in Android | |||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
Once you reached the specific number of your peer contact, then you can reach the history of communications between you and that number by pressing the "info" icon in Android and iPhone or just pressing the central button on the keyboard in BlackBerry (please check
, Xref AnchorName bb_central_button
and Xref AnchorName iphone_info_icon
).Xref AnchorName android_info_icon
You'll get exactly the same view shown in
, Xref AnchorName bb_detailed_history
or Xref AnchorName iphone_detailed_history
.Xref AnchorName android_detailed_history
| Info |
|---|
Please note that by convention your outgoing communications are placed on the right side of the screen, as the incoming ones by the chosen number are placed on the left of the screen. |
...
So you can now type your message, just as in
| Xref | ||
|---|---|---|
|
| Xref | ||
|---|---|---|
|
| Xref | ||
|---|---|---|
|
You have to select an account from the list shown in
| Xref | ||
|---|---|---|
|
| Xref | ||
|---|---|---|
|
Once you select the desired phone number of the account you want to send Secure Messages to, then you get the view shown in
| Xref | ||
|---|---|---|
|
Secure Messages status icons and known limitations
Each Secure Message is displayed with an icon showing its status. Available Statuses/icons aretime you send a Secure Message you can see a status icon appear on its side. Here follows an explanation of each icon along with its status name and meaning:
| Icon | Description | Meaning | Timeouts and general behaviour |
|---|---|---|---|
Sending Message | PrivateGSM is actually trying to send the Secure Message to its recipient via PrivateServer | If there is some network issue, then PrivateGSM starts the retry procedure: it tries to send 5 times the message to PrivateServer. If it fails at the fifth try (5 * TLSTimeout = 60 secs), then the message remains in the client queue waiting for one of the following triggers:
If more than 12 hours passed and the message is still in client queue waiting to be sent, then the message expires: a "Send error" notification is fired by PrivateGSM and the message is removed from sender queue
| |
 | Message Enqueued | PrivateGSM was able to send the Secure Message which now is in the queue of PrivateServer encrypted. PrivateServer tries to deliver it to its destination. | If delivery is not possible because the peer if offline, PrivateServer retries 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. 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 recipient. The message could be read as not. | None | |
| Error sending Message | This status is a fall back for any other one and it's triggered both by timeouts and error responses. | None |
Receive
...
a Secure Message
Obviously a Secure Message can be received as it can be sent. In this case a specific notification is raised by PrivateGSM.
iPhone locked | PrivateGSM in background | Once you open the application |
|---|---|---|
new Secure Message notification is shown | PrivateGSM shows an event notification on its icon | "Recent" icon shows how many events occurred. Clicking on "Recent" shows "History" list with event item in bold. |
 |  |  |
| BlackBerry locked | Click on system's notification area | Click on PrivateGSM item |
|---|---|---|
Sound and vibration notify a new event. Once unlocked "new message" icon is shown in notification area | Event list is dropped down. PrivateGSM has its item as well (bottom line). | You got redirected directly to "History" view where the proper item is in bold. |
 |  |  |
As shown above each platform shows the event notification differently, according to the underlying operating system behaviour.
Features and limits (no chat group, no chat rooms, sì a emoji->indica come attivarlo su iphone e android, status della consegna del messaggio, tempi di validità del messaggio, no attach, no autosplit, max lenght = 160 chars)
...