Setting Up Parlay X Terminal Status/SIP With Geo-redundant OCCAS-SC Without Session Replication
(Doc ID 1982245.1)
Last updated on FEBRUARY 25, 2019
Applies to:Oracle Communications Services Gatekeeper - Version 5.1.0 and later
Information in this document applies to any platform.
While setting up OCSG 5.1 with the new Terminal Status/SIP plugin which communicates with OCCAS-SC IM-PSX in the geo-redundant production environment, there is a configuration problem.
The OCSG clusters (AT and NT) are spanning multiple sites (MAN session replication::http://docs.oracle.com/cd/E15523_01/web.1111/e13709/failover.htm#CLUST235) and ParlayX clients access this system through a global, load-balanced URI.
The OCCAS-SC cluster is not spanning multiple sites, and SIP clients access this system through a local, load-balanced VIP address.
When configuring the OCSG TerminalStatus/SIP plugin, the 'PSX SIP domain' must be set to the site-specific VIP address, so it needs different 'PSX SIP Domain' for the OCSG server instances depending on which site it's running on. But this seems to be impossible, since the plugin configuration is set on the whole domain (i.e. spanning both sites). In other words, the geo-redundant OCSG cluster can only connect to one site of OCCAS-SC.
Is there a way around this without having to split up OCSG into site-specific clusters?
Can the 'PSX SIP Domain' configuration parameter be set per server instance, instead of for the domain?
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