| Summary: | ASTERISK-20569: chan_dahdi does not overwrite context completely. | ||
| Reporter: | Tim Heath (theath) | Labels: | |
| Date Opened: | 2012-10-16 08:47:53 | Date Closed: | |
| Priority: | Minor | Regression? | |
| Status: | Open/New | Components: | Channels/chan_dahdi |
| Versions: | Frequency of Occurrence | Constant | |
| Related Issues: | |||
| Environment: | Asterisk 1.8.11-cert7 Linux 2.6.32-279.el6.x86_64 | Attachments: | ( 0) digium-info_20121016.tar.gz ( 1) digiuminfo.txt |
| Description: | If the context for dahdi channels are defined twice, in the same file or seperate, asterisk with report one context for the channel, but use the other. i.e. with the following config:
group=0 context=MyContext1 channel=>1-23 group=0 context=MyContext2 channel=>1-23 In the asterisk cli, issuing "dahdi show channels" will report the context for channel 1-23 as "MyContext2". However, and inbound call on those channels will enter the dialplan at MyContext1. The issue is easily worked around by either erasing the duplicate definition. (or setting the same context in both places I suppose) found the issue while working case 00300083, but easily reproduced it in the techsupport lab. | ||
| Comments: | By: Tim Heath (theath) 2012-10-16 08:50:41.074-0500 -added autosupport -config files should show the problem scenario on span 2. By: Richard Mudgett (rmudgett) 2012-10-16 14:51:04.163-0500 This happens with PRI and SS7 channels. These channels can not be reconfigured. Also this configuration warning has been ignored: LOG_WARNING, "Attempt to configure channel %d with signaling %s ignored because it is already configured to be %s.\n" chan_dahdi has always been terrible at processing its config files. | ||