<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 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:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Verdana","sans-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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Verdana","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.apple-style-span
{mso-style-name:apple-style-span;}
.MsoChpDefault
{mso-style-type:export-only;}
@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>I’m planning to upgrade my CCM 4.1(3)4d cluster to 4.1(3)5d
in order to resolve this bug: CSCsg83588:<o:p></o:p></p>
<div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;
padding:0in 0in 1.0pt 0in'>
<p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p>
</div>
<p class=MsoNormal><span class=apple-style-span><span style='font-family:Courier'>If
Unity completes a blind transfer too quickly to a consultation leg that is
busy, the Unity port may stay busy in Callmanager and will no longer be able to
process incoming calls. </span></span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:Courier'><o:p> </o:p></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-family:Courier'>If
this happens over and over the result may be that all Unity ports stop being
able to process calls and calls to Unity will get busy tone. </span></span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:Courier'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:Courier'><o:p> </o:p></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-family:Courier'>It
appears that the Callmanager feature layer does not check for this
condition. </span></span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:Courier'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:Courier'><o:p> </o:p></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-family:Courier'>Workaround: </span></span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:Courier'><o:p> </o:p></span></p>
<p class=MsoNormal><span class=apple-style-span><span style='font-family:Courier'>Stop/start
Unity services. This will re-register the Unity ports and clear the
faulty condition. </span></span><span style='font-size:12.0pt;font-family:
"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>This software defect was resolved in software release Cisco
Callmanager 4.1(3) SR 5B<o:p></o:p></p>
<div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;
padding:0in 0in 1.0pt 0in'>
<p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Has anyone seen this defect and/or already upgraded their
CCM to 4.1(3)5d? Any issues? Thanks.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>Rasim
Duric<br>
Network Analyst (CCS)<br>
University of Guelph<br>
Guelph, N1G 2W1, ON<br>
519-824-4120x53146<br>
rduric@uoguelph.ca</span><o:p></o:p></p>
</div>
</body>
</html>