[cisco-voip] CCS and Partitions best practices

Mon Apr 11 18:37:47 EDT 2005

Thanks everyone. I just rolled out today six new sites (all in pilot testing phase with no major problems) I settled in the following approach:

All DNs are in PT_Default

4 CSS for DNs

Internal
Local
National 
International

Each site has: 

1 region
1 Device pool 
1 CSS for the devices for 911 and local calling

each device in each branch office gets the CSS for devices 
each dn gets a CSS based on the class of restriction 

I created one additional PT for vm ports and on ccs for vm pilot. Additionally, I created route lists with the gateways in case any gateway is down. I followed your guys recommendation and read 2 cisco books which were awesome, I will definitely recommend them to any new comer to CCM like myself:

Cisco CallManager Best Practices
Cisco IP Telephony : Planning, Design, Implementation, Operation and Optimization. 

LAST QUESTION:

I want to create a number so users can call the centralized VM locally. For example, our pilot number is 5555 and I want to create the number 2222 that gets send to the pilot number 5555. How can I do this and still retain the caller originating caller ID so the call to 5555 does come from 2222 but from the originating number. What I am trying to achieve is having a local DID in each site so users can call a local number from their home phones/cell phones and use the alternate extension on Unity. 

Thanks a bunch. 
Marcello

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

Good start.

I hope you have more then one gateway, right?  I would make 911 it's own partion and route it out the local gateway.

Then I would probably make two more partions.  HQ_DN's and Br_DNs.

HQ_CSS

HQ_911

HQ_DNs

BR_DNs

HQ_LD

HQ_International

HQ_Toll Free

BR_CSS

BR_911

BR_DN

HQ_DN

BR_LD

BR_INTERnational

BR_toll free

That way you can make sure that all 911 calls go out the local PSTN connection.  And if you want all calls to just go out the main PRI the CSS could be the same except for the 911 calls 

I'm getting ready to do toll bypass.  And AAR with it......... Data entry anyone.

Scott

  _____  

From: Marcello Pedersen [mailto:mpedersen at touchbase.us] 
Sent: Friday, April 08, 2005 2:20 PM
To: Voll, Scott; cisco-voip at puck.nether.net
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  <mailto:mpedersen at touchbase.us> 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 
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050411/582a18d2/attachment-0001.html