In CAP2 Mediation Call Disconnect By MSC Not Handled Properly
(Doc ID 1966546.1)
Last updated on FEBRUARY 27, 2019
Applies to:Oracle Communications Converged Application Server - Service Controller - Version 6.1.0 and later
Information in this document applies to any platform.
For CAP2 (IMSSFCAP2 over IMSCFCAP2) Mediation Run Out Of Credit scenario (AC with releaseIfdurationExceeded set True) Oracle Communications Converged Application Server - Service Controller (OCCAS-SC) behaves differently and not correct in both cases when last Accounting Request (ACR) sent on TCAP End on TCAP Continue followed by TCAP End.
1. In case MSC sends ACR on TCAP END - OCCAS-SC sends ACR to SCP on TCAP Continue without any followed TCAP End.
2. In case MSC sends ACR on TCAP Continue followed by TCAP END - OCCAS-SC sends ACR with following ERB oDisconnect Leg 1.
The issue and call flow are identical with and without ocsb.tcap.end.postpone.in.millisecond system property set.
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