Fixes are available
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
SIP container does not handle error case where a UA uses the same to-tags in different responses. WebSphere Application Server V8.0 Distributed operating systems.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 Session Initiation * * Protocol (SIP) * **************************************************************** * PROBLEM DESCRIPTION: The SIP container does not handle a * * case where there are multiple * * responses to a proxy, all with the * * same to-tag * **************************************************************** * RECOMMENDATION: * **************************************************************** The SIP container doesn't detect a case where there are two or more responses with the same to-tag in proxy mode, which is forbidden according to RFC 3261.
Problem conclusion
The fix lets the SIP container detect a situation where there are multiple responses to a proxy with the same to tag. In this case the container generates an error response and prints a warning. The error response to be generated is defined via the following custom property: "generated.container.error.on.to.tag.duplication". If the custom property isn't defined or set to 0 - the fix will be disabled. The valid values of the custom property are error codes between 3xx-6xx. Instruction of how to set SIP custom properties on V8.5.5 are in the following link: http://www-01.ibm.com/support/knowledgecenter/SSCKBL_8.5.5/com.i bm.websphere.nd.multiplatform.doc/ae/rjpx_sipcontaincustprops.ht ml The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.10 and 8.5.5.4 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
PI14132
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-20
Closed date
2014-07-14
Last modified date
2014-07-14
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022