OCCAS 5.0 Badly Fills Contact Header On Outgoing TCP Request (Doc ID 1333607.1)
Last updated on OCTOBER 10, 2016
Oracle Communications Converged Application Server - Version: 5.0.0 to 5.0.0 - Release: 5.0 to 5.0 Information in this document applies to any platform.
In a typical B2B UA application, when creating an outgoing SIP INVITE Request that will be more than 1300 bytes, the container correctly use the TCP protocol to send the message as recommended in the RFC 3261, but it badly filled the Contact header with setting the transport parameter to "udp" instead of "tcp" as recommended in the JSR 289 §18.104.22.168 :
"While setting the Contact header for an outgoing message the containers MUST set the transport parameter to the transport that is used to send this message."
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a Million Knowledge Articles and hundreds of Community platforms