The official description of ZRTP is 'Media Path Key Agreement for Secure RTP'. It's a protocol to exchange and verify end-to-end encryption keys for voice communications.
ZRTP is being developed by Philip Zimmermann (Mr. PGP), Alan Johnston and Jon Callas as alternative to the various encryption signaling protocols with specifically the End-to-End argument in mind.
RTP: ZRTP carried in RTP version 0 packets.
XXX - Add example decoded traffic for this protocol here (as plain text or Wireshark screenshot).
The ZRTP dissector is fully functional. It supports the protocol versions 0.80, 0.85, 0.90, 0.95, 1.0 and 1.1.
Capture on Windows
(From the Zfone project website):
If you want to use Wireshark to capture Zfone encrypted VoIP traffic on the same machine that Zfone is running on, you cannot do it on Windows. This is because on Windows, the Zfone device driver is closer to the network adapter than the Wireshark device driver. This means Wireshark captures only unencrypted IP traffic. Zfone has already decrypted incoming packets before Wireshark can see them, and Zfone only encrypts outgoing packets after they have passed through Wireshark. This problem only exists on Windows.
If you need to capture encrypted packets from a Windows machine running Zfone, you must run Wireshark on a separate machine between the two parties.
The dissector has no preference settings. The RTP dissector has to set 'Treat RTP version 0 packets as' to 'Invalid or ZRTP'.
Example capture file
XXX - Add a simple example capture file to the SampleCaptures page and link from here (see below). Keep this file short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.
A complete list of ZRTP display filter fields can be found in the display filter reference
Show only the ZRTP based traffic:
You cannot directly filter ZRTP protocols while capturing. However, if you know the UDP port used (see above), you can filter on that one.