Copying To Calling Logical Subscriber Causes Unterminated String From Normalisation
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.
Kindly note that here the copy succeeds, but as per the below debug, it is the post-copy normalisation that perturbs the string. Also this issue seems to occur with many of the Session CC fields, e.g. CC Calling Network Address etc.
Sample Debug Logs:
Here the de-normalisation is triggered internally, so it can not be avoided. This makes it impossible to copy to this field which is significantly impacting the ability to configure some services correctly.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms