You can definately achieve this, but you'll have to plan out your dial plan in order to get the right combination of filters to get what you want.

For example, as you see from your example above, the 9.@ route patterns allows everything. By adding a route filter, you only allow or deny access based on matched clauses. Checking the 'block this route pattern' is what I mean by denying.

So, at a minimum, you need one 9.@ route patterns which allows everything and one 9.@ route pattern with a filter that denies something.

The more precise the match will take precedence.

Assuming you want to get rid of all local 10 digit dialing, you can create another 9.@ route pattern with a route filter that has "local area code exists" and block that route pattern. Or you could just add it to the filter you already have. The local area code predicate (that's what I call it) refers to any area code that exists whenever there is no 0 or 1 in front of it. As soon as there is a 1 or 0, then it is an area code, not a local area code.

If you eventually want some local 10 digit dialing, you can just create another route pattern 9.@ with the appropriate filter and make sure to route that pattern. Or you can simplify things by using 9.123xxxxxxx, replacing 123 with your local area code.

Just to throw a wrinkle into things, the SRNDs talk about the 'device/line approach' which basically says you give the device access to all dialing and use 'deny' on the line's calling search space to restrict offnet dialing. This is very important for extension mobility to ensure that the person logging in has the same class of service whereever they go.

Let us know if that helps, if not, post back.

Lelio

Please rate posts if they help.