DAP Real Time Wallet Notifications Fail with Exception "Notification value name too long, value = <NOTIFICATION_NAME> maximum size = 41"
(Doc ID 2045680.1)
Last updated on MARCH 02, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 184.108.40.206.0 [Release 4.3 to 12.0.0]
Oracle Solaris on SPARC (64-bit)
In all versions of Oracle Communications Network Charging and Control (NCC), Real Time Wallet Notifications (RTWNs) are used to notify subscribers of specific events such as expiry, recharges etc. which have taken place against their wallet.
NCC offers the ability to configure these RTWNs as either Short Message Service (SMS) templates or Data Access Pack (DAP) templates depending on how the solution is expected to fit into a network. More information on this is available in the Charging Control Services (CCS) User Guide.
When using DAP templates, a problem exists in version of NCC earlier than 220.127.116.11 where the RTWN can fail at runtime (ie. when it is triggered), due to the length of the configure RTWN name:
Creation of a new RTWN with an exceptionally long name.
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