1049 - SCCP did not route - SS not in MAP tbl

The SCCP did not route a message because the destination subsystem was not in the Mated Application (MAP) table. 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.1049    CARD 1101,A1  INFO      SCCP did not route - SS not in MAP tbl
             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.1049    CARD 1101,A1  INFO      SCCP did not route - SS not in MAP tbl
             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

ADDR

Address

AI

Address Indicator

CDPA

Called party address

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).

SS

Subsystem

SSN

Subsystem number

TT

Translation type

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

Recovery

1. If the subsystem indicated in the message is not a mated application to the EAGLE 5 ISS, no further action is necessary.
2. If the SCCP message should have been routed, use the ent-map command to add the subsystem number to the mated application (MAP) table.