Paul Mossman wrote: > Hi all, > > As part of XX-6490, I'll need to construct a Polycom 0000000000.cfg > config file. The challenge is that a default version of this file is > included in the Polycom SIP Application zip archive. Activation of a > Polycom device file must not over-write my constructed c, and > inactivation must not remove it. > > I don't know at this point whether my 0000000000.cfg will be static, or > generated at some point. > > In any case, what's the best way to preserve my 0000000000.cfg during > Polycom device file Activate/Inactivate? > > A couple options: > > 1. Simply ensure that 0000000000.cfg is read-only. This currently > causes a PermissionDenied exception that is displayed in the GUI, but > this would be trivial to suppress. > > 2. Allow a list of "exclude" zip file entries to be specified for in > upload.xml, and use this from the "entries" loops in Upload.java > deployZipFile() and undeployZipFile(). But I see that the upload.xml > data is accessed though intermediate FileSettings.java objects, which > are not specific to zip files... >
I prefer 2 to 1. Can you write some more about how auto provisioning would work. 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/
