On Sat, Apr 9, 2011 at 5:43 PM, George Niculae <[email protected]> wrote:
> On Sat, Apr 9, 2011 at 4:50 PM, Mircea Carasel <[email protected]> wrote: > > > > > > On Fri, Apr 8, 2011 at 10:45 PM, Douglas Hubler <[email protected]> > wrote: > > > > I vote for keeping the details in files, because I think that the admin > can > > look in the files quicker and easier in disaster situations, to find any > > potential error and it doesn't matter if configuration server is up or > down. > > > > Sipxconfig will read details from files and display on the servers page > as > > specified above. > > > > IMO we should keep replication details in the audit logs we already > writing and node states in db (this could include also enabled / > disabled) > I was looking in sipxconfig-audit.log and noticed that there are written only successful replications, failed replications are not reported. We can extend a bit and log also failures there. In addition we can create some sort of parsing mechanism to parse the audit log file and present details for each node in servers page. Nodes state can stay in db as it is now, as you suggest, Thanks, Mircea > > George >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
