[Index]

Model: device/cuc/AlternateExtension

Voicemail

To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com

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

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

Related Topics

Add, Update, or Delete a 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. On the CUC Account tab, 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

    • 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.
  4. On the Alternate Extensions tab, 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. On the Message Actions tab, 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. On the Credentials tab, 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. On the 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. On the Caller Input tab, 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 tab displays 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.

Model Details: device/cuc/AlternateExtension

Title Description Details
Partition Name The name of the associated partition
  • Field Name: PartitionObjectId
  • Type: String
  • Target: device/cuc/Partition
  • Target attr: ObjectId
  • Format: uri
Partition URI
  • Field Name: PartitionURI
  • Type: String
  • Format: uri
Phone Type * An index into the alternate extensions for a subscriber.
  • Field Name: 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"]
Object Id The primary key for this table. A globally unique, system-generated identifier for a DtmfAccessId object. - template parameter [2]
  • Field Name: ObjectId
  • Type: String
URI
  • Field Name: URI
  • Type: String
  • Format: uri
Alternate Extension Advanced URI The URI to get the advanced setting of the alternate extension.
  • Field Name: AlternateExtensionAdvancedURI
  • Type: String
Dtmf Access Id * The dialable number.
  • Field Name: DtmfAccessId
  • Type: String
Location Object Id The unique identifier of the Location object to which this location (denormalized) belongs.
  • Field Name: LocationObjectId
  • Type: String
Display 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: DisplayName
  • Type: String
User Object Id * template parameter [1]
  • Field Name: UserObjectId
  • Type: ["String"]
  • Target: device/cuc/User
  • Target attr: ObjectId
  • Format: uri
Location URI
  • Field Name: LocationURI
  • Type: String
  • Format: uri