From 427f17fd9dce64952e9a906d6788ef836d9e4587 Mon Sep 17 00:00:00 2001 From: Mark Michelson Date: Tue, 8 Jan 2008 21:18:32 +0000 Subject: Adding the option of specifying a second interface in a member definition for a queue. app_queue will monitor this second device's state for the member, even though it actually calls the first interface. This ability has been added for statically defined queue members, realtime queue members, and dynamic queue members added through the CLI, dialplan, or manager. (closes issue #11603, reported by acidv) git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@97203 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- configs/queues.conf.sample | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'configs') diff --git a/configs/queues.conf.sample b/configs/queues.conf.sample index 7fe148639..92c323773 100644 --- a/configs/queues.conf.sample +++ b/configs/queues.conf.sample @@ -375,7 +375,10 @@ shared_lastcall=no ; entries with higher penalties are considered last. An optional member ; name may also be specified after a second comma, which is used in log ; messages as a "friendly name". Multiple interfaces may share a single -; member name. +; member name. An optional state interface may be specified after a third +; comma. This interface will be the one for which app_queue receives device +; state notifications, even though the first interface specified is the one +; that is actually called. ; ; It is important to ensure that channel drivers used for members are loaded ; before app_queue.so itself or they may be marked invalid until reload. This @@ -386,6 +389,7 @@ shared_lastcall=no ;member => Zap/3,10,Bob Johnson ;member => Agent/1001 ;member => Agent/1002 +;member => Local/1000@default,0,John Smith,SIP/1000 ; ; Note that using agent groups is probably not what you want. Strategies do -- cgit v1.2.3