Hi all, I'd like to kick off the discussion on XCF-2736: Enable Polycom Logs and User Preferences store capability (ftp).
Currently, as ftp server does not allow "write" permission on ftp server, so it prevents Polycom phone from uploading its logs and locally configured user preferences ( stored in <MAC>-phone.cfg). This feature request is to add support to allow Polycom phone to upload its logs and locally configured user preferences. Some backgroud information on the user preferences. Locally configured user preferences are saved in <MAC>-phone.cfg, and uploaded to ftp server. As described in http://list.sipfoundry.org/archive/sipx-dev/msg16028.html , locally configured user prefrerences are considered as "override" parameters, and that means they have precedence over the configuration file contents, and are saved in the local cache and will survive between phone reboots. To allow polycom to upload data( logs/user preferences), I am proposing to add a sub directory, polycom_data, with "write" permission under tftproot, to store Polycom logs (and user preferences). Wether to set it with "write+read" or "write" only permission is debatable as each option has its trade-offs, security vs usability. 1) with "write+read" permission, it will allow Polycom to upload and download logs and user preferences (<MAC>-phone.cfg). Advantage: This will allow to address the problem described in http://list.sipfoundry.org/archive/sipx-dev/msg16028.html programmly by sipXconfig generating a blank <MAC>-phone.cfg to override the out-of-date local settings of user preferences when a phone is moved from one sipX system to another one. Disadvantage: This will lead some security issue. As Scott commented in an offline discussion, "the phones may (will) write security-sensitive information into those files, and with those permissions they'd be public. And _I_ can write the User Prefs for _your_ phone". 2) with "write" only permission, it will only allow Polycom to upload logs. Note: without allowing "read" permission, there I no need to upload user preferences (<MAC>-phone.cfg). Advantage: This will address the security issue exposed by option 1). Disadvantage: User have to manually address the issue described in http://list.sipfoundry.org/archive/sipx-dev/msg16028.html when phones are moved between different sipX systems, or phones are swapped. Personally, I will vote for option 2, because moving phones between different sipX systems or changing phones does not happen so often, and good thing is that there is a workaround for that, but I'd like to reach a consensus <http://www.google.ca/search?hl=en&sa=X&oi=spell&resnum=1&ct=result&cd=1 &q=consensus&spell=1> in the community before I start to implement it. The other aspect is quota enforcement. We do not want Polycom logs/data eat up all the disk space. Therefore, we need to enforce quota on the directory, polycom_data. However, not sure quota support is available on all the Linux distributions we support? What options do we have in terms of quota control? Or it has to be done as part of ISO build? Can anyone knows this topic better can comment on this? I believe this can be independent of the changes above for creating a folder and related changes around that, so I will open a separate JIRA issue to track quota control. Thanks in advance! Huijun
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
