Cisco UCM 7.1 and MS Exchange 2013 UM for Voice Mail

Posted on 2014-01-15
Last Modified: 2014-02-05
We currently have a Cisco 7.1 voice system and it goes to our Exchange 2007 Unified Messaging for voice mail.    We are in the process of deploying Exchange 2013 and I am trying to setup voice mail at a new pilot number to be handled by the Exchange 2013/UM environment.  If I call the voice mail pilot number I am getting a fast busy at this point. When I try to search for docs on this integration I constantly get information on Cisco to Lync integration.  Not Exchange 2013 UM.   Here's what I've added in UCM:

-A SIP Trunk pointing to one of the Exchange 2013 Mailbox servers (all other details same as existing trunk.)
-Voice mail pilot with a new number
-Voice mail profile
-Route patter (1280)

If I use the Cisco Dialed Number Analyzer the call is routed successfully.  So I don't think there' an issue of Calling Search Space or whatever.  I suspect more needs to be done on the Exchange 2013 side.  

Any links or advice appreciated.
Question by:amigan_99
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 4
LVL 20

Expert Comment

by:José Méndez
ID: 39783417
Amigan, would you be willing to attach CM traces so I can help you dissect the SIP communication?

Author Comment

ID: 39783447
I think I have found a good clue.  I ran NMAP on the two mailbox servers and the dag.  Port 5060 for SIP was not available for TCP nor UDP.  The existing working UM server IS listening at that port.  So...what is the mojo that gets Exchange 2013 to listen for SIP at port 5060??
LVL 20

Expert Comment

by:José Méndez
ID: 39783478
Is the engine that listens on port 5060 turned on in Exchange? Did you see any other ports like 5061 in NMAP?
Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.


Author Comment

ID: 39783528
What is the engine that makes exchange listen on port 5060?  TCP port 5061 is likewise not open.  See results:

Discovered open port 139/tcp on

Discovered open port 25/tcp on

Discovered open port 443/tcp on

Discovered open port 135/tcp on

Discovered open port 3389/tcp on

Discovered open port 445/tcp on

Discovered open port 80/tcp on

Discovered open port 593/tcp on

Discovered open port 81/tcp on

Discovered open port 3800/tcp on

Discovered open port 2103/tcp on

Discovered open port 6006/tcp on

Discovered open port 3828/tcp on

Discovered open port 6025/tcp on

Discovered open port 6009/tcp on

Discovered open port 2107/tcp on

Discovered open port 2105/tcp on

Discovered open port 444/tcp on

Discovered open port 1801/tcp on

Discovered open port 6007/tcp on

Discovered open port 808/tcp on

Discovered open port 6001/tcp on

Discovered open port 3801/tcp on

Discovered open port 465/tcp on

Discovered open port 137/udp on

Author Comment

ID: 39783647
LVL 20

Expert Comment

by:José Méndez
ID: 39783664
I am not sure which component could possibly be turned on from the Services Manager in Windows and get the system start listening on port 5060. Microsoft Exchange Unified Messaging Call Router service according to this doc?:
LVL 20

Expert Comment

by:José Méndez
ID: 39783668
Oh, ok, didn't see your reply hahahaha

Author Comment

ID: 39784049
I used netstat -o on the working system and use the PID from that to see if I can find the name of the process that serves up 5060.  And the answer is... MSExchangeUM.  :-)

 TCP     hrk-cucmpub:5060       ESTABLISHED     3840
 TCP     hrk-cucmsub1:5060      ESTABLISHED     3840
 TCP     hrk-cucmpub:5060       ESTABLISHED     3840
 TCP     hrk-cucmsub1:5060      ESTABLISHED     3840 I need to go to the 2013 server and see if this service is running.  If yes then it's either a problem with MSExchangeUM configuration or firewall rules are pooching things.

Accepted Solution

amigan_99 earned 0 total points
ID: 39825363
I found the answer here.  

The net-net is the mailbox servers will listen to 5065/5067 for unsecure and 5066/5068 for TLS is you set UMStartUpMode to "dual".  If you set that to "TCP" then you have UM listening at 5065 or if TLS 5067.  Everything is now working.

Author Closing Comment

ID: 39835097
This is the key information:

SIP (Mailbox server - UM worker process)      

5065 and 5067 for TCP (unsecured). 5066 and 5068 for mutual TLS (secured). This is the case when UMStartupMode is set to Dual. If UMStartUpMode is set to TCP or TLS, ports 5065 and 5066 are used. The default UMStartupMode is TCP.      

Ports can’t be changed.

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
Find out what you should include to make the best professional email signature for your organization.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to:…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question