DuVoice Support - vs7:manual:admin:templates

Call Routing

Anonymous (anonymous@undisclosed.example.com) — 2023-02-01T18:26:26+00:00

2026/10/02 13:49	current
Line 1:	Line 1:
	+	{{indexmenu_n>10}}
	+	====== Call Routing =====
	+
	+	A call routing plan is a powerful tool that determines how calls are processed during a certain time window (based on day of week and time of day). It is the called party's mailbox that determines which call routing plan is active for a given call. Multiple call routing plans may be assigned to a mailbox, but only one of them may be considered active at any given time. //If two or more call routing plans have overlapping time windows, the one listed first on the mailbox's call routing tab is the one that will be active.//
	+
	+	When there is no active call routing plan (either none assigned to the mailbox or none that are active for the current time), the system will take default actions instead (what action depends on whether transfers are allowed for the given mailbox as well as the current state of the call).
	+
	+	<WRAP round important 75%>
	+	Changing the settings for the //Auto Attendant// call routing template, assigned to auto attendant mailboxes by default (such as 991), can disable the auto attendant function and/or put the voice mail ports into an infinite loop. For most applications, the default settings for this template should not be modified.
	+	</WRAP>
	+
	+	Whether you opt to edit an existing call routing plan or create a new one, the system will open a dialog for editing similar to that shown below. Other than the title bar, the dialog for creating a new call routing plan and for editing an existing plan are virtually identical.
	+
	+	To save your changes, click OK. If you are creating a new template, the system will prompt you to enter a filename before saving the file; if you are editing an existing template, it will just overwrite the existing file.
	+
	+	To close the dialog without saving any changes, click Cancel.
	+
	+	<WRAP round tip 75%>
	+	//If you want to create a new template based on an existing one, use the Copy option, then edit the copy.//
	+	</WRAP>
	+
	+	{{:images:vs7:manual:tpl-callroute.png?nolink\|}}
	+
	+	The above figure shows the dialog for editing a call routing plan, with the //Standard// call routing plan loaded.
	+
	+	===== Call Routing Properties =====
	+
	+	This section includes the schedule settings that determine when the template is active as well as the settings that determine what to do at the start of the call (when someone is attempting to transfer to a mailbox using this template).
	+
	+	\|< 90% 15% >\|
	+	^Property^Description^
	+	\|//Starting At//\|Time of day when the template becomes active, for any day on which it is allowed to be active.\|
	+	\|//Ending At//\|Time of day when the template becomes inactive, for any day on which it is allowed to be active.\|
	+	\|//Days//\|The days of week for which the //Starting At// and //Ending At// times are valid; the template will be inactive for the entirety of any day not selected.\|
	+	\|//Routing Address//\|The mailbox address used by the //Routing Technique// when routing the call.\\ \\ If any address other than //Office Extension// is chosen you will need to create that address in any mailbox that will use the template. Otherwise, you may experience serious problems when attempting to transfer to the mailbox.\|
	+	\|//Routing Technique//\|The manner in which the call is routed on the initial transfer attempt. This will almost always be extension transfer (paired with Office Extension as the routing address).\\ \\ If the mailbox has //Do Not Disturb// enabled, then the call will be routed to the mailbox greeting rather than attempting a transfer.\|
	+	\|//Routing Method//\|This will always be //Standard Method// and should not be changed.\|
	+	\|//Routing Chain/Complete//\|The action to take after the greeting has been played and (if appropriate) a message has been recorded. If you select //Execute Mailbox//, another selection box will appear to the right; select the mailbox to execute from that list.\|
	+
	+	==== Routing Complete Actions ====
	+
	+	The following actions are provided for use by the //Routing Chain/Complete// setting:
	+
	+	\|< 90% 15% >\|
	+	^Action^Description^
	+	\|//Disconnect//\|Hangs up the call immediately.\|
	+	\|//Execute mailbox//\|Leaves the current mailbox and executes the active call routing plan for the specified mailbox.\|
	+	\|//Launch IVR application//\|Reserved for future use.\|
	+	\|//Return to attendant//\|Returns the call to the current location's auto attendant mailbox.\|
	+	\|//Transfer to operator//\|Transfers the call to the extension of the current location's operator mailbox.\|
	+
	+	===== Optional Completion Properties =====
	+
	+	This section includes the settings that determine the action to take if the call returns to voice mail because the transfer attempt was not successful. Each of the following settings uses a selection box to choose from a predefined list of options. If the option selected requires a secondary setting, another selection box will appear to the right. For example, if //Execute Mailbox// is selected, a secondary selection box will appear to the right from which you can choose the mailbox number to execute.
	+
	+	\|< 90% 20% >\|
	+	^Property^Description^
	+	\|//Ring No Answer//\|The action to take when a call to the extension is not answered.\|
	+	\|//Busy//\|The action to take when the extension is busy.\|
	+	\|//No Plan Active//\|Not used; deprecated.\\ \\ //If no plan is active, the system will take default actions based on the call status://\\ \\ On RNA, it will perform the //Ring no answer processing.//\\ On busy, it will perform //Busy/Queuing processing.//\\ On failure due to network problems, it will perform //Return to attendant//.\|
	+	\|//Telephone Network Problems//\|The action to take if errors on the telephone network occur (e.g., no dial tone or no ring back).\|
	+
	+	==== Optional Completion Actions ====
	+
	+	The following actions are provided for use by the settings found under Optional Completion Properties:
	+
	+	\|< 95% 20% >\|
	+	^Action^Description^
	+	\|//Busy/Queuing processing//\|Plays the busy greeting and, if the COS allows, offers the option to join a call queue for this extension. Otherwise, it will take a message, if appropriate, after playing the greeting. This option is only available for the Busy setting.\|
	+	\|//Disconnect//\|Hangs up the call immediately. This is not supported on SIP.\|
	+	\|//Execute mailbox//\|Leaves the current mailbox and executes the call routing plan for the specified mailbox.\|
	+	\|//Immediate record//\|Begins recording a message immediately, without playing any greeting or prompts. Whether a beep is played first or not depends on the configuration of the assigned COS.\|
	+	\|//Launch IVR application//\|Reserved for future use.\|
	+	\|//Play blocking greeting and go to voice mail//\|Plays the selected mailbox greeting and invokes the assigned SDA menu, recording a message if appropriate.\|
	+	\|//Return to attendant//\|Returns the call to the current tenant's auto attendant mailbox.\|
	+	\|//Ring no answer processing//\|Plays the RNA greeting and invokes the assigned SDA menu, recording a message if appropriate. This option is not available for the Busy setting.\|
	+	\|//Transfer to operator//\|Transfers the call to the extension of the current tenant's operator mailbox.\|
	+
	+	===== How It Works =====
	+
	+	The call routing plan is used to alter how a call is processed by the system in one of two places: either at the start of the call (when the extension is first dialed) or at the end of a call (after it has been answered or not answered). One further consideration is the schedule that specifies the time period and days of the week during which the template is considered active (collectively known as the time window).
	+
	+	==== Time Window ====
	+
	+	The time window determines when the template is active and when it is not. For any time that falls outside of the time window, the template is inactive and has no effect on the call whatsoever. The only caveat to the time window is the //Template Disabled// check box on the Call Routing Plans property page; if the template is marked as disabled, then it is considered inactive at all times on all days regardless of the time window settings for the template itself.
	+
	+	The time window for a call routing plan follows these three rules:
	+
	+	- For any day of the week that is not selected, the template will not be active for that entire 24-hour period.
	+	- For any day of the week that is selected, the template will be active from the starting time until the ending time (inclusive), and otherwise inactive, except in the case where both times are set to 12:00 a.m.
	+	- If the starting and ending times are both 12:00 a.m., then for any day of the week that is selected the template is active for the entire day.
	+
	+	<WRAP round info 75%>
	+	If you assign more than one template to a mailbox and they have overlapping time windows (such that both would be considered active during a given time period), the one listed first will be the one that is used. In searching for an active routing plan, the system moves from the top down, stopping at the first template that is considered active.
	+	</WRAP>
	+
	+	==== Start of Call ====
	+
	+	In this context, start of call is defined as either when a caller dials the extension from within the system (e.g., at the main greeting auto attendant or during some other mailbox's greeting) or when the caller selects an SDA action that has been defined to transfer to an extension. In either case, the first thing the system does is check for an active call routing plan.
	+	* If there is no active call routing plan, it will perform the default action: //transfer to the mailbox extension//.
	+	* If there is an active plan, it will run the technique specified by the template. If the technique is //extension transfer//, it will transfer to the //Route To// address specified by the template. For the //Standard// call routing plan, this is the //Office Extension// address, which is the extension number defined on the Owner Settings property page. Other call routing techniques may perform some action other than transferring and may not even use the //Route To// address at all.
	+
	+	==== End of Call ====
	+
	+	In this context, end of call means either that the transfer was completed successfully or the call has bounced back to the voice mail system (VMS) because either it was not able to complete the transfer or the call went unanswered or the line was busy (or DND). Note that on integrated systems using blind transfers, a call bounced back on busy or ring no answer may come into the system as a 'new' call on a different voice port; nevertheless, it is still treated as the 'end of call' in this context (as long as the call is integrated in a way that identifies it as having been forwarded on busy or RNA).
	+
	+	The first thing the VMS does in this case is to check for an active call routing plan. If there is no active plan, then default actions are used instead.
	+	* For ring no answer, the default action is //Ring no answer processing// (play the ring no answer greeting and follow the SDA).
	+	* For busy, the default action is //Busy/Queuing processing// (play the busy greeting and follow the SDA or allow caller to join the call queue).
	+	* In all other cases, the default action is //Play blocking greeting and goto voice mail// (play the call blocking greeting and follow the SDA).
	+
	+	For standard mailboxes, absent the caller selecting an SDA action, the VMS will default to taking a message after the appropriate greeting is played, unless the assigned COS does not allow messages to be taken (in which case it will typically return to the main greeting auto attendant).
	+
	+	If a call routing plan is active, then the actions taken will depend on how the settings listed in the Optional Completion Events section are configured. They may or may not be the same as the default actions listed above.
	+
	+	===== Why Use It =====
	+
	+	As discussed in the How It Works section above, the VMS will automatically take certain call routing actions by default if no plan is assigned to the mailbox or if the assigned plan is not active. So why would you create and assign a different call routing plan template? To change how the calls are processed.
	+
	+	For example, you may not want to enable call queuing, as it can quickly tie up a lot of voice lines, preventing callers from being able to leave messages and subscribers from being able to retrieve messages. This can easily be a problem on small systems. So you may want to make sure that your mailboxes are using a call routing plan template that has the Busy condition assigned the action //Play blocking greeting and goto voice mail// rather than the //Busy/Queuing processing// action. And, in fact, this is exactly how the //Standard// call routing plan template—-the one used by //standard// mailboxes by default--—is configured.

Class of Service

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:27+00:00

2026/10/02 13:49	current
Line 1:	Line 1:
	+	{{indexmenu_n>20}}
	+	====== Class of Service =====
	+
	+	Class of service (COS) templates define the mailbox attributes and subscriber permissions and restrictions that control the behavior of the mailbox. Only one COS may be assigned to a mailbox at a time, although a scheduled event template may override the assigned COS for mailboxes that support the use of scheduled events. The COS template is assigned to the mailbox on the Owner Settings property page.
	+
	+	Whether you opt to edit an existing template or create a new one, the system will display the COS Editor dialog as shown in the sections below. Other than what is displayed in the title bar and which buttons are available at the bottom, the dialog is the same in both cases.
	+
	+	To save changes to an existing template, click Save. This option is not available if you are creating a new template.\\
	+	To save a template with a new file name, click Save As.\\
	+	To close the editor without saving any changes, click Cancel.
	+
	+	COS settings are split across several property pages:
	+
	+	* [[vs7:manual:admin:templates:cos:general\|General]] -- Various settings that don't fit in the other categories.
	+	* [[vs7:manual:admin:templates:cos:recording\|Recording]] -- Settings related to sending and receiving voice messages.
	+	* [[vs7:manual:admin:templates:cos:playback\|Playback]] -- Settings related to message playback.
	+	* [[vs7:manual:admin:templates:cos:transfers\|Transfers]] -- Settings related to transferring.
	+	* [[vs7:manual:admin:templates:cos:vemail\|VeMail]] -- Settings related to the VeMail feature.
	+	* [[vs7:manual:admin:templates:cos:greetings\|Greetings / Prompts]] -- Settings related to playing mailbox greetings and prompts.
	+	* [[vs7:manual:admin:templates:cos:wakeup\|Wakeup Calls]] -- Settings related to the Wakeup Call feature (for guest mailboxes only).

Message Delivery

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:27+00:00

2026/10/02 13:49	current
Line 1:	Line 1:
	+	{{indexmenu_n>30}}
	+	====== Message Delivery =====
	+
	+	Message delivery templates are used to forward copies of incoming messages to other mailboxes or email addresses.
	+
	+	One step in enabling the VeMail feature, for example, is to assign the //Auto Forward to Email// message delivery template to the mailbox. //More than one template may be assigned to a given mailbox, and all of them will be processed for each message received.//
	+
	+	Whether you are creating a new template or editing an existing one, the system will display the current settings in a dialog similar to that shown in the figure below. The only significant difference is in the text displayed in the title bar. This particular example shows the //Auto Forward// template opened for editing.
	+
	+	{{:images:vs7:manual:tpl-msgdel.png?nolink\|}}
	+
	+	To save your changes, click OK. If you are creating a new template, you will be prompted to enter a filename before the data is saved; if you are creating a custom template, the filename is created for you. In any case, Cancel will discard any changes not previously saved.
	+
	+	===== Definition =====
	+
	+	These settings define what triggers the template, what process is performed and how often to retry on failure.
	+
	+	\|< 90% 20% >\|
	+	^Setting^Description^
	+	\|//Event//\|Type of event that triggers this template. Options include: <WRAP>
	+	* All messages
	+	* Normal messages
	+	* Urgent messages
	+	Select //all messages// to forward any new message regardless of type. Otherwise, select the type of new message to be forwarded.
	+
	+	//The priority message type that is also listed has been deprecated and should not be used.//
	+	</WRAP>\|
	+	\|//Address//\|The address to which the message will be forwarded. To forward to another mailbox, select a //Mailbox// address. For VeMail, select an //Email// address.\|
	+	\|//Technique//\|Always ''Auto-forward''. //This setting cannot be changed.//\|
	+	\|//Method//\|Always ''Standard Method''. //This setting cannot be changed.//\|
	+	\|//Delete upon delivery//\|If //enabled//, the original message will be automatically deleted after it has been successfully forwarded. If //disabled//, the original message will remain in the mailbox until it is manually deleted.\|
	+	\|//Initial delay//\|Minimum time, in minutes, to wait after the triggering event before processing the template.\|
	+	\|//Retry interval//\|Minimum time, in minutes, to wait after a failed delivery attempt before trying again.\|
	+	\|//Do not exceed//\|Maximum number of times to attempt delivery, including the initial attempt.\|
	+
	+	<WRAP round important 75%>
	+	If more than one template is assigned to the mailbox, the //delete upon delivery// option may cause the messages to be deleted before all templates are processed.
	+	</WRAP>
	+
	+	===== Schedule =====
	+
	+	These settings define the schedule that determines when the template is active and when it is not.
	+
	+
	+	\|< 85% 15% >\|
	+	^Setting^Description^
	+	\|//Days//\|Select the days of the week that this template can be active. //Template will be inactive for the entire day for any days not selected.//\|
	+	\|//Starting at//\|The time at which the template starts being active on the days selected.\|
	+	\|//Ending at//\|The time at which the template stops being active on the days selected.\|
	+
	+	===== How It Works =====
	+
	+	Message delivery templates are used to forward messages to another mailbox, or to an email address, based on a schedule.
	+
	+	Forwarding messages to the subscriber's email address is what the VeMail feature is all about. The 7.00 provides a predefined global message delivery template specifically for this purpose: //Auto Forward to Email//. This template will automatically forward all messages to the subscriber's //Email 0// address, 24 hours a day, seven days a week.
	+
	+	==== Time Window ====
	+
	+	The time window determines when the template is active and when it is not. For any time that falls outside of the time window, the template is inactive and has no effect on the mailbox whatsoever. The only caveat to the time window is the //Template Disabled// check box on the Message Delivery page in the mailbox editor; if the template is marked as disabled, then it is considered inactive at all times on all days regardless of the time window settings for the template itself.
	+
	+	The time window for a message delivery template follows these rules:
	+	- For any day of the week that is not selected, the template will be inactive for that entire 24-hour period.
	+	- For any day of the week that is selected, the template will be active from the starting time until the ending time (inclusive) and otherwise inactive.
	+	- If the starting and ending times are both 12:00 a.m., then the template is active for the entire day.
	+
	+	==== Application ====
	+
	+	Message delivery templates are applied at the time the message is received by the mailbox, subject to the //Initial Delay// setting. They are applied in the order listed, from the top down.
	+
	+	All active templates will be applied, not just the first active template in the list.
	+
	+	==== Rollover ====
	+
	+	Message delivery templates __do not__ support rollover. If a message arrives during a time when no message delivery template is active then the message will not be forwarded at all. This differs from notification templates where a notification would be scheduled for the first template to become active as long as there is at least one assigned template that will become active.
	+
	+	===== Why Use It =====
	+
	+	The primary use of message delivery templates is for VeMail, to forward a copy of each message to the subscriber's email address. You can have just urgent messages forwarded or all messages. You can even configure it to delete the message out of the mailbox after it has successfully sent the email.
	+
	+	Another common use is to forward a copy of the message to one or more other mailboxes. In the past, this has been used to distribute incoming messages to multiple people. However, with the addition of //distribution// mailboxes, you can now accomplish the same thing by simply directing the callers into a distribution mailbox whose list contains the subscriber mailboxes you want to receive the messages.

Notifications

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:27+00:00

2026/10/02 13:49	current
Line 1:	Line 1:
	+	{{indexmenu_n>40}}
	+	====== Notifications =====
	+
	+	A notification template is used to ensure that a selected outdial process is performed whenever a selected triggering event occurs during a time when the template is active.
	+
	+	The most common example is to trigger the MWI process to turn on the message light whenever a new message is received in the mailbox, or to turn off the message light whenever the subscriber has saved or deleted the last message in the new message queue. If you want to automatically forward a message on receipt, use a message delivery template.
	+
	+	Whether you are editing an existing template or creating a new one (global or custom), the system will display a dialog similar to the one shown below. The only significant difference is the text displayed in the title bar.
	+
	+	{{:images:vs7:manual:tpl-notif-mwion.png?nolink\|}}
	+
	+	To save your changes, click OK. If you are creating a new template, you will be prompted to enter a filename before the data is saved; if you are creating a custom template, the filename is created for you. In any case, Cancel will discard any changes not previously saved.
	+
	+	===== Definition =====
	+
	+	These settings define what triggers the notification, what type of notification it is, and how often to retry on failure.
	+
	+	\|< 90% 20% >\|
	+	^Setting^Description^
	+	\|//Event//\|The event that triggers the notification.\|
	+	\|//Address//\|The address used for the notification (where relevant).\\ \\ If the address number is set to ''ALL'', then a notification will be generated for every address of the selected type that has been defined.\|
	+	\|//Technique//\|The technique used for the notification.\|
	+	\|//Light for every message//\|Only used if the technique is //Message Waiting Indicator On.// \\ \\ If //enabled//, a MWI notification will be sent for every new message received.\\ If //disabled//, a notification is only sent for the first new message received.\|
	+	\|//Method//\|The method used to perform the notification. Only relevant for MWI notifications.\\ \\ //Address// field must be set to //MWI// or else this field will be disabled.\|
	+	\|//Initial Delay//\|Time to wait after the triggering event before attempting the notification, in minutes.\|
	+	\|//Retry Interval//\|Time to wait after an attempt fails before trying again, in minutes.\|
	+	\|//Do not exceed//\|Maximum number of attempts, including the initial attempt.\|
	+
	+	==== Events ====
	+
	+	The following is the list of possible trigger events from which you can select when setting the //Event// property above.
	+
	+	\|< 90% 20% >\|
	+	^Event^Description^
	+	\|//all messages//\|Triggers on the receipt of any new message, regardless of message type.\|
	+	\|//disk storage//\|Triggers when free disk space has fallen below 25% of the total disk space.\|
	+	\|//failed wakeup call//\|Triggers when a wakeup call remains unanswered after the maximum number of retries.\|
	+	\|//listen to new messages//\|Triggers when subscriber starts listening to the new message queue.\|
	+	\|//login request//\|Triggers when subscriber logs into the mailbox.\|
	+	\|//mailbox log off//\|Triggers when the subscriber exits the mailbox.\|
	+	\|//no unread messages//\|Triggers when the subscriber has listened to all new messages, even if they were skipped and not saved or deleted.\|
	+	\|//normal messages//\|Triggers on the receipt of a new, normal voice message.\|
	+	\|//relay page//\|Triggers in response to a relay page SDA menu action.\|
	+	\|//reminder//\|Triggers at the wakeup time scheduled for a guest mailbox. Requires use of the Wakeup Call technique, as listed in the next section.\|
	+	\|//restrict Phone//\|Triggers in response to a command from the PMS or InnDesk to change a room phone's restriction status.\\ \\ //Only valid for the Vodavi PBX, which uses inband DTMF to signal a change in phone restriction status.//\|
	+	\|//retrieve new messages//\|Triggers when the subscriber has saved or deleted all new messages.\|
	+	\|//unrestrict phone//\|Triggers in response to a command from the PMS or InnDesk to change a room phone's restriction status.\\ \\ //Only valid for the Vodavi PBX, which uses inband DTMF to signal a change in phone restriction status.//\|
	+	\|//until no messages//\|Triggers as long as there are any messages at all, including saved or archived messages.\|
	+	\|//urgent messages//\|Triggers on the receipt of a new, urgent voice message.\|
	+	\|//while new messages//\|Triggers as long as there are any new messages.\|
	+
	+	==== Techniques ====
	+
	+	The following is the list of possible techniques from which you can select when setting the Technique property above.
	+
	+	\|< 90% 20% >\|
	+	^Technique^Description^
	+	\|//Alert Operator//\|Calls the operator extension assigned to the same tenant as the subscriber's mailbox and plays a message to alerting them to a failed wakeup call.\\ \\ Use with the //failed wakeup call// event only.\|
	+	\|//Alert Operator Email//\|Sends a failed wakeup call email alert to the //Email 0// address for the operator assigned to the same tenant as the subscriber's mailbox.\\ \\ Use with the //failed wakeup call// event only.\|
	+	\|//Confirmed Verbal Notification//\|Calls the specified address and immediately plays a prompt asking the called party to press 1 to accept the call.\\ \\ Using the //Confirmed// settings on the COS template's Transfers tab, it will wait a certain length of time for a DTMF digit and, if none is received, will repeat the message up to a maximum number of times.\\ \\ If a valid DTMF is pressed within the time limit, the rest of the notification be performed; otherwise, it will be assumed to be RNA and will reschedule per the template settings.\|
	+	\|//Email Notification//\|Sends an email to the specified email address. Intended for message reception events only. Requires that //Address// be set to an //Email// address.\\ \\ This is not VeMail. A copy of the message is not attached.\|
	+	\|//Message Waiting Indicator Off / On//\|Sends the MWI off or on code using the specified Method and Address.\|
	+	\|//Pager Notification//\|Dials the specified address, assuming it to be a pager. On connect, it dials the associated pager display string.\|
	+	\|//Relay Page//\|Dials the specified address, assuming it to be a pager. On connect, it dials the caller's callback number as the pager display string.\|
	+	\|//Restrict Phone//\|Dials the inband digits to restrict a phone. The //Address// field should be ''Office Extension''. //Used on hospitality systems integrated with a Vodavi PBX.//\|
	+	\|//Unrestrict Phone//\|Dials the inband digits to unrestrict a phone. The //Address// field should be ''Office Extension''. //Used on hospitality systems integrated with a Vodavi PBX.//\|
	+	\|//Verbal Message Notification//\|Dials the specified address as a phone number. On connect, plays prompts to the called party. Differs from //Confirmed Verbal Notification// in that it uses call progress to determine if the call is answered.\|
	+	\|//Wakeup Call//\|Dials the specified address and, on connect, plays a wakeup announcement. Dialing method and other settings are configured on the Wakeup Call tab in the COS.\|
	+
	+	==== Methods ====
	+
	+	The following is the list of available methods for MWI notification. For all other notification types, the method is irrelevant. Address must be type MWI, otherwise method will default to //Inband//.
	+
	+	<WRAP round info 75%>
	+	The //PMS Only// and //+ PMS// options are only valid if the PMS protocol supports sending MWI notifications. or a voice message count. to the PMS. Not all protocols support this.
	+	</WRAP>
	+
	+	\|< 85% 15% >\|
	+	^Method^Description^
	+	\|//Inband, Inband + PMS//\|Dials DTMF codes over the phone. //This is the default method.//\\ \\ If //Inband + PMS// is selected, a message count or MWI status packet will be sent to the PMS as well, assuming the PMS protocol supports it.\|
	+	\|//PBXLINK, PBXLINK + PMS//\|Sends MWI notifications via a PBX Link connection (if the link protocol supports it).\\ \\ If //PBXLINK + PMS// is selected, a message count or MWI status packet will be sent to the PMS as well, assuming the PMS protocol supports it.\|
	+	\|//Serial, Serial + PMS//\|Sends MWI notifications via a serial connection to the PBX.\\ \\ Do not use this for the Hitachi PBX; it connects to the 7.00 as a PMS link not a PBX link.\\ \\ If //Serial + PMS// is selected, a message count or MWI status packet will be sent to the PMS as well, assuming the PMS protocol supports it.\|
	+	\|//SIP, SIP + PMS//\|The system sends a SIP notify packet to the PBX and lets the PBX notify the endpoint (phone). SIP only.\\ \\ If //SIP + PMS// is selected, a message count or MWI status packet will be sent to the PMS as well, assuming the PMS protocol supports it.\|
	+	\|//TAPI, TAPI + PMS//\|The system notifies the PBX via a TAPI link. This is only supported when integrating with an Avaya IP Office via TAPI.\\ \\ If //TAPI + PMS// is selected, a message count or MWI status packet will be sent to the PMS as well, assuming the PMS protocol supports it.\|
	+	\|//PMS Only//\|Send MWI notifications to the PMS only.\\ \\ //Use this option only if the PMS controls the MWI lights or for the Hitachi PBX (which connects to the 7.00 as a PMS link).//\|
	+
	+	===== Schedule =====
	+
	+	These settings define the schedule that determines when the template is active and when it is not.
	+
	+	\|< 85% 15% >\|
	+	^Property^Description^
	+	\|//Days//\|Select the days of the week that this template can be active. //Template will be inactive for the entire day for any days not selected.//\|
	+	\|//Starting at//\|The time at which the template starts being active on the days selected.\|
	+	\|//Ending at//\|The time at which the template stops being active on the days selected.\|
	+
	+	===== How It Works =====
	+
	+	Notification templates are used to control when certain mailbox events (such as receiving a new message) should trigger a particular action (such as notifying the subscriber that he or she has a new message). The 7.00 provides several different events that can trigger a notification, as well as several different actions that can be taken. Most of these actions involve outdialing to one of the defined mailbox addresses, although there are a few exceptions. One thing that should be noted, however, is that notifications do not actually do anything with a message itself; for that type of action (e.g., auto-forwarding to email), use a Message Delivery template.
	+
	+	==== Time Window ====
	+
	+	The time window determines when the template is active and when it is not. For any time that falls outside of the time window, the template is inactive and will not be triggered. The only exception to the time window is the //Template Disabled// setting on the Notifications property page; if the template is marked as disabled, then it is considered inactive at all times on all days regardless of the time window settings for the template itself.
	+
	+	The time window for a notification template follows these rules:
	+	- For any day of the week that __is not__ selected, the template will be inactive for that entire 24-hour period.
	+	- For any day of the week that __is__ selected, the template will be active from the starting time until the ending time (inclusive) and otherwise inactive.
	+	- If the starting and ending times are both 12:00 a.m., then the template is active for the entire day.
	+
	+	==== Application ====
	+
	+	Notifications are normally scheduled when the event that triggers them occurs, but are only scheduled for templates that are active (per the time window). If there are multiple templates assigned to the mailbox for which the triggering event is relevant and none of them is currently active, then the notification will be scheduled for the starting time of the earliest relevant template. //Thus, even if the template is configured to have no initial delay, the notification may still be delayed because it has to wait until the template becomes active.//
	+
	+	For example, if a caller leaves a message at 4:30 a.m. and the earliest time at which a relevant notification template becomes active is 7:00 a.m., then the notification will be scheduled for 7:00 a.m., even though that is two and half hours after the message was received. Note also that even if there is another template that is also triggered by new messages but does not become active until 8:00 a.m., it will not be triggered by the message received at 4:30 a.m. //The system will only trigger the first template for which the event is relevant.//
	+
	+	On the other hand, if the message is received at 8:05 a.m., then both notifications would occur (assuming that both are still active). //Every template that is active when a relevant event occurs will be triggered as long as the combination of the notification technique and notification address is unique. It is only when there is no active template that the system schedules the notification only for the template that will become active first.//
	+
	+	==== Rollover ====
	+
	+	If the first attempt at a notification fails-—e.g., receiving no answer on a verbal notification attempt—-the system will retry as specified in the template. Once the maximum number of attempts is reached, it will stop, even if every attempt has failed. If the time window for the template expires before every attempt has been made, the next attempt will be scheduled for the start of the next time window. This is called //rollover//. When rollover occurs, the counter for the number of attempts is reset to zero.
	+
	+	==== Cancellation ====
	+
	+	Once the subscriber logs into the mailbox, all pending notifications that are based on receipt of new messages are canceled.
	+
	+	===== Why Use It =====
	+
	+	Notifications are used for a variety of applications. The chief use is to light the MWI lamp when a new message arrives in the mailbox and to turn it off when the last new message has been saved or deleted. They are also used to notify the subscriber via pager or telephone (often a cell phone) when new or urgent messages have arrived, and to send wakeup calls to guests in a hospitality environment.

Question and Answer

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:27+00:00

2026/10/02 13:49	current
Line 1:	Line 1:
	+	{{indexmenu_n>50}}
	+	====== Question and Answer ======
	+
	+	A Question and Answer template is used in conjunction with a QA mailbox (no other mailbox type can use them). It defines the script that will be followed when a call is forwarded to the mailbox. This script replaces the usual process of applying the call routing plan, playing the greeting, and applying the SDA. None of those things applies to a QA mailbox; it always follows the assigned script. In fact, QA mailboxes do not even have normal mailbox greetings, nor do they allow call routing templates or SDA templates to be assigned to them.
	+
	+	QA scripts may be either local (custom) or global. A global script can be used by any QA mailbox; a custom script can only be used by the mailbox in which it is created. Global scripts are created from the Template Manager (accessed by selecting Templates \| Question and Answer from the main menu); custom scripts are created from the QA Script property page of the mailbox.
	+
	+	Creating a QA script is a two-step process:
	+	- Record the QA prompts
	+	- Edit the QA script
	+
	+	It is recommended that you record the prompts first so that you can then use them in designing the script.
	+
	+	===== Record the QA Prompts =====
	+
	+	To record the prompts for a //custom// QA script, follow these steps:
	+	- Login to the QA mailbox in which the custom script will be created.
	+	- Press ''4'' to record greetings.
	+	- Press ''1'' to change question and answer greetings.
	+	- Enter the greeting number, followed by the ''#'' key. This can be any number you like, up to 9 digits (if you enter 9 digits, you don't have to press # at the end).
	+	- Press ''1'' to record the greeting.
	+	- Record after the tone; press ''#'' when finished.
	+	- Press ''1'' to re-record, ''2'' to append or ''*'' to accept.
	+	- Repeat steps 4 through 7 for each greeting (prompt) you want to record. There is no limit to how many QA prompts you can record.
	+
	+	To record the prompts for a //global// QA script, follow these steps:
	+	- At the auto attendant greeting, dial ''%%**%%97#'' to access the administrator menus.
	+	- Enter the administrator password (default is ''8000#'').
	+	- Press ''7'' to change question and answer greetings.
	+	- Enter the QA number, followed by the ''#'' key. If creating a new QA script, select any number you want that isn't already in use, up to 9 digits (if you enter 9 digits, you don't have to press # at the end).
	+	- Enter the greeting number, up to 9 digits, followed by the ''#'' key. If you enter a 9 digit number, you don't need to press # at the end.
	+	- Press ''1'' to record the greeting.
	+	- Record after the tone; press ''#'' when finished.
	+	- Press ''1'' to re-record, ''2'' to append or ''*'' to accept.
	+	- Repeat steps 6 through 9 for each greeting (prompt) you want to record. There is no limit to how many QA prompts you can record.
	+
	+	One thing to consider when recording QA prompts is that you do not have to get a response from the caller after every prompt (whether recording a verbal response or getting a DTMF response). You can, for example, record an introductory prompt that will play before the first question and a concluding prompt to play after the response to the last question.
	+
	+	Once you have recorded all of your prompts, you are ready to edit the script.
	+
	+	===== Edit the QA Script =====
	+
	+	After you have recorded the prompts, you are ready to edit the script. Although the editing process is essentially the same for both custom and global scripts, there are some slight differences, so we'll look at each in turn.
	+
	+	==== Edit Custom Script ====
	+
	+	To edit a custom script:
	+	- Open the mailbox for editing.
	+	- Select the QA Script property page.
	+	- In the //Script ID number// selection box, select ''Custom'' if it is not already selected.
	+
	+	The figure below shows a custom QA script being edited:
	+
	+	{{:images:vs7:manual:tpl-qa-custom.png?nolink\|}}
	+
	+	To save your changes, click OK or Apply. To discard them, click Cancel.
	+
	+	==== Edit Global Script ====
	+
	+	To edit a global script, follow these steps:
	+	- Select Templates \| Question and Answer from the main menu.
	+	- In the Template Editor, select the QA template (script ID) that you wish to edit.
	+	- Click Edit to open the selected script for editing.
	+
	+	The figure below shows a global script (with an ID of 301) being edited:
	+
	+	{{:images:vs7:manual:tpl-qa-global.png?nolink\|}}
	+
	+	To save any changes, click Save. To discard them, click Cancel.
	+
	+	==== Options ====
	+
	+	An Options button appears on both dialogs. For the mailbox QA Script property page, the button is in the upper left corner. For the global QA script editor, the button is in the lower left corner. In either case, the Options dialog that is opened when you click the button is the same, as shown below.
	+
	+	{{:images:vs7:manual:tpl-qa-actions.png?nolink\|}}
	+
	+	The settings displayed in this dialog are used to determine how to proceed after the caller has completed the QA script.
	+
	+	\|< 90% 20% >\|
	+	^Setting^Description^
	+	\|//If a flagged option was selected//\|Defines the action to take after the QA script is completed in the case where the caller responded to a CHOICE with a DTMF that was flagged; the purpose of flagging a CHOICE option is to have the system take a different action than the default action.\\ \\ There are two possible actions you can select: <WRAP>
	+	* Transfer will transfer the caller to the extension you specify.
	+	* Use Default will take the action defined in the //Default action// setting.
	+	</WRAP>\|
	+	\|//Default action//\|Defines the action to take after the QA script is completed, in all cases except when a flagged option was selected by the caller and the //If a flagged option was selected// setting is set to //Transfer//.\\ \\ There are four possible actions from which you can choose: <WRAP>
	+	* Attendant will redirect the caller back to the auto attendant main greeting.
	+	* Disconnect will simply hang up the call.
	+	* Operator will transfer the caller to the operator extension for the current tenant.
	+	* Transfer will transfer the caller to the extension you specify.
	+	</WRAP>\|
	+	\|//Save partial session//\|If //enabled//, any answers the caller recorded will be concatenated into a single message recording and delivered to the mailbox, even if the caller hung up before answering all the questions.\\ \\ If //disabled//, the caller must answer all questions; incomplete responses will be discarded.\\ \\ For survey-style QA scripts (i.e., those using CHOICE and GET DTMF commands), this setting is ignored and partial survey data is always saved.\|
	+
	+	==== Script Editing Commands ====
	+
	+	There are six command buttons you can use to edit the script, summarized in the table below and then described in detail in the following sections:
	+
	+	\|< 85% 15% >\|
	+	^Button^Description^
	+	\|//Play//\|Play a QA prompt recording.\|
	+	\|//Record//\|Record a response from the caller.\|
	+	\|//Edit//\|Repeats the caller's response and allows him or her to accept it, append to it or discard it and start over. //If the Edit command is used, it must be the last command in the script.//\|
	+	\|//Choice//\|Waits for the caller to press a single DTMF key. //This option is only available if the Survey IVR feature has been licensed.//\|
	+	\|//Get DTMF//\|Waits for the caller to enter one or more DTMF digits. //This option is only available if the Survey IVR feature has been licensed.//\|
	+	\|//Remove//\|Removes the last command from the script.\|
	+
	+	<WRAP round info 75%>
	+	Commands are always added to the end of the script and each click of the Remove command will delete the last command entered.
	+	</WRAP>
	+
	+	=== Play ===
	+
	+	Click Play to add a PLAY command as the next line of the script. This will open the Prompt Selection dialog, shown below, from which you can select the prompt file you want to be played at the given point in the script.
	+
	+	{{:images:vs7:manual:tpl-qa-prompt-select.png?nolink\|}}
	+
	+	All valid existing prompts are listed in the table. In the example above, there is only existing prompt, ''1.wav''. For each prompt, the table displays the filename, the date and time it was recorded, and the full path to where the actual file resides.
	+
	+	To add a PLAY command using one of the existing prompts, select it in the list and click OK.
	+
	+	To assign a prompt that is in a different file folder, click Browse and navigate to the folder that contains the prompt. Select the file and click Open to add it to the list. Then select it in the list and click OK to add the PLAY command to the script.
	+
	+	<WRAP round important 75%>
	+	If you assign a prompt file from a different folder using the //Browse// option, you will not be able to re-record it using the QA mailbox. If you want the ability to re-record the prompt over the phone, use the Import option instead, as it will copy the selected prompt to the QA script's folder.
	+	</WRAP>
	+
	+	To import a pre-recorded prompt from a different file folder so that you can use it in the QA script and have the ability to re-record it over the phone, click Import. Use the Open dialog to navigate to the folder containing the prompt. Select the prompt and click Open to import it. A copy of the selected file will be added to the QA script's own folder and will be renamed to the next available number, starting at 0. For example, if there are currently no prompt files in the QA script's folder and you import a file, it will be named ''0.wav''. The next one will be ''1.wav'', then ''2.wav'', and so on. Select the imported prompt in the list and click OK to add the PLAY command.
	+
	+	Finally, if you haven't yet recorded the prompts but want to create the script with temporary placeholder files, click Generate. This will copy a blank prompt file into the folder, naming it with the next available number, starting at 0. For example, if there are no prompts currently in the script's folder and you click Generate, it will create a file named ''0.wav''. The next one will be ''1.wav'', then ''2.wav'', and so on. Select the generated prompt in the list and click OK to add the PLAY command.
	+
	+	=== Record ===
	+
	+	Click Record to add a RECORD command to end of the script.
	+
	+	A RECORD command causes the system to record a response from the caller. There is no additional prompting; the system merely plays a beep and starts recording. The caller can press either ''#'' or ''*'' to halt the recording. Each subsequent response is appended to the end of the recording. At the end of the script, the recording, which comprises all responses from the caller, is deposited in the mailbox as a new message.
	+
	+	=== Edit ===
	+
	+	Click Edit to add an EDIT command to the end of the script. This command should only be used once and only at the end of the script, after all question-response pairs have been entered. It will play back all of the caller's responses to the caller and allow him or her to accept it, append to it, or discard it and start over.
	+
	+	=== Choice ===
	+
	+	//This option is only available if the Survey IVR feature has been licensed for your system.//
	+
	+	Use this command to get a single-digit DTMF response from the caller. When you select this option, the Set Valid Survey Options dialog is displayed, as shown below.
	+
	+	{{:images:vs7:manual:tpl-qa-valid-options.png?nolink\|}}
	+
	+	Click the buttons under //Enabled options// to indicate which DTMF keys are valid responses to the question posed by the previous PLAY command (a CHOICE command should always be preceded by a PLAY command).
	+
	+	For any key you select under //Enabled options//, you can also select it under //Flag these options//. What this means is that if the caller responds to the question by pressing one of the flagged DTMF digits, then at the end of the call the //flagged action// will be taken instead of the //default action// (see the Options section, above). One possible use of this feature: while taking a customer satisfaction survey, you may want to have any caller who responds to a question with a choice indicating 'poor' or 'dissatisfied' to be transferred to a live person so that their dissatisfaction can be addressed promptly, while for any generally satisfied callers you just want to disconnect at the end.
	+
	+	After configuring both sections as desired, click OK. The system will append a line to the end of the script consisting of the CHOICE keyword, a space, a string of digits and, optionally, another space followed by another string of digits. The first set of digits are the ones you only selected for //Enabled options//. The second set are those you also selected for //Flag these options//. For example, if you enable keys 1 through 4 and then select keys 3 and 4 under //Flag these options//, the line added to the script would read: ''CHOICE 12 34''.
	+
	+	When the system processes a CHOICE command, it will wait for a single DTMF digit from the caller. If an invalid response is made, it will state that the response was not valid, repeat the previous PLAY command, and then re-execute the CHOICE command. When a valid response is entered, the key pressed is added to the data record for the call and the system will proceed to the next command in the script. If the response was a flagged key, the system will note that a flagged response has been made by the caller and it will take appropriate action at the end of the script.
	+
	+	<WRAP round info 75%>
	+	It is not necessary to include an option for repeating the question; the caller can always press # to repeat the prompt.
	+	</WRAP>
	+
	+	=== Get DTMF ===
	+
	+	Use the GETDTMF command to get a multiple-digit response from the caller, such as an ID number. When you select this option, the Set Number of Digits to Get dialog is displayed, as shown below.
	+
	+	{{:images:vs7:manual:tpl-qa-getdtmf.png?nolink\|}}
	+
	+	Enter the minimum and maximum number of digits the caller can enter. //The maximum value cannot be less than the minimum value.// If the number entered by the caller must be of an exact length, set both values to the same number (as seen in the figure above).
	+
	+	When processing a GETDTMF command, if the caller does not enter at least the minimum number of digits, the system will repeat what was entered and state that it is not valid. It will then repeat the previous PLAY command and re-execute the GETDTMF command. Once a valid response is received, it will add the digits entered to the data record and proceed to the next command in the script.
	+
	+	===== How It Works =====
	+
	+	When a call is directed into a QA mailbox (whether on ring no answer or busy, or because DND is enabled), it will immediately execute the QA script rather than perform the normal call processing (i.e., playing a greeting, employing an SDA menu, etc.). The QA script is processed line by line from the top down until it reaches the end of the script. At that point, it will save the recorded message (or the data record, if it is a survey-style QA) and then either disconnect, return to the auto attendant, transfer to an extension, or go to another mailbox; the actual action taken depends on the configuration of the Options settings.
	+
	+	There are two styles of QA that you can employ: //interview// and //survey//. There is no guarantee of proper functioning if the two types are mixed together in a single script.
	+
	+	==== Interview ====
	+
	+	The interview style of QA will typically alternate between playing a recorded question and then recording a response. At the end, all responses are concatenated together and saved as a single message in the mailbox. This style only uses the PLAY, RECORD and EDIT keywords, where the EDIT keyword would be used once, at the end, to allow callers to review their responses and either append a further statement or even start all over before the message is sent.
	+
	+	==== Survey ====
	+
	+	The survey style of QA uses the PLAY, CHOICE, and GET DTMF commands. A typical script will alternate between playing a greeting that contains a statement, question or instruction and then employing either the GET DTMF keyword (to get a multi-digit response) or the CHOICE keyword (to get a single-digit response). At the end, all the responses are concatenated together, separated by commas, along with a few other pieces of information such as the date and time, the mailbox number, the caller ID and the line number. This string is then added to a comma-separated value (CSV) data file.
	+
	+	<WRAP round info 75%>
	+	The interview style of QA is available on all systems by default, but the survey style must be licensed. If it is not, then the survey-specific keywords (CHOICE and GET DTMF) will not be available to you.
	+	</WRAP>
	+
	+	===== Why Use It =====
	+
	+	A QA mailbox is useless without a QA script for it to follow. QA mailboxes can be used for a number of purposes. For example, the interview style of QA can be used as a preliminary job interview to get basic information from a potential new hire. Or it can be used to prompt someone calling for technical support to leave their name, phone number, license or trouble-ticket number, and a basic description of the problem. The survey style can be used to collect customer satisfaction data by asking a series of questions to which the caller is instructed to respond by pressing a digit from 1 to 5 (where, for example, 1 means strongly agree or very satisfied and 5 means strongly disagree or very dissatisfied).
	+
	+	With the ability to take different actions at the conclusion of the QA script, there are undoubtedly many other applications for which a QA mailbox can be used.

Scheduled Events

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:27+00:00

2026/10/02 13:49	current
Line 1:	Line 1:
	+	{{indexmenu_n>60}}
	+	====== Scheduled Events ======
	+
	+	Scheduled event templates are used to alter mailbox behavior based on a schedule.
	+
	+	The auto attendant mailbox for the default tenant, 991, for example, uses a scheduled event template to override the active greeting and SDA menu. By default, it plays the night greeting (greeting 3) and uses the Night Menu Action SDA template, but the assigned scheduled event template, //Day Schedule//, overrides those settings during business hours so that it plays the day greeting (greeting 2) and uses the Day Menu Action SDA template instead. Other possible uses of scheduled event templates include: office closures, holidays, vacations, lunch hours, etc.
	+
	+	Whether you are editing an existing template or creating a new one (global or custom), the system will display a dialog similar to the one shown in the figure below. The main difference is in the text displayed in the title bar. The example below shows the dialog for creating a new global template.
	+
	+	{{:images:vs7:manual:tpl-evt-new.png?nolink\|}}
	+
	+	To save your changes, click OK. If you are creating a new template, you will be prompted to enter a filename before the data is saved. If you are creating a custom template, the filename is created for you. Clicking Cancel will discard any changes not previously saved.
	+
	+	===== Schedule Settings =====
	+
	+	These settings collectively are used to determine when the template is and is not active.
	+
	+	\|< 90% 20% >\|
	+	^Setting^Description^
	+	\|//Start Date, End Date//\|The template can only be active on or after the //Start Date//, up through, but not after, the //End Date//. //To make this template active regardless of the date, set both values to the same date (or select the Date Override option).//\|
	+	\|//Start Time, End Time//\|For any day on which the template can be active, it will only be active during the time interval defined by these settings.\\ \\ Set the //Start Time// to the time of day you wish this template to start being used and set the //End Time// to the time of day you wish the mailbox to revert back to its default behavior.\|
	+	\|//Date Override//\|If enabled, the date values are ignored and are both automatically set to January 1, 1700.\|
	+	\|//Holiday Override//\|If enabled, this template will override any other template assigned to the mailbox whenever the date and time fall within the time window during which this template is active.\\ \\ Normally, the first active template in the list (on the mailbox's Scheduled Events property page) is the one that is used. However, if any template has //Holiday Override// enabled, then it will be used instead, even it is at the bottom of the list.\\ \\ //If more than one template has Holiday Override enabled and both are active at the current time, the one listed first will be used.//\|
	+	\|//Restrict To//\|Select which days of the week this template can be active. //For any day not selected, the template will be inactive for the entire day, regardless of any other setting.//\|
	+
	+	===== When Active Change =====
	+
	+	These are the mailbox settings from the Owner Settings property page that are overridden while the template is active. Not all of them apply to all mailbox types. For example, neither //Extension, Use Call Blocking, Busy Greeting, RNA Greeting,// nor //Use Call Screening// apply to system mailboxes (like 991) because you cannot transfer to a system mailbox's extension, ever. Consequently, they always use the blocking greeting and always have call blocking (DND) enabled.
	+
	+	\|< 90% 20% >\|
	+	^Setting^Description^
	+	\|//SDA File//\|Select the SDA template to use when this template is active.\|
	+	\|//Extension//\|Enter the extension to use for transfers, MWI notifications, etc., while this template is active.\|
	+	\|//COS File//\|Select the class of service template to use when this template is active.\|
	+	\|//Use Call Blocking//\|Check this box to block transfers to the mailbox's extension while this template is active.\|
	+	\|//Call Blocking Greeting//\|Enter the greeting number to use for calls routed to the mailbox greeting due to call blocking.\|
	+	\|//Busy Greeting//\|Enter the greeting number to use for calls routed to the mailbox greeting due to a busy signal.\|
	+	\|//RNA Greeting//\|Enter the greeting number to use for calls routed to the mailbox greeting due to not being answered.\|
	+	\|//Use Call Screening//\|Check this box to enable call screening for any transfer that occurs while this template is active.\\ \\ Call screening is not available on SIP-enabled systems.\|
	+
	+	===== How It Works =====
	+
	+	A scheduled event is used to alter mailbox behavior based on a schedule. This could be as simple as changing the greeting or blocking transfers during a certain time period or as significant as changing the active SDA and COS templates.
	+
	+	There are two occasions at which the template may be applied:
	+	* At the start of the call (when the caller is attempting to transfer to the mailbox extension)
	+	* At the end of the call (when the mailbox greeting is about to be played).
	+
	+	==== Time Window ====
	+
	+	The time window determines when the template is active and when it is not. For any time that falls outside of the time window, the template is inactive and has no effect on the mailbox whatsoever. The only exception to the time window is the //Template Disabled// checkbox on the Schedule Events property page; if the template is marked as disabled, then it is considered inactive at all times on all days regardless of the time window settings for the template itself.
	+
	+	Determining the time window for a given day requires considering three things:
	+	* The current date
	+	* The current day of the week
	+	* The current time
	+
	+	The flowchart below shows the basic decision tree used by the system, moving from left to right, and is discussed in more detail in the following sub-sections.
	+
	+	{{:images:vs7:manual:fc-evt-decision-tree.png?nolink\|}}
	+
	+	=== Date Range and Date Override ===
	+
	+	The time window for a scheduled event is a little more complex than it is for the other template types, but that complexity allows for considerable flexibility. The first thing the system considers is whether the //Date Override// checkbox has been checked; if so, then it skips to the next step below.
	+
	+	If //Date Override// is not checked, then the system checks if the current date is either before the //Starting Date// or after the //Ending Date//. If it is, then the template is considered inactive; otherwise, the system continues to the next step.
	+
	+	=== Days of Week and Holiday Override ===
	+
	+	If the date checks out, then the next step is to consider the //Holiday Override// option. If it is enabled, then it doesn't matter what day of the week it is and the system will continue to the final step, checking the time.
	+
	+	If //Holiday Override// is not enabled, then the system will check if the current date falls on a day of the week that has been selected in the template. If not, then the template is inactive; otherwise, the system continues to the next step.
	+
	+	=== Time Range ===
	+
	+	The final check is whether the current time is before the //Starting Time// or after the //Ending Time//. If it is, then the template is inactive. Otherwise, the template is active.
	+
	+	<WRAP round info 75%>
	+	If you assign more than one template to a mailbox and they have overlapping time windows (such that both would be considered active during a given time period), the one listed __first__ will be the one that is used.\\ \\ In searching for an active template, the system moves from the top down, stopping at the first template that is considered active. __One exception__: if a template has the holiday override enabled, and is otherwise active, then that is the template that will be used, even if it is at the bottom of the list. If more than one active template has the holiday override enabled, the first one in the list has priority.
	+	</WRAP>
	+
	+	==== Start of Call ====
	+
	+	In this context, //start of call// is defined as either when a caller dials the extension from within the system (e.g., at the main greeting auto attendant or during some other mailbox's greeting) or when the caller selects an SDA action that has been defined to transfer to an extension. In either case, the first thing the system does is check for an active scheduled event. If one is found, its settings are temporarily applied to the mailbox. This is done even before it checks for a call routing plan.
	+
	+	A scheduled event cannot change the active call routing plan template, but if the active plan is defined to perform a transfer to the //Office Extension//, the scheduled event can alter the routing plan's behavior by changing the assigned COS template (which can change the transfer type), by enabling call screening, or by blocking transfers altogether. It can even temporarily change the //Office Extension// address so that transfers are directed to a different physical extension than the one assigned on the Owner Settings property page.
	+
	+	==== End of Call ====
	+
	+	In this context, //end of call// means right before the mailbox greeting is played. At this point, the system will again check for an active scheduled event and, if one is found, apply its settings. In this case, the scheduled event may temporarily change which greeting will be played and which SDA template will be used to interpret and handle any touch tone entries from the caller. A change of COS template may also affect whether the mailbox can take a message and whether that message can be marked urgent or private.
	+
	+	<WRAP round info 75%>
	+	If the mailbox type is not standard, some settings may be irrelevant. System mailboxes, for example, cannot take messages, regardless of how the assigned COS template is configured.\\ \\ //QA, distribution, group// and //guest// mailboxes do not use scheduled event templates at all.
	+	</WRAP>
	+
	+	===== Why Use It =====
	+
	+	The purpose of a scheduled event template is to change the behavior of a mailbox during a certain period of time. This can be useful in any number of ways. Here are two examples.
	+
	+	==== Example 1: Automated Attendant ====
	+
	+	The primary use of scheduled events in the 7.00 is to provide a means to have a day greeting (and associated SDA menu) and a night greeting (and menu) for the main greetings automated attendant mailbox, and to have the system switch between the two automatically based on a schedule.
	+
	+	Consider mailbox 991, the automated attendant mailbox for the default tenant. By default, it is configured to play the night greeting (greeting 3) and use the //Night Menu Action// SDA template. However, the assigned scheduled event template, //Day Schedule//, overrides these settings during business hours so that it plays the day greeting (greeting 2) and uses the //Day Menu Action// SDA template instead. By default, business hours are defined as 8:00 a.m. to 5:00 p.m., Monday through Friday, in perpetuity (i.e., the //Date Override// option is enabled).
	+
	+	==== Example 2: Subscriber Mailbox ====
	+
	+	Another possible use of a scheduled event would be to automate a subscriber's mailbox so that it allows transfers during business hours but blocks them after hours (so that callers do not have to wait for a ring no answer condition before being able to leave a message).
	+
	+	You can accomplish this by configuring the mailbox to have //Do Not Disturb On// enabled by default (on the Owner Settings property page) and use a scheduled event template to disable call blocking (DND) during business hours. And, as with the automated attendant example, you could even have it change which greeting is played. Call screening, too, is a feature that you might want on during the day but off after hours (assuming this is not a SIP system, which does not support call screening).
	+
	+	The caveat here is that the subscriber would have to be working relatively fixed, regular hours or the automatic call blocking might cause them to miss calls they would otherwise have answered.

Single Digit Actions

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:27+00:00

2026/10/02 13:49	current
Line 1:	Line 1:
	+	{{indexmenu_n>70}}
	+	====== Single Digit Actions ======
	+
	+	Single digit action (SDA) templates are used to define the menu options available to callers while the mailbox greeting is playing (and for a specified number of seconds after it ends).
	+
	+	If the greeting finishes playing with no interruption from the caller, the system consults the SDA template to determine how long to wait for a response. When the caller does press a DTMF digit, the system consults the assigned SDA template to determine what it should do. And if the caller never responds at all, the SDA defines what to do in that case also.
	+
	+	Whether you are editing an existing template or creating a new one (global or custom), the system will display a dialog similar to the one shown in the figure below. The main difference is in the text displayed in the title bar. The example below shows the //Night Menu Action// template.
	+
	+	{{:images:vs7:manual:tpl-sda-nightmenu.png?nolink\|}}
	+
	+	To save your changes, click OK. If you are creating a new template, you will be prompted to enter a filename before the data is saved. If you are creating a custom template, the filename is created for you. Clicking Cancel will discard any changes not previously saved.
	+
	+	<WRAP round info 75%>
	+	//Since custom SDA templates are edited directly in the mailbox (not in this dialog), you will also have the option to click //Apply//. In this case, it will act the same as clicking OK: the custom template will be saved.//
	+	</WRAP>
	+
	+	===== Action Assignments =====
	+
	+	In each of the selection boxes, you may either choose an action from the list, type in an extension number to transfer to, or leave it blank. A blank entry is considered invalid, although if it is not marked for single-digit entry the caller may type that digit as the first digit of an extension number. You can also manually type in the action, even if it is not shown in the list, as long as what you type in is a valid action. In some cases, even if you select the action from the list you may need to type in additional data such as a mailbox number.
	+
	+	==== Single Digit Entry (SD) ====
	+
	+	The //SD// checkbox indicates whether the given DTMF digit is restricted for single digit entry. If it is checked, the system will take the assigned SDA action immediately after the caller presses that digit, if it is the first digit pressed. If the //SD// checkbox is not checked, then the system will not act immediately after that digit is pressed but will wait to see if the caller is dialing an extension to transfer to. Since digits //A-D, *// and //#// cannot be used as part of an extension number, they are always acted upon immediately, so no //SD// checkbox is provided for them.
	+
	+	<WRAP round important 75%>
	+	If the //SD// checkbox is checked for any of the digits 1-9, the caller will not be able to dial any extension that starts with that number. For example, if //SD// is checked for the '5' key, then the caller cannot dial any extension number starting with '5'.
	+	</WRAP>
	+
	+	==== Action Keys / Events ====
	+
	+	The following keys and events can be assigned one of the available actions:
	+
	+	\|< 85% 15% >\|
	+	^Key / Event^Description^
	+	\|//0-9, *, #, A-D//\|DTMF digits to which an action can be assigned.\|
	+	\|//No Input//\|Event triggered if the caller does not press any DTMF digits within the time allotted.\|
	+	\|//Fax Freq//\|Deprecated. //Fax is not supported in this version.//\|
	+
	+	===== Other Settings =====
	+
	+	There are four additional settings listed below the //Action// settings. They are:
	+
	+	\|< 85% 15% >\|
	+	^Setting^Description^
	+	\|//Max DTMF//\|Maximum number of digits to wait for if the caller dials an extension number. This setting is ignored if single digit entry is in effect.\|
	+	\|//Wait for input//\|The number of seconds to wait for a DTMF digit after the greeting has finished playing.\\ \\ //After the first DTMF digit is received, the system will use the global inter-digit delay value to determine how long to wait for each additional DTMF digit. The default inter-digit delay value is 5 seconds.//\|
	+	\|//Restrict to single digit entry//\|Sets or clears all //SD// checkboxes.\\ \\ Enabling this option will also change the //Max DTMF// setting to 1 digit and will disable that field so it cannot be changed. This is done because setting //Max DTMF// to any value but 1 makes no sense if all //SD// checkboxes have been checked.\|
	+	\|//Disable translation on transfers//\|If checked, extension (mailbox) numbers entered by the caller will not be translated by the translation table.\\ \\ By default, extensions entered by callers are always run through the translation table before the transfer is attempted. This option disables translation for this template only.\\ \\ //If you assign the //Goto// or //Login// actions to the SDA and configure them to use inline translations, they will not be affected by this setting.// //Likewise, translations are never applied to SDA keys that are configured to transfer to a specified mailbox.//\|
	+
	+	===== Action Options =====
	+
	+	There are a number of possible actions that can be assigned to each DTMF digit or event. These actions can be divided into the follow general categories:
	+	* [[vs7:manual:admin:templates:sda:routing\|Call routing]] -- actions that can transfer the call to another extension or to an outside line.
	+	* [[vs7:manual:admin:templates:sda:directory\|Directory access]] -- actions that access a spell-by-name directory.
	+	* [[vs7:manual:admin:templates:sda:greet\|Greetings and Languages]] -- actions that change what greeting is played or change the active language for the caller.
	+	* [[vs7:manual:admin:templates:sda:isirsi\|ISI and RSI]] -- actions that invoke either the Inventory System Interface IVR or the Room Status Interface IVR or both.
	+	* [[vs7:manual:admin:templates:sda:misc\|Miscellaneous]] -- action that do not fit in any of the other categories.
	+	* [[vs7:manual:admin:templates:sda:paging\|Paging]] -- actions that trigger pager notifications.
	+	* [[vs7:manual:admin:templates:sda:login\|User login]] -- actions that allow the caller to login to a mailbox.
	+
	+	===== How It Works =====
	+
	+	The SDA menu goes into effect as soon as the mailbox greeting starts to play and continues until the //Seconds to wait for input// have elapsed following the conclusion of the greeting. As soon as the caller presses a key or the wait time is exceeded, the SDA template will take effect.
	+
	+	If a DTMF digit is received, the system will check if it is supposed to wait for additional digits. If so, it will use the inter-digit delay time to decide how long to wait for the next DTMF digit. As soon as it times out without receiving another DTMF, it will move to the next step: processing the DTMF it has received.
	+
	+	If it received more than one digit, it will check if the digits received represent a valid mailbox; if so, it will transfer to that extension (or goto that mailbox if the mailbox's assigned COS does not allow transfers or if the mailbox's DND setting is enabled). If the digits received are not a valid mailbox, it will state that fact and return to the auto attendant.
	+
	+	If only one digit was received, then the system will take the action assigned to that key. If no action was assigned (i.e., it was left blank), then the system will state that it was an invalid entry and will replay the greeting.
	+
	+	===== Why Use It =====
	+
	+	Single digit action (SDA) templates are used to offer various call routing options to the caller based on single-digit DTMF keypresses. They are most commonly used for the main greetings auto attendant mailbox(es) and for audiotext menus, but are also used for subscriber mailboxes to offer some basic options (such as allowing the caller to skip the greeting and go directly to recording a message). Every mailbox type, except //distribution, group// and //QA//, has at least a basic SDA template assigned (usually //Standard//).
	+
	+	//QA// mailboxes always behave according to the assigned QA script and therefore do not use SDA templates at all. //Distribution// and //group// mailboxes are vastly simplified mailboxes compared to the standard type. They use a built-in SDA that will return to the auto attendant if the ''*''key is pressed and on any other DTMF (or on //No Input//), will go directly to recording a message. Because this behavior is built-in, it cannot be changed by the user.
	+
	+	===== Inline Translations =====
	+
	+	Both the //Goto// and //Login// actions (and only those actions) support inline translations, which will take any DTMF entered by the caller, run it through the specified translation, and then perform the specified action on the translated number. An inline translation string has two parts: a single-character code indicating the type of translation to perform, followed by one or more digits used in performing the specified translation. The following table lists all supported translation codes. All examples assume the translation was assigned to the '4' key.
	+
	+	\|< 70% 10% 20% 20% 20% >\|
	+	^ Code ^ Meaning ^ Example ^ Caller's DTMF ^Result (mailbox)^
	+	\| + \| Add \| +1000 \| 412 \|1412\|
	+	\| - \| Subtract \| -100 \| 412 \|312\|
	+	\| A \| Append \| A3 \| 412 \|4123\|
	+	\| P \| Prepend \| P3 \| 412 \|3412\|
	+	\| R \| Replace \| R300 \| 412 \|300\|
	+	\| S \| Strip \| S1 \| 412 \|42\|
	+	\| M \| Mask \| M3%%*%%1\\ M5%%^%% \| 412\\ 412 \|34121\\ 512\|
	+
	+	As shown in the table above, there are seven translation types:
	+	* Add / Subtract -- adds (or subtracts) a given value to (from) the DTMF entered by the caller.
	+	* Append / Prepend -- adds one or more DTMF digits to the end of (or in front of) the DTMF digits entered by the caller.
	+	* Replace -- ignores whatever the caller entered, replacing it entirely with the specified DTMF digits.
	+	* Strip -- removes all occurrences of the specified DTMF digit(s) from the digits entered by the caller.
	+	* Mask -- uses the specified mask string to manipulate the DTMF digits entered by the caller, according to a strict set of rules detailed below.
	+
	+	<WRAP round info 75%>
	+	When using a translation, remember that the translation will be performed on all of the DTMF digits entered by the caller, including the initial DTMF key that indicates which menu action to perform.
	+	</WRAP>
	+
	+	==== Using the Mask Translation Type ====
	+
	+	Where the other translation types are straight-forward, the mask translation type requires further explanation. When you use this translation type, the additional data you provide is called a //mask// and is used by the system to manipulate the user-entered DTMF in order to produce the desired output string.
	+
	+	Masks use special characters to instruct the system on what to do with each character of the user input:
	+
	+	\|< 80% 10% >\|
	+	^ Character ^What it means^
	+	\| ''*'' \|Copy the next digit in the input string to the next position in the result string, as-is.\|
	+	\| ''^'' \|Discard the next digit in the input string.\|
	+	\| ''0''-''9'' \|Copy directly to the next position in the result string, as-is. Does not affect the input string at all.\|
	+
	+	When building the result string, the system will never copy a digit from the input string unless the mask tells it to do so. If the input string is ''12345'' and the mask is ''789'' then the result string will be ''789'', because the mask did not have any asterisks (*) to tell the system to copy any of the input digits to the result string.
	+
	+	Furthermore, each special character (* or ^) in the mask acts on one and only one digit in the input string. So with an input of ''12345'' and a mask of ''%%%%'', the result string would be ''12''. Any other character in the mask than those four special characters will be added to the result string in the next available position. Given the same input string but with a mask of ''%%0%%'', the result string would be ''12034''. Processing a non-special character in the mask does not cause the system to skip the next character in the input string.**
	+
	+	As suggested by the above examples, digits in the input string are dealt with one by one, from left to right, and once a digit has been copied or discarded, you cannot return to it later in the processing.

2026/10/02 13:49	current
Line 1:	Line 1:
	+	{{indexmenu_n>20}}
	+	====== Class of Service =====
	+
	+	Class of service (COS) templates define the mailbox attributes and subscriber permissions and restrictions that control the behavior of the mailbox. Only one COS may be assigned to a mailbox at a time, although a scheduled event template may override the assigned COS for mailboxes that support the use of scheduled events. The COS template is assigned to the mailbox on the Owner Settings property page.
	+
	+	Whether you opt to edit an existing template or create a new one, the system will display the COS Editor dialog as shown in the sections below. Other than what is displayed in the title bar and which buttons are available at the bottom, the dialog is the same in both cases.
	+
	+	To save changes to an existing template, click Save. This option is not available if you are creating a new template.\\
	+	To save a template with a new file name, click Save As.\\
	+	To close the editor without saving any changes, click Cancel.
	+
	+	COS settings are split across several property pages:
	+
	+	* [[vs7:manual:admin:templates:cos:general\|General]] -- Various settings that don't fit in the other categories.
	+	* [[vs7:manual:admin:templates:cos:recording\|Recording]] -- Settings related to sending and receiving voice messages.
	+	* [[vs7:manual:admin:templates:cos:playback\|Playback]] -- Settings related to message playback.
	+	* [[vs7:manual:admin:templates:cos:transfers\|Transfers]] -- Settings related to transferring.
	+	* [[vs7:manual:admin:templates:cos:vemail\|VeMail]] -- Settings related to the VeMail feature.
	+	* [[vs7:manual:admin:templates:cos:greetings\|Greetings / Prompts]] -- Settings related to playing mailbox greetings and prompts.
	+	* [[vs7:manual:admin:templates:cos:wakeup\|Wakeup Calls]] -- Settings related to the Wakeup Call feature (for guest mailboxes only).

2026/10/02 13:49	current
Line 1:	Line 1:
	+	{{indexmenu_n>40}}
	+	====== Notifications =====
	+
	+	A notification template is used to ensure that a selected outdial process is performed whenever a selected triggering event occurs during a time when the template is active.
	+
	+	The most common example is to trigger the MWI process to turn on the message light whenever a new message is received in the mailbox, or to turn off the message light whenever the subscriber has saved or deleted the last message in the new message queue. If you want to automatically forward a message on receipt, use a message delivery template.
	+
	+	Whether you are editing an existing template or creating a new one (global or custom), the system will display a dialog similar to the one shown below. The only significant difference is the text displayed in the title bar.
	+
	+	{{:images:vs7:manual:tpl-notif-mwion.png?nolink\|}}
	+
	+	To save your changes, click OK. If you are creating a new template, you will be prompted to enter a filename before the data is saved; if you are creating a custom template, the filename is created for you. In any case, Cancel will discard any changes not previously saved.
	+
	+	===== Definition =====
	+
	+	These settings define what triggers the notification, what type of notification it is, and how often to retry on failure.
	+
	+	\|< 90% 20% >\|
	+	^Setting^Description^
	+	\|//Event//\|The event that triggers the notification.\|
	+	\|//Address//\|The address used for the notification (where relevant).\\ \\ If the address number is set to ''ALL'', then a notification will be generated for every address of the selected type that has been defined.\|
	+	\|//Technique//\|The technique used for the notification.\|
	+	\|//Light for every message//\|Only used if the technique is //Message Waiting Indicator On.// \\ \\ If //enabled//, a MWI notification will be sent for every new message received.\\ If //disabled//, a notification is only sent for the first new message received.\|
	+	\|//Method//\|The method used to perform the notification. Only relevant for MWI notifications.\\ \\ //Address// field must be set to //MWI// or else this field will be disabled.\|
	+	\|//Initial Delay//\|Time to wait after the triggering event before attempting the notification, in minutes.\|
	+	\|//Retry Interval//\|Time to wait after an attempt fails before trying again, in minutes.\|
	+	\|//Do not exceed//\|Maximum number of attempts, including the initial attempt.\|
	+
	+	==== Events ====
	+
	+	The following is the list of possible trigger events from which you can select when setting the //Event// property above.
	+
	+	\|< 90% 20% >\|
	+	^Event^Description^
	+	\|//all messages//\|Triggers on the receipt of any new message, regardless of message type.\|
	+	\|//disk storage//\|Triggers when free disk space has fallen below 25% of the total disk space.\|
	+	\|//failed wakeup call//\|Triggers when a wakeup call remains unanswered after the maximum number of retries.\|
	+	\|//listen to new messages//\|Triggers when subscriber starts listening to the new message queue.\|
	+	\|//login request//\|Triggers when subscriber logs into the mailbox.\|
	+	\|//mailbox log off//\|Triggers when the subscriber exits the mailbox.\|
	+	\|//no unread messages//\|Triggers when the subscriber has listened to all new messages, even if they were skipped and not saved or deleted.\|
	+	\|//normal messages//\|Triggers on the receipt of a new, normal voice message.\|
	+	\|//relay page//\|Triggers in response to a relay page SDA menu action.\|
	+	\|//reminder//\|Triggers at the wakeup time scheduled for a guest mailbox. Requires use of the Wakeup Call technique, as listed in the next section.\|
	+	\|//restrict Phone//\|Triggers in response to a command from the PMS or InnDesk to change a room phone's restriction status.\\ \\ //Only valid for the Vodavi PBX, which uses inband DTMF to signal a change in phone restriction status.//\|
	+	\|//retrieve new messages//\|Triggers when the subscriber has saved or deleted all new messages.\|
	+	\|//unrestrict phone//\|Triggers in response to a command from the PMS or InnDesk to change a room phone's restriction status.\\ \\ //Only valid for the Vodavi PBX, which uses inband DTMF to signal a change in phone restriction status.//\|
	+	\|//until no messages//\|Triggers as long as there are any messages at all, including saved or archived messages.\|
	+	\|//urgent messages//\|Triggers on the receipt of a new, urgent voice message.\|
	+	\|//while new messages//\|Triggers as long as there are any new messages.\|
	+
	+	==== Techniques ====
	+
	+	The following is the list of possible techniques from which you can select when setting the Technique property above.
	+
	+	\|< 90% 20% >\|
	+	^Technique^Description^
	+	\|//Alert Operator//\|Calls the operator extension assigned to the same tenant as the subscriber's mailbox and plays a message to alerting them to a failed wakeup call.\\ \\ Use with the //failed wakeup call// event only.\|
	+	\|//Alert Operator Email//\|Sends a failed wakeup call email alert to the //Email 0// address for the operator assigned to the same tenant as the subscriber's mailbox.\\ \\ Use with the //failed wakeup call// event only.\|
	+	\|//Confirmed Verbal Notification//\|Calls the specified address and immediately plays a prompt asking the called party to press 1 to accept the call.\\ \\ Using the //Confirmed// settings on the COS template's Transfers tab, it will wait a certain length of time for a DTMF digit and, if none is received, will repeat the message up to a maximum number of times.\\ \\ If a valid DTMF is pressed within the time limit, the rest of the notification be performed; otherwise, it will be assumed to be RNA and will reschedule per the template settings.\|
	+	\|//Email Notification//\|Sends an email to the specified email address. Intended for message reception events only. Requires that //Address// be set to an //Email// address.\\ \\ This is not VeMail. A copy of the message is not attached.\|
	+	\|//Message Waiting Indicator Off / On//\|Sends the MWI off or on code using the specified Method and Address.\|
	+	\|//Pager Notification//\|Dials the specified address, assuming it to be a pager. On connect, it dials the associated pager display string.\|
	+	\|//Relay Page//\|Dials the specified address, assuming it to be a pager. On connect, it dials the caller's callback number as the pager display string.\|
	+	\|//Restrict Phone//\|Dials the inband digits to restrict a phone. The //Address// field should be ''Office Extension''. //Used on hospitality systems integrated with a Vodavi PBX.//\|
	+	\|//Unrestrict Phone//\|Dials the inband digits to unrestrict a phone. The //Address// field should be ''Office Extension''. //Used on hospitality systems integrated with a Vodavi PBX.//\|
	+	\|//Verbal Message Notification//\|Dials the specified address as a phone number. On connect, plays prompts to the called party. Differs from //Confirmed Verbal Notification// in that it uses call progress to determine if the call is answered.\|
	+	\|//Wakeup Call//\|Dials the specified address and, on connect, plays a wakeup announcement. Dialing method and other settings are configured on the Wakeup Call tab in the COS.\|
	+
	+	==== Methods ====
	+
	+	The following is the list of available methods for MWI notification. For all other notification types, the method is irrelevant. Address must be type MWI, otherwise method will default to //Inband//.
	+
	+	<WRAP round info 75%>
	+	The //PMS Only// and //+ PMS// options are only valid if the PMS protocol supports sending MWI notifications. or a voice message count. to the PMS. Not all protocols support this.
	+	</WRAP>
	+
	+	\|< 85% 15% >\|
	+	^Method^Description^
	+	\|//Inband, Inband + PMS//\|Dials DTMF codes over the phone. //This is the default method.//\\ \\ If //Inband + PMS// is selected, a message count or MWI status packet will be sent to the PMS as well, assuming the PMS protocol supports it.\|
	+	\|//PBXLINK, PBXLINK + PMS//\|Sends MWI notifications via a PBX Link connection (if the link protocol supports it).\\ \\ If //PBXLINK + PMS// is selected, a message count or MWI status packet will be sent to the PMS as well, assuming the PMS protocol supports it.\|
	+	\|//Serial, Serial + PMS//\|Sends MWI notifications via a serial connection to the PBX.\\ \\ Do not use this for the Hitachi PBX; it connects to the 7.00 as a PMS link not a PBX link.\\ \\ If //Serial + PMS// is selected, a message count or MWI status packet will be sent to the PMS as well, assuming the PMS protocol supports it.\|
	+	\|//SIP, SIP + PMS//\|The system sends a SIP notify packet to the PBX and lets the PBX notify the endpoint (phone). SIP only.\\ \\ If //SIP + PMS// is selected, a message count or MWI status packet will be sent to the PMS as well, assuming the PMS protocol supports it.\|
	+	\|//TAPI, TAPI + PMS//\|The system notifies the PBX via a TAPI link. This is only supported when integrating with an Avaya IP Office via TAPI.\\ \\ If //TAPI + PMS// is selected, a message count or MWI status packet will be sent to the PMS as well, assuming the PMS protocol supports it.\|
	+	\|//PMS Only//\|Send MWI notifications to the PMS only.\\ \\ //Use this option only if the PMS controls the MWI lights or for the Hitachi PBX (which connects to the 7.00 as a PMS link).//\|
	+
	+	===== Schedule =====
	+
	+	These settings define the schedule that determines when the template is active and when it is not.
	+
	+	\|< 85% 15% >\|
	+	^Property^Description^
	+	\|//Days//\|Select the days of the week that this template can be active. //Template will be inactive for the entire day for any days not selected.//\|
	+	\|//Starting at//\|The time at which the template starts being active on the days selected.\|
	+	\|//Ending at//\|The time at which the template stops being active on the days selected.\|
	+
	+	===== How It Works =====
	+
	+	Notification templates are used to control when certain mailbox events (such as receiving a new message) should trigger a particular action (such as notifying the subscriber that he or she has a new message). The 7.00 provides several different events that can trigger a notification, as well as several different actions that can be taken. Most of these actions involve outdialing to one of the defined mailbox addresses, although there are a few exceptions. One thing that should be noted, however, is that notifications do not actually do anything with a message itself; for that type of action (e.g., auto-forwarding to email), use a Message Delivery template.
	+
	+	==== Time Window ====
	+
	+	The time window determines when the template is active and when it is not. For any time that falls outside of the time window, the template is inactive and will not be triggered. The only exception to the time window is the //Template Disabled// setting on the Notifications property page; if the template is marked as disabled, then it is considered inactive at all times on all days regardless of the time window settings for the template itself.
	+
	+	The time window for a notification template follows these rules:
	+	- For any day of the week that __is not__ selected, the template will be inactive for that entire 24-hour period.
	+	- For any day of the week that __is__ selected, the template will be active from the starting time until the ending time (inclusive) and otherwise inactive.
	+	- If the starting and ending times are both 12:00 a.m., then the template is active for the entire day.
	+
	+	==== Application ====
	+
	+	Notifications are normally scheduled when the event that triggers them occurs, but are only scheduled for templates that are active (per the time window). If there are multiple templates assigned to the mailbox for which the triggering event is relevant and none of them is currently active, then the notification will be scheduled for the starting time of the earliest relevant template. //Thus, even if the template is configured to have no initial delay, the notification may still be delayed because it has to wait until the template becomes active.//
	+
	+	For example, if a caller leaves a message at 4:30 a.m. and the earliest time at which a relevant notification template becomes active is 7:00 a.m., then the notification will be scheduled for 7:00 a.m., even though that is two and half hours after the message was received. Note also that even if there is another template that is also triggered by new messages but does not become active until 8:00 a.m., it will not be triggered by the message received at 4:30 a.m. //The system will only trigger the first template for which the event is relevant.//
	+
	+	On the other hand, if the message is received at 8:05 a.m., then both notifications would occur (assuming that both are still active). //Every template that is active when a relevant event occurs will be triggered as long as the combination of the notification technique and notification address is unique. It is only when there is no active template that the system schedules the notification only for the template that will become active first.//
	+
	+	==== Rollover ====
	+
	+	If the first attempt at a notification fails-—e.g., receiving no answer on a verbal notification attempt—-the system will retry as specified in the template. Once the maximum number of attempts is reached, it will stop, even if every attempt has failed. If the time window for the template expires before every attempt has been made, the next attempt will be scheduled for the start of the next time window. This is called //rollover//. When rollover occurs, the counter for the number of attempts is reset to zero.
	+
	+	==== Cancellation ====
	+
	+	Once the subscriber logs into the mailbox, all pending notifications that are based on receipt of new messages are canceled.
	+
	+	===== Why Use It =====
	+
	+	Notifications are used for a variety of applications. The chief use is to light the MWI lamp when a new message arrives in the mailbox and to turn it off when the last new message has been saved or deleted. They are also used to notify the subscriber via pager or telephone (often a cell phone) when new or urgent messages have arrived, and to send wakeup calls to guests in a hospitality environment.