Fix (APAR):  PK64000

Status:  Fix

Release:  6.1.0.15

Operating System:  Linux

Supersedes Fixes:  

CMVC Defect:  PK64000

Byte size of APAR:  12232

Date: 2008-05-05

Abstract:  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.

Description/symptom of problem:  
PK64000 resolves the following problem:

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:                                                      
None                                                            

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:
None

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   


Directions to apply fix:  
NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release 6.0
__ Application Server (Express or BASE)
__ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
__ Extended Deployment (XD)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
__ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

For detailed instructions to Extract the Update Installer see the following Technote:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400

1) Copy PKxxxxx.pak file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory).

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  
NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.



Additional Information: