Header Contact Not Correct When Using Method Setoutboundinterface

(Doc ID 1368899.1)

Last updated on SEPTEMBER 22, 2016

Applies to:

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

Symptoms

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.
Example:
Contact:<sip:wlssuser@host:5060;transport=udp;wlsscid=-6eee7f0af63b61c8>
If method setOutboundInterface is not called, the header Contact is correctly created.

Expected header looks like:
Contact:<sip:wlssuser@host:5060;transport=udp;wlsscid=-6eee7f0af63b61c8;sipappsessionid=keyEs1q-ProblemContact75402%23G0R1C0_Development-ProblemContact75402_-6eee7f0af63b61c8>

Cause

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