Summary:	ASTERISK-30274: chan_dahdi: Unavailable channels are BUSY
Reporter:	N A (InterLinked)	Labels:
Date Opened:	2022-10-23 15:29:58	Date Closed:	2022-10-26 10:46:11
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_dahdi
Versions:	18.15.0	Frequency of Occurrence	Constant
Related Issues:
Environment:		Attachments:
Description:	ASTERISK-29989 fixed an issue a while back where busy channels were unavailable when they weren't. Well, we now have the reverse issue: unavailable channels are busy when they're not. (e.g. mixup of BUSY and CHANUNAVAIL) Ultimately, the underlying issue here seems to be that the current mechanism of determining whether a DAHDI channel is insufficient. If the peer is available but in use, it should be busy, and if it's not available at all then it should be CHANUNAVAIL. This is actually not a regression, the problem is in chan_dahdi and not app_dial. I don't have a solution just yet but you can assign this to me.
Comments:	By: Asterisk Team (asteriskteam) 2022-10-23 15:30:02.606-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Friendly Automation (friendly-automation) 2022-10-26 10:46:12.207-0500 Change 19419 merged by Friendly Automation: chan_dahdi: Fix unavailable channels returning busy. [https://gerrit.asterisk.org/c/asterisk/+/19419|https://gerrit.asterisk.org/c/asterisk/+/19419] By: Friendly Automation (friendly-automation) 2022-10-26 10:55:38.918-0500 Change 19458 merged by Friendly Automation: chan_dahdi: Fix unavailable channels returning busy. [https://gerrit.asterisk.org/c/asterisk/+/19458|https://gerrit.asterisk.org/c/asterisk/+/19458] By: Friendly Automation (friendly-automation) 2022-10-26 11:14:26.693-0500 Change 19480 merged by George Joseph: chan_dahdi: Fix unavailable channels returning busy. [https://gerrit.asterisk.org/c/asterisk/+/19480|https://gerrit.asterisk.org/c/asterisk/+/19480] By: Friendly Automation (friendly-automation) 2022-10-26 11:14:52.528-0500 Change 19459 merged by George Joseph: chan_dahdi: Fix unavailable channels returning busy. [https://gerrit.asterisk.org/c/asterisk/+/19459|https://gerrit.asterisk.org/c/asterisk/+/19459]