1044 - SCCP did not route - DPC OOS

The SCCP did not route a message because the destination point code (DPC) was out-of-service (OOS). 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.1044    CARD 1101,A1  INFO      SCCP did not route - DPC OOS
             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.1044    CARD 1101,A1  INFO      SCCP did not route - DPC OOS
             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:1

Legend

ADDR

Address

AI

Address Indicator

CDPA LENGTH

Called party address length

CGPA

Calling party address

DATA

Hex dump of TCAP part of MSU

DPC

Destination point code

LSN

Linkset name. The name must be unique.

MSG TYPE

Message type

OPC

Origination point code

PC

Point code for the SS7 end user (OPC).

SIO

Service information octet

SSN

Subsystem number

TT

Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

1. Check the route and linksets by entering the rept-stat-dstn and rept-stat-ls commands.
2. Verify the link status using the rept-stat-slk command.
   For example, enter:
   rept-stat-slk:loc=:port=b
   Example of the output:

   RLGHNCXA03W 00-09-27 17:00:36 EST  EAGLE 35.0.0
   SLK     LSN          CLLI         PST           SST        AST
   1203,B  nsp1         ls02clli     OOS-MT        Unavail     ----
      ALARM STATUS       =  No alarm
      UNAVAIL REASON     =  FL NA LI RI 
   Command Completed.

3. Check the UNAVAIL REASON field in the output of the rept-stat-slk command.
   UNAVAIL REASON codes:
   FL – The signaling link has a fault.
   NA – The signaling link is not aligned.
   LI – The signaling link has been inhibited locallyRI – The signaling link has been inhibited remotely.
   LB – The signaling link has been blocked locally.
   RB – The signaling link has been blocked remotely.
   FC – The signaling link is unavailable because of false congestion. RD (xx.xxx) – The signaling link is unavailable because of a restart delay to prevent signaling link oscillation. The number in parentheses indicates the amount of time, in seconds, remaining in the restart delay period. The link is restarted automatically after this amount of time has elapsed.
4. If the UNAVAIL REASON indicates an alignment problem or fault, activate a loopback using the act-lpb command, or use a physical loopback.
   (For a V.35, you must use an appropriate physical V.35 loopback.) If the signaling link aligns, contact the far-end to correct the problem.
5. If the UNAVAIL REASON still indicates an alignment problem or fault, check the status of the card by entering the rept-stat-card command for the specified card.
6. If the rept-stat-card command indicates a problem with the card, reset the card by entering the init-card command with the specified card location.
   If the card still does not align, try first reseating the card, then replacing the card. Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
   1. If the UNAVAIL REASON indicates a locally inhibited link, enter the unhb-slk command with the specified card location.
   2. If the UNAVAIL REASON indicates a locally blocked link, enter the ublk-slk command with the specified card location.
7. Otherwise, this indicates a failure at the distant node.
   Routing to this node has been halted as a result of network management. Maintenance personnel should be aware of the OOS condition, but no action is necessary. Monitor the links to the DPC and verify the DPC status changes to IS-NR (In-Service - Normal).