Handshake Failure Between DAP and OSD over HTTPS
(Doc ID 2102903.1)
Last updated on DECEMBER 06, 2024
Applies to:
Oracle Communications Network Charging and Control - Version 5.0.3 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communications Network Charging and Control (OCNCC) Version 5.0.3, it is observed that the Secure Sockets Layer (SSL) handshake connection between Data Access Pack (DAP) and Open Services Development (OSD) fails when using HTTPS.
For example, we can use DAP to send a SOAP/XML request to the OSD interface, in order to do further processing to the originating control plan and to create a separate Event Detail Record (EDR) for later processing. Here the problem is that the OSD and DAP can talk to each other using Hypertext Transfer Protocol (HTTP), but when the HTTPS is introduced the handshake between DAP and OSD fails.
The dapIF debug reports the handshake failure as below:
Changes
Adding OSD as a DAP Application Service Provider (ASP).
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |