Enterprise CSS and PT plan revised?

Unanswered Question
Oct 20th, 2008

Someone had showed me a new approach last month or so about devising a new strategy for CSS and PTs for enterprise deployments. It was a Cisco document about the recommended approach for Line CSS/PT and Device CSS etc.

You can basically have a couple different approaches. Example:

30 sites

- each site has it's own PT/CSS (island)

- 4 digit extensions

- 3 digit site code

- Translation patterns to/from each "island" (granted, alot of Translations, but less processing used on CUCM if all lines are in the same CSS)

- Unity 7 digit mailboxes

But I saw some document that create a new approach or something that was different.

Anyeone seen this or have other recommendations?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Chris Deren Mon, 10/20/2008 - 11:39

What is your question?

The device/line approach has been around for while, it's nicely described in the CM SRND.

I've been using it on every implemention for the last few years.

CM 7 takes it to next level with Local Route Groups, where you can put all patterns in a gloabl PT and use a global CSS at the device level and have the Device Pool control which Route Group to use. It comes with its own caveats as with this config you can only have one route group per site, etc.

Chris

Actions

This Discussion