Eagle: UIM 1223 - SCCP Did Not Route

Asset ID:	1-72-2386560.1
Update Date:	2018-04-17
Keywords:

Solution Type Problem Resolution Sure

Solution 2386560.1 : Eagle: UIM 1223 - SCCP Did Not Route - Bad Translation

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 46.0 and later
Tekelec

Symptoms

Customer complained that messages coming from the MSC having as destination a third party platform we're not routed by the STP and that UIM 1223 was received - "SCCP did not route - bad translation".

7863.1223 CARD 1305 INFO SCCP did not route - bad translation

SIO=83 OPC= xxxxx DPC= yyyyy

SCCP MSG TYPE=09

CDPA: NI=0 RI=0 GTI=04 SSNI=1 PCI=0

TT=000 NP=01 NAI=003 ADDR=111111111

PC=-------------- SSN=006

CGPA: NI=0 RI=0 GTI=04 SSNI=1 PCI=0

TT=000 NP=01 NAI=004 ADDR=222222222222

PC=-------------- SSN=008

LSN=lsnname GTTSETIDX=0

Report Date:18-04-13 Time:10:48:57

Changes

Cause

The STP received the message with the GT in a national format, which was not defined in the e164natl set table in the STP causing the translation to fail.

tekelecstp 18-04-13 13:25:21 HST EAGLE 46.5.0.0.1-70.39.1

rtrv-gta:gttsn=e164natl:gta=111111111

Command entered at terminal #20.

;

E2405 Cmd Rej: GTA/SADDR does not exist in any range

Trace info:

tekelecstp 18-04-13 13:34:50 HST EAGLE 46.5.0.0.1-70.39.1

MSU TRACE H'0038: Card=1305

Trace ID 8 Condition: (brief=Y, MSU size=173)

LOC= 1305

GT= 111111111

SI= 3

MODE= debug

Info: GTT FAILED: TRANS_ENTRY_NOT_FOUND-2

Solution

The solution was to define the 6391999xx range for GT translation in the e164natl table. After the definition, calls were OK and no more UIMs 1223 were received.

ent-gta:gttsn=e164natl:gta=111111111:egta=111111119:xlat=dpc:ri=ssn:pcn=xxxxx

Attachments

This solution has no attachment