My Oracle Support Banner

Transport Parameter In Contact Header Not Set Correctly When TCP Transport Is Used (Doc ID 1261515.1)

Last updated on OCTOBER 12, 2018

Applies to:

Oracle Communications Converged Application Server - Version 4.0.0 and later
Information in this document applies to any platform.

Symptoms

When a SIP application creates a request and explicitly sets the transport parameter to be TCP, by setting transport equals TCP on the topmost Route header, OCCAS will correctly choose TCP as transport. 


It will correctly set transport as TCP also on its own Contact header added by container, making the UAS send responses via TCP. However, on the Contact header, it falsely set transport equals UDP causing new requests like ACK and BYE to be sent back via UDP instead of TCP..

In CONTACT header, container should set transport equals to TCP instead of UDP, in order to send new requests like ACK and BYE via TCP.

The issue can be reproduced with OCCAS select TCP as transport for an outbound request by setting transport equals TCP parameter.
The issue is seen on both OCCAS 4.0 and OCCAS 5.0.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.