DAP2 Node Causes Slee Crash When Provided Profile Tag is Empty
Last updated on MAY 12, 2014
Applies to:Oracle Communications Network Charging and Control - Version 4.4.0 and later
Information in this document applies to any platform.
slee_acs process on Service Logic Controller (SLC) dumps core file when DAP Request feature node is used in control plan to send PI SOAP command. For more information on DAP Request feature node and PI SOAP command, kindly consult DAP and PI technical guide in Network Charging and Control (NCC) documentation. To get NCC documentation, please refer to Article 1341844.1 "How to Download Oracle Communications Network Charging and control OCNCC/NCC)Documentation".
Back Trace of the core file looks as below.
For more information how to take back traces of core file kindly refer to KM 1368101.1 " Use GDB to Read a Core File and View Backtrace Information on a Solaris System".
Below are detailed steps to reproduce the problem:
1.) Create a sample control plan using DAP Request Feature node.
2.) Use DAP Request Feature node to send PI SOAP command. MSISDN argument for PI SOAP command is configured to use profile field named CC Extension digits 9 in profile block incoming data session.This is explained with sample configuration of DAP Request Feature node as below.
3.) On execution of the control plan if CC Extension digits 9 is empty (does not contain valid data) then slee-acs process will crash.
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