[asterisk-bugs] [JIRA] (ASTERISK-25935) channels/sig_pri.h -> sig_pri_span -> force_restart_unavailable_chans in wrong scope

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-25935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230289#comment-230289 ] 

Asterisk Team commented on ASTERISK-25935:
------------------------------------------

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.

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].

> channels/sig_pri.h -> sig_pri_span -> force_restart_unavailable_chans in wrong scope
> ------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-25935
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25935
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_dahdi
>    Affects Versions: 13.1.0
>         Environment: Asterisk certified 13.1-cert3 or Asterisk 13.1-cert4 or Asterisk 13.1-cert5
> CentOS 6
>            Reporter: Frederic LE FOLL
>
> This issue is a clone of ASTERISK-25257.
> Asterisk 13.1-cert3 received an upgrade of chan_dahdi.c and sig_pri.h.
> sig_pri.h defines file force_restart_unavailable_chans only when #if defined(HAVE_PRI_MCID) is true.
> chan_dahdi.c uses this field without the condition.
> Thus, chan_dahdi won't compile if HAVE_PRI_MCID is not defined.
> Original issue was discovered on Asterisk 13.4.0, but it also affects Asterisk certified 13.1-cert3 and newer.



--
This message was sent by Atlassian JIRA
(v6.2#6252)