Marek wrote: > 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.
Huijun: In your designer testing of XCF-2728 (Enable Polycom Productivity Suite), did you happen to test a 601? Marek: Can you give more details on the severity of the issue, and which configurations? I understand that one work-around will be to upgrade all 601 sets to 3.1.0 firmware. But if you encounter the issue, how easy is it to recover? > 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. We do not use https, though I think we might like to in the future. Just to confirm, the https problem with 'older' model phones is _not_ addressed in SIP 3.1.0? Thanks. -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
