SCP Arms o-BCSM Events in requestReportBCSM when IDP eventTypeBCSM is termAttemptAuthorized
Last updated on JULY 26, 2017
Applies to:Oracle Communications Network Charging and Control - Version 4.4.0 to 5.0.2 [Release 4.4 to 5.0]
Information in this document applies to any platform.
In all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) up to and including 5.0.1, Roaming Mobile Originating (MO) calls are configured to use Reoriginating Application (RAP), the following will happen:
- Initial Detection Point (IDP) comes in with eventTypeBCSM: termAttemptAuthorized.
- The Mobile Switching Center (MSC) expects a requestReportBCSMEvent arming t-BCSM events, but the Service Logic Controller (SLC) arms originating-BasicCallStateModel (o-BCSM) events.
- The MSC replies with an unexpectedDataValue error
This can be witnessed in snoop traces:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms