SDK Example of Procedure/Method for Storing Call Context Leaks Memory (Doc ID 2221547.1)

Last updated on FEBRUARY 14, 2017

Applies to:

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

Symptoms

The Oracle Communications Network Charging and Control (NCC) Software Development Kit (SDK) is based on the NCC application programming interface (API) and allows you to create NCC components that satisfy customer-specific requirements that the NCC software does not address.

The service loader, which physically is a shared library that is loaded by slee_acs, is the part of Advanced Control Services (ACS) that is responsible for initializing the right service for a call and loading its control plan, profiles, and so on, if they are required.  A service loader, however, is not required to execute a control plan; it can perform all of the service control logic itself. A service loader also acts as a mediation layer between the inbound SLEE interface and the service. The service loader also performs the final manipulation of data that is returned to the network interface when a triggering interface sends back a network event.

In the examples provided as part of the SDK, functions to store and retrieve service data results in a memory leak for each call in the SDK library.

Changes

Install and use the NCC SDK.

Cause

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