PM40797: THE SIP CONTAINER DOES NOT RESPOND CORRECTLY TO A KEEPALIVE

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
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 the SIP container receives a keepalive "ping" request from
  an RFC 5626 ("outbound") enabled client, it does not respond
  correctly with a keepalive "pong" response.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Session Initiation Protocol (SIP) users of  *
  *                  IBM WebSphere Application Server            *
  ****************************************************************
  * PROBLEM DESCRIPTION: The server does not respond correctly   *
  *                      to SIP keep-alive.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem occurs when a standalone application server
  receives a CRLF keep-alive request from a SIP client. The CRLF
  keep-alive technique is detailed in RFC 5626 section 3.5.1.
  The server is expected to respond with a single CRLF sequence.
  Instead, it responds with a "Content-Length: 0" header field,
  followed by two CRLF sequences. This is a violation of RFC
  5626 section 5.4.
  

Problem conclusion

• The problem is fixed in the SIP container. With this fix, the
  container responds to the keep-alive request with a single
  CRLF sequence, as instructed in RFC 5626.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.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:

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP