[asterisk-users] What is the purpose of membermacro in queues.conf

[Mark Michelson]

Rajkumar S wrote:
> Hi,
> 
> There are 3 new settings (setinterfacevar, setqueueentryvar,
> setqueuevar)  and  membermacro settings in 1.6 queues.conf. What is
> the potential use of these settings? The variables set are useful, but
> there is no indication of the purpose they could be used? Any one with
> some light on potential use case of these new features?
> 
> raj
> 

I'd be glad to explain them.

First of all, setinterfacevar was actually around in 1.4, but its use has been 
expanded in 1.6.0. In 1.4, this would cause the MEMBERINTERFACE channel variable 
to be set. In 1.6.0, this setting also sets the MEMBERNAME, MEMBERCALLS, 
MEMBERLASTCALL, MEMBERPENALTY, MEMBERDYNAMIC, and MEMBERREALTIME variables. The 
purpose of exposing these values is to allow for an administrator to use these 
for any purpose he may desire.

Second, there's setqueuevar. Its purpose is similar to setinterfacevar, in that 
it exposes values to the dialplan so that an administrator can use them how he 
wishes. The variables set are QUEUENAME, QUEUEMAX, QUEUESTRATEGY, QUEUECALLS, 
QUEUEHOLDTIME, QUEUECOMPLETED, QUEUEABANDONED, QUEUESRVLEVEL, and QUEUESRVLEVELPERF.

Finally, you asked about membermacro. This allows for a macro to execute on a 
queue member's channel when he answers the call. This is very similar to the 'M' 
option for the dial application. Some people use this sort of feature as a 
"post-answer hook" into the dialplan so that they can perhaps log statistical 
information, or present the queue member with information about the incoming call.

Mark Michelson
> _______________________________________________
> -- 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