1
Outbound and QueueMetrics / Re: Quemeterics not recognising remote caller hangup
« on: May 10, 2007, 10:11:49 »
Hi
I did a workaround to resolve the problem when the remote caller hangs up first. Firstly, it seems that most of the times if the remote side hangs up first, Asterisk does no send the AGI variable back to the queueDial script and then it does not terminate properly and the call just seems to go on and on.
So I put the following line into my hang-up-call macro:
exten => s,n,System( echo "${EPOCH}|${UNIQUEID}|${QUEUENAME}|${AGENT}|COMPLETECALLER|0|${ANSWEREDTIME}" >> /var/log/asterisk/queue_log )
this line then records, into queue_log, that the call is terminated properly and queuemetrics no longer displays a call as continuing indefinitely.
I put in 'COMPLETECALLER' as I know that I only get the error when remote hangsup first and '0' as we are not interested how long the remote party took to answer the phone.
Thanks once more for a great product
Angelo
I did a workaround to resolve the problem when the remote caller hangs up first. Firstly, it seems that most of the times if the remote side hangs up first, Asterisk does no send the AGI variable back to the queueDial script and then it does not terminate properly and the call just seems to go on and on.
So I put the following line into my hang-up-call macro:
exten => s,n,System( echo "${EPOCH}|${UNIQUEID}|${QUEUENAME}|${AGENT}|COMPLETECALLER|0|${ANSWEREDTIME}" >> /var/log/asterisk/queue_log )
this line then records, into queue_log, that the call is terminated properly and queuemetrics no longer displays a call as continuing indefinitely.
I put in 'COMPLETECALLER' as I know that I only get the error when remote hangsup first and '0' as we are not interested how long the remote party took to answer the phone.
Thanks once more for a great product
Angelo