Nortel 7.5 CS1K QSI QSIG PRI tie line to Avaya CM 5.2receiving excessive DCH055 and DCH054 messages

[McVoIPin]

I'm hoping someone can help with an issue we are having. About 2 weeks ago we had a double rectifier failure on Verizon's MUX and when it was brought back up one of our tie lines have been giving us excessive DCH055 & DCH054 messages on our Nortel PBX. Nothing has changed in programming ans this span has been up for years. In LD 60 when you do a LCNT on the loop, it shows no errors on the counters. I had Verizon run test patterns after hours on the circuit with no findings on their end. Also had a Verizon tech out to test the cicuit and replace the Smart Jack with no change. I replaced the T1(MM710B) card on the Avaya CM and even moved it to another slot. I also moved the MSDL port to another card on the Nortel side thinking the outage may have impacted that (couldn't bring down and FDL MSDL card because it's a 4 port card with 3 other circuits on it). I even had my vendor out with a T-BERD and can not find any errors on both ends when the problem occurs. During the day during heavy traffic the alarm occurs approx. every 7-10 mins but during the night with lesser traffic it can go an hour without an error. It's almost like a buffer is filling up and then dropping the DCH but re-establishing seconds later. I'm running out of options. Any thoughts? Below is the release of our Nortel PBX and PEPs whioh I know are a little behind.

VERSION 3621

System type is - Communication Server 1000M MG/CP PIV
CP PIV - Pentium M 1.1 GHz

RELEASE 7
ISSUE 50 Q +
IDLE_SET_DISPLAY
DepList 1: core Issue: 01(created: 2013-10-07 10:23:45 (est))

MDP>LAST SUCCESSFUL MDP REFRESH :2013-10-11 00:18:30(Local Time)
MDP>USING DEPLIST ZIP FILE DOWNLOADED :2013-10-07 10:23:45(est)
SYSTEM HAS NO USER SELECTED PEPS IN-SERVICE


LOADWARE VERSION: PSWV 100

INSTALLED LOADWARE PEPS : 0

ENABLED PLUGINS : 1

PLUGIN STATUS PRS/CR_NUM MPLR_NUM DESCRIPTION
-------------------------------------------------------------
501 ENABLED Q02138637 MPLR30070 Enables blind transfer to a SIP endpoint even if SIP UPDATE is not supported by the far end

A sample of DCH captures
DCH 56 UIPE_OMSG CC_FAC_REQ REF 0000BA06 CH 0 TOD 10:16:25 CK 73C09540

DCH 56 UIPE_OMSG CC_FAC_REQ REF 0000BA06 CH 0 TOD 10:16:25 CK 73C09541

DCH 56 UIPE_OMSG CC_SETUP_REQ REF 00001BAD CH 56 20 TOD 10:16:25 CK 73C099DC
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:8025770383 NUM PLAN: PRIVATE TON: ESN CDP
CALLED #:1428 NUM PLAN: PRIVATE TON: ESN CDP

DCH 56 UIPE_IMSG CC_PROCEED_IND REF 00001BAD CH 56 20 TOD 10:16:27 CK 73C09ABE

DCH 56 UIPE_IMSG CC_ALERT_IND REF 00001BAD CH 56 20 TOD 10:16:27 CK 73C09AE4

DCH 56 UIPE_OMSG CC_FAC_REQ REF 00001BAD CH 0 TOD 10:16:27 CK 73C09B60

DCH 56 UIPE_OMSG CC_FAC_REQ REF 00001BAD CH 0 TOD 10:16:27 CK 73C09BA0

DCH 56 UIPE_IMSG CC_SETUP_CONF REF 00001BAD CH 56 20 TOD 10:16:31 CK 73C0C0BE
PROGRESS: TERMINATING END IS NOT ISDN
CONNECT #:8011428 NUM PLAN: UNKNOWN TON: UNKNOWN

DCH 56 UIPE_OMSG CC_DISC_REQ REF 00001BA9 CH 56 22 TOD 10:16:33 CK 73C0D7CE
CAUSE: #16 - NORMAL CALL CLEARING

DCH 56 UIPE_OMSG CC_FAC_REQ REF 0000BA06 CH 0 TOD 10:16:39 CK 73C106BC

DCH 56 UIPE_OMSG CC_FAC_REQ REF 0000BA06 CH 0 TOD 10:16:39 CK 73C106BE

[highlight #FCE94F]DCH055 DCH: 56 RLS NO RESPONSE TIME: 10:16:47 6/02/2015

DCH054 DCH: 56 EST CONFIRM TIME: 10:16:53 6/02/2015[/highlight]
DCH 56 UIPE_OMSG CC_STATUS_REQ REF 0000BA06 CH 56 1 TOD 10:16:53 CK 73C1660C
CAUSE: #31 - NORMAL UNSPECIFIED
STATE:CALL ACTIVE

DCH 56 UIPE_OMSG CC_STATUS_REQ REF 00001BA3 CH 56 12 TOD 10:16:53 CK 73C1660D
CAUSE: #31 - NORMAL UNSPECIFIED
STATE:CALL ACTIVE

DCH 56 UIPE_OMSG CC_STATUS_REQ REF 00001B99 CH 56 15 TOD 10:16:53 CK 73C1660F
CAUSE: #31 - NORMAL UNSPECIFIED
STATE:CALL ACTIVE

DCH 56 UIPE_OMSG CC_STATUS_REQ REF 00001B36 CH 56 19 TOD 10:16:53 CK 73C16610
CAUSE: #31 - NORMAL UNSPECIFIED
STATE:CALL ACTIVE

DCH 56 UIPE_OMSG CC_STATUS_REQ REF 00001BAD CH 56 20 TOD 10:16:53 CK 73C16612
CAUSE: #31 - NORMAL UNSPECIFIED
STATE:CALL ACTIVE

DCH 56 UIPE_OMSG CC_STATUS_REQ REF 00001BAC CH 56 21 TOD 10:16:53 CK 73C16614
CAUSE: #31 - NORMAL UNSPECIFIED
STATE:CALL ACTIVE

DCH 56 UIPE_OMSG CC_STATUS_REQ REF 00001BAB CH 56 23 TOD 10:16:53 CK 73C16617
CAUSE: #31 - NORMAL UNSPECIFIED
STATE:CALL ACTIVE

DCH 56 UIPE_OMSG CC_SETUP_REQ REF 00001BAE CH 56 22 TOD 10:16:59 CK 73C19E01
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:8025770383 NUM PLAN: PRIVATE TON: ESN CDP
CALLED #:1787 NUM PLAN: PRIVATE TON: ESN CDP

DCH 56 UIPE_OMSG CC_DISC_REQ REF 00001BAC CH 56 21 TOD 10:17:05 CK 73C1C770
CAUSE: #16 - NORMAL CALL CLEARING

DCH 56 UIPE_IMSG CC_REJECT_IND REF 00001BAE CH 56 22 TOD 10:17:07 CK 73C1DDEE
CAUSE: #102 - RECOVERY ON TIMER EXPIRY


DCH 56 UIPE_OMSG CC_SETUP_REQ REF 00001BAF CH 56 22 TOD 10:17:09 CK 73C1F200
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:8025770383 NUM PLAN: PRIVATE TON: ESN CDP
CALLED #:4000 NUM PLAN: PRIVATE TON: ESN CDP

DCH 56 UIPE_OMSG CC_DISC_REQ REF 00001BAF CH 56 22 TOD 10:17:13 CK 73C204E3
CAUSE: #16 - NORMAL CALL CLEARING

DCH 56 UIPE_IMSG CC_RELEASE_CONF REF 00001BAF CH 56 22 TOD 10:17:13 CK 73C204FD

DCH 56 UIPE_OMSG CC_SETUP_REQ REF 00001BB0 CH 56 22 TOD 10:17:23 CK 73C25604
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:8025770383 NUM PLAN: PRIVATE TON: ESN CDP
CALLED #:2951 NUM PLAN: PRIVATE TON: ESN CDP

DCH 56 UIPE_IMSG CC_PROCEED_IND REF 00001BB0 CH 56 22 TOD 10:17:23 CK 73C256E9

DCH 56 UIPE_IMSG CC_PROGRESS_IND REF 00001BB0 CH 56 22 TOD 10:17:23 CK 73C25704
PROGRESS: CALL IS NOT END TO END ISDN



Can this patch be related?

MPLR31441
PRI2 loops do not always recover after a Call Server Initialization - DCH055 DCH: xxx RLS CTS DOWN is reported.
7.6