line/device CSS methodologies and approaches

Unanswered Question
Apr 16th, 2009

is there a better or best way to approach line/device CSS? The SRND doc of course says one way. Another way someone showed me the other day was interesting.

On the device CSS, allow ALL. (no restrictions) but then on the line, the restrictions are set by css. For example. On the line we allow Long Distance dialing only, no international.

We then create Route Patterns to block INT, but allow patterns for LD, Local, 911, etc.

Granted, there is probably a right ways to do this approach. But I have never done blocking before. I always do Class of Service by CSS/PT.

CSS_LD - (LD, Local, Internal, 911)

CSS_INT - (INT, LD, Local, Internal, 911, etc)

CSS_LD - PT_LD, PT_Local, PT, Internal, etc)

How do most design single site css/pt. Block to restricting dialing, or not including the PT that has the RP for outbound?

cheers!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.

This is a very common (and good) way of doing it. This is the example given in the Cisco Press CallManager Fundamentals book. I usually configure blocking patterns instead of leaving it out and hoping that nobody comes along and save an overly permissive route pattern.

A big benefit to the device+line CSS method is with extension mobility - when a person logs into a phone, their CoS and line follows them but the route group used will come from the physical phone and thus route correctly for the site. This means if you can visit a remote office and sign into a phone, your calls won't still try to go through the gateways at the home office.

Tommer Catlin Fri, 04/17/2009 - 05:32

on the device, is the CSS always set to the highest CSS or unrestricted for extension mobility?

Tommer Catlin Fri, 04/17/2009 - 08:16

Highest ... I meant unrestricted.. the way you summed it is perfect. Unrestricted at the device, restrictive on the line. Build everything else around that model.

Thanks Michael!

iptuser55 Fri, 04/17/2009 - 08:29

the main reason behind user based CSS or Device based CSS is due to how yur dpeloy the Cluster. If you have a cluster with oly one customer, user then eiterh way is ok however if it is a hosted or a multi- tenant install then the Deviced based is best. The Deviced Based CSS reduces the number of partition and CSS required. If yoo wish to reduce it even further look at "flat partitioning"

Chris Deren Fri, 04/17/2009 - 10:56

We at CDW Berbee do this on every one of our engagement (and there is many :-)) This is a very good way to limit the amount of configuration as with 4 classes of restrictions you decrease the amount of CSS and PTs by the factor of 4. Obviously the more sites you have the greater the benefit. With that being said I do this even on deployments with single site as you never know if a customer decides you add more sites, and this approach has some benefits such as native support for EM, etc.

To answer your other question, the CSS applied to the line has precedence over the device CSS, so in case you have 2 exact route patterns the one matched by line CSS (blocking) will be matched first.

The SRND actually has this approach very well documented as well.

HTH,

Chris

Actions

This Discussion