Discovery 1: Integrate Cisco Unity Connection

Introduction
As you start configuring your voicemail and messaging system, you need to be aware of the options that you have
for adding users, enabling features, and integrating Cisco Unified Communications Manager with Cisco Unity
Connection.

When integrated with Cisco Unified Communications Manager, Cisco Unity Connection provides voice-messaging
features for users that you configure manually, or through LDAP integration. After receiving voice messages in their
mailboxes, users receive message-waiting lights on their phones. Users can retrieve, listen to, reply to, forward,
and delete their messages by accessing the voice-messaging system with an internal or external call.
This lab will take approximately 120 minutes to complete.

Topology

Job Aid
Device Information

Device Description IP Address Credentials

PC-1 Jump Host 1 10.1.5.200 Student, C0ll@B

PC-2 Jump Host 2 10.1.5.201 Student, C0ll@B

HQ-UCM Cisco Unified Communications Manager 10.1.5.5 administrator, C0ll@B

UCX Cisco Unity Connection 10.1.5.8 administrator, C0ll@B

Task 1: Integrate Cisco Unified Communications Manager with Cisco Unity
Connection Via SCCP
You will configure and verify SCCP integration between Cisco Unity Connection and Cisco Unified Communications
Manager.

Activity
Prepare for Discovery
You will register two Cisco IP Communicators on Cisco Unified Communications Manager.

Step 1
Connect to PC-1, wait until you see the network connection notification (blue panel on right side) Click
No button to cancel network discovery. If you do not see the blue network notificaton wait for a while for
the lab automation system to finish configuring PC-1.

Step 2
On PC-1, open Firefox and navigate to Cisco Unified Communications Manager Administration
(https://10.1.5.5/ccmadmin). Log in using Administrator for the username and C0ll@B for the password.
Step 3
Select Device > Phone, click Find and observe if Cisco IP Communicator phones are displayed. If phones are
not displayed wait a while for the automation system to finish configuring Cisco Unified Communicacitons
Manager and then click Find again. Continue only when phones are displayed.

Step 4
Connect to PC-1 and register Cisco IP Communicator with Cisco Unified CM. PC-1 uses DN 11001 on its first
line. You will call this phone HQ Phone 1 throughout the discovery.

Device Name: HQ-CIPC-1

TFTP: 10.1.5.5

Step 5
Connect to PC-2 and register Cisco IP Communicator with Cisco Unified CM. PC-2 uses DN 11002 on its first
line. We will call this phone HQ Phone 2 throughout this discovery.

Device Name: HQ-CIPC-2

TFTP: 10.1.5.5

Run the Voice Mail Port Wizard on Cisco Unified Communications Manager
You will configure Cisco Unified Communications Manager for SCCP integration with Cisco Unity Connection.

Step 6
On PC-1, using the Firefox browser, log into Cisco Unified Communications Manager Administration using the
 credentials from the Job Aids. Choose Advanced Features > Voice Mail and start the Cisco Voice Mail Port
wizard. Configure the following settings; for the parameters not listed here, use the default values that the wizard
suggests:

Add a New Voicemail Server

Cisco Voice Mail Server Name: Cisco-VM-P1

Add Ports

Number of Ports: 4

Configure Device Information for Ports:

Description: SCCP Voice Mail Port Group 1

Device Pool: HQ
Calling Search Space: DEVICE_HEADQUARTERS_CSS
Device Security Mode: Non Secure Voice Mail Port
Location: HQ
Configure Directory Numbers:

Beginning Directory Number: 18101

Partition: LINE_INTERNAL_PT
Calling Search Space: LINE_LONGDISTANCE_CSS
External Number Mask: 408555XXXX

Configure Line Group:

Check the Yes. Add directory numbers to a new Line Group radio button
Line Group Name: Voicemail_LG

Step 7
 Review the configuration and finish the wizard. Click the Hunt List wizard hyperlink and create a new hunt list
with the following settings:

Name: Voicemail_HL
Description: SCCP Voicemail Hunt List
Cisco Unified Communications Manager Group: HQ-CUCM-GROUP-1
Enable This Hunt List: Check the box
For Voice Mail Usage: Check the box

Step 8
After saving this hunt group, add the line group Voicemail_LG to the hunt list. Save and Reset the hunt list. Go
back to the hunt list overview (Call Routing > Route/Hunt > Hunt List) and check that the status shows
“Registered with CUCM-PUB.CLL-COLLAB.INTERNAL.”
Step 9
 Choose Call Routing > Route/Hunt > Hunt Pilot and configure a new hunt pilot with the following settings:

Hunt Pilot: 18100

Route Partition: LINE_INTERNAL_PT
Description: SCCP Voicemail Hunt Pilot
Hunt List: Voicemail_HL
Provide Outside Dial Tone: Uncheck the box.
Save the configuration

Configure the Voice Mail Pilot and Profile on Cisco Unified Communications Manager
You will add the voicemail pilot number, which is the extension that you dial to listen to your voice messages. Then
you will add a voicemail profile, so that your Cisco IP phone automatically dials the voicemail pilot number when
you press the Messages button.

Step 10
Choose Advanced Features > Voice Mail > Voice Mail Pilot. Click Add New to add a new voicemail pilot.
Configure the following settings:

Voice Mail Pilot Number: 18100

Calling Search Space: LINE_INTERNAL_ONLY_CSS
Description: Voice Mail Pilot – SCCP Integration
Make This the Default Voice Mail Pilot for the System: Check the box.

There can only be one default voicemail pilot in a Cisco Unified Communications Manager cluster.
Use the default for most phones.
Step 11
Choose Advanced Features > Voice Mail > Voice Mail Profile. Click Add New to add a new voicemail profile.
Configure the following settings:

Voice Mail Profile Name: SCCP-VM-PROFILE

Description: SCCP Voicemail profile
Voice Mail Pilot: 18100/LINE_INTERNAL_ONLY_CSS
Make This the Default Voice Mail Profile for the System: Check the box.
Voice Mail Box Mask: XXXXX

There can be only one default voicemail profile in a Cisco Unified Communications Manager cluster.
Use the default for most phones so that it is automatically used without any phone-specific
configuration requirements.
The Voice Mail Box Mask is used to format the voice mailbox number for auto-registered phones.
When a call is forwarded to a voice-messaging system from a directory line on an auto-registered
phone, Cisco Unified Communications Manager applies this mask to the number that is configured in
the Voice Mail Box field for that directory line.
Step 12
Choose Advanced Features > Voice Mail > Message Waiting and add new MWIs. Configure the following:

Message Waiting Number: 18198

Partition: LINE_INTERNAL_PT
Description: SCCP MWI On
Message Waiting Indicator: On
Calling Search Space: LINE_INTERNAL_ONLY_CSS
Step 13
After saving, copy the MWI entry and change the number to 18199. Change the description to SCCP MWI Off,
and set the indicator to Off.
Step 14
Go back to the Message Waiting Numbers overview. You will see the numbers 18198 and 18199 for MWI on
and off, respectively. Notice that the used icons are colored: green for on, and red for off.
Step 15
Go to the HQ-CIPC-1 phone configuration in Cisco Unified Communications Manager and choose Line [1] -
11001. The Voice Mail Profile is set to <None> by default. The description next to the drop-down box is “Choose
<None> to use system default.” If you use the default voicemail profile for most the phones, you do not have to
configure the profile for every DN.

Step 16
Reset the DN. Press the Message button on HQ phone 1. You will get a reorder tone because the hunt pilot
18100 was dialed and the Cisco Unity Connection server is not yet configured.

Integrate Cisco Unity Connection Using SCCP

Now you will configure Cisco Unity Connection for SCCP integration with Cisco Unified Communications Manager.

Step 17
On PC-1, using the Firefox browser, log in to Cisco Unity Connection Administration using the credentials from
the Job Aids. Choose Telephony Integrations > Phone System. Choose the default Phone System and review
the settings. Rename the phone system as SCCP CUCM Integration, check Send Message Counts check box,
and keep the other default settings. Notice the message “The phone system cannot take calls until a port group
is set. Use the Related Links to add a port group.”
Step 18
Add a new port group for Cisco Unified Communications Manager. Use Related Links and choose Add Port
Group or choose Telephony Integrations > Port Group and configure the following settings:

Display Name: SCCP CUCM Integration-1

Device Name Prefix: Cisco-VM-P1-VI
MWI On Extension: 18198
MWI Off Extension: 18199
IPv4 Address or Host Name: 10.1.5.5

The Device Name Prefix, must be the same as it is configured in Cisco Unified Communications
Manager, otherwise the voicemail ports will not register in Cisco Unified Communications Manager.
For redundancy, you can configure a second Cisco Unified Communications Manager server
address in Cisco Unity Connection in a production environment.
Step 19
After you save, this message is displayed: “The phone system cannot take calls if it has no ports. Use the
Related Links to add ports.”
Step 20
Add the ports using the Related Links. Choose Add Ports or choose Telephony Integrations > Port. On the
Port page, change the Number of Ports from 1 to 4 and save the changes.
Step 21
In the Related Links, choose Check Telephony Configuration. The Task Execution Results window should
show that no problems are detected.
Step 22
Return to Cisco Unified Communications Manager Administration and choose Advanced Features > Voice Mail
> Cisco Voice Mail Port. Click Find. You should see that all four voicemail ports now have the status
“Registered with CUCM-PUB.CLL-COLLAB.INTERNAL” and have the IPv4 address 10.1.5.8.

Use the Cisco Unified Communications Manager Real-Time Monitoring Tool as the Port Monitor
Now you will use Cisco Unified Communications Manager Real-Time Monitoring Tool (Cisco Unified RTMT) to
verify your SCCP integration.

Step 23
On PC-1, use Explorer to browse to Z:\ drive and start Cisco Unified RTMT installer by double click the
file CcmServRtmtPlugin.exe.

Step 24
Follow Cisco Unified RTMT installer instructions to complete the installation proccess.
 Step 25
On PC-1, start the Cisco Unified RTMT and connect to Cisco Unity Connection via the IP address 10.1.5.8.
Accept any certification messages and log in with the Cisco Unity Connection Application Administrator
credentials. When the tool starts, choose Default in the Configuration List and click OK. Choose Cisco Unity
Connection > Port Monitor, choose the node, set the polling rate to 1 second, and start the polling. After a few
seconds, you will see the four SCCP ports that you set up. All four ports are idle.

Step 26
In the Application Status and Display Status fields, you can see what happens in Cisco Unity Connection. On HQ
Phone 1, press the Messages button again to make another call to Cisco Unity Connection. During the call,
hover the mouse over the Display Status field. First, the opening greeting prompt is played, followed by the
operator and goodbye prompts. The goodbye call handler ends the call. This process will take a few seconds to
complete.
Step 27
Press the Messages button on HQ Phone 1 again. You should see the incoming call on the first port. View the
displayed call information in the Port Monitor and take some time to become familiar with Cisco Unified RTMT.

Choose the row of interest and move the cursor over the field Display Status, for example. You can read
the full text and know what happens if you have to troubleshoot a remote user call.

Task 2: Integrate Cisco Unified Communications Manager with Cisco Unity

Connection Via SIP
You will configure and verify SIP integration between Cisco Unity Connection and Cisco Unified Communications
Manager.

Activity
Configure Cisco Unified Communications Manager for SIP Integration
You will configure a SIP connection to Cisco Unity Connection to access the voice-messaging system.

Step 1
In Cisco Unified Communications Manager Administration, choose System > Security > SIP Trunk Security
Profile. Add a new profile and configure the following:

Name: HQ SIP TRUNK FOR UNITYCX

Description: Headquarters SIP Trunk Profile for Cisco Unity Cx
Accept Out-of-Dialog Refer: Check the box.
Accept Unsolicited Notification: Check the box.
Accept Replaces Header: Check the box.
Step 2
Choose Device > Trunk and add a new SIP trunk pointing to Cisco Unity Connection with the following settings:

Device Name: 10.1.5.8

Description: HQ SIP Trunk to CUCx
Device Pool: HQ
Calling Search Space Inbound Calls section: LINE_INTERNAL_ONLY_CSS
Redirecting Diversion Header Delivery – Inbound: Check the box.
Redirecting Diversion Header Delivery – Outbound: Check the box.
SIP Destination Address: 10.1.5.8
SIP Trunk Security Profile: HQ SIP TRUNK FOR UNITYCX
Rerouting Calling Search Space: LINE_INTERNAL_ONLY_CSS
Out-of-Dialog Refer Calling Search Space: LINE_INTERNAL_ONLY_CSS
SIP Profile: HQ SIP Profile
Step 3
Save and reset the trunk.

Step 4
Choose Advanced Features > Voice Mail > Voice Mail Pilot. Add a new voicemail pilot for SIP access to Cisco
Unity Connection with the following settings (do not make this voicemail pilot the system default!):

Voice Mail Pilot Number: 18200

Calling Search Space: LINE_INTERNAL_ONLY_CSS
Description: Voice Mail Pilot – SIP Integration
Step 5
Choose Advanced Features > Voice Mail > Voice Mail Profile. Add a new profile with the following settings (do
not make this voicemail profile as system default!):

Voice Mail Profile Name: SIP-VM-PROFILE

Description: SIP Voicemail Profile
Voice Mail Pilot: 18200/LINE_INTERNAL_ONLY_CSS
Voice Mail Box Mask: XXXXX
Step 6
Choose Call Routing > Route/Hunt > Route Pattern and create a new route pattern to reach Cisco Unity
Connection with the following settings:

Route Pattern: 18200

Route Partition: LINE_INTERNAL_PT
Description: HQ SIP Voice Mail Route Pattern
Gateway/Route List: 10.1.5.8
Provide Outside Dial Tone: Uncheck the box.
Save

When you uncheck the Provide Outside Dial Tone box, look at the Call Classification setting, which
changes to OnNet.
Step 7
Go to HQ Phone 2 and configure the DN to use your newly created SIP voicemail profile. Now HQ Phone 1 (DN
11001) uses SCCP and HQ Phone 2 (DN 11002) uses SIP to reach Cisco Unity Connection.
Step 8
Press the Messages button on HQ Phone 2. You will hear a reorder tone because the voicemail pilot 18200 was
dialed and the Cisco Unity Connection server is not yet configured for SIP integration. If the phone is not dialing
the voicemail pilot number, reset the DN.

Integrate Cisco Unity Connection Using SIP

Step 9
In Cisco Unity Connection Administration, choose Telephony Integrations > Phone System and add a new
phone system named SIP CUCM Integration. Check Send Message Counts check box and keep all the other
default settings.
Step 10
Add the port group to Cisco Unity Connection with the following settings:

Port Group Type: SIP

IPv4 Address or Host Name: 10.1.5.5

For redundancy, you can configure a second Cisco Unified Communications Manager server address in
Cisco Unity Connection in production environments.
Step 11
Add four ports for SIP integration. Use the Check Telephony Configuration tool again. No problems should be
detected.
Step 12
Press the Messages button on HQ Phone 2 and open the Port Monitor. You should hear the Cisco Unity
Connection opening greeting. In the Port Monitor, you should see eight ports, and a SIP port should answer the
call.

For the SCCP integration, the top-down algorithm is used to choose ports. That is, the phone always
uses the first port. If you press the Messages button again on HQ Phone 2, you see that the SIP trunk
works with the circular algorithm. If you press the Messages button a second time, the Port Monitor will
show that the second SIP port is used.

Step 13
If Cisco Unity Connection does not answer the call, review the configuration.

Task 3: Examine Call Routing in Cisco Unity Connection

You will examine how the default call routing works.

Default Call-Routing Behavior

By default, two direct and two forwarded call-routing rules exist in Cisco Unity Connection.

For direct calls, the user can log into the mailbox by entering the PIN. If the caller has no assigned mailbox, then
the standard opening greeting is played.
For forwarded calls in which a caller dials an extension that is not answering, the call is forwarded to Cisco Unity
Connection. If the forwarding number is a configured extension in Cisco Unity Connection, then the caller can leave
a message for this user. If the extension is not configured, then the standard opening greeting is played to the
caller.
Additional call-routing rules can be configured for direct and forwarded calls to manage call routing or start an auto-
attendant.

Direct Call Routing

Direct call-routing rules process calls from users and unidentified callers who directly dial Cisco Unity Connection.

The following are the predefined default direct call-routing rules:

Attempt Sign-In: Calls from users (identified users) are routed to the user login conversation.
Opening Greeting: Calls from unidentified callers (users without a mailbox) are routed to the opening greeting.

The order of the Attempt Sign-In rule can be changed. Rules that are added in the direct call-routing table can also
be changed. The Opening Greeting rule is always the last entry in the call-routing table.
When a direct call-routing rule is used, calls can be filtered and an action can be applied. Callers can be sent to the
following options:
Calling Number: The rule is applied for a specified calling number, such as 11001 or 123*, for all calls starting
with 123.
Dialed Number: The rule is applied for a specified dialed number such as the number of a call handler.
Port: The rule is applied for a specified incoming port (1 to n).
Phone System: The rule is applied for a specified phone system that delivers the call. This condition can be
chosen if more than one phone system exists.
Schedule: The rule is applied for the chosen schedule, such as all hours, weekdays, or any customized
schedule.

Call actions can be used in combination with rule conditions. For example, all calls that come from the phone
number of a particular customer can be transferred directly to the user. Or all calls that come to an outdated
company number can receive an informational message about the new number and then be transferred to the
company auto-attendant.

You can specify the following call-routing rule conditions:

Calling Number: The rule reacts according to the calling number, such as 11001, or 123*, for all calls starting
with 123.
Dialed Number: The rule reacts according to the dialed number, such as the number of a call handler.
Port: The rule reacts according to the incoming port (1 to n).
Phone System: The rule reacts according to the phone system that delivers the call. This condition can be
chosen if more than one phone system exists.
Schedule: The rule reacts according to a chosen schedule, such as all hours, weekdays, or any customized
schedule.

When combined with the call action, such rule conditions can, for example, transfer all calls from the area code 123
to a certain user, or process all calls from 11001 in a specific way.

A call-routing rule can be configured with one or more rule conditions. If any rule condition matches, the call action
is executed.

Forwarded Call Routing

Forwarded call-routing rules process calls that are forwarded to Cisco Unity Connection. Forwarded calls are from
a user extension or from an extension that is not associated with a user account, such as a conference room.

The following forwarded routing rules are predefined:

Attempt Forward: All calls that are forwarded from a Cisco Unity Connection user with a mailbox are routed to
the user greeting. The caller can leave a message.
Opening Greeting: Calls that are forwarded from an extension that is not associated with a user account are
routed to the opening greeting.

The difference between direct routing and forward routing is the origin of the call:
Direct call
Forwarded call

An extra rule condition is available for forwarded calls compared to directed calls. This rule is the Forwarding
Station rule condition, which reacts according to the number of the phone that is configured with a Call Forward.

Forwarding routing rules can be used, for example, to process all calls that go to a conference station and to send
these calls to an operator.

Activity
Test the Default Call-Routing Behavior for Directed Calls
You will test the default call-routing behavior for direct calls.

Step 1
From HQ Phone 1, call Cisco Unity Connection and monitor the call in Cisco Unified RTMT. You should see that
the reason is listed as Direct for a direct call.
Step 2
In Cisco Unity Connection, choose Call Management > Call Routing > Direct Routing Rules. Open the first
rule. The Attempt Sign In rule sends all identified callers to the mailbox login because the Conversation is set to
Attempt Sign-In.
Step 3
Choose the second rule, Opening Greeting. This rule is always the last rule and sends all callers to the opening
greeting call handler, which you just heard.
Step 4
Choose Users > Users and add a new user with the following settings:

Based on Template: voicemailusertemplate

Alias: jdoe
First Name: John
Last Name: Doe
Display Name: John Doe
Extension: 11001

The display name is filled in automatically. It is also the name that is announced to callers by default.
Step 5
After saving, set the Active Schedule to All Hours and uncheck the Set for Self-Enrollment at Next Sign-In
check box and click Save.
Step 6
Choose Edit > Change Password and set the PIN to 123789. Choose Edit > Password Settings and uncheck
the User Must Change at Next Sign-In check box.
Step 7
Press the Messages button on HQ Phone 1. You will be asked to log in to your mailbox. Monitor the call flow in
Cisco Unified RTMT. RTMT will show first Subscriber-Sign-In. When you are prompted, enter the PIN followed by
the pound sign (). You will see “Display Status: Subscriber Mailbox (John Doe)” in Cisco Unified RTMT.

Test the Default Call-Routing Behavior for Forwarded Directed Call Routing
You will test the default call-routing behavior for forwarded calls.

Step 8
Choose Call Management > Call Routing > Forwarded Routing Rules. Open the first rule. The Attempt
Forward rule sends all identified redirected callers to the mailbox to leave a message. Therefore, the
Conversation is set to Attempt Forward.
Step 9
Choose the second rule, Opening Greeting. This rule is always the last rule and sends all redirected callers to
the opening greeting call handler.
Step 10
On PC-2, use the Firefox browser to access http://10.1.5.100/Sample Voicemail.mp4. You will use this sample
voice message for testing purposes.

Step 11
Make a call from 11002 (HQ Phone 2) to 11001 (HQ Phone 1) and do not pick up. After 20 seconds, the call will
be forwarded to Cisco Unity Connection due to the CFNA condition. Cisco Unified RTMT (on PC-1) will show
“Display Status: Playing Greeting for Subscriber John Doe.” When asked to leave a message, go to PC-2 and
click the Play button to play the sample voice message, then hang up. Follow the call in the Port Monitor,
especially the call reason and redirected number, and verify that SCCP is used.
Step 12
On HQ Phone 1, you should now see the envelope icon next to line 1, which means it has new voice messages.
Press the Messages button on HQ Phone 1, log in to your mailbox, and listen to the new message. Press 3 to
delete it. Monitor the call flow in Cisco Unified RTMT to see how the Application Status and Conversation Status
change as you jump between stages of the conversation.
Step 13
Return to Cisco Unity Administration and add another user, Jane White, with the Alias jwhite and the extension
11002. Modify the following parameters and leave the other settings the same as for John Doe:

Phone System: SIP CUCM Integration

Active Schedule: All Hours
Set for Self-Enrollment at Next Sign-In: Uncheck the box.

After saving, set the PIN to 123789 and uncheck the User Must Change at Next Sign-In check box.
Step 14
Call from 11001 (HQ Phone 1) to 11002 (HQ Phone 2) and do not pick up. Follow the call with the Port Monitor,
especially the call reason and redirected number. Verify that the SIP CUCM Integration phone system is used,
and that you see “Display Status: Playing Greeting for Subscriber Jane White.”
Add and Modify Call-Routing Rules to Test Call-Routing Behavior

Step 15
Add a new direct call-routing rule called direct_rule_test. After saving, press the Message button on both HQ
phones. Evaluate what happens. You should see “Display Status: Entering Name Lookup Handler in the Port
Monitor.”
Step 16
In the new rule, look at the section Send Call To. Because there is no configured routing rule condition, all calls
are matched and are sent to the system directory handler. The caller is asked to spell the last and first name of
the user they want to reach.

Step 17
Delete the new direct_rule_test rule.

Step 18
Go to the Attempt Sign-In rule and add a routing rule condition as follows:

Calling Number: Equals 11001

Step 19
Place a call from 11001 to Cisco Unity Connection. Cisco Unity Connection will ask for the PIN, and in the Port
Monitor you should see “Display Status: Subscriber Sign-In.”

Step 20
Now call from 11002 to Cisco Unity Connection. Evaluate what happens. Because only the caller with the
extension 11001 is allowed to log in to the user mailbox, all callers—even identified users—are sent to the
opening greeting and you see Playing Opening Greeting in the port monitor.

Step 21
Remove the routing rule condition and test that both users can again log in to their mailbox. In the Port Monitor,
you should see “Display Status: Subscriber Sign-In” for both callers.