Hi, Shayan
At the time when conf support was developped thetre was BIIG time
constraint on the developpement time.
So iinstead of writing fullblown N-Way conf support i hackded much more
simpler 2 way support
Another issue was that at the time doing 2 sessions witn Audio/Video +
echo cancellation pushed common CPUs to their limit.
Thanks
Vadim
On 28/06/11 16:11, Shayan Eftekhari wrote:
Hi,
Thanks a lot for your response.
Do you know why PhApi is limited to just a 3-way conference?
QuteCom use Verona based on osip/exosip
Take a look at http://hg.qutecom.org/verona
Envoyé de mon iPhone
Le 27 juin 2011 à 10:23, Dave Neary <dne...@free.fr
<mailto:dne...@free.fr>> a écrit :
> Hi,
>
> Shayan Eftekhari wrote:
>> It seams that QuteCom uses libpurple for its non-SIP protocol support.
>
> Yup.
>
>> But when I searched about QuteCom's SIP stack, I found nothing except a
>> class named "SipWrapper" which seams to belong to a dedicated
library of
>> QuteCom and implements some SIP functionalities. My question is: "Does
>> QuteCom use SipWrapper to overcome all of its SIP stuffs and where
can I
>> find its features to compare it with other SIP stack libraries like
Opal".
>> //Thanks for any help in advance
>
> QuteCom still uses osip for SIP stuffs. It should be possible to swap
> out osip/exosip and use Sofia or Opal instead, but it would be quite a
> lot of work.
>
> Cheers,
> Dave.
>
> --
> Dave Neary
> dne...@free.fr <mailto:dne...@free.fr>
> Tel: +33 9 51 13 46 45
> Cell: +33 6 77 01 92 13
> _______________________________________________
> QuteCom-dev mailing list
> QuteCom-dev@lists.qutecom.org <mailto:QuteCom-dev@lists.qutecom.org>
> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
_______________________________________________
QuteCom-dev mailing list
QuteCom-dev@lists.qutecom.org
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
_______________________________________________
QuteCom-dev mailing list
QuteCom-dev@lists.qutecom.org
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
