Exchange 2013 Unified Messaging with Cisco Unified Communication Manager


The below article explains the detail on how to configure Exchange 2013 unified messaging with the Cisco Unified Communication Manager. The scenario considered where the Exchange 2013 Client access server and Exchange 2013 Mailbox Server role are installed in separate server box.

Just have a glance on below technet article if you have not read it.. for better understanding of Exchange Server 2013 Unified Messaging

New for Unified Messaging in Exchange 2013 – http://technet.microsoft.com/en-us/library/jj150545%28v=exchg.150%29.aspx

Understanding Exchange 2013 Voice Architecture – http://technet.microsoft.com/en-us/library/jj150516%28v=exchg.150%29.aspx

UM Protocols, Ports, and Services – http://technet.microsoft.com/en-us/library/aa998265%28v=exchg.150%29.aspx

Protocol

TCP port

SIP (CAS – Microsoft Unified Messaging Call Router service)

5060 (unsecured), 5061 (secured). The service listens on both ports.

SIP (Mailbox server – Microsoft Exchange Unified Messaging service)

5062 (unsecured), 5063 (secured). The service listens on both ports.

SIP (Mailbox server – UM worker process)

5065 and 5067 for TCP (unsecured). 5066 and 5068 for mutual TLS (secured).

Configuration of Exchange Unified Messaging 2013

1.      Creating Unified Messaging Dial Plan

            New-UMDialplan -Name UMDialPlan -NumberofDigits 4

2.      Creating Unified Messaging UM IP Gateways

3.      Configuring UM Hunt Groups

4.      Adding Client Access server to UM dial plan

       Set-UMCallRouterSettings -DialPlans MySIPDialPlan -Server ClientAccessServer -UMStartupMode Dual

5.      Adding Mailbox server to UM dial plan

        Set-UMService -Identity MailboxServer -DialPlans MySIPDialPlan -Status Disabled -UMStartupMode Dual

Note: The UM dial plan should be SIP URI whereas Telephone Extension or E.164 dial plans can’t be associated, but the servers will answer all incoming calls. It prompts error when you try to add “The dial plan can’t be associated with the Client Access server. Only SIP URI dial plans can be associated with Exchange 2013 Client Access servers.”

Ref: http://technet.microsoft.com/en-us/library/aa996399%28v=exchg.150%29.aspx

Setting up Cisco Unified Communication Manager for Exchange Unified Messaging 2013

Note: This setup is for TCP and for not TLS. The below list of configuration plays vital role in Exchange 2013 UM with CUCM.

  • Create trunk for Exchange 2013 CAS Server with port 5060
  • Create trunk for Exchange 2013 Mailbox Server with port 5062 to 5068
  • Create a sip route and select domain routing. Enter the mailbox server FQDN and select the dedicated mailbox server trunk

1.      Create the SIP profile for Exchange:

Goto Device -> Device Settings -> SIP Profile -> Add new

Name: Exchange 2013 SIP Profile
Check: Early Offer support for voice and video calls (insert MTP if needed)

            Click Save.

2.      Create SIP Trunk Security Profile:

Goto System -> Security -> SIP Trunk Security Profile

Name: Exchange 2013 SIP Security Profile

Check: Accept out-of-dialog refer**
Check: Accept unsolicited notification
Check: Accept replaces header

Click Save

3.      Creating SIP Trunk pointing to Exchange 2013 CAS Server.

      You point your voicemail pilot number to this trunk in CUCM

Goto   Device -> Trunk -> Click Add new

Trunk type: SIP Trunk
Device Protocol: SIP
Trunk Service Type: None

Next.

Device Name: Exchange 2013 CAS Trunk
Device Pool: (I use default but it may be different based on you setup)

Check: Media Termination Point Required
UnCheck: PSTN Access

Check: Redirecting Diversion Header Delivery – Inbound
Check: Redirecting Diversion Header Delivery – Outbound

Destinations (Enter the Exchange 2013 CAS Server FQDN with Port 5060 )

CASServer.mail.com 5060

SIP Trunk Security Profile: Exchange 2013 SIP Security Profile

SIP Profile: Exchange 2013 CAS Server SIP Profile

Save and Reset the trunk.

4.      Creating SIP Trunk pointing to Exchange 2013 Mailbox Server.

Goto Device -> Trunk -> Click Add new

Trunk type: SIP Trunk
Device Protocol: SIP
Trunk Service Type: None
Next.

Device Name: Exchange 2013 Mailbox Trunk
Device Pool: (I use default but it may be different based on you setup)

Enable: Media Termination Point Required
Untick: PSTN Access

Destinations (Enter the Exchange 2013 Mailbox Server FQDN with Port 5062 to 5068 )

MBXServer.mail.com 5062
MBXServer.mail.com 5063
MBXServer.mail.com 5064
MBXServer.mail.com 5065
MBXServer.mail.com 5066
MBXServer.mail.com 5067
MBXServer.mail.com 5068

SIP Trunk Security Profile: Exchange 2013 SIP Security Profile

SIP Profile: Exchange 2013 Mailbox Server SIP Profile

Save and Reset the trunk.

5.      Setup the domain routing so when the CAS server redirects the INVITE it knows which trunk to send it too.

Repeat this step for each mailbox server and update the pattern and sip trunk to match each time:

Goto Call Routing -> SIP Route Pattern -> Add New:
Select Domain Routing from the drop down list

IPv4 Pattern: MBXServer.mail.com
SIP Trunk: MBXServer.mail.com

Now the Exchange 2013 CAS redirect to the Exchange 2013 Mailbox Server on looking to the URI domain routing route

Known issue in Cisco Unified Communication Manager

Issue: Call Trace “DNS Query Fail” – “302 Temporarily Moved” message.

Solution: The Cisco unified communication manager will not able to to resolve the FQDN in the SIP route to an IP address, even though it can able to ping the FQDN from the CM server. Inorder to overcome this you need to upgrade the CM to 9.1.2

Reference:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcucumgx/9xcucumg020.html

http://blogs.technet.com/b/abhay/archive/2013/07/16/configuring-exchange-2013-unified-messaging-with-a-pbx-test-lab-setup.aspx

Advertisements

About Raji Subramanian

Nothing great to say about me...Just want to share my knowledge for others that will be useful at any moment of time when they stuck in critical issue....
This entry was posted in Exchange 2013 SP1, Exchange Server 2013 and tagged , , . Bookmark the permalink.

5 Responses to Exchange 2013 Unified Messaging with Cisco Unified Communication Manager

  1. Eric says:

    Hi,

    Since Exchange 2013 does not accept anymore association between a tel extension UMdialplan and a server, Exchange cannot send anymore MWI notifications to PBX, right ? it used to worked with Exchange 2010.

  2. Jeremiah Rutherford says:

    Have you guys seen an issue when you are trying to dial in from PSTN to access VM it requests your mailbox extension twice. This is integrated with CM 10.5.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s