1446 - XUDT UDT conversion failed
The conversion from XUDT to UDT (or UDT to XUDT)
failed, and the message was routed without the XUDT UDT conversion. Depending
on which features are applied after XUDT UDT conversion, other processing of
the message may occur after the failed XUDT UDT conversion.
Example
0018.1446 CARD 1103,A INFO XUDT UDT conversion failed
SIO=03 OPC=001-001-001 DPC=002-002-002
SCCP MSG TYPE=04
CDPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=250 NP=04 NAI=010 ADDR=123456789012345678901
PC=003-003-003 SSN=005
CGPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=100 NP=07 NAI=012 ADDR=012345678901234567890
PC=001-001-001 SSN=004
LSN=ABCD123 GTTSET=3 203 46
Report Date:10-06-14 Time:16:20:19
Legend
- ADDR
- Address
- CDPA
- Called party address
- CGPA
- Calling party address
- DPC
- Destination point code
- GTI
- Global title indicator
- GTTSET
- GTT Set Index
- LSN
- Linkset name. The name must be unique.
- MSG TYPE
- Message type
- NAI
- Nature of address indicator
- NI
- Network indicator value
- NP
- Numbering plan
- OPC
- Origination point code
- PC
- Point code for the SS7 end user (OPC).
- PCI
- Protocol control information
- RI
- Routing indicator
- SIO
- Service information octet
- SSN
- Subsystem number
- SSNI
- Subsystem number indicator
- TT
- Translation type
Alarm Level: No alarm condition. The message is informational only.
Recovery
Refer to the following to correct the problem:
- Database Administration Manual - Global Title Translation
- The
ent/chg/rtrv-dstn
commands in the Commands Manual