No Parameters Filled in DAP Request for Empty Variables in XML Document
(Doc ID 2667113.1)
Last updated on FEBRUARY 24, 2021
Applies to:Oracle Communications Network Charging and Control - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC and NCC), starting with 12.0.2, there is a known issue with Data Access Pack (DAP) request sent to Application Service Provider (ASP).
According to NCC Documentation (Data Access Pack User's and Technical Guide) - DAP uses a template language to describe the format of the messages (requests) that are sent to ASPs. This template language controls variable substitution and repetition of subtrees.
There are two formats that variables can take in the XML document:
1 An empty XML element:
This is interpreted as a variable called phone_number
2 A specific format of text string:
This is interpreted as a variable called $phone_number.
In addition to user defined variables, there are several other variables which are substituted automatically by the DAP interface.
In the current scenario, parameters in DAP request to ASP are empty if an empty tag is used in templates.
A DAP Operation is defined like this:
... which means that the "anumber" and "bnumber" variables should be substituted with the values coming from Incoming or Outgoing Session Data (DAP Operation).
In turn, the request to ASP is empty for both anumber and bnumber:
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