Re: [asterisk-dev] Queue Gate Concept

2016-10-21 Thread Richard Mudgett
On Fri, Oct 21, 2016 at 6:09 PM, Troy Bowman wrote: > Where I work, we're running a call center on Asterisk, using app_queue. > > For a long while, we were using multiple queues for each speciality (or > "skill"), placing agents in several queues, and using the "announce" > queue.conf configurati

Re: [asterisk-dev] app_queue.c PAUSALL/UNPAUSEALL reason

2016-10-21 Thread Richard Mudgett
On Fri, Oct 21, 2016 at 5:46 PM, Troy Bowman wrote: > > I always need to apply this patch before putting Asterisk into Production. > > The pauses for specific queues get the reason logged properly, but the > pausealls don't. I rely on pausalls and their reasons for reporting, > though I'm trying

[asterisk-dev] Queue Gate Concept

2016-10-21 Thread Troy Bowman
Where I work, we're running a call center on Asterisk, using app_queue. For a long while, we were using multiple queues for each speciality (or "skill"), placing agents in several queues, and using the "announce" queue.conf configuration option to whisper to the agent the role they should perform

[asterisk-dev] app_queue.c PAUSALL/UNPAUSEALL reason

2016-10-21 Thread Troy Bowman
I always need to apply this patch before putting Asterisk into Production. The pauses for specific queues get the reason logged properly, but the pausealls don't. I rely on pausalls and their reasons for reporting, though I'm trying to get away from it by keeping agents in single queues. Can we

Re: [asterisk-dev] ARI StasisEnd event vs. channel variables

2016-10-21 Thread Corey Farrell
On Fri, Oct 21, 2016 at 12:32 PM, Kevin Harwell wrote: > On Fri, Oct 21, 2016 at 10:49 AM, Corey Farrell wrote: >> >> >> I'm in favor per app config. I do not yet use ARI, but when I do I >> will have '#tryinclude /etc/asterisk/ari.d/*.conf' in ari.conf. My >> hope is that each ARI app would in

Re: [asterisk-dev] ARI StasisEnd event vs. channel variables

2016-10-21 Thread Kevin Harwell
On Fri, Oct 21, 2016 at 10:49 AM, Corey Farrell wrote: > > I'm in favor per app config. I do not yet use ARI, but when I do I > will have '#tryinclude /etc/asterisk/ari.d/*.conf' in ari.conf. My > hope is that each ARI app would install it's own config to > /etc/asterisk/ari.d, avoid modificati

Re: [asterisk-dev] ARI StasisEnd event vs. channel variables

2016-10-21 Thread Corey Farrell
On Fri, Oct 21, 2016 at 9:37 AM, Sébastien Duthil wrote: > On 19/10/16 11:59 AM, Mark Michelson wrote: >> I had thought about making the list of channel variables per-ARI app >> instead of global, but I don't know if that's actually desired. > > The underlining question would be: do people use

Re: [asterisk-dev] ARI StasisEnd event vs. channel variables

2016-10-21 Thread Mark Michelson
I have opened https://issues.asterisk.org/jira/browse/ASTERISK-26492 and have attached the patch there. Feel free to try it out and let me know on the issue how it works for you. On Fri, Oct 21, 2016 at 8:37 AM, Sébastien Duthil wrote: > On 19/10/16 11:59 AM, Mark Michelson wrote: > > I actually

Re: [asterisk-dev] ARI StasisEnd event vs. channel variables

2016-10-21 Thread Sébastien Duthil
On 19/10/16 11:59 AM, Mark Michelson wrote: > I actually have a patch I've written locally in my spare time that > adds an ari.conf option called "channelvars" that works exactly the > same as for manager.conf. In other words, it modifies channel > snapshots to have the channel variables specified