has anyone ever seen reorder app causing inbound call failures (we had to disable it to get calls to work)

 i can force this issue by doing.    sup callflow maintenance flush ...

What does option "use_federated_listener" do?

Out of morbid curiosity is kazoo 5.x actually going to be delivered this year? It was "promised" last year.

Ysean: i ask this weekly

and have asked that we set a firm open-sourcing date despite app exchange status

to no avail, biz heads require appex be ready

That thing still isn't done? I thought I saw it on the corp website. At least an index of apps. it was mostly 2600hz, though,

i believe they're still working on service plans, how to enforce any limitations the app developer may want on the cluster operator

aaaaah

like if you have to pay per VM the app runs on, making sure it only runs on the X VMs you paid for

stuff like that

Yup, gotcha.

I suppose that comes down to creating a system for a few specific limitation factors and telling partners / prospects "this is what you have... adjust pricing accordingly.:

basically

but i continue to agitate for open sourcing regardless of appex status

one day i think i'll have annoyed them so much they'll give in

ahahaha

using my kids as inspiration

Are there no partners that are pushing for progress?

I would think they'd be interested in an extra revenue stream.

And, of course, 2600hz taking a cut.

there are, i don't have insight into the conversations though

Thanks mc_ for continuing to push for us. :) I hate to act "entitled" as I know we wouldn't have what we do now if it wasn't for the generosity/openness of 2600Hz to begin with, and I understand the reasoning behind why some parts of Kazoo are closed source (like Callcenter), and others I don't understand (Konami Pro and KazooDB lol) but hopefully they will continue (or rather get back on track) on a

primarily open source model.

But anyway your consistency and support of keeping Kazoo OSS is much appreciated by myself and I'm sure many others.