[asterisk-bugs] [Asterisk 0015365]: ChanIsAvail is returning unavailable when the device is actually available

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15365 
====================================================================== 
Reported By:                ip-rob
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15365
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-06-20 09:50 CDT
Last Modified:              2009-08-20 14:59 CDT
====================================================================== 
Summary:                    ChanIsAvail is returning unavailable when the device
is actually available
Description: 
We have a SIP device (snom 300) that is registered successfully with
asterisk 1.4.25 (sip show peers shows the device). We are running freepbx
and try to call the extension associated with the device and the call goes
through. When we try to intercom, the call returns busy. 

FreePBX uses the following dialplan for intercom. The ChanIsAvail is
returning the channel isn't available when it clearly is (calls can be
routed there and it is registered in sip show peers).  The sip.conf
includes a qualify statement which shows the peer online with 40ms response
time.

The problem does not impact ALL devices. Re-registering the device and/or
rebooting it has no impact on the problem. 

Over time the number of devices impacted increases.  Once a device is in
this "state" then it will never get back to a correct state unless the
system is completely rebooted.


====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-20 14:59 lmadsen        Status                   new => feedback     
======================================================================