PK83615: RFC NON-COMPLIANCE IN COPYING ROUTE HEADERS AND CONTACT HEADERS IN DIALOGS

Fixes are available

APAR status

Closed as program error.

Error description

The problem is that we do not follow the RFC in copying route
headers and contact headers in dialogs. If we find transport=tls
we change it to transport=tcp. This is the problem.
**************
If the route set is empty, the UAC MUST place the remote
target URI into the Request-URI.  The UAC MUST NOT add a
Route header field to the request.

If the route set is not empty, and the first URI in the
route set contains the lr parameter (see Section 19.1.1),
the UAC MUST place the remote target URI into the
Request-URI and MUST include a Route header field
containing the route set values in order, including all
parameters.

If the route set is not empty, and its first URI does not
contain thelr parameter, the UAC MUST place the first URI
from the route set into the Request-URI, stripping any
parameters that are not allowed in a Request-URI.  The UAC
MUST add a Route header field containing the remainder of
the route set values in order, including all parameters.
The UAC MUST then place the remote target URI into the
Route header field as the last value.

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  Session Initiation Protocol (SIP) users of  *
*                  IBM WebSphere Application Server V6.1 and   *
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: When sending a subsequent message in a  *
*                      dialog, the transport parameter gets    *
*                      altered.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem is in the container modifying the transport
parameter in the request URI and the top Route URI when
sending subsequent requests within a dialog.
For example, the container receives INVITE with Contact
sip:alice@atlanta.com;transport=tls and then it sends a BYE
with sip:alice@atlanta.com;transport=tcp in the request URI.

Problem conclusion

The bug is fixed in the container by copying the URI from the
initial request that created the dialog into subsequent
requests, without modifying any parameters in the URI.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.25 and 7.0.0.5.  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
PK83615
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-30
Closed date
2009-04-03
Last modified date
2009-04-03

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK83615: RFC NON-COMPLIANCE IN COPYING ROUTE HEADERS AND CONTACT HEADERS IN DIALOGS

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?