DAP Request Feature Node Is Not Able To Identify The Timeout From Destination ASP (Doc ID 3068554.1)

Last updated on JANUARY 27, 2025

Applies to:

Goal

In Oracle Communications Convergent Charging Controller (OC3C) version 15.0.0.0.0, the Data Access Pack Request (DAP2) feature node cannot distinguish timeouts from the destination Application Service Provider (ASP).
When OC3C uses the DAP2 feature node to send a request to a destination module, it should identify scenarios where the request successfully reaches the destination, but no response is received within the expected timeframe.

Currently, the DAP2 feature node categorizes such timeout cases under the generic "Error" exit, which is also used for other error scenarios.
To address this, a flag or variable is needed to differentiate timeout cases from other errors. Is there a solution or workaround available for this requirement?

Solution

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