DAP SendRequest Feature Node is Failing to Send Out Empty Value Strings
(Doc ID 1980290.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 5.0.2 [Release 4.3 to 5.0]
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) up to and including 5.0.2, the Data Access Pack (DAP) SendRequest Feature Node (FN) fails if an attempt is made to send an empty/NULL string out based on the DAP template.
It does not matter whether the source profile tag does not exist, whether it is empty, or whether you set it to an empty value. In all cases, the behavior is exactly the same.
The DAP SendRequest FN rejects any empty value:
sendRequest.cc 136  dapMacroNodes Asked to exit down branch Error
sendRequest.cc 138  dapMacroNodes FinalBranch not set, exiting down requested branch
sendRequest.cc 1351  dapMacroNodes now leaving state 6: following branch 5
It is expected that DAP should support empty values for string parameters, so it should allow this.
Note that profile notifications, i.e. messages generated on the Service Management Service (SMS), do not have this limitation. There, this works just fine, and the string parameters will have an empty value in the outgoing message.
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