[ previous ] [ next ] [ threads ]
 To :  jeroen <jeroen@h...>, Yate List <yate@v...>
 From :  =?ISO-8859-2?Q?Maciek_Kami=F1ski?= <maciejka@t...>
 Subject :  Re: [yate] project architecture question
 Date :  Tue, 22 Mar 2011 13:20:07 +0100
Hi Jeroen,

Yate/YAYPM combo should serve you well. In fact I have developed sort
of conference server myself. You can read short report in Yate User
Opinions page: http://yate.null.ro/pmwiki/index.php?n=Main.UsersOpinions.
It was 1500 lines of python because it included "realtime" web ui for
conference. For a basic prototype it should be much less.

YAYPM has not changed much since 2008 because it is a very thin layer
above Yate extmodule protocol and there were no changes in the
protocol since than.

Disclaimer: I am the original YAYPM developer.


2011/3/21 jeroen :
> Hi list,
> I'm working on a proof-of-concept project for managing conference calls.
> Django is used as backend where users can setup conferences. Normally
> only one user will speak, others can connect to listen.
> Maybe later an iphone/android 'app' will be developed for selectingat
> conferences, for now a web frontend with sip URI's will do.
> I'm looking into Yate as the SIP frontend and particularly drawn to Yate
> because of YAYPM. Although I never worked with twisted/deferred I hope
> to be able to quickly get into a working concept and I like to use
> python.
> Users will be authenticated/registered with Django so I need Yate/YAYPM
> to catch and handle auth messages and setup the conference calls. I
> noticed there's very little documentation (I mean examples to work with)
> to get started and very little has changed since 2008.
> Do you think using Yate/YAYPM is the right choice ? Please share you
> thoughts and ideas to get me started.
> thanks,
> Jeroen