| Summary: | ASTERISK-16570: Usage of unavailable channels on multi-PRI NT spans (NFAS) | ||
| Reporter: | Birger "WIMPy" Harzenetter (wimpy) | Labels: | |
| Date Opened: | 2010-08-15 11:24:44 | Date Closed: | |
| Priority: | Minor | Regression? | No |
| Status: | Open/New | Components: | Channels/chan_dahdi |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When Asterisk is (re)started while (only) the primary interface is down, it correctly activates the secondary D-channel, but none 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 | ||
| Comments: | By: Leif Madsen (lmadsen) 2010-08-31 13:19:36 Do you have a simple test that would show this happening? It seems you're able to reproduce this quite readily. Might help the developer in testing the same scenario. By: Birger "WIMPy" Harzenetter (wimpy) 2010-08-31 14:32:00 Can be reproduced by unplugging the primary interface and then (re) starting Asterisk. | ||