Scott wrote: > Did you consider the alternative of using the SOAP API to > have sipXprovision tell sipXconfig to create the configuration?
Yes, but I ruled it out because auto-provisioning is triggered by the phone's HTTP GET request to the sipXprovision port 8185 servlet. The configuration is returned synchronously, and the phone data is queued for asynchronous provisioning into sipXconfig. I think this is a good thing, and would be lost if there was a runtime dependency on sipXconfig for the configuration content. > 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.... The two components write to the same directory but never to the same file, so I don't think there's an issue. (sipXprovision only ever writes 000000000000.cfg, which sipXconfig does not. Upon auto-provisioning the configuration is returned in the HTTP GET response, not from file content in the TFTP directory.) -Paul [email protected] _______________________________________________ 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/
