On Sun, Jun 12, 2005 at 06:10:53AM -0400, Michael Di Martino wrote: > > However i still get the same error. Please help we cannot connect call > form my norstar to asterisk w/ it dropping in 10 seconds. > > Jun 12 10:51:51 NOTICE[213005]: PRI got event: 5 on Primary D-channel of > span 2 > Jun 12 10:51:51 WARNING[213005]: No D-channels available! Using Primary > on channel anyway 48!Jun 12 10:51:51 NOTICE[262160]: Alarm cleared on > channel 35 > Jun 12 10:51:51 NOTICE[262160]: Alarm cleared on channel 36 > Jun 12 10:51:51 NOTICE[262160]: Alarm cleared on channel 37 > Jun 12 10:51:51 NOTICE[262160]: Alarm cleared on channel 38
Hmmm. Links works and suddenly stops. No changes to either side both of which you control. To test the cable idea someone had, pull the cable and see if messages are the same or different. If the same, then it's likely the cable that's the problem. If different, the it's likely that the cable is not the problem. My vote is for clocking. I've had non-Asterisk T1/E1 circuits act fine for long periods and then flake out. Correcting the clocking relationship fixed the flakyness. One way to investigate clocking is to use the pri commands to watch the D channel activity. If you see lots of Q.921 messages (SABME, RR, etc.) then it might be the result of fouled up messaging from bad CRC and other broken protocol events stemming from bad clocking. I've collected some articles and discussions on T1/E1 clocking here: http://www.voip-info.org/tiki-index.php?page=Asterisk+PRI -- Mike _______________________________________________ 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
