On Sep 19, 2006, at 6:32 PM, Kevin P. Fleming wrote:
----- Nicolás Gudiño <[EMAIL PROTECTED]> wrote:
2) In order to track correctly the events in queue_log, you should use
"/n" for Local channels. If not, you will get some events with Local
and others with the real device name.
To bring this to some closure, we are going to make a change to
app_queue to support a 'logical name' for all queue members, static or
dynamic, which will be used in manager events and queue_log entries if
supplied. This will even allow the queue_log to stay consistent when
the mapping for a member changes from one channel name to another.
Great, how about tracking state of Local/ members on the queue? Is that
possible? I have not looked at the code myself, haven't found the
time.. but I believe this is the greatest shortcoming when using
dynamic members using Local channels. If this could be fixed, then
Agentcallbacklogin won't be missed, at least by myself.
--
Nicolas Gudino
Buenos Aires - Argentina
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
