My Oracle Support Banner

VWS Triggers to OSD Fail with Error "Got an error message as a response, errorCode=5" (Doc ID 2448081.1)

Last updated on JUNE 29, 2022

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC), Open Services Development (OSD) is a Simple Object Access Protocol (SOAP) server on the Service Logic Controllers (SLCs) that SOAP clients can trigger Control Plans (CPs) through.  On the Voucher and Wallet Servers (VWS'), the beServiceTrigger process is a SOAP client that can send requests to osdInterface typically for Real Time Wallet Notifications (RTWNs) or Control Plan Periodic Charges (PCs).

When osdInterface processes these requests, it may fail and report the following error:

As a result, an error is returned to beServiceTrigger and the triggering event is stored and retried after a configurable amount of time.  This cycle repeats forever.

Changes

 

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


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