Configuring Advanced Voice Mail
Available Languages
Table Of Contents
Configuring Advanced Voice Mail
Configuring Integrated Messaging
Required Data for This Procedure
Required Data for This Procedure
Accessing Live-Reply from the TUI
Required Data for This Procedure
Configuring the Delivery of Future Messages
Backup and Restore of Future Messages
Displaying and Deleting Future Messages
Configuring Nonsubscriber Message Delivery
Configuring Nonsubscriber Message Delivery
Required Data for This Procedure
Configuring Broadcast Messages
Overview of Broadcast Messages
Configuring Broadcast Messages
Configuring a Group with Broadcast Privileges
Configuring the Broadcast Message Length and Expiration Time
Required Data for This Procedure
Enabling the MWI Lights for Broadcast Messages
Displaying Current Broadcast Messages
Displaying Broadcast Messages Received Per Mailbox
Displaying Broadcast Messages Received by the Voice-Mail System
Changing Broadcast Message Start and End Times
Disabling Broadcast Privileges for a Group
Disabling MWI Lights for Broadcast Messages
Configuring the Local-Broadcast Privilege
Configuring Restriction Tables
Configuring Restriction Tables
Configuring a Restriction Table
Configuring Advanced Voice Mail
Last Updated: June 21, 2007
This chapter contains the following procedures for configuring advanced Cisco Unity Express voice mail features:
•
Configuring IMAP (optional)
•
•
•
•
•
•
Configuring IMAP
This section discusses the following topics:
•
Overview
Integrated messaging on Cisco Unity Express is the convergence feature for voicemail and e-mail systems. It allows subscribers to have an integrated view of their e-mails and voice-mail messages from a single e-mail client using IMAP Version 4 rev1.
Subscribers can delete voice-mail messages or mark them as read or unread in a manner similar to e-mail messages.
The voice-mail messages are downloaded as attachments to e-mail messages. Subscribers can access the voice-mail messages over the network or can download them selectively. If the messages are downloaded, subscribers can play them locally using standard media players without requiring a connection to Cisco Unity Express.
Accessing voice-mail messages from general delivery mailboxes (GDMs) is not supported.
To access this feature, subscribers must be configured with the vm-imap privilege.
Note
IMAP Server
The IMAP server must be enabled on Cisco Unity Express before the server allows e-mail clients to connect. The feature can be enabled in the following modes:
•
Non-SSL is the least secure mode.
•
•
This mode allows both SSL and non-SSL connections.
If you change the connection mode on the IMAP server, verify the configuration on the clients, which may need to be changed to match the IMAP server configuration.
The maximum number of simultaneous IMAP connections is configurable up to 50.
Any changes to the IMAP configuration require a restart of the IMAP server. You can restart the IMAP server using the enable (IMAP) command-line interface (CLI) command or a graphical-user interface (GUI) option.
E-mail Client Considerations
The following e-mail clients are supported:
•
•
•
•
•
•
•
Note
To connect to Cisco Unity Express, configure the e-mail client to accept the user ID and password of the Cisco Unity Express subscriber.
Note
If this feature is enabled in SSL mode only, verify that the e-mail client is configured to use SSL connections to the IMAP server.
The same subscriber can connect to Cisco Unity Express from one or more e-mail clients using one or more connection types (SSL or non-SSL). Each session counts against the maximum number of connections allowed to the IMAP server.
Subscribers cannot retrieve the following types of messages from their personal mailboxes:
•
•
The voice-mail messages are downloaded as .wav attachments to the Inbox folder of the e-mail clients.
If a subscriber receives a new message or saves a voice-mail message in the Inbox folder, the Cisco Unity Express retains the message in its database. If mandatory message expiry is enabled on Cisco Unity Express, the message is subject to the expiry timer.
If a subscriber moves a voice-mail message from the Inbox folder to another folder on the e-mail client, Cisco Unity Express deletes the message from its database. Mandatory message expiry would not affect that message.
Note
Cisco Unity Express supports the following operations on the e-mail clients:
•
The Mark Read operation on the e-mail client is equivalent to Message Save on the voice-mail system. Similarly, the Mark Unread on the e-mail client is equivalent to the Mark New on the voice-mail system.
•
•
Errors displayed on the e-mail clients are dependent on the client implementation. See the client documentation for more information.
Configuring Integrated Messaging
Follow this procedure to configure the Integrated Messaging capability.
Prerequisites
The system must have a default security certificate and private key installed before SSL connections are permitted on Cisco Unity Express. Use the show crypto key command to display the system default certificate-key pair. If no default pair exists, follow the procedure in "Configuring Security" on page 133.
Required Data for This Procedure
Name of a subscriber group that has the vm-imap privilege.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
Note
9.
10.
11.
12.
13.
14.
DETAILED STEPS
Step 1
config t
Example:se-10-0-0-0# config t
Enters configuration mode.
Step 2
service imap
Example:se-10-0-0-0(config)# service imap
Enters Integrated Messaging configuration mode.
Step 3
enable
Example:se-10-0-0-0(config-imap)# enable
Enables the Integrated Messaging feature on a system-wide basis.
Step 4
maxsessions num-sessions
Example:se-10-0-0-0(config-imap)# maxsessions 25
Specifies the maximum number of concurrent IMAP client sessions. Valid values are 1 to 50. Default is 50.
Step 5
session idletimeout minutes
Example:se-10-0-0-0(config-imap)# session idletimeout 45
Specifies the number of minutes an IMAP session can be idle. After this maximum is reached, the system automatically disconnects the session. Valid values are 30 to120 minutes. The default is 30 minutes.
Step 6
session security {ssl | none | mixed}
Example:se-10-0-0-0(config-imap)# session security ssl
Specifies the type of IMAP connections accepted from IMAP clients. Any IMAP client trying to make any other type of connection will be rejected.
•
•
•
Note
Step 7
end
Example:se-10-0-0-0(config-imap)# end
Exits Integrated Messaging configuration mode
Step 8
groupname groupname privilege vm-imap
Example:se-10-0-0-0(config)# groupname sales privilege vm-imap
se-10-0-0-0(config-imap)# groupname imap-users privilege vm-imap
Specifies an existing group that will have access to the Integrated Messaging capability. Repeat this step if more than one group will have Integrated Messaging access.
Step 9
end
Example:se-10-0-0-0(config)# end
Exits configuration mode.
Step 10
username username group groupname
Example:se-10-0-0-0# username user4 group sales
Assigns a subscriber to the group.
Step 11
show imap configurations
Example:se-10-0-0-0# show imap configuration
(Optional) Displays all Integrated Messaging configuration parameters.
Step 12
show imap sessions
Example:se-10-0-0-0# show imap sessions
(Optional) Displays all active Integrated Messaging sessions.
Examples
The following example shows sample output from the show imap configuration command.
se-10-0-0-0# show imap configurationStatus: enabledIdle Timeout(minutes) 45Max Sessions: 25Security Mode: sslThe following example shows sample output from the show imap sessions command.
se-10-0-0-0# show imap sessionsSessions IP Address Connect Time User ID====================================================================1 10.21.82.244 Wed Nov 16 07:35:02 CST 2005 sales2 172.18.10.10 Wed Nov 16 08:23:15 CST 2005 imap-users3 172.18.10.5 Wed Nov 16 10:11:40 CST 2005 imap-usersDisplaying IMAP Sessions
To display IMAP sessions, see "Monitoring Active IMAP and VoiceView Express Sessions" on page 251.
Configuring Live Record
This section discusses the following topics:
Warning
Overview
This feature enables Cisco Unity Express subscribers to record live conversations and store the recording as a message in their mailbox. They can then play it or forward it to another subscriber or group of subscribers. This feature can also be used between Cisco Unity Express subscribers and nonsubscribers. Do this by conferencing the nonsubscriber's call leg into a Cisco Unity Express recording session and then recording the conversation to the appropriate mailbox. To alert participants that the call is being recorded, Cisco Unity Express periodically beeps.
The recording stops automatically when the call leg to the Cisco Unity Express recording session is terminated or the subscriber's voice mailbox is full, whichever occurs first. Depending on the Cisco Unified Communications Manager or Cisco Unified CME settings, the call leg can terminate either when the conference initiator ends the call or when the last participant ends the call. After the conference is terminated, the voice conversation can continue without further recording. When the live-record session is stopped, the recording is put in the new message state and the MWI is triggered.
Each recording can be saved, deleted, or forwarded just like any other voice mail message and are addressed as being from the subscriber. The recording is applied against the subscriber's mailbox limit until it is deleted.
You can only enable the live-record feature globally for Cisco Unity Express; you cannot enable it on a per-user basis. To initiate a live-record session, users conference to an extension configured as call-forward-all on Cisco Unified Communications Manager or Cisco Unified CME and is setup to forward all incoming calls to the voice mail pilot number.
The maximum number of live-record sessions is controlled by the voicemail pilot number maxsessions trigger setting. The size of live-record messages is limited only by the amount of space remaining in the subscriber's voice mailbox. Live-record messages do not trigger the cascading message notification feature.
Note
Configuration
To configure the live-record feature, simply define:
•
This dummy extension forwards all incoming calls to the voice mail pilot number on Cisco Unity Express.
•
Use the voicemail live-record pilot-number digits command and supply the live-record pilot number as the digits argument.
•
You can configure the beep duration and interval on Cisco Unity Express as needed to satisfy any applicable laws concerning notification that a call is being recorded. By default, the beep duration is 250 milliseconds and the beep interval is 15 seconds.
For more informaton on how to configure the Live Record feature on Cisco Unified CME, see the Cisco Unified Communications Manager Express System Administrator Guide.
Using Live-Record
After live-record is properly configured, users can use the following sequence of steps to initiate a live-record session. This example assumes a call is already established. The subscriber wanting to record the conversation does not need to be the caller who initiated or received the call.
1.
Press the conference softkey button. The current conversation is paused.
2.
3.
4.
5.
Press the conference softkey button again. At this point, everything either party says is recorded except the beeps played by Cisco Unity Express.
To end the live-record session, remove the Cisco Unity Express from the conference and continue the call, or hang up and terminate the call.
Error Conditions
The following error conditions can occur for subscribers using live-record:
•
•
Limitations
A one-button solution for live-record is not available. Create a conference soft key and a live-record speed dial key. This gives users the following three button solution:
1.
2.
3.
Live-record is only available to Cisco Unity Express local subscribers. Remote subscribers or external callers cannot use this feature because it uses the extension number assigned to the caller. However, this feature does not provide a prompt to ask the user to identify the extension and password and help prevent remote users from attempting to use the service.
Live-recorded messages do not trigger a message notification when delivered to the voice mailbox.
Configuring Live Record
Prerequisites
You must configure Cisco Unified Communications Manager or Cisco Unified CME with a dummy extension to forward all calls to the Cisco Unity Express voice mail pilot number.
Required Data for This Procedure
Configure the pilot number that you want to use for live recording (the extension number used to forward all incoming calls to the Cisco Unity Express voice mail pilot number).
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Examples
The following are samples of output for the show voicemail live-record command:
se-10-0-0-0# show voicemail live-recordStatus: enabledpilot number: 0295Conversation beep settingsduration: 250 millisecondsinterval: 15 secondsStatus: disabledpilot number: disabledConversation beep settingsduration: disabledinterval: 15 secondsConfiguring Live Reply
This section discusses the following topics:
Overview
This feature enables Cisco Unity Express subscribers who listen to the voice messages by phone or VVE to reply to another user's message by pressing 4-4. When this feature is invoked, Cisco Unity Express attempts to establish a call between the two parties. If the attempt is successful, the subscriber is connected to the called party or the voice call is forwarded based on rules defined by the called party. After the call is ended, the initial connection to voice mail is disconnected and the subscriber is not returned to their voice mail session. To review other voice mail messages after a successful live-reply session, the subscriber must redial the voice mail pilot number.
The behavior when there is a call failure is determined by the system's transfer-mode setting (see the transfer-mode subcommand for the ccn subsystem sip command). If transfer mode is set to blind, the connection to voice mail is lost when the call is either succeeds or fails. If transfer mode is semi-attended or attended, the connection to voice mail is retained when there is any call failure, such as an invalid number or busy. The message state is not changed by this feature. For example, if the subscriber is listening to a new message and decides to invoke this feature, the message remains in the new state.
Subscribers can use this feature with regular or deleted messages but cannot be used with messages from the local General Delivery Mailbox (GDM), broadcast messages, expired messages, NDR, or DDR. When subscribers attempt to use this feature with any of these messages, they receive an error voice prompt and are returned to the voice mail menu from which they tried to invoke this feature.
The following sections describe how the two methods of access this feature:
•
•
Accessing Live-Reply from the TUI
Subscribers can use the live-reply feature from the following three TUI menus:
•
•
•
To live-reply to a message, the subscriber must first listen to a message in one of the above queues. The subscriber can also use live reply when the message review menu is played giving the options to reply or forward the message. To use live reply, the subscriber must press 4-4 in sequence.
Accessing Live-Reply from VVE
Unlike the TUI, in VVE there is only one list of voice mail messages. All messages that qualify for live-reply have an additional menu that is displayed when you press the Reply button. This menu allows the subscriber to select the normal voice mail reply or allow a live reply if the caller's information is available.
If the message is forwarded, the live reply feature connects to the last number from which the message was forwarded.
By default, live-reply is disabled. Use either the CLI or GUI at the system level to enable live-reply. Users cannot configure this feature.
This feature uses the E.164 number to make the outbound call. Therefore, the number of the calling party returned as part of voice call must be dialable. How the senders E.164 number is determined depends on how the voice mail was delivered to the subscriber's mailbox. The two possible methods of delivery are:
•
•
These methods are discussed in the following sections.
Telephone Delivered Voice Mail
An example of this scenario is when the sender of voice mail calling a subscriber is forwarded to the subscriber's voice mailbox. If the calling party information exists for the sender, it is stored in the voice mail message envelope. The subscriber can listen to this message and attempt to live reply to this message. If the calling party information is not available, attempting to live-reply to a message results in an "Invalid option" error. For more information, see the "Limitations" section.
VPIM (Network) Delivered Voice Mail
To support this feature, the network message delivered using VPIM between Cisco Unity Express nodes or between Cisco Unity Express and Cisco Unity contains the E.164 number, starting in 3.0 (if it is configured and available for the subscriber).
You can configure the live-reply feature so that it can be used with existing VPIM capable systems that send only the subscriber's mailbox number (which may or may not be the appropriate E.164 number) instead of the E.164 number. Do this by setting up a rule to define each remote location in your Cisco Unity Express configuration that will be used to determine which E.164 number to dial to reach the author of the VPIM delivered voice mail. This determination is done based on network configuration location settings.
You can configure this rule to use one of the following options as the sender's E.164 number:
•
•
•
•
•
By default, Cisco Unity Express uses the E.164 number supplied by a peer 3.1 system in the VPIM header, if present. Otherwise it uses the configured rule to determine the E.164 number to use for this message.
In some cases, you can reconfigure remote sites to use the mailbox ID as the E.164 number to dial for live reply. You can use this configuration when:
•
•
You probably have overlapping extensions between sites. In this case, Cisco Unity Express could be configured to use the remote systems phone prefix with the subscriber's mailbox ID to derive the E.164 number to dial. You can use this method if you configure your Cisco Unified Communications Manager or Cisco Unified CME to implement this dial plan and transform the mailbox ID received in the VPIM message into a unique E.164 address.
In addition to determining how to derive the E.164 phone number to use with live reply, you can also set the precedence of the VPIM E.164 number over the rule derived phone number.
Limitations
Live-reply cannot apply call restrictions on a per-subscriber basis. Because the outbound dialing is from Cisco Unity Express on behalf of the user, any restrictions on dialed numbers must be applied to all users equally. There cannot be a privileged set of Cisco Unity Express subscribers that have a broader set of live-reply dialed numbers. For example, subscribers cannot be divided into groups (such as employees and management) where one group (management) can live-reply to all locations and the other group (employees) can only live-reply to local extensions.
If you use a complex dial-plan, it might be difficult or impossible to configure live-reply to correctly handle remotely delivered VPIM messages. If the remote system is Cisco Unity or an earlier version of Cisco Unity Express, the live-reply number is not included in the VPIM header. This makes it difficult or impossible to determine the E.164 number Cisco Unity Express must dial to reach the sender. For example, a dial plan where mailbox IDs are unrelated to user extensions may make it impossible for the system to derive the E.164 number to call.
Configuration
You can configure the following items for the Live Reply feature:
•
•
•
•
These items are explained in the following sections.
Network Precedence
Network precedence determines which E.164 number Cisco Unity Express dials when making a live-reply to a VPIM delivered message. It specifies the priority of the following methods of determining the live-reply E.164 number:
•
•
•
Calling Number Rule
The calling number rule specifies how the live-reply extension is derived from configuration and VPIM vcard data. Knowing the callers E.164 number is essential for live-reply functionality. Note however, knowing the E.164 number for the sender of a voice mail is not required if live-reply disabled.
defines the behavior of the options for deriving a sender's E.164 number. The last column shows an example of the derived number, assuming that the location ID is configured as 111, the location prefix is configured to 444, and the mailbox ID of the incoming VPIM message is 5678.
Table 1 Behavior of the Options for Deriving a Sender's E.164 Number
Prepend Digits
This setting specifies any additional digits that you want to be dialed before the calling-number rule derived E.164 number for a remote subscriber.
Restriction Table
The restriction table enable you to control how the live reply feature is used. As described in the "Configuring Restriction Tables" section, use the following parameters to define a restriction table:
•
•
•
•
•
Configuring Live Reply
Prerequisites
To restrict specified extensions from using this feature, you must configure a restriction table as described in the "Configuring Restriction Tables" section.
Required Data for This Procedure
This procedure requires the prepend digits (any additional digits that you want dialed before the calling-number rule derived E.164 number for a remote subscriber).
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
Step 1
config t
Example:se-10-0-0-0# config t
Enters configuration mode.
Step 2
voicemail live-reply enable
Example:se-10-0-0-0(config)# voicemail live-reply enable
Enables the Live Reply feature on a system-wide basis.
Step 3
voicemail live-reply network-precedence {phonenumberE164 [calling-number-rule] | calling-number-rule}
Example:se-10-0-0-0(config)# voicemail live-reply network-precedence calling-number-rule
Determines which live-reply E.164 number Cisco Unity Express dials when making a live-reply to a VPIM delivered message. Specifies the use of one of the following methods of determining the live-reply E.164 number:
•
•
•
Step 4
voicemail live-reply calling-number-rule {extension | prefix-extension | location-extension | location-prefix-extension | prefix-location-extension}
Example:se-10-0-0-0(config)# voicemail live-reply calling-number-rule location-extension
Specifies how the live-reply extension is derived from the configuration and the VPIM vcard data. This determines how to construct the remote subscriber's E.164 phone number. For more information, see the "Calling Number Rule" section.
Step 5
voicemail live-reply restriction table-name
Example:se-10-0-0-0(config)# voicemail live-reply restriction live-reply-r-table
Associates a restriction table to the live reply feature.
Step 6
network location id ID_number
Example:se-10-0-0-0(network)# network location id 112
Enters network location mode.
Step 7
calling-number-rule prepend-digits digits
Example:se-10-0-0-0(config)# calling-number-rule prepend-digits 91
Specifies additional digits to dial before the calling-number rule derived E.164 number for a remote subscriber.
Step 8
end
Example:se-10-0-0-0(config)# end
Exits to privileged EXEC mode.
Step 9
show voicemail live-reply
Example:se-10-0-0-0# show voicemail live-reply
(Optional) Displays the current configuration for the live-reply feature.
Step 10
show network detail location id loc-id
Example:se-10-0-0-0# show network detail location id 112
(Optional) Displays information about the current network location, including the prepend digits setting.
Step 11
show voicemail live-reply restriction-table
Example:se-10-0-0-0# show voicemail live-reply restriction-table
(Optional) Displays the restriction-table associated with the live-reply feature.
Examples
The following is sample output for the show voicemail live-reply command:
se-10-0-0-0# show voicemail live-replyStatus: enabledRemote subscriber dialingcalling number rule: location+prefix+extensionnumber preference: E164 number then calling number ruleRestriction Table: live-reply-restrictionMinimum digits allowed: 1Maximum digits allowed: 30Dial Strings:Preference Call Pattern Allowed1 19000... yes2 170000 yes3 * yesThe following example shows information about the remote Cisco Unity Express location with the ID of 102:
se-10-0-0-0# show network detail location id 102Name: Dallas/Fort WorthAbbreviation: DFWEmail domain: dfw.mycompany.comMinimum extension length: 2Maximum extension length: 15Phone prefix: 4VPIM encoding: dynamicSend spoken name: enabledSend vCard: enabledState: enabledVPIM broadcast ID: vpim-broadcastSent msg count: 0Received msg count: 0Live-reply calling number rule prepend: 91The following is sample output for the show voicemail live-reply restriction-table command:
se-10-0-0-0# show voicemail live-reply restriction-tableRestriction Table: live-reply-restrictionMinimum digits allowed: 1Maximum digits allowed: 30Dial Strings:Preference Call Pattern Allowed1 19000... yes2 170000 yes3 * yesConfiguring the Delivery of Future Messages
Cisco Unity Express subscribers may create and schedule voice-mail messages for future delivery to one or more subscribers on the local system or on configured remote network locations.
You do not need to configure this feature for subscribers.
Subscribers can schedule message delivery for up to 1 year in advance.
Senders can readdress, rerecord, and review the message before scheduling it for delivery. After the system confirms the date and time for the future delivery, the sender cannot change or delete the message.
You can display and delete messages marked for future delivery.
A subscriber can schedule any number of messages for future delivery if the subscriber's mailbox has enough space. The system counts all the sender's future messages against the sender's quota until a message is sent. After a future message is delivered, it is counted against the recipient's quota.
The following sections describe this feature:
•
•
•
Permitted Subscribers
No special privileges are required to use this feature.
All subscribers configured on the system have access to this feature.
Message Delivery Time
Any change or drift in the system time impacts the message delivery. For example, a sender schedules a message for a 4:00 p.m. delivery when the system time is 3:00 p.m.
•
•
•
System Status Impact
If the sending system is in a shutdown state with messages scheduled to be delivered during that time, the system delivers the messages when the system is up again.
If the sending system is in an "offline" state with messages scheduled to be delivered during that time, the system delivers the messages when the system returns to the "online" state.
Unsuccessful Message Delivery
If you change the IP address or hostname of the remote location before delivery of a scheduled message, the system delivers the message successfully.
Message delivery fails in the following situations:
•
For example, location A has a message scheduled for delivery to remote location B on 15-April 2006. You disable location A on 14-April-2006. Message delivery fails.
•
•
In all cases, the system generates a nondelivery receipt (NDR).
Loss of Future Messages
Multiple scenarios can cause the loss of future messages:
•
•
•
Incorrect Message Delivery
Subscriber or network configuration changes may impact delivery of scheduled messages.
•
•
Backup and Restore of Future Messages
The system backs up messages scheduled for future delivery as part of a data backup. When that backup is restored, the system delivers the scheduled messages at the appropriate times. If the scheduled delivery time is in the past, the system delivers those messages when as the system is restored.
Recipients may receive a scheduled message more than once. For example, you back up the system on 20-March-2006. This backup contains messages scheduled for 25-March-2006. On 26-March-2006, the system experiences a power outage. The administrator uses the 20-March-2006 backup to restore the system. The system redelivers the scheduled messages contained in the backup file.
Displaying and Deleting Future Messages
To display and delete future messages, see "Monitoring Future Messages" on page 316.
Configuring Nonsubscriber Message Delivery
This section discusses the following topics:
•
Overview
This feature gives Cisco Unity Express subscribers the ability to record a voice message and send it to an external number or nonsubscriber at the predefined time up to 1 year in advance. The subscriber who is sending the message can readdress and rerecord the message, change the message delivery options, and review the message while setting it up for delivery. You can also use the same functionality to simply forward a voice message.
Messages with no audio, typically faxes and fax NDR, may not be forwarded to an external number. Only faxes with a voice attachment are allowed.
After subscribers configure messages for delivery, they do not receive any indication that there are messages marked for delivery to nonsubscribers. However, the administrator can view and delete any messages that are marked for future delivery to nonsubscribers. To provide this functionality, enhancements to the future delivery commands are included with this feature.
Limitations to this functionality include:
•
•
•
•
The subscribers use the same method as before 3.0 to send messages or to compose messages for future delivery. To send a message to nonsubscribers, subscribers enter the nonsubscriber number when the TUI prompts them to enter the recipients' number after pressing #4. The system does not attempt to validate any of these numbers.
The message is delivered to the called number regardless of who answers the phone or whether the called number is forwarded to another number. The messages are delivered based on the current system time (within a grace period of 5 minutes of the actual scheduled time). A message is delivered successfully when:
•
•
If a system is shutdown or offline and it has messages scheduled to be delivered during that period, those messages are delivered when the system is running again.
When a subscriber's mailbox is deleted, all messages scheduled for delivery by that subscriber are also deleted. However, the messages are not deleted when a subscriber's mailbox is disabled. When a message is scheduled to be delivered, the system verifies that sender's mailbox is enabled. A message is discarded only if the mailbox is disabled at that time.
Any messages scheduled for delivery are backed up as part of a regular data backup. When you restore a backup, all messages in the backup that are scheduled for delivery are sent to the recipients as specified. If the scheduled delivery time of some of the messages have passed, they are sent when the system is up after the restore. Therefore, it is possible for recipients to receive a message more than once.
Messages to nonsubscribers are contained in the future message queue until their scheduled time of delivery. These messages are counted as part of the sender's quota until they are removed from the message queue. A subscriber can schedule any number of messages for the delivery, if there is space available in their mailbox.
When a message is delivered, the prompt played to nonsubscribers is one of the following:
•
•
•
After listening to a message, a nonsubscriber can repeat the playing of the message up to two times by responding to the prompt "To repeat this message, press 1."
When a subscriber sends a message to a nonsubscriber and the sending subscriber's mailbox is full, the message cannot be delivered. If this is the case, the following prompt is played to the sender:
"Your message could not be delivered to extension external_number. Your mailbox is full. You cannot send messages to a phone number. To send another message, press 1. To exit, press *."
Configuring Nonsubscriber Message Delivery
Prerequisites
To restrict this feature from delivering messages to specified external numbers, you must configure a restriction table as described in the "Configuring Restriction Tables" section.
Required Data for This Procedure
Name of the restriction table you want to associate with this feature.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Examples
se-10-0-0-0# show voicemail messages futureMessage ID: JMX0637L023-NM-FOC08221WRB-731357131983Sender: User1Recipient(s): UserALength(sec): 30Delivery time: Mon, 11 April 2006 08:0000-0800 (PST)Message ID: JMX0637L023-NM-FOC08221WRB-731183375855Sender: User2Recipient(s): UserB, 95550041 (External)Length(sec): 20Delivery time: Wed, 13 April 2006 10:15:00-0800 (PST)se-10-0-0-0# show voicemail msg-notification restriction-tableRestriction Table: msg-restrictionMinimum digits allowed: 1Maximum digits allowed: 30Dial Strings:Preference Call Pattern Allowed1 19000... yes2 170000 yes3 * yesConfiguring Broadcast Messages
This chapter describes the procedures for configuring the networking capability on the local Cisco Unity Express voice-mail system and contains the following sections:
•
•
•
•
•
•
•
•
•
Overview of Broadcast Messages
Cisco Unity Express permits sending broadcast messages to local and remote network locations. Cisco Unity Express permits subscribers with the broadcast privilege to send local and network broadcast messages. Subscribers obtain this privilege as members of a group that has the broadcast privilege.
Sending a broadcast message is available through the Cisco Unity Express telephone user interface (TUI).
The broadcast message sender has the option to readdress, rerecord, and review the message before sending it out. The sender also can set the start and end times for the message and the number of days the broadcast message plays before the system deletes it. The maximum life of a broadcast message is 365 days. The default message lifetime is 30 days.
The sender can include any or all of the remote locations configured on the local system. The remote addresses can be location numbers or location names. When using the location name, the number of matches may resolve into several locations. If the number of locations is less than or equal to 4, the system gives the sender the option to select the exact location. If the number of matches is greater than 4, the sender must enter more letters to narrow the search.
All subscribers at the remote location receive the broadcast message. The recipients hear the message immediately after logging in to their voice mailboxes. The recipients cannot interrupt the message with any DTMF key. Recipients can save or delete the broadcast message; they cannot reply or forward a broadcast message.
The system administrator at each location determines how or when the message waiting indicator (MWI) lights.
It is possible for the MWI lights to turn on for a broadcast message on some systems but not for others.
Configuring Broadcast Messages
Perform the following procedures to configure broadcast messages:
•
•
Configuring a Group with Broadcast Privileges
Use the following EXEC mode command to configure a group with broadcast privileges:
group group-name privilege broadcast
where group-name is the set of subscribers who will have the capability of creating and sending broadcast messages.
The following example assigns the broadcast privilege to a group named managers:
se-10-0-0-0# group managers privilege broadcastConfiguring the Broadcast Message Length and Expiration Time
Use the following procedure to configure the local system for broadcast messages.
Required Data for This Procedure
The following information is required to configure the broadcast message length and expiry time:
•
•
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Examples
The following example sets the broadcast message length to 20 seconds and the expiration time to 2 days.
se-10-0-0-0# config tse-10-0-0-0(config)# voicemail broadcast recording time 20se-10-0-0-0(config)# voicemail default broadcast expiration time 2se-10-0-0-0(config)# exitEnabling the MWI Lights for Broadcast Messages
Use the following Cisco Unity Express configuration mode command to enable the MWI lights when a voice mailbox receives a broadcast message.
voicemail broadcast mwi
The following example illustrates enabling the MWI lights for broadcast messages:
se-10-0-0-0# config tse-10-0-0-0(config)# voicemail broadcast mwise-10-0-0-0(config)# endDisplaying Broadcast Messages
Multiple commands are available to display information about broadcast messages.
Displaying Current Broadcast Messages
Use the following EXEC mode command to display broadcast messages:
show voicemail broadcast messages
The output for this command may appear similar to the following:
se-10-0-0-0# show voicemail broadcast messagesMessage ID: JMX0824L4R4-NM-FOC08221WSQ-1103139552166-NBCMSender: 1005@nyc.mycompany.comLength(secs): 10Start time: 21:12:54 Nov 23 2005 PSTEnd time: 11:48:06 Dec 4 2005 PSTMessage ID: JMX0824L4R4-NM-FOC08221WSQ-1103084723247-NBCMSender: /sw/local/users/user45Length(secs): 30Start time: 08:41:09 Dec 7 2005 PSTEnd time: 09:00:00 Jan 3 2006 PSTIf a subscriber at a remote network location sends the broadcast message, the e-mail domain of the remote sender appears in the Sender field. If a local subscriber sends the message, the pathname to the sender appears in the field.
If no broadcast messages are active, the output may appear similar to this:
se-10-0-0-0# show voicemail broadcast messagesNo Broadcast MessagesDisplaying Broadcast Messages Received Per Mailbox
The following command is modified to display broadcast message information:
show voicemail mailboxes
The column BCST displays the number of broadcast messages received by the mailboxes. The output for this command may appear similar to the following:
se-10-0-0-0# show voicemail mailboxesOWNER MSGS NEW SAVE DEL BCST MSGTIME MBXSIZE USEDuser1 16 16 0 0 4 3000 3000 100%user2 16 16 0 0 4 3000 3000 100%user3 16 16 0 0 4 3000 3000 100%user4 16 16 0 0 4 3000 3000 100%Displaying Broadcast Messages Received by the Voice-Mail System
The following command is modified to display broadcast message information:
show voicemail usage
The row broadcast message count displays the number of broadcast messages received by the voice mail system. The output for this command may appear similar to the following:
se-10-0-0-0# show voicemail usagepersonal mailboxes: 120general delivery mailboxes: 0orphaned mailboxes 0capacity of voicemail (minutes): 6000allocated capacity (minutes): 6000.0total message time used (seconds): 7543total message count: 7001average message length (seconds): 1.0774175117840308broadcast message count: 4future message count: 0networking message count: 0greeting time used (seconds): 3greeting count: 1average greeting length (seconds): 3.0total time used (seconds): 7546total time used (minutes): 125.76667022705078percentage time used (%): 2messages left since boot: 0messages played since boot: 0messages deleted since boot: 0Deleting a Broadcast Message
Use the following EXEC mode command to delete a broadcast message:
voicemail broadcast message message-id delete
where message-id is the coded identifier for the message. Use the show voicemail broadcast messages command to obtain the message ID.
The following example deletes a broadcast message:
se-10-0-0-0# voicemail broadcast message JMX0824L4R4-NM-FOC08221WSQ-1103139552166-NBCM deleteChanging Broadcast Message Start and End Times
Use the following EXEC mode commands to change the start and end times of a broadcast message:
voicemail broadcast message message-id starttime time date
voicemail broadcast message message-id endtime time date
where message-id is the coded identifier for the message, time is the time in the 24-hour clock format, and date has the format YYYY-MM-DD. Use the show voicemail broadcast messages command to obtain the message ID.
The following examples change the start and end times for a broadcast message:
se-10-0-0-0# voicemail broadcast message JMX0824L4R4-NM-FOC08221WSQ-1103139552166-NBCM starttime 10:00 2004-09-15
se-10-0-0-0# voicemail broadcast message JMX0824L4R4-NM-FOC08221WSQ-1103139552166-NBCM endtime 15:30 2004-09-16
Disabling Broadcast Privileges for a Group
Use the following EXEC mode command to remove the broadcast privileges from a group:
no group groupname privilege broadcast
where groupname is the group to have the broadcast privileges removed.
The following example disables the broadcast privilege for the group named managers:
se-10-0-0-0# no group managers privilege broadcastDisabling MWI Lights for Broadcast Messages
Use the following Cisco Unity Express configuration mode command to disable the MWI lights for broadcast messages.
no voicemail broadcast mwi
The following example illustrates how to disable the MWI lights for broadcast messages:
se-10-0-0-0# config tse-10-0-0-0(config)# no voicemail broadcast mwise-10-0-0-0(config)# endConfiguring the Local-Broadcast Privilege
Cisco Unity Express provides a local-broadcast privilege that permits subscribers to send broadcast messages only to other subscribers on the local system. The local-broadcast privilege is a subset of the broadcast privilege, which permits subscribers to send broadcast messages to all configured subscribers and locations on the network.
Cisco Unity Express does not create a default group for local-broadcast subscribers. The administrator must create a group of subscribers and assign the local-broadcast privilege to it.
This feature is available on Cisco Unity Express modules NM-CUE-EC, NM-CUE, and AIM-CUE.
To configure this option from the GUI, use the Configure > Groups option and select a group.
Prerequisites
Name of the group that will be assigned to the local-broadcast privilege. Verify that the group exists before assigning the privilege.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Example
The following example displays the privileges for multiple groups.
se-10-0-0-0# show groups privilegesGROUPID PRIVILEGESAdministrators superuser ManagePrompts ManagePublicListAdministrators ViewPrivateListBroadcasters broadcastmanagers broadcast ViewPrivateListengineers local-broadcastConfiguring Restriction Tables
This section discusses the following topics:
•
Overview
The following features use restriction tables to enable you to restrict access to the feature's functionality:
•
•
•
•
For each of these features, the restriction table controls the phone numbers that subscribers can use to access the feature. These restrictions are available only for phone devices and numeric pagers.
The system provides a predefined table that can be modified by the administrator. The table applies to all subscribers and groups on the system. A typical use of this table is to prevent the use of long-distance or international numbers for the feature
The system checks the restriction table when the subscriber is assigning phone numbers to phone devices (such as a cell phone, home phone, or work phone), to a numeric pager, and before making an outcall. If a phone number is listed in the table as restricted, the system sends a message to the subscriber.
If a subscriber has a number configured for a device and the administrator later restricts that number system-wide, notification calls will not be made to that number. The administrator must remove the number for the individual subscriber.
Cisco Unity Express provides a default restriction table that defines two requirements:
•
•
Valid patterns can include digits 0 to 9, asterisk (*), and dot (.). The * indicates a match of zero or more digits. Each dot serves as a placeholder for 1 digit.
Valid setting values are allowed or disallowed.
When a subscriber tries to set up or change a phone number assigned to a device, the system verifies that the number has the allowed number of digits. If it does not, the subscriber receives a system message.
If the number of digits is acceptable, the system checks the number against the dial patterns in the restriction table, starting with the first pattern (preference 1). If the number does not match the first pattern, the system checks the next pattern in the table (preference 2), and so forth until a match is found. The system either permits or restricts the call as specified in the dial string.
The default restriction table permits all phone numbers to be used, as shown in Table 2.
You can change only the preference and permission of this pattern.
The restriction table can contain identical dial strings, which have the same call pattern and permission setting. This includes the default pattern. You can delete any of these dial strings if the table contains at least one default pattern.
Table 3 illustrates a restriction table with international numbers and restricted numbers.
Table 3 Restriction Table with International Numbers
1
9011*
No
2
91..........
No
3
*
Yes
Table 4 illustrates a restriction table that permits one number in an area code but restricts all other numbers in that area code.
Table 4 Restriction Table with Restricted Area Code
1
9011*
No
2
912225550150
Yes
3
91222.......
No
4
*
Yes
Following are the parameters that you can configure for restriction tables:
•
•
•
•
•
•
•
Configuring Restriction Tables
The following sections describe how to configure restriction tables:
•
•
•
Creating a Restriction Table
Prerequisites
None.
Required Data for This Procedure
None.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Examples
The following is sample output for the show restriction-table table-name command:
se-10-0-0-0# show restriction-table fax-restrictionRestriction Table: fax-restrictionMinimum digits allowed: 1Maximum digits allowed: 30Dial Strings:Preference Call Pattern Allowed1 19000... yes2 170000 yes3 * yesDeleting a Restriction Table
Prerequisites
None.
Required Data for This Procedure
None.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Examples
To see sample output for the show restriction-table table-name command, see the "Examples" section.
Configuring a Restriction Table
To configure a restriction table, you can set any of the following parameters or you can accept the default values:
•
•
•
Prerequisites
None.
Required Data for This Procedure
None.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Examples
To see sample output for the show restriction-table table-name command, see the "Examples" section.
Feedback