Oracle SCA - Bad SIP Diversion Header Information
(Doc ID 2668008.1)
Last updated on JUNE 04, 2020
Applies to:Oracle Communications Network Charging and Control - Version 4.4.1 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) up to and including 220.127.116.11, Session Control Agent (SCA) is a highly available and scalable Session Initiation Protocol (SIP) transparent back-to-back user agent (B2BUA), redirect server, proxy server and registrar. It provides support for SIP messaging and integrated triggering capabilities for NCC/3C and third-party applications.
The SIP Diversion Header Implementation for Redirecting Number feature provides support for a new SIP header field; Call Control (CC)-Diversion. The CC-Diversion header field enables the SIP gateway to pass call control redirecting information during the call setup. Call control redirection is the redirection of a call based on a subscriber service such as call forwarding.
RFC 5806 defines SIP diversion as follows:
- A change to the ultimate destination endpoint of a request. A change in the Request-URI of a request that was not caused by a routing decision. This is also sometimes called a deflection or redirection.
- A diversion can occur when the “user” portion of the Request-URI is changed for a reason other than expansion or translation.
- A diversion can occur when only the “host” portion of the Request-URI has changed if the change was due to a non-routing decision.
There is an issue where SCA is adding an additional diversion header to the outgoing invite message.
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