cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1614
Views
0
Helpful
0
Comments
Meddane
VIP
VIP

Scenario:

This article describes the auto attendant configuration on Cisco Unity Connection by managing call handler, transfer rules, caller input and Direct Routing Rules.
The goal is: call the auto attendant number and when the caller is connected, use the digit numbers to take actions such as transfer a call to another user, transfer a call to conference hosted on Cisco Meeting Server and search in the directory.

Components used:

The article is based on:

Cisco Unity Connection 12.5.
Cisco Unified Communication Manager 12.5.
Cisco Meeting Server version 3.0.0.

Meddane_0-1660753870896.png

 Configure Voice Mail Pilot

Navigate to Advanced Features > Voice Mail > Voice Mail Pilot. Add a new voicemail pilot for SIP integration to Cisco Unity Connection with the following settings:

Voice Mail Pilot Number: 2200

Calling Search Space: None

Meddane_1-1660753870902.png

Meddane_2-1660753870908.png

Configure Voice Mail Profile

Navigate to Advanced Features > Voice Mail > Voice Mail Profile. Add a new profile with the following settings:

  • Voice Mail Profile Name: SIP
  • Voice Mail Pilot: 2200

Meddane_3-1660753870915.png

Meddane_4-1660753870921.png

On HQ-CUCM, navigate to Device > Device Settings > SIP Profile. Enter the name SIP_Trunk_Profile_CUC. Enable the SIP OPTIONS ping.

Meddane_5-1660753870930.png

Meddane_6-1660753870937.png

Meddane_7-1660753870940.png

On HQ-CUCM, navigate to System > Security > Sip Trunk Security Profile.

Create a SIP Trunk Security Profile with the following settings :

  • Name: SIP_Trunk_Security_Profile_CUC
  • Device Security Mode: Non Secure
  • Incoming Transport Type: TCP+UDP
  • Outgoing Transport Type: TCP
  • Incoming port: 5060
  • Accept presence subscription: check the box
  • Accept out-of-dialog refer: check the box
  • Accept unsolicited notification: check the box
  • Accept Replaces Header: check the box

Meddane_8-1660753870948.png

Meddane_9-1660753870955.png

Create a SIP Trunk toward hq-cuc.lab.local 10.1.5.17, named SIP-Trunk-CUC.

Meddane_10-1660753870964.png

In the SIP Information, enter the IP address 10.1.5.17 of HQ-CUC, and select the Trunk_SIP_Security_Profile_CUC and SIP_Trunk_Profile_CUC.

Meddane_11-1660753870967.png

Meddane_12-1660753870978.png

Create a new route pattern to reach Cisco Unity Connection with the following settings:

  • Route Pattern: 2200
  • Gateway/Route List: SIP-Trunk-CUC

Meddane_13-1660753870986.png

Meddane_14-1660753870992.png

Meddane_15-1660753871005.png

Meddane_16-1660753871014.png

Meddane_17-1660753871022.png

On HQ-CUC, select Telephony Integrations > Phone System and add a new phone system named PhoneSystemSIP.

 Meddane_18-1660753871032.png

Add the port group to HQ-CUC with the following settings:

  • Port Group Type: SIP
  • IPv4 Address or Host Name: 10.1.5.15

Meddane_19-1660753871039.png

Meddane_20-1660753871047.png

Meddane_21-1660753871054.png

Add 2 ports for the SIP integration.

Meddane_22-1660753871062.png

Meddane_23-1660753871069.png

On HQ-CUC, choose Call Management > Directory Handlers and add a new call handler. Enter a display name HQ-Directory with extension 3300.

Meddane_24-1660753871076.png

Meddane_25-1660753871087.png

Meddane_26-1660753871095.png

Add a new system call handler called HQ-AA with the Extension 9900.

Meddane_27-1660753871104.png

Meddane_28-1660753871112.png

Meddane_29-1660753871121.png

Meddane_30-1660753871129.png

Add a new system call handler called To-Jdoe-Extension without extension.

Meddane_31-1660753871135.png

Meddane_32-1660753871144.png

Go to Edit > Transfer Rules. In the standard transfer rule, under the Transfer Action send the calls to the Extension or URI 51001.

Meddane_33-1660753871150.png

Meddane_34-1660753871160.png

Meddane_35-1660753871167.png

Add a new system call handler called Demystify From Scratch Meeting without extension.

Meddane_36-1660753871172.png

Meddane_37-1660753871181.png

Go to Edit > Transfer Rules. In the standard transfer rule, under the Transfer Action send the calls to the Extension or URI ccnp@collab.lab.local.

Meddane_38-1660753871187.png

Meddane_39-1660753871196.png

Meddane_40-1660753871203.png

Edit the System Call Handler HQ-AA.

Meddane_41-1660753871213.png

In the call handler, choose Edit > Caller Input. Configure the following actions to caller inputs to link the call handlers together:

Caller Input 1: Set the Call Handler to To-Jdoe-Extension.

Meddane_42-1660753871221.png

Meddane_43-1660753871230.png

Caller Input 2: Set the Call Handler to Demystify From Scratch Meeting.

Meddane_44-1660753871238.png

Caller Input 3: Set the Directory Handler to HQ-Directory.

Meddane_45-1660753871246.png

Meddane_46-1660753871255.png

When users call the Auto Attendant System 9900 defined in Cisco Unity Connection, they cannot reach the AA et hear the openning greeting “Enter your pin followed by pound etc….” instead of the Auto Attendant greeting.

The cause of this problem is the Default Call-Routing Behavior. When users dial the AA number 9900, CUCM routes this call to CUC through SIP trunk, the CUC considers this call as a Directed calls, before handling the call with the system call handlers, CUC needs to route the call using the call routing rules.

For direct calls two routing rules can be applied:

  1. Attempt Sign In if the calling number is associated with mailbox
  2. Opening Greeting if the calling number is not associated with mailbox

To solve this problem and the users will be routed to the System Call Handler AA 9900 a new routing rule with a dialed number 9900 as condition should be added with the following configuration:

  1. Send Call To -> Call Handler: HQ-AA.
  2. Direct Routing Condition Rule Condition -> Dialed Number EQUAL 9900.

Now when users dials the AA number 9900 the CUC looks in its routing table a match rule, from TOP – DOWN, and finds a match with a condition DIALED NUMBER 9900 and makes an action defined in the “Send Call to AA-Main” and now the users are redirected to the Auto Attendant and navigate through the menu offered by the system.

Meddane_47-1660753871262.png

Add a new Direct Routing Rule named HQ-AA Routing Rule. Send the call to the Call

Handler HQ-AA. Add a rule condition where Dialed Number Equals 9900.

Meddane_48-1660753871267.png

Meddane_49-1660753871277.png

Meddane_50-1660753871284.png

Meddane_51-1660753871293.png

Meddane_52-1660753871302.png

In the System Call Handler HQ-AA, Under the Standard Greeting transfer rules, check the Allow Transfers to Numbers not Associated with Users or Call Handlers.

Meddane_53-1660753871311.png

Cisco Unity Connection PCA can be used by users to attempt to change a phone number that is used for call transfer, in this situation, Cisco Unity Connection applies the restriction table that is associated with the CoS Class Of Service of the user to verify that the entered phone number is allowed.

Note the restriction table is not checked when an administrator changes the extension via the Cisco Unity Connection, while it is checked when a user changes the extension number via TUI or PCA.

Access the Cisco Unity Connection HQ-CUC, navigate to System Settings > Restriction Tables, you should see five predefined restriction tables.

Edit the Default System Transfer, all restriction tables block long-distance and international number by default.

Meddane_54-1660753871321.png

To allow transfer numbers or URI such as ccnp@ccnp.lab.local uncheck the pattern “*” to avoid blocking this pattern and click Save.

Meddane_55-1660753871330.png

Using the AudioText Manager tool access the Cisco Unity Connection to record a new standard greeting that announces the options listed in the Caller Inputs of the Call Handler HQ-AA.

Meddane_56-1660753871334.png

Record something like this :

« Hello, this is my lab collaboration, type 1 to reach john doe, type 2 to reach a conference, type 3 to look in the head quarter directory »

Meddane_57-1660753871348.png

Meddane_58-1660753871357.png

On HQ-CUCM. Create a new route pattern to reach Auto Attendant number 9900 with the following settings:

  • Route Pattern: 9900
  • Gateway/Route List: SIP-Trunk-CUC

Meddane_59-1660753871363.png

Meddane_60-1660753871371.png

Meddane_61-1660753871378.png

One CIPC US Phone registered with the DN 11001, and Jabber Client registered with user jdoe and DN 51001.

Meddane_62-1660753871410.png

Meddane_63-1660753871414.png

From the US Phone dials 9900. You should hear the standard greeting recorded previously : « Hello, this is my lab collaboration, type 1 to reach john doe, type 2 to reach a conference, type 3 to look in the head quarter directory »

Meddane_64-1660753871436.png

Type the Digit 1, The Cisco Unity Connection transfers the call to John Doe and the Jabber Client rings.

Meddane_65-1660753871465.png

Type the digit 2, the US Phone is connected to the Meeting or the space hosted by the Cisco Meeting Server Cluster.

Meddane_66-1660753871487.png

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: