On Wed, 2010-02-10 at 09:49 -0500, Carolyn Beeton wrote: > > -----Original Message----- > > From: Yang, Huijun AVAYA (CAR:9D30) > > Sent: Wednesday, February 10, 2010 9:42 AM > > To: Beeton, Carolyn AVAYA (CAR:9D60); 'George Niculae'; > > '[email protected]' > > Subject: RE: [sipX-dev] TLS Peer internal user & peer > > identitiesreplicationquestions > > > > > > > > > > - per my understanding - peeridentities.xml will be declared as > > > <osconfig> resource in sipxbridge-process.xml.in and > > > sipXproxy-process.xml.in and > it will not require service restart > > > after replication. I think there is some additional work > > required on > > > Operation side to handle this new > > resource and also to pick up > > > changes on the fly? > > > > > > Ever considering using IMDB option? Besides IMDB, I know > > that on the > > > Operation side, there is a mechanism that be used several > > places that > > > a background process monitors the timestamp of the configuration > > > files, if the file is ever changed, the process will re-parse the > > > configurations and pick up the changes on the fly, which does not > > > require service restart. > > > > > > > > > Huijun > > > > > > > > > > > > At the moment, peeridentities.xml is only parsed on startup > > of sipxbridge. This is not a file that will be changing once > > things are working, so > I don't see much of a problem here. > > > > What if adding new peers onto a system? Without the mechanism > > to take configurations on fly, sipXbridge has to be > > restarted, though in reality, that probably don't happen that often. > > > > Huijun > > > > Yes, someday someone will write a RefreshingFileReader in sipXcommons > for the Java apps to use (or maybe (or almost certainly) there is > already one I'm not aware of?)
More likely than not this will involve adding a new CA cert, which (due to Java limitations) will require a restart anyway. _______________________________________________ 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/
