From: Kristian K. <kri...@gm...> - 2007-05-18 14:31:33
|
On 5/18/07, Tony Plack <To...@pl...> wrote: > > I believe this is a Asterisk console bug, but thought I would run it through > here first. I can get Asterisk into a tight loop 100% of the time. Here is > what I know... > > First I have verbosity set to 20 in the asterisk.conf file. I believe that > has some bearing on this issue for two reasons. One it doesn't occur if I > turn verbosity off and two, there is no updates to the console occurring > without verbosity. > > Next, I connect to my Astlinux box using putty on a Windows XP machine (yes, > windows is involved in this but it may happen with other clients, just not > tested) and fire up asterisk console with "asterisk -r" > > Next, I put my Windows machine into suspend without shutting down putty. > This leaves the connection in an open state on the Linux box. > > Next, I have a call generated on my Digium TDM401 card via zap. This may > also work with SIP but it is not as consistent. > > At this point, the box stops responding. If I call the Zap Channel line, I > hear the SIT tones and the message starting "This system..." in stutter > format, like the machine is trying to push it out but the box is at 100%. > > The console is not responsive and I cannot troubleshoot it any further. > There is no dump file created or any logging done on the box. I have no way > to verify which asterisk process is exactly to blame. > > Here is my theory, The Zap Channel is trying to write via the console to a > port which was not closed properly, therefore, it goes into a loop trying to > contact that device. > > Like I said, this happens 100% of the time, I just cannot troubleshoot it > further. If I close out the putty session properly, I do not have an issue. > Tony, Wow! That is certainly an Asterisk bug... Have you mentioned anything on asterisk-users or filed a bug on bugs.digium.com? -- Kristian Kielhofner |