[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 09:49 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...
====================================================================== 

---------------------------------------------------------------------- 
 davidw - 06-25-08 09:49  
---------------------------------------------------------------------- 
It's stable and recognizing that the SIP device is associated with the
agent, but the agent is not going unavailable.  I'm still trying to work
out what is wrong.

[Jun 25 15:32:39] NOTICE[10058] chan_sip.c: Peer '4222' is now
UNREACHABLE!  Last qualify: 89
[Jun 25 15:32:39] DEBUG[10058] chan_sip.c: Destroying SIP dialog
483a739c0083a38d065929f633d76bdb at 192.168.130.116
[Jun 25 15:32:39] VERBOSE[10058] logger.c: Really destroying SIP dialog
'483a739c0083a38d065929f633d76bdb at 192.168.130.116' Method: OPTIONS
[Jun 25 15:32:39] DEBUG[10058] devicestate.c: Notification of state change
to be queued on device/channel SIP/4222
[Jun 25 15:32:39] DEBUG[10040] chan_sip.c: Checking device state for peer
4222
[Jun 25 15:32:39] DEBUG[10040] devicestate.c: Changing state for SIP/4222
- state 5 (Unavailable)
[Jun 25 15:32:39] DEBUG[10040] devicestate.c: Notification of state change
to be queued on device/channel Agent/1001
[Jun 25 15:32:39] DEBUG[10040] chan_sip.c: Checking device state for peer
4222
[Jun 25 15:32:39] DEBUG[10040] devicestate.c: Changing state for
Agent/1001 - state 1 (Not in use)
[Jun 25 15:32:39] DEBUG[10065] app_queue.c: Device 'SIP/4222' changed to
state '5' (Unavailable) but we don't care because they're not a member of
any queue.
[Jun 25 15:32:39] DEBUG[10065] app_queue.c: Device 'Agent/1001' changed to
state '1' (Not in use) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-25-08 09:49  davidw         Note Added: 0089216                          
======================================================================