<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:"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: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: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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>We’ve had the same problem with FW version 3.3.1. We’ve noticed that it only happens when the call is terminated through a hunt group. There was some sort of a reINVITE that triggered a weird ring back tone in the middle of the call. Polycom support has acknowledged the issue and suggested to downgrade to 3.2.4, but as you probably know, the structure of the configuration files is different in the pre 3.3.x FW. The next FW version is scheduled to be released in July. We are still trying to come up with a work around. <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><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:#314B98'>Brad Anouar</span></b><b><span style='font-size:11.0pt;font-family:"Verdana","sans-serif";color:#314B98'> </span></b><b><span style='font-size:8.0pt;font-family:"Verdana","sans-serif";color:#454545'> </span></b><span style='font-size:8.0pt;font-family:"Verdana","sans-serif";color:#454545'>| Anywhere (310) 360-2028 | Corporate (800) 942-4700 | <a href="http://www.broadcore.com/"><span style='color:#454545'>www.broadcore.com</span></a></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span 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 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"'> voiceops-bounces@voiceops.org [mailto:voiceops-bounces@voiceops.org] <b>On Behalf Of </b>Pete E<br><b>Sent:</b> Friday, June 03, 2011 10:54 AM<br><b>To:</b> voiceops@voiceops.org<br><b>Subject:</b> [VoiceOps] Polycom ghost ringing<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Back in January there were a couple of posts related to "ghost ringing" on Polycom phones. At the time the workaround seemed to be to downgrade to v3.3.0 (we're on 3.3.1). Looking at the release notes on 3.3.1 it looks like the .0 release was pretty buggy and therefore we'd rather not downgrade to it. Polycom has not acknowledged (to us) that they even know about the problem. Does anyone know if any headway has been made in actually fixing the issue?<o:p></o:p></p></div></div></body></html>