PM57136: IN A DOUBLE RECORD ROUTE SCENARIO DESCRIBED IN RFC 5658 SUBSEQUE NT REQUESTS DO NOT GET THEIR SECOND ROUTE HEADER REMOVED.

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

• In a double Record Route scenario described in RFC 5658
  subsequent requests do not get their second Route header
  removed.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V8.0       *
  *                  Session Initiation Protocol (SIP)           *
  *                  application users.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Subsequent requests do not get their    *
  *                      second route header removed             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the second Route header is checked it is not recognized
  as belonging to a local listening point because of erroneous
  checking for local listening points.
  

Problem conclusion

• Added a custom parameter to Record Route headers added in the
  double record route scenario and fixed the checking for local
  listening points.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.3.  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

• R800 PSY

     UP