<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=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 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";}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hello,<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'>According to the UCM 6 SRND, all messaging components, including
the Exchange server and Unity server, are to be located on the same LAN. So,
you cannot move the Exchange server to the remote site unless the Unity server
will be at that same site in a unified messaging configuration. <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'>Thanks,<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'>James<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"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Jorge L. Rodriguez Aguila<br>
<b>Sent:</b> Saturday, March 22, 2008 7:46 PM<br>
<b>To:</b> Miller, Steve; cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] SRST Switching to Subscriber Site?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The answer I guess is conditional. For a 100 Users you can keep
a centralized deployment and do SRST. Putting a Callmanager Sub at this
location will require you to Put a larger Pipe between this site and the HQ, as
at least 1 Meg will be needed for ICCS between CCMs. In terms of the
Unity Box, It doesn’t matter where the Mailbox resides as the Unity will pass
the message into the Exchange cluster via the server he is homed to and will
arrive into the mailbox of the person no matter which server he resides in. If
you are indeed thinking about the Sub at the remote site you should keep in
mind that you would still be passing the traffic along to the Unity box in the
Central site unless you put one at the remote site as well, Otherwise if your
Wan Link goes down, you will still have CCM capabilities but your calls routed
to the AA will fail.<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'>Jorge<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"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Miller, Steve<br>
<b>Sent:</b> Friday, March 21, 2008 11:41 AM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> [cisco-voip] SRST Switching to Subscriber Site?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=ES><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span lang=ES style='font-size:10.0pt;font-family:"Arial","sans-serif"'>We
have a site which is changing. They are a remote site, currently
operating as an SRST site, but their Exchange server (currently at the home
office) is going to be moved to the remote location. We have unified
messaging and we currently have A Pub and Sub at our home office and a remote
Sub at another office. Is it mandatory in such circumstances that we install a
Call Manager and Unity box for this third site? They have about 35 users
- and may have as many as 100 in the next couple years. Any suggestions?</span><span
lang=ES><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span lang=ES> <o:p></o:p></span></p>
</div>
<p><strong><span lang=ES>Steve Miller</span></strong><span lang=ES><br>
Telecom Engineer<br>
Dickstein Shapiro LLP<br>
1825 Eye Street NW | Washington, DC 20006<br>
Tel (202) 420-3370| Fax (202) 330-5607<br>
<a href="mailto:MillerS@dicksteinshapiro.com">MillerS@dicksteinshapiro.com</a></span><span
lang=ES style='font-family:"Arial","sans-serif"'> </span><span lang=ES><o:p></o:p></span></p>
<div>
<p class=MsoNormal><span lang=ES> <o:p></o:p></span></p>
</div>
<pre><span lang=ES>--------------------------------------------------------<o:p></o:p></span></pre><pre><span
lang=ES>This e-mail message and any attached files are confidential<o:p></o:p></span></pre><pre><span
lang=ES>and are intended solely for the use of the addressee(s) <o:p></o:p></span></pre><pre><span
lang=ES>named above. This communication may contain material <o:p></o:p></span></pre><pre><span
lang=ES>protected by attorney-client, work product, or other <o:p></o:p></span></pre><pre><span
lang=ES>privileges. If you are not the intended recipient or person <o:p></o:p></span></pre><pre><span
lang=ES>responsible for delivering this confidential communication <o:p></o:p></span></pre><pre><span
lang=ES>to the intended recipient, you have received this <o:p></o:p></span></pre><pre><span
lang=ES>communication in error, and any review, use, dissemination, <o:p></o:p></span></pre><pre><span
lang=ES>forwarding, printing, copying, or other distribution of <o:p></o:p></span></pre><pre><span
lang=ES>this e-mail message and any attached files is strictly <o:p></o:p></span></pre><pre><span
lang=ES>prohibited. Dickstein Shapiro reserves the right to monitor <o:p></o:p></span></pre><pre><span
lang=ES>any communication that is created, received, or sent on its <o:p></o:p></span></pre><pre><span
lang=ES>network. If you have received this confidential <o:p></o:p></span></pre><pre><span
lang=ES>communication in error, please notify the sender <o:p></o:p></span></pre><pre><span
lang=ES>immediately by reply e-mail message and permanently delete <o:p></o:p></span></pre><pre><span
lang=ES>the original message. <o:p></o:p></span></pre><pre><span lang=ES><o:p> </o:p></span></pre><pre><span
lang=ES>To reply to our email administrator directly, send an email <o:p></o:p></span></pre><pre><span
lang=ES>to postmaster@dicksteinshapiro.com<o:p></o:p></span></pre><pre><span
lang=ES><o:p> </o:p></span></pre><pre><span lang=ES>Dickstein Shapiro LLP<o:p></o:p></span></pre><pre><span
lang=ES>http://www.DicksteinShapiro.com<o:p></o:p></span></pre><pre><span
lang=ES><o:p> </o:p></span></pre><pre><span lang=ES>==============================================================================<o:p></o:p></span></pre></div>
</body>
</html>