I have a very basic query. What's the difference between appying Calling Search Place on the phone configuration page ( 1st page) & the line configuration page ( 2nd page) ?
Thanks for your kind words! For the question regarding the SRND reference to CCM 4.2, this was only in reference to User Device Profiles and Extension Mobility. The different rules for Device Level vs Line/Device Level CSS's are still applicable.
For your second question, take a close look at your CSS's. Are all the available Partitions (including the Local **non-Toll partition) listed as "Selected" under the International CSS? It seems like this phone that didn't have the CSS set on the Line may have been able to dial International but not dial 9 Local due to the Selected Partitions under International, did you try?
Please compare the CSS settings to one of your working phones.
Hope this helps!
The Key word here is "concatenates", here you go:
If you configure a calling search space both on an IP phone line and on the device (IP phone) itself, Cisco CallManager concatenates the two calling search spaces and places the line calling search space in front of the device calling search space. If the same route pattern appears in two partitions, one contained in the line calling search space and one contained in the device calling search space, then Cisco CallManager selects the route pattern that is listed first in the concatenated list of partitions (in this case, the route pattern that is associated with the line calling search space).
Hope all is well! This is actually a little complicated to try and explain without some visuals. We do know that the Device Level CSS is easier to configure for Single-Site deployments but becomes very complicated and config intensive for Multi-Site deployments. When using the combination of Line/Device (recommended for Multi-Site) a combination of the two CSS levels is used to provide Calling restrictions/routing. Here are some clips along with links to an "in-depth" look;
Classes of Service with the Device CSS - Single-site deployment
With Cisco Unified CallManager, you can define classes of service for IP Telephony users by combining partitions and device calling search spaces with external route patterns, as follows:
â¢Place external route patterns in partitions associated with the destinations they can call. While you could place all route patterns in a single partition, you can achieve more refined call restriction policies by associating the route patterns with partitions according to the destinations they can call. For example, if you place local and international route patterns in the same partition, then all users can reach both local and international destinations, which might not be desirable. Cisco recommends that you group route patterns in partitions according to the reachability policies for the various classes of service.
â¢Configure each calling search space to be able to reach only the partitions associated with its call restriction policy. For example, configure the local calling search space to point to the internal and local partitions, so that users assigned to this calling search space can place only internal and local calls.
â¢Assign these calling search spaces to the phones by configuring them on the Cisco Unified CallManager device pages. In this way, all lines configured on the device automatically receive the same class of service.
With this approach, the device calling search space performs two distinct logical functions:
The calling search space contains specific partitions, which in turn contain specific route patterns that point to specific PSTN gateways through route lists and their associated route groups.
â¢Class of service
By selectively including certain partitions and not others in the device calling search space, you effectively apply calling restrictions to certain groups of users.
As a consequence, when you apply this approach to a multisite deployment with centralized call processing, you have to replicate partitions and calling search spaces for each site because for each site you have to create classes of service and, at the same time, route the PSTN calls out of the local branch gateways
continued on next page .....