[Index]

Model: device/cuc/AlternateExtension

Voicemail

Full HTML Help

Overview

VOSS Automate allows admin users to add, update, or delete Cisco Unity Connection (CUC) voicemail accounts (voicemail users), and their associated voicemail services, via (default menus) Subscriber Management > Voicemail.

Note

Optionally (depending on your deployment), VOSS Automate supports a Unity SIP integration feature that can be used in place of your existing voicemail service. See Introduction to Unity SIP Integration

Important

Users and associated services added through VOSS Automate are also added to Cisco Unity Connection (CUC) voicemail system.

If a user identifier is updated on the CUC integrated LDAP server, the alias update on the CUC server is deferred to the next LDAP-CUC sync. The alias change is then synced in to VOSS Automate in the VOSS Automate-CUC sync that follows the LDAP-CUC sync. The updated alias displays in the CUC Account settings, in the Voicemail Account Name field.

Related Topics

Call Handler (Auto Attendant) in the Core Feature Guide

Unified Messaging Account

Unified Messaging (Single Inbox) is a Cisco Unity Connection (CUC) service that enables users to have a single inbox in their e-mail client that is used for their e-mail as well as their Voicemail.

Note

The following CUC settings, set to 'True' (On), are included in Unified Messaging:

The following two models were added to the Model Type List CUCXN Overbuild Resources for Unified Messaging:

VOSS Automate also added a new Model Type list CUCXN Unified Messaging Services, and added the same two Models: device/cuc/ExternalService and device/cuc/ExternalServiceAccount

Add, Edit, or Delete a Voicemail Account

Prerequisites:

Perform these steps:

  1. In the VOSS Admin Portal, go to (default menus) Subscriber Management > Voicemail.

  2. From the summary list view, choose an option:

  3. At CUC Account, configure CUC account details, such as voicemail account name (the subscriber), voicemail number, and the language the caller hears. For details, see Unified Messaging Account

    Note

    • If a user identifier is updated on the CUC integrated LDAP server, the alias update on the CUC server is deferred to the next LDAP-CUC sync. The alias change is then synced in to VOSS Automate in the VOSS Automate-CUC sync that follows the LDAP-CUC sync. The updated alias displays in the CUC Account settings, in the Voicemail Account Name field.

    • The Voicemail Number drop-down only shows numbers associated to the selected subscriber (chosen for voicemail account name).

    • Email address is auto-populated when selecting an existing subscriber.

    • Click the Plus icon (+) at Unified Messaging Account to add a unified messaging service. See Unified Messaging Account. Once saved, the summary header is the user's email address. It is only possible to add one CUC messaging account per subscriber in VOSS Automate.

      To change from one Unified Messaging Account type to another, delete the existing entry and click Save. Then add the new Unified Messaging Account type in the Unified Messaging Service field.

  4. At Alternate Extensions, add alternate extensions available to the CUC voicemail user, if applicable.

    Note

    Once you've saved these changes you can log in to Cisco Unity Connection, choose the user you updated, and go to Edit > Alternate Extensions to view the alternate extension configured in VOSS Automate.

  5. From Alternate Extension choose the Partition from the drop-down and click Save.

  6. At Message Actions, define how incoming voicemail, email, fax, and receipt messages are handled. If the selected message action involves relaying the message, enter a valid email address in the Relay Address field.

    Note

    You can accept the default message actions and update them later.

  7. At Credentials, configure a password and PIN.

    Note

    The admin user configuring the account can lock these credentials or require the user to change the credentials on first login. The CUC user password template and CUC user PIN template in the user's Quick Add Group (QAG) are applied. See Quick Add Subscriber Group Default Model.

  8. At Notification Devices tab, add devices used to notify this CUC user of voicemails sent to them.

    Note

    • While the system automatically provisions default notification devices, you can add additional devices when adding a voicemail account.
    • SMS notification is only available if an SMPP Provider has been added on the relevant Voicemail server.
  9. At Caller Input, click on the required key (*, #, or 0 to 9), then select an action from the drop-down to associate caller input keys to specific actions (to configure default caller input keys). See Caller Input.

    Note

    • The Caller Input settings display only once the CUC account (including voicemail account name) has been created and saved.
    • Additional fields are exposed when choosing certain options. For example, when you choose the User with Mailbox call action, the User with Mailbox and Transfer / Greeting fields are exposed.
  10. Save your changes to add or update this voicemail account.

    Note

    Once you've added a voicemail service to a subscriber, the lines lines used by any devices associated with the subscriber are updated to reflect the proper call forward and voicemail profile settings to enable the following buttons: Call Forwarding to Voicemail and Voicemail.

Voicemail

A Voicemail account can only be added if:

When adding a new Voicemail account, the following workflow is executed:

  1. A CUC account is added with the details input by the user.
  2. Alternate extensions are added with the details input by the user (if applicable).
  3. Message actions are initially added with defaults, but can be updated with details input by the user if the Subscriber has been added, or upon modification.
  4. Credentials (password and PIN) are added with the details input by the user. The password and PIN can either be locked by the administrator, or the user can be prompted to change the credentials upon first login.
  5. Notification Devices are added. The system automatically provisions default notification devices, however additional notification devices can also be added when adding a Voicemail account.
  6. Caller Input keys are updated or added as configured by the user.

You can modify either an existing Voicemail account service information (details that were added to a Voicemail account during the Add Voicemail process), or you can modify a Voicemail account by adding new Voicemail services (those that were not added to the Voicemail account during the initial Add Voicemail process). For example, you can add additional alternate extensions and/or notification devices. After adding a Voicemail service to a subscriber, any lines that are used by any of the devices associated to the subscriber must be updated to reflect the proper call forward and Voicemail profile settings to enable the Call Forwarding to Voicemail and Voicemail buttons.

When modifying a Voicemail account, the workflow and processes are executed as with the Add workflow.

When deleting a Voicemail account, the following should be noted about the workflow:

  1. All elements associated with the Voicemail account are deleted.
  2. Modular Delete workflows can be carried out as a part of a Modify workflow.

Note

Model Details: device/cuc/AlternateExtension

Title Description Details
Alternate Extension Group Assigned by FDP
  • Field Name: Alternate Extension
  • Type: Object
Number * The dialable number.
  • Field Name: Alternate Extension.DtmfAccessId
  • Type: String
Phone Type * An index into the alternate extensions for a subscriber.
  • Field Name: Alternate Extension.IdIndex
  • Type: Integer
  • Choices: ["Work Phone", "Work Phone 2", "Home Phone", "Home Phone 2", "Mobile Phone", "Mobile Phone 2", "Work Fax", "Work Fax 2", "Home Fax", "Directory URI"]
Name The text name of this DtmfAccessId to be used when displaying entries in the administrative console, e.g. Cisco Unity Connection Administration.
  • Field Name: Alternate Extension.DisplayName
  • Type: String
Partition Name The name of the associated partition
  • Field Name: Alternate Extension.PartitionObjectId
  • Type: String
  • Target: device/cuc/Partition
  • Target attr: ObjectId
  • Format: uri
Assigned User * template parameter [1]
  • Field Name: Alternate Extension.UserObjectId
  • Type: ["String"]
  • Target: device/cuc/User
  • Target attr: ObjectId
  • Format: uri