Avidcomm

It's been a while but I remember you also had to enable the PRI protocol in A 90 something Load 90, 91, 93 Like I said it's been awhile.

Avidcomm

PRI coming up looks like this

0186 L2P 0002 ckb ENM rcv lnk 0 chl 24 RR PH_DAT_I
0187 L2P 0002 ckb rcv lnk0 B24 siz=12 PH_DAT_I
0188 L2P 0002 ckb ENM rcv lnk 0 chl 24 I FRM PH_DAT_I
0189 L3E 0002 valh data ptr = 41e2ed
018a L3E 0001 chk_l3ms returning TRUE
018b L3E 0002 SEI EST SEI 0 - event = DL_DATA
018c L3E 0002 -CRN- U0 CRN = 8000 Ev = L2 RESTART func = d1
018d L3E 0002 CRN New state = U0
018e IDS 0002 IDS Interface Process @ 020 sec
018f IDS 0002 idsc No calls Active
0190 L2P 0002 ckb rcv lnk0 B24 siz=4 PH_DAT_I
0191 L2P 0002 ckb ENM rcv lnk 0 chl 24 RR PH_DAT_I
0192 TSW 0001 1sec Rcv Slip Negative
0193 L2P 0002 ckb rcv lnk0 B24 siz=4 PH_DAT_I
0194 L2P 0002 ckb ENM rcv lnk 0 chl 24 RR PH_DAT_I
0195 IDS 0002 IDS Interface Process @ 040 sec
0196 IDS 0002 idsc No calls Active
0197 L2P 0002 ckb rcv lnk0 B24 siz=4 PH_DAT_I
0198 L2P 0002 ckb ENM rcv lnk 0 chl 24 RR PH_DAT_I
0199 L2P 0002 ckb rcv lnk0 B24 siz=4 PH_DAT_I
019a L2P 0002 ckb ENM rcv lnk 0 chl 24 RR PH_DAT_I
019b TSW 0040 1sec 15 minute timeout
019c IDS 0002 IDS Interface Process @ 0:15: 0 sec
019d IDS 0002 idsc No calls Active

T1 CARD MONITORING (H) Mon 11-10-97 6:09 p

REVISION: PRI 1.00 DATE: Mon 11-10-97 6:08 p [A]SSIGN 2 SLOTS Y
ALARM STATUS: 07
BPV STATUS: 00 [V]OLUME 07

MISC. INFO MSG_in: 30 MSG_out: 24 Board Reset[s]: 4
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

CH # 01 Line 49 NULL CH # 13 Line 61 NULL
CH # 02 Line 50 NULL CH # 14 Line 62 NULL
CH # 03 Line 51 NULL CH # 15 Line 63 NULL
CH # 04 Line 52 NULL CH # 16 Line 64 NULL
CH # 05 Line 53 NULL CH # 17 Line 65 NULL
CH # 06 Line 54 NULL CH # 18 Line 66 NULL
CH # 07 Line 55 NULL CH # 19 Line 67 NULL
CH # 08 Line 56 NULL CH # 20 Line 68 NULL
CH # 09 Line 57 NULL CH # 21 Line 69 NULL
CH # 10 Line 58 NULL CH # 22 Line 70 NULL
CH # 11 Line 59 NULL CH # 23 Line 71 NULL
CH # 12 Line 60 NULL CH # 24 D CHANNEL MF_EST_NRM

[E]nter card number to monitor [ CR = next card ][ 15 ]


PRI Down looks Like this Notice Channel 24

T1 CARD MONITORING (H) Mon 11-10-97 6:09 p

REVISION: PRI 1.00 DATE: Mon 11-10-97 4:50 p [A]SSIGN 2 SLOTS Y
ALARM STATUS: 07
BPV STATUS: 00 [V]OLUME 09

MISC. INFO MSG_in: MSG_out: 2 Board Reset[s]: 4
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

CH # 01 Line 72 NULL CH # 13 Line 84 NULL
CH # 02 Line 73 NULL CH # 14 Line 85 NULL
CH # 03 Line 74 NULL CH # 15 Line 86 NULL
CH # 04 Line 75 NULL CH # 16 Line 87 NULL
CH # 05 Line 76 NULL CH # 17 Line 88 NULL
CH # 06 Line 77 NULL CH # 18 Line 89 NULL
CH # 07 Line 78 NULL CH # 19 Line 90 NULL
CH # 08 Line 79 NULL CH # 20 Line 91 NULL
CH # 09 Line 80 NULL CH # 21 Line 92 NULL
CH # 10 Line 81 NULL CH # 22 Line 93 NULL
CH # 11 Line 82 NULL CH # 23 Line 94 NULL
CH # 12 Line 83 NULL CH # 24 D CHANNEL AWAIT EST

[E]nter card number to monitor [ CR = next card ][ 17 ]

gei_spot

enl dch xxxx in ld 96, before trying to bring up your loops. Hope that helps, if not post back, I will be up for a little while.

gei_spot

Sorry, did not read through... dumb ?, have you checked the CSU's? are they up? Have you verified that the spans are truly up with a test set? You are showing RED which through my experience means that something is wrong locally.

Ramjet

Is it up now? We had the same here in Jonesboro, although nothing down that we know of yet. Just came in to the office, and no calls yet, and no word from the on-call tech of anything? By the way, who do you work for in Jacksonville? I am with Ritter Communications up here in JBR.

epsilon6

Luckly, nothing had to be done. SBC lost power to a pairgain due to a power surge caused by some high voltage power lines touching/shorting out. SBC said that their generator did not transfer power, and because of union rules, they were not allowed to start their generator at the site (small little gas powered generator (you would imagine they would have a battery backup of some sort). The wind caused a small fire, but nothing that bad. We lost power for about 30 minutes, but thankfully, our generators were gunning.

Actually, I work in Little Rock for the Little Rock Municipal Airport Commission (in, of course, Little Rock, AR).

After doing some research and analyzing the data, our T1 were enabled software wise in the switch, and the ALARM STATUS: RED meant there was a problem on their side. All is well now.

Ramjet

We have been having probs wi SBC and the union. It seems that there is some kind of stipulation about calling a tech out after hours. It's very hard to get a tech called out, then it takes them hours to show up at the site!!! OH WELL, as they say, "We are the phone company"

telecom116

One of the things I do is check out the Network Interface Device (smartjacks, NIDs, whatever you want to call them) at the telco demark. With most T1s or DDS circuits supplied by HDSL on one or two pairs the LEDs on these help out as much as anything. When I have had problems I have found the HDSL lights flashing off and on, or no indication at all on one or both pairs. When telco tells you its your equipment, but when you can say, "Your telco interface is completely dark," it tends to put it back onto them real quick.

John_In_Dakota

Red alarm: far end problem
Yellow alarm: in house problem

__________________
Fellas', I need more Cow Bell!