OCCAS Is Not Using The Configured Value For retry-after Value (Doc ID 1083237.1)

Last updated on OCTOBER 10, 2016

Applies to:

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

Symptoms

OCCAS 3.1 MP1 is not using the configured value for retry-after, but always uses the default value of 180 second.
Set the following in sipserver.xml but in packet sniffing it is set to 180.
<retry-after-value>5400</retry-after-value>


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