Paul – I don’t have all of the history, but I believe the Polycom Support was created in the day of Pingtel, where there was a strategic relationship. I believe it continued somewhat with Nortel and their relationship. It looks like the early support was created by Douglas, he can chime in with his comments. I believe Paul Mossman did the final work with Nortel. It’s been pretty much on cruise control for the past few released due to the perception of no pressing needs to update things, and priorities elsewhere on the project. Oh course I’m thinking out loud here with my own opinion of things.
Clearly, there are workarounds for the current models with the exception of the VVX500 phones that will work for people needing to deploy phones. I believe the community will get this issue resolved, and a lot more in due course. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, May 03, 2012 8:27 AM To: sipXecs developer discussions Subject: Re: [sipx-dev] Support for 4.0.2+ and beyond firmware for Polycom In the "Polycom Support for 3.3 + and VVX500 and other next gen phones" thread Todd stated the following: > In time, I will start a campaign to begin development of a fund > for members of the community that want this support to get involved in > development of it by assisting in the funding of it. This will be a first > for this project, and hopefully the beginning of more projects like this to > come. Difficult to judge who's right and who's wrong, it is also not important. At least Todd attempted several times to get things started for 3.3 and now 4.0 support for the best phones for SipX. The replies on all attempts has been minimal. I won't be of any help as my Management decided to go full MCST, my SipX days are numbered........ It would be a real pitty if the community can't organise itself to build support for the newer firmware. Who/what/when/how were all the previous models made? Paul From: Tony Graziano <[email protected]> To: sipXecs developer discussions <[email protected]> Date: 30-04-2012 18:05 Subject: Re: [sipx-dev] Support for 4.0.2+ and beyond firmware for Polycom Sent by: [email protected] _____ You stated you had a developer working on new firmware already, asked for contributions to speed it along when I put out a call for volunteers, bluntly, you said it was in progress so everything stopped on this side... On Mon, Apr 30, 2012 at 12:00 PM, Todd Hodgen <[email protected]> wrote: That discussion was had and you effectively stopped it last time. Excuse me? How do I stop a discussion Tony. I guess if you are saying that my input to a discussion has the ability to stop it then I guess that would be accurate. Geez Tony, I know you like to be blunt. But ridiculous fails to accomplish much. On Apr 29, 2012 11:57 PM, "Todd Hodgen" <[email protected]> wrote: The phone group should be able to become the master "container" of the "firmware" used. It could certainly be an option. Yes, it could be an option. I guess it sounds like you are wanting to have a rewrite of what is there today. I’m looking for options to modify what is there. I don’t have an interest personally in rewriting what works today. Explain? 1. Re-writing the sipxconfig field name/values for configuration yes, agreed. That is a minimum requirement for 4.4.x support 2. Containerizing (is that a word) the firmware b phone group to allocate the proper firmware. Agreed, that makes things easy. 3. Adding new feature to new fimrware and sending profiles based on "profile name" instead of mac address (i.e. login/logout of phone via xhtml to get the profile to load, hot reloading of phones without reboot, new features like pin-locking, etc.). Hot loading of phones doesn’t require this change – it work now when the phone simply loads 4.0.2x firware. The rest of these features I don’t have knowledge of – it is an enhancement it seems to the phones. Personally, I’d be happy to move the management of these phones forward with the features sipXecs has today, along with what is incorporated in the new firmware. For example, on my desktop today, I have the ability to move my mouse from Screen 1, to Screen 2, to the screen of the Polycom phone. This requires no rewrite of sipXecs, just the firmware on the phone to support it. The VVX1500 plugin has all of the requirments for video support for that phone, and it will be a part of the VVX500 phone as well. Once the mouse is there, my keyboard is typing directly on the Polycom phone. Enter URI, click on the directory, search by name, etc. Nothing required by sipx for this, just the firmware. You can add lines, remove lines, change extensions, etc. and in many instances it just works, nothing is required for that. You should just load a phone with that firmware and see what it is capable of doing. This is the reason why there should be an involved discussion prior to people starting to make changes to the templates. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Douglas Hubler Sent: Sunday, April 29, 2012 5:22 PM To: sipXecs developer discussions Subject: Re: [sipx-dev] Support for 4.0.2+ and beyond firmware for Polycom On Sat, Apr 28, 2012 at 3:46 AM, Todd Hodgen <[email protected]> wrote: > I’d like to suggest that a new section be added to the Device file > section of the GUI for the Polycom phones. Today, there exists a > section for uploading Firmware (current) and for adding Firmware for > legacy phones. I’d like to propose a temporary section for adding the > 3.3.x versions of Firmware also. I would think controlling firmware version by phone group would be more useful then by phone model. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net <http://myhelp.myitdepartment.net/> Blog: http://blog.myitdepartment.net <http://blog.myitdepartment.net/> _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net <http://myhelp.myitdepartment.net/> Blog: http://blog.myitdepartment.net <http://blog.myitdepartment.net/> _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/ LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net <http://myhelp.myitdepartment.net/> Blog: http://blog.myitdepartment.net <http://blog.myitdepartment.net/> _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net <http://myhelp.myitdepartment.net/> Blog: http://blog.myitdepartment.net <http://blog.myitdepartment.net/> _______________________________________________ sipx-dev mailing list [email protected] List Archive: <http://list.sipfoundry.org/archive/sipx-dev/> http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
