Content-Type Should Not Be Case-Sensitive Per RFC

(Doc ID 1558054.1)

Last updated on DECEMBER 20, 2017

Applies to:

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


A call flow times out in the network because the originator is sending a "Content-Type"header field containing "application/SDP". The OCCAS container does not pass the message to the deployed application and the call hangs and eventually the originator sends in a CANCEL to the INVITE. The RFC below states the attributes are case-insensitive:



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