[asterisk-bugs] [Asterisk 0012771]: Bogus <member> is still 'Not in Use' warnings for AgentLogin'ed agents.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12771 
====================================================================== 
Reported By:                davidw
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12771
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.20.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             06-02-2008 09:57 CDT
Last Modified:              07-04-2008 01:21 CDT
====================================================================== 
Summary:                    Bogus <member> is still 'Not in Use'  warnings for
AgentLogin'ed agents.
Description: 
Asterisk seems to correctly know when an AgentLogin type agent is busy on a
call, however every time our agent gets a call, we get a message like:

WARNING[16777] app_queue.c: The device state of this queue member,
Anonymous, is still 'Not in Use' when it probably should not be! Please
check UPGRADE.txt for correct configuration settings.

We've tried to get good presence information from the SIP phones that are
logging in as the agents, but haven't found a recipe that does achieves
this for outgoing calls.  However, this should be irrelevant as it is the
Agent itself whose state matters, not that of the SIP phone.  Moreover, for
AgentLogin, the busy state on the phone wouldn't change for each call, but
would cover the whole logged in period.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0012773 [patch] Agent doesn't propagate device ...
====================================================================== 

---------------------------------------------------------------------- 
 stp - 07-04-08 01:21  
---------------------------------------------------------------------- 
My system also have this warning message but I use SIP channel with
QueueAddMemeber. In my case, the warning happens because delay of
devicestate on SIP device.

There is addition code in devicestate.c , function
__ast_device_state_changed_literal(), that will handle state change on both
device and call. For example, when SIP answer, there will be notification
on state change for device SIP/XXXX and for call SIP/XXXX-YYYYY. By adding
the call to notification list, sip_devicestate() function will search for
device state of the call SIP/XXXX-YYYY. Which is not possible to find,
therefore, sip_devicestate() will call ast_gethostbyname() and get stuck
there for few seconds (about 10 secs). Delay in sip_devicestate() cause
notification thread not be able to process others state change for a while.
So the everything that wait for state change will not work as expect. After
change code in __ast_device_state_changed_literal, my problem is solved and
warning for "UPGRADE.txt" gone.

I also believe that this also a cause for bug 0012680 too. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-04-08 01:21  stp            Note Added: 0089723                          
======================================================================