ā02-15-2013 10:17 AM - edited ā03-16-2019 03:45 PM
Hello,
Currently I am faced with the possibility of needing to integrated CUCM 8.6 with MS Exchange Unified Messaging for voicemail. I am not keen on this idea and I would much rather use Cisco Unity Connection and keep the messaging store and MWI services on the Cisco Linux platform.
However, I may not have a choice unless there are compelling technical arguments against it. Does anyone here have any experience with this kind of integration? Is it easy to do? How reliable is it?
Solved! Go to Solution.
ā02-16-2013 05:42 PM
Hi - I had replied to the similar thread few days back, pasting from there instead of retyping, it may be useful to you:
https://supportforums.cisco.com/message/3855669#3855669
-----------
"The document provided is for CUCM 7. Microsoft officialy supports direct trunk to CUCM 5.1, 6.X, 7.0 and 8.0 (and yes these are exact versions as on technet).
I had done this sometime ago with CUCM 8.5 and exchange 2010 UM and had used third party (NET - Microsoft recommendation) IP gateways for mediation. Microsoft didnot officialy certify CUCM 8.5 for direct SIP Trunk. The reason is, I beleive difference in SIP stack for both Microsoft and Cisco. Although it will work directly as well (which I had labbed at that time) their may be some interoperatability issues.
Since you are looking for CUCM 8.6, I would recommend doing a complete research before going ahead with a direct SIP trunk.
Implementation wise it is simple. On a high level, you will need to build UM servers if required (which you may not have already if not using unified messaging).You will need a SIP Trunk between CUCM and Microsoft UM servers, directly or through compatible device as per design decision. You will point voicemail hunt pilot to the SIP Trunk. Configure dial plan and mailbox policies on UM to point to mailbox servers where actual voicemail will be stored. On exchange side you enable UM for user mailboxes and on CUCM you create a Voice mail profile and assign to users extension. It worked pretty much well other than, when client's exchange servers were underperforming - Voicemail service would also experience slow response.
You can go to Microsoft technet and search for "Telephone system integration with UM" you will find more information on this."
-----------
Technicaly it works ok but the decison to chose one over other is your enviornment specific. In some cases (in my case as well), where you can leverage existing infrastructure instead of significant investment into buying new or in some cases renewing old and obsolete systems is one of the primary drivers for these integrations. Where possible its good idea to stick with one vendor for sake of simplicity and avoiding interoperability issues.
Operationaly since you are hosting voicemail on Exchange UM, troubleshooting may require either both skills (Cisco or Microsoft) or involve two different teams working on it.
Please let us know if this resolves your queries.
Terry
ā02-15-2013 10:22 AM
ā02-15-2013 10:32 AM
Yes, I have read this document but it's for the wrong version of CUCM (I'm on 8.6 and have also recently learned, the hard way, that SIP trunks to ancillary systems have any some problems with DMTF).
I would like some input with respect to people's experience with the integration and if it can even be recommended.
ā02-15-2013 10:48 AM
I have an integration between CUCM 8.6 in my lab with Exchange 2010 Unified Messaging following the standards noted in the document included above. I also have worked with customers running the same as well as Exchange 2007 in production environments for messaging. The main thing is that you have to use G.711 as the CODEC or use transcoding.
Hailey
Please rate helpful posts!
ā02-16-2013 05:42 PM
Hi - I had replied to the similar thread few days back, pasting from there instead of retyping, it may be useful to you:
https://supportforums.cisco.com/message/3855669#3855669
-----------
"The document provided is for CUCM 7. Microsoft officialy supports direct trunk to CUCM 5.1, 6.X, 7.0 and 8.0 (and yes these are exact versions as on technet).
I had done this sometime ago with CUCM 8.5 and exchange 2010 UM and had used third party (NET - Microsoft recommendation) IP gateways for mediation. Microsoft didnot officialy certify CUCM 8.5 for direct SIP Trunk. The reason is, I beleive difference in SIP stack for both Microsoft and Cisco. Although it will work directly as well (which I had labbed at that time) their may be some interoperatability issues.
Since you are looking for CUCM 8.6, I would recommend doing a complete research before going ahead with a direct SIP trunk.
Implementation wise it is simple. On a high level, you will need to build UM servers if required (which you may not have already if not using unified messaging).You will need a SIP Trunk between CUCM and Microsoft UM servers, directly or through compatible device as per design decision. You will point voicemail hunt pilot to the SIP Trunk. Configure dial plan and mailbox policies on UM to point to mailbox servers where actual voicemail will be stored. On exchange side you enable UM for user mailboxes and on CUCM you create a Voice mail profile and assign to users extension. It worked pretty much well other than, when client's exchange servers were underperforming - Voicemail service would also experience slow response.
You can go to Microsoft technet and search for "Telephone system integration with UM" you will find more information on this."
-----------
Technicaly it works ok but the decison to chose one over other is your enviornment specific. In some cases (in my case as well), where you can leverage existing infrastructure instead of significant investment into buying new or in some cases renewing old and obsolete systems is one of the primary drivers for these integrations. Where possible its good idea to stick with one vendor for sake of simplicity and avoiding interoperability issues.
Operationaly since you are hosting voicemail on Exchange UM, troubleshooting may require either both skills (Cisco or Microsoft) or involve two different teams working on it.
Please let us know if this resolves your queries.
Terry
ā02-16-2013 09:52 PM
Terry (+5) As usual excellent post!
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
ā02-16-2013 11:51 PM
Thanks mate for endorsing - appreciate your feedback!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide