[cisco-voip] General design question re: partitions

Erick Bergquist erickbee at gmail.com
Fri Nov 23 10:49:24 EST 2007


It depends, but as far as Voicemail ports. If you have Unity failover
and set up failover in a way the failover server answers calls if a
call is received, then if someone calls one of the numbers on one of
those VM Ports then Unity goes into failover. Not really good. So in
this scenario, partitoning off the VM ports into a partition that
isn't in a CSS works. Then you set a wildcard translation pattern to
cover the VM DN range so if people call a VM port # directly it goes
to the VM Pilot number.

On Nov 23, 2007 9:43 AM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
>
> When we first deployed our system, we were a bit wet behind the ears, so we
> put everything in one partition. That was quickly changed when we realized
> that if we wanted any control over calling we would need to make some
> changes. While we have a handle on the partitions we assign DNs on phones
> to, we've got a number of other partitions which we assign system DNs to.
> Voicemail ports, CTI route patterns, etc all have their own partition.
>
> Assuming we don't have overlapping DNs and all DNs are the same length, is
> it possible to simply have two partitions for system DNs, those that need to
> be dialable and those that shouldn't be dialable? And hope for the best?
> Should we even worry about non-dialable DNs, e.g. voicemail ports? Is it a
> big deal if users can dial voicemail ports directly?
>
> So, my question to the list is: How far have you gone with partitions?
>
> --------------------------------------------------------------------------------
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> "Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo."      WJR
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>


More information about the cisco-voip mailing list