Agent is not Dialed - Queue

Hi All,

We are using Asterisk 1.2.18 in a CentOS box. Implemented a queue (maqueue) structure for handling customer calls. There are 4 queue members (85744,85766,85511,84888). These 4 members are logged in using AgentCallbackLogin application. But at some point, one of the agent’s SIP phone does not ring for an incoming call to this queue. I checked the agent status and it is not in paused state. When I looked in the CLI, I couldn’t see any attempt by the Asterisk to dial that particular agent. What are the possiblities for a queue member not dialed by Asterisk? This agent is defined in agents.conf, member of the queue defined in queues.conf and is not paused. The output of show agents from CLI is shown below:

[quote]8557 (Name1) available at ‘8557@specagentdial’ (musiconhold is ‘default’)
8545 (Name2) not logged in (musiconhold is ‘default’)
8555 (Name3) available at ‘8555@specagentdial’ (musiconhold is ‘default’)
8552 (Name4) not logged in (musiconhold is ‘default’)
8551 (Name5) not logged in (musiconhold is ‘default’)
8541 (Name6) not logged in (musiconhold is ‘default’)
8444 (Name7) not logged in (musiconhold is ‘default’)
85577 (Name8) not logged in (musiconhold is ‘default’)
85744 (Name9) available at ‘85744@specagentdial’ (musiconhold is ‘default’)
85766 (Name10) available at ‘85766@specagentdial’ (musiconhold is ‘default’)
84888 (Name11) available at ‘84888@specagentdial’ (musiconhold is ‘default’)
85511 (Name12) available at ‘85511@specagentdial’ (musiconhold is ‘default’)[/quote]
The CLI message is given below:

[quote] – Executing Wait(“Zap/1-1”, “2”) in new stack
– Executing Answer(“Zap/1-1”, “”) in new stack
– Executing Playback(“Zap/1-1”, “Thankyou9800”) in new stack
– Executing Set(“Zap/1-1”, “editeduid1=1247824046”) in new stack
– Executing Set(“Zap/1-1”, “editeduid2=897”) in new stack
– Executing Set(“Zap/1-1”, “editeduid=1247824046-897”) in new stack
– Executing Set(“Zap/1-1”, “MONITOR_FILENAME=QMA_20090717-054744_1247824046-897”) in new stack
– Executing AGI(“Zap/1-1”, “|QMA_20090717-054744_1247824046-897|MAQ”) in new stack
– Executing Queue(“Zap/1-1”, “maqueue|t|||180”) in new stack
– Executing AGI(“Local/84888@specagentdial-14bb,2”, “|84888|315362XXXX”) in new stack
– Executing AGI(“Local/85744@specagentdial-beba,2”, “|85744|315362XXXX”) in new stack
– Executing AGI(“Local/85511@specagentdial-67be,2”, “|85511|315362XXXX”) in new stack[/quote]
Here, from above, AGI program which handles the dial operation does not make any attempt to dial 85766. Wondering why this is happening. The issue gets resolved only when asterisk service is restarted which is not a pretty good workaround. Any clue on this?


Kurian Thayil.

Note Asterisk 1.2 is no longer supported and AgentCallbackLogin is deprecated from Asterisk 1.4 (use local channels instead).

Hi David,

Thanks for the reply. So is this a known bug in Asterisk 1.2.X series and one of the reason the AgentCallbackLogin got deprecated?


Kurian Thayil.

Not supported basically means that not many people will know what bugs there are in 1.2.

I suspect the reason that it is deprecated is that it complex processing that can be simulated using a more general mechanism.