PK64000: WAS.SIP.SIPCONTAINER SHOULD SEND 400 BAD REQUESTWHEN INITIAL DIALOG REQUEST DOESN'T CONTAIN CONTACT

PK64000; 6.1.0.15: No '400 bad request' error when contact header is absent
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• In Websphere Application Server version 6.1.0.15, the
  sipContainer should send 400 bad request response when the
  initial dialog request doesn't contain a Contact header.
  Client instead receives "200 OK" on SUBSCRIBE request instead
  of "400 Bad Request".
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM Websphere Application Server version     *
  *                 6.1 Session Initiation Protocol (SIP) users  *
  ****************************************************************
  * PROBLEM DESCRIPTION: When an incoming dialog initial         *
  *                      request does not contain a "Contact"    *
  *                      header, UAS will fail to send           *
  *                      subsequent reqeusts to UAC which sent   *
  *                      the reqeust.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  To establish a dialog Initial Request and Response on it
  should both contain Contact header.
  

Problem conclusion

• Code has been changed to verify in the SipContainer that the
  initial incoming request contains a Contact header. If not, we
  will reject the request  with  "400 Bad Request" error code.
  This fix will be provided in IBM Websphere Application Server
  fix pack 6.1.0.19.
  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:

Modules/Macros

• SIP
  

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP