- 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
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:
- Overview of Cisco Unity Express Networking
- Configuring Network Locations
- Disabling a Network Location
- Downloading and Uploading Network Location Spoken Names
- Adding Remote Subscribers to the Local Directory
- Downloading and Uploading Remote Subscriber Spoken Names
- Configuring a Location with vCard Information
- Configuring the LRU Cache
- Configuring the Broadcast Message VPIM ID for a Network Location
Overview of Cisco Unity Express Networking
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 Unified Communications Manager or Cisco Unified Communications Manager Express call control platforms. Supported networked voice-mail configurations include:
- Cisco Unity Express to Cisco Unity Express
- Cisco Unity Express to Cisco Unity
- Cisco Unity to Cisco Unity Express
Cisco Unity Express must be installed and configured at each remote location.
You must configure VPIM networking on Cisco Unity, including the primary location for Cisco Unity and the delivery locations for remote Cisco Unity Express locations.
Types of Remote Addressing
Cisco Unity Express supports the following types of remote addressing:
Blind Addressing
A subscriber can send a message to another subscriber on a remote location, which must be configured on the local (sender’s) system. The sender addresses the message using the location ID of the remote system plus the recipient’s extension number at the remote location.
When the message is sent to the remote subscriber, the sender will not hear a confirmation of the recipient’s name or extension. This is blind addressing.
Spoken Name Confirmation for Remote Subscribers
Administrators can assign user IDs and extensions in the local Cisco Unity Express directory for subscribers at existing remote locations. Additionally, administrators or other privileged subscribers can record spoken names for these subscribers using the Administration via Telephone (AvT) feature.
If the local system has vCard information enabled, incoming vCard information updates the remote subscriber information on the local system. The vCard information may contain the remote subscriber’s first name, last name, and spoken name. This information is stored in the least recently used (LRU) cache.
A sender on the local system can address a message to a remote subscriber using dial-by-name or dial-by-extension. If a spoken name for the recipient is recorded, the sender hears the spoken name as confirmation. If the recipient does not exist in the local directory but is in the LRU cache, the sender hears the LRU cache information as confirmation. If the remote subscriber is not in the directory or the cache, the sender receives the recipient’s location ID and extension.
Delivery Notifications
Cisco Unity Express supports the following message delivery notification types:
Non-Delivery Receipt (NDR)
If the system cannot deliver a message to a remote site after 6 hours, the local sender receives a non-delivery receipt (NDR) indicating the message was not sent or that the message was not delivered to the recipient’s mailbox.
This receipt indicates the reason for nondelivery. If nondelivery is due to the recipient’s mailbox being full, nonexistent, or disabled, the nondelivery 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.
Delayed Delivery Record (DDR)
Cisco Unity Express sends a delayed delivery record (DDR) to the local 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.
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 sender must delete the existing DDR in order to receive an updated DDR for the same message.
Configuring Network Locations
Follow this procedure to configure the network locations.
Prerequisites
- Cisco Unity Express must be installed and configured at each remote location.
- Network connectivity between all Cisco Unity Express and Cisco call control system sites must be established.
- Ensure that VPIM networking is configured on Cisco Unity, including the primary location for Cisco Unity and the delivery locations for remote Cisco Unity Express locations.
Required Data for This Procedure
The following information is required to configure networking on Cisco Unity Express:
- Network location ID number—Unique ID number for each location used by the voice-mail sender to send a remote message. The maximum length of the number is 7 digits. Cisco Unity Express supports a maximum of 500 locations.

Note Avoid creating locations with conflicting IDs, such as 100, 1001, and so forth. This may lead to ambiguity while sending messages to these locations and may lead to messages being addressed incorrectly.
- E-mail domain name—E-mail domain name or IP address for the remote voice-mail system. The domain name is attached to the local voice-mail originator’s extension when sending a VPIM message. The local system’s e-mail domain name must be configured to receive remote voice-mail messages.
- (Optional) Location name—Descriptive name of the network location.
- (Optional) Abbreviated location name—Abbreviated name of the network location. Maximum length of the name is 5 characters.
- (Optional) Voice-mail system telephone number prefix—Phone number prefix that is added to a local voice-mail originator’s extension to create a VPIM address. A prefix is required only if an e-mail domain services multiple locations, and extensions between the locations are not unique. The maximum length of the prefix is 15 digits. The default prefix is empty.
- (Optional) Length of the local voice-mail system extensions. The default minimum is 2, the default maximum is 15.
- (Optional) VPIM encoding scheme—Encoding scheme options for translating voice-mail messages at the local Cisco Unity Express system are dynamic, G.711mu-law, or G.726. The default scheme is dynamic.
- (Optional) Voice-mail spoken name capability—Enabling this functionality permits receipt of a voice-mail originator’s spoken name, which is played at the beginning of the received voice-mail message.
- (Optional) Broadcast VPIM ID—Used for sending and receiving broadcast messages between network locations. See Configuring the Broadcast Message VPIM ID for a Network Location for more information.
- (Optional) Secure Messaging—Used for supporting secure messaging. Supported in Cisco Unity Express 8.6 and later versions. See the “Configuring Secure Messaging” section for more information.
- Location ID for the local system.
SUMMARY STEPS
3. (Optional) name location-name
4. (Optional) abbreviation name
6. (Optional) voicemail phone-prefix digit string
7. (Optional) voicemail extension-length number [min number | max number]
8. (Optional) voicemail vpim-encoding {dynamic | G711ulaw | G726}
9. (Optional) voicemail spoken-name
10. (Optional) voicemail secure-messaging
12. Repeat Steps 2 through 11 for each remote location.
13. network local location id number
DETAILED STEPS
Examples
The following examples illustrate the output from the show network commands on company Mycompany’s call control system in San Jose with remote voice-mail provided by six remote Cisco Unity Express sites.
The following example illustrates output from the show network queues command. The output includes the following fields:
- ID—Job ID.
- Retry—Number of times that Cisco Unity Express has tried to send this job to the remote location.
- Time—Time when the job will be resent.
Disabling a Network Location
Cisco Unity Express supports disabling a location in the Cisco Unity Express network from sending or receiving Cisco Unity Express voice-mail messages. The system does not delete the network location from the Cisco Unity Express database.
To reestablish voice-mail message transmission to and from the network location, use the enable command.

Note Deleting the e-mail domain for a network location also disables the location.
SUMMARY STEPS
DETAILED STEPS
Examples
The following example displays the details for network location 15 with networking disabled:
The following example re-establishes voice-mail transmission to and from network location 15.
Downloading and Uploading Network Location Spoken Names
Use the Administration via Telephone (AvT) options to record the spoken names. You can download these spoken names from a Cisco Unity Express module to an external server or upload them from an external server to a Cisco Unity Express module.
The following sections describe this feature:
- Required Data for This Procedure
- Downloading the Location Spoken Name
- Uploading the Location Spoken Name
Required Data for This Procedure
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:
The following example uploads the spoken name file rename.wav for location 500:
Uploading 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:
The following example uploads the spoken name file rename.wav for location 500:
Adding Remote Subscribers to the Local Directory
Cisco Unity Express permits the addition of remote subscribers to the local voice- mail directory.
The local Cisco Unity Express directory allows inclusion of frequently addressed remote subscribers. 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 NM-CUE-EC supports a maximum of 100 remote subscribers, the NM-CUE supports a maximum of 50 remote subscribers, and the AIM-CUE supports a maximum of 20 remote subscribers.
Use the AvT to record the spoken name for the remote subscribers. If a remote subscriber 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 subscriber’s vCard updates the local system with the remote subscriber’s first name, last name, or extension.
The following sections describe this feature:
- Configuring the Local Directory with Remote Subscribers
- Displaying Remote Subscribers
- Deleting Remote Subscriber Information
Configuring the Local Directory with Remote Subscribers
Configuring remote subscribers 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 subscriber and a spoken name for the remote location.
Configuring the remote subscriber can be done in the Cisco Unity Express configuration mode and the EXEC mode. Both modes permit adding the remote subscriber to the local directory but have different capabilities for other subscriber information. Use the remote username location command once, in either mode, to associate the remote subscriber with a network location.
Configuration Mode
Use this Cisco Unity Express configuration mode procedure to configure remote subscribers on the local system.
Required Data for This Procedure
The following information is required to configure remote subscribers on the local system:
SUMMARY STEPS
2. remote username username location location-id create
DETAILED STEPS
EXEC Mode
Use this Cisco Unity Express EXEC mode procedure to configure remote subscribers on the local system.
Required Data for This Procedure
The following information is required to configure remote subscribers on the local system:
SUMMARY STEPS
1. remote username username location location-id create
2. remote username username fullname display display-name
DETAILED STEPS
Examples
The following example configures several remote subscribers.
Displaying Remote Subscribers
Several commands are available to display remote subscribers.
Displaying All Remote Subscribers
The following command displays all remote subscribers configured on the local system:
The output for this command may appear similar to the following:
Displaying a Specific Remote Subscriber
The following command displays the details for a specific remote subscriber:
show remote user detail username username
where username is the specific remote subscriber.
The output for this command may appear similar to the following:
Deleting Remote Subscriber Information
Several commands are available to delete remote subscriber information from the local directory.
Deleting an Extension Number
The following configuration mode command deletes a remote subscriber’s extension number:
no remote username username phonenumber extension-number
where username is the name of the remote subscriber and extension-number is the remote subscriber’s extension.
The following example deletes extension 75555 from remote subscriber User 2:
Deleting a Remote Subscriber Entry in Local Directory
The following EXEC mode command deletes the remote subscriber from the local directory:
remote username username delete
where username is the name of the remote subscriber.
The following example deletes the remote subscriber User 2:
Deleting a Remote Username
The following EXEC mode commands delete the remote subscriber’s name:
no remote username username fullname display display-name
no remote username username fullname first first-name
no remote username username fullname last last-name
where username is the name of the remote subscriber, display-name is the remote subscriber’s display name, first-name is the remote subscriber’s first name, and last-name is the remote subscriber’s last name.
The following example deletes the display name from remote subscriber User 2:
The following example deletes the first name from remote subscriber User 2:
The following example deletes the last name from remote subscriber User 2:
Downloading and Uploading Remote Subscriber Spoken Names
Use the Administration via Telephone (AvT) options to record the spoken names. You can download these spoken names from the Cisco Unity Express module to an external server or upload the names from an external server to the Cisco Unity Express module.
The following sections describe this feature:
- Required Data for This Procedure
- Downloading the Remote Subscriber Spoken Name
- Uploading the Remote Subscriber Spoken Name
Required Data for This Procedure
Downloading the Remote Subscriber Spoken Name
To download the remote subscriber 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:
The following example uploads the spoken name file user1.wav for remote subscriber user1:
Uploading the Remote Subscriber Spoken Name
To upload the network location 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:
The following example uploads the spoken name file user1.wav for remote subscriber user1:
Configuring a Location with vCard Information
Cisco Unity Express supports sending and receiving vCard information in voice-mail messages. A remote subscriber’s vCard information contains the subscriber’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 used (LRU) cache with the remote subscriber information. (For more information about configuring the spoken name, see Adding Remote Subscribers to the Local Directory.)
When addressing a message to a remote subscriber, 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 number of subscribers that the LRU cache stores depends on the hardware module installed. See the Release Notes for Cisco Unity Express for the maximum cached users supported.
The following sections describe this feature:
Enabling and Disabling vCard Information
The remote location numeric ID is required to enable the location to receive vCard information.
SUMMARY STEPS
DETAILED STEPS
Examples
The following example enables receipt of vCard information to network locations 23 and nyc:
The following command disables receipt of vCard information to network location nyc:
Displaying 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:
Displaying vCard Status For the Local System
The following EXEC mode command displays details for the local Cisco Unity Express system:
The following example displays details for the local system with vCard enabled:
Configuring the LRU Cache
Cisco Unity Express supports a least recently used (LRU) cache that contains vCard information about remote subscribers. An LRU cache is a database of remote subscribers’ first names, last names, and spoken names. These remote subscribers are not configured in the Remote User Directory. The subscribers 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 subscriber, the system accesses this information to send a spoken name confirmation about the remote subscriber 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.
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 subscriber, the sender will not receive a spoken name confirmation if the remote subscriber is no longer in the LRU cache. The number of subscribers that the LRU cache stores depends on the hardware module installed. See the Release Notes for Cisco Unity Express for the maximum cached users supported.
Do one or both of the following to avoid the inconsistent confirmation response:
- To ensure that a sender always receives a spoken name confirmation for a remote subscriber, configure the remote subscriber in to the Remote User Directory.
- Disable the LRU cache.
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 and Disabling the LRU Cache
Use the following Cisco Unity Express configuration mode command to enable the LRU cache on the local system:
The following example illustrates enabling the LRU cache on the local system:
Use the following Cisco Unity Express configuration mode command to disable the LRU cache on the local system. Disabling the cache clears all cache entries and prevents storage of new subscriber entries.
The following example illustrates disabling the LRU cache on the local system:
Displaying LRU Cache Data
Use the following Cisco Unity Express EXEC mode command to display the local system’s LRU cache data:
The system displays the location ID, location name, extension, and last accessed time for each cached user.
Configuring 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.
Required Data for This Procedure
SUMMARY STEPS
2. network location id location-id
DETAILED STEPS
Examples
The following example sets the VPIM ID to ny-270 for network location 150:
Troubleshooting Commands
To troubleshoot network configuration in Cisco Unity Express, use the following commands in EXEC mode.
SUMMARY STEPS
1. trace networking smtp [ all | receive | send | work ]
2. trace networking vpim [all | receive | send]
3. trace networking sysdb [all]
5. trace networking database [ all | connection | execute | garbage | largeobject | mgmt | query | results | transaction ]