In Multiple Call-Leg Application, After The Call is Successfully Set Up, OCSB Immediately Disconnect The Call

(Doc ID 1511761.1)

Last updated on OCTOBER 10, 2016

Applies to:

Oracle Communications Service Broker - Version 3.1.1 to 3.1.1 [Release 3.1.0]
Information in this document applies to any platform.


In multiple call-leg application scenario triggered from CAP4, OCSB 3.1.1 is behaving inconsistently.
After the call is successfully set up, OCSB immediately decides to disconnect the call.

Scenario is the following:

  1. InitialDP is sent, and INVITE for incoming leg sent to AS (Application Server)
  2. 8 Invites, translated to ICA (InitiateCallAttempt), got ICARes, sent RRBCSM (RequestReportBCSMEventArg) on ICA leg and CWA (ContinueWithArgument)
  3. 8 outgoing legs send eventTypeBCSM oTermSeized
  4. Leg7 send EventReportBCSM of Oanswer, IMSCF send OK to AS, CWA to network
  5. AS cancel all other 7 legs
  6. IMSCF send 7 disconnectLeg to network
  7. AS send OK to first leg with sdp of leg7 in order to connect them
  8. IMSCF start the moveLeg operation of moving leg7 to CS1, first stage of this operation is disconnectLeg2 (dummyleg "leg2") in order to be able to perform moveLeg operation.
  9. disconnectLegResult of one of the other 7 legs is coming from network and by mistake translated in IMSCF sib to part of the moveLeg operation, this cause ContinueWithArgument to CS1 and this is forbidden before RRBCSM.
  10. DisconnectLegResult of leg2 is coming, IMSCF want to finish the moveLeg operation and send RRBCSM for leg1 + moveLeg to network, this RRBCSM got error because of the previous CWA on CS1.



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms