Jman, **watch the following: ascend1> test 4-28948 Data-Svc=Modem calling...answering... Error: call terminated << This was successfully calling my phone at my office desk. >> ascend1> test 28948 Data-Svc=Modem << This was successfully CRASHING one of my MAX4K, as one can easily verify by analyzing the syslog/fat output below: >> May 7 19:18:18 ascend1 ASCEND: slot 9 port 4, Outgoing Call, 28948 May 7 19:19:58 ascend1 ASCEND: slot 0 port 0, Ethernet Up May 7 19:20:07 ascend1 ASCEND: slot 0 port 0, line 1, channel 0, Trunk Up May 7 19:20:07 ascend1 ASCEND: slot 0 port 0, line 2, channel 0, Trunk Up May 7 19:20:07 ascend1 ASCEND: slot 0 port 0, line 1, channel 0, Trunk Up May 7 19:20:07 ascend1 ASCEND: slot 0 port 0, line 2, channel 0, Trunk Up FATAL ERROR: Index: 1 Load: eo.m40 Revision: 5.0Ap3 Date: 05/07/1997. Time: 19:18:30 Location: b01eff1c b01f1ccc b01f2934 b0127b98 b01c3504 b0052dd0 SYSTEM IS UP: Index: 100 Load: eo.m40 Revision: 5.0Ap3 Date: 05/07/1997. Time: 19:20:10 Such behavior is known at my site since some early 4.X Releases (4.4, but not sure). NOTICE: This call (above) was originated towards an ALCATEL4400 switch with OSlevel 1.5.2. **Now let's try something different: ascend2> test 9-79828948 Data-Svc=Modem calling... May 7 19:34:29 ascend2 ASCEND: call 111 OR slot 9 port 5 MODEM 979828948 << This was successfully calling my phone at my office desk. >> ascend2> test 79828948 Data-Svc=Modem calling... Error: call failed ascend2> ascend2> May 7 19:35:59 ascend2 ASCEND: slot 9 port 7, Outgoing Call, 79828948 May 7 19:35:59 ascend2 ASCEND: slot 9 port 7, Call Terminated << And THIS was UNsuccessfully crashing one of my MAX4K, as one can easily verify by analyzing the syslog output below :) >> NOTICE: The latter call (above) was originated towards a (probably) SIEMENS swith at German TELEKOM. Obviously you may not only crash your MAX by dialing in with carefully selected dialup clients, you might have the option to do so by running your MAX at carefully selected switches too!!!! Sounds familiar? Known problem? Kevin? > I upgraded from 4.6Cp11 last week on my 4002 to 5.0Ap5. > After a week the MAX started resetting frequently. I have identified > the problem as being caused by someone dialing out on the BRI-T card > with a 2 prefix instead of 9 ( I use trunk groups). I found this out > by accident when the person tried to make a video call but forgot the > prefix. I can reproduce this every time! > This is the fatal-history. Thanks for listening, -- ----------------------------------------------------------------------- Stefan Lanz Member of Lanz@rz.uni-frankfurt.de * Unix Cluster Administration (BEUS) Phn: +49 69 798-28948 * Networking Staff Fax: +49 69 798-28313 Frankfurt University Computing Centre --===-- Johann Wolfgang Goethe Universitaet, D-60054 Frankfurt, Germany ----------------------------------------------------------------------- ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.shore.net/~dreaming/ascend-faq">http://www.shore.net/~dreaming/ascend-faq</A>> or <<A HREF="ftp://ftp.shore.net/members/dreaming/ascend-faq.txt">ftp://ftp.shore.net/members/dreaming/ascend-faq.txt</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <!--X-Follow-Ups-End--> <!--X-References--> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg00073.html">(ASCEND) Netwarp 2.2.4</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg00061.html">(ASCEND) Palmtop port</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg00076.html">Re: (ASCEND) Palmtop port</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg00073.html">(ASCEND) Netwarp 2.2.4</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="mail11.html#00074"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd4.html#00074"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>