PI21665: WEBSPHERE CAN USE THE SAME FROM TAG AND VIA BRANCH IN TWO DIFFERENT REQUESTS EVEN IF CALL-ID IS DIFFERENT.

Fixes are available

APAR status

Closed as program error.

Error description

A network product sends options to Application Server with
active/standby configurations and two different IP address. The
active and the standby use the same from tag and via branch in
these two different requests although call-id is different.
Application Server treats the second options as a
re-transmission of the first one and returns 200 ok to two
different IP address. This will appear in the TCP/IP trace and
Application Server traces.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V8.0 and V8.5 Session Initiation     *
*                  Protocol (SIP)                              *
****************************************************************
* PROBLEM DESCRIPTION: Two different SIP request were          *
*                      accepted as the same SipRequest         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The SIP Container didn't test the "sent-by" pareameters in
the Via header. This caused it to recognize different requests
received from differnt clients to be received as the same
SipRequest.

Problem conclusion

We now test the sent-by parameters in the Via according to the
RFC 3261.

The fix for this APAR is currently targeted for inclusion in
fix pack 8.5.5.5 and 8.0.0.10.  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
PI21665
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
2014-07-09
Closed date
2014-09-30
Last modified date
2014-09-30

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI21665: WEBSPHERE CAN USE THE SAME FROM TAG AND VIA BRANCH IN TWO DIFFERENT REQUESTS EVEN IF CALL-ID IS DIFFERENT.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSY

Document Information

Share your feedback

Need support?