On Thursday, April 28, 2016 04:06:50 PM James wrote:
> Michael Mol <mikemol <at> gmail.com> writes:
> > Bah. So you guys aren't going to let me get away with trash-talking
> > without
> > some accountability of details. OK. I'll let you know when I've written up
> > something; I've already emailed one person a handful of my complaints in
> > bullet form. But that'd need to get more properly fleshed out before I
> > drop it somewhere more archival in nature.
> 
> Like I said, it's GOOD to have you back, brah.....

Hey, the major reason for my absence was / is *time*. So the more time 
investment I have to make, the less likely I am to speak up in the first place. 
;)

> 
> > I use freeswitch here all the time as my home pbx and it does things
> > asterisk either cannot do, or only with great difficulty.  I can even
> > put c# code in it using mono and a lot of times the xml is insufficient
> > and this is where this comes in handy.  There is a mailing list, so you
> > can ask questions as well.  Its one strength and also weakness is there
> > are a lot of variables, some of which are poorly documented, and some
> > not documented at all.
> 
> Perhaps we need some code help, to join our team. Sinced MM has deep
> experience with shrot comings and other like what works form them, do
> we have a quorum?

To be clear, 80% of my grievances with FreeSwitch have to do with the nature 
of their configuration and documentation. 9% had to do with a weird issue 
wherin we wound up rebooting the VM containing FS on a schedule; none of my 
instrumentation made it obvious what the nature of the leak was, but somehow 
rebooting the VM would resolve the issue. The remaining 1% was the difficulty in 
setting the thing up for anything but their preferred platform.


-- 
:wq