What is a "Secure Message"?
A secure message is a text message that can be sent and received by using PrivateGSM. Secure Message uses the same communication infrastructure of the Secure Voice communication to exchange data:
- Server Authentication by SSL certificate
- HTTPS and SIP over TLS protocols to exchange data
It's possible to send just text messages, but as PrivateGSM supports UNICODE and emoji character set, you can add emoticon icons as well.
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.
How does a Secure Message work?
When a customer chooses to send a Secure Message, it triggers an HTTP POST request in his client towards PrivateServer which plays a "store-and-forward" role. As soon as the receiver pops up online, PrivateServer delivers the Secure Message.
At current state of development, message encryption is granted on the server for the storing period by an internal key. Future development will implement asymmetric key encryption side-to-side (PGP like, actually).
Delivery is performed by SIP over TLS protocol, so as you can see the whole end-to-end path is encrypted and as the message is stored after a local encryption on the server, then there's (almost) no way of deciphering it.
Send a Secure Message
It's possible to write Secure Messages to other parties both by answering them or by writing for your own initiative. In the first case you would probably use the "History" view, in the latter you would use the "Contacts" list instead.
Since the "History" lists all the communication attempted or happened on your PrivateGSM, it's possible to start a conversation using "History" as well, eg: answering to a missed call by a Secure Message or just using one event conveniently.
Sending Secure Messages from "History" view
Each platform let you reach the "History" list by different names:
| Platform | "History" icon |
|---|---|
| Android |  |
| BlackBerry |  |
| iPhone |  |
As you can see in figure 1. type a new Secure Message: you can type Secure Messages and send them to your party by pressing enter button (cfr. figure 2. "enter" keyboard button).
Sending Secure Messages from "Contacts"
Secure Messages are also available from "Contacts" view.
You have to select an account from the list shown in $text.replaceAll("]*>"," ").replaceAll("\s*\z","") and show its details by clicking on the blue icon displayed on its right side. Then you get a view like in figure 3. contacts list tab.
Once you select the desired phone number of the account you want to send Secure Messages to, then you get the view shown in figure 1. type a new Secure Message from where you can type your message.
Secure Messages status icons and known limitations
Each Secure Message is displayed with an icon showing its status. Available Statuses/icons are:
| 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 | |
 | 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. |
Receive a secure message
sdgsdg
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)
sdfds
To use Emoji set it's mandatory to enable it on your device. This is an Operating System option thus please refer to your device manual.
You can also communicate by text messages using the Private Message System (henceforth PMS). PMS provides Private Text Message (henceforth PTM) which does relay on the very same security infrastructure the voice calls do.