Is it possible to do roll-over message notification this way:<br><br>1) Notify device1 when a message comes in (Can be done now)<br>2) Notify a second Device when the message doesn't get retrieved within X amount of time, say..5 minutes (?).<br>3) Notify a third Device when the message doesn't get retrieved within Y amount of time, say.. 15 minutes (?).<br><br>Seems like Unity only notifies the next notification device if the first notification device fails to answer or busy. So if the first device is a pager/cell phone or even a home phone with an answer machine then it will never touch the next device. <br><br>Any suggestions on how to enable this function?<br><br>Systems Engineer
sure, you can do this. This is what the "Send initial notification after how many minutes" field is for at the bottom of the notification device. For instance:
Phone 1 is set to trigger on all urgent voice mails and has a delay of 0 minutes and retries every 15.
Phone 2 is set to trigger on all urgent voice mails and has a delay of 15 minutes and retries every 15.
Phone 3 is set to trigger on all urgent voice mails and has a delay of 30 minutes and retries every 15.
Say phone one is a field tech, phone 2 is his manager, phone 3 is HIS manager and so on. The effect of this is when a message arrives the field tech gets called. If the message is still in there 15 minutes later, the field tech AND his manager get a call. If after another 15 minutes an urgent message is still there, the tech, his manager and HIS manager get a call and so on...
Should be able to handle most esclation scenarios.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.