My Oracle Support Banner

Understanding the Network Charging Control (NCC) SLEE "check" Command Output and Reported Usage of SLEE Resources (Dialogs, Events and Calls) in Determining Call Leaks (Doc ID 1289659.1)

Last updated on JULY 22, 2019

Applies to:

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


The aim of this bulletin is to enable administrators of the Oracle Communications Network Charging Control (NCC) solution to better understand the SLEE (Service Logic Execution Environment) check command output and its reported usage of internal SLEE resources: Dialogs, Events and Calls.  Further discussion is made on how monitoring of the check output can be used to help identify service affecting call leaks.


The NCC SLEE used by the Service Logic Controllers (SLC - legacy term UAS (Universal Application Server)) and/or Voucher Wallet Servers (VWS - legacy term UBE (Universal Billing Engine)).


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
 SLEE Resource Allocation
 SLC SLEE Resource Usage and Detecting Call Leaks
 So what is normal for the SLC check output?
 What is the difference between DEAD and ACTIVE SLEE Calls?
 What if I find my SLEE resources are scarce?
 VWS SLEE Resource Usage
 Monitoring SLEE Resources Trends

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.