How to Start osaChamScs Instance with Custom eserv.config Location?
(Doc ID 1392414.1)
Last updated on JANUARY 05, 2023
Applies to:
Oracle Communications Network Charging and Control - Version 3.1.0 and laterInformation in this document applies to any platform.
Goal
How to start the osaChamScs instance with custom eserv.config location?The OSA Gateway Client Interface allows proprietary ASPs to utilise the billing, account management and functionality of the Oracle Voucher and Wallet Server (VWS) using the interface defined in the 3GPP OSA/Parlay specifications.
The OSA specifications define an architecture that enables application service providers to make use of network functionality through an open, standardised interface API. The purpose of this interface is to shield the complexity of the network, its protocols and specific implementations from the client application.
The OSA CHAM (Charging and Account Management) gateway implements a subset of the OSA APIs for the Account Management and Charging Service Capability Features.
The OSA specifications define an architecture that enables application service providers to make use of network functionality through an open, standardised interface API. The purpose of this interface is to shield the complexity of the network, its protocols and specific implementations from the client application.
The OSA CHAM (Charging and Account Management) gateway implements a subset of the OSA APIs for the Account Management and Charging Service Capability Features.
Solution
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
| Goal |
| Solution |