I think there are several people on this list who have volunteered to take a section of the code and work on it.
On Thu, Mar 22, 2012 at 11:25 PM, Todd Hodgen <[email protected]> wrote: > There was a call out for this several months ago if you recall. I've got > a > developer working on this now, with first code being delivered end of > month, > or mid April Douglas - this is Raju, as we discussed at Colab. > > I've committed to paying for this development work, but would gladly accept > help from others in paying for it. Donations can be made to Sipfoundry and > noted as being for the Polycom Firmware work. > > The primary work required here is plugins for 3.3+ firmware. BTW, I've > researched and the only difference between 3.3 and 4.0.1 is the inclusion > of > the VVX500 phones. There really is no reason to work on 3.3 firmware, it > should be skipped and developed under 4.0.1 in my opinion. IN fact, it > should be developed on 4.0.2 which will be released end of month, as there > is a MOH bug that affects phones used with sipXecs. I have an approved > beta > test phone from Polycom to test the beta software when it is released. A > VVX500 was provided by my company to the Developers for being able to > evaluate and test this firmware for now and future releases. > > I think we are underway on this project already. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Douglas Hubler > Sent: Thursday, March 22, 2012 7:29 AM > To: sipXecs developer discussions > Subject: Re: [sipx-dev] Polycom firmware 3.4 (latest) and invitation for > supporting it > > On Thu, Mar 22, 2012 at 9:12 AM, Tony Graziano > <[email protected]> wrote: > > I'd like to schedule a work session online to break the polycom > > configuration before/after parameters up into "sections". Will will > > take an assignment as would anyone else willing to participate. With > > that done, maybe we can schedule a second session with some dev help > > to make the code available and get some guidance to change the > > parameters so the devs dont have to do all the heavy lifting. > > For 2nd session, I volunteer to help make "code available" *if* this > involves sipxecs 4.6. This should mostly be a documentation exercise how > to > iterate thru build/deploy/test cycle for the non-developer types. > _______________________________________________ > 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 Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
