To integrate GVP 7.6 (aka the old Telera product) with the Genesys Management Layer, Genesys uses a Windows service named “CMEInterface” which, in theory, allows the status of an IPCS server to be monitored and controlled through Solution Control Interface (SCI).
I say in theory because testing I have performed indicates that starting and stopping IPCS components through SCI is somewhat hit and miss. This is especially true in an environment where Genesys SIP server is deployed in a HA configuration using Windows Load Balancing to present a Virtual IP Address (VIP) for the SIP Server pair.
Therefore, for this client I have changed the configuration as follows:
For each GVP IPCS installation, I created a Third Party Application for the WatchDog. On the Annex tab I added a “start_stop” section using the standard Windows Service Control command to start or stop the “WatchDog” Windows service:
For each GVP IPCS installation, I created two alarm reaction scripts – one to start the IPCS WatchDog service and one to stop it:
I created an alarm condition to detect Hot Standby primary mode being activated (Log Event 4563) on the backup SIP T-Server:
And added alarm reactions to stop and restart each GVP IPCS Server:
Note that in the example shown above I have also configured an additional Alarm Reaction which starts another Third Party application. This is actually a batch script which uses Windows Load Balancing to disable port 5060 on the server where the primary SIP server is installed and enable port 5060 on the server where the backup SIP Server (which has now been promoted to PRIMARY) is running. By using Windows Load Balancing in this way I can configure a single Virtual IP Address (VIP) in the host mappings in Avaya SIP Enablement Services (SES):