You can use broken translation patterns to stop this. i.e. if you have want
to prevent the general populous from being able to create a BLF to an
executive extension then create a translation pattern for that extension in
the first partition in the general users subscribe CSS that translated to
Subject: Re: [cisco-voip] Self Care Portal + BLF Speed Dials
Thanks Ryan, I see what you're saying. Though I would have to counter with:
isn't that was subscribe calling search spaces are for? Controlling watcher's
visibility to presentities?
That would be like saying: We need to remove the CFA
All,
I'm running up against the lack of support for BLF management in SCP:
https://tools.cisco.com/bugsearch/bug/CSCus02109
Has anyone run into this and come up with a solution which both:
A) Maintains the BLF+Speed Dial functionality
B) Allows End Users to self manage the BLF+Speed Dial
The idea behind BLFs and self care portal is that since it lets the user see
linestate the admin must provision it. It’s a privacy thing for the user on the
BLF destination that originated long before we had Jabber contacts to tell us
what the user is up to.
If you wanted to do your own it
Thanks Ryan, I see what you're saying. Though I would have to counter
with: isn't that was subscribe calling search spaces are for? Controlling
watcher's visibility to presentities?
That would be like saying: We need to remove the CFA setting from Self
Care Portal because we can't control where
