<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">Dear Issac,<DIV><BR class="khtml-block-placeholder"></DIV><DIV>Makes sense.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>We got asked about moving back to firmware 1.6.7 as well and the official answer from Polycom is "not a problem"! Put the firmware on your server and remove the 2.0 firmware from this server and when the phone reboots it will grab the 1.6.7 firmware and load it on the phone. Polycom says its as easy as that.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>We can surely get 1.6.7 on our ftp site. We haven't done this due to a major server system upgrade we've been working on for our website. The current server we have is a temporary location for this firmware, we have just the necessities on this server as this particular server isn't within our main cluster of servers (there isn't much bandwidth or power here until we move to the new server farm). I'll have one of our techs post this firmware in a little bit here on the temp ftp server.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Good question on the .cfg files. I don't know ... 1.6.7 .cfg files won't work "correctly" with 2.0.1 firmware since the files changed. Not sure about the other way around, I would assume they'd work, but wouldn't recommend it as you may experience stability issues or glitches from the phone not knowing what to do with some the parameters in these newer files. It's always best to use the .cfg files given with the firmware on your phones.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Hope that helps.</DIV><DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>As far 1.6.7 firmware supporting multiple presences (48 i think), maybe I was wrong on that; however, I remember reading the 2.0.1 firmware release notes and they mentioned that feature was fixed within the 2.0 firmware. Maybe they fixed it before that and just never documented it or maybe I misread it. If it works through in 1.6.7, great! Thanks Douglas.</DIV><DIV><BR><DIV> <SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Jessee Holmes</FONT></P><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Atacomm / Ataractic Corporation</FONT></P><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">www.atacomm.com</FONT></P><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">V: 1-877-700-VOIP</FONT></P><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><A href="mailto:jholmes@atacomm.com">jholmes@atacomm.com</A></FONT></P><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Looking for voice over IP products? Visit our VoIP store at <A href="http://voipstore.atacomm.com">http://voipstore.atacomm.com</A>/</FONT></P><BR class="Apple-interchange-newline"></SPAN> </DIV><BR><DIV><DIV>On Oct 11, 2006, at 10:36 AM, Issac Simchayof wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"> <DIV class="Section1"><P class="MsoNormal"><SPAN style="font-size:11.0pt;font-family:" calibri","sans-serif";="" color:#1f497d"="">Jessee,<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"="">The reason for me upgrading to 2.01 is we wanted to add some 430’s to our system which from what I understand have a problem with 1.67, at this point we will just go with more 501’s instead. <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"="">What is the procedure to go back to 1.67? <O:P></O:P></SPAN></P><P class="MsoNormal"><SPAN style="font-size:11.0pt;font-family:" calibri","sans-serif";="" color:#1f497d"="">Will you be adding 1.67 to your FTP site? currently you only have 2.01.<O:P></O:P></SPAN></P><P class="MsoNormal"><SPAN style="font-size:11.0pt;font-family:" calibri","sans-serif";="" color:#1f497d"="">Will the sip.cfg and phone.cfg from 2.01 work on 1.67?<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"="">Thanks,<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"="">Issac<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 #91C0FF 1.0pt;padding:3.0pt 0in 0in 0in"><P class="MsoNormal"><B><SPAN style="font-size:9.0pt;font-family:" segoe="" ui","sans-serif""="">From:</SPAN></B><SPAN style="font-size:9.0pt;font-family:" segoe="" ui","sans-serif""=""> asterisk-users-bounces@lists.digium.com [<A href="mailto:asterisk-users-bounces@lists.digium.com">mailto:asterisk-users-bounces@lists.digium.com</A>] <B>On Behalf Of </B>Jessee J Holmes<BR> <B>Sent:</B> Wednesday, October 11, 2006 10:09 AM<BR> <B>To:</B> Asterisk Users Mailing List - Non-Commercial Discussion<BR> <B>Subject:</B> Re: [asterisk-users] RE: Welcome to the "asterisk-users" mailing list<O:P></O:P></SPAN></P> </DIV> </DIV><P class="MsoNormal"><O:P> </O:P></P><P class="MsoNormal">Most want the 2.0.1 firmware for a few reasons:<O:P></O:P></P> <DIV><P class="MsoNormal"><O:P> </O:P></P> </DIV> <DIV><P class="MsoNormal">A) They have the latest; although, this is a poor reason, it's still a reason people download and use the latest firmware - remember here always, "If it's not broken, DON'T fix it!"<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal"><O:P> </O:P></P> </DIV> <DIV><P class="MsoNormal">B) They are hoping to fix a previous problem they've had in the past (i.e. stability issues - usually caused by other factors besides just firmware)<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal"><O:P> </O:P></P> </DIV> <DIV><P class="MsoNormal">C) They are told to. IF you are needing to talk to a support professional, especially Polycom, you NEED to upgrade to the latest firmware or they simply will not help you (most of the times anyways)<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal"><O:P> </O:P></P> </DIV> <DIV><P class="MsoNormal">These are a few I can think of anyways; and unfortunately, it's going to be a problem sooner or later.<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal"><O:P> </O:P></P> </DIV> <DIV><P class="MsoNormal"><O:P> </O:P></P> </DIV> <DIV><P class="MsoNormal"><O:P> </O:P></P> <DIV><DIV style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><SPAN style="font-size:9.0pt; font-family:" helvetica","sans-serif";color:black"="">Jessee Holmes<O:P></O:P></SPAN></DIV><DIV style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><SPAN style="font-size:9.0pt; font-family:" helvetica","sans-serif";color:black"="">Atacomm / Ataractic Corporation<O:P></O:P></SPAN></DIV><DIV style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><SPAN style="font-size:9.0pt; font-family:" helvetica","sans-serif";color:black"=""><A href="http://www.atacomm.com">www.atacomm.com</A><O:P></O:P></SPAN></DIV><DIV style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><SPAN style="font-size:9.0pt; font-family:" helvetica","sans-serif";color:black"="">V: 1-877-700-VOIP<O:P></O:P></SPAN></DIV><DIV style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><SPAN style="font-size:9.0pt; font-family:" helvetica","sans-serif";color:black"=""><A href="mailto:jholmes@atacomm.com">jholmes@atacomm.com</A><O:P></O:P></SPAN></DIV><DIV style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; min-height: 14px; "><SPAN style="font-size:9.0pt;font-family:" helvetica","sans-serif";color:black"=""><O:P> </O:P></SPAN></DIV><DIV style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><SPAN style="font-size:9.0pt; font-family:" helvetica","sans-serif";color:black"="">Looking for voice over IP products? Visit our VoIP store at <A href="http://voipstore.atacomm.com">http://voipstore.atacomm.com</A>/<O:P></O:P></SPAN></DIV><P class="MsoNormal"><SPAN style="font-size:9.0pt;font-family:" helvetica","sans-serif";="" color:black"=""><BR> <BR> </SPAN><O:P></O:P></P> </DIV><P class="MsoNormal"><O:P> </O:P></P> <DIV> <DIV><P class="MsoNormal">On Oct 10, 2006, at 4:56 PM, Eric ManxPower Wieling wrote:<O:P></O:P></P> </DIV><P class="MsoNormal"><BR> <BR> <O:P></O:P></P> <DIV><P class="MsoNormal">What I don't understand is why people MUST use the 2.0.x firmware.<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal"><O:P> </O:P></P> </DIV> <DIV><P class="MsoNormal">Jessee J Holmes wrote:<O:P></O:P></P> </DIV> <BLOCKQUOTE style="margin-top:5.0pt;margin-bottom:5.0pt"> <DIV><P class="MsoNormal">A few of our technical support staff here at Atacomm are currently working on this issue with Polycom, Digium and one of our customer's (who posted in here earlier this week).<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal">There are some major differences from the 1.x.x firmware and the 2.01 firmware. Obviously, many on here, voip-info.org, and all over the Internet have reported troubles where their presence feature that stops working after they upgrade their Polycom phones to firmware revision 2.0.1 when the phones are configured with an Asterisk system. A couple new things have been added to the .cfg files that MUST now be set in order for presence to work again with an Asterisk system.<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal">In the sip.cfg file:<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal">feature feature.1.name="presence" feature.1.enabled="1"<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal">In the phone[mac].cfg file:<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal"><attendant attendant.uri="user_112@password_112" attendant.reg=""/><O:P></O:P></P> </DIV> <DIV><P class="MsoNormal">However, there are still confirmed problems with this setup (i.e. LEDs not working), which Polycom and ourselves are currently testing in our labs trying to fix. The reasoning for this is Digium doesn't seem to follow the "standards" for presence support and are currently working to change this functionality within Asterisk. Polycom designed their phones, and specifically their firmware, to work with the "standards" (more specifically, the Microsoft LCS - Live Communications Server).<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal">This issue has been reported on multiple instances to Polycom, Digium, and ourselves; but, no real resolution is completed yet. We'll continue working on this issue within our labs and post an official answer when one is available.<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal">Sorry for the bit of bad news, if anyone is willing to contribute working / half working code, we'd be more than happy to look at it and work with Polycom and Digium on getting this fixed for everyone AS<O:P></O:P></P> </DIV> </BLOCKQUOTE> <DIV><P class="MsoNormal">_______________________________________________<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal">--Bandwidth and Colocation provided by Easynews.com --<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal"><O:P> </O:P></P> </DIV> <DIV><P class="MsoNormal">asterisk-users mailing list<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal">To UNSUBSCRIBE or update options visit:<O:P></O:P></P> </DIV> <DIV><P class="MsoNormal"><SPAN class="apple-converted-space"> </SPAN><A href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</A><O:P></O:P></P> </DIV> </DIV><P class="MsoNormal"><O:P> </O:P></P> </DIV> </DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">--Bandwidth and Colocation provided by Easynews.com --</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">asterisk-users mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">To UNSUBSCRIBE or update options visit:</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN class="Apple-converted-space"> </SPAN><A href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</A></DIV> </BLOCKQUOTE></DIV><BR></DIV></DIV></BODY></HTML>