Alberto wrote: > Paul Mossman ha scritto: >> I'm going to try and squeeze this into 4.2, under XX-5838: Add >> provisioning of phones with HTTPS and authentication. >> >> Focus will be on the following phones: >> - Bria Professional >> - SNOM >> - LG-Nortel 68xx >> - Nortel IP 12x0 >> - Polycom SoundPoint IP >> >> My plan is to decommission the current SNOM provisioning URL, so >> existing deployments will need to manually reconfigure each phone upon >> upgrade. >> > What are your plan here for Snoms? As you already know Snom use option > dhcp 66 and 67. > Updating the Snom plug-in I found this as a partial limit in what I'd > like to do. > Option 66 is a URL but it cannot contain a path > Option 67 is the settings file name but CAN contain a path > To make it clearer: > Snom will work with this: > 66: http://example.org:8090 > 67: /phone/profile/docroot/{mac}.xml > > but won't work with the following options: > 66: http://example.org:8090/phone/profile/docroot/ > 67: {mac}.xml > > Why would I ever want it in the last way? For a very simple reason. I > found Snom v7 firmware will look for some default settings file in the > url provided in option 66. It usually look for a specific model file and > then for it's own {mac}.xml without specifying it. It will search for > http://example.org:8090/{model}.xml but won't work if option 66 is > http://example.org:8090/phone/profile/docroot/. > > In other words I could make Snoms self provisioning using only option 66 > if it does contain just a root path http://example.org:8090. So I'm > proposing the http service used for provisioning to present generated > file in the http root without the need of the /phone/profile/docroot/ path. > >> The existing FTP and TFTP mechanism will be kept for now, but the plan >> will be to phase them out eventually. >> >> > Well FTP and TFTP are probably not suggested for many deployments but I > would not really like they're eventually phased out. I would prefer to > have some sort of settings in sipxconfig where I can choose what type of > provisioning should be enabled or not. Of course HTTPs could be default > choice, but I'd like to change it to TFTP or HTTP for small deployments. > > What I'm proposing is: unify http and tftp directory in a unique > provisioning directory and add four configurable switch in sipxconfig to > enable/disable tftp, ftp, http, https provisioning of the same unique > directory. More services could be enabled at the same time. This could > provide as well an easy way to tell users where (URLs) the files are > provisioned if one of those is enabled. This would give a lot of > flexibility to the administrator. Snoms actually supports all the above > protocols for provisioning. > > This could eventually solve an issue I found while patching for XX-5861. > File upload does not actually support deployments in http directory. Or > at least is not as simple as it is for phones. > >
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. _______________________________________________ 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/
