TRUNKS IN COMBO CARD LOCK UP NEEDS REBOOT TO CLEAR

[mancom]

I am receiving this error message on a IP 500v2 rel 9.1.6 4 modem lines from timewarner all lock up. no reason. reboot brings the lines back. any thoughts, Cable dialtone replaced modem 3x, not sure if the ATM4Uv2 should be replaced? any thoughts would be appreciated. Thanks

system trace
13:38:43 277556633mS PRN: ATM4Uv2 DSP 0: ReadSiLabsRegister - interface not ready
13:38:43 277556634mS PRN: ATM4Uv2 DSP 0: ReadSiLabsRegister - interface not ready
13:38:43 277556634mS PRN: ATM4Uv2 DSP 0: ReadSiLabsRegister - interface not ready
13:38:43 277556637mS PRN: ATM4Uv2 DSP 0: ReadSiLabsRegister - interface not ready
13:38:43 277556637mS PRN: ATM4Uv2 DSP 0: ReadSiLabsRegister - interface not ready
13:38:43 277556637mS PRN: ATM4Uv2 DSP 0: ReadSiLabsRegister - interface not ready
13:38:43 277556638mS PRN: ATM4Uv2 DSP 0: ReadSiLabsRegister - interface not ready
13:38:44 277557505mS ATMChannel: [1] CMLinkLayer Tx: 'Blocked'
13:38:44 277557505mS ATMChannel: [1] CMLinkLayer Tx: 'CmLlMsgLineDown'
13:38:44 277557505mS ATMChannel: [3] CMLinkLayer Tx: 'Blocked'
13:38:44 277557505mS ATMChannel: [3] CMLinkLayer Tx: 'CmLlMsgLineDown'
13:38:44 277557506mS ATMChannel: [4] CMLinkLayer Tx: 'Blocked'
13:38:44 277557506mS ATMChannel: [4] CMLinkLayer Tx: 'CmLlMsgLineDown'
13:38:44 277557506mS ATMCMLine: [1] CMLinkLayer Rx: 'Blocked' callid=(lid=1, id=0, in=1)
13:38:44 277557506mS ATMCMLine: [1] StateChange Idle->DiscInd
13:38:44 277557507mS ATMCMLine: [1] CMLinkLayer Rx: 'CmLlMsgLineDown' callid=(lid=1, id=0, in=1)
13:38:44 277557508mS ATMCMLine: [3] CMLinkLayer Rx: 'Blocked' callid=(lid=0, id=0, in=1)
13:38:44 277557508mS ATMCMLine: [3] StateChange Idle->DiscInd
13:38:44 277557508mS ATMCMLine: [3] CMLinkLayer Rx: 'CmLlMsgLineDown' callid=(lid=0, id=0, in=1)
13:38:44 277557509mS ATMCMLine: [4] CMLinkLayer Rx: 'Blocked' callid=(lid=0, id=0, in=1)
13:38:44 277557510mS ATMCMLine: [4] StateChange Idle->DiscInd
13:38:44 277557510mS ATMCMLine: [4] CMLinkLayer Rx: 'CmLlMsgLineDown' callid=(lid=0, id=0, in=1)
13:38:44 277557611mS ATMChannel: [2] Sloppy timeout(500ms)
13:38:44 277557611mS ATMIO: [2] TRUNK RELEASE (no line dropped)
13:38:44 277557611mS ATMChannel: [2] StateChange Releasing->Idle
13:38:44 277557611mS ATMIO: [2] ECHO CANCELLATION OFF
13:38:44 277557611mS ATMIO: [2] BLOCK FORWARDING OFF
13:38:44 277557611mS ATMIO: [2] CLI DETECTION ON, EQUALISER OFF
13:38:44 277557612mS ATMChannel: [2] CMLinkLayer Tx: 'Idle'
13:38:44 277557612mS ATMCMLine: [2] CMLinkLayer Rx: 'Idle' callid=(lid=0, id=0, in=1)
13:38:44 277558505mS ATMChannel: [2] CMLinkLayer Tx: 'Blocked'
13:38:44 277558505mS ATMChannel: [2] CMLinkLayer Tx: 'CmLlMsgLineDown'
13:38:44 277558505mS ATMCMLine: [2] CMLinkLayer Rx: 'Blocked' callid=(lid=0, id=0, in=1)
13:38:44 277558506mS ATMCMLine: [2] StateChange Idle->DiscInd

 

[critchey]

There is a PSN out for "clicking" on lines for any cards using an ATM4 V2 card on newer control units (PCS19 or higher). I have seen it go beyond just the clicking, also causing static and sometimes locking up lines as you described. You can try moving the cards to slots 3 and 4 to see if that helps. You could also try using a V1 combocard and see if that resolves the issue since it seems to only be with V2 ATM4s.

 

[Telecomboy]

I have this happening at a client. PCS 19 with a combo v2. It is clicking though, not locking up. Tried moving to slot 3 and 4 with the same results. I am going to swap out the ip500v2 with a lower pcs to see if that resolves it.

 

[mancom]

Thank you, We don't have clicking, just heavy static, then all lines lock up. I was thinking of moving them up to 9.1.8. Also another thought was to locate an older combo card.

 

[emmitt2727]

I have been battling a variation of this too. Calls answered by embedded AA and disconnected before a choice is made hang. If the call passes to a phone, it drops when they hang up. I have replaced the combo card and the issue goes away. Every call before failed every call after worked. Lasted 3 months and then returned. I put in another combo card, same results. This time I put in some loop current regulators to see if that is causing the issue. Frustrating issue for sure.

 

[amriddle01]

Yours is lack of programming, not an issue, the provider needs to setup disconnect clear/supervision

 

[mancom]

It is really frustrating. We do have disconnect/clear box checked and set at 500ms(default). System monitor does report "sloppy disconnect" times up to 2000ms before lock up.
What would you suggest setting it to, 400ms?

 

[emmitt2727]

amriddle01 we tested the lines to make sure we are getting disconnect from the provider, and we get it on all the lines.

 

[amriddle01]

You checked with a multimeter? Did you alter your system settings to approx. 150ms lower than the providers timings?

 

[mancom]

yes, that is our decided next step. we will check with the meter, and lower the disconnect setting down 150ms. hopefully that will do the trick.
thanks so much!