<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Consolas;
}
@page Section1 {margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"
}
PRE {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
SPAN.HTMLPreformattedChar {
FONT-FAMILY: Consolas
}
SPAN.EmailStyle20 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"
}
SPAN.EmailStyle22 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"
}
.MsoChpDefault {
FONT-SIZE: 10pt
}
DIV.Section1 {
}
</style>
<meta content="MSHTML 6.00.6001.18000" name="GENERATOR">
<style title="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body lang="EN-US" vlink="purple" link="blue" ocsi="x">
<div dir="ltr"><font face="Tahoma" color="#000000" size="2">You are Correct;</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><span class="content"> All messaging system infrastructure components must be located on the same highly available LAN as the Cisco Unity server(s) that they service.
</span></div>
<div dir="ltr"><span class="content"><font face="times new roman"></font></span> </div>
<div dir="ltr"><span class="content"><a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/6x/unity.html#wp1044699">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/6x/unity.html#wp1044699</a></span></div>
<div dir="ltr"><span class="content"></span><span class="content"><font face="times new roman"></font></span> </div>
<div dir="ltr"><span class="content"><font face="times new roman">Jorge</font></span></div>
<div dir="ltr"><span class="content"><font face="times new roman"></font></span> </div>
<div id="divRpF949230" style="DIRECTION: ltr">
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> James Buchanan [jbuchanan@ctiusa.com]<br>
<b>Sent:</b> Saturday, March 22, 2008 9:41 PM<br>
<b>To:</b> Jorge L. Rodriguez Aguila; Miller, Steve; cisco-voip@puck.nether.net<br>
<b>Subject:</b> RE: [cisco-voip] SRST Switching to Subscriber Site?<br>
</font><br>
</div>
<div></div>
<div>
<div class="Section1">
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Hello,</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">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.
</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Thanks,</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">James</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"></span> </p>
<div>
<div style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class="MsoNormal"><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</span></b><span style="FONT-SIZE: 10pt; 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?</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">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.</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"></span> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Jorge</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"></span> </p>
<div>
<div style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<p class="MsoNormal"><b><span style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</span></b><span style="FONT-SIZE: 10pt; 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?</span></p>
</div>
</div>
<p class="MsoNormal"><span lang="ES"></span> </p>
<div>
<p class="MsoNormal"><span lang="ES" style="FONT-SIZE: 10pt; 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"></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="ES"></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"></span></p>
<div>
<p class="MsoNormal"><span lang="ES"></span> </p>
</div>
<pre><span lang="ES">--------------------------------------------------------</span></pre>
<pre><span lang="ES">This e-mail message and any attached files are confidential</span></pre>
<pre><span lang="ES">and are intended solely for the use of the addressee(s) </span></pre>
<pre><span lang="ES">named above. This communication may contain material </span></pre>
<pre><span lang="ES">protected by attorney-client, work product, or other </span></pre>
<pre><span lang="ES">privileges. If you are not the intended recipient or person </span></pre>
<pre><span lang="ES">responsible for delivering this confidential communication </span></pre>
<pre><span lang="ES">to the intended recipient, you have received this </span></pre>
<pre><span lang="ES">communication in error, and any review, use, dissemination, </span></pre>
<pre><span lang="ES">forwarding, printing, copying, or other distribution of </span></pre>
<pre><span lang="ES">this e-mail message and any attached files is strictly </span></pre>
<pre><span lang="ES">prohibited. Dickstein Shapiro reserves the right to monitor </span></pre>
<pre><span lang="ES">any communication that is created, received, or sent on its </span></pre>
<pre><span lang="ES">network. If you have received this confidential </span></pre>
<pre><span lang="ES">communication in error, please notify the sender </span></pre>
<pre><span lang="ES">immediately by reply e-mail message and permanently delete </span></pre>
<pre><span lang="ES">the original message. </span></pre>
<pre><span lang="ES"> </span></pre>
<pre><span lang="ES">To reply to our email administrator directly, send an email </span></pre>
<pre><span lang="ES">to postmaster@dicksteinshapiro.com</span></pre>
<pre><span lang="ES"> </span></pre>
<pre><span lang="ES">Dickstein Shapiro LLP</span></pre>
<pre><span lang="ES">http://www.DicksteinShapiro.com</span></pre>
<pre><span lang="ES"> </span></pre>
<pre><span lang="ES">==============================================================================</span></pre>
</div>
</div>
</body>
</html>