ERR9032: channels locking out persistently

[hartburn]

I have looked in related threads but cannot see anything which explains or resolves this issue for me.

Opt. 61C
We have two PRI channels which keep locking out - always the same two channels (24 & 26). If re-enabled, they lockout almost immediately. The channels never enable automatically.

We also have a TN which was on the last successful call on ch26 which cannot now be released from 'Busy', despite DISU and ENLU commands.

I have seen a suggestion to try setting the SERV setting in LD96 to ENBL (it is currently DSBL), but do not want to do this while there is traffic in case it causes problems, as it can only be disabled when the DCH is disabled. I will wait until out of hours.

In the meantime, does anyone know where I should be looking to resolve this? Our maintainer happily lays this at the circuit provider's door and vice versa.

Thanks

Here is the DCH info:

PRI2 LOOP 6 - ENBL
REF CLK: ENBL
TRACKING
SERVICE RESTORE: YES
ALARM STATUS: ACCEPTABLE
CH 01 - IDLE DID VOD * CH 02 - IDLE DID VOD *
CH 03 - IDLE DID VOD * CH 04 - IDLE DID VOD *
CH 05 - IDLE DID VOD * CH 06 - IDLE DID VOD *
CH 07 - IDLE DID VOD * CH 08 - IDLE DID VOD *
CH 09 - IDLE DID VOD * CH 10 - IDLE DID VOD *
CH 11 - IDLE DID VOD * CH 12 - IDLE DID VOD *
CH 13 - IDLE DID VOD * CH 14 - IDLE DID VOD *
CH 15 - BUSY DID VOD * CH 16 - IDLE DID VOD *
CH 17 - BUSY DID VOD * CH 18 - BUSY DID VOD *
CH 19 - BUSY DID VOD * CH 20 - BUSY DID VOD *
CH 21 - IDLE DID VOD * CH 22 - BUSY DID VOD *
CH 23 - BUSY DID VOD * CH 24 - LCKO DID VOD *
CH 25 - BUSY DID VOD * CH 26 - LCKO DID VOD *
CH 27 - IDLE DID VOD * CH 28 - BUSY DID VOD *
CH 29 - BUSY DID VOD * CH 30 - BUSY DID VOD *
CH 31 - DCH 6

Here are the messages from LD96

DCH 6 UIPE_OMSG CC_SETUP_REQ REF 00003B5D CH 6 26 TOD 10:59:22
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5546 NUM PLAN: E164

CALLED #:1320207xxxxxxx NUM PLAN: E164

DCH 6 UIPE_OMSG CC_SETUP_REQ REF 00003B5E CH 6 24 TOD 10:59:22
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5546 NUM PLAN: E164
CALLED #:1320207xxxxxxx NUM PLAN: E164

ERR9032 6 26 10:59:22 8/10/2008

 

[phonz1]

You have to pursue this with the Telco, they have 2 bad channels

 

[trvlr1]

We had similar problems on a system that is no longer in service now. I agree that the telco is the first place to look, but I am not sure you will get too far there, we never did. In the case of the phones going busy, we found the only way to correct that was to nul all appearances of the number on all phones, then program them back. I personally thought this was probably happening when one particular number or place was being called, but we were unable to track that down or get any good help from the specific person that repeatedly had the issue.

 

[hartburn]

OK, I will take it up again with the telco.

trvlr1 - thanks. I outed the phone then reinstated a copy on the TN. All ok there as a result.

Now just waiting to see which TN's have locked out this morning after grabbing those two bad channels.

If I get any insights from the telco i will put them up here.

Thanks again

 

[hartburn]

Fianlly got the telco to swap the card in their exchange and everything has been stable since (fingers crossed).

Thanks again for the advice.