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, 2015

Applies to:

Oracle Communications Network Charging and Control - Version 4.4.0 and later
Information in this document applies to any platform.


On Oracle Communications Network Charging and Control (OCNCC/NCC), 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:



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