I have been using the line/device dial plan for some time now and am wanting to move fully to the Cisco recommended globalized dial plan. I have most of this in place already with the e164 dialing and calling party translations etc. The one part I am missing is the CSS.
Do I now just put the "allowed" partitions in the line CSS below the "blocked" partitions, remove the device level CSS and leave it at that?
In the SRND though there is the following:
"When using the +E.164 dial plan approach explained in the chapter on Dial Plan, all PSTN route patterns are accessible by the line CSS"
which seems to me to say that you no longer need to use the device level CSS.
To add to this, from SRND 12.X -
The main architectural approach used to attain this globalization can be summarized as follows:
Now, when you define CSS at both line and device, the line CSS take precedence (it's more like a concatenation of both CSS partitions). I would always want to have any restriction partitions to be at the line level so that the calls are not allowed in the first place. Allowed partitions go at the Device CSS. This is the line/device approach and should not matter if I have globalisation or not.
Now, you could globalise and route through the RP itself at the same time skipping the TP all together. If you don't have any block patterns, then you can use either line or device CSS (line CSS would be correct since it is closest to the source).
I found what I was looking for. I knew I had read it somewhere. From SRND 12:
"As described in the chapter on Dial Plan, the line/device approach has some specific issues, and creating a +E-164 dial plan based on the line/device approach is not recommended. The recommended approach for +E.164 dial plans is to combine class of service selection and dialing normalization on the line CSS and use the Local Route Group feature to address the requirement for site-specific egress gateway selection. In this approach the device CSS on the phone is not used at all."
Just found it. Are you setting up this dial plan keeping in mind mobility ? Because the section that you quoted this from is for Device Mobility dial plan considerations. Here is the complete thing and the reason why line/device approach has issues -
In a line/device dial plan approach, these route patterns would be addressed by the device CSS configured on the endpoint. When roaming but not leaving the device mobility group, the calling endpoint’s device CSS is replaced by the Device Mobility CSS configured on the roaming device pool. If fixed egress gateway selection is required for some calls and the route patterns for those calls are addressed by the device CSS, you have to make sure that roaming devices always roam across device mobility groups. This will guarantee that roaming endpoints always use the device CSS configure on the endpoint.
When using the +E.164 dial plan approach explained in the chapter on Dial Plan, all PSTN route patterns are accessible by the line CSS, which is not changed or updated for roaming devices.
I have highlighted the areas that are relevant.
Yes I know that this excerpt is from the Roaming section but it makes reference to the Dial Plan section saying it describes there issues and why you should no longer use the line/device deployment. I agree that I cannot find this in the Dial Plan section but it seems to me that the line/device approach is still deprecated.