| Summary: | ASTERISK-15794: Context statement removed from [general] section of sip.conf, but remained active even after a reload | ||
| Reporter: | hugolivude (hugolivude) | Labels: | |
| Date Opened: | 2010-03-11 21:00:54.000-0600 | Date Closed: | 2011-06-07 14:05:13 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/Configuration |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Cent OS 5.0 When a context in the [general] section of sip.conf is removed, it persists even after a reload. I discovered this while troubleshooting issue ASTERISK-1678010. I have sip.conf this way: [general] context=incoming-bogus-calls . . . [voip-provider] context=ValidIncoming . . . I found that asterisk was sending calls from my voip-provider to “incoming-bogus-calls” instead of “ValidIncoming”. I removed context=incoming-bogus-calls from the [general] section and did a reload but Asterisk continued to try and send the calls to “incoming-bogus-calls” as indicated in the sip debug messages. I rebooted and this behaviour ceased - the calls began to be directed to “ValidIncoming” as expected. | ||
| Comments: | |||