My Oracle Support Banner

IP Address In Connector.sip.address To Connector When Public Addres Is FQDN (Doc ID 2525798.1)

Last updated on AUGUST 24, 2020

Applies to:

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

Symptoms

As part of the acceptance is was found a new issue in JSR309 interactions when Evolved communications Application Server (ECAS) is configured for working in High Availability (HA) mode (Coherence).

In order to work in HA mode, customer needs to set in the "External Listen Address" parameter in the sip channel of ECAS the FQDN that represents both engines in the cluster.

This is required in order to have in-call fail-over working: ECAS will send the value defined in this parameter in the Contact header. Having the FQDN in Contact will make it possible for CSM to redirect in-dialog requests to another engine in case the engine serving the call gets down. Having just the IP Address won't make in-call fail-over possible.

The issue found is that, when Ext-Listen-Address is defined that way, DLG connector returns an error when instructed to send traffic to MRF (i.e. in Hold cases). It seems DLG is not able to match the IP Address (sent by ECAS app to the connector) with the FQDN, even while this FQDN is included in the /etc/hosts file.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.