CTI Route Points do not use CSS's. You can verify this yourself by changing a working CTI Route Point (Do it in UCCX not CUCM) to use a CSS that you know has no partitions in it, and test a call. I'm confident it will still work.
CTI Ports however do use CSS's, however, in UCCX you cannot configure the line CSS, only the device. It's confusing because the wording in UCCX is "DN Calling Search Space", however, if you look in CUCM, you'll see that it's the device and not the line that got configured.
With that bit cleared up, now you're left with a single CSS to worry about, which can be called something like: UCCX_CSS, and contains in the following order a list of Partitions like:
- Block_Always
- Block_Emergency
- Block_International
- Internal
- Local
- National
- Toll_Free_Numbers
This way you get your general class of control with a single CSS, and the rest of the allowing or denying of numbers can be done in scripting.
E.g., If you have a dial by extension autoattendant and you do not want to transfer calls out to the PSTN, you could do something like:
if (caller_input.startsWith("9"))
true
play prompt (invalid number + try_again)
goto get_caller_input
false
redirect (caller_input)
successful
end
You could also create different CSS's and different port groups that have different class of resitrictions.
E.,g., Your self service IVR that transfers caller to a 3rd party call center, could use CTI Port Group 1 which uses UCCX_National_CSS. Your branch office auto attendant could use CTI Port Group 2 which uses UCCX_Internal_CSS.
Sorry I didn't answer your direct question, but I would just take the documentation as they way it is, unless you can prove it in a lab one way or the other. I do hope the information I gave you is helpful regardless.
Happy designing!
Anthony Holloway
Please use the star ratings to help drive great content to the top of searches.
