[asterisk-bugs] [Asterisk 0016035]: Status of dahdi/zap channels incorrectly reported unavailable instead of idle
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Jan 22 10:57:08 CST 2010
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: acknowledged
Asterisk Version: 1.4.27-rc2
JIRA: SWP-580
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: 2010-01-22 10:57 CST
======================================================================
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
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0016472 hints : DEVSTATE UNAVAIABLE not interpr...
======================================================================
----------------------------------------------------------------------
(0117073) viniciusfontes (reporter) - 2010-01-22 10:57
https://issues.asterisk.org/view.php?id=16035#c117073
----------------------------------------------------------------------
Me and a colleague of mine are working on a patch for that issue.
Meanwhile, we did a horrible hack to work around this issue.
On main/pbx.c, change the line 1946 from
return AST_EXTENSION_UNAVAILABLE;
to
return AST_EXTENSION_NOT_INUSE;
Note that this will make all unavaible extensions to appear as idle,
probably even if they don't exist. As our customer had just a few SIP
extensions, this hack worked fine for them.
Issue History
Date Modified Username Field Change
======================================================================
2010-01-22 10:57 viniciusfontes Note Added: 0117073
======================================================================
More information about the asterisk-bugs
mailing list