On Fri, 2009-10-23 at 13:55 -0400, Paul Mossman wrote: > Hi all, > > The auto-provision feature currently constructs Polycom config file > content from code, without the use of templates. It's pretty basic > right now, and effectively duplicates template content in sipXconfig. > > I'd like to start using the sipXconfig Polycom templates. I can't find > a good reason to involve the running sipXconfig instance in this. The > current plan will simply be to use Velocity and the templates from > /etc/sipxpbx/polycom/ directly. > > I have a hunch that it may also be useful to re-use a couple sipXconfig > classes. If so, I certainly wouldn't do anything that reads or writes > from the database. > > Any objections and/or guidance? Thanks.
Did you consider the alternative of using the SOAP API to have sipXprovision tell sipXconfig to create the configuration? Whether you touch the database or not, if two components are both writing to the directory from which phones retrieve configurations, then there's a potential for conflicts.... _______________________________________________ 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/
