Multiple Outstanding Transactions On A Single Dialog Having Failed and Duplicated call-id Issues
Last updated on DECEMBER 20, 2017
Applies to:Oracle Communications Converged Application Server - Version: 4.0.0 to 4.0.0 - Release: 4.0.0 to 4.0.0
Information in this document applies to any platform.
Setup a SIP session from OCCAS to the media server and send SIP INFO messages to transport the MSML to the media server.
OCCAS does not send many of the SIP INFO messages and in some cases duplicates call-id appear on different SIP INFO’s.
On a standalone machine setting the -Dwlss.local.serialization=true reproduces the concurrent INFO issue, but setting the -Dwlss.local.serialization=false seems resolve this, however, it is unacceptable due to memory utilization.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms