PH21614: SIP REQUESTS WITH APPROPRIATE CSEQ NUMBERS RECEIVE MESSAGE 500 INCORRECT CSEQ

9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3

APAR status

• Closed as program error.

Error description

• SIP requests with appropriate CSeq numbers are being rejected.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Session Initiation Protocol (SIP)    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using                              *
  *                      B2buaHelper.createResponseToOriginalReq *
  *                      uest, requests with correct CSeq        *
  *                      numbers might be rejected with an 500   *
  *                      error.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a SIP session is forked, requests with correct CSeq
  numbers might be rejected with an 500 Incorrect CSeq error.
  

Problem conclusion

• A fix was made in the SIP Container so when using the
  createResponseToOriginalRequest API, the cloned session does
  not inherit the remote sequence number from the original
  session.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.18 and 9.0.5.3. For more information, see
  'Recommended Updates for WebSphere Application Server':
  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP