I am trying to tidy up CallManager as there seems to be alot of stuff
configured in it that is not used.  The data in this cluster is very
cluttered and messy if you will and could be simplified alot in my
opinion.

Things I am trying to clean up for example:

Calling Search Space
Partitions
Translation Patterns
Route Patterns

And so on.

For many things I am able to determine if they are used are not simply
by looking at the dependency records.  However I am not able to do
that for Translation Patterns, at least not that I see.

Any ideas on the best way to handle stuff like this?  The system has
been in place for a few years and locations have come and gone, not to
mention the people who set it up seem to have gone a bit overboard in
the way things were setup.

I am by no means a design or planning expert, but I have been managing
and maintaining a couple of small callmanger implementations for about
5 years now.  I still get confused myself in how everything ties
together to be honest but some how always manage to work it out.  :-)

Any advice, tools / utils, suggestions, warnings, words of wisdom is
all greatly appreciated.

[ Post a follow-up to this message ]

To see if a translation pattern is being used,  use the Dialed Number
Analyzer to make some test calls through CCM, the output of DNA will
show what patterns and translations are being matched.

tm

Tim Medley
Moxie Enterprises
Email: tim.medley@moxieent.com
Phone: (704) 905-4604




On Mar 16, 2007, at 12:40 PM, Dane wrote:

> I am trying to tidy up CallManager as there seems to be alot of stuff
> configured in it that is not used.  The data in this cluster is very
> cluttered and messy if you will and could be simplified alot in my
> opinion.
>
> Things I am trying to clean up for example:
>
> Calling Search Space
> Partitions
> Translation Patterns
> Route Patterns
>
> And so on.
>
> For many things I am able to determine if they are used are not simply
> by looking at the dependency records.  However I am not able to do
> that for Translation Patterns, at least not that I see.
>
> Any ideas on the best way to handle stuff like this?  The system has
> been in place for a few years and locations have come and gone, not to
> mention the people who set it up seem to have gone a bit overboard in
> the way things were setup.
>
> I am by no means a design or planning expert, but I have been managing
> and maintaining a couple of small callmanger implementations for about
> 5 years now.  I still get confused myself in how everything ties
> together to be honest but some how always manage to work it out.  :-)
>
> Any advice, tools / utils, suggestions, warnings, words of wisdom is
> all greatly appreciated.
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

[ Post a follow-up to this message ]

If a Partition shows no CSS dependencies associated then the partition
is not being used right?

I see some partitions that have route patterns listed as a dependency
but no CSS's or anything else for that matter so I have to assume that
the partition must not be used right?

Am I missing anything?



On 3/16/07, Tim Medley <tim.medley@moxieent.com> wrote:
> To see if a translation pattern is being used,  use the Dialed Number
> Analyzer to make some test calls through CCM, the output of DNA will show
> what patterns and translations are being matched.
>
> tm
>
>
> Tim Medley
> Moxie Enterprises
> Email: tim.medley@moxieent.com
> Phone: (704) 905-4604
>
>
>
>
>
> On Mar 16, 2007, at 12:40 PM, Dane wrote:
>
> I am trying to tidy up CallManager as there seems to be alot of stuff
> configured in it that is not used.  The data in this cluster is very
> cluttered and messy if you will and could be simplified alot in my
> opinion.
>
> Things I am trying to clean up for example:
>
> Calling Search Space
> Partitions
> Translation Patterns
> Route Patterns
>
> And so on.
>
> For many things I am able to determine if they are used are not simply
> by looking at the dependency records.  However I am not able to do
> that for Translation Patterns, at least not that I see.
>
> Any ideas on the best way to handle stuff like this?  The system has
> been in place for a few years and locations have come and gone, not to
> mention the people who set it up seem to have gone a bit overboard in
> the way things were setup.
>
> I am by no means a design or planning expert, but I have been managing
> and maintaining a couple of small callmanger implementations for about
> 5 years now.  I still get confused myself in how everything ties
> together to be honest but some how always manage to work it out.  :-)
>
> Any advice, tools / utils, suggestions, warnings, words of wisdom is
> all greatly appreciated.
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>

[ Post a follow-up to this message ]