Unable To Convert Hex to Integer Using Copy Feature Node
(Doc ID 2310596.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Network Charging and Control - Version 6.0.1 and later
Information in this document applies to any platform.
On Oracle Communications Convergent Charging Controller(OC3C) Applications, 6.0.1 version, it is observed that one cannot use the Copy Feature Node to convert a hexadecimal string to an integer value.
Consider an example where one of the Simple Object Access Protocol (SOAP) endpoints the user communicate with expects to receive the Location Area Code(LAC) and Cell ID as part of the messaging. These fields need to be sent as their integer equivalents. There does not seem to be a way to be able to cast hexadecimal telephony digits to integers, however.
Here the user would have expected a Copy Feature Node(as shown below), when used to write from an NSTRING profile tag to an INTEGER profile tag, to do a hexadecimal conversion.
However it just writes a '0' as shown in the below sample debug logs.
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