Pros:
1) CallManager 5 integrated with Exchange 2007 2) CallManager 4.1 & Exchange does work, but with limited functionality such as no MWI, which is a big drawback, but then there is an email notification as an option.
3) Great documentation and support via Microsoft TechNet forums 4) CCM4.1 features that do work:
- Access to Auto Attendant - Call from Phone1 to Phone2 & get Phone2 Voicemail.
- Call from Phone1 to Phone2 & Phone2 gets VM email stating that is has received a missed call/voicemail from Phone1 Cons:
1) Limited functionality & testing with CCM4.1 and Exch07UM; MWI, Call Transfers, & FAX capabilities 2) Limited and lack of support & testing of features that do work with CCM4.1 and Exch07UM 3) Voice quality between CallManager & Exch07UM is questionable, but that could be a result of the development setup involving VMware, etc. QoS is configured and verified.
Bottom Line:
1) Use CCM5 with Exchange 2007 UM in production because of support. Deploying CCM4.1 with Exchange 2007 UM will give you limited support from Microsoft, Cisco and user community.
2) Deploying CCM4.1 in production by only explaining its limitations up-front & at a small scale. I have deployed CCM4 with Exch07 UM for small environments and the solution works great!
CCM & Exchange 2007 UM Install Steps:
Great install docs; reference “CCM Integration Exchange 2007 UM” doc including the CCM4/Exch07UM doc, which has screenshots of its working configuration.
Design & Migration Notes:
1) An environment may have, for example:
- CCM4.1(x), Cisco Unity, Exchange 2003, & Domain Controller (AD)
2) Build the CCM5 server & Exchange 2007 UM/MB/etc in your new environment. Here you would do all necessary testing, etc.
3) Slowly migrate Phone profiles & extensions from CCM4 to CCM5 including moving the users Exchange mailbox from EXCH03 to EXCH07.
4) A SIP or H323 trunk will be required between the two CallManager servers to place calls between the two new environments.
Completed this migration for numerous projects with success.
Issues:
1) The Diversion Header seems to be a big issue if you are using CCM4.1 & CME by most people or if Diversion Delivery is disabled on CCM5. The following issues listed below reflect some of these problems and how to resolve them.
2) When calls go to Voicemail it goes to the subscribers own VM mailbox and not the destination phone VM mailbox:
- To fix this, for CCM4.1: Change the Destination port under the SIP trunk to be 5065 3) If IP phone calls VM or Auto-Attendant, it quickly connects and disconnects:
- Check if the Exchange 2007 UM is enabled and running. Also check if the Dial Plan is configured/applied under the Organization & Server Configuration 4) Auto-Attendant & Voicemail Pilot:
- Define an Auto-Attendant (AA) number; which is like the main greeting; let’s say 5000. Therefore, I would dial 5000 on my IP phone.
- The VM pilot (Voice subscriber) is configured for 5001. Configure a VM pilot number then a VM profile on CCM. Apply that VM profile on the IP phone(s).
5) Phone1 calls Phone2. Phone2 VM email is from itself:
- This is Diversion Header problem. Go to CCM SIP trunk config & change “Calling Party Selection” to “Originator”
Michel Thomatis, CCIE #6778 Network Principal SixNet Consulting Group, LLC www.SixNetConsulting.com
VoIP Integration with Cisco CallManager and Microsoft Exchange - To learn more about this author, visit Michel Thomatis's Website.
Like this article? Share it with your friends
|
|
Michel Thomatis's
Complete
List Of
Technology
Articles
|
|
|
If you enjoyed this article, get Michel Thomatis's Complete List of Technology Articles For FREE!
|
| |
|
|
|
![[Get Copyright Permissions]](http://license.icopyright.net/images/icopy-w.gif){kind=small}
