Summary:	ASTERISK-00160: AgentCallBackLogin is logged in but doesn't answer is never retried
Reporter:	Adam Goryachev (adamg)	Labels:
Date Opened:	2003-08-25 04:24:25	Date Closed:	2011-06-07 14:05:05
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_queue
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	When I login using AgentCallBackLogin to a queue, and this agent is the only member of the queue (at the moment) and a call is added to the queue, the agent is called, and if they don't answer, they are never tried again... ****** ADDITIONAL INFORMATION ******    -- Executing Queue("Zap/2-1", "queue|t") in new stack    -- Started music on hold, class 'default', on Zap/2-1    -- outgoing agentcall, to agent '1001', on 'Local/1001@dispatchlogin-34e1,1'    -- Called 1001    -- Executing Dial("Local/1001@dispatchlogin-34e1,2", "Modem/g1:90402078431") in new stack    -- Called g1:90402078431    -- Nobody picked up in 15000 ms    -- Hungup 'Modem[i4l]/ttyI1'  == Spawn extension (dispatchlogin, 1001, 1) exited non-zero on 'Local/1001@dispatchlogin-34e1,2' [Some minutes later]...    -- Stopped music on hold on Zap/2-1    -- User disconnected when they almost made it  == Spawn extension (remote, s, 7) exited non-zero on 'Zap/2-1'    -- Hungup 'Zap/2-1' agents.conf: [agents] autologoff=10 agent => 1001,1234,Adam Goryachev agent => 1002,1234,Sarah Gwilliam agent => 1003,1234,Doris Mitchell queues.conf [general] [queue] music = default strategy = ringall timeout = 15 retry = 5 maxlen = 0 member => Agent/1001,2
Comments:	By: Mark Spencer (markster) 2003-08-25 08:47:51 I'll need some debug to go along with this... Be sure debugging is enabled to console in /etc/asterisk/logger.conf Look for messages along the lines of: (Parallel Trying 'Agent/1001' with metric 2000000 Also, show the results of "show agents" both before and after the non-answered call. By: tclark (tclark) 2003-08-25 19:53:32 err Hem... This looks like a config error the timeout on the q is 15 seconds (timeout = 15 )and the autologout for the agent is 10 seconds (autologoff=10 ) so if the agent never ans after 10 secs he will be logged out of the q mark, might be nice to add a DEBUG msg saying that the agent autologoff time expired & he is being logged out By: Mark Spencer (markster) 2003-08-26 09:30:22 There is one logged with LOG_NOTICE that says "Agent <foo> was auto logged off" By: Mark Spencer (markster) 2003-08-26 09:30:44 Configuration issue By: Adam Goryachev (adamg) 2003-08-27 06:00:13 Quote: There is one logged with LOG_NOTICE that says "Agent <foo> was auto logged off" But I don't get this message, though you are correct, show agents before/after shows the agent has been logged out. logger.conf: console => debug,notice,warning,error output on console:    -- Starting simple switch on 'Zap/2-1'    -- Executing Goto("Zap/2-1", "remote|s|7") in new stack    -- Goto (remote,s,7)    -- Executing Queue("Zap/2-1", "queue|t") in new stack    -- Started music on hold, class 'default', on Zap/2-1    -- outgoing agentcall, to agent '1001', on 'Local/1001@dispatchlogin-9fa7,1'    -- Executing Dial("Local/1001@dispatchlogin-9fa7,2", "Modem/g1:90402078431") in new stack    -- Called 1001    -- Called g1:90402078431    -- Nobody picked up in 15000 ms    -- Hungup 'Modem[i4l]/ttyI1'  == Spawn extension (dispatchlogin, 1001, 1) exited non-zero on 'Local/1001@dispatchlogin-9fa7,2' Started with asterisk -vvvvvvvvvrd By: Mark Spencer (markster) 2003-08-27 09:32:59 You won't get it over -r, only on the console or in the messages file.