SCA Critical Errors When Receiving SIP 488 Message
(Doc ID 2822884.1)
Last updated on DECEMBER 17, 2021
Applies to:
Oracle Communications Network Charging and Control - Version 6.0.1 and laterOracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.
Symptoms
In Oracle Communications Network Charging and Control (NCC) and Oracle Communications Convergent Charging Controller (OC3C), the 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 Oracle Communications Network Charging and Control and third-party applications. The SCA enables real-time charging, instant messaging and personal mobility in SIP-based next generation networks (IETF/ETSI NGNs) and in the IP Multimedia Subsystem (3GPP IMS, 3GPP2 MMD). It can be integrated into NCC's Prepaid Charging solutions based on Charging Control Services (CCS), with on-line charging interfaces to the NCC Voucher and Wallet Server and to third party real-time billing systems.
There is a scenario when SCA receives a SIP 488 message that generates the following error message:
The scenario messages looks like following:
a-leg SCA b-leg
------ INVITE ------>
------ INVITE ------>
<------- 100 ---------
<------- 100 ---------
<------- 488 ---------
-------- ACK -------->
<------- 404 ---------
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 |