[asterisk-bugs] [Asterisk 0012773]: [patch] Agent doesn't propagate device state changes from underlying device.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12773 
====================================================================== 
Reported By:                davidw
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   12773
Category:                   Channels/chan_agent
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     ready for testing
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 11:30 CDT
Last Modified:              06-25-2008 10:41 CDT
====================================================================== 
Summary:                    [patch] Agent doesn't propagate device state changes
from underlying device.
Description: 
Given a SIP phone logged in with AgentLogin, and monitored with qualify, if
you remove the power on the phone (or, presumably, unplug it from the
network) Asterisk detects that the phone has become unavailable, but the
agent continues to receive calls, resulting in callers going into a black
hole.

Ideally, I believe that the agent should detect the state change on the
underlying device and change its own state to logged off, and therefore
generate a state change to CHANUNVAIL.  This would result in correct
hinting for the agent's state.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0012771 Bogus <member> is still 'Not in U...
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 06-25-08 10:41  
---------------------------------------------------------------------- 
I thought loginchan was the obvious field to use, too, until I actually
checked what was stored in that field.  It's an extension and context, not
a name of a channel. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-25-08 10:41  Corydon76      Note Added: 0089220                          
======================================================================