Summary:ASTERISK-04600: agent making outgoing call after logging in using agentcallbacklogin is reported as unavailable instead of busy
Reporter:Jon Gabrielson (gabriels)Labels:
Date Opened:2005-07-15 09:43:51Date Closed:2011-06-07 14:10:19
Versions:Frequency of
Description:If an agent answers an incoming call and then
gets a second caller trying to dial their
direct extension, the agent is correctly
reported as busy, but if an agent logs in using
agentcallbacklogin and then makes an outgoing
call, when someone calls their extension, they
are reported as unavailable when they should be
reported as busy.
Comments:By: Michael Jerris (mikej) 2005-07-15 09:50:39

Can you create a patch to correct this issue?

By: Olle Johansson (oej) 2005-07-27 12:12:52

...waiting for an answer..

By: Jon Gabrielson (gabriels) 2005-07-27 14:04:22

I've looked at the code, and can't seem to find
where the problem is originating from.  It could
well be a an easy fix, but I'm not familiar
enough with the code to know.

By: Kevin P. Fleming (kpfleming) 2005-08-26 19:33:43

We will need a complete call trace with verbose and debug turned on to be able to see what is happening here; I've reviewed the chan_agent code and it appears to be doing the right thing, but I can't tell for sure without seeing a trace.

By: Michael Jerris (mikej) 2005-09-01 21:34:36

Suspended this bug due to no response.  Unfortunately we can not troubleshoot this issue further without the requested call trace.  Please re-open this bug if the issue persists when you have call traces ready to review.  Thanks!