|
|
Table Of Contents
Networking Cisco Unity Express
Cisco Unity Express Networking Overview
Downloading and Uploading Network Location Spoken Names
Downloading the Location Spoken Name
Uploading the Location Spoken Name
Adding Remote Users to the Local Directory
Impact of Remote Messages on the Local User
Configuring the Local Directory with Remote Users
Deleting Remote User Information
Downloading and Uploading Remote User Spoken Names
Downloading the Remote User Spoken Name
Uploading the Remote User Spoken Name
Configuring Caller ID for Incoming Messages
Enabling Caller ID on the Local System
Disabling Caller ID on the Local System
Configuring a Location with vCard Information
Enabling a Location to Receive vCard Information
Disabling Receipt of vCard Information
Configuring Network Broadcast Messages
Configuring Broadcast Messages
Configuring the Broadcast Message VPIM ID for a Network Location
Enabling the MWI Lights for Broadcast Messages
Changing the Broadcast Message Start and End Times
Disabling the Broadcast Privileges for a Group
Disabling the MWI Lights for Broadcast Messages
Configuring Distribution Lists
Members of a Distribution List
Properties of Distribution Lists
Differences Between Cisco Unity Express and Cisco Unity Distribution Lists
Configuring Public Distribution Lists
Networking Cisco Unity Express
This chapter describes the procedures for configuring the networking capability on the local Cisco Unity Express voice-mail system and contains the following sections:
•
Cisco Unity Express Networking Overview
•
•
•
•
•
•
•
•
•
Cisco Unity Express Networking Overview
Cisco Unity Express supports the Voice Profile for Internet Mail (VPIM) version 2 protocol to permit voice-mail message networking between Cisco Unity Express and Cisco Unity voice-mail systems that are not co-located on the same router or server. The voice-mail systems can reside on Cisco CallManager or Cisco CallManager Express call control platforms. Supported networked voice-mail configurations include:
•
•
•
Non-Delivery Record (NDR)
Voice-mail message networking uses Non-Delivery Records (NDRs) for handling undelivered messages. Currently, when a message cannot be delivered to a local subscriber, the sender receives an immediate notification of the reason. However, when sending to a remote subscriber, immediate feedback may not be possible due to repeated attempts to contact the remote location or to deliver the message.
After a specified amount of time, the sender receives a new voice-mail message indicating the reason for non-delivery. If non-delivery is due to the recipient's mailbox being full, non-existent, or is disabled, the non-delivery message includes the sender's original message. When the sender plays the NDR, the sender can readdress and resend the original message or delete the message.
Blind Addressing
When a subscriber sends a message to another subscriber on the same (local) Cisco Unity Express voice-mail system, the sender can address the recipient using spell-by-name or an extension number. The sender hears a confirmation of the recipient's spoken name, if it is recorded, or the recipient's extension number.
When a subscriber sends a message to a remote subscriber, the sender will not hear a confirmation of the recipient's name or extension. This is blind addressing. The address of the remote recipient is the location ID of the remote system plus the recipient's extension number at the remote location.
Spoken Name Confirmation for Remote Users
Beginning with Release 2.1, administrators or other privileged users can add remote users to the local directory using the Administration via Telephone (AvT) feature, which is part of the Telephone User Interface (TUI). Administrators can record spoken names for these remote users. The Cisco Unity Express network module (NM) supports up to 50 remote users; the Advanced Integration Module (AIM) supports up to 20 remote users.
This directory permits local voice-mail senders to address messages to the remote users using dial-by-name and to receive spoken name confirmation of the recipients. If a recipient is not in the directory, the sender receives the recipient's location ID and extension.
If the local system has vCard information enabled, incoming vCard information updates the remote user directory. The vCard information also updates a dynamic cache of remote users. This cache contains the first names, last names, and spoken names of remote users and is updated on a least recently used (LRU) basis. If a local sender addresses a voice message to a remote user who is not in the local directory but is in the LRU cache, the sender hears a spoken name for the remote user. If the remote user is not in the directory or the cache, the sender does not receive spoken name confirmation.
Components
•
•
•
•
Prerequisites
•
•
Restrictions
•
•
Configuring Network Locations
To configure network locations in Cisco Unity Express, perform the following tasks at each network location.
Prerequisites
The following information is required to configure networking on Cisco Unity Express:
•
•
•
•
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
DETAILED STEPS
Step 1
config t
Example:se-10-0-0-0# config t
Enters configuration mode.
Step 2
network location id number
Example:se-10-0-0-0(config)# network location id 9
Enters location configuration mode to allow you to add or modify a location.
•
•
Step 3
name location-name
Example:se-10-0-0-0(config-location)# name "San Jose"
(Optional) Descriptive name used to identify the location. Enclose the name in double quotes if spaces are used.
•
Step 4
abbreviation name
Example:se-10-0-0-0(config-location)# abbreviation sjcal
(Optional) Creates an alphanumeric abbreviation for the location that is spoken to a user when the user performs addressing functions in the telephone user interface. You cannot enter more than 5 characters.
•
Step 5
email domain domain-name
Example:se-10-0-0-0(config-location)# email domain cisco.com
Configures the e-mail domain name or IP address for the location. The domain name is added when sending a VPIM message to the remote location (for example, "4843000@cisco.com"). If you do not configure a domain name or IP address, the Cisco Unity Express system at this location cannot receive network messages.
•
Caution
Step 6
voicemail phone-prefix digit-string
Example:se-10-0-0-0(config-location)# voicemail phone-prefix 484
Configures the phone number prefix that is added to an extension to create a VPIM address for a user at the location. A prefix is required only if an e-mail domain services multiple locations and extensions between the locations are not unique. Valid values: 1 to 15 digits. Default value: empty.
•
Step 7
voicemail extension-length {number | min number max number}
Example:se-10-0-0-0(config-location)# voicemail extension-length 8
se-10-0-0-0(config-location)# voicemail extension-length min 5 max 9
Configures the voice mail extension length for the location.
•
•
•
•
Step 8
voicemail vpim-encoding {dynamic | G711ulaw | G726}
Example:se-10-0-0-0(config-location)# voicemail vpim-encoding G711ulaw
Configures the encoding method used to transfer voice-mail messages to this location.
•
•
•
•
•
Step 9
voicemail spoken-name
Example:se-10-0-0-0(config-location)# voicemail spoken-name
(Optional) Enables sending the spoken name of the voice-mail originator as part of the message. If the spoken name is sent, it is played as the first part of the received message. Default: enabled.
•
Step 10
end
Example:se-10-0-0-0(config-location)# end
Exits location configuration mode.
Step 11
network local location id number
Example:se-10-0-0-0(config)# network local location id 1
Enables networking for the local Cisco Unity Express system identified by the location ID number.
•
Caution
Step 12
exit
Example:se-10-0-0-0(config)# exit
Exits configuration mode.
Step 13
show network locations
Example:se-10-0-0-0# show network locations
(Optional) Displays the location ID, name, abbreviation, and domain name for each configured Cisco Unity Express location.
Step 14
show network detail location id number
Example:se-10-0-0-0# show network detail location id 9
(Optional) Displays network information for the specified location ID, including the number of messages sent and received.
Step 15
show network detail local
Example:se-10-0-0-0# show network detail local
(Optional) Displays network information for the local Cisco Unity Express location, including the number of messages sent and received.
Step 16
show network queues
Example:se-10-0-0-0# show network queues
(Optional) Displays information about messages in the outgoing queue that are to be sent from this Cisco Unity Express system. The queue information contains three displays: one for urgent job queue information, one for normal job queue information, and one for running job information.
Examples
The following examples illustrate the output from the show network commands on company ABC's call control system in San Jose with remote voice-mail provided by six remote Cisco Unity Express sites.
se-10-0-0-0# show network locationsID NAME ABBREV DOMAIN101 'San Jose' SJC sjc.cue.abc.com102 'Dallas/Fort Worth' DFW dfw.cue.abc.com201 'Los Angeles' LAX lax.cue.abc.com202 'Canada' CAN can.cue.abc.com301 'Chicago' CHI chi.cue.abc.com302 'New York' NYC nyc.cue.abc.com401 'Bangalore' BAN bang.cue.abc.comse-10-0-0-0# show network detail location id 102Name: Dallas/Fort WorthAbbreviation: DFWEmail domain: dfw.cue.abc.comMinimum extension length: 2Maximum extension length: 15Phone prefix:VPIM encoding: G726Send spoken name: enabledSent msg count: 10Received msg count: 110se-10-0-0-0# show network detail localLocation Id: 101Name: San JoseAbbreviation: SJCEmail domain: sjc.cue.abc.comMinimum extension length: 2Maximum extension length: 15Phone prefix:VPIM encoding: dynamicSend spoken name: enabledThe following example illustrates output from the show network queues command. The output includes the following fields:
•
•
•
se-10-0-0-0# show network queuesRunning Job Queue=================ID TYPE TIME RETRY SENDER RECIPIENT107 VPIM 06:13:26 20 jennifer 1001@sjc.cue.abc.com106 VPIM 06:28:25 20 jennifer 1001@sjc.cue.abc.comUrgent Job Queue=================ID TYPE TIME RETRY SENDER RECIPIENT123 VPIM 16:33:39 1 andy 9003@lax.cue.abc.comNormal Job Queue=================ID TYPE TIME RETRY SENDER RECIPIENT122 VPIM 16:33:23 1 andy 9001@lax.cue.abc.com124 VPIM 16:34:28 1 andy 9003@lax.cue.abc.com125 VPIM 16:34:57 1 andy 9002@lax.cue.abc.com126 VPIM 16:35:43 1 andy 9004@lax.cue.abc.comTroubleshooting Commands
To troubleshoot network configuration in Cisco Unity Express, use the following commands in EXEC mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Downloading and Uploading Network Location Spoken Names
Use the Administration via Telephone (AvT) options to record the spoken names. Those name files are stored in the Lightweight Directory Access Protocol (LDAP) on the Cisco Unity Express module. If you download the files to a server other than the Cisco Unity Express module, you can upload those spoken name files to another Cisco Unity Express module in the network.
The following sections describe this feature:
•
•
Prerequisites
•
•
•
Downloading the Location Spoken Name
To download the network location spoken name, use the following command in Cisco Unity Express EXEC mode:
network copy spokenname url url location id location-id loginname server-login password server-password
where the command arguments are defined as:
url
URL to the spoken name file on the server.
location-id
Network location ID.
server-login
Server login.
server-password
Server password.
The following example uploads the spoken name file rename.wav for location 500:
se-10-0-0-0# network copy spokenname url ftp:/10.4.51.66/rename.wav location id 500 loginname admin password testUploading the Location Spoken Name
To upload the network location spoken name, use the following command in Cisco Unity Express EXEC mode:
network copy spokenname location id location-id url url loginname server-login password server-password
where the command arguments are defined as:
location-id
Network location ID.
url
URL to the spoken name file on the server.
server-login
Server login.
server-password
Server password.
The following example uploads the spoken name file rename.wav for location 500:
se-10-0-0-0# network copy spokenname location id 500 url ftp:/10.4.51.66/rename.wav loginname admin password testDisabling a Network Location
Cisco Unity Express supports disabling a location from the Cisco Unity Express network. A new command is available to disable a network location from sending or receiving Cisco Unity Express voice-mail messages. This command does not delete the network location from the Cisco Unity Express database.
To re-establish transmission of voice-mail messages to and from the network location, use the enable command.
Prerequisites
You will need the network location ID to disable a network location.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Examples
The following example displays the details for network location 15 with networking disabled:
se-10-0-0-0# config tse-10-0-0-0(config)# network location id 15se-10-0-0-0(config-location)# no enable!!!WARNING!!!:Disabling location will disablenetworking to/from this location.Do you wish to continue[n]?:yse-10-0-0-0(config-location)# endse-10-0-0-0(config)# exitse-10-0-0-0#se-10-0-0-0# show network detail location id 15Name: houstonAbbreviation: houEmail domain: how.cue.abcdef.comMinimum extension length: 2Maximum extension length: 15Phone prefix: 4VPIM encoding: dynamicSend spoken name: enabledSend vCard: enabledState: disabledVPIM broadcast ID: vpim-broadcastSent msg count: 1Received msg count: 1The following example re-establishes voice-mail transmission to and from network location 15.
se-10-0-0-0# config tse-10-0-0-0(config)# network location id 15se-10-0-0-0(config-location)# enablese-10-0-0-0(config-location)# endse-10-0-0-0(config)# exitAdding Remote Users to the Local Directory
Cisco Unity Express permits the addition of remote users to the local voice- mail directory.
The local Cisco Unity Express directory is enhanced to allow inclusion of frequently addressed remote users. This capability allows a local voice-mail sender to address a remote recipient using dial-by-name. Additionally, the system provides the sender with a spoken name confirmation of the remote recipient so that the sender can verify that the name and location are correct.
Regardless of the license level, the network module (NM) supports a maximum of 50 remote users and the advanced integration module (AIM) supports a maximum of 20 remote users.
System administrators have a new menu option available on the Cisco Unity Express telephone user interface (TUI) to record the spoken name for the remote users. If a remote user does not have a spoken name recorded, the system uses the remote extension number and location as confirmation to the local sender.
If the vCard option is configured, the remote user's vCard updates the local system with the remote user's first name, last name, or extension.
The following sections describe this feature:
•
•
Impact of Remote Messages on the Local User
Prior to Release 2.1, the local sender had to use blind addressing to send a message to a remote recipient. Now the local sender can use dial-by-name for the remote recipient's address. If a name or number conflicts with another, the system presents the sender with all conflicting addresses to make a selection.
The local sender hears the remote user's spoken name if it is configured by one of the following methods:
•
•
If the remote sender's spoken name is not configured either locally or remotely, the local user hears the remote extension number and remote location name.
When a local user plays back a message from a remote user, the local user hears the remote sender's spoken name or remote phone number, spoken name of the remote office, the date, and the time that the message was sent. If the local system received the message more than 30 minutes after the message was sent, the local user also hears the time when the message was received. If the local user replies to this message, the local system automatically sets up the appropriate remote address information.
If the system cannot deliver a message to a remote site after 6 hours, the local user receives a non-delivery record (NDR) indicating that the message was not sent or that the message was not delivered to the recipient's mailbox. Beginning with Release 2.1, Cisco Unity Express adds a delayed delivery record (DDR), which is a notification left in the sender's mailbox after 60 minutes of trying to deliver the original message. Unlike the NDR, the DDR does not contain the original message as an attachment and does not count against the sender's mailbox capacity. Additionally, the DDR cannot be saved, only deleted. The system stores only one copy of a DDR for a particular message in the sender's mailbox. The user must delete the existing DDR in order to receive an updated DDR for the same message.
Configuring the Local Directory with Remote Users
Configuring remote users requires the following procedures:
•
CLI commands exist to configure the local and remote sites in the system. GUI screens are available to configure the location parameters.
•
See the chapter "Configuring a Location with vCard Information" for that procedure.
•
This section describes this procedure.
•
The administrator uses the TUI to record a spoken name for the remote user and a spoken name for the remote location.
Configuring the remote user can be done in the Cisco Unity Express configuration mode and the EXEC mode. Both modes permit adding the remote user to the local directory but have different capabilities for other user information. Use the remote username location command once, in either mode, to associate the remote user with a network location.
Configuration Mode
Use this Cisco Unity Express configuration mode procedure to configure remote users on the local system.
Prerequisites
The following information is required to configure remote users on the local system:
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
EXEC Mode
Use this Cisco Unity Express EXEC mode procedure to configure remote users on the local system.
Prerequisites
The following information is required to configure remote users on the local system:
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Examples
The following example configures several remote users.
se-10-0-0-0# config tse-10-0-0-0(config)# remote username asmith location sjc createdse-10-0-0-0(config)# remote username asmith phonenumber 84444se-10-0-0-0(config)# remote username tbrown location sjc createdse-10-0-0-0(config)# remote username tbrown phonenumber 81111se-10-0-0-0(config)# remote username jdoe location nyc createdse-10-0-0-0(config)# remote username jdoe phonenumber 92222se-10-0-0-0(config)# remote username sjones location nyc createdse-10-0-0-0(config)# remote username sjones phonenumber 93333se-10-0-0-0(config)# endse-10-0-0-0# remote username asmith fullname display "Al Smith"se-10-0-0-0# remote username asmith fullname first Alse-10-0-0-0# remote username asmith fullname last Smithse-10-0-0-0# remote username tbrown fullname display "Tom Brown"se-10-0-0-0# remote username tbrown fullname first Tomse-10-0-0-0# remote username tbrown fullname last Brownse-10-0-0-0# remote username jdoe fullname display "Jane Doe"se-10-0-0-0# remote username jdoe fullname first Janese-10-0-0-0# remote username jdoe fullname last Doese-10-0-0-0# remote username sjones fullname display "Susan Jones"se-10-0-0-0# remote username sjones fullname first Susanse-10-0-0-0# remote username sjones fullname last Jonesse-10-0-0-0#Displaying Remote Users
Several commands are available to display remote users.
Displaying All Remote Users
The following command displays all remote users configured on the local system:
show remote users
The output for this command may appear similar to the following:
se-10-0-0-0# show remote usersasmithtbrownjdoesjonesDisplaying a Specific Remote User
The following command displays the details for a specific remote user:
show remote user detail username username
where username is the specific remote user.
The output for this command may appear similar to the following:
se-10-0-0-0# show remote user detail username asmith
Full Name: Al SmithFirst Name: AlLast Name: SmithNick Name:Extension: 84444Location Id: sjcDeleting Remote User Information
Several commands are available to delete remote user information from the local directory.
Deleting an Extension Number
The following configuration mode command deletes a remote user's extension number:
no remote username username phonenumber extension-number
where username is the name of the remote user and extension-number is the remote user's extension.
The following example deletes extension 75555 from remote user Al Smith:
se-10-0-0-0# config tse-10-0-0-0(config)# no remote username asmith phonenumber 84444se-10-0-0-0(config)# endDeleting a Display Name
The following EXEC mode command deletes the remote user's display name:
no remote username username fullname display display-name
where username is the name of the remote user and display-name is the remote user's display name.
The following example deletes the display name from remote user Al Smith:
se-10-0-0-0# no remote username asmith fullname display "Al Smith"Deleting a First Name
The following EXEC mode command deletes the remote user's first name:
no remote username username fullname first first-name
where username is the name of the remote user and first-name is the remote user's first name.
The following example deletes the first name from remote user Al Smith:
se-10-0-0-0# no remote username asmith fullname first AlDeleting a Last Name
The following EXEC mode command deletes the remote user's last name:
no remote username username fullname last last-name
where username is the name of the remote user and last-name is the remote user's last name.
The following example deletes the last name from remote user Al Smith:
se-10-0-0-0# no remote username asmith fullname last SmithDeleting a Remote User Entry in Local Directory
The following EXEC mode command deletes the remote user from the local directory:
no remote username username
where username is the name of the remote user.
The following example deletes the remote user Al Smith:
se-10-0-0-0# config tse-10-0-0-0(config)# no remote username asmithse-10-0-0-0(config)# endDownloading and Uploading Remote User Spoken Names
Use the Administration via Telephone (AvT) options to record the spoken names. Those name files are stored in the Lightweight Directory Access Protocol (LDAP) on the Cisco Unity Express module. If you download the files to a server other than the Cisco Unity Express module, you can upload those spoken name files to another Cisco Unity Express module in the network.
The following sections describe this feature:
•
•
Prerequisites
•
•
•
Downloading the Remote User Spoken Name
To download the remote user spoken name, use the following command in Cisco Unity Express EXEC mode:
remote copy spokenname url url username username loginname server-login password server-password
where the command arguments are defined as:
url
URL to the spoken name file on the server.
username
Remote user ID.
server-login
Server login.
server-password
Server password.
The following example uploads the spoken name file abrown.wav for remote user abrown:
se-10-0-0-0# remote copy spokenname url ftp:/10.4.51.66/abrown.wav username abrown loginname admin password testUploading the Remote User Spoken Name
To upload the network location spoken name, use the following command in Cisco Unity Express EXEC mode:
remote copy spokenname username username url url loginname server-login password server-password
where the command arguments are defined as:
username
Remote user ID.
url
URL to the spoken name file on the server.
server-login
Server login.
server-password
Server password.
The following example uploads the spoken name file abrown.wav for remote user abrown:
se-10-0-0-0# remote copy spokenname username abrown url ftp:/10.4.51.66/abrown.wav loginname admin password testConfiguring Caller ID for Incoming Messages
Cisco Unity Express supports caller ID information for incoming voice-mail messages.
When receiving an incoming voice-mail message from an external caller, the system attempts to match the associated caller ID information with an entry in the local directory. If a match is not found and the system is configured to play caller ID information, the system plays the sender's telephone number in the message envelope when the recipient listens to that message. If the system is not configured to play caller ID information, the system plays "Unknown Caller" in the message envelope.
Cisco Unity Express does not verify that the caller ID information is valid. That function is dependent on the central office (CO) and the incoming trunk setup. Additionally, the local system plays caller ID information for Cisco CallManager Express or Cisco CallManager extensions that are not configured in the local Cisco Unity Express directory.
The default caller ID status is disabled. Use the GUI Defaults > Voice Mail option or the CLI command described below to enable or disable playing of caller ID information.
Note
The following sections describe this feature:
•
•
Enabling Caller ID on the Local System
Use the following Cisco Unity Express configuration mode command to enable the playing of caller ID information in the message envelope of incoming external calls.
voicemail callerid
The following example illustrates enabling caller ID information on local system:
se-10-0-0-0# config tse-10-0-0-0(config)# voicemail calleridse-10-0-0-0(config)# exitDisabling Caller ID on the Local System
Use the following Cisco Unity Express configuration mode command to disable the playing of caller ID information in the message envelope of incoming external calls.
no voicemail callerid
The following example illustrates disabling caller ID information on local system:
se-10-0-0-0# config tse-10-0-0-0(config)# no voicemail calleridse-10-0-0-0(config)# exitConfiguring a Location with vCard Information
Cisco Unity Express supports sending and receiving vCard information in voice-mail messages. A remote user's vCard information contains the user's first name, last name, and extension. Cisco Unity Express uses the vCard information from incoming voice profile for Internet mail (VPIM) messages and the recorded spoken name to populate and update a least recent user (LRU) cache with the remote user information. (For more information about configuring the spoken name, see "Adding Remote Users to the Local Directory".)
When addressing a message to a remote user, the local sender hears the spoken name as a confirmation of the intended recipient. The LRU cache is a source of the spoken name.
The maximum length of the LRU cache is 50 users on the network module (NM) and 20 users on the advanced integration module (AIM).
The following sections describe this feature:
•
•
Enabling a Location to Receive vCard Information
The remote location numeric ID is required to enable the location to receive vCard information.
The system default is to send the vCard information.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Examples
The following example enables receipt of vCard information to network locations 23 and nyc:
se-10-0-0-0# config tse-10-0-0-0(config)# network location 23se-10-0-0-0(config-location)# voicemail vcardse-10-0-0-0(config-location)# endse-10-0-0-0(config)# network location nycse-10-0-0-0(config-location)# voicemail vcardse-10-0-0-0(config-location)# endse-10-0-0-0(config)# exitDisplaying vCard Status
Several commands are available to display vCard status.
Displaying vCard Status For a Specific Location
The following Cisco Unity Express EXEC mode command displays details about a specific remote location:
show network detail location id location-id
where location-id is the remote location number.
The following example displays details about network location 15, which has vCard enabled:
se-10-0-0-0# show network detail location id 15Name: houstonAbbreviation: houEmail domain: how.cue.abcdef.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: 0Displaying vCard Status For the Local System
The following EXEC mode command displays details for the local Cisco Unity Express system:
show network detail local
The following example displays details for the local system with vCard enabled:
se-10-0-0-0# show network detail localLocation ID: 10Name: SanJoseCAAbbreviation: sjcEmail domain: sjc.cue.abcdef.comMinimum extension length: 2Maximum extension length: 15Phone prefix:VPIM encoding: G726Send spoken name: enabledSend vCard: enabledState: enabledVPIM broadcast ID: vpim-broadcastDisabling Receipt of vCard Information
Use this procedure to disable receipt of vCard information.
SUMMARTY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Examples
The following command disables receipt of vCard information to network location nyc:
se-10-0-0-0# config tse-10-0-0-0(config)# network location nycse-10-0-0-0(config-location)# no voicemail vcardse-10-0-0-0(config-location)# endse-10-0-0-0(config)# exitConfiguring the LRU Cache
Cisco Unity Express supports a least recent user (LRU) cache that contains vCard information about remote users. An LRU cache is a database of remote users' first names, last names, and spoken names. These remote users are not configured in the Remote User Directory. The users contained in the cache are referred to as cached users.
Network messages update the contents of the LRU cache. When a local sender addresses a voice-mail message to a remote user, the system accesses this information to send a spoken name confirmation about the remote user to the local sender. Each time a network message arrives from a cached user or each time a local sender sends a voice message to a cached user, the system updates the timestamp of the cached user's entry in the LRU cache.
The maximum capacity of the LRU cache is 50 users on the network module (NM) and 20 users on the advanced integration module (AIM). When the LRU cache reaches its maximum capacity, a new entry erases the existing entry with the oldest timestamp. This means that the next time a local sender calls a remote user, the sender will not receive a spoken name confirmation if the remote user is no longer in the LRU cache.
Do one or both of the following to avoid the inconsistent confirmation response:
•
•
The LRU cache contents are saved after system reloads.
By default, the LRU cache is enabled on the local system. Use the GUI Defaults > Voice Mail option or the CLI commands described below to change the status of the LRU cache.
The following sections describe this feature:
Enabling the LRU Cache
Use the following Cisco Unity Express configuration mode command to enable the LRU cache on the local system:
remote cache enable
The following example illustrates enabling the LRU cache on the local system:
se-10-0-0-0# config tse-10-0-0-0(config)# remote cache enablese-10-0-0-0(config)# exitDisabling the LRU Cache
Disabling the cache clears all cache entries and prevents new user entries from being stored in the cache.
Use the following Cisco Unity Express configuration mode command to disable the LRU cache on the local system.
no remote cache enable
The following example illustrates disabling the LRU cache on the local system:
se-10-0-0-0# config tse-10-0-0-0(config)# no remote cache enablese-10-0-0-0(config)# exitDisplaying LRU Cache Data
Use the following Cisco Unity Express EXEC mode command to display the local system's LRU cache data:
show remote cache
The system displays the user ID, location, extension, and last accessed time for each cached user.
se-10-0-0-0# show remote cacheRemote user cache is enabledID LOCATION EXTENSION LAST ACCESSED TIME3014001 sjc 5555 Tue Sep 21 10:38:28 PDT 20046661005 nyc 1111 Tue Sep 21 14:55:11 PDT 2004Configuring Network Broadcast Messages
Cisco Unity Express permits sending broadcast messages to local and remote network locations. Cisco Unity Express permits users with the broadcast privilege to send local and network broadcast messages. Users 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 re-address, re-record, and review the message before sending it out. The sender also has the option to set the number of days the broadcast message plays before the system deletes it. The maximum life of a broadcast message is 30 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 has to 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 up.
It is possible for the MWI lights to turn on for a broadcast message on some systems but not for others.
The following sections describe this feature:
•
•
•
•
•
•
•
•
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 users 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.
Prerequisites
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)# exitConfiguring the Broadcast Message VPIM ID for a Network Location
Use the following procedure to configure the VPIM ID for broadcast messages for a network location.
Prerequisites
The following information is required to configure the broadcast message VPIM ID for a network location:
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Examples
The following example sets the VPIM ID to ny-270 for network location 150:
se-10-0-0-0# config tse-10-0-0-0(config)# network location id 150se-10-0-0-0(config-location)# voicemail broadcast vpim-id ny-270se-10-0-0-0(config-location)# endse-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 to turn on 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
Several 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.cue.abcdef.comLength(secs): 10Start time: 21:12:54 Nov 23 2004 PSTEnd time: 11:48:06 Dec 4 2004 PSTMessage ID: JMX0824L4R4-NM-FOC08221WSQ-1103084723247-NBCMSender: 5555@nyc.cue.abcdef.comLength(secs): 30Start time: 08:41:09 Dec 7 2004 PSTEnd time: 09:00:00 Jan 3 2005 PSTDisplaying Broadcast Messages Received Per Mailbox
The following command is modified to display broadcast message information:
show voicemail mailboxes
A new 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
A new 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: 4networking 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 (%): 2Deleting 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 the 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 the 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 the MWI Lights for Broadcast Messages
Use the following Cisco Unity Express configuration mode command to turn off the MWI lights for broadcast messages.
no voicemail broadcast mwi
The following example illustrates disabling 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 Distribution Lists
Cisco Unity Express permits configuration of distribution lists that allow users to send a voice-mail message to multiple recipients at one time. This section describes distribution lists and contains the following sections:
•
•
•
•
•
Members of a Distribution List
Members of a distribution list can be any combination of the following:
•
A remote user that is statically configured on the local system can be a member of a distribution list. However, that remote user cannot own a distribution list on the local system.
•
•
•
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.
•
Specify the location ID and extension of the blind address. The system verifies the location ID and the extension length.
Public Distribution Lists
All local users of the system can use a public distribution list in the address of a voice-mail message. Table 10 describes the features of a public distribution list.
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.
Private Distribution Lists
Any local user can create private distribution lists that are visible and accessible only to the user. Table 11 describes the features of private distribution lists.
Properties of Distribution Lists
Cisco Unity Express distribution lists have the following properties:
•
Valid names have a maximum of 64 characters and include the letters A to Z, a to z, digits 0 to 9, and the characters underscore (_), dot (.), and dash (-). Names must start with a letter. Do not use spaces in the name.
Valid private list numbers are 1 to 5.
Public list numbers have a maximum length of 15 digits. A list number can match the user's or GDM's telephone number but must not match another local public list number.
The system automatically assigns 9999 to the default everyone public list. An administrator can change this number using the GUI menu option Voice Mail > Distribution Lists > Public Lists. The 9999 number cannot be changed using TUI options or CLI commands.
•
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 user.
When a user 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.
•
The default everyone public list has a spoken name by default. An administrator can change this name using the TUI.
•
This same series of actions applies to the removal of a group, except for private lists (a group cannot own a private list).
•
Differences Between Cisco Unity Express and Cisco Unity Distribution Lists
Table 12 describes important differences between the Cisco Unity Express and Cisco Unity distribution lists.
Configuring Public Distribution Lists
Use this procedure to create public distribution lists.
Note
Prerequisites
Local and remote users must be previously defined on the system.
The following information is required to create a public distribution list:
•
•
The following information is required to add members to a distribution list:
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Examples
The following example creates public distribution list number 5 for engineers:
se-10-0-0-0# config tse-10-0-0-0(config)# list name engineers number 5 createse-10-0-0-0(config)# list number 5 owner abcdefse-10-0-0-0(config)# list number 5 owner progmgrsse-10-0-0-0(config)# list number 5 member abcdef type userse-10-0-0-0(config)# list number 5 member xxyyzz type userse-10-0-0-0(config)# list number 5 member betamgrs type groupse-10-0-0-0(config)# list number 5 member tech type gdmse-10-0-0-0(config)# list number 5 member nyc7777 type blindse-10-0-0-0(config)# exitDisplaying 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:
show lists public
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:
se-10-0-0-0# show lists publicList number List Name Type5 engineers Public9999 everyone PublicNumber: 5Name: engineersType: PublicDescription:Owners:abcdef Local Userprogmgrs GroupMembers:abcdef Local Userxxyyzz Local Userprogmgrs Grouptechs General Delivery Mailboxtech25 Remote Usernyc5555 Blind AddressDisplaying Details of a Public Distribution List
The following Cisco Unity Express EXEC mode command displays details of a specific public distribution list:
show lists 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 lists detail public name engineers
Number: 5
Name: engineers
Type: PublicDescription:Owners:abcdef userprogmgrs groupMembers:abcdef userxxyyzz userbetamgrs grouptechs gdmtech25 remotenyc5555 blindThe 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 user or group:
show lists owner owner-id
where owner-id is the name of a user 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:
se-10-0-0-0# show lists owner abcdefOwner: abcdefList Number List Name List Type4 projectteam Private List5 engineers Public List25 managers Public ListDisplaying 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 user:
show lists 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 user. An error message appears if list-name, list-number, or owner-id does not exist.
The list owner and local users who are members of the ViewPrivateList or Administrators groups can view the private lists that belong to a particular user.
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:
se-10-0-0-0# show lists detail private name projectteam owner abcdefNumber: 4Name: projectteamType: PrivateDescription:Owner:abcdefMembers:tech1 usertech2 usertesters grouptech10 remoteThe command show lists detail private number 4 owner abcdef 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:
se-10-0-0-0# config tse-10-0-0-0(config)# list number 10 deletese-10-0-0-0(config)# exitse-10-0-0-0#
Posted: Fri Jan 13 04:50:01 PST 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
