[cisco-voip] CCS and Partitions best practices

Fri Apr 8 18:30:14 EDT 2005

As you can see by the numerous postings, there are several different ways to deploy a dial plan, each with their advantages and disadvantages. What is important is to plan out what your users look like and where you might see some restrictions coming in play. The SRND helps with describing some of the scenarios and technique, i.e. device/line approach vs line approach. You'll definately need a crystal ball to see what the future might look like - and if it works as good as ours, you'll only have to redesign your dialplan once. ;)

-----                                                                -----
Lelio Fulgenzi, B.A.                                  lelio at uoguelph.ca.eh
Network Analyst (CCS)
University of Guelph                             FAX:(519) 767-1060 JNHN
Guelph, Ontario N1G 2W1                          TEL:(519) 824-4120 x56354
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
mob lawyer: your people insulted my brother.
dr. house: what? romano in the parmesan cheese shaker again?
  ----- Original Message ----- 
  From: Marcello Pedersen 
  To: Voll, Scott ; cisco-voip at puck.nether.net 
  Sent: Friday, April 08, 2005 5:19 PM
  Subject: RE: [cisco-voip] CCS and Partitions best practices

  So let say I have 2 sites with centralized CCM. 

  Site A :

  HQ_CCS

  and three partitions 

  BR_911_local_and_toll_free
  BR_Long_Distance
  BR_International

  Site b:

  Branch_CCS

  and three partitions 

  BR_ 911_local_and_toll_free
  BR_Long_Distance
  BR_International

  There shouldn't be a problem with user A calling user B right?

   -----Original Message-----
  From: Voll, Scott [mailto:Scott.Voll at wesd.org]
  Sent: Friday, April 08, 2005 2:07 PM
  To: cisco-voip at puck.nether.net
  Subject: RE: [cisco-voip] CCS and Partitions best practices

    To add to that we have two different CSS in each location.  One for staff so they can call long distance and one for common area phones that can only dial local.  If you're a larger enterprise you might look at doing it by department.  It all comes down to how you want to service people.  I think it's best to keep your options open. More partions more CSS add complexity but they also open up more options.

    Scott

----------------------------------------------------------------------------

    From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
    Sent: Friday, April 08, 2005 1:11 PM
    To: cisco-voip at puck.nether.net
    Subject: Re: [cisco-voip] CCS and Partitions best practices

    There is a fundamental restriction with the number of 'characters' a calling search space can contain in it's partition list - I'm pretty sure that number is 512 characters. That means there is no limit to the number of partitions in a calling search space per se, but the list of partitions, including the semi-colon seperator can not exceed 512 characters.

    That being said, devices of a similar nature/purpose should be grouped together in their own partition, allowing you to control access to those devices. Voicemail is a good example of one where you really don't want people to access the ports directly, you want them to access a pilot and the pilot number is a translation to the first voicemail port which rings busy/noanswer to the next voicemail port. Coincedentally, this structure has changed in 4.0, voicemail ports no longer have a ring busy/noanswer destination. However, this still doesn't change the principle behind 'hiding' the voicemail ports.

    It also depends on the dialplan strategy you take with respect to off-net access. We've taken an approach where the device has access to all offnet patterns and the line's CSS included route patterns that block access.

    Something to remember, is to keep the <none> partition empty. Since by default, the <none> partition is searched, there is no easy way to block a CSS from searching the <none> partition for a DN to match other than explicitly adding route patterns that block it. It is handy to have an emergency number there so a phone, even misconfigured, can still call the emergency number. 

      ----- Original Message ----- 

      From: Marcello Pedersen 

      To: cisco-voip at puck.nether.net 

      Sent: Friday, April 08, 2005 3:59 PM

      Subject: [cisco-voip] CCS and Partitions best practices

      Hey Everyone,

      I am wondering what are the best practices for implanting CCS and partitions. Should each site have its own partition and CCS? How about VM ports should they be in a in its own partition. 

      also can I forward a DN to the VM pilot number so user can access centralized VM from the road?

      Regards,
      Marcello

      ______________________________________________________________________
      This email has been scanned by the MessageLabs Email Security System.
      For more information please visit http://www.messagelabs.com/email 
      ______________________________________________________________________

      _______________________________________________
      cisco-voip mailing list
      cisco-voip at puck.nether.net
      https://puck.nether.net/mailman/listinfo/cisco-voip

    ______________________________________________________________________
    This email has been scanned by the MessageLabs Email Security System.
    For more information please visit http://www.messagelabs.com/email 
    ______________________________________________________________________

  ______________________________________________________________________
  This email has been scanned by the MessageLabs Email Security System.
  For more information please visit http://www.messagelabs.com/email 
  ______________________________________________________________________

------------------------------------------------------------------------------

  _______________________________________________
  cisco-voip mailing list
  cisco-voip at puck.nether.net
  https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050408/a020c7d5/attachment.html