<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<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
}
</STYLE>
<STYLE title=owaParaStyle>P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>
<META content="MSHTML 6.00.2900.3268" name=GENERATOR></HEAD>
<BODY lang=EN-US vLink=purple link=blue bgColor=#ffffff ocsi="x">
<DIV><FONT face=Arial size=2>Forgot about that...if you can get it to work that
is. I heard it can be difficult and dependant on your carrier.</FONT></DIV>
<DIV> </DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>"Bad grammar makes me [sic]" - Tshirt<BR></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=jorge.rodriguez@netxar.com
href="mailto:jorge.rodriguez@netxar.com">Jorge L. Rodriguez Aguila</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> ; <A
title=jbuchanan@ctiusa.com href="mailto:jbuchanan@ctiusa.com">James
Buchanan</A> ; <A title=MillerS@dicksteinshapiro.com
href="mailto:MillerS@dicksteinshapiro.com">Miller, Steve</A> ; <A
title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Saturday, March 22, 2008 10:38
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [cisco-voip] SRST Switching
to Subscriber Site?</DIV>
<DIV><BR></DIV>
<DIV dir=ltr><FONT face=Tahoma color=#000000 size=2>I guess in this case the
ideal solution would be to have SRST CFNA or CFWB out the PSTN into
the <A href="mailto:Unity@HQ">Unity@HQ</A> for VoiceMail during an SRST
situation. For AA you can have a Tcl Script or have a live operator during the
SRST condition.</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=tahoma size=2>Either that or have the local users in a
CUE integrated via networking to the Unity at the Main Site.</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=tahoma size=2>Jorge</FONT></DIV>
<DIV dir=ltr><FONT face=tahoma size=2></FONT> </DIV>
<DIV id=divRpF429764 style="DIRECTION: ltr">
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Lelio Fulgenzi
[lelio@uoguelph.ca]<BR><B>Sent:</B> Saturday, March 22, 2008 10:36
PM<BR><B>To:</B> Jorge L. Rodriguez Aguila; James Buchanan; Miller, Steve; <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><B>Subject:</B>
Re: [cisco-voip] SRST Switching to Subscriber Site?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>
<DIV><FONT face=Arial size=2>a couple of questions:</FONT></DIV>
<UL>
<LI><FONT face=Arial size=2>does unity support SRST? if so, how about
distributing a small unity server out there. dialing domains would allow the
grouping and it's less likely to be upgraded as frequently as
callmanager.</FONT>
<LI><FONT face=Arial size=2>does unity express support unified messaging
with exchange? if so, go with unity express as your messaging solution (i
know it supports SRST w/ SIP) and unity express and unity can be
networked.</FONT></LI></UL>
<DIV><FONT face=Arial size=2>if it was me, I would do everything i could to
eliminate distributing my subscribers. the hassel of upgrading them and
repairing them would be a nightmare. especially if you don't have onsite
support. the amount spent travelling, buying additional hardware could be
better spent solidifying your WAN connection and/or looking for a
backup.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>there seems to be some pretty good bandwidth on
3G networks now and you can buy 3G interface cards for ISRs. is some QoS you
can policy route only voice traffic when the link goes down.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>that's just me.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph,
Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>"Bad grammar makes me [sic]" - Tshirt<BR></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV style="BACKGROUND: #e4e4e4; FONT: 10pt arial"><B>From:</B> <A
title=jorge.rodriguez@netxar.com
href="mailto:jorge.rodriguez@netxar.com">Jorge L. Rodriguez Aguila</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=jbuchanan@ctiusa.com
href="mailto:jbuchanan@ctiusa.com">James Buchanan</A> ; <A
title=MillerS@dicksteinshapiro.com
href="mailto:MillerS@dicksteinshapiro.com">Miller, Steve</A> ; <A
title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Saturday, March 22, 2008 9:50
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] SRST
Switching to Subscriber Site?</DIV>
<DIV><BR></DIV>
<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"
target=_blank>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; <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><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>
<P></P>
<HR>
<P></P>_______________________________________________<BR>cisco-voip mailing
list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<BR></BLOCKQUOTE></DIV></BLOCKQUOTE></BODY></HTML>