You can specify different settings, such as password and transfer rules associated with a user template or a particular user account through Cisco Unity Connection Administration interface. For information on user accounts, see the Users chapter and for information on user templates, see the User Templates section.

The Edit User Template Basics page allows you to specify the settings, such as alias and first name associated with a particular user template.

The Edit User Basics page allows you specify the settings, such as alias and first name associated with a particular user account.

Consider the following points while changing the alias of a user:

• If you change the alias for a user, Unity Connection automatically creates an SMTP proxy address for the previous alias. This allows the other Unity Connection users to reply to the messages that were sent from the previous alias but the replies automatically reach to the new alias of the user.
• When Unity Connection is integrated with an LDAP directory, the Alias field cannot be changed for any user who is integrated with an LDAP user. However, if you are using Active Directory as the LDAP directory, you can change the value of the LDAP field that is mapped to the Alias field. The alias change is replicated to Unity Connection when the Unity Connection database is synchronized with the LDAP directory. This also causes Unity Connection to automatically create an SMTP proxy address for the previous alias.

Caution

If you are using an LDAP directory other than Active Directory and you change the value of the LDAP field that is mapped to the Alias field, the user is converted to a non-LDAP-integrated user.

In the following configurations, you cannot edit fields, such as Alias (User ID in Cisco Unified Communications Manager Administration), and First Name:

• In Cisco Business Edition, when the Unity Connection user is integrated with the Cisco Unified CM Application User. You can only edit these fields in Cisco Unified CM Administration.
• In Unity Connection or in Cisco Business Edition, when Unity Connection user data is synchronized with data in an LDAP directory. You can only edit these fields in the LDAP directory.

  Note	If Unity Connection is configured to authenticate Unity Connection web application user names and passwords against the LDAP directory, you cannot change the Unity Connection web application password.

• In Unity Connection, if digital networking is configured, you cannot edit any fields for a user on servers other than the home server of the user. You must edit user settings on the server on which the user account was created.

  For information on moving mailboxes from one mailbox store to another, see the LDAP chapter.

Default phone PINs and web application passwords are applied to each user account that you create. The web application password and voicemail PIN settings for individual users determine:

• The authentication rule that governs the user account.
• The time of password or PIN lockout if the user password or PIN is locked by an administrator.
• The password changing settings of a user, whether user is allowed to change the password or the password must be changed during next sign in.
• The expiry of a password or PIN.
• The last time a password or PIN was changed.
• The number of failed sign-in attempts, the time of the last failed sign-in attempt, and the time period that the lockout is enforced.

You can change the web application password and voicemail PIN settings for a user on the Edit > Password Settings page for the user or associated user template.

Note	In Cisco Business Edition, you can change user voice mail PINs and web application passwords either from the User Management pages in Cisco Unified CM Administration.

Note	If Unity Connection is integrated with an LDAP directory, the web application password and password settings (for example, password-complexity settings and whether the password expires) are controlled by the LDAP server.

Users can also use the Messaging Assistant to change the passwords and PINs.

You can assign different roles (System Roles and Custom Roles) to a user from the Edit Roles page of a user or the associated user template. System Roles are the predefined roles provided by Unity Connection whereas Custom Roles are the roles that the administrator creates based on the requirements. For more information on different roles and privileges, see the Roles section of the "User Attributes" chapter..

Note	While specifying the user account settings, you can assign multiple roles to a particular user through Edit Roles page. The role you assign to the user account defines the privileges and tasks that an administrator can perform.

Unity Connection can set message waiting indicators (MWIs) at up to 10 extensions for a user when new voice messages arrive. When a user account is added, Unity Connection automatically enables the MWI at the primary extension for the user.

You can change MWI settings, add or delete MWI extensions in Cisco Unity Connection Administration on the Message Waiting Indicators page for a user.

In a SCCP integration with Cisco Unified CM or in a SIP trunk integration with Cisco Unified CM 7.1 and later, Unity Connection can also send message counts to supported Cisco IP phones.

Note	You cannot specify MWI settings for user templates.

The transfer rules specify how Unity Connection handles calls transferred from an automated attendant to user phones. As per the call transfer settings, Unity Connection can either release the call to the phone system, or it can supervise the transfer.

When Unity Connection is set to supervise transfers, it can provide additional call control with call holding and call screening for indirect calls:

• With call holding, when the phone is busy, Unity Connection can ask callers to hold. Unity Connection manages each caller in the queue according to the settings that you configure.

  The wait time in the call holding queue for the first caller in the queue defaults to 25 seconds. If the caller is still on hold after this amount of time, Unity Connection asks if the caller wants to continue holding, leave a message, or try another extension. If the caller does not press 1 to continue holding, or press 2 to leave a message, the caller is transferred back to the Opening Greeting. If call holding is not selected, callers are sent to whichever user greeting is enabled.

• With call screening, Unity Connection can ask for the name of the caller before connecting to a user. The user can then hear who is calling and, when a phone is shared by more than one user, who the call is for. The user can then accept or refuse the call.

  If the call is accepted, it is transferred to the user phone. If the call is refused, Unity Connection plays the applicable user greeting.

Note	Transfer, screening, and holding settings do not apply when an outside caller or another user dials a user extension directly.

To control how Unity Connection handles indirect calls at different times of the day or for specified period of time, you can define Standard, Closed, and Alternate transfer rules. The Standard transfer rule is always enabled and cannot be turned off. You can determine whether to enable Closed and Alternate transfer rules or customize the time for which the transfer rules should be enabled.

You can specify message settings for a specific user on the Edit Message Settings page for the user or user template that you use to create users. The message settings determine the message recording length, secure access, and message action of the outside (unidentified) callers when leaving messages for a user. You can specify the following settings:

• The maximum recording length for messages left for a user by outside callers.
• The action of outside callers when leaving messages for a user. For example, mark messages urgent or private, or re-record the messages.
• The secure access for the messages left by outside callers are secure. For more information, see the "Securing User Messages in Cisco Unity Connection" chapter of the Security Guide for Cisco Unity Connection Release 12.x to learn how Unity Connection handles secure messages. The guide is available at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/security/b_12xcucsecx.html.

The language of the Unity Connection prompts that callers hear when leaving messages for a user.

Message actions determine how Unity Connection handles different types of messages that it receives for a user. Unity Connection applies the configured action for all messages of a given type that are addressed to the user. For example, if the message action for voice messages is set to relay messages of this type to a user at an alternate SMTP address, Unity Connection relays all voice messages including VPIM messages, messages that are sent from an IMAP client, and messages that are recorded and sent by phone. By default, Unity Connection is configured to accept each type of message, meaning that it delivers the message to the user mailbox.

If you choose to relay voice messages to another address, you should consider the following:

• When messages are set to be relayed, users are no longer able to access relayed messages from the Unity Connection phone interface, Web Inbox, Messaging Inbox, or other clients, such as Phone View or Cisco Unified Personal Communicator. You can use the Accept and Relay the Message action to instruct Unity Connection to save a copy of the message in the local user mailbox (where it is accessible by user interfaces) and also relay a copy to another address.
• Unity Connection relays dispatch messages as regular messages.
• Unity Connection does not relay broadcast messages.
• You can configure whether Unity Connection relays private messages and secure messages on the System Settings > Advanced > Messaging page. Private messages are relayed as regular messages with the private flag and secure messages are relayed as regular messages.
• If user accounts are configured to relay voice messages to an alternate SMTP address, the voice messages cannot be transcribed. If users want transcriptions along with the relay feature, you can configure user accounts to Accept and Relay voice messages. This allows the copy of the message that is stored on the Unity Connection server to be transcribed.
• When you configure SMTP notification devices for users, transcription is sent to the user SMTP address. This means that users receive two emails at the SMTP addresses. The first one is the relayed copy of the message WAV file. The second is the notification that includes the transcription. If the users need to access the original recording, users can call in Unity Connection or use an IMAP client to access the user account.

Note	SMTP Relay functionality has been primarily designed to configure corporate email address only. In order to avoid any loop in relaying the message, Primary SMTP address of Unity Connection should not be configured as Relay address.

Note	Unity Connection supports the relay function in message action only when you have configured an SMTP smart host on the System Settings > SMTP Configuration > Smart Host page.

The caller input settings define actions that Unity Connection takes in response to phone keypad keys pressed by callers during a user greeting. For each greeting that allows caller input, you can specify whether callers can skip the greeting, record a message, exit the greeting, transfer to numbers that are not associated with users or call handlers, or transfer to an alternate contact number, call handler, directory handler, or interview handler of your choice. You also use caller input settings to specify which keys users can press to interrupt a user greeting so that they can sign in to Unity Connection.

The caller input settings can be changed only by an administrator user. By default, for each user greeting, Unity Connection acts on certain keys and ignores others.

Table A-1 lists the default actions assigned to phone keypad keys.

Note	Verify that the phone keypad key you select to lock is not the first digit of any of the extensions in your system. If it is, locking the key prevents callers from dialing an extension.

Unity Connection allows you to specify the maximum size, or quota, for every user mailbox. You can configure mailbox quotas that permits Unity Connection to:

• Issue a warning when a mailbox reaches a specified size.
• Prevent a user from sending messages when the mailbox reaches a larger size.
• Prevent a user from sending or receiving messages when the mailbox reaches the largest size that you want to allow.

To handle the varying needs of users in your organization, you can override the systemwide quotas for individual mailboxes and for user templates. For example, you may want to allow employees in the sales department to have larger mailboxes than other employees. If you create user accounts for all sales employees using the same template, you can either specify higher quotas for the user template or higher quotas for individual user accounts.

Caution

Quotas are not enforced for messages left by outside callers if the Full Mailbox Check for Outside Caller Messages check box is not checked. This check box appears on the System Settings > Advanced > Conversations page. For more information, see the Help for that page.

Unity Connection offers several versions of the phone conversation that users hear and use. The version you select determines whether Unity Connection responds only to phone keypad input or also uses voice recognition to interpret spoken commands:

• Touchtone Conversation- Users press keys to tell Unity Connection what they want to do. There are several touchtone conversations to choose from. Each one offers a unique keypad mapping for the message retrieval menus. For some, the keys assigned to options in the Main menu are also unique.
• Voice-Recognition Conversation- Users say voice commands to interact with Unity Connection. Even when assigned to the voice-recognition conversation, users can also press keys on the phone to tell Unity Connection what they want to do; in this case, the touchtone conversation setting is used to determine which keys are mapped to which options. This allows the touchtone conversation setting to serve as a backup if the voice-recognition services are unavailable, and also when users simply choose to use the keypad instead of voice commands to interact with Unity Connection.The user account or template must be assigned to a class of service that enables a license and the voice-recognition feature.

In case of a video call, Unity Connection plays the touchtone conversation only, even if the user is enabled for voice-recognition conversation (Use Voice Recognition Input Style). The user selects the applicable key to switch to voice-recognition conversation (Switch Between Using the Phone Keypad and Using Voice Commands) using custom keypad mapping.

All of the settings on the Playback Message Settings page, with the exception of the For Draft Messages, Play field, are applicable both to Unity Connection messages and to messages stored externally, depending on whether users are enabled to access email in third party message stores, and are enabled to use the single inbox feature.

System broadcast messages are recorded announcements that are sent to everyone in an organization. Users can either send system broadcast messages to all users or update the system broadcast messages stored in user mailboxes.

Note	By default, Unity Connection users are not enabled to send or update broadcast messages.

To send or update system broadcast messages, users log on to Broadcast Message Administrator which is a special conversation that permits the users to send or update broadcast messages. For more information, see the Messaging chapter.

Users can enable or record up to seven greetings using Messaging Assistant or phone. The greeting settings in Cisco Unity Connection Administration for a user template or user account allow you to specify which greetings are enabled, how long they are enabled, the greeting source, and the actions that Unity Connection takes during and after each greeting.

When a greeting is enabled, Unity Connection plays the greeting in the applicable situation until the specified date and time arrives, and then the greeting is automatically disabled. A greeting can also be enabled to play indefinitely, which is useful for busy or closed greetings, or when an alternate greeting is enabled by a user during a leave of absence.

Following are the types of greetings that a user can record:

• Audio Greeting: Allows you to record an audio message that must be played when a particular greeting is enabled. For example, you can record an audio message for the Busy greeting, which the callers hear when the call is busy.
• Video Greeting: Allows you to record a video message that must be displayed when a particular greeting is enabled. For example, you can record a video message for the Holiday greeting, which the callers hear when the recipient is on holiday. For more information on Video greetings, see Video chapter.

Post greeting recordings are the recorded messages that are played after greetings but before callers are allowed to leave a message for a user. For example, you may want to enable a post greeting recording for a particular group of users to convey a confidentiality policy or to let callers know when they can expect a response to the message. You can also use the feature to remind callers to include contact information, invoice or policy numbers, and other such information when they leave messages.

For each post-greeting recording, you use the Media Player on the Edit Post Greeting Recording page of a user template or user to record what you want callers to hear. Post greeting recordings are configured on the Call Management > Custom Recordings page in Cisco Unity Connection Administration. For information on custom recordings, see the Custom Recordings section.

Users can be configured to call a phone or a pager or send text, or SMS messages to notify users of new messages and calendar events. You can configure the parameters for the call or notification message, the events that trigger the notification, and the schedule on which the notification occurs by setting up notification devices.

You can setup the notification devices for users using the Edit Notification Devices page of a user or user template. For more information, see the Notifications chapter.

Note	With Unity Connection 10.5 and later, you can also enter the URI number for the work, mobile, and home notification devices.

When configuring the single inbox for Unity Connection, check the Generate SMTP Proxy Address From Corporate Email Address check box. When you check this check box, Unity Connection automatically creates a new SMTP proxy address for the value in the Corporate Email Address field. An SMTP proxy address allows Unity Connection to map the sender to a user and to map the message recipients to users by comparing the SMTP addresses in the message header to its list of SMTP proxy addresses. Applicable SMTP proxy addresses are necessary when using Cisco ViewMail for Microsoft Outlook with the single inbox feature to send messages.

When integrated with Exchange, Unity Connection allows touchtone and voice-recognition conversation users to hear the emails read to them when they sign in to Unity Connection using phone. The Text-to- Speech (TTS) playback is available provided that the text portion of the message does not exceed 1 MB in size and the text format of the message is supported by Unity Connection. Supported formats include plain text, quoted-printable text, HTML, and XML.

To enable users to access email in Exchange, configure unified messaging and select the options applicable to text to speech. For more information, see Unified Messaging Guide for Cisco Unity Connection for Release 12.x at, https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/unified_messaging/b_12xcucumgx.html .

Unity Connection allows the users to record and play video greetings using a video endpoint. Unity Connection facilitates you to record and play all types of following greetings as video:

• Alternate
• Busy
• Internal
• Closed
• Standard
• Holiday

Note	Error greetings are played only as audio greetings.

In addition to the primary extension for each user, you can set up alternate extensions. Alternate extensions can be used for various reasons, such as handling multiple line appearances on user phones. Alternate extensions can also make calling Unity Connection from an alternate device, such as a mobile phone or a phone at another work site more convenient.

When you specify the phone number or URI for an alternative extension, Unity Connection handles all calls from that number in the same way that it handles calls from a primary extension (assuming that ANI or caller ID is passed along to Unity Connection from the phone system). This means that Unity Connection associates the alternate phone number with the user account and when a call comes from that number, Unity Connection prompts the user to enter a PIN and sign in.

If users set an alternate device to forward to Unity Connection, callers can hear the user greeting and leave messages for the user, just as they would when dialing the primary extension of the user. (Callers can also be transferred to the alternate extension for a user from the automated attendant.) Users need to set forwarding from the device itself, not in Unity Connection. Note that the phone number must be passed to Unity Connection for the system to recognize the device.

Users can also address messages to an alternate extension that is associated with another user.

Alternate extensions are grouped into two categories:

• Administrator-defined alternate extensions-Administrators can add up to 9 alternate extensions. Administrators can view and edit both administrator-defined and user-defined alternate extensions.
• User-defined alternate extensions-Users can add up to 10 alternate extensions if they belong to a class of service that allows them to manage user-defined alternate extensions. Users can view administrator-defined alternate extensions if they belong to a class of service that allows them to do so.

Class of service settings allow you to determine whether users can view or manage alternate extensions and whether they can use the Unity Connection Messaging Assistant to manage a set of own alternate extensions.

Users who belong to a class of service with the Allow Users to Manage Their User-Defined Alternate Extensions option enabled can automatically add alternate extensions.To learn more about this feature, see the System Settings chapter.

Using the Custom Keypad Mapping tool in Cisco Unity Connection Administration, you can provide users with the option to edit the alternate extensions from the Preferences menu in the phone interface. When a user selects the option to edit the alternate devices, Unity Connection allows you to list or delete the existing alternate extensions. If the user signs in from a phone number that is not the primary extension or an existing alternate extension or in the Excluded Extensions for Automatically Added Alternate Extensions restriction table, when they select the option to edit the alternate devices, Unity Connection offers to add the phone number as a new alternate extension. For more information on custom keypad mapping, see the Using the Custom Keypad Mapping Tool section.

Alternate names are different versions of a name than what is listed in the corporate directory. Cisco Unity Connection considers these names when a caller uses voice recognition to place a call. For example, if a caller asks Unity Connection to dial "Mary Jameson," which was the maiden name of Mary Brown, Unity Connection can reference this information and connect the caller to the correct user.

In addition to recognizing alternate names when users and outside callers use voice recognition to place a call, Unity Connection recognizes alternate names when callers and users use voice recognition to address voice messages. Alternate names can be created for users, VPIM contacts, administrator-defined contacts, system distribution lists, private lists, and user-defined contacts.

While Unity Connection already recognizes hundreds of common shortened names (Bill in place of William, for example), you might want to add another version of an uncommon name, unusual nicknames, or maiden names. You could also use alternate names to add phonetic spellings of hard-to-pronounce names. For example, you could add "Goolay" as an alternate name for the last name "Goulet."

From the Cisco PCA, users can edit or change the alternate names and can also create alternate names for customers, suppliers, family members, and friends who are not included in the Unity Connection directory, or for private lists. This helps in making it easier for the users or outside callers to dial the contacts or address to the lists when using voice commands.

Note	You cannot add or edit alternate names on a user template, nor can you use the Bulk Edit utility to add or edit alternate names for multiple user accounts.

Users can use the private distribution lists that are associated with the accounts to send voice messages to more than one user at a time. The users can set up and manage the private lists using the Messaging Assistant or the phone. For more information on private distribution list, see the " Managing your Private List " chapter of the User Guide for the Cisco Unity Connection Messaging Assistant Web Tool (Release 12.x) at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/user/guide/assistant/b_12xcucugasst.html.

Note	You cannot specify private lists on a user template or for multiple user accounts at once.

Unity Connection uses SMTP proxy addresses to map the recipients of an incoming SMTP message sent from an IMAP client to the appropriate Unity Connection user or VPIM contact. If users use IMAP clients to send, reply to, or forward messages to VPIM contacts you should configure each VPIM contact with an SMTP address.

Note	Unity Connection handles SMTP messages sent to the contacts that are not associated with a VPIM location according to the option selected for the System Settings > General Configuration > When a Recipient Cannot Be Found setting.

For example, when Robin Smith, whose email client is configured to access Unity Connection with the email address robin.smith@example.com, records a voice message in ViewMail for Outlook and sends it to chris.jones@example.com, Unity Connection searches the list of SMTP proxy addresses for robin.smith@example.com and chris.jones@example.com. If these addresses are defined as SMTP proxy addresses for the Unity Connection users Robin Smith and Chris Jones respectively, Unity Connection delivers the message as a voice message from Robin Smith to Chris Jones.

Note	For more information on configuring Unity Connection so that users can use IMAP clients to send, forward, or reply to messages through the Unity Connection server, see the Integrated Messaging