(Step-By-Step) Cisco Unity Connection SCCP Integration With CUCM Cisco Call Manager

13/09/2019 [Step-by-Step] Cisco Unity Connection SCCP Integration with CUCM Cisco Call Manager
[Step-by-Step] Cisco Unity Connection SCCP Integration with CUCM Cisco Call
Manager
By UCCollaborationGeek | December 9, 2016 2 Comments
The optional Cisco Unity Connection server, available as part of Cisco IP Telephony Solutions,
delivers voice-messaging capability for users when they are unavailable to answer calls. Cisco
Unity Connection SCCP Integration is used to connect CUCM and CUC together.
CUC is compatible with 3rd party PBXs and products, even it supports 3rd party non-IP based
PBXs via PIMG and TIMG methods. Cisco Unity Messaging System also works as an IVR server
for auto attendant.
CUC Voicemail system can be integrated to CUCM via SCCP or SIP protocol. Both of these
integrations have its own pros and cons. We have already seen SIP integration between CUC
and CUCM. Today I would like to explore configuring Cisco Unified Communications Manager
and Unity Connection a step-by-step guide with SCCP integration.
https://www.uccollaborationgeek.com/cisco-unity-connection-sccp-integration-with-cucm/ 1/25
As compared to SIP integration, SCCP (Skinny Client Control Protocol) is straight forward and it
gives a one to one correlation of voicemail ports between CUCM and CUC.
You may have interested to check out the discussion SIP vs SCCP Integration.
Well, let’s begin our configurations.
Cisco Unity Connection SCCP Integration: CUCM Side
Before going to the configuration parameters first, we gonna look at the call flow between
CUCM and CUC. As far as CUCM is concerned the Cisco Unity Connection is an external
application server.
So how to extend our calls to CUC? In SCCP integration of CUC, the call will be extended using
voice mail ports, which is a logical IVR ports between CUCM and CUC.
Please refer the following diagram to better understand the call flow and configuration check
list.
Step 1: MWI Con guration
Message Waiting indicator configuration is required in the case of SCCP integration where
as in SIP integration the MWI information is exchanged via SIP NOTIFY message.
In this step, we create two DNs (Directory Numbers) for turning ON and OFF the MWI.
As production level perspective, we have to configure a Calling Search Space (CSS) for MWI
numbers.
So, let’s go ahead and create Calling Search Space (TEXAS_VM_CSS) for MWI DNs.
[Note: All my phone DNs are in TEXAS_INTERNAL_PT, hence the TEXAS_VM_CSS must contain
TEXAS_INTERNAL_PT].
Navigate to Advanced Features >> Voice Mail >> Message Waiting
Add one DN (1062) for MWI ON and another one DN (1063) MWI OFF as shown in below.
[Note: I kept both of the numbers in TEXAS_INTERNAL_PT]
Step 2: Voice Mail Port Con guration
Interaction between CUCM and CUC done using logical IVR ports called Voice Mail Ports,
which are licensed feature.
Before proceeding to Voice Mail ports, let’s set up a Device Pool for the ports
(TEXAS_APP_SERVER_DEVICE_POOL) and ensure that the all inter region codec is set to G.711.
Navigate over to Advanced Features >> Voice Mail >> Cisco Voice Mail Port Wizard
Give a name to Voice Mail port: CiscoUM1
>> Next
Now specify the number of ports required, it is a licensed feature. The more voice mail port
license you purchase from Cisco, the more concurrent communication it supports.
In our example I have added 10 ports.
>> Next
Configure the Voice Mail port information here.
Description: TEXAS_SCCP_VM_PORT
Device Pool: TEXAS_APP_SERVER_DEVICE_POOL
Calling Search Space: TEXAS_VM_CSS
Location: Hub_None (I’m not con guring any bad width management)
Device Security Pro le: Non Secure Voice Mail Port
>> Next
Each voice mail port can be addressed by a directory number, hence provide a beginning
number and Partition for Voice Mail Port.
I have configured 1064 as beginning directory number (CUCM will automatically assign
remaining 10 numbers) and the partition which I have assigned is TEXAS_INTERNAL_PT.

Internal Caller ID: VoiceMail (Optional, you can con gure as you wish)
External Phone Number Mask: 5125551060 (Optional, best practice to set your main voice mail DID)
>> Next
[Note: The CSS in Voice Mail port and DN in turn avoid hacking of your Unity Connection
to make toll fraud calls. This issue I will cover up later].
After setting up these voicemail ports and their directory number, we should add all the voice
mail port DN to a Line Group.
Select Yes, Add Directory Numbers to a New Line Group
>> Next
Give a name to Line group: TEXAS_VM_LG
>> Next
You can see the confirmation window, verify every settings one more time, go ahead and click
Finish.
You will be presented with Summary page, select Add this Line Group to a new or existing
Hunt List.
Step 3: Hunt List Con guration
Create a new hunt List,
Name: TEXAS_VM_HL
Select proper CUCM group
Check [ ] Enable the hunt list and [ ] For Voice Mail Usage
Add the previously created line group (TEXAS_VM_LG) to it.
>> Save
Step 4: Hunt Pilot Con guration
Go to Call Routing >> Route/Hunt >> Hunt Pilot

Now select a DN, it would be the voice mail number.
Hunt Pilot: 1060

Route Partition: TEXAS_INTERNAL_PT
Description: TEXAS_VM_HP
Hunt List: TEXAS_VM_HL (Created in Step 3)
Alerting Name: Voice Mail
ASCII Alerting Name: Voice Mail
>> Save
Step 5: Voice Mail Pilot Con guration
Go to Advanced Features >> Voice Mail >> Voice Mail Pilot >> Add New
Voice Mail Pilot Number: 1060 (It should be same as Hunt Pilot Number)
Description: TEXAS_VM_PILOT
>> Save
[Note: The CSS will be having visibility to Hunt Pilot DN, since Hunt Pilot DN is in
TEXAS_INTERNAL_PT, we have to assign a CSS which contain TEXAS_INTERNAL_PT for the Voice
Mail Pilot Number]
Step 6: Voice Mail Pro le Con guration
Go to Advanced Features >> Voice Mail >> Voice Mail Profile >> Add New
Voice Mail Pro le Name: TEXAS_VM_PROFILE_SCCP

Description: TEXAS_VM_PROFILE_SCCP
Voice Mail Pilot: 1060/ TEXAS_VM_CSS (Created in Step 5)
>> Save
Step 7: Associate Voice Mail Pro le in Line Page of All Phones
Go to line page of every device and set the Voice Mail Profile that we created in Step 6.
Also configure the Call Forward Voice Mail check boxes based on the requirement.
>> Save
As of now we have successfully completed the CUCM side configurations of Unity Connection
Integration.
Cisco Unity Connection SCCP Integration: Unity Side
Let’s take a look at the Cisco Unity Connections side configurations, it is not bulky as compared
to CUCM side.
Step 8: Unity Phone System Con gurations
Login to Cisco Unity Connection Administration page and go over to Telephony Integrations
>> Phone System
You can see one default PhoneSystem there, we gonna go ahead and use this. Zero
configurations required at the PhoneSystem level. PhoneSystem will be configured if you have
different clusters sharing same Cisco Unity Connection or while integrating with third party
PBXs (PIMG, TIMG).
Let’s go to the next step.
Step 9: Port Group Con gurations
Go to Port Group and click Add New.
Configure the following,
Phone System: PhoneSystem (Step 8)

Port Group Type: SCCP
Display Name: PhoneSystem-SCCP (Optional, you may pick your own)
Device Name Pre x: CiscoUM1-VI
[Note: This should match exactly as the Voice Mail Port name in CUCM]
MWI On Extension: 1062 (Step 1)

MWI O Extension: 1063 (Step 1)
IPV4 Address or Host Name: 142.100.64.11 (CUCM-PUB)
>> Save
[More info: If you wanna to add other subscriber servers, go to Port Group >> Edit >> Servers
Click Add and enter the Subscriber Call Manager IP
Step 10: Port Con gurations
Navigate to Port configuration,
Number of Ports: 10 (Because in CUCM side we speci ed 10 ports)

Phone System: PhoneSystem (Step 8)
Port Group: PhoneSystem-SCCP (Step 9)
Configure Port Behavior as shown below.
>> Save
Check Telephony Con guration
Go to Related Links >> Check Telephony Configuration >> Go
Make sure ‘No problems detected’
Now head over to CUCM and go to Advanced Features >> Voice Mail >> Voice Mail Port >>
Find
Make sure the status of our 10 voice mail port as Registered.
Great! You have successfully integrated Cisco Unity Connection for Cisco Call manager using
SCCP protocol. Now your voice mail system is up and running, try so send couple of voice mails.
In my next article, I will be coming with basic User Management in Cisco Unity Connection.
Hope this helps, don’t forget to like our Facebook page and share the article.
Category: Cisco Unity Connection
2 thoughts on “[Step-by-Step] Cisco Unity Connection SCCP Integration with CUCM Cisco Call
Manager”
Ahmed
July 26, 2018
Thanks
UCCollaborationGeek Post author

July 27, 2018
You are most welcome Ahmed

(Step-By-Step) Cisco Unity Connection SCCP Integration With CUCM Cisco Call Manager

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

(Step-By-Step) Cisco Unity Connection SCCP Integration With CUCM Cisco Call Manager

Uploaded by

Copyright:

Available Formats

13/09/2019 [Step-by-Step] Cisco Unity Connection SCCP Integration with CUCM Cisco Call Manager

Cisco Unity Connection SCCP Integration: CUCM Side

Step 1: MWI Con guration

Navigate to Advanced Features >> Voice Mail >> Message Waiting

[Note: I kept both of the numbers in TEXAS_INTERNAL_PT]

Step 2: Voice Mail Port Con guration

Give a name to Voice Mail port: CiscoUM1

Configure the Voice Mail port information here.

Calling Search Space: TEXAS_VM_CSS

Select Yes, Add Directory Numbers to a New Line Group

Give a name to Line group: TEXAS_VM_LG

Step 3: Hunt List Con guration

Create a new hunt List,

Step 4: Hunt Pilot Con guration

Go to Call Routing >> Route/Hunt >> Hunt Pilot

Hunt Pilot: 1060

Step 5: Voice Mail Pilot Con guration

Step 6: Voice Mail Pro le Con guration

Voice Mail Pro le Name: TEXAS_VM_PROFILE_SCCP

Step 7: Associate Voice Mail Pro le in Line Page of All Phones

Cisco Unity Connection SCCP Integration: Unity Side

Step 8: Unity Phone System Con gurations

Step 9: Port Group Con gurations

Go to Port Group and click Add New.

Configure the following,

Phone System: PhoneSystem (Step 8)

MWI On Extension: 1062 (Step 1)

Click Add and enter the Subscriber Call Manager IP

Step 10: Port Con gurations

Navigate to Port configuration,

Number of Ports: 10 (Because in CUCM side we speci ed 10 ports)

Configure Port Behavior as shown below.

Check Telephony Con guration

Go to Related Links >> Check Telephony Configuration >> Go

Make sure ‘No problems detected’

Make sure the status of our 10 voice mail port as Registered.

Category: Cisco Unity Connection

UCCollaborationGeek Post author

You are most welcome Ahmed

You might also like