SCA Does Not Support SIP Re-INVITE Messages
(Doc ID 2529273.1)
Last updated on OCTOBER 14, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 220.127.116.11.0 [Release 4.3 to 12.0.0]
Oracle Communications Convergent Charging Controller - Version 6.0.0 to 18.104.22.168.0 [Release 6.0 to 12.0.0]
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 22.214.171.124, Session Control Agent (SCA) does not support a Re-INVITE message.
SCA is NCC's/3C's Session Initiation Protocol (SIP) gateway and will convert from SIP to Intelligent Network Application Part (INAP) to Advanced Control Services (ACS).
A SIP re-INVITE, as described in RFC 6141, is a INVITE on an existing dialog and is used by SIP endpoints to update the Session Description Protocol (SDP) information. As NCC/3C generally only cares for the SIP header information, the re-INVITE should be forwarded as-is along with all subsequent messages.
Currently, no version of NCC/3C will do anything upon receiving a re-INVITE. This is the problematic call flow:
As a result, the endpoint that sent the re-INVITE will eventually time out and try to end the call with a BYE. This results in the following error:
The alarm will say A_BYE or B_BYE depending on which leg sent the BYE message after a re-INVITE.
The symptoms of this will depend on the service design. Essentially the BYE will not disconnect the call and the call itself will continue to run indefinitely. If the call is being charged, then all the subscribers funds will be consumed.
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