Clean-up, fixes, and enhancements to ZRTP

[Werner Dittmann]

Mikael,

both implementations are identical with regard of the ZRTP
state engine and methods. Only the "glue code" between
ZRTP implementation and "host" RTP stack (minisip's RTP / ccRTP)
is different.

And yes, I'm thinking about packing it into a shared lib. This
will be one of the next steps during development. I waited for
this because I liked to see if the ZRTP state engine is really
independent of the RTP stack - it is :-)

Regards,
Werner



Mikael Magnusson wrote:
> Werner Dittmann wrote:
>> All,
>>
>> checked in a better version of the ZRTP code. It contains fixes
>> to support Zfone Beta 2 (it is nearly "bug-compatible" :-)  ).
>>
>> Also some enhancements with respect to the GoClear facility of
>> ZRTP - not yet complete, but some code is already there.
>>
>> Cleanup of code.
>>
>> The same ZRTP implementation (the protocol engine) is now available
>> as part of the GNU ccRTP stack (not yet released, use CVS HEAD) and
>> is of course inter operable with minisip. Together with Michel de Boers
>> we tested this with the combination of GNU ccRTP and twinkle. Any client
>> that uses GNU ccRTP now can use ZRTP with just a few lines of code
>> change (about 10 lines of code change in twinkle to support basic ZRTP,
>> implementing the user interface in twinkle's GUI needed some more changes
>> of course).
>>
>> Regards,
>> Werner
> 
> Nice, have you considered releasing the ZRTP implementation as a
> separate package? I run a diff between the ZRTP implementation in
> minisip and GNU ccRTP, and found it's almost identical. I think it would
> nice with ZRTP as a shared library.
> 
> Mikael
> _______________________________________________
> Minisip-devel mailing list
> Minisip-devel at minisip.org
> http://lists.minisip.org/mailman/listinfo/minisip-devel
>