<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
..shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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;}
/* 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.pbu1bullet1, li.pbu1bullet1, div.pbu1bullet1
{mso-style-name:pbu1_bullet1;
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";}
p.pb2body2, li.pb2body2, div.pb2body2
{mso-style-name:pb2_body2;
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.EmailStyle21
{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'>But didn’t the minimum bandwidth requirement go up to full
1.54Mbps ?<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> Friday, March 14, 2008 4:46 PM<br>
<b>To:</b> Grisham, Tom<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Question: What version of CUCM extends the RTT
window for Wan clustering subscribers.<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'>Cisco “Relaxed” from 40 to 80 on 6.1<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=pbu1bullet1>•<span lang=ES><img width=19 height=2 id="_x0000_i1026"
src="cid:image001.png@01C88612.CC3703F0"
alt="http://www.cisco.com/en/US/partner/i/templates/blank.gif"></span>Delay <o:p></o:p></p>
<p class=pb2body2><a name=wp1059906></a>The maximum one-way delay between any
two Unified CM 6.0 servers should not exceed 20 msec, or
40 msec round-trip time (RTT). <b>Beginning with Cisco Unified CM
Release 6.1, the maximum one-way delay between two Unified CM servers
can be up to 40 msec, or 80 msec round-trip time. Measuring the delay
is covered in </b><b><span lang=ES><a
href="http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/srnd/6x/models.html#wp1044078"><span
lang=EN-US>Delay Testing</span></a></span></b>. Propagation delay between two
sites introduces 6 microseconds per kilometer without any other network
delays being considered. This equates to a theoretical maximum distance of
approximately 3000 km for 20 ms delay or approximately
1860 miles. These distances are provided only as relative guidelines and
in reality will be shorter due to other delay incurred within the network. <o:p></o:p></p>
<p class=MsoNormal><span lang=ES 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 Rodríguez Aguila<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>CCNA,CCVP<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Senior Network Consultant<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Netxar Technologies<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>jorge.rodriguez@netxar.com<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Office 787-765-0058<o:p></o:p></span></p>
<p class=MsoNormal><span lang=ES style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>PCS 787-688-8530<o:p></o:p></span></p>
<p class=MsoNormal><span lang=ES style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><img border=0 width=101 height=34 id="Picture_x0020_1"
src="cid:image002.png@01C88612.CC3703F0" alt=netxar><o:p></o:p></span></p>
<p class=MsoNormal><span lang=ES 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'><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>Grisham, Tom<br>
<b>Sent:</b> Friday, March 14, 2008 4:22 PM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> [cisco-voip] Question: What version of CUCM extends the RTT
window for Wan clustering subscribers.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=ES><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=ES style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Can
anyone share in which version of CUCM that the RTT boundaries will be
"relaxed" or "extended" between subscribers clustered over
the WAN. It is my understanding that the 40ms boundary was to be adjusted
somewhere in the 6.x or 6.1 Linux platforms.</span><span lang=ES><o:p></o:p></span></p>
<div>
<p class=MsoNormal><span lang=ES> <o:p></o:p></span></p>
</div>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY></HTML>