Hi Grant,
Here's the clip from the SRND that Chris nicely referenced (+5 Chris) and
the key principle that Chris described (TIE goes to the Line level CSS);
If the same route pattern appears in two partitions, one contained in the line's calling search space and one contained in the device's calling search space, then according to the r ules described in the section on
Partitions, Unified CM selects the route pattern listed first in the concatenated list of partitions (in this case, the route pattern associated with the line's calling search space).
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/dialplan.html#wp1044321
Guidelines for the Line/Device Approach
Consider the following guidelines when using the line/device approach:
•
For this approach to work, the blocked patterns configured within the line calling search space must be at least as specific as the route patterns configured within the device calling search space. Wherever possible, Cisco recommends that you configure the blocked patterns as more specific than the routed ones, to avoid any possibility of error. Use extra care when dealing with the @ wildcard because the patterns defined within it are very specific.
•AAR is triggered when on-net DNs are dialed. Access to these DNs can be controlled by the same processes described previously. AAR uses a different calling search space for rerouted calls. In most cases, the AAR calling search space can be the same as the site-specific, unrestricted device calling search space because it can never be dialed directly by end users.
•Refer to the section on Call-Forward Calling Search Spaces, for guidance on using the line/device approach for Call Forward All actions.
From:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/dialplan.html#wp1150997
Cheers!
Rob
"Talk about a dream
Try to make it real"
- Springsteen
