Fixes are available
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
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
The IBM-Destination header is not removed from the Session Initiation Protocol (SIP) ACK message in the following scenario: *WebSphere Application Server sends Invite to the User Agent. *User Agent rejects with 4XX response containing the Record-Route header. *WebSphere Application Server sends ACK with IBM-Destination header containing the Record-Route value. This issue occurs when working with WebSphere Application Server in a federated environment.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server version * * 8.0 Session Initiation Protocol (SIP) * * users * **************************************************************** * PROBLEM DESCRIPTION: The IBM-Destination internal header is * * not removed from the SIP ACK message * * to a 4XX response. * **************************************************************** * RECOMMENDATION: * **************************************************************** In the SIP Stack the header is only removed when the connection is null or not reliable in TransportCommLayerMgr.sendMessage().
Problem conclusion
Changed the code in the SIP Stack - TransportCommLayerMgr.sendMessage() - to remove the header for any case (and not just for a null/unreliable connection). The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.1. 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 number
PM40796
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-06-05
Closed date
2011-06-09
Last modified date
2011-06-09
APAR is sysrouted FROM one or more of the following:
PM35954
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
Document Information
Modified date:
27 October 2021