Damian Krzeminski ha scritto: > > There is really no reason to phase out any provisioning method. In many > cases TFTP is a perfect solution and it is used to provision a wide range > of network devices. > Provisioning service should be configurable so that admin can switch any > methods off/on but I do not have any plans to allow patches that would > remove provisioning methods. > If we are talking about longer term plans: provisioning service should be > separated from sipXconfig so that it can be run on an independent remote > machine. sipXconfig should communicate with provisioning service pushing > configuration files through REST. The service or services should do what > they do best: serve files. > D. > Hi Damian, this is definitely a relief for my ear.
I'm working on a general file (firmware, language files) deployments solution for Snom. I currently see this limits: - Snoms are not bounded to only http anymore. Provisioning can happen via TFTP, FTP and HTTPS as well. - Snoms will look at option 66 and search for some hard-coded files (like firmwares or language files) in the root dir. If possible I would suggest a couple of improvements: - unify docroot and tftproot to a unique provisioning directory. And deploy the same directory using different protocols. - deploy http files on a root dir; files will be no longer in http://sipx.example.org:8090/phone/profile/docroot/ but in http://sipx.example.org:8090/ Pros are the plug-in won't be bounded anymore to a specific deployment protocol (TFTP,FTP,HTTP,HTTPs). When the phone firmware allows that protocol, it can be used changing probably just some dhcp options. Cons: plug-ins will not carry any details on a specific deployment technology. Is left to the administrator to use TFTP if that one is needed for the phone in use. While this could bring issues I believe it won't be too bad. If I want to use phone X I would always have to learn how to configure dhcp options for that particular model from the wiki. The wiki, other than dhcp options, should tell which deployment protocol is needed. While some configurable switch to enable/disable deployment protocols in sipxconfig would definitely be desiderable, it is already quite simple to disable one or more of them uninstalling the relative RPM. Thanks Alberto _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
