PRI channel going into lookout

[lamasu]

Hello friends,

Need your input. I have a PRI (loop 29), about 6 or 7 times a day, I get an error (err 93xx 29 x). I looked it up and it said that channel (x) went into lockout and x changes all the time. Sometimes it is channel, 2,8,22...etc. There is no consistency as to the time or channel. Any thoughts...

Thank you.

 

[3tdp33ler]

IMHO this can be a result of some d-channel problems:
the M1 waits for some d-channel message for a while, a remote side does not send the message, a b-channel goes into lockout.
Try to monitor and analize the d-channel messages related to lockouted channels.

 

[johnpoole]

1st post is right, another thing to check would be ld 96 stat serv. those service msgs may need to be on, or mya be on and need to be off, trmb yes or a pni number on a route that is not matched on both ends can cause that problem. pni needs to be blank if that pri is not internal, ie tie to another merridian. lockout usually means the d didn't see a clean rls, enl msgi x and enl msgo x in ld 96 will allow you to capture the dch msgs and maybe see the problem. do these channels rls after a short time or do you have to dsch x x ench x x?

john poole
bellsouth business
columbia,sc

 

[lamasu]

Thank you friends. John, I did a stat serv in 96 and both my local PRI's are DSBL and both my long distance PRI's are ENBL. (The channels do release after they go into lockout shortly after)

 

[johnpoole]

you might try

ld 96
enl serv x on the d and see waht that does, it really depends on the service msg status on the other end, but if i have problems of that nature i usually at least give that a once over to see if it helps..

john poole
bellsouth business
columbia,sc

 

[jhenley]

I had channels going into lockout err9032. Channels stayed in lockout until an incoming call hit the channel. It ended up being a patch for the switch.