My Oracle Support Banner

SCP Arms o-BCSM Events in requestReportBCSM when IDP eventTypeBCSM is termAttemptAuthorized (Doc ID 1477657.1)

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.

Symptoms

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:

IDP:

Camel
    invoke
        invokeId: present (0)
            present: 1
        opcode: local (0)
            local: initialDP (0)
        InitialDPArg      
            eventTypeBCSM: termAttemptAuthorized (12)

           
SLC response:

Camel
    invoke
        invokeId: present (0)
            present: 1
        opcode: local (0)
            local: requestReportBCSMEvent (23)
        RequestReportBCSMEventArg
            bcsmEvents: 6 items
                BCSMEvent
                    eventTypeBCSM: oCalledPartyBusy (5)
                    monitorMode: interrupted (0)
                    legID: sendingSideID (0)
                        sendingSideID: 02
                BCSMEvent
                    eventTypeBCSM: oNoAnswer (6)
                    monitorMode: interrupted (0)
                    legID: sendingSideID (0)
                        sendingSideID: 02
                    dpSpecificCriteria: applicationTimer (1)
                        applicationTimer: 35
                BCSMEvent
                    eventTypeBCSM: oAbandon (10)
                    monitorMode: notifyAndContinue (1)
                    legID: sendingSideID (0)
                        sendingSideID: 01
                BCSMEvent
                    eventTypeBCSM: routeSelectFailure (4)
                    monitorMode: interrupted (0)
                BCSMEvent
                    eventTypeBCSM: oDisconnect (9)
                    monitorMode: interrupted (0)
                    legID: sendingSideID (0)
                        sendingSideID: 02
                BCSMEvent
                    eventTypeBCSM: oDisconnect (9)
                    monitorMode: notifyAndContinue (1)
                    legID: sendingSideID (0)
                        sendingSideID: 01


MSC response:

Camel
    returnError
        invokeId: present (0)
            present: 1
        errcode: local (0)
            local: unexpectedDataValue (15)

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.