QueueMetrics > Outbound and QueueMetrics
Quemeterics not recognising remote caller hangup
QueueMetrics:
Does thei happens whenever the agent hangs up, or only when the agent hangs up while not in conversation or while the agents hangs up while in conversation?
I am trying to replicate this behaviour on both * 1.2 and 1.4 we have here in the lab and I am not having success...
QueueMetrics:
If anybody is using * 1.4, try the following:
--- Quote ---A locally executed AGI script will receive SIGHUP on hangup from the channel except when using DeadAGI. This can be disabled by setting the AGISIGHUP channel variable to "no" before executing the AGI application.
--- End quote ---
And see if the application behaves correctly. If you're running 1.2, this cannot be done. I believe the cause of this problem is the script receiving HANGUPs.
kcmon:
I am not quite understanding what you mean "while in conversation" or "while not in conversation" It boils down to who hangs up first. If the agent hangs up first, the call is not terminated correctly in queuemetrics. If the customer hangs up first, the call is terminated correctly. Currently, we have been telling our agents to allow the customer to hang up so that the numbers look correct.
As to the script getting SIGHUP, I believe this may be the case. Since I am running Asterisk 1.2, I can't use the AGISIGHUP variable. What harm would occur if I ignore the SIGHUP in the AGI script itself. Will this work?
QueueMetrics:
I suggest you track the h extension and write a fake entry, though the actual talk time will be mistracked.
kcmon:
Thanks for the tip. I am now tracking the h extension and this issue seems to be fixed.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version