PrivateGSM: Blackberry/iPhone/Nokia mobile voice encryption with ZRTP or SRTP/SDES

I absolutely avoid to use my own personal blog to make promotion of any kind of product.

That time it’s not different, but i want to tell you facts about products i work on without fancy marketing, but staying technical.

Today, at PrivateWave where i am CTO and co-founder, we released publicly mobile VoIP encryption products for Blackberry, iPhone and Nokia:

  • The 1st ever Blackberry encrypted VoIP with ZRTP - PrivateGSM VoIP Professional
  • The 1st ever iPhone encrypted VoIP with ZRTP - PrivateGSM VoIP Professional
  • The 1st ever Blackberry encrypted VoIP client with SRTP with SDES key exchange over SIP/TLS - PrivateGSM VoIP Enterprise


At PrivateWave we use a different approach respect to most voice encryption company out there, read our approach to security .

The relevance of this products in the technology and industry landscape can be summarized as follow:

  • It’s the first voice encryption company using only standards security protocols (and we expect the market will react, as it’s clear that proprietary tech coming from the heritage of CSD cannot provide same value)
  • It’s the first approach in voice encryption to use only open source & standard encryption engine
  • It’s the first voice encryption approach to provide different security model using different technologies (end-to-end for ZRTP and end-to-site for SRTP)

Those suite of Mobile Secure Clients, designed for professional security use only using best telecommunication and security technologies, provide a high degree of protection along with good performance also in bad network conditions:

The applications are:


The supported mobile devices are:

Regarding ZRTP we decided to stress and stretch all the security and paranoid feature of the protocol with some little addition:

Our strict address book integration, goes beyond ZRTP RFC specification, that could be vulnerable to certain attacks when used on mobile phones because of user behavior of not to look at mobile screen.

Our paranoy way of using ZRTP mitigate such conditions, we will write about this later and/or will add specific details for RFC inclusion.

Some words on PrivateGSM Professional with end-to-end encryption with ZRTP

Read technical sheet there!

To download it click here and just put your phone number

Those are the results of hard work of all my very skilled staff (16 persons worked on this 6 projects for 3 different platforms) on challenging technologies (voice encryption) in a difficult operating environment (dirty mobile networks and dirty mobile operating systems) for more than 2 years.

I am very proud of our staff!

What next?

In next weeks you will see releasing of major set of documentations such as integration with asterisks, freeswitch and other Security Enabled PBX, along with some exciting other security technology news that i am sure will be noticed ;)

It has been an hard work and more have to be done but i am confident that the security and opensource community will like such products and our transparent approach also with open important releases and open source integration that make a very politically neutral (backdoor free) technology.


  • 1
    20 January 2011 - 10:00 am | Permalink

    You should add your client to the list at

    Unfortunately, 800 EUR per year is too expensive for private use…

  • 2
    30 September 2011 - 12:43 pm | Permalink

    Could you please extend your sentence “Receiver is FREE that means that only who make calls have to buy the application, receiver does not need to pay anything”.

    Are you proposing end users a free passive zrtp engine for key exchange for incoming calls on media line. Otherwise how zrtp protocol make handshake for dhparts, commit vs. with other end?

  • Leave a Reply

    Your email address will not be published. Required fields are marked *