PM63808: ISSUES WITH SIP CONTAINER

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• When a Session Initiation Protocol (SIP) application on
  WebSphere Application Server establishes a dialog as UAC and
  receives a re-INVITE from the UAS, the container is responding
  with a ?SIP 491 No Final Response to previous INVITE?. The
  previous INVITE (the one that created the dialogue) had
  received a 200OK response and been acknowledged. In this case,
  the container should be passing the reINVITE to the SIP
  application as it is a valid request.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0 and V8.5                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: After SipContainer sent a 491 response  *
  *                      on an INVITE, it sent a 491 error       *
  *                      response on any incoming request on     *
  *                      the same dialog.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The Session Initiation Protocol (SIP) container doesn't change
  the internal state of the dialog once it sends a 491 response
  on an ambiguous request. It causes the SipContainer to
  continue and send the 491 response for all incoming requests
  on this dialog.
  

Problem conclusion

• Now, when the container receives a 200 OK after it sends a 491
  on an ambiquous request, the sipContainer changes the state of
  the dialog to success.
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.4 and 8.5.0.1.  Please refer to the Recommended
  Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PM70431

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R800 PSY

     UP