[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Linphone-developers] Port to libeXosip v4
From: |
Guillaume Beraudo |
Subject: |
Re: [Linphone-developers] Port to libeXosip v4 |
Date: |
Tue, 29 Apr 2014 13:51:03 +0200 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
Hi Eli,
An extract from out official communication of this month:
ZRTP now available on Linphone under proprietary license
Belledonne Communications has developed its own implementation of ZRTP
called "b-zrtp". In addition to the GPL license and unlike the previous
zrtp implementation, b-zrtp is also now available under proprietary
license and does not have any dependencies on OpenSSL. This
new ZRTP implementation uses the cryptography functions of polarSSL
which was already integrated in Linphone.
Guillaume
On Wed, Apr 09, 2014 at 02:50:03PM -0400, Eli Burke wrote:
> Guillaume,
>
> Could we get a similar statement about the reason you guys created your own
> ZRTP implementation (“bzrtp”)?
>
> Has it been tested for interoperability with ZRTP implementations used by
> other VOIP products?
>
> Thanks,
> Eli
>
> On Apr 9, 2014, at 12:01 PM, address@hidden wrote:
>
> > Message: 1
> > Date: Wed, 9 Apr 2014 10:04:24 +0200
> > From: Guillaume Beraudo <address@hidden>
> > To: address@hidden
> > Subject: Re: [Linphone-developers] Port to libeXosip v4
> > Message-ID: <address@hidden>
> > Content-Type: text/plain; charset=iso-8859-1
> >
> > Hi Leonard,
> >
> > There have been anouncements on the list.
> > For example on January 8th Margaux stated:
> >
> > +Liblinphone level improvements thanks to new "belle-sip" SIP stack:
> > * multiple SIP transports simultaneously now allowed
> > * IP dual stack: can use IPv6 and IPv4 simultaneously
> > * fully asynchronous behavior: no more lengthly DNS or connections
> > * sip.instance parameter (RFC5626)
> > * alias parameter (RFC5923)
> > * better management of network disconnections
> > * SIP/TLS handled through lightweight polarssl library (instead of
> > * openssl)
> > * SIP transaction state machines improved (RFC6026)
> > * Privacy API (RFC3323, RFC3325)
> > * Full support of rich presence in (RFC4480)
> > * Better handling of sips scheme in URIs.
> >
> >
> > Guillaume Beraudo
>
> _______________________________________________
> Linphone-developers mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/linphone-developers