On Sun, Oct 18, 2009 at 8:14 PM, Paul Mossman <[email protected]>wrote:
> > 1. Upgrading Polycom firmware will become more manual that other phones. > Would the inconsistency be too confusing? Would it be too inconvenient? > (Though, a default "all" Phone Group would remove much of the > inconvenience.) > > 2. I don't think sipXecs can (or should) check that you're uploading an > exact match of the firmware version you've selected. > > 3. It is less simple. When a new superadmin sets up the Polycom > firmware on a new system, there will be an increased chance for error. > You'll need to match the version under Device Files with the version > selected under Phones. If there's a mismatch, then Polycoms won't pick > up the firmware. You may not notice. If you do notice, you may not > immediately understand what the problem is. > > 4. Likely there'll be a few Polycom release between the two that we > support in any given sipXecs release. This may seem odd to new users. > Why for example, would we support 3.1.3RevB and 3.2.2, but not > 3.1.3RevC, 3.2.0, and 3.2.1? > > > Thoughts? > My vote for the simplest approach. I know sipX in known for supporting many devices, but at what point does this become convoluted? I would be inclined to simply "warn" the user of legacy issues when a mixed environment is detected, offer some advice such as grouping, and move on. Frankly, I'm impressed Polycom has been able to support so many phones up to this point with a single firmware release. my $.02
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
