SCCP CLDR Error cause type:1 value:3. How to analyze it? (Doc ID 1286824.1)

Last updated on APRIL 25, 2012

Applies to:

Oracle Communications Network Charging and Control - Version 2.4.0 and later
Information in this document applies to any platform.

Symptoms

The SUA stack running on an SLC can report following error which may need a bit of investigations to understand the meaning of it (slc1 and itp1 are machine names examples):

Dec 29 13:52:35 slc1 sua_if: [ID 839465 user.notice] sua_if(17918) NOTICE: {400023} sctp:itp_s1:15000:slc1_s1:14999: Received CLDR, source ri:gt
ai:7 ssn:12 pc:120 gt:{gti:4 tt:254 np:1 noa:3 450224}, destination ri:pc ai:5 ssn:12 pc:12684 gt:{gti:4 tt:254 np:1 noa:3 090727}, cause type:1 value:3



The document [SIGTRAN Alarms Guide (1.2-02.00).pdf] can give a good grasp on the issue, but without further details:

Cause:
"A SCCP UDTS, XUDTS, LUDTS or a SUA CLDR message has been received."

Resolution:
 " These may be expected occasionally, especially if a network is overloaded or unreliable. If large numbers of the messages are received, then  check your network for connectivity or congestion problems."



Therefore, symptoms are that we face some data not treated by the MSC.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms