Wrong Content For FCI Component In Response Message Sent To MSC In Case Of Camel Roaming Call
(Doc ID 2703963.1)
Last updated on FEBRUARY 11, 2022
Applies to:
Oracle Communications Network Charging and Control - Version 12.0.2.0.0 and laterInformation in this document applies to any platform.
Goal
On Oracle Communications Network Charging and Control (OCNCC/NCC) 12.0.2 environment which is integrated with external online charging system (OCS), an InitialDP message is sent to slee_acs for a Camel v1 roaming call received by m3ua_if.
A CCR-I(Credit Control Request - Initial) message is sent to external OCS, which responds with a CCA-I(Credit Control Answer - Initial) message containing "PS-Free-Format-Data" AVP (Attribute Value Pair) having a value like [FCI]xxxxx.
As per current implementation in NCC (see ccsConcept=acsTariffCode feature), when "PS-Free-Format-Data" AVP contains '(FCI)' or '[FCI]' or '<FCI>' prefix, the prefix is removed and rest of string is set as FurhishChargingInformation(FCI) by copy one-to-one as fCIBillingChargingCharacteristics.
The TCAP message sent by m3ua_if to MSC(Mobile Switching Centre) contains a FCI component having xxxxx string copied as fCIBillingChargingCharacteristics.
This is causing MSC to abort the call, as it expects a freeFormatData parameter under fCIBillingChargingCharacteristics.
See call flow in the below picture:
According to standard 3GPP TS 29.078:
- fCIBillingChargingCharacteristics:
This parameter contains the following parameters;
- fCIBCCCAMELsequence1:
This parameter contains the following parameters;
- freeFormatData:
This parameter contains free-format billing and/or charging characteristics;
- partyToCharge:
This parameter indicates the party to bill and/or charge;
- appendFreeFormatData:
This parameter indicates whether previous FurnishChargingInformation free format data is appended or overwritten. Refer to 3GPP TS 23.078 [7] for details on the usage of this parameter.
How to configure NCC in order to send FCI component in the response message as it is expected by MSC, and as recommended by 3GPP TS 29.078 standard?
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 |