The SLEE.cfg Parser Silently Ignores Wrong Syntax for Numerical and Hexanumerical Variables and Applies Wrong Values

(Doc ID 1451218.1)

Last updated on SEPTEMBER 16, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 2.2.0 to 4.4.1 [Release 2.2 to 4.4]
Oracle Solaris on SPARC (64-bit)



The symptoms and impacts of this problem may be various in the way that wrong SLEE.cfg numerical values will be passed to the SLEE.  An full list of numerical values can be found in the Network Charging and Control (NCC) documentation, please read:

SLEE Technical Guide - Chapter : Configuring the SLEE - Modifying SLEE.cfg

Please read the following document to learn how to download NCC documentation:

How to Download Oracle Communications Network Charging and Control (OCNCC/NCC) Documentation

Some of the most common (and probably the most important) impacted variables are :

The MAX* values sort of define how much processing will be possible into the SLEE at any time.

The SERVICEKEY links the incoming message to the Service or the Interface, it is an essential element to be able to route the incoming messages to the right service or interface inside the SLEE.

General description

Two parsing issues have been detected:

Real life examples


This problem impacts all version of the NCC software until the future 5.0 version.


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