+1 Overflow should not be a requirement for maxWaitTime and/or maxQueueDepth.
- MM On Wed, May 9, 2012 at 7:35 AM, Domenico Chierico < [email protected]> wrote: > that's great... I'm ready to contribute but I need to discuss if all > community is agree with my ideas > > > On Wed, May 9, 2012 at 12:25 PM, Michael Picher <[email protected]> wrote: > > eZuce isn't putting any dev effort into the existing acd platform. > > > > Contributions are of course welcome. > > > > Mike > > > > On May 9, 2012 4:17 AM, "Domenico Chierico" < > [email protected]> > > wrote: > >> > >> Working on old style ACD I've found some some strange behaviours for > >> which I'm trying to get a fix. > >> I'm not sure if all are interested into ACD improvement so I'm > >> reporting it just to know what to do. > >> > >> at first some odds on configuration: > >> > >> if I haven't set any Overflow strategies the maxWaitTime counter is > >> forced to 0, I feel that this is an unnecessary constraint, so i > >> removed this and lets the calls into queue get a "call termination" > >> stuff. > >> > >> quite the same is for the maxQueueDepth strategies that works just if > >> some overflow strategie is set. > >> > >> Then I've some other little improvements that I can discuss with you > >> later. > >> > >> > >> Domenico Chierico > >> _______________________________________________ > >> sipx-dev mailing list > >> [email protected] > >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > > > > _______________________________________________ > > sipx-dev mailing list > > [email protected] > > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
