Magix 4.0 PRI / T1 WOES. 1

[rmktech]

I have installed a Magix 4.0 with a pri about two months ago. First off all went great. Inbound and outbound no problem. About 3.5 weeks ago we started going down from time to time. The system does not seem to drop calls. On inbound calls we get the canned SBC "All Circuits are Busy" I have replaced the T1 module. No fix or change. SBC tells me that they can not find anything on there end. The supposedly did a Class A inspection of the CO. When they say they do this the problem stops for 3-5 days then re-ocurrs.

I have copied the error log it is as follows:



A Last 99 System Errors:

A Message ss/pp Cnt First Last Code
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:21:35 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:21:40 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:21:45 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:21:50 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:21:55 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:00 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:05 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:10 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:15 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:20 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:25 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:30 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:35 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:40 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:45 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:50 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:22:55 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:00 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:05 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:10 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:15 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:20 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:25 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:30 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:35 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:40 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:45 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:50 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:23:55 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:24:00 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:24:05 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:24:10 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:24:19 7003
A DS1 SLIP ALARM 01/00 - - 08/19 00:30:45 6C0A
A POOL BUSY 00/02 - - 08/19 14:28:34 4C02
A POOL BUSY &/OR OOS 00/02 - - 08/22 21:49:10 4C03
A POOL BUSY 00/02 - - 08/23 11:32:45 4C02
A POOL BUSY &/OR OOS 00/02 - - 08/23 11:32:49 4C03
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:07:01 7003
A PRI B-CHNL NOT RELEASED 01/01 - - 08/23 14:07:05 7004
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:07:10 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:07:15 7003
A INVALID SANITY RESPONSE 01/00 - - 08/23 14:07:18 7804
A NOT IN NORMAL OP MODE 01/00 - - 08/23 14:07:19 7801
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:07:25 7003
A DS1 LOSS OF SIGNAL ALARM 01/00 - - 08/23 14:08:58 6C01
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:09:06 7003
A POOL BUSY &/OR OOS 00/01 - - 08/23 14:09:10 4C03
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:09:11 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:09:16 7003
A POOL BUSY &/OR OOS 00/01 - - 08/23 14:09:20 4C03
A DS1 BLUE ALARM 01/00 - - 08/23 14:09:21 6C02
A ERROR LOG


A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:09:21 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:09:26 7003
A POOL BUSY &/OR OOS 00/01 - - 08/23 14:09:31 4C03
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:09:31 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:09:36 7003
A POOL BUSY &/OR OOS 00/01 - - 08/23 14:09:40 4C03
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:09:41 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:09:46 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:09:51 7003
A POOL BUSY &/OR OOS 00/01 - - 08/23 14:09:53 4C03
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:09:56 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:01 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:06 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:11 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:16 7003
A POOL BUSY &/OR OOS 00/01 - - 08/23 14:10:20 4C03
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:21 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:26 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:31 7003
A POOL BUSY &/OR OOS 00/01 - - 08/23 14:10:35 4C03
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:36 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:41 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:46 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:51 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:10:56 7003
A POOL BUSY &/OR OOS 00/01 - - 08/23 14:10:57 4C03
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:11:01 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:11:06 7003
A POOL BUSY &/OR OOS 00/01 - - 08/23 14:11:09 4C03
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:11:11 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:11:16 7003
A POOL BUSY &/OR OOS 00/01 - - 08/23 14:11:20 4C03
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:11:21 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:11:26 7003
A DS1 LOSS OF SIGNAL ALARM 01/00 - - 08/23 14:11:30 6C01
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:11:31 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:11:36 7003
A POOL BUSY &/OR OOS 00/01 - - 08/23 14:11:38 4C03
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:11:41 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:11:46 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:11:55 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:12:00 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:12:05 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/23 14:12:10 7003
A DS1 MISFRAME ALARM 01/00 - - 08/23 14:15:41 6C09
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:21:25 7003
A PRI D-CHNL INOPERATIVE 01/00 - - 08/19 00:21:30 7003

A Permanent Errors:

A Message ss/pp Cnt First Last Code

A Transient Errors:

A Message ss/pp Cnt First Last Code
A ERROR LOG


A POOL BUSY 00/02 002 08/19 14:28:34 08/23 11:32:45 4C02
A POOL BUSY &/OR OOS 00/02 002 08/22 21:49:10 08/23 11:32:49 4C03
A INVALID SANITY RESPONSE 01/00 001 08/23 14:07:18 08/23 14:07:18 7804
A NOT IN NORMAL OP MODE 01/00 001 08/23 14:07:19 08/23 14:07:19 7801
A POOL BUSY &/OR OOS 00/01 011 08/23 14:09:10 08/23 14:11:38 4C03
A DS1 MISFRAME ALARM 01/00 001 08/23 14:15:41 08/23 14:15:41 6C09


Everything I see points back to SBC(T1 /pri provider).
Could I be misssing something?


Thanks

Ron K.

 

[merlinman]

What modules do you have in the system?

 

[rmktech]

MerlinMan:

t1, 412 tdl, 024 tdl, 016 tr. In that order


ron k.

 

[rmktech]

Merlinman:

To be more specific:
01=100d/csu/dsu-u
0b / 33/ a1
02=412-ls tdl
02/ 0b / 02
03=024 tdl
02 / 0b / 02
04=016 trr
50/ 22 / 12

does this change anything??

ron k

 

[merlinman]

Well, it doesn't seem to be the Hardware Conflict we know about.

The 100d csu-dsu doesn't have the problem with the 016 boards that previous versions have.

 

[rmktech]

I am changing the processor today, just tom keep the customer happy. magix 4.0 r7.0

I am sure it is SBC though.

thank you

ron k

 

[merlinman]

Good Luck...

I can do dial in support if need be, but we gotta' set it up in advance....

 

[phonesrus]

Take a look at your T-1 SmartJack and see if it is a PairGain HDSL unit (SBC installed a lot of them) The PairGain unit uses Two (2) 765Kb channels each transmitting half of the circuit on a pair (ch1-12 on Loop1) and (13-24[13-23+d] on loop2) on a 4-wire circuit, in order to gain more cable feet between repeaters. If you have copper trouble on loop2 you could have the repeated/intermittant loss of "D" channel you are seeing, but existing calls on the loop1 will remain stable. This is not a conventional T-1 circuit. Look at the lamps marked loop1 and loop2 and see if you see them flash yellow or Red: both indicate issues with loop. You can also get into the serial port on the SJ and look at the reports with Hyperterminal. Just a suggestion, but I have seen it a number of times, since I am in an SBC area. If you open a ticket with SBC, ask to speak with a tester in ISDN/GBC and request him/her to look at the PM data on the circuit.

 

[rmktech]

Hello all back again. I am still having this problem with the pri. I have had SBC replace the smart jack and still every so often i get a can message saying "All circuits are busy",, sbc say my switch is telling them that. The odd thing is everything works fine, then for no appearent reason the message plays to incoming callers. All previous PM's have shown nothing.

any comments??

Thanks
Ron

 

[merlinman]

1st, confirm or deny Phonesrus issues.

Now my other 2 cents - If you have INTERMINTTENT CONNECTION PROBLEMS, your T1 will go down,and the OTHER END will say the problem is with us. (Of Course)

So, another thing to check is CONNECTIVITY.

Perhaps a bad wire?

Get it up amd working and, REALLY, start baning on things with your hand and see if it goes into trouble.

Take this for what it's worth......

"An Installer's job is to make it work, A repairman's job is to make it fail"[/color blue]

That is to say, if it ain't broke, you can't fix it.....

Again....- - Good Luck - -

 

[SYQUEST]

Phonesrus and Merlinman are right on the money! The problem with HDSL T1 is the lack of alarm indication when the HDSL envelope goes bad because of cable pairs or doublers going to sleep! This problem has been around from the beginning of its use in the loop plant when the telcos started to replace repeatered T1 with HDSL(cost). The only way you will get a T1 alarm from the HDSL is if it dies because of no power on the loop. (upstream alarms in the CO will be sent but that is all) I have had these things drive me nuts when using channel 24 for DDS and it would not work. But no alarms! Then I found out what it was doing when I put the T-Berd on it to monitor and bang that was it.

I would open a new trouble ticket and have the CO techs read the stats in the HTU-C and HTU-R and have them monitor the ckt also. Pacific Bell never installed any automated way for the PCO to dump the stats on the units. They have to be done manually in the CO.

What HDSL does is change the T1 signal to another format using a 2B1Q protocol or translation, something akin to a VPN maybe. 12 channels on each pair, but without some of the limitations of repeatered T1: NEXT, bridge taps, etc. but the T1 envelope is completely isolated from the HDSL 2B1Q and when it is impaired and affects the T1 transmission no alarms are generated at the T1 level.

....JIM....