linphone-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] Linphone new sip stack


From: Paulo Vicentini
Subject: Re: [Linphone-developers] Linphone new sip stack
Date: Fri, 2 Aug 2013 18:57:05 -0300

to compile on my win7...added AI_V4MAPPED  


On Wed, Jul 31, 2013 at 4:50 PM, Jehan Monnier <address@hidden> wrote:
Hi,

Yes,  instead, you can get belle-sip from git://git.linphone.org/belle-sip

Cheers


Le 31 juil. 2013 à 20:46, Paulo Vicentini <address@hidden> a écrit :

So, linphone no longer depends on libeXosip2 ?




On Mon, Jul 29, 2013 at 6:54 PM, Jehan Monnier <address@hidden> wrote:
Dear list,

We just push a new version of Linphone with major improvements in the signaling component of Linphone. The main change is the integration of belle-sip, a brand new sip stack developed by the Linphone's team. 

Bellow the list of main new features.
        * multiple SIP transports simualtaneously 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 lightweighted polarssl library (instead of openssl)
        * SIP transaction state machines improved (RFC6026)
        * Privacy API
        * Full support of rich presence

Best regards



_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers


_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers


_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers


Attachment: pv_getaddrinfo_FLAGS.txt
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]