Restarting IVR Servers and Drivers

[Jim]

Is there a way to automate the a restart of the IVR server. Every once in a great while Genesys and a Periphonics box will stop talking. On the IVR (Sun) should be able to write something that will restart the IVR Drivers but if I also need to close and restart the IVR server that resides on a NT box how would I do it? Would have to coordinated between the Sun and NT so the server starts before the drivers start. Any help would be great!

[Victor]

Have you tried using one of those monitoring packages. We usually use FirstWatch to do monitor a particular task, and when that task is gone, restart something else, or switchover to something else...
I believe you can monitor a particular task on a remote machine, shut it down, and then restart it using this package.
What are you using now?

[Jim]

Currently me and my pager are the backup system. I was hoping to find something less expensive then First Watch and was not sure if First Watch could handle restarting processes in sequence across different operating systems. Will have to check it out.

Jim

[TM]

You should be able to use FirstWatch to restart the system by making it run a script, which would in return would start restarting this or that.

There is a less expensive method which would rely on a cron job, which would monitor all your processes, and when one is down, it would run a particular script to restart the program. There are also a myriad of NT programs which would allow you to monitor a particular task and when it fails, restart it, or run a batch file which does what you want.

In my modest opinion, instead of focusing on the recovery package, it would be prudent to see if the problem itself could be resolved. ave you talked to Genesys about what might be causing the system to freeze?

[Jim]

The problem is the IVR's decide to reboot for no apparent reason. While the magical reboot is being addressed with the people at Peri, when it does reboot everything comes back on line but when the peri2is process starts it doesn't reestablish the communication with the IServer. The IServer needs to be stopped and restarted then the peri2is can be started and everything is fine. The good people at Genesys said that the "problem is currently being addressed by Engineering".

We can write a CRON job to restart the peri2is process but to have it talk to the NT box to restart the I Server is beyond my abilities at this point.

Jim

[Ramesh Pitchumani]

Jim:

In our case, we also shut down the Periphonics IVR and restart it. It runs on a UNIX machine. But I never shut down the Genesys IVR interface server. Whenever the Peri box restarts, I just need to start my DRIVER. It autmatically establishes connetion with the IVR interface server and everything runs normal. I do have to delete all the files in the PIPES directory in the Peri machine before I can start the IVR interface driver (peri2is). But I never restart my IVR I/F server on the Genesys box. Let me know if I have understood your problem in a wrong manner.

Thanks,
Ramesh.

[Jim]

Our problem is that the DRIVER does not always establish the connection with the server after the IVR is brought back up. Most of the time it's OK but every so often I have to restart the server. Genesys has sent me an update to the driver so I'm hoping this will solve the problem.

Do you manually start the Peri2is process or do you have it start automatically when the IVR start up?

Jim

[Ramesh Pitchumani]

Currently we start it manually. We are planning to write a script to start it automatically in the future. We havent gone live yet. That is one of the things that we are working on.

Thanks,
Ramesh.