PRI Channels locking out

[kwoerner]

working on 2 PRI's connecting two 81C's. My problem is that the channels are going LCKD on one side and MBSY on the other. The channels have be outed and rebuilt. A day or so goes by and they go back out. An INI or sysload will clear them but then they go back out. I get this error message when they go.

PRI0101 loop ch c
"The B-channel (ch) is locked out because a RELCOMP or RELEASE message
has been received with one of the following cause (c) values: 82 =
channel does not exist 44 = requested
channel is not available 6 = alternate channel not acceptable"

Severity: Critical



I get a cause 44 after the loop and channel numbers. They are connecting two 81C's (CS1000M)one running 4.0 the other 3.0. Any thoughts?

 

[johnpoole]

post the route of at least one of those. that is a pretty standard tie trunk... couple of things i would check.. ld 96 stat serv. those may need to be toggled.. i run them on, but have had to turn them off to second party switches.. the other is pni number. they have to match and need to be entered in the cdb on both ends as well. another prompt that is good for that is trmb. that is best turned off. you don't usually need it unless your using a single voice mail. of course in the rdb supv needs to be no on both ndec and fdec on both ends.. that tells both switches to disconnect on station supervision.. ie the stations hang up and the trunk drops... all of that is thinking the lcnt tables on both ends are zero'ed out.. a clean pri is a must before you try software cure

john poole
bellsouth business
columbia,sc

 

[mluckie1]

Are you getting anyy ERR codes on those channels? There is a patch for LCKO of channels. I think it is P19572_1, can't say for sure but you may want to confirm this with your service provider. Also if you DSCH and ENCH does it go idle? Is it the same channel the goes to LCKO?

 

[johnpoole]

another thought. after you change or build a dch. you need to dis msdl x all, enl msdl x fdl to write those changes to the card.. to find which msdl your on. map dch, all commands being ld 96

john poole
bellsouth business
columbia,sc

 

[kwoerner]

DSCH and ENCH will make it idle but then a few minutes later it goes back to LCKD. After outing and rebuilding, channels will go LCKD a few days later. It is different channels that lock out not the same ones every time. I have two PRI's sharing one DCH. It seems to progress to 2 or 3 channels on each PRI then stops. After the 2 or 3 lock out it seems to stop locking out other channels. I have all the latest patches on both switches. Loaded them about a month ago.

 

[mluckie1]

Is the patch listed abouve one of them? Or is it just the Deplist that was updated. This is a seperate patch. Which side is going to LCKO rls 3 or 4? The reason the other side goes to MBSY is because it knows the other side is in LCKO.

 

[kwoerner]

I do have patch p19572_1 loaded. Rls 3 side says LCKO Rls 4 says MBSY. So your saying the side with LCKO is the one with the problem?

 

[mluckie1]

That's the side I would check. Is the patch in that system?

 

[johnpoole]

without a dch monitor you can't be sure. side b can lock out if side a does not ack that channel detail..

ld 96
enl msgi x
enl msgo x

lots of data, about a page per call...

john poole
bellsouth business
columbia,sc

 

[kwoerner]

That patch is not loaded on the switch with rls 3.0. That could be the culprit.

 

[mluckie1]

That's where I would start. Get the patch installed on that end. LCKO is usualy caused when a set or trunk doesn't hang up. Before running the monitoring of the Dchannel I would get the patch installed then see if the problem goes away. If it is still there then I would monitor the Dchannel. The problem is intermittent and you may need to collect alot of messages and then will need to isolate the time, exact time preferable, when it occured.

 

[kwoerner]

Thanks all!