Question on immediate shutdown

[agfa]

Like to know what might be the situations were 'Immediate Shutdown' in PVP doesn't work
We ran into 2 occasions where there is a problem. we could not figure out what might be causing it from our end. We couldn't figure out the time we might need to wait for terminating each line.

1) if 2 users log into two separate lines and starts to enter some crietria for search . Once the <Immediate Shutdown> button on PLUM is clicked, the first line is immediately dropped, while the second line remains active, but no more prompts are heard.

2) Even when only one user is logged into the system we get to the same trouble, when the user is trying to enter the critera and validating it.

Right now looks like when the call prompts for some input/criteria this seems to happen.

[support]

When using the IVR platform, you should not use "Immediate Shutdown" unless you're willing to lose some/all existing connections. You should use "Graceful Shutdown" for nearly all situations.

[agfa]

That's true. But our customers will be exposed to PVP user interface. So we have to do testing to see whether any of the settings in PVP affects our implementation.

Since we are getting problems in specific areas and easily reproducible we like to figure out why this is happening.

[support]

Hello,

The "Immediate Shutdown" feature does not guarantee that all calls will be hung up immediately, it is provided to force the IVR platform to shutdown if there is some internal failure that causes the IVR system to become unresponsive to a graceful shutdown request. If the customer performs an immediate shutdown the system stops the plumvp process that is currently running halting any interactions with the remote caller and preventing the IVR system from answering any new calls until the process is restarted by the user. Upon restarting the IVR platform all of the analog channels will be reset and the IVR system will continue to take calls on all of the lines.

Regards,
Plum Support