| Simon, Bill 2006-07-31, 1:11 pm |
| Since the topic has sort-of come up...
We have a number of techs who are in CallManager admin and Unity admin all
day long. Accountability is difficult. MLA helps set up restrictions, but
as others have been pointing out, there's no recordkeeping.
We are trying to set up a system where people log their own changes using a
form -> database but this is only good if people use it. In other words,
it's no good - because people will conveniently forget to use such a system,
especially when it's slowing down their work.
Any thoughts on how to do detailed (but not over-detailed) tracking of
changes made by technicians in the CallManager or Unity admin interfaces?
---
Bill Simon - bills@tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/ <http://tns.its.psu.edu/>
_____
From: Lelio Fulgenzi [mailto:lelio@uoguelph.ca]
Sent: Monday, July 31, 2006 10:18 AM
To: Robert Kulagowski; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] MLA command history?
All I ever found, even after turning debug on, was the URL that the person
visited. Nothing about database changes.
There is a product from Arcana Networks called ManageExpress
<http://www.arcananet.com/products/MeVoIP.asp> that was built for
CallManager express, but I've been told they recently upgraded it for
CallManager compatibilitiy. I have yet to test it out but it looks like it
has what you (we're) looking for.
If you test it out and it works, let us know. ;)
----- Original Message -----
From: Robert <mailto:bob@smalltime.com> Kulagowski
To: cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
Sent: Monday, July 31, 2006 8:53 AM
Subject: Re: [cisco-voip] MLA command history?
> There is an MLA trace file that is a little cryptic but will give you
> a general breadcrumb history for a user. Normally in the
> c:\Program Files\Cisco\Trace\MLA directory if I recall correctly.
I just took a look, and unless there's some debug level that isn't
turned up high enough, the details just aren't there. I was really
hoping for something like "user x: action: delete route pattern 8.090!"
or something similar.
Is this level of detail available? It's difficult to perform a
post-mortem with what's in there now.
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip>
|