Not Proper Handling When Adding Record-Route Header When Proxy Traversing Different Transports
Last updated on APRIL 02, 2018
Applies to:Oracle Communications Converged Application Server - Version 5.0.0 to 5.0.0 [Release 5.0]
Information in this document applies to any platform.
When the OCCAS proxy is adding record-route the transport parameter is not added. This trigger the UA to send subsequent requests using UDP and that behavior creates some problems.
The Patch for <Bug 8831838> may be a work-around to only force TCP, but since SIP trunk providers very often use DNS SRV the application cannot know the used protocol until request is sent out.
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