[asterisk-bugs] [JIRA] (ASTERISK-22756) [patch]Correct cause code for chan_dahdi request when trunk congested
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Fri Oct 25 16:36:03 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-22756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton updated ASTERISK-22756:
------------------------------------
Status: Open (was: Triage)
> [patch]Correct cause code for chan_dahdi request when trunk congested
> ---------------------------------------------------------------------
>
> Key: ASTERISK-22756
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-22756
> Project: Asterisk
> Issue Type: Improvement
> Security Level: None
> Components: Channels/chan_dahdi
> Affects Versions: 1.8.24.0, 12.0.0-beta1
> Environment: Any
> Reporter: Michael Walton
> Severity: Minor
> Attachments: chan_dahdi.c.correct-trunk-cause.r400911.patch
>
>
> New channel request in dahdi_request currently returns AST_CAUSE_CONGESTION for group matched with no channel available, but returns AST_CAUSE_BUSY for channel matched. This is fine for non-trunk channels, but breaks dialplan logic for trunk channels (e.g. FXO with fxsks signaling), because AST_CAUSE_BUSY is interpreted as "unable to reach party by any means" and terminates trunk hunting logic e.g. in FreePBX. The corrected cause, AST_CAUSE_CONGESTION, is interpreted as "try another means to reach party", resulting in selection of next priority trunk as intended. This patch uses the ISTRUNK() macro to determine the cause:
> ISTRUNK(p) ? AST_CAUSE_CONGESTION : AST_CAUSE_BUSY
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list