Ok, so no big surprise here... Avaya won't support it. However, the reason I got was that, because "a process could hang" which would prevent CMS or the Server from restarting "and no one would know" because a live person wasn't monitoring it. Guess in this day and age, monitoring tools are not used by Avaya like we use them.
Plus I'd have a call on my cell pretty quick if people couldn't get access to CMS after a reboot.
The process to get it working wouldn't change either, I'd still have to go on site, or call the vendor that hosts our network location, and power cycle the server.
Sometimes can't understand Avaya's reasoning. We'll be changing to a BP for CMS support hopefully at the end of this contract. Might get a different answer from them.
- Stinney
Quoting only proves you know how to cut and paste.