PM28896: NOTIFICATIONS ARE GENERATED WITH "PO" HEADER INSTEAD OF "IBM-PO"

7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Notifications are generated with "PO" header instead of "IBM-PO"
  header. This causes the notifications to be rejected with 408
  timeout response.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM Websphere Application Server version    *
  *                  7.0 Session Initiation Protocol (SIP) users *
  ****************************************************************
  * PROBLEM DESCRIPTION: Notifications are generated with "PO"   *
  *                      header instead of "IBM-PO" header.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  We used "PO" header in SipProxyInfo and TransportCommLayerMgr.
  This caused the notifications to be rejected with 408 timeout
  response.
  

Problem conclusion

• Fixed SipProxyInfo and TransportCommLayerMgr to use "IBM-PO"
  header.
  The fix for this APAR is currently targeted for inclusion in
  fix pack  7.0.0.15.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R700 PSY

     UP