How to setup CUCM 10.5 for Exchange 2013 Unified Messaging Voicemail

twitterlinkedinmail

CUCM 10.5 Configuration

Update:

Originally we were running version: 10.5.2.10000-5 where we had some issues and had to upgrade to version: 10.5.2.12901-1 in order to fix the issue and have it functional again.

Create a SIP Profile

1. Log into your CUCM web console: https://X.X.X.X

2. From the menu select: Device –> Device settings –> SIP Profile

3. Click Add New

4. Provide a name and configure the SIP profile as per the screen shots below ensure that:

a. SDP Information

i. SDP-Session-level Bandwidth Modifier for Early Offer and Re-invites is set to TIAS and AS

b. Early offer support for voice and video calls* is set to : Mandatory (insert MTP if needed)

5. Click Save

clip_image002

clip_image004

clip_image006

clip_image008

Create SIP Trunk Security Profile

We will need to 2 SIP Trunk Security Profiles: 1 for the CAS(Client Access Server) and 1 for the MBX (Mailbox) The reason for this is the initial request from the CUCM server to Exchange UM will go out on port 5060, however the Exchange UM server will send a 302 Moved Temporarily and redirect us to talk back to it on port 5062.

1. From the Menu Select: System -> Security -> SIP Trunk Security Profile

2. Click Add New

3. Create 2 SIP Trunk Security Profiles: 1 for the CAS(Client Access Server) and 1 for the MBX (Mailbox) The reason for this

a. CAS

i. Provide a proper name

ii. Ensure Incoming Port is set to 5060

iii. Check the boxes for:

1. Accept out-of-dialog refer**

2. Accept unsolicited notification

3. Accept replaces header

clip_image010

b. MBX

i. Provide a proper name

ii. Ensure Incoming Port is set to 5062

iii. Check the boxes for:

1. Accept out-of-dialog refer**

2. Accept unsolicited notification

3. Accept replaces header

clip_image012

Create a SIP Trunk

We will need to create 2 SIP Trunks, one USING the IP of the CAS port 5060 and the other using FQDN of the MBX on ports 5062, 5065, 5067, the reason is will when the CUCM first sending the invite to Exchange UM it goes out on port 5060, the Exchange UM server redirects to port 5062 and subsequently could redirect on ports 5065,5067 as well.

1. From the menu Select: Device –>Trunk

2. Click Add New

3. Trunk Configuration

a. CAS – Follow the screenshots below and ensure you have the below configured

i. Check: Media Termination Point Required

ii. UnCheck: PSTN Access

iii. Check: Redirecting Diversion Header Delivery – Inbound

iv. Check: Redirecting Diversion Header Delivery – Outbound

v. SIP Information:

1. Line 1 enter the IP Address of the Exchange Server x.x.x.x in the destination address field and port 5060

vi. Click Save

clip_image014

clip_image016

clip_image018

 clip_image020

b. MBX – Follow the screenshots below and ensure you have the below configured

i. Check: Media Termination Point Required

ii. UnCheck: PSTN Access

iii. Check: Redirecting Diversion Header Delivery – Inbound

iv. Check: Redirecting Diversion Header Delivery – Outbound

v. SIP Information:

1. Line 1 enter the FQDN uexchange.contoso.com of the Exchange Server in the destination address field and port 5062

2. Line 2 enter the FQDN uexchange.contoso.com of the Exchange Server in the destination address field and port 5065

3. Line 3 enter the FQDN uexchange.contoso.com of the Exchange Server in the destination address field and port 5067

vi. Click Save

clip_image022

clip_image023

clip_image024

clip_image026

Create a SIP Route Pattern

1. From the menu Select: Call Routing -> SIP Route Pattern

2. Click Add New

3. Enter following information for your Exchange 2013 Server

a. Pattern Usage: Domain Routing

b. IPV4 Pattern: ucexchange.contoso.com

c. Route Partition: select the appropriate partition to route the call

d. SIP Trunk/Route List: Select ucexchange.contoso.com from the drop down list

4. Click Save

clip_image027

Create a route patterns for the VM DID Pilot number Subscriber Access

1. From the menu Select: Call Routing -> Route Pattern

2. Click Add New

3. Enter following information for your Pilot number

a. Route Pattern: 232700X

b. Route Partition: select the appropriate partition to route the call

c. Gateway/Route List: Select your CAS SIP TRUNK from the drop down list

4. Click Save

clip_image029

clip_image031

Create a Voice Mail Pilot Number

1. From the menu Select: Advanced features -> Voicemail -> Voicemail pilot

2. Click Add New

3. Voicemail Pilot Number : 2327001

4. Check: Make this the default Voice mail Pilot for the system

5. Click Save

clip_image032

Create a Voice Mail Profile

1. From the menu Select: Advanced features -> Voicemail -> Voicemail profile

2. Click Add New

3. Enter the Name: Default

4. Select the voicemail Pilot number: 2327001

5. Check: Make this the default Voice Mail Profile for the System

clip_image033

Exchange 2013 Configuration

Log into Exchange 2013 by browsing to https://ucexchange.contoso.com/ecp

Create a UM IP Gateway

1. From the left hand menu you Select: Unified messaging

2. Click -> UM IP Gateways

a. GW 1

i. Click the +

ii. Enter the name CUCMIPGW

iii. Enter the IP Address x.x.x.x

iv. Click Save

clip_image034

Create a Dial Plan

1. From the left hand menu you Select: Unified messaging

2. Click UM Dial Plans

3. Click +

4. Provide the Name CUCM

5. Extension length: 7

6. Dial Plan type: Telephone extension

7. VoIP security Mode: Unsecured

8. Audio Language: English

9. Country/Region Code: 1

10. Click Save

11. Double click the CUCM UM Dial Plan to modify the configuration

clip_image036

a. Click Configure

clip_image038

i. Click Outlook Voice Access

 clip_image040

1. Outlook Voice Access Number Enter: 2327001

ii. Click Dialing Rules

clip_image042

1. Click + to add a dialing rule

a. Dialing Rule Name: All

b. Number Pattern to transform: *

c. Dialed Number: *

d. Click Save

iii. Click Dialing Rule Authorization

clip_image044

1. Click the + and associate the new dialing rule previously created to the In-country/region dialing rule group

iv. Click Transfer & Search

clip_image046

1. Allow callers to search for users by name or alias

a. Select: In the entire organization

v. Click Save

b. Double click the CUCM Default UM Mailbox Policy

clip_image048

i. Click PIN Polices

clip_image050

1. Minimum PIN Length: 4

2. PIN Recyle: 1

3. Check: Allow common Patterns

4. Uncheck:

a. Enfor PIN lifetime

b. Number of sign-in failures before PIN reset

c. Number of sign-in failures before lockout

ii. Click: Dialing Authorization

clip_image052

1. Associate the All authorization group

iii. Click Save

12. UM Hunt Groups

clip_image053

a. Click the +

b. Select CUCMIPGW

c. And Click Save

Exchange 2013 – Lync Configuration

To configure Exchange 2013 UM and Lync integration, follow the steps located here: https://technet.microsoft.com/en-us/library/gg398768(v=ocs.15).aspx

twitterlinkedinmail

6 comments on “How to setup CUCM 10.5 for Exchange 2013 Unified Messaging Voicemail

  1. Nice blog post! Just a little bit of feed back if you dont mind. Its probably worth noting the version of CUCM you used as there’s an identified DNS bug with CUCM 8.5 up to 10.5 with Exchange 2013 UM integration.

    https://tools.cisco.com/quickview/bug/CSCuc74600

    I found in my testing that CUCM 10.5.2.11900-3 has the DNS bug CSCuc74600 which causes media establishment to fail, but when CUCM was patched to 10.5.2.12900-14 integration with UM worked. Essentially CUCM must be configured to use DNS, which a) Is generally unconventional for a CUCM deployment and b) can be problematic as this has to be done from the shell and an outage is also required for the DNS settings to take effect.
    My biggest nag with this configuration though is the lack of cooperation between MSFT and Cisco in providing better support for CUCM Exchange 2013 interoperability. From what i can gather Cisco have made a change in the SIP stack for CUCM 8.5 upwards which now requires all this additional configuration that was not required for Exchange 2007 or 2010 (direct SIP) as well as a reliance on DNS.

    At scale if HA is required this configuration introduces unnecessary complexity with the reliance on DNS, sip route patterns and the additional trunks required for media redirection. Considering how out of date the Exchange Telephony Advisor is it would be really useful if MS provided some clarity on their direction with PBX support for UM as from my point of view it definitely appears not to be an area of interest for them anymore, with more focus and emphasis on Skype for Business/O365 (UM) integration.

  2. Great post!

    I’m very interested in attempting this setup as well. I’m hung up trying to find a way to light the voicemail indicator on a Cisco phone when using Exchange UM as voicemail instead of Unity Connection. Any thoughts on that?

  3. i setup exchange 2016 UM with just 1 sip trunk to port 5060
    the cucm was taking care the 302 redirect with the fqdn on its own.
    i am running cucm 11.0.1a(SU2)
    initially i had the dns ersolution bug (74600) but after the upgrade to SU2 it got solved.

  4. Awesome Write up! A few things I discovered in my configuration that shouldn’t be unique…We have multiple CUCM servers (4 to be exact) an multiple mailbox/cas servers (4 mailbox, 4 cas). I discovered that there is a checkbox on the trunk config “Run on All Active Nodes”, I checked this, I also had to put all 4 of my CUCM servers in Exchange as SIP gateways in order for Exchange to even answer the call.

    I also had to put all 4 CAS servers and all 4 Mailbox servers in the trunk config. That way if we lose our primary site voice mail will still function.

    No on to configure the MWI

Leave a Reply

Your email address will not be published. Required fields are marked *

*