| Summary: | ASTERISK-05360: zapata.conf not reloaded on asterisk reload | ||
| Reporter: | Doug (racedoug) | Labels: | |
| Date Opened: | 2005-10-24 20:23:30 | Date Closed: | 2011-06-07 14:10:06 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | referring to an old issue 1172, is there a way to reload the zapata conf, without restarting asterisk? any work arounds? maybe another way to make the config changes in the zapata manually without loading the zapata conf? | ||
| Comments: | By: Russell Bryant (russell) 2005-10-24 20:40:27 reload chan_zap.so However, you can not change the signalling on a reload. By: Matt O'Gorman (mogorman) 2005-10-24 20:43:08 many of these issues have been addressed but some can not be changed. with 1.2 and later much can be reloaded really everything except signalling. This is awesome, close bug? By: Doug (racedoug) 2005-10-24 21:03:05 when you unload/load chan_zap.so any calls in progress get dropped is there a friendly way to reload without cutting off all the calls that are up? By: Matt O'Gorman (mogorman) 2005-10-24 23:11:42 a standard reload will reload everything that is possible in can_zap unloading a module wil always end any thing involved with said module, for example unloading chan_sip will end all your sip calls. By: Kevin P. Fleming (kpfleming) 2005-10-31 17:37:58.000-0600 Please don't open bugs just to ask questions... those are better handled on IRC or on the mailing lists. | ||