Configure Direct Transfer to Unity Connection Mailbox with Extension Wildcard

Available Languages

Download Options

  • PDF     (97.1 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (151.5 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (163.2 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:October 10, 2018
Document ID:213808

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes how to transfer calls directly into a voicemail box with extension mask in Cisco Unity Connection (CUC).

     Contributed by Luis Gomez, Cisco TAC Engineer.

    Prerequisites

    Requirements

    Cisco recommends that you have knowledge of these topics:

    • Unity Connection
    • Cisco Unfied Communication Manager (CUCM)

    Components Used

    The information in this document is based on CUC Release 9.X or later integrated via Session Initiation Protocol (SIP) or  Skinny Call Control Protocol (SCCP) with CUCM 9.x or later.

    The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

    Configuration

    Step 1. Create a new Voice Mail Profile on CUCM:

    Navigate to Advance Features > Voice Mail >  Voice Mail Profile > Add New

    Voice Mail Profile Name

    Use a distinguished name for this Profile
    Description Optional
    Voice Mail Pilot

    Assign the pre-configured pilot number and Calling Search Space (CSS) for current integration, use Route Pattern if SIP or Hunt Pilot if SCCP
    Voice Mail Box Mask Use a wildcard to match the dialing plan of users extension, for example: use XXXX to match 4 digit extensions dial plan
    Make this the default Voice Mail Profile for the System Unchecked

    Similar as shown in the image:

               

    Step 2. Create a new CTI Route Point on CUCM:

    Navigate to Device > CTI Route Point > Add New, configure these settings:

    Device Name Use a distinguished name for this Route Point
    Description Optional
    Device Pool Use pre-configured Device Pool for Voice Mail Integration
    Calling Search Space Use pre-configured CSS for Voice Mail Integration

    Similar as shown in the image:

              

    Step 3.  Configure the Directory Number for CTI

    Add a New Line under the Association section, configure the Directory Number as asterisk+wildcard  to match dial plan of users extensions:

    Similar as shown in the image:

              

    Under Call Forward and Call Pickup Settings select Forward All to Voice Mail option:

              

    Verify

    Transfer to any pattern that match *XXXX reach the CTI Route Point, the Voicemail Box mask XXXX allows only 4 digit extension to be routed, Unity Connection receives the call as a forwarded call to that extension and send caller directly to user's mailbox.

    Troubleshoot

    For transferred call that reach CUC Default Opening Greeting use Remote Port Status Monitor (rPSM) for Unity Connection to verify the transfer extensions.

    TAC Authored

    Contributed by Cisco Engineers

    • Luis Gomez
      Cisco TAC Engineer

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products