Atis Lezdins a écrit : > You could enable "core set verbose 3" and "core set debug 1", and then > post corresponding log when you see this happens. > Ok so, what you are saying is that this shouldn't happens ? (in normal conditions the queue should be a fifo)
Anyway, i had the idea this was caused by the login of a new member that other calls hadn't have time to 'register' or sometime like that, and the new call has already taken the full list in action. So i've investigated the *real* need behind this, and reprogrammed the queue and fixed the penalty system to allow for a multi-level agent system, which answer the need better than connecting/disconnecting at needs. However if this still happen i'll try the debug, but the core is already at verbose 3 and it's a pain in the arse to follow and even work with the console ... By the way do someone know a way using AEL/conf to obtain the queue(s) an agent is a member of ? i can't seem to find a way to 'browse' the astdb key "/Queue/PersistentMembers/*" nor is there a key referencing every queues actives ... _______________________________________________ -- 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
