<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;
}
@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.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"
}
LI.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"
}
DIV.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"
}
SPAN.BalloonTextChar {
FONT-FAMILY: "Tahoma","sans-serif"
}
P.pbu1bullet1 {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"
}
LI.pbu1bullet1 {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"
}
DIV.pbu1bullet1 {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"
}
P.pb2body2 {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"
}
LI.pb2body2 {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"
}
DIV.pb2body2 {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"
}
SPAN.EmailStyle21 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"
}
SPAN.EmailStyle22 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"
}
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">Yes.</font></div>
<div dir="ltr"><font face="Tahoma" size="2"></font> </div>
<div dir="ltr"><span class="content">
<p class="pBu1_Bullet1">Prior to Release 6.1 of Unified CM, 900 kbps of bandwidth was required for Intra-Cluster Communications Signaling (ICCS) traffic for 10,000 BHCA between sites that are clustered over the WAN. An additional 644 kbps of bandwidth was required
for database and other intra-cluster communication for every remote server. Thus, a minimum of T1 bandwidth was required in deployments with clustering over the WAN to account for ICCS and additional database traffic between Unified CM servers.
</p>
<a name="wp1060408"></a><a name="wpmkr1060079"></a>
<p class="pBu1_Bullet1">•<img height="2" alt="" src="http://www.cisco.com/en/US/partner/i/templates/blank.gif" width="19" border="0"><strong>For Unified CM 6.1 and later releases, a minimum of 1.544 Mbps (T1) bandwidth is required for Intra-Cluster Communication
Signaling (ICCS) for 10,000 busy hour call attempts (BHCA) between sites that are clustered over the WAN. This is a minimum bandwidth requirement for call control traffic, and it applies to deployments where directory numbers are not shared between sites that
are clustered over the WAN</strong>. The following equation may be used as a guideline to calculate the bandwidth for more than 10,000 BHCA between non-shared directory numbers at a specific delay:
</p>
<p class="pBu1_Bullet1"> </p>
<p class="pBu1_Bullet1">This is the url to the SRND if you want to keep reading on this since it has changed a bit.</p>
<p class="pBu1_Bullet1"><a href="http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/srnd/6x/models.html#wp1044130">http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/srnd/6x/models.html#wp1044130</a></p>
<p class="pBu1_Bullet1"> </p>
<p class="pBu1_Bullet1">Jorge</p>
</span></div>
<div id="divRpF918178" style="DIRECTION: ltr">
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> Jason Aarons (US) [jason.aarons@us.didata.com]<br>
<b>Sent:</b> Friday, March 14, 2008 8:34 PM<br>
<b>To:</b> Jorge L. Rodriguez Aguila; 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.<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'">But didn’t the minimum bandwidth requirement go up to full 1.54Mbps ?</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> 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.</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Cisco “Relaxed” from 40 to 80 on 6.1</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"></span> </p>
<p class="pbu1bullet1">•<span lang="ES"><img id="_x0000_i1026" height="2" alt="http://www.cisco.com/en/US/partner/i/templates/blank.gif" src="cid:image001.png@01C88612.CC3703F0" width="19"></span>Delay
</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" target="_blank"><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. </p>
<p class="MsoNormal"><span lang="ES" 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 Rodríguez Aguila</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">CCNA,CCVP</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Senior Network Consultant</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Netxar Technologies</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">jorge.rodriguez@netxar.com</span></p>
<p class="MsoNormal"><span style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Office 787-765-0058</span></p>
<p class="MsoNormal"><span lang="ES" style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">PCS 787-688-8530</span></p>
<p class="MsoNormal"><span lang="ES" style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><img id="Picture_x0020_1" height="34" alt="netxar" src="cid:image002.png@01C88612.CC3703F0" width="101" border="0"></span></p>
<p class="MsoNormal"><span lang="ES" 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'"></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>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.</span></p>
</div>
</div>
<p class="MsoNormal"><span lang="ES"></span> </p>
<p class="MsoNormal"><span lang="ES" style="FONT-SIZE: 10pt; 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"></span></p>
<div>
<p class="MsoNormal"><span lang="ES"></span> </p>
</div>
</div>
<p></p>
<hr size="1">
<p></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>
</div>
</body>
</html>