SCA Rejects 200OK Messages Coming Right After "183 Session Progress"
(Doc ID 2541360.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.4.1 and later
Information in this document applies to any platform.
Session Control Agent (SCA) interface provides support for SIP/SIMPLE messaging and integrated triggering capabilities for Oracle Applications and third-party applications.
In the current scenario, an issue was found for SCA which is not acknowledging (ACK'ing) 200OK messages coming right after 183 (Session Progress) from the B-Leg.
This issue is described in the following GraphFlow:
The INVITE message sent by SLC in the first Frame is acknowledged by Metaswitch/SRP in Frame 4.
Next, SLC will send INVITE to the B-Leg which responds with 183 (Session Progress) and 200OK right after (5ms later). At this stage, 200OK received by SLC has not been acknowledged by SCA and B-Leg continues to send 200OK.
Attempt Termination nodes from control plan associated with this call flow have a Timeout configured for 15seconds.
The SLC somehow acknowledges 200OK only after the 15 second timer expires.
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