1122 - LNP rcvd query with undefined TT/SERV

The LNP Query Subsystem received a message with an undefined Service. The Called Party Translation type in the incoming message determines the format of the MSU. This UIM can be issued when there is no LNP Service associated with the Translation Type of this MSU.

If the Translation Type of the MSU is provisioned as a Translation Type for LNPQS Service, the Eagle attempts to determine the actual LNP Service for this message by examining the OP CODE value. If the OP CODE does not match any supported by the Eagle Service (IN, AIN, IS-41), this UIM is issued.

This UIM can also be issued as a result of an error response from an end office because the Eagle LNP database response returned an LRN that was not provisioned in the end office.

Trace tools and/or the hex dump in the UIM can be used to determine the TCAP information. Note that the GTT data is not contained in the SCCP layer because the Eagle does not return this information in the LNP response to the end office.

Example

RLGHNCXA21W 00-04-18 19:00:11 EST EAGLE 31.3.0
0107.1122 CARD 1103,A1 INFO LNP rcvd query with undefined TT/SERV
          SIO=03 OPC=003-252-000 DPC=000-071-000
          CDPA: AI=10 SSN=05 TT=250
                 ADDR=ABCDEF1234567890ABCDE
          CGPA: AI=12 PC=001-001-001 SSN=002
          DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
                   2e cf 01 00 d0 02 83 01 f2 25 aa 0b
                   84 09 01 00 11 0a 19 49
          LSN=A1234567

Legend

ADDR

Address

AI

Address Indicator

CDPA

Called party address

CGPA

Calling party address

DATA

Hex dump of TCAP part of MSU

DPC

Destination point code

LSN

Linkset name. The name must be unique.

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. If the IN, AIN, IS-41, PCS 1900, or LNPQS LNP Query translation type has not been provisioned, it needs to be provisioned using the ent-lnp-serv command.

   If any of the above LNP Query Translation Types has not been provisioned, it can be changed using the chg-lnp-serv command.

2. If the Translation Type has been provisioned correctly, an SSP node in the network is using the wrong Translation Type or an invalid query.