OCCAS Sends Additional SIP/SDP "200 OK, With Session Description" Messages After Session End (Doc ID 1587335.1)

Last updated on SEPTEMBER 12, 2016

Applies to:

Oracle Communications Converged Application Server - Version 2.1.0 and later
Information in this document applies to any platform.

Symptoms

A basic SIP session flow, between UAs (User Agents), may look something like the following:

   ----> INVITE
   <---- 100 Trying
   <---- 200 OK, with session description
   ----> ACK
   ----> BYE
   <---- 200 OK


Network tracing occasionally shows, for some SIP sessions, that OCCAS (Oracle Communication Converged Application Server) is re-sending the SIP/SDP "200 OK, with session description" response multiple times after the SIP session has ended.  The call flow looks something like this:

   ----> INVITE
   <---- 100 Trying
   <---- 200 OK, with session description
   ----> ACK
   ----> BYE
   <---- 200 OK    // Call ended
   <---- 200 OK, with session description
   <---- 200 OK, with session description
   <---- 200 OK, with session description
   <---- 200 OK, with session description
   <---- 200 OK, with session description
   <---- 200 OK, with session description

The network tracing shows the ACK response and BYE request are sent very closely together, with less than a 1 millisecond gap.  Analysis of OCCAS logs also shows BEA-331604 warning messages being generated at the same time as the ACK/BYE message being received.  For example:

Cause

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