Summary:ASTERISK-01166: zapata.conf not reloaded on asterisk reload.
Reporter:zoa (zoa)Labels:
Date Opened:2004-03-06 04:10:37.000-0600Date Closed:2011-06-07 14:10:44
Versions:Frequency of
Description:Asterisk reload should also reload zapata.conf i think.
(eg when you changed the context for zapata in zapata.conf.)
Comments:By: Brian West (bkw918) 2004-03-06 23:47:18.000-0600

This is complicated.  You can't really reload the config when channels are in service.  The only option is to unload chan_zap and load it back if possible.  Mark has already talked about this.  I and others have worked hard to make the unload of chan_zap work.

By: Mark Spencer (markster) 2004-03-06 23:49:20.000-0600

The correct thing will be to support reload with the exception of changing signalling.  That should be possible to do, but is not likely to happen before 1.0.

By: James Golovich (jamesgolovich) 2004-03-07 03:03:11.000-0600

I've worked on this in the past, I'll have to dig out my previous efforts and see what has to be done.  Had some special case scenarios when changing channel signalling that had to be worked around but shouldn't be much of an issue now.

By: zoa (zoa) 2004-03-07 05:14:10.000-0600

nopez its not much of an issue, i think including the statement "requires an unload of the module / restart of asterisk" in zapate.conf is good enough, that way people will know to restart.

By: opsys (opsys) 2004-03-11 12:43:16.000-0600

If the zapata file could simply be reread and all values except for signalling reloaded that would help trememdously for move, adds, and changes as if you change the person from one desk to another simply changing the callerid info as well as callwaiting, mailbox, etc. has to be done at EOD and needs a truck roll, instead of ssh!  Changing signaling rarely happens but the other stuff changes quite frequently.

edited on: 03-11-04 12:42

By: Brian West (bkw918) 2004-04-13 13:20:54

this is hard to do.  unload chan_zap.so, load chan_zap.so it should work.

By: twisted (twisted) 2004-04-29 09:51:40

Since this may get picked back up after 1.0/1.1 release, I'm going to close it for now.  If it needs to be re-opened, it can be done by posting back here.