EXPERIMENTAL: replace the queueDial.agi with a pure-scripting solution

[goit]

Thank you for the reply. 

My concern is for the "Dial" command. As you can see (Macro(ael-druid-trunkdial), DRUID executes an AEL script to do the dialing. It does not use asterisk "dial" command direclty. the AEL script is the one that executes the "Dial" command. I don't think what you suggested will work, but i will give it a try.

[QueueMetrics]

Well there is no reason to be concerned - I'm not sure what the macro does, but surely is not needed by the underlying Asterisk architecture, as long as the trunk name makes sense. 

[qmax]

the Dial application sets channel variables
DIALEDTIME and ANSWEREDTIME

what is the reason of using EPOCH and having global variables ?
Upd. what i mean is:

Why:

Code: [Select]

exten => h,n(case-A),Set(WT=$[${GLOBAL(${GM}ans)} - ${ST}])
exten => h,n,Set(CT=$[${EPOCH} - ${GLOBAL(${GM}ans)}])
exten => h,n,QueueLog(${QUEUEID},${UNIQUEID},Agent/${AGENTID},COMPLETEAGENT,${WT},${CT})
is preffered over:

Code: [Select]

exten => h,n(case-A),QueueLog(${QUEUEID},${UNIQUEID},Agent/${AGENTID},COMPLETEAGENT,$[${DIALEDTIME} - ${ANSWEREDTIME}],${ANSWEREDTIME})
w/out using any global variables
here, DIALEDTIME and ANSWEREDTIME are channel variables set by Dial application

[qmax]

another question...
when call is answered, Dial sets DIALSTASUS to "ANSWER"

what is the reason of using GLOBAL(${GM}) ?

is it possible, that macro set by M option is not called, while dialstatus is still set to ANSWER ?
asterisk documentation it is not quote clean for me.

[QueueMetrics]

You would better do a trace ands see steèp-by-step what it does.