My Oracle Support Banner

DCA Unable To Decode "Address" AVP With Address Family E.164 (Doc ID 2648359.1)

Last updated on MARCH 13, 2020

Applies to:

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

Symptoms

On Oracle Communications Network Charging and Control (NCC) 12.0.2.0.0 version,

ACTUAL BEHAVIOR
----------------------------

The Short Message Service (SMS) integration over diameter is providing location information using the 3GPP parameter Originator-SCCP-Address Attribute-Value-Pair (AVP). The specification indicates the encoding is as follows:

The Address Type discriminator in RFC 3588 [401] is set to value 8, E.164, and the address information is UTF8 encoded.

So, for an address of "399999999" for example, the encoded value would be 00083339393939393939 in hex. However, NCC fails to decode this message, treat this as corrupt and throws the below Error:


EXPECTED BEHAVIOR
--------------------------------

The PICS lists the AVP as "compliant by configuration" so it should be possible, it certainly works if the IPv4 address type discriminator is used.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.