[VOIPSEC] ZRTP and Asterisk

Alejandro Cabrera Obed acabrera at sintys.gov.ar
Wed Aug 6 19:12:07 BST 2008


Thanks Werner,

I used Wireshark in order to trace ZRTP packets, but I don't remember
what I see. I'll do it again.

Phill Zimmerman told me to use tha ZRTP patch in Asterisk, and he was
surprised when I tell my experience among Twinkle+libzrtp.

Just one more question: which scenario do you use Twinkle+ZRTP in ???
Maybe direct connections or through a SIP server like Openser ???

Thanks a lot !!!

Alejandro

Dittmann, Werner (NSN - DE/Munich) wrote:
>
> Hello Alejandro,
>
> just got a link to your question on the VOIPSEC list
> regarding this topic. I'm quite familiar with the
> GNU ZRTP / Twinkle implementation of ZRTP, however
> I'm not familiar with Asterisk.
>
> Here just some ideas why it could work with Twinkle:
>
> Twinkle is quite flexible with respect to audio codecs,
> it supports a lot of them.
>
> Now, if the Twinkle clients agree on a codec and Asterisk
> does not need to re-encode the RTP packets and just transport
> them unaltered between the clients then ZRTP will obviously work.
>
> Depending on the Twinkle and Zfone versions a connection between
> Twinke and Zfone is possible or not  :-) - computers are digital
> devices ;-) .
>
> (Just checked the Twinkle Web site: Michel de Boer did not
> yet update to the latest version of ZRTP. I use a newer/modified
> version here in my sandbox.)
>
> To analyse this further I would need a protocol trace (Wireshark)
> to analyse the traffic. My first guess: something is wrong
> with the Asterisk configuration and twinkele is able (somehow)
> to perform direkt client-to-client connections.
>
>
> Best regards,
> Werner
>


-- 
Ing. Alejandro Cabrera Obed
Interconexion
SINTyS
Sistema de Identificacion Nacional Tributario y Social
Consejo Nacional de Coordinacion de Politicas Sociales
Presidencia de la Nacion
Julio A. Roca 782 - Piso 5
Ciudad Autonoma de Bs. As.
Tel: (54 11) 4343-0181/89 interno 5172
4334-3676 4342-5648
acabrera at sintys.gov.ar

NOTA DE RESPONSABILIDAD:
----------------------------------------------------------------------
Este mensaje proviene de Internet,tome los recaudos necesarios en su
manejo.
El contenido del presente mensaje y sus adjuntos es privado,
estrictamente confidencial y exclusivo para su destinatario, pudiendo
contener información protegida por normas legales y de secreto
profesional.
Bajo ninguna circunstancia su contenido puede ser transmitido o revelado a
terceros ni divulgado en forma alguna. En consecuencia de haberlo recibido
solicitamos contactar al remitente y eliminarlo de su sistema.
-------------------------------------------------------------------------- 





More information about the Voipsec mailing list