From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: freeSwitch
Date: Thu, 28 Apr 2016 12:38:12 -0400 [thread overview]
Message-ID: <2457244.Hi0vOJHnAI@serenity> (raw)
In-Reply-To: <loom.20160428T175433-356@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1822 bytes --]
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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-04-28 16:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 3:21 [gentoo-user] freeSwitch James
2016-04-27 5:53 ` covici
2016-04-27 13:51 ` [gentoo-user] freeSwitch James
2016-04-27 13:59 ` covici
2016-04-27 14:12 ` James
2016-04-27 15:12 ` Meik Frischke
2016-04-27 14:21 ` [gentoo-user] freeSwitch Michael Mol
2016-04-27 22:17 ` Stroller
2016-04-27 22:48 ` Max R.D. Parmer
2016-04-28 4:26 ` J. Roeleveld
2016-04-28 5:17 ` covici
2016-04-28 12:54 ` Michael Mol
2016-04-28 16:06 ` [gentoo-user] freeSwitch James
2016-04-28 16:38 ` Michael Mol [this message]
2016-04-28 19:24 ` Neil Bothwick
2016-04-28 19:32 ` Michael Mol
2016-04-28 19:37 ` Neil Bothwick
2016-04-29 11:26 ` Michael Mol
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2457244.Hi0vOJHnAI@serenity \
--to=mikemol@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox