My Oracle Support Banner

IMSSFCAP2 Instance Throw An Exception And The Call Is Released (Doc ID 2469163.1)

Last updated on NOVEMBER 21, 2019

Applies to:

Oracle Communications Service Broker - Version 6.0.0.1.0 and later
Information in this document applies to any platform.

Symptoms

In OCSC with two core instances in the orchestrate rule.
      -imssfcap2_icsscp_instance is routing to call guard scp which decides whether to continue/block the call.
      -imasf_wifi_instance is routing to OCCAS SIP application which controls the call flow.

The designed call flow is that if the called is noAnswer, connect the call to the called's VM.
So the second <Connect> will be triggered and sent by OCSC.
The imssfcap2_icsscp_instance successively receives two ERB<noAnswer> and ERB<CallAccepted> but it doesn't know actually the call has been reconnected. So it throws the following exception:



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.