[asterisk-bugs] [JIRA] (ASTERISK-16570) Usage of unavailable channels on multi-PRI NT spans

Birger "WIMPy" Harzenetter (JIRA) noreply at issues.asterisk.org
Tue Jun 23 12:17:32 CDT 2015


     [ https://issues.asterisk.org/jira/browse/ASTERISK-16570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Birger "WIMPy" Harzenetter updated ASTERISK-16570:
--------------------------------------------------

    Description: 
When Asterisk is (re)started while (only) the primary interface is down, it correctly activates the secondary D-channel, but non the less selects B-channels from the unavailable primary interface.
It only happens when the primary interface is unavailable from the beginning.
If it's been up and fails while Asterisk is running, channel selection works as expected.

****** ADDITIONAL INFORMATION ******

Tried with Asterisk-1.8.0-beta2, dahdi-2.3.0.1+2.3.0, libpri-1.4.11.2 and libpri-1.4.12-beta1

  was:
When Asterisk is (re)started while (only) the primary interface is down, it correctly activates the secondary D-channel, but non the less selects B-channels from the unavailable primary interface.
It only happens when the primary interface if unavailable from the beginning.
If it's been up and fails while Asterisk is running, channel selection works as expected.

****** ADDITIONAL INFORMATION ******

Tried with Asterisk-1.8.0-beta2, dahdi-2.3.0.1+2.3.0, libpri-1.4.11.2 and libpri-1.4.12-beta1


> Usage of unavailable channels on multi-PRI NT spans
> ---------------------------------------------------
>
>                 Key: ASTERISK-16570
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-16570
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_dahdi
>            Reporter: Birger "WIMPy" Harzenetter
>            Severity: Minor
>
> When Asterisk is (re)started while (only) the primary interface is down, it correctly activates the secondary D-channel, but non the less selects B-channels from the unavailable primary interface.
> It only happens when the primary interface is unavailable from the beginning.
> If it's been up and fails while Asterisk is running, channel selection works as expected.
> ****** ADDITIONAL INFORMATION ******
> Tried with Asterisk-1.8.0-beta2, dahdi-2.3.0.1+2.3.0, libpri-1.4.11.2 and libpri-1.4.12-beta1



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



More information about the asterisk-bugs mailing list