I tried to upgrade to 1.0.5 for libpri and all asterisk stuff to the last version. But now, my spans stays in RED Alarm. All seems ok, no error. Just no more links up I use a TE405P. Any idea ? I think it?s something from the old release that make conflict. So I tried to get back to previous version but I got the same problem. Not more SPAN UP Is there a script or something to uninstall all libpri, zaptel, asterisk librairy and files to try to get back to a nice config ? Thanks for your support. Regis -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050207/b80d1d67/attachment.htm
On Mon, 2005-02-07 at 20:16 +0100, R?gis MARTIN wrote:> I tried to upgrade to 1.0.5 for libpri and all asterisk stuff to the > last version. But now, my spans stays in RED Alarm. All seems ok, no > error. Just no more links up > > I use a TE405P. > > Any idea ? > > > > I think it?s something from the old release that make conflict. > > So I tried to get back to previous version but I got the same problem. > Not more SPAN UP > > > > Is there a script or something to uninstall all libpri, zaptel, > asterisk librairy and files to try to get back to a nice config ?Have you rebooted to clear the old modules out of memory before the new ones load. If not it may be the fact that your running old driver code with newer libpri code. BTW, TURN OFF HTML EMAIL. -- Steven Critchfield <critch@basesys.com>
> > I tried to reinstall all previous version (zapata, zaptel, libpri and > > asterisk) > > I reboot. And then... same thing :( > > Ring your T1 supplier, and ask them what they see. > They may well have marked it as "out-of-service", in which > case it won't come back 'till they re-enable it.I don't know if this is the case in your situation, but I've seen something similar with my TE410P card after an abrupt power loss (i.e. someone inadvertantly unplugging the power cord from the asterisk machine**): I get red alarms on all ports. The fix is to power down, physically unplug the machine so there is no power going to it for several seconds, then start up again. I'm well aware of this by now, but I called my provider several times in vain before I understood this pattern. I recall someone (Critch, I think) giving an explanation for this sometime back, but I'm unable to find it right now. ** Yup, that would be my dumb self... twice.