1045 - SCCP did not route - DPC congested
The SCCP did not route a message because the destination point code (DPC) was congested. The message was discarded.
Example
This output indicates an error against the original
destination rather than the redirected destination.
RLGHNCXA21W 02-07-21 16:20:19 EST EAGLE 37.5.0
0246.1045 CARD 1101,A1 INFO SCCP did not route - DPC congested
OPC=1-200-2
TRANSLATED PC=5-038-6 TRANSLATED SS=202
CDPA LENGTH=019 MSG TYPE=04
CDPA: AI=05 PC=1-050-1 SSN=006 TT=007
ADDR=ABCDEF0123456789ABCDE
LSN=ABCD123
Report Date:02-07-21 Time:16:20:19
This alternate output includes the redirected destination and is
used when a redirected MSU encounters an error.
RLGHNCXA21W 02-07-21 16:20:19 EST EAGLE 37.5.0
0246.1045 CARD 1101,A1 INFO SCCP did not route - DPC congested
OPC=1-200-2
TRANSLATED PC=5-038-6 TRANSLATED SS=202
CDPA LENGTH=019 MSG TYPE=04
GTT on CdPA used MOSMSGTA=9193802053
CDPA: AI=05 PC=1-050-1 SSN=006 TT=007
ADDR=ABCDEF0123456789ABCDE
LSN=ABCD123
Report Date:02-07-21 Time:16:20:19
Legend
Alarm Level: No alarm condition. The message is informational only.
Recovery
This indicates an SCCP message was discarded due to
congestion at a distant node. Maintenance personnel should monitor the network
and verify the nodes congestion status changes to zero (no congestion).
Note:
A transfer controlled (TFC) should have been received on the link to indicate congestion to this node. When the congestion status changes, the congestion status indicator in the flow control messages indicates what message type priorities can be transmitted to the distant node. If the condition persists, follow normal company procedures in dealing with congestion at distant nodes.