1225 - SCCP did not route - DPC OOS

This message indicates that SCCP did not route a message because the destination point code (DPC) was out-of-service (OOS). The message was discarded.

Example

station1234 99-08-30 16:28:08 EST EAGLE 35.0.0
0019.1225 CARD 1104,A SCCP did not route - DPC OOS
TRANSLATED PC=003-003-003 TRANSLATED SS=005
CDPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
TT=250 NP=04 NAI=010 ADDR=123456789012345678901
PC=003-003-003 SSN=005
CGPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
TT=100 NP=07 NAI=012 ADDR=012345678901234567890
PC=004-004-004 SSN=003
LSN=A1234567

Legend

ADDR

Address

CDPA

Called party address

CGPA

Calling party address

DPC

Destination point code

GTI

Global title indicator

MSG TYPE

Message type (for example, connection request, connection confirm, connection refused)

NAI

Nature of address indicator

NI

Network indicator value

NP

Numbering plan

OPC

Origination point code

PC

Point code

PCI

Protocol control information

RI

Routing indicator

SIO

Service information octet

SSN

Subsystem number

SSNI

Subsystem number indicator

TT

Translation type

TRANSLATED PC

Translated point code

TRANSLATED SS

Translated subsystem

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=xxxx:port=b

   where xxxx is the card location.

   Example of the output:

   RLGHNCXA03W 00-09-27 17:00:36 EST  EAGLE 35.0.0
   SLK     LSN          CLLI         PST           SST        AST
   1201,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.

   Following is an explanation of the UNAVAIL REASON codes:

   FL - The signaling link has a fault.

   NA - The signaling link is not aligned.

   LI - The signaling link has been inhibited locally.

   RI - 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 does not come up and links align, try first reseating the card, then replacing the card.

   Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

7. If the UNAVAIL REASON indicates a locally inhibited link, enter the unhb-slk command with the specified card location.
8. If the UNAVAIL REASON indicates a locally blocked link, enter the ublk-slk command with the specified card location.
9. 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).