[Asterisk-Users] Zaptel/PRI problem

[Chris A. Icide]

Willy,

You may very well have a faulty card, or like I mentioned earlier there may 
be an incompatibility between the device that TWT installed at your site 
and the T100P card in the asterisk server.

What is the exact mfg. make and model number on the device they installed 
that splits the T1?  Are they still providing that variable bandwidth service?

You've gone about as far as you can debugging this software and system 
wise.  You ought to contact digium if you haven't already and have them 
send you a replacement T100P card and swap them out.

The fact that you have to do a power-cycle to restore correct functionality 
points more and more to some kind of hardware issue.  If a soft reboot 
doesn't fix what a hard does, you've kind of eliminated the OS driver 
issue, as well as asterisk coding or config file errors.

If this happens again as you list below and you are in a situation where 
you can perform a couple tests, try the following things:

unplug the T1 cable from the T100P card soft reboot and plug it back 
in.  Does this resolve the problem like the hard reboot?

with the T1 plugged in, power cycle the CPE box that does your 
phone/Internet breakout.

I'm just wondering if there is some incompatibility between you and that 
TWT box that might be causing all this and the steps above might add a 
little clarity to that.

-Chris


On 05:57 PM 4/10/2004, willy at yponeinc.com wrote:
 >List People ... I am getting really frustrated with this
 >digium t1 interface.
 >And I spoke (wrote) too soon!
 >Major crash this afternoon.  No sound at all.
 >Did a (remote) system reboot, and no change in status.  The
 >CLI indicates a call getting answered and an announcement
 >being played, but only a faint hiss is heard, and a faint
 >'click' when asterisk hangs up.
 >This will require me to actually drive to the place where
 >the [*] is located and do a full powerdown reboot.
 >Disheartening!!!
 >For the purpose of record, here's the notices/warnings seen
 >when the T1 interface died (so to speak)
 >Apr 10 13:31:11 WARNING[-1284645968]: PRI: Short write:
 >-1/15 (Unknown error 500)
 >Apr 10 13:31:11 WARNING[-1284645968]: Detected alarm on
 >channel 2: Red Alarm
 >Apr 10 13:31:11 WARNING[-1274156112]: PRI: Short write:
 >-1/15 (Unknown error 500)
 >Apr 10 13:31:11 WARNING[-1274156112]: Detected alarm on
 >channel 3: Red Alarm
 >Apr 10 13:31:11 WARNING[-1295135824]: PRI: Short write:
 >-1/15 (Unknown error 500)
 >Apr 10 13:31:11 WARNING[-1295135824]: Detected alarm on
 >channel 4: Red Alarm
 >Apr 10 13:31:11 WARNING[-1295135824]: PRI: Short write:
 >-1/15 (Unknown error 500)
 >Apr 10 13:31:11 WARNING[-1221706832]: Detected alarm on
 >channel 6: Red Alarm
 >Apr 10 13:31:11 WARNING[-1221706832]: Detected alarm on
 >channel 7: Red Alarm
 >etc. etc.
 >The alarms then cleared, and another event occured sometime
 >later:
 >Apr 10 16:14:42 WARNING[-1211216976]: PRI: Read on 35
 >failed: Unknown error 500
 >Apr 10 16:14:42 NOTICE[-1211216976]: PRI got event: 8 on
 >span 1
 >And since then: Bingo! No more voice (sound)
 >Apr 10 16:14:42 WARNING[-1211216976]: PRI: Read on 35
 >failed: Unknown error 500
 >Apr 10 16:14:42 NOTICE[-1211216976]: PRI got event: 8 on
 >span 1