Last updated on OCTOBER 10, 2016
Applies to:Oracle Communications Converged Application Server - Service Controller - Version 6.1.0 and later
Information in this document applies to any platform.
For a scenario with a simple redirection service which adds a prefix to the CdPN and monitors the call. If the call setup fails, a fallback feature makes a new attempt without the prefix.
For the fallback attempt, OCCAS-SC must generate a CAP Connect, but since no parameters are modified, a CAP Continue is created, causing the MSC to Continue the call attempt WITH the previously set prefix.
How can we force OCCAS-SC to generate a Connect from that 302 (without updating the CgPN or CdPM)?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms