[asterisk-bugs] [Asterisk 0016035]: Status of dahdi/zap channels incorrectly reported unavailable instead of idle

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16035 
====================================================================== 
Reported By:                francesco_r
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16035
Category:                   Core/PBX
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.27-rc2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-07 05:57 CDT
Last Modified:              2009-10-07 08:44 CDT
====================================================================== 
Summary:                    Status of dahdi/zap channels incorrectly reported
unavailable instead of idle
Description: 
Using the latest asterisk 1.4 releases, the state of a zaptel/dahdi
extension in idle is incorrecly reported with core show hints. For example
this is the output of a zaptel installation:
271 at ext-local           : ZAP/32                State:Unavailable    
Watchers  0

Or this is with dahdi:
521 at ext-local           : DAHDI/1               State:Unavailable    
Watchers  1

Instead ringing and inuse is correcly reported:
521 at ext-local           : DAHDI/1               State:Ringing        
Watchers  1

With an old 1.2 asterisk the status is always correct:
251                 : ZAP/32                State:Idle            Watchers
 0


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

---------------------------------------------------------------------- 
 (0111971) francesco_r (reporter) - 2009-10-07 08:44
 https://issues.asterisk.org/view.php?id=16035#c111971 
---------------------------------------------------------------------- 
I have several asterisk installations, it's difficult for me to know in
which release appeared this bug. But i have checked three different server
with 1.4.20, 1.4.21 and 1.4.24 and seems to work:
4075 at ext-local           : ZAP/5                 State:Idle
599 at ext-local           : DAHDI/32              State:Idle           
Watchers  0

I use standard FreePBX setup, so the files are auto-generated. In the
context ex-local i have:
exten => 4075,1,Macro(exten-vm,novm,4075)
exten => 4075,n,Hangup
exten => 4075,hint,ZAP/5 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-07 08:44 francesco_r    Note Added: 0111971                          
======================================================================