Cisco Unity Express VoiceMail and Auto Attendant CLI Administrator Guide

Sharing Ports Among Applications and Triggers

One of the parameters that you may configure for the voice-mail and auto-attendant applications is the maximum number of callers who can concurrently access the application at any specific time. This parameter, maxsessions, is limited by the number of ports on the Cisco Unity Express module. (See Recording a Prompt File for the number of ports on your module.) For Cisco Unified Communications Manager, the ports are configured using the ctiport command (see Configuring JTAPI Parameters (Cisco Unified Communications Manager Only)).

Consider your expected call traffic when assigning the number of ports to an application. One application might need more available ports than another, but each application must have at least one port available for incoming calls.

Suppose, for example, that your module has four ports and you assign four to the voice-mail application maxsessions and four to the auto-attendant maxsessions. If four callers access voice-mail simultaneously, no ports will be available for auto-attendant callers. Only when zero, one, two, or three callers access voice-mail simultaneously will at least one port be available for auto-attendant.

Suppose, instead, that you assign three to the voice-mail maxsessions and three to the auto-attendant maxsessions. At no time will one application use up all the ports. If voice-mail has three active calls, one caller can access auto-attendant. A second call to auto-attendant will not go through at that moment.

Similarly, you must assign the maxsessions parameter to each application trigger, which is the telephone number that activates the application’s script. The value of the trigger’s maxsessions cannot exceed the application’s maxsessions value.

Required Data for This Procedure

The following information is required to configure the default voice-mail application:

• Application name: voicemail
• Maximum number of subscribers who can access voice-mail simultaneously

SUMMARY STEPS

1. config t

2. ccn application voicemai l

3. description “ text ”

4. maxsessions number

5. end

6. exit

7. show ccn application

8. copy running-config startup-config

DETAILED STEPS

Example

The following example illustrates the show ccn application output:

Types of Mailboxes

Cisco Unity Express supports two types of mailboxes:

• Personal mailbox—This mailbox is assigned to a specific subscriber and is accessible only by this subscriber. When a caller leaves a message in this mailbox, the message waiting indicator (MWI) light turns on.
• General delivery mailbox (GDM)—This mailbox is assigned to a group of subscribers. (See Adding and Modifying a Group for the definition of group members.) All members in the group have access to the mailbox. When a caller leaves a message in this mailbox, no MWI is turned on. Instead, when a member logs in to the personal mailbox, the mailbox menu allows the member to access the messages in each GDM to which the member belongs. Only one person can access the GDM at a time. After the first person saves or deletes a message in the GDM, the message is no longer played as “new” for any subsequent members.
• Announcement-only mailbox—This mailbox can play the user greeting and disconnect the call only; it cannot take any messages from callers or send messages. For more information, see the “Configuring an Announcement-Only Mailbox” section.

Mailbox Properties

• Cisco Unity Express supports IP telephones using Skinny Client Control Protocol (SCCP) or analog telephones behind an SCCP gateway (such as the Cisco VG 248 or the Cisco ATA). Media Gateway Control Protocol (MGCP) IP telephones, analog FXS telephones on the Cisco Unified CME router, and soft telephones are not supported.
• Only the owner of a personal mailbox can delete messages in the mailbox. All members of a GDM can delete messages in the mailbox. The administrator cannot delete messages or display the length of time for which messages are stored in the system. When the mailbox owner logs in to the voice mailbox, the application notifies the owner of any expired messages.

If the mandatory message expiry feature is enabled, the owner must delete the expired messages. If the mandatory message expiry feature is disabled, the owner can delete or save each message.

If a message is saved from the expired messages menu, the expiry timer is restarted for that message.

• Mailboxes can have different storage sizes. Consider the purpose of the mailbox when assigning a smaller or larger size than the default. The aggregate of all mailboxes cannot exceed the maximum storage allowed on your system. See Recording a Prompt File for the mailbox storage capacity for your system, and use the show voicemail usage command to display the amount of storage already configured.

Configuring Mailboxes

Follow this procedure to configure voice mailboxes.

Prerequisites

Verify that the users and groups that will have voice mailboxes are configured before using this procedure. If you have not created the users and groups, see Adding and Modifying a User or Adding and Modifying a Group.

Required Data for This Procedure

System-wide mailbox default values were configured during the installation process. If necessary, modify any of the following values for a specific mailbox:

• Mailbox size
• Expiration time in days
• Message size

Use the show voicemail limits command to display the default values. See Configuring System-Wide Voice-Mail Parameters for more information about system-wide mailbox default values.

SUMMARY STEPS

1. config t

2. voice mailbox owner name [ size seconds ]

3. description “ text ”

4. enable

5. expiration time days

6. greeting { alternate | standard }

7. mailboxsize seconds

8. messagesize seconds

9. tutorial

10. zerooutnumber “ number ”

11. end

12. exit

13. show voicemail { detail { mailbox | user } name | limits | mailboxes [ idle days ] | usage | users }

14. copy running-config startup-config

DETAILED STEPS

	Command or Action	Purpose
Step 1	config t   se-10-0-0-0# config t	Enters configuration mode.
Step 2	voice mailbox owner name [ size seconds ]   se-10-0-0-0(config)# voice mailbox owner user3 se-10-0-0-0(config)# voice mailbox owner sales	Creates a mailbox for the name value and with storage size seconds value, and enters mailbox configuration mode. This command maps the subscriber’s name and extension (configured using the username command) to the voice mailbox.
Step 3	description “ text ”   se-10-0-0-0(config-mailbox)# description “User 3 mailbox”	(Optional) Enters a description of the mailbox. Use double quotes around the text.
Step 4	enable   se-10-0-0-0(config-mailbox)# enable	Activates the new mailbox or reactivates the disabled mailbox.
Step 5	expiration time days   se-10-0-0-0(config-mailbox)# expiration time 10	Sets the number of days for which messages are stored in the mailbox. The default is 30 days. This value takes precedence over the system-wide expiration time.
Step 6	greeting { alternate | standard }   se-10-0-0-0(config-mailbox)# greeting standard	Specifies which greeting to use when a caller reaches the mailbox. The mailbox owner can record standard and alternate greetings from the telephone user interface (TUI). If the subscriber has not recorded any messages, the default recording is used. Note Beginning in Cisco Unity Express 7.1, additional options for the greeting command are available. See Configuring Multiple Greetings.
Step 7	mailboxsize seconds   se-10-0-0-0(config-mailbox)# mailboxsize 300	Specifies the storage size of the mailbox, in seconds. This is the same as the size parameter mentioned in Step 2.
Step 8	messagesize seconds   se-10-0-0-0(config-mailbox)# messagesize 120	Specifies the maximum size of an incoming message, in seconds.
Step 9	tutorial   se-10-0-0-0(config-mailbox)# tutorial	Enables the mailbox tutorial program when the telephone subscriber logs in to the voice-mail system for the first time. The default is enabled. If the tutorial command is enabled after the mailbox is configured, the tutorial will start again but will confirm the subscriber’s previous choices, rather than erasing them all. Use the no tutorial command to disable the tutorial.
Step 10	zerooutnumber “ number ”   se-10-0-0-0(config-mailbox)# zerooutnumber “2100”	Specifies the extension where a caller is routed when the caller presses “0’ to reach an operator after being transferred to a subscriber’s mailbox.
Step 11	end   se-10-0-0-0(config-mailbox)# end	Exits mailbox configuration mode.
Step 12	exit   se-10-0-0-0(config)# exit	Exits configuration mode.
Step 13	show voicemail { detail { mailbox | user } name | limits | mailboxes [idle days] | usage | users }   se-10-0-0-0# show voicemail detail mailbox sales se-10-0-0-0# show voicemail detail mailbox user1 se-10-0-0-0# show voicemail detail user user3 se-10-0-0-0# show voicemail limits se-10-0-0-0# show voicemail mailboxes se-10-0-0-0# show voicemail mailboxes idle 5 se-10-0-0-0# show voicemail usage se-10-0-0-0# show voicemail users	Displays voice mailbox properties. detail —Displays the details for a configured mailbox for the subscriber with the specified user ID. For a group mailbox, this is the name of the mailbox, not the owner of the mailbox. If a subscriber is an owner of a group mailbox, details for both the subscriber’s personal and group mailboxes are displayed. limits —Displays the default values for all mailboxes. mailboxes —Displays all configured mailboxes and their current mailbox storage status. The idle parameter displays the mailboxes that have been inactive for at least the specified number of days. usage —Displays how much of the system’s voice-mail capacity has been used or configured. users —Lists the local voice-mail subscribers.
Step 14	copy running-config startup-config   se-10-0-0-0# copy running-config startup-config	Copies the configuration changes to the startup configuration.

Examples

The following example configures a mailbox for a subscriber and displays the output of the show commands:

Configuring Multiple Greetings

Beginning in version 7.1, you can configure multiple greetings. These greetings fall into the following three categories:

• Standard greetings
• Alternate greetings

This category includes the following types of greetings:

– Alternate

– Meeting

– Vacation

– Extended absence

• State-based greetings:

This category includes the following types of greetings:

– Busy

– Closed

– Internal

By default, the standard greeting is enabled and none of the alternate or state-based greetings are enabled. The standard greeting is always enabled but if one of the alternate greetings is enabled, it takes precedence over the standard and state-based greetings.

You can enable one or all of the state-based greetings. These greetings are played when no alternate greeting is enabled and the following conditions apply:

• When the system is busy, the busy greeting is played. When enabled, the busy greeting has precedence over the other state-based greetings.
• During nonbusiness hours, the closed greeting is played.
• When the call is from an internal number, the internal greeting is played.

Except for the standard greeting, when you enable a greeting, you can also specify an end date for the greeting.

You can also perform the following actions for all of the greetings:

• Set the source of the greeting.
• Upload a greeting.

Set the source of the greeting to one of the following:

• System greeting

This greeting comes with the system and is made of system prompts.

• User recording

This greeting is recorded/uploaded by the user. It can be recorded whether or not it is enabled.

• None

This greeting is an empty greeting and can be selected if you want no greeting to be played.

By default, the source is the custom user recorded greeting. If the custom greeting is enabled and there is no user recording, the system greeting is played.

SUMMARY STEPS

1. config t

2. voice mailbox owner name

3. greeting {alternate | meeting | vacation | extended-absence | busy | internal | closed } { enable | enable until month month day day time hh : mm } recording-type {user-recording | none | system-default}

4. exit

5. voicemail default biz-schedule name

6. end

7. voicemail mailbox copy owner owner greeting { alternate | meeting | vacation | extended-absence | busy | internal | closed } url url username username password password

8. voicemail mailbox delete owner owner greeting { alternate | meeting | vacation | extended-absence | busy | internal | closed } user-recording

9. show voicemail detail mailbox name

DETAILED STEPS

Examples

The following is sample output from the show voicemail detail mailbox command:

Configuring PINless Mailbox Access

Cisco Unity Express 3.2 offers the optional PINless voice mail feature, by which a subscriber can log in to their mailbox without a PIN. There are two modes of PINless voice mail access:

• To allow PINless access to voice mail only from the voice mailbox owner’s configured extension or E.164 number. PINless login is not allowed from a subscriber’s fax number.
• To allow PINless access to the mailbox from any phone.

Note In both of these scenarios, people other than the intended recipient can listen to the messages in the voice mailbox configured to offer PINless access.

Prerequisites

Cisco Unity Express 3.2 or a later version

The TUI and PINless Login

A mailbox configured to have PINless access only from its owner’s primary extension can be accessed from that phone without its owner’s user ID or PIN; however, if that mailbox is accessed from any other extension, its owner’s user ID and PIN are both required. To get the menu for entering these, the subscriber must press ‘*-*’ from the main mailbox menu.

A mailbox configured to have PINless access from any phone needs neither user ID nor PIN to be accessed from its owner’s primary extension; however, when accessed from any other phone, that mailbox requires its owner’s user ID. To get the menu for entering this, the subscriber must press ‘*-*’ from the main mailbox menu.

Outcall Notification

On an outcall notification, the subscriber can enter their PIN to login to the mailbox. If PINless login from any phone is configured for that mailbox, then that subscriber can access the mailbox directly without challenge during outcall notification. If you configure PINless login to be from a subscriber extension only, that subscriber must enter the PIN to login to the mailbox during notification if notification is not to any of the subscriber's configured phones.

PIN Expiration

When PINless login is configured, the PIN expiration does not apply. If PINless login from subscriber’s phones is enabled, PIN expiration applies only when logging into the mailbox from an extension other than the mailbox owner’s own.However, this applies only to personal mailboxes. To configure the PIN expiration in conjunction with PINless configuration and AVT, see Administration Via Telephone.

Account Lockout, Mailbox In Use, and Mailbox Disabled

Account lockout, mailbox in use, and mailbox disabled apply regardless of PINless configuration.

Administration Via Telephone

PINless login applies only to the personal mailboxes; it does not apply to Administration Via Telephone (AvT). A subscriber must always enter both their extension and their PIN when logging into AvT.

If the subscriber’s PIN has expired, the subscriber will be unable to log into AvT until they change their PIN. However, AvT will not prompt them to do so, and if their mailbox is configured to be PINless, the system does not prompt them to change their PIN when accessing their voice mailbox. Under these conditions, the subscriber must manually change their PIN by using one of the three following options:

• CLI, with the command username [name] pin [digits]
• GUI, on the User Profile page)
• TUI (under Setup Options > Personal Settings)

Tutorial

When a subscriber logs into their mailbox and the tutorial is run, the tutorial feature always requires them to set their PIN even if they have been configured to have PINless login.

VoiceViewExpress and PINless Login

When a PINless subscriber accesses VoiceViewExpress from their primary extension, they are taken directly to the home page. If that subscriber accesses VoiceView from some other phone, they must delete the autopopulated mailbox ID. They do this by going to the home page of the mailbox to which the phone is registered and pressing the “logout” softkey to get the login page. Here they must enter their own user ID, and also their PIN, unless they have been configured to have PINless voice mail from any phone.

Voice Message On Disabling Pinless Login

When you disable the PINless login for a mailbox, the system generates a new voice message and stores it in the mailbox: "Your mailbox was enabled to login without password and later it was disabled. If you have any questions contact the system administrator."

Voice Message on Changing from PINless Login from Any Phone to PINless Login from Subscriber’s Phone

Whenever you change a voice mailbox configuration from PINless login from any phone to PINless login from subscriber’s phone, the system generates a message: "Your mailbox was enabled to login without password from any phone and later it was disabled. If you have any questions contact the system administrator."

If you want to change PIN login behavior for a mailbox, use the login pinless command.

Starting in Cisco Unity Express config-mailbox mode, enter the following command:

[no|default] login pinless {subscriber-phones | anyphone}

The no login pinless... command forces a subscriber to enter a PIN in order to access the voice mailbox.

The default login pinless... command has the same effect as the no login pinless... command, because a PIN is required to access voice mailboxes by default.

The login pinless subscriber-phones command allows a caller to access the voice mailbox from the subscriber's configured extension, E.164, or fax numbers without requiring a PIN. Callers not originating from one of these sources will be required to enter a PIN.

The login pinless any-phone command allows any caller to access to the voice mailbox without entering a PIN.

Note Although this command appears under the GDM configuration, it is valid only for personal mailboxes. If you try to use the command in the GDM configuration, you get an error message.

The following Cisco Unity Express EXEC mode command for displaying mailbox details also displays the PINless login configuration.

show voicemail detail mailbox [ owner ]

Unlocking a Voice Mailbox

If a mailbox becomes locked, the telephone subscriber will hear a message stating that the mailbox is unavailable. Use the voice mailbox unlock command to unlock the mailbox.

Starting in Cisco Unity Express EXEC mode, enter the following command:

voice mailbox unlock { owner name | telephonenumber tel-number }

This command is equivalent to the GUI operation of clicking the Unlock icon under Voice Mail > Mailboxes.

Refreshing Message Waiting Indicators

Occasionally the MWI lights on a subscriber’s telephone get out of synchronization with the voice message status of the mailbox. When this condition happens, the MWI light is lit although the mailbox has no new messages or the MWI light is not lit although the mailbox has new messages.

Use the mwi refresh all or mwi refresh telephonenumber command to refresh the MWI lights and to synchronize the mailbox message status and MWI lights. If the subscriber has no messages, the MWI turns off. If the subscriber has voice messages, the MWI light turns on.

Starting in Cisco Unity Express EXEC mode, enter the following command:

mwi refresh all

or

mwi refresh telephonenumber tel-number

where tel-number is the telephone number of a specific extension.

This command is equivalent to the GUI operation of clicking the Refresh All or Refresh Selected icons under Voice Mail > Message Waiting Indicators > Refresh.

Configuring an Announcement-Only Mailbox

Beginning in version 7.1, you can configure announcement-only mailboxes. These mailboxes can play the user greeting and disconnect the call only; they cannot take any messages from callers or send messages.

Announcement-only mailboxes enable you to:

• Perform any operations that can be performed on a greeting in personal mailboxes, such as recording or deleting.
• Use all the new greeting types introduced by the multiple greeting feature. For more information, see the Configuring Multiple Greetings.
• Configure a General Delivery Mailbox as an announcement-only mailbox.

Also, announcement-only mailboxes:

• Cannot be part of everyone’s list (9999)
• Are counted against the mailbox license
• Have a default size of 5 minutes when they are created, but the default size can be modified later

Because announcement-only mailboxes cannot send or receive messages, you cannot:

• Create distribution lists for them
• Configure notification devices for them

Therefore announcement-only mailboxes cannot:

• Have messages addressed to them
• Have notifications cascaded to them
• Receive broadcast messages

Subscribers can log in to announcement-only mailboxes using either the TUI, VVE, or IMAP. However, there is no reason to use IMAP to log into announcement-only mailboxes because they do not contain messages.

The following features are available only for personal mailboxes and cannot be used with announcement-only mailboxes:

• Message expiration time
• Message size
• Fax configuration

The following operations are available only for personal mailboxes in the TUI and VVE and cannot be used with announcement-only mailboxes:

• Playing new, saved, or deleted messages
• Sending messages
• Setting message parameters, such as configuration lists or notification devices

SUMMARY STEPS

1. configure terminal

2. voice mailbox owner name type announcement-only [ size seconds ]

3. end

4. show voicemail detail mailbox name

DETAILED STEPS

Examples

The following is sample output from the show voicemail detail mailbox command:

Configuring Call Flow Customization

Beginning in version 7.1, you can customize how the call flow proceeds in response to keys pressed by the caller during a call. For each mailbox, the mailbox owner or system administrator can assign one of the following actions to the keys input by the caller:

• Transfer the call to another number
• Connect to the operator
• Ignore the input
• Repeat the greeting
• Say good bye
• Skip the greeting
• Proceed with subscriber sign-in

These actions can be assigned only to single digit input by the user, such as the numbers zero through nine (0 - 9), the asterisk (*), or the pound sign (#).

You can also optionally restrict the use of the caller input feature by configuring a caller call-flow restriction table.

SUMMARY STEPS

1. configure terminal

2. voice mailbox owner name

3. caller-flow caller-input input { ignore | repeat-greeting | say-goodbye | skip-greeting |subscriber-signin | transfer-to E164Phone | transfer-operator }

4. exit

5. voicemail conversation caller caller-flow restriction-table restriction-tablename

6. end

7. show voicemail detail mailbox name

8. show voicemail conversation caller caller-flow restriction-table

9. show running-config

DETAILED STEPS

Examples

For examples of the output from the following commands, see the “Examples” section.

• show voicemail detail mailbox
• show voicemail conversation caller caller-flow restriction table
• show running-config

Configuring System-Wide Voice-Mail Parameters for All Voice Mailboxes

SUMMARY STEPS

1. config t

2. voicemail capacity time minutes

3. voicemail message mandatory-expiry

4. system language preferred xx_YY

5. voicemail default { broadcast expiration time days | expiration time days | language xx_YY | mailboxsize mailboxsize-seconds |
messagesize messagesize-seconds }

6. voicemail operator telephone tel-number

7. voicemail recording time seconds

8. voicemail callerid

9. voicemail conversation caller recording-prompt

10. voicemail mailbox-selection { last-redirect | original-called }

11. exit

12. copy running-config startup-config

13. show voicemail limits

14. show system language

DETAILED STEPS

Example

The following example sets voicemail parameters.

The following example displays the output from the show voicemail limits command:

To display the status of the caller recording-prompt, use the show running-config command. If the prompt has been disabled, the following line appears in the output:

The show running-config output will not display any status of the prompt if the prompt is enabled.

The following example displays the output from the show system language preferred command:

The following example displays the output from the show system language installed command:

Configuring the Ability to Leave Multiple Voice Messages in the Same Session

Starting in release 3.0, callers can leave multiple voice message for the same or different subscriber without having to be first transferred to the operator.

You can configure these options by either:

• Using two commands available in 3.1 and later versions:

– voicemail conversation caller multi-msgs-same-mbx

– voicemail conversation caller multi-msgs-any-mbx

• Adding the options as parameters in the calling script.

The voicebrowser.aef script is called when a call lands on voice mail pilot number. This script calls the login.vxml script internally. To pass the options to leave multiple messages as parameters of the calling script, customers can write a new.aef script to use instead of voicebrowser.aef. It is identical to the existing script, except that it will call login.jsp instead of login.vxml. It will pass the two parameters: multMsgsSameMbx and multMsgsDiffMbx. A value of 0 for these parameters means that the option is disabled, a value of 1 means that the option is enabled.

If both the above mentioned methods are used, the values passed in as the script parameters take precedence.

When callers are done leaving their message, they can use this feature by selecting from the following options:

• If the option to leave another message for the same mailbox is enabled, callers hear the prompt:

“To leave another message for this mailbox, press 1”

When callers press 1, they are prompted to record their message.

• If the option to leave a message for different mailbox is enabled, callers hear the prompt:

“To leave a message for another mailbox on this system, press 2”

“When callers press 2, they are prompted to:

– Select a user or GDM on the system

– Record the message

• If both options are enabled, callers hear both prompts described above and are then prompted with the corresponding options.

If both options are disabled or the timeout is exceeded, the call is not prompted for any input and is then either:

• Transferred to the operator, if the operator number is configured
• Disconnected

Prerequisites

Cisco Unity Express 3.0 or a later version

SUMMARY STEPS

1. config t

2. voicemail conversation caller multi-msgs-same-mbx

3. voicemail conversation caller multi-msgs-any-mbx

4. end

5. show voicemail conversation {caller | subscriber}

DETAILED STEPS

Configuring the Use of a Voice Mail Summary Prompt during Subscriber Login

Starting in release 3.0, a system-wide configuration option enables subscribers to play a summary of the new messages in the corresponding General Delivery Mailboxes (GDMs) during login. This option is applicable only to users, not to GDMs. You can configure this option using either the CLI or the GUI.

This option is disabled by default. When the option is disabled, the behavior is the same as in previous versions. Before 3.0, for a subscriber to see if there were any new messages in their associated GDMs, they would have to access an individual GDM by pressing 9 when they logged into their mailbox.

When this option is enabled, users hear a prompt that explains how many messages they have and how many of those messages are urgent. If a GDM has a spoken name, it is included in the message. Otherwise, the mailbox extension is included in the message. After this point, the functionality is the same as in previous versions.

Prerequisites

Cisco Unity Express 3.0 or a later version

SUMMARY STEPS

1. config t

2. voicemail conversation subscriber play-gdm-summary

3. end

DETAILED STEPS

Configuring Message Properties (Envelope) Customization

Starting in release 3.0, you can customize voice mail message playback preferences, such as which message properties subscribers hear when they retrieve a message using the TUI. These message properties are also commonly known as the message envelope.

By default, Cisco Unity Express plays all message properties. The message properties consist of the sender information, date and time of when the message was sent, reception date and time (if the message was received later than 30 minutes after it was sent), and other details such as the message number, type, priority. With this feature, you can customize the message playback to exclude information on the sender, date and time, and the day of week that the message was sent.

You can only customize the message properties of regular (new/saved/deleted) messages. You cannot customize Non-Delivery Receipts (NDR), Delayed Delivery Receipts (DDR), and broadcast messages because all available envelope information is essential in understanding those messages.

The following sections describe how to configure the following two options for configuring message properties:

• Specify that only some of the system-wide message properties (envelope) are played for regular voice mail messages.
• Include the playing of the day-of-week information in the message properties (envelope) of voice mail for regular messages.

Configuring Whether to Include Only Brief Message Properties

Prerequisites

Cisco Unity Express 3.0 or a later version

SUMMARY STEPS

1. config t

2. voicemail conversation subscriber msg-properties brief

3. end

4. show voicemail conversation subscriber

DETAILED STEPS

Configuring Whether to Include Day-of-Week Message Properties

SUMMARY STEPS

1. config t

2. voicemail conversation subscriber msg-properties day-of-week

3. end

4. show voicemail conversation subscriber

DETAILED STEPS

Configuring Default Addressing for Sending a Voice Message

Prior to release 3.0, you could not specify whether voice messages were addressed by name or extension at the system level for all the features. Starting with release 3.0, the default setting is the same as in previous versions, which is to address the message by name.

Prerequisites

Cisco Unity Express 3.0 or a later version

SUMMARY STEPS

1. config t

2. voicemail conversation address-by {extension | name}

3. end

4. show voicemail conversation {caller | subscriber}

DETAILED STEPS

Configuring 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 Unified Communications Manager Express or Cisco Unified Communications Manager 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 An external call is any telephone number that is not listed in the Cisco Unity Express subscriber directory. Possible sources of external calls are the local telephone company, an IP telephone, or an H.323 gateway. These sources must be configured to present caller ID information to the Cisco Unity Express system.

The following sections describe this feature:

• Enabling Caller ID on the Local System
• Disabling Caller ID on the Local System

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:

Disabling 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:

Configuring Secure Messaging

Secure messaging allows individual mailbox subscribers to mark messages as secure. Messages marked secure have greater restrictions for sending, accessing and forwarding. See the following sections:

• Overview
• Configuring Global Secure Messaging Support
• Configuring Secure Messaging Support for Individual Mailboxes
• Enabling Secure Messaging Support for a Remote Network Location

Prerequisites

Cisco Unity Express 8.6 or a later version

Overview

Messages can be marked secure to restrict access in certain cases. Messages can be marked secure by individual subscribers, or you can configure Cisco Unity Express so that all outgoing messages are automatically marked secure.

You can configure the secure messaging to one of four settings:

• Ask—Subscribers have the option of marking any outgoing messages as secure.
• Always—All outgoing messages are automatically marked secure by the system.
• Never—No outgoing messages may be marked as secure. Subscribers do not have the option of marking messages secure.
• Private—All outgoing messages marked private are automatically marked secure by the system. Subscribers do not have the option of marking messages secure. This is the default setting.

These settings can be applied globally or to an individual mailbox.

Messages marked secure can be accessed using the Telephony User Interface and VoiceView Express without restrictions. Messages marked secure can only be accessed on the Web Voicemail interface if the subscriber accesses Cisco Unity Express using a secure HTTPS session.

Table 7-1 shows how subscribers can manage secure messages depending on how they access Cisco Unity Express.

Note To receive secure messages from IMAP clients, the IMAP session security command must be set to “mixed” or “ssl”. For more information, see the “Configuring IMAP” section.

If a subscriber selects a secure message while accessing the Cisco Unity Express Web Voicemail interface through a non-secure HTTP session, the following message is displayed:

“This message is marked as secure and cannot be accessed in this session. Please re-login with https://<hostname>user.”

Messages marked secure cannot be saved past the expiration date as configured using the voicemail default expiration time command. Subscribers are prompted to delete any expired messages that are marked secure.

Configuring Global Secure Messaging Support

This procedure configures the global Cisco Unity Express secure messaging support for all outgoing messages.

SUMMARY STEPS

1. config t

2. voicemail secure-messaging outgoing { always | ask | never | private }

DETAILED STEPS

Configuring Secure Messaging Support for Individual Mailboxes

This procedure configures secure messaging support for individual mailboxes. The settings for the individual mailbox override the global secure messaging setting.

SUMMARY STEPS

1. config t

2. voice mailbox owner name [type announcement-only] [siz e seconds ]

3. secure-messaging incoming

4. secure-message outgoing { always | ask | never | private }

DETAILED STEPS

Enabling Secure Messaging Support for a Remote Network Location

This procedure enables secure messaging for all incoming messages to a remote network location. If this setting is not enabled, then an NDR message will be generated for any messages marked secure sent to the remote location.

Prerequisite

The remote network location must be configured. See the “Configuring Network Locations” section.

SUMMARY STEPS

1. config t

2. network location id number

3. voicemail secure-messaging

DETAILED STEPS