From: Tony P. <To...@pl...> - 2007-05-18 13:45:01
|
<html><head><meta name=3D"Generator" content=3D"PSI HTML/CSS Generator"/> <style type=3D"text/css"><!-- body{font-family:'Tahoma';font-size:10pt;font-color:'#000000';} LI{display:list-item;margin:0.00in;} p{display:block;margin:0.00in;} body{} --></style> </head><BODY ><div><SPAN style=3D"font-family:'Arial';font-size:10pt;">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...</SPAN></div> <div> </div> <div><SPAN style=3D"font-family:'Arial';font-size:10pt;">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.</SPAN></div> <div> </div> <div><SPAN style=3D"font-family:'Arial';font-size:10pt;">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"</SPAN></div> <div> </div> <div><SPAN style=3D"font-family:'Arial';font-size:10pt;">Next, I put my= Windows machine into suspend without shutting down putty.  This leaves= the connection in an open state on the Linux box.</SPAN></div> <div> </div> <div><SPAN style=3D"font-family:'Arial';font-size:10pt;">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.</SPAN></div> <div> </div> <div><SPAN style=3D"font-family:'Arial';font-size:10pt;">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%.</SPAN></div> <div> </div> <div><SPAN style=3D"font-family:'Arial';font-size:10pt;">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.</SPAN></div> <div> </div> <div><SPAN style=3D"font-family:'Arial';font-size:10pt;">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.</SPAN></div> <div> </div> <div><SPAN style=3D"font-family:'Arial';font-size:10pt;">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.</SPAN></div> <div> </div> <div> </div> </body></html> |
From: Aleks C. <ac...@st...> - 2007-05-18 14:00:39
|
Awsome bug, but yea, that's an Asterisk issue. Aleks 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. > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... > -- Aleks Clark Star2Star Communications, LLC. 1605 Main Street Sarasota, Fl. 34236 941-234-0001 x118 ac...@st... www.star2star.com |
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 |