FWIW, this really should be a sipx-dev discussion (IMO).

The polycom phones will "discard" any parameter they are given that they do
no know how to handle (like EFK).

That being said, I think there was a workaround being suggested by Paul to
allow sipx to "know" the model of a phone and hence, push (or allow the
phone) a legacy version of firmware for just this instance.

On Thu, Jan 7, 2010 at 2:06 PM, Eric Varsanyi <sip...@eljv.com> wrote:

> I got the impression from the polycom release notes that the base config
> files that come with each firmware release have to be used with that
> firmware release, I looked around in the template stuff but I couldn't find
> any obvious way to use different templates for different instances of a
> polycom phone.
>
> How does one do that in 4.2? It looked to me like someone just checked in
> the updated templates (based on the files in the 3.2.2 release zip) in 4.2
> and now 4.2 supports phones with firmware 3.2.2 and 4.0.4 supports phones
> with firmware 3.1.3c (based on the config file templates alone).
>
> Or does it really not matter if 3.2.2 config parameters end up in a 3.1.3c
> phone?
>
> -Eric
>
> On Jan 7, 2010, at 11:59 AM, Paul Mossman wrote:
>
> >
> > This presents a challenge when sipXecs is deployed with a mix of legacy
> > and non-legacy Polycoms.
> >
> > The configuration file generation is actually handled very well now.
>
> _______________________________________________
> sipx-users mailing list sipx-users@list.sipfoundry.org
> 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/
>



-- 
======================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431

Email: tgrazi...@myitdepartment.net

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
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/

Reply via email to