In CAP2 Mediation Call Disconnect By MSC Not Handled Properly
Last updated on DECEMBER 20, 2017
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) OCCAS-SC behave differently and not correct in both cases when last ACR sent on TCAP End on TCAP Continue followed by TCAP End.
1. In case MSC sent ACR on TCAP END - OCCAS-SC sends ACR to SCP on TCAP Continue without any followed TCAP End.
2. In case MSC sent 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.
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