- Cisco Unity Express Features
- Overview of Cisco Unity Express Voice Mail and Auto Attendant
- Entering and Exiting the Command Environment
- Configuration Tasks
- Configuring System Components
- Configuring Users and Groups
- Configuring Voice Mail
- Configure Smart Licensing
- Configuring Authentication, Authorization, and Accounting
- Configuring the Administration via Telephone Application
- Configuring Auto Attendants
- Configuring Message Notification
- Configuring VoiceView Express
- Networking Cisco Unity Express
- Configuring Distribution Lists
- Configuring Security
- Backing Up and Restoring Data
- Language Support
- Configuring Advanced Voice Mail
- Advanced Configuration
- Monitoring the System
- Configuring SNMP Monitoring
- Registering Cisco Unity Express Endpoints to Cisco Unified Messaging Gateway
- Configuring Your Cisco IOS Gateway for T.37 On-Ramp and Off-Ramp Fax Support
- Troubleshooting
Configuring Distribution Lists
This chapter describes distribution lists and contains the following sections:
Overview of Distribution Lists
Distribution lists allow subscribers to send a voice-mail message to multiple recipients at the same time. The sender can send voice messages to distribution lists only on the local system. The sender cannot address a voice message to a distribution list on a remote system.
Cisco Unity Express supports two types of distributions lists:
Properties of Distribution Lists
Cisco Unity Express distribution lists have the following properties:
– Local and remote subscribers
A remote subscriber that is statically configured on the local system can be a member of a distribution list. However, that remote subscriber cannot own a distribution list on the local system.
– General delivery mailboxes (GDMs)
Specify the location ID and extension of the blind address. The system verifies the location ID and the extension length.Members—Distribution lists can comprise a variety of members: local subscribers, remote subscribers, blind addresses, GDMs, groups, and other lists.
A public list member can be another public list but may not be a private list.
A private list member can be any public list and may be another private list owned by the same subscriber.
When a subscriber addresses a voice message to a public or private distribution list, the system verifies that the list has members. If the list is empty, the system plays a prompt indicating that the list contains no members and does not allow the list to be used as a recipient of the message.
- Recursive distribution lists are permitted. For example, list A can be a member of list B, and list B can be a member of list A.
- The system generates a special public distribution list, the everyone list, which contains all the local subscribers. It does not contain the local groups, GDMs, and other lists. You cannot add to or delete members from this list, assign an owner to this list, or delete this list.
- Each list must have a unique name or number.
Valid names have a maximum of 64 characters and include the letters A to Z, a to z, digits 0 to 9, underscore (_), dot (.), and dash (-). Names must start with a letter. Spaces are not allowed.
- The owner of a public or private distribution list can record a spoken name for the list using the TUI. Recording or uploading the spoken name cannot be done through the GUI or CLI.
The everyone public list has a default spoken name. An administrator can change this name using the TUI.
- If a local or remote subscriber is deleted from the system, the subscriber is no longer a member or owner (in the case of local subscribers) of any public or private distribution list on the system. The system deletes all private lists owned by the deleted local subscriber. If the local subscriber was the sole owner of a public distribution list, the Administrators group assumes ownership of that list.
This same rules apply to the removal of a group, except that the system does not delete any private lists.
Public Distribution Lists
All local subscribers of the system can use a public distribution list to address their voice-mail messages.
Use the Cisco Unity Express graphical user interface (GUI), telephone user interface (TUI), or command-line interface (CLI) to create and manage public distribution lists.
Table 15-1 describes the features of a public distribution list.
|
|
|
---|---|---|
Depends on the Cisco Unity Express hardware. See the Release Notes for Cisco Unity Express for more information. |
Maximum number of lists allowed on the system This number does not include the everyone list. |
|
A public distribution list must have a unique number. The everyone list has the number 9999 by default. The administrator can change this number using only the GUI menu option Voice Mail > Distribution Lists > Public Lists. |
||
The everyone list cannot have an owner. The owner can be any local subscriber or group. If the owner is a group, all the members of that group are owners of the list. Members of the Administrators group are implicit owners of all public distribution lists. If all the owners of a list are deleted, the Administrator group continues to have ownership of the list. |
||
Depends on the Cisco Unity Express hardware. See the Release Notes for Cisco Unity Express for more information. |
This total is the sum of all members in all public lists on the local system, excluding the everyone list. |
|
This total is the sum of all owners of all public lists on the system, excluding the everyone list. |
||
Local subscribers belonging to the Administrators group, or to any group with the ManagePublicList privilege, can create public lists. |
Private Distribution Lists
Any local subscriber can create private distribution lists that are accessible only to that subscriber.
Table 15-2 describes the features of private distribution lists.
Differences Between Cisco Unity Express and Cisco Unity Distribution Lists
Table 15-3 describes important differences between the Cisco Unity Express and Cisco Unity distribution lists.
Configuring Public Distribution Lists
Use this procedure to create or modify public distribution lists.
Note Use the TUI or GUI to create private distribution lists. No CLI commands are available for private distribution lists.
Beginning in release 3.2, you can add nonsubscribers to distribution lists. This enables the delivery of voice messages to people who do not have a mailbox on the system by using a single address to reference a list of addresses when sending the message. By using this single aggregated address, a subscriber can send a single message to all the recipients included in the distribution list.
When nonsubscriber numbers are submitted for addition to a distribution list, they are checked against the nonsubscriber restriction table. If a nonsubscriber address is restricted, it is not added to the distribution list. If you change a restriction table after a list has been created, the system does not revalidate distribution lists. Instead, distribution lists are revalidated when they is used to send outgoing mail to nonsubscriber addresses and any addresses that are restricted are removed from the list of recipients. In addition, there is no change in the way the existing system sends the message. The system still checks the nonsubscriber restriction table before sending a message to a nonsubscriber, future message queues, a backup restore, and so on.
Prerequisites
Required Data for This Procedure
The following information is required to create a public distribution list:
- List name and number
- (Optional) List description—The description can have a maximum of 64 characters.
The following information is required to add members to a distribution list:
SUMMARY STEPS
2. list name list-name number list-number create
3. list number list-number owner owner-ID
4. list number list-number member { member-name | extension } type { group | user | gdm | list | remote | blind | nonsubscriber }
5. (Optional) list number list-number description description
DETAILED STEPS
Examples
The following example creates public distribution list number 5 for engineers:
Configuring Private Distribution Lists
Local subscribers can configure their private distribution lists using the GUI menu option VoiceMail > Distribution Lists > My Private Lists or by using the TUI.
No CLI commands are available for configuring private lists.
Displaying Distribution Lists
Several commands are available to display distribution lists and their members.
Displaying All Public Distribution Lists
The following Cisco Unity Express EXEC mode command displays all the public distribution lists on the local system:
This command displays the lists in alphabetical order with each list name, number, and type, followed by the details of each list.
Output from this command may appear similar to the following:
Displaying Details of a Public Distribution List
The following Cisco Unity Express EXEC mode command displays details of a specific public distribution list:
show list detail public { name list-name | number list-number }
where list-name is the name of the list and list-number is the number of the list.
This command displays the list number, list name, list type, owners, and members of the list with their type categories.
Output from this command may appear similar to the following:
se-10-0-0-0# show list detail public name engineers
The command show list detail public number 5 would display the same output as shown above.
Displaying an Owner’s Lists
The following Cisco Unity Express EXEC mode command displays the public and private lists owned by a specific subscriber or group:
where owner-id is the name of a subscriber or group. An error message appears if owner-id does not exist.
This command displays the list number, list name, and list type for all the public and private lists that belong to the specified owner. The lists appear in alphabetical order, private lists first followed by public lists.
Output from this command may appear similar to the following:
Displaying Details of a Private Distribution List
The following Cisco Unity Express EXEC mode command displays the details of a specific private distribution list for a specific subscriber:
show list detail private { name list-name | number list-number } owner owner-id
where list-name is the name of the private list, list-number is the number of the private list, and owner-id is the name of a subscriber. An error message appears if list-name, list-number, or owner-id does not exist.
This command displays the list number, list name, owner, members, and member types of the specified private distribution list.
Output from this command may appear similar to the following:
The command show lists detail private number 4 owner user15 would display the same output as shown above.
Deleting Distribution Lists
The TUI and GUI have options for deleting private and public distribution lists. Additionally, the CLI has a command for deleting public lists on the local system.
Use the following Cisco Unity Express configuration mode command to delete public distribution lists:
list number list-number delete
where list-number is the number of the public distribution list.
The following example deletes list number 10 from the local system: