How to Create a New smInapCA Instance to Trigger a Different SLEE Service Key
(Doc ID 2512514.1)
Last updated on MARCH 27, 2023
Applies to:
Oracle Communications Network Charging and Control - Version 5.0.2 and laterInformation in this document applies to any platform.
Goal
On Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), there is an optional control agent, smInapCA, which is a Customized Applications for Mobile networks Enhanced Logic (CAMEL) Application Part (CAP) version 1 (CAP1) Global Packet Radio Service (GPRS) gateway.
It sits between the Signalling Transport (SIGTRAN) interface and slee_acs and converts between Oracle's internal Intelligent Network Application Part (INAP) protocol and CAP1 for GPRS.
This article will explain how to create an additional instance of the smInapCA to trigger a different Service Logic Execution Environment (SLEE) Service Key (SK) in order to differentiate services in Advanced Control Services (ACS).
By triggering different ACS services, it is possible to run completely different Control Plans and offer completely different service logic.
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 |
| References |