[asterisk-users] Queue member (Agent) does not Dial

Kurian Thayil kurianmthayil at gmail.com
Fri Jul 17 04:58:38 CDT 2009


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:

8557         (Name1) available at '8557 at specagentdial' (musiconhold is
'default')
8545         (Name2) not logged in (musiconhold is 'default')
8555         (Name3) available at '8555 at 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 at specagentdial' (musiconhold is
'default')
85766        (Name10) available at '85766 at specagentdial' (musiconhold is
'default')
84888        (Name11) available at '84888 at specagentdial' (musiconhold is
'default')
85511        (Name12) available at '85511 at specagentdial' (musiconhold is
'default')

The CLI message is given below:

    -- 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",
"agi_queue.sh|QMA_20090717-054744_1247824046-897|MAQ") in new stack
    -- Executing Queue("Zap/1-1", "maqueue|t|||180") in new stack
    -- Executing AGI("Local/84888 at specagentdial-14bb,2",
"agi_qdial.sh|84888|315362XXXX") in new stack
    -- Executing AGI("Local/85744 at specagentdial-beba,2",
"agi_qdial.sh|85744|315362XXXX") in new stack
    -- Executing AGI("Local/85511 at specagentdial-67be,2",
"agi_qdial.sh|85511|315362XXXX") in new stack

Here, from above, AGI program agi_qdial.sh 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?

Regards,

Kurian Thayil.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090717/167d706d/attachment.htm 


More information about the asterisk-users mailing list