The TE410P should run fine under both Redhat 9 and Fedora Core 1. My first question is: Are you running a new CVS version? Maybe there have been bugs introduced with all of the recent changes. I'm running under December versions - works ok, except for problems experienced under very heavy call loads, that have been discussed on here many times (still not resolved)
But it also sounds possible that you're having basic PRI problems of some sort, perhaps clock sourcing or something similar. Please share your zaptel.conf and zapata.conf, including which span is connected to what. Regards Scott Scott M. Stingel Emerging Voice Technology Inc. Palo Alto, California and London, England Email: [EMAIL PROTECTED] URL: www.evtmedia.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Gomillion Sent: Monday, January 26, 2004 7:43 AM To: [EMAIL PROTECTED] Subject: [Asterisk-Users] TE410P on Redhat 9 I am the proud new owner of a TE410P, and installed it on a RedHat 9 box. After compiling just fine, running like a champ in tests, and having my extensions.conf configured to taste, I went ahead and did a live beta test this past weekend. The phone system stopped responding 3 times. The first time, I got into the asterisk console, vi -rvvvvv. I didn't see anything too out of the ordinary, except for lots of messages that all of the lines were busy (even though no calls were up and I have 2 PRI's). I thought it odd, but since I had been tweaking a config file or two, I didn't think too much about it. I just stopped * and Zaptel, and then restarted them, in reverse order. And everything was beautiful. THen, on Saturday night, around 7:00 PM, I tried to call in again (I was calling in every half hour to make sure it was working), it had died. I was in a bad mood, and just restarted the same as I had the day before to get it over with. Finally, on Sunday morning, I tested the phone, and at about 8:00 am * was not responding. I logged in, again with 5 v's, and saw an error message to the effect "Span 2 is up". Span 2 is a PRI from * to my Norstar MICS, using a cross-over cable. I think the LBO and signalling are correct, because calls went through it just fine until the 3 times mentioned above. I started by doing a reload, which changed nothing, then a restart when convenient, which changed something... Now, Span 1, 2, 3, and 4 all gave the message that they were up, about 1x per 2 seconds, each. Every 5 or 6 messages I would see that one of the spans was down, but most of the messages were just about being up. I immediately stopped Asterisk and Zaptel, restarted Zaptel, then Asterisk, and everything ran fine through this morning, when I took Asterisk out of the loop (planned end of the beta test). Does anyone have any ideas what might be causing this, and how to diagnose without taking our main phone switch down? I have access to a PRI, but it has no phone numbers that ring into it, so I can connect to real network equipment and make calls, but cannot receive any. Thanks, David Gomillion _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
