[asterisk-bugs] [Asterisk 0012144]: Agent status in queues

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12144 
====================================================================== 
Reported By:                DougUDI
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   12144
Category:                   General
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             03-05-2008 06:00 CST
Last Modified:              03-05-2008 12:17 CST
====================================================================== 
Summary:                    Agent status in queues
Description: 
In CLI using show queues command I will often get diferent status for same
agents on seperate queues. I believe the way the queue works is the
following:

Status = "Unknown" or "Not In USe" (the queue will pass calls to agents)

Status = "Ringing", "In use" or "Paused" (the queue stops passing calls)

Now this is correct however I have where there are 2 queues setup with
different Agents and the status of the Agent is not the same in both queues
(see below). The problem is that in 1 queue the Agent shows as "In Use" and
the other "Unknown" and therefore calls will be passed to the queue and
agent that shows as "Unknown" even though the Agent is on a call. This
causes a return of "Circut-Busy" and adds a CDR with No-Answer. This will
cause a mass amount of CDR's that are usless and end up with millions of
these entries in the database of Master.csv. When using a mysql database
this causes lookups to be very slow due to the masses of CDR's.

Can anyone explain why we have "unknown" status or how we can stop this
status showing a different value on seperate queues?

Thanks
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 03-05-08 12:17  
---------------------------------------------------------------------- 
state_interface is not officially supported in 1.4. I have no idea what
your backport entails, so I have no idea if there is an error there or
somewhere else. I am closing this issue since the report is against an
unsupported feature of 1.4. If the same behavior happens with 1.4 without
the state_interface backport or if the problem happens in trunk, please
feel free to reopen. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-05-08 12:17  putnopvut      Note Added: 0083461                          
======================================================================