[cisco-voip] Cleaning up CallManager

[Stu Packett]

If you're going to do some clean up, I highly suggest you use CMReports
to document your CallManager system before you made any changes.  This
helped me out one time when we we had to delete a few old voicemail
pilot numbers before we migrated to Unity.  I needed to know what the
old voicemail pilot was setup as, so I just looked through my old report
and made the change necessary.
 
It's a great way to document a 'before and after' setup.

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Tech Guy
Sent: Tuesday, October 03, 2006 8:28 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Cleaning up CallManager


Anyone have any good tips or pointers for cleaning up a CallManager
install?  Let me elaborate.  Just started working for present employer
about 3 months ago.  One of the primary responsibilites is CallManager.
This past weekend I upgraded it from 3.3(5) to 4.1(3) in preparation to
also setup two IPCC servers that have been sitting in boxes here like a
year.
 
One thing I have noticed is that it seems CallManager is setup a bit
more complicated here then it really needs to be.  I am also finding
alot of things that simply aren't being used.  For instance partitions,
if a partition has no dependencies then am I wrong to assume it is not
used and save to remove? 
 
I don't know how consultants do this sort of stuff, what a pain it is to
have to come into pre-existing installations and try to make sense of
everything and clean things up.
 
Ah well any tips or advice let me have it, anything has to be more
helpful then me slowly clicking away in here try to follow things and
see whats what.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061003/22b02950/attachment.html