and we do support modules fully written in C++. I think the biggest
difference between FreeSWITCH and Yate are in its approach to using
other libraries and our licensing. One of the main design goals we
started with was to re-use as much already written code as possible.
The best example of this is that we use the sofia-sip library
heavily. This library was 5+ years of development before we ever used
it and is a massive piece of work. Yate has often taken the opposite
approach of writing nearly everything themselves. I don't think this
approach is sustainable for any project as you can not focus on
everything and make it really good. I spent several years watching
the problems the asterisk project ran into and by far the most
numerous were related to sip in some way. I don't think any project
that chooses the route of writing their own sip stack in the end will
be able to handle the maintenance requirements without a massive user
and developer base.
This just by itself is a great reason to start a new project. This is exactly the type of response I wanted. :)
> Personally since even now Freeswitch has a bigger community I'd
> probably only look at Yate to make sure I have a somewhat generic
> event model for Vicidial (somewhere on my to-do list).
Not sure what you mean here. FreeSWITCH has an event system, what do
you mean by generic?
Yes Freeswitch does. Vicidial doesn't -- yet. Vicidial's event model (if you want to call it that...) needs a bit of work to straighten things out. I was just saying that looking the events generated by Asterisk, Freeswitch and Yate that overlap would make the Vicidial event system pretty generic.
> This message is by no means meant to be taken as an attack on
> Freeswitch. I'm just curious.
No offense taken. :D