[cisco-voip] CUCM 8.5 integration with Exchange 2010 for Voice mail

[Jason Aarons (AM)]

I think I understand that Exchange 2010 has a crappy sip stack.  Good info. <lol>

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nate VanMaren
Sent: Friday, February 17, 2012 11:03 AM
To: gr11; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 8.5 integration with Exchange 2010 for Voice mail


Two things off the top of my head.


1.        Exchange has a crappy sip stack.  So you have to use a MTP on the SIP trunk because it won't deal with RTP source/destination changes in a session.  Like when someone does a supervised transfer to voicemail.

2.       Exchange has a crappy sip stack.  So if you want correct caller name on the voicemail on call transferred to voicemail, you have to run the transfer through an app that waits for the transferee to complete the transfer to send the call to exchange.

Voicemail preview takes a lot of hardware.  I think our boxes are quad core with 8/16gb of ram and 4-5 calls will max out the CPU.

-Nate

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of gr11
Sent: Thursday, February 16, 2012 5:17 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CUCM 8.5 integration with Exchange 2010 for Voice mail

Hi List,

I am providing the CUCM8.5 integration with exchange 2010 for a customer for their voice mail needs. The customer has an old unity server that will be decommissioned and voice mail functionality will be provided by exchange 2010 UM.

Anyone who has done this before, any pitfalls or things to be aware of? We are going to use a third party gateway for SIP Trunk termination to/from CUCM and exchange

Thanks,
GR


NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.



itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120217/6319ee9f/attachment.html>