Using the Loop Limit Feature Node Generates a Fatal Engine Error if Configured for 0 Loops
(Doc ID 1916027.1)
Last updated on MARCH 27, 2023
Applies to:
Oracle Communications Network Charging and Control - Version 4.3.0 to 6.0.1 [Release 4.3 to 6.0]Oracle Communications Convergent Charging Controller - Version 6.0.0 to 6.0.1 [Release 6.0]
Information in this document applies to any platform.
Symptoms
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C), the Loop Limit feature node is described in the help as accepting values from 1 to 1000 for the number of loops. However the edit feature node screen allows a value of 0 to be saved. When ACS processes this feature node with this value set to 0, it generates a fatal error similar to this:
and the call will fail.
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 |