There have been some issues identified relating to feature enablement when there is no valid license key.
One of these (Issue 44509) was addressed in SIP 3.1.0. In that case, certain configurations did not work properly as there was an issue with reading in the license on an IP 601 phone. There is still a smaller version of this use case that remains and this relates to the use of https as a provisioning protocol with 'older' model phones e.g. IP 601, 501, etc. If you are not using https for provisioning we should be okay, if we are then we should look into a method of avoiding the issue. Marek -----Original Message----- From: Paul Mossman [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 10, 2008 11:33 AM To: Dutkiewicz, Marek; Joseph Attardi Cc: [EMAIL PROTECTED] Subject: RE: [sipX-dev] Another Polycom question: feature.x.name Marek wrote: > If you do try and enable a feature on a phone that does not > support the feature the phone will simply ignore the attempt > to enable it. And we are depending on this behaviour for two of the Productivity Suite features: "nway-conference" and "call-recording". We have enabled them, and assume that the phones will behave correctly if they don't load an enabling license file, and/or are a model that does not support the feature. -Paul _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
