On Thu, May 5, 2011 at 7:02 PM, Mircea Carasel <[email protected]> wrote: > I researched some more about replications and I noticed the following: > 1. During First-Run-Task dial plans configuration files are replicated > (among all others): > authrules.xml, fallbackrules.xml, forwardingrules.xml, mappingrules.xml > When send Profiles is pressed for a selected server those files are not > replicated > My question is: Is this correct - not to replicate dialplans conf files > during sendProfiles? > 2. The way the code looks leads me to the idea that something is missing for > sure: > In ServiceConfiguratorImpl there is a method: > initLocations() - that iterates through locations and calls initLocation() > for every one. At the end it replicates dial plans > during first-run-task it is called initLocations() - so dialplans are > replicated > during sendProfiles it iterates through all selected locations and calls > initLocation() for each - so dialplans are not replicated > I was imaging that send profiles should replicate all for every selected > location, the same as first-run-task > I also noticed that sipxconfig-report-config is not replicated during > send-profiles, but replicated durng first-run-task
I agree with you, the way it appears to be working doesn't sound very useful. I'm sure there's no comments explaining why. Does the code explicitly call out these exceptions, or given the design do you feel it could be an likely mistake. If you have a few minutes to get to the bottom of it, it would be greatly appreciated, I certainly have made assumptions on customer machines that send profiles send all config info. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
