Copying To Calling Logical Subscriber Causes Unterminated String From Normalisation (Doc ID 2290813.1)

Last updated on JULY 27, 2017

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.


On Oracle Communications Convergent Charging Controller(OC3C), 6.0.1 version, when using a Copy Feature Node to copy a value over the Calling Logical Number (for example a service handover or similar scenario), the copy succeeds, but a subsequent normalisation pass is triggered internally that removes the null termination from the string.

Consider an example, where the Copy node is configured as below. It copies Session Data / Outgoing Session Data / CC Pending Termination Number to Session Data / Incoming Session Data / CC Calling Logical Number.


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