<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:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</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=ES-AR link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi all:<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 lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Version 6.1.4 has a bug with Unicast MOH. This functionality does
not work properly.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>CSCta10219 Unicast Music on Hold May Not Play.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>After
you invoke music on hold (MOH) several times, unicast MOH may not play. MOH can
be invoked by using hold, transfer, conference, park, and so on. <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
name="Workaround_-_Option_1"></a><a name=wp990129></a><b><span lang=EN-US
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Workaround - Option
1 <o:p></o:p></span></b></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
name=wp990130></a><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Upgrade
to a version of Cisco Unified Communications Manager that contains a fix for
this issue. <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
name="Workaround_-_Option_2"></a><a name=wp990131></a><b><span lang=EN-US
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Workaround - Option
2 <o:p></o:p></span></b></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
name=wp990132></a><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Configure
the MOH servers to send out multicast MOH and unicast MOH on the same MOH
resources. <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
name=wp990133></a><span lang=ES style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Procedure
<o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span lang=ES
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>
<hr size=2 width="100%" noshade style='color:gray' align=center>
</span></div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
name=wp990134></a><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Step 1
</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><img
width=5 height=2 id="Picture_x0020_2" src="cid:image001.gif@01CA2BB2.61172400"
alt="cid:image004.gif@01CA113A.D33E47D0"></span><span lang=EN-US
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Configure each MOH
audio source ID for multicast. <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
name=wp990135></a><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Step 2
</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><img
width=5 height=2 id="Picture_x0020_3" src="cid:image001.gif@01CA2BB2.61172400"
alt="cid:image004.gif@01CA113A.D33E47D0"></span><span lang=EN-US
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Configure each MOH
server to multicast. <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
name=wp990136></a><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Step 3
</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><img
width=5 height=2 id="Picture_x0020_4" src="cid:image001.gif@01CA2BB2.61172400"
alt="cid:image004.gif@01CA113A.D33E47D0"></span><span lang=EN-US
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Make sure that
Media Resource Groups (if any are defined) do not have multicast enabled. <o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
name=wp990137></a><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Be
aware that no network (router) changes to forward multicast MOH packets are
required if Media Resource Groups (MRG) are not configured to enable multicast
MOH. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><img
width=28 height=25 id="Picture_x0020_5" src="cid:image002.gif@01CA2BB2.61172400"
alt="cid:image005.gif@01CA113A.D33E47D0"></span><span lang=ES style='font-size:
11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span lang=ES
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
name=wp990138></a><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Note
</span></b><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><img
width=1 height=2 id="Picture_x0020_7" src="cid:image003.gif@01CA2BB2.61172400"
alt="cid:image006.gif@01CA113A.D33E47D0"></span></b><b><span lang=EN-US
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>The MOH servers
transmit multicast streams for each MOH source and MOH codec, so network
traffic to the local network may increase. The multicast streams will remain
continuous and run at all times.<br>
<br>
The MOH servers send the multicast streams to the local router; but, if the
rounter is not configured to forward the MOH multicast packets, impact to the
LAN traffic will be minimal. By default, routers do not forward multicast MOH
packets. <o:p></o:p></span></b></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I don’t know if in </span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif"'><a
href="http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=6.1%284%29SU1&mdfid=281023410&sftType=Unified+Communications+Manager+Updates&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unified+Communications+Manager+Version+6.1&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=null&imname=&hybrid=Y&imst=N&lr=Y"><span
lang=EN-US>6.1(4)SU1</span></a></span><span lang=EN-US style='font-size:11.0pt;
font-family:"Calibri","sans-serif"'> version this bug was solved.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Best
regards<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hernan<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US 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>Ed Leatherman<br>
<b>Sent:</b> miércoles, 02 de septiembre de 2009 09:36<br>
<b>To:</b> Wes Sisk<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Call for opinions; 6.1.3 or 6.1.4?<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>If I were specifically going
for a particular fix and nothing else, i would prefer the "minimal
set" to try and minimize the risk of introducing a new bug or problem.
That said, if I had a problem and TAC told me I had to upgrade to 6.1.4, I
wouldn't be upset about it.. just wouldn't be my preference. I would grouse
about it later if I ran into a new bug ;)<br>
<br>
As far as the original post, if it's a new install/upgrade from 4 or 5, I would
probably load 6.1.4. That said, we're on 6.1.3 right now and don't plan on
upgrading any further in that 6.x train, next upgrade will be 7.x most likely
for a time of day routing with unified mobility.<o:p></o:p></p>
<div>
<p class=MsoNormal>On Tue, Sep 1, 2009 at 10:09 AM, Wes Sisk <<a
href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal>IMHO this is very critical. If you come to me for support I
cannot give you a "minimal set" change between where you are and
where the fix is available. You are going to get all of the changes from
6.1.3 to 6.1.4 in addition to any new fix that is tailored to your environment.
I may be a bit biased as my business leads me to expect things to be
broken. To that end it appears prudent to get as close as possible to any
patches that may be necessary.<br>
<br>
I would very much like to hear the positions of others.<br>
<span style='color:#888888'><br>
/Wes</span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
<br>
On Tuesday, September 01, 2009 9:25:24 AM , Lelio Fulgenzi <a
href="mailto:lelio@uoguelph.ca" target="_blank"><lelio@uoguelph.ca></a>
wrote:<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'>Ah, yes, that's another way to look at it. As each dot.dot release
is released, the previous likely gets shelved for development.<br>
<br>
<br>
---<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>
<br>
<br>
----- Original Message -----<br>
From: "Wes Sisk" <a href="mailto:wsisk@cisco.com" target="_blank"><wsisk@cisco.com></a><br>
To: "STEVEN CASPER" <a href="mailto:SCASPER@mtb.com" target="_blank"><SCASPER@mtb.com></a><br>
Cc: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>,
<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a><br>
Sent: Tuesday, September 1, 2009 9:04:59 AM GMT -05:00 US/Canada Eastern<br>
Subject: Re: [cisco-voip] Call for opinions; 6.1.3 or 6.1.4?<br>
<br>
6.1(3) is "done" meaning no more ES will be built for it. If you
upgrade to 6.1.3 and encounter a serious issue Cisco will require you to
upgrade to 6.1.4 or an engineering special of 6.1.4 to get a fix.<br>
<br>
net: 6.1(4) is the "best" place to be currently.<br>
<br>
/Wes<br>
<br>
On Tuesday, September 01, 2009 6:18:50 AM , STEVEN CASPER <a
href="mailto:SCASPER@mtb.com" target="_blank"><SCASPER@mtb.com></a>
wrote:<o:p></o:p></span></p>
<pre><span style='color:black'>I believe 6.1.4 fixes the Denial of Service vulnerabilities recently reported.<o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'> <o:p></o:p></span></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><span
style='color:black'>Lelio Fulgenzi <a href="mailto:lelio@uoguelph.ca"
target="_blank"><lelio@uoguelph.ca></a> 08/31/09 11:25 PM >>><o:p></o:p></span></pre><pre><span
style='color:black'> <o:p></o:p></span></pre></blockquote>
</blockquote>
</blockquote>
<pre><span style='color:black'>Not easy, but necessary. Even taking a look at SEV 1/2 bugs should be enough. Also, my understanding is that ES's are no longer what ES's were in the days of 3.x and 4.x (possibly 5.x). They're not built for individual customers like they used to be, but essentially, they are what service packs used to be. Granted they're not published for some reason. <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>--- <o:p></o:p></span></pre><pre><span
style='color:black'>Lelio Fulgenzi, B.A. <o:p></o:p></span></pre><pre><span
style='color:black'>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 <o:p></o:p></span></pre><pre><span
style='color:black'>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) <o:p></o:p></span></pre><pre><span
style='color:black'>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <o:p></o:p></span></pre><pre><span
style='color:black'>"Bad grammar makes me [sic]" - Tshirt <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span
style='color:black'>----- Original Message ----- <o:p></o:p></span></pre><pre><span
style='color:black'>From: "Brandon Phelps" <a
href="mailto:btphelps@atomicnets.com" target="_blank"><btphelps@atomicnets.com></a> <o:p></o:p></span></pre><pre><span
style='color:black'>To: <a href="mailto:cisco-voip@puck.nether.net"
target="_blank">cisco-voip@puck.nether.net</a> <o:p></o:p></span></pre><pre><span
style='color:black'>Sent: Monday, August 31, 2009 10:00:28 PM GMT -05:00 US/Canada Eastern <o:p></o:p></span></pre><pre><span
style='color:black'>Subject: Re: [cisco-voip] Call for opinions; 6.1.3 or 6.1.4? <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>meh, thats easy to do. Looking more for opinions and anecdotes. <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>Would most people install an ES without having a specific reason for <o:p></o:p></span></pre><pre><span
style='color:black'>doing so? <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>B <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span
style='color:black'>Lelio Fulgenzi wrote: <o:p></o:p></span></pre><pre><span
style='color:black'> <o:p></o:p></span></pre>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><span
style='color:black'>I think you'll hear from Cisco TAC over and over, always use the latest <o:p></o:p></span></pre><pre><span
style='color:black'>version and the latest ES. Nowadays, especially from x.x.3 to x.x.4 it's <o:p></o:p></span></pre><pre><span
style='color:black'>not feature enhancements but bug fixes mostly. Or so we're told. Take a <o:p></o:p></span></pre><pre><span
style='color:black'>look at the bug list, see if there are any that stand out and not work <o:p></o:p></span></pre><pre><span
style='color:black'>for you. <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>--- <o:p></o:p></span></pre><pre><span
style='color:black'>Lelio Fulgenzi, B.A. <o:p></o:p></span></pre><pre><span
style='color:black'>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 <o:p></o:p></span></pre><pre><span
style='color:black'>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) <o:p></o:p></span></pre><pre><span
style='color:black'>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <o:p></o:p></span></pre><pre><span
style='color:black'>"Bad grammar makes me [sic]" - Tshirt <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span
style='color:black'>----- Original Message ----- <o:p></o:p></span></pre><pre><span
style='color:black'>From: "Brandon Phelps" <a
href="mailto:btphelps@atomicnets.com" target="_blank"><btphelps@atomicnets.com></a> <o:p></o:p></span></pre><pre><span
style='color:black'>To: <a href="mailto:cisco-voip@puck.nether.net"
target="_blank">cisco-voip@puck.nether.net</a> <o:p></o:p></span></pre><pre><span
style='color:black'>Sent: Sunday, August 30, 2009 8:35:38 PM GMT -05:00 US/Canada Eastern <o:p></o:p></span></pre><pre><span
style='color:black'>Subject: [cisco-voip] Call for opinions; 6.1.3 or 6.1.4? <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>Which one is more stable? <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>CUCM 6.1.3 or 6.1.4? <o:p></o:p></span></pre><pre><span
style='color:black'>_______________________________________________ <o:p></o:p></span></pre><pre><span
style='color:black'>cisco-voip mailing list <o:p></o:p></span></pre><pre><span
style='color:black'><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a> <o:p></o:p></span></pre><pre><span
style='color:black'><a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a> <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span
style='color:black'>------------------------------------------------------------------------ <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>_______________________________________________ <o:p></o:p></span></pre><pre><span
style='color:black'>cisco-voip mailing list <o:p></o:p></span></pre><pre><span
style='color:black'><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a> <o:p></o:p></span></pre><pre><span
style='color:black'><a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a> <o:p></o:p></span></pre><pre><span
style='color:black'> <o:p></o:p></span></pre></blockquote>
<pre><span style='color:black'>_______________________________________________ <o:p></o:p></span></pre><pre><span
style='color:black'>cisco-voip mailing list <o:p></o:p></span></pre><pre><span
style='color:black'><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a> <o:p></o:p></span></pre><pre><span
style='color:black'><a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a> <o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'>************************************<o:p></o:p></span></pre><pre><span
style='color:black'>This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.<o:p></o:p></span></pre><pre><span
style='color:black'>There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.<o:p></o:p></span></pre><pre><span
style='color:black'>************************************<o:p></o:p></span></pre><pre><span
style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span
style='color:black'>_______________________________________________<o:p></o:p></span></pre><pre><span
style='color:black'>cisco-voip mailing list<o:p></o:p></span></pre><pre><span
style='color:black'><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><o:p></o:p></span></pre><pre><span
style='color:black'><a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></pre><pre><span
style='color:black'> <o:p></o:p></span></pre>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<br clear=all>
<br>
-- <br>
Ed Leatherman<o:p></o:p></p>
</div>
</body>
</html>