Header Contact Not Correct When Using Method Setoutboundinterface

(Doc ID 1368899.1)

Last updated on JUNE 25, 2018

Applies to:

Oracle Communications Converged Application Server - Version 4.0.0 to 4.0.0 [Release 4.0.0]
Information in this document applies to any platform.


In OCCAS 4.0, the Contact header is not correct when application creates a new sipApp with createApplicationSessionByKey and uses the method setOutboundInterface of SipSession.
sipappsessionid information is missing.
If method setOutboundInterface is not called, the header Contact is correctly created.

Expected header looks like:




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