As it is done today, the wrap-up time is not terribly useful in Asterisk, as it is fixed-length. If you need to implement it in a real-life scenario, it would be better to pause the agent when the call is through and have him unpause manually when he's done the wrap-up; this way you get a measurable metric as well.
Just my two eurocents, l. 2009/12/18 Magnus Benngård <magnu...@inputinterior.se> > Hi! > > Trying to understand how wrapuptime is working... > I have written a small php script that let agents log in/out > off a queue. That part is working as a clock but wrapuptime > is not doing what I expect. > > Input Interiör - Queue Manager > > 0317998989 has 0 calls (max unlimited) in 'rrmemory' strategy > (5s holdtime, 94s talktime), W:0, C:8, A:1, SL:0.0% within 0s > Members: > SIP/0317998971 with penalty 2 (dynamic) (Not in use) has taken no > calls yet > SIP/0317998975 with penalty 2 (dynamic) (Not in use) has taken no > calls yet > SIP/0317998972 with penalty 1 (dynamic) (Not in use) has taken 8 > calls (last was 2 secs ago) > No Callers > > SIP/0317998972 did hang up 8 seconds ago, but if someone calls the queue > at this moment, the call will start ringing on SIP/0317998972 again. > I thought the wrapuptime should cause the call to go to one of the other > agents. Did I miss anything in the configs or is it that we have different > penalties or...? > -- Loway - home of QueueMetrics - http://queuemetrics.com
_______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users