PRI Alarms

[FortKnox]

What do these alarms mean? I am not familiar with the "SGR"

01C12 UDS1-BD n WARNING 05/01/12:28 00/00/00:00
2 ISDN-SGR n WARNING OUT 05/01/12:28 00/00/00:00
2 ISDN-SGR n WARNING OUT 05/01/12:28 00/00/00:00
SYNC n WARNING 05/01/12:28 00/00/00:00
SYNC n WARNING 05/01/12:28 00/00/00:00
2 ISDN-SGR n WARNING OUT 05/01/12:30 00/00/00:00

 

[irisngen]

the circuit could be down, status signal group 2, what is the status?

 

[mikeydidit]

Is it showing your signaling group as out of service. Do a status on it. It will show the same thing. You need to get your D signaling channel back up for that group.

"Wise men speak because they have something to say; Fools because they have to say something."
(Plato)

 

[irisngen]

test board 1c12, what test is it failing?

 

[phoneguy55]

I don't think the circuit is down. I have seen this before. There is a problem with the clocking that you are recieving from your service provider. That is causing your sync warning and the warning on your signaling group. As long as it is not service effecting, give it some time, the alarm should clear itself.

 

[irisngen]

True, but with the signal group in a warning state, the d channel could still be out. if he/she send us the "test board 1c12" screen & the status of the signal group we could know further.

 

[phoneguy55]

your right. test board will tell us more.

 

[FortKnox]

My circuit is still down.

stat sig 2

Port: 01C1224 Level 3 State: out-of-service

I did a busy/release on the trunk...no fix.


test board 01c12 Page 1

TEST RESULTS

Port Maintenance Name Alt. Name Test No. Result Error Code

01C12 UDS1-BD 138 FAIL
01C12 UDS1-BD 139 PASS
01C12 UDS1-BD 140 PASS
01C12 UDS1-BD 141 PASS
01C12 UDS1-BD 142 PASS
01C12 UDS1-BD 143 PASS
01C12 UDS1-BD 144 PASS
01C12 UDS1-BD 145 PASS
01C12 UDS1-BD 146 PASS
01C12 UDS1-BD 1227 ABORT 1951
01C1201 ISDN-TRK 17/01 36 PASS
01C1201 ISDN-TRK 17/01 255 FAIL 8
01C1201 ISDN-TRK 17/01 256 ABORT 1113
01C1201 ISDN-TRK 17/01 257 ABORT 1116
01C1202 ISDN-TRK 17/02 36 PASS
01C1202 ISDN-TRK 17/02 255 FAIL 8
01C1202 ISDN-TRK 17/02 256 ABORT 1113
01C1202 ISDN-TRK 17/02 257 ABORT 1116
01C1203 ISDN-TRK 17/03 36 PASS
01C1203 ISDN-TRK 17/03 255 FAIL 8
01C1203 ISDN-TRK 17/03 256 ABORT 1113
01C1203 ISDN-TRK 17/03 257 ABORT 1116
01C1204 ISDN-TRK 17/04 36 PASS
01C1204 ISDN-TRK 17/04 255 FAIL 8
01C1204 ISDN-TRK 17/04 256 ABORT 1113
01C1204 ISDN-TRK 17/04 257 ABORT 1116
01C1205 ISDN-TRK 17/05 36 PASS
01C1205 ISDN-TRK 17/05 255 FAIL 8
01C1205 ISDN-TRK 17/05 256 ABORT 1113
01C1205 ISDN-TRK 17/05 257 ABORT 1116

....and so on for the rest of the channels.

 

[1a22ip]

Try to busy and release port 01C1224. this might kick the D-channel in the butt. Has there been a change to the trunk group lately? It sounds like the D-channel is not talking.

Hope this helps
ED

1a2 to ip I seen it all

 

[phoneguy55]

If the circuit is down. Open a ticket with the service provider.

 

[mikeydidit]

You can also pull the board out, let it set for about 30 seconds, and then reseat it. Sometimes that will get the link/board to come back up. If not, then like phoneguy55 said, call your provider and have them do a tech dispatch.

"Wise men speak because they have something to say; Fools because they have to say something."
(Plato)

 

[FortKnox]

Called Qwest, they can loop the smartjack, they say its on our end. No problem with our other PRI's.

There was a Avaya tech out there yesterday to replace the netcon board, he couldnt get the new up, so he just put the old one back in. As far as I know, thats all that has changed.

I have busy/released the trunk and just the signal group.

How do I tell where the clocking/sync is coming from? Can I change its clocking source? If I have another Qwest PRI, can I move my D-channel to one of the other PRI's?

 

[irisngen]

i found that failing test 138 may be your connection is unplugged, or CSU is bad. Test 139 is no signal from carrier. if you can unplug from the vendors jack & place a loop back plug on your cable, then status again. the trunk group b channels should come in service, this way you know it's a vendor issue.

 

[FortKnox]

Well, I started the day by calling Qwest...as usual, its my problem, they can loop to the smartjack etc...you know the song.

After much hairpulling, Qwest was called again.

At 12:28am this morning they randomly decided to busy out our PRI and they turned it back up, and of course everything started working again.

Less than a month ago we couldnt place any calls on our Qwest dedicated. We would get the solid tone for putting in our l/d pac code (service provided by Qwest) and they kept saying 'we're not even getting the digits from you' and I said 'bs, you are getting digits b/c I get a PAC tone prompt.' Anyway, they ended up admitting that for 'some odd reason' our PAC code table was deleted from their system and it had to be rebuilt.

Been real happy with Qwest for about 7 years, but they have proactively been screwing up a lot lately.

 

[mikeydidit]

Glad you got it up and runing. I think we have all been through this reguardless of the provider.

"Wise men speak because they have something to say; Fools because they have to say something."
(Plato)

 

[irisngen]

next time, busy the board, reset the board then release the board. that sometimes "wakes" the circuit up. Glad everything is ok now.

 

[m4ilm4n]

Just to add my 2 cents - I got hit with the ISDN-SGR alarm just the other day (and read this thread - thanks gang!). Called out the circuit, it was good to the smart jack but dead to the CPE. After several late-nite hours of chasing it down, all I can say is:

Beware of the well-meaning tech with a pair of nips - they'd cut off our primary trunk's tail wire from the card cage to the riser pairs while doing maintenance.

 

[definityandcmuk]

put a loop back on the circuit see what happens

 

[gblucas]

I had a similar recurring problem with AT&T (SBC - AmeriTech, whoever they are today). I kept loosing the signal group on a PRI circuit. I thought that it was a Telco issue for sure, after I had swapped out the DS1 board and CSU and it came back up. Telco said that it was my equipment, and Avaya said that it was Telco. The problem would happen about 2 or 3 times in 4 to 6 weeks and then go away for 3 or 4 months, then we would have problems again. Avaya finally admitted that there might be a problem with V11, so the upgraded the PBX to V12 (CM2.1). I still ended up with the problem. No help at all. The sight was remote, so the office manager would just pull the DS1 card to reset it, if she was unable to reach anyone. It just happened to be an inbound Toll Free circuit, so the only way that we knew it had gone down, was a client call the local number to tell us. It was very frustrating to say the least. This is still an ongoing problem, but it is someone elses now...

gblucas

 

[donbott]

How about AT&T's new IVR for trouble tickets?

DonBott