Just to add a note to the great tips from John (+5 points for this my friend!)
It sounds like the Intertel feature might be quite like this Unity Connection feature;
Cascading Message Notification
Cascading message notification allows you to send notifications to a widening circle of recipients. Cisco Unity Connection continues to send notifications according to the devices you selected until the message has been saved or deleted by a recipient.
For example, to create a cascade of message notifications for your Technical Support department, set the first message notification to be sent immediately to the pager of the front-line technical support representative. If the message that triggered the first notification has not been saved or deleted after a delay of 15 minutes, the next notification can be sent to the pager of the department manager. A third notification can be set up to call an employee in the Problem Resolution Group if the message is not saved or deleted after 30 minutes, and so on.
Note that when a user receives a notification as part of the cascade, the notification prompts the user to log on to the mailbox that is being monitored by the cascade.
An alternative to cascading message notification is to use dispatch messaging. For details, see the "Dispatch Messages" section in the "Messaging" chapter of the System Administration Guide for Cisco Unity Connection.
Step 1 In Cisco Unity Connection Administration, find the user account whose mailbox you want to monitor with a cascading notification.
Step 2 On the Edit menu, click Notification Devices.
Step 3 On the Notification Devices page, select a notification device and enter the applicable settings so that it notifies a person in the recipient list for the cascading notification. For example, for the first recipient, you would enter the phone number for the pager that belongs to the front-line technical support representative.
Step 4 In the Delay Before First Notification Attempt field, enter the desired delay for the device, in minutes.
Space notifications between each device at regular intervals, such as every 15 minutes. For the first device you set up, consider specifying 0 as the delay so that the first recipient receives the notification immediately. For the device of the second recipient, specify 15 minutes. Specify 30 minutes for the device of the next recipient, and so on.
Step 5 If the notification device is a pager or phone, choose a value for the Phone System field such that Connection can dial out to the phone number of the user who receives the notification; this is not necessarily the same phone system used by the user whose mailbox is being monitored as part of the cascade.
Step 6 Click Save.
Step 7 Repeat Step 2 through Step 6 to set up another device for the next person on the recipient list for the cascading notification. Note that in order for the cascading notification to work properly, the same Notification Rule Events check boxes must be checked on all of the devices in the cascade.
If you go into the subscriber your trying this for and go into notification options you'll see the schedule about half way dow the page, scroll past that to "Notification Options" - click the radio button for "Repeat notification if there are still new messages after this many minutes:" and put in a number which represents the number of minutes in between notifications. Also you can configure what happens when the device doesn't answer.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...