The SMINAPCA Interface Needs to pass the MCC/MNC from the CellIdOrLAI It Receives to Slee_acs
(Doc ID 2862396.1)
Last updated on APRIL 18, 2022
Applies to:Oracle Communications Network Charging and Control - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The SM Inap Call Agent (SmInapCA) interface needs to pass the MCC/MNC (Mobile Country Code/Mobile Network Code) from the cellIdOrLAI it receives to slee_acs
The SMINAPCA allows Convergent Charging Controller Documentation (OC3C) to support CAMEL Application Part version 1(CAP1) for voice roaming call control, and by extension, pre-paid charging of CAP1 calls.
Currently the SMINAPCA can read MNC/MCC data from the cellIdOrLAI field in incoming InitialDP messages, but does not transfer this detail to slee_acs in the CAP2+ InitialDP it creates.
It is required that the MNC/MCC transferred to slee_acs so that customer can pass it on to ECE so that ECE can rate CAP1 roaming calls based on MCC/MNC
a. Set up a Service Logic Execution Environment(SLEE) configuration with both the SMINAPCA and slee_acs configured. SMINAPCA should be configured to send traffic to slee_acs.
b. Send a CAP1 Intial Detection Point (IDP) to the SMINAPCA. this can be done with a slpit script by setting the appContext field in the initialDP message to be "0,4,0,0,1,0,50,0", and sending it to the service key used by the SMINAPCA.
The CAP1 roaming agent (SMINAPCA) is specifically designed for CAP1 roaming support, and prepaid charging is generally charged by MCC/MNC. The CAP1 roaming agent is not performing its complete function if it is not passing on MCC/MNC for pre-paid charging.
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