One of my clients today had a POTS line with a bad punch, and no dialtone. I used "zap destroy channel x" remotely to keep it from being used to send outbound calls, which worked fine. Line repunched, ready again to use, but how do I "undestroy" the channel? In the end I kicked everyone off with "zap restart" (which for some reason I had to do twice). Is there are a more elegant method to deal with this kind of issue? Cheers, j
----- "Jeff LaCoursiere" <jeff at jeff.net> wrote:> One of my clients today had a POTS line with a bad punch, and no > dialtone. > I used "zap destroy channel x" remotely to keep it from being used to > send > outbound calls, which worked fine. ?Line repunched, ready again to > use, > but how do I "undestroy" the channel? > > In the end I kicked everyone off with "zap restart" (which for some > reason > I had to do twice). ?Is there are a more elegant method to deal with > this > kind of issue? > > Cheers, > > jNope, that's the best you can do without restarting Asterisk. Is requiring two restarts reproducible? I'd really like to see console output with verbosity and debug set to 4 on chan_dahdi, preferably while only using zap channels. Jeff
----- "Tzafrir Cohen" <tzafrir.cohen at xorcom.com> wrote:> On Wed, Oct 01, 2008 at 01:39:29PM -0500, Jeff Peeler wrote: > > > Nope, that's the best you can do without restarting Asterisk. Is > > requiring two restarts reproducible? I'd really like to see console > > > output with verbosity and debug set to 4 on chan_dahdi, preferably > > while only using zap channels. > > Jeff is asking specifically about chan_dahdi and not about chan_zap > because he fixed this issue and several related issues (e.g.: > 'zap restart'/'dahdi restart' not working for a system with PRI, or > after a configuration error). Though he fixed them at the specific > version when chan_zap was renamed chan_dahdi and hence if you find > those > symptoms in chan_zap you probably still use the "buggy" version. > > -- > Tzafrir Cohen > icq#16849755 jabber:tzafrir.cohen at xorcom.com > +972-50-7952406 mailto:tzafrir.cohen at xorcom.com > http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir >Yes, the new changes will be in 1.4.22. I continually have to remind myself that users aren't running the most up to date code. Jeff