My Oracle Support Banner

OCCAS-SC IM-SSF SIP-CAP3 Mapping Of CAP Parameters RedirectingPartyID And OriginalCalledPartyID Missing (Doc ID 2550431.1)

Last updated on AUGUST 24, 2020

Applies to:

Oracle Communications Converged Application Server - Service Controller - Version 6.1.0 and later
Information in this document applies to any platform.

Symptoms

When using OCCAS-SC IM-SSF (SIP->CAP), SIP->CAP3 mapping of CAP parameters redirectingPartyID and originalCalledPartyID are missing.

In IM-SCF (CAP->SIP), RedirectionInformation is mapped from the INVITE Diversion headers:
 - originalRedirectionReason from the bottom Diversion header “reason” parameter
 - redirectionCounter form the top-most Diversion header “counter” parameter
 - redirectionReason from the top-most Diversion header “reason” parameter

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.