<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">It’s not very bad at all. But Unity Connection 8.5+ is a much more full featured
<b>voicemail</b> system, and you get nice single inbox. There are a lot more knobs in Connection to control how stuff works.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Just depends on the needs.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> bill@hitechconnection.net [mailto:bill@hitechconnection.net]
<br>
<b>Sent:</b> Thursday, February 23, 2012 2:14 PM<br>
<b>To:</b> Jason Aarons (AM); Nate VanMaren; Gr<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] CUCM 8.5 integration with Exchange 2010 for Voice mail<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p><span style="font-size:9.0pt;font-family:"Courier New";color:black">So beside these two things why is the Exchange 2010 UM so bad? I am having a hard time from a competitive standpoint convincing someone NOT to dump unity / unity connection and move directly
to Exchange 2010 UM when they have the E-CAL already as part of their enterprise agreement.</span>
<o:p></o:p></p>
<p> <o:p></o:p></p>
<div style="margin-top:3.75pt;margin-bottom:3.75pt">
<p class="MsoNormal"><span style="font-family:"Courier New""><br>
On February 17, 2012 at 5:02 PM Nate VanMaren <<a href="mailto:VanMarenNP@ldschurch.org">VanMarenNP@ldschurch.org</a>> wrote:
<br>
<br>
> Yea there isn’t really “ports” that you have to worry about on the SIP integrations, just max number of calls.
<br>
> <br>
> You will still need a VM pilot and profile, and then a route pattern that points to the sip trunk that is pointed at exchange UM.
<br>
> <br>
> <a href="http://www.agileit.com/Blog/Lists/Posts/Post.aspx?ID=820">http://www.agileit.com/Blog/Lists/Posts/Post.aspx?ID=820</a>
<br>
> <br>
> <a href="http://www.microsoft.com/download/en/details.aspx?id=13591">http://www.microsoft.com/download/en/details.aspx?id=13591</a>
<br>
> <br>
> <br>
> From: Gr <a href="mailto:[mailto:grccie@gmail.com]">[mailto:grccie@gmail.com]</a>
<br>
> Sent: Friday, February 17, 2012 3:00 PM <br>
> To: Jason Aarons (AM); Nate VanMaren <br>
> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a> <br>
> Subject: Re: [cisco-voip] CUCM 8.5 integration with Exchange 2010 for Voice mail
<br>
> <br>
> Thanks Nate, Jason! Valuable information, I will keep this in mind. <br>
> <br>
> Another question is we just create voice mail pilot in cucm and route it to sip trunk and then in exchange 2010 we create voice mail pilot and the actual voice mail ports?
<br>
> <br>
> Thanks, <br>
> GR <br>
> <br>
> <br>
> Sent from my iPhone <br>
> <br>
> On 18/02/2012, at 4:35 AM, "Jason Aarons (AM)" <<a href="mailto:jason.aarons@dimensiondata.com%3cmailto:jason.aarons@dimensiondata.com">jason.aarons@dimensiondata.com<mailto:jason.aarons@dimensiondata.com</a>>> wrote:
<br>
> I think I understand that Exchange 2010 has a crappy sip stack. Good info. <lol>
<br>
> <br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net%3cmailto:cisco-voip-bounces@puck.nether.net">
cisco-voip-bounces@puck.nether.net<mailto:cisco-voip-bounces@puck.nether.net</a>>
<a href="mailto:[mailto:cisco-voip-bounces@puck.nether.net]">[mailto:cisco-voip-bounces@puck.nether.net]</a><<a href="mailto:[mailto:cisco-voip-bounces@puck.nether.net]">mailto:[mailto:cisco-voip-bounces@puck.nether.net]</a>> On Behalf Of Nate VanMaren
<br>
> Sent: Friday, February 17, 2012 11:03 AM <br>
> To: gr11; <a href="mailto:cisco-voip@puck.nether.net%3cmailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net</a>> <br>
> Subject: Re: [cisco-voip] CUCM 8.5 integration with Exchange 2010 for Voice mail
<br>
> <br>
> <br>
> Two things off the top of my head. <br>
> <br>
> <br>
> 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.
<br>
> <br>
> 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.
<br>
> <br>
> 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.
<br>
> <br>
> -Nate <br>
> <br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net%3cmailto:cisco-voip-bounces@puck.nether.net">
cisco-voip-bounces@puck.nether.net<mailto:cisco-voip-bounces@puck.nether.net</a>>
<a href="mailto:[mailto:cisco-voip-bounces@puck.nether.net]">[mailto:cisco-voip-bounces@puck.nether.net]</a><<a href="mailto:[mailto:cisco-voip-bounces@puck.nether.net]">mailto:[mailto:cisco-voip-bounces@puck.nether.net]</a>> On Behalf Of gr11
<br>
> Sent: Thursday, February 16, 2012 5:17 PM <br>
> To: <a href="mailto:cisco-voip@puck.nether.net%3cmailto:cisco-voip@puck.nether.net">
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net</a>> <br>
> Subject: [cisco-voip] CUCM 8.5 integration with Exchange 2010 for Voice mail <br>
> <br>
> Hi List, <br>
> <br>
> 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.
<br>
> <br>
> 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
<br>
> <br>
> Thanks, <br>
> GR <br>
> <br>
> <br>
> 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. <br>
> <br>
> <br>
> <br>
> itevomcid <o:p></o:p></span></p>
</div>
</div>
</body>
</html>