<div dir="ltr"><div>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 something inaccessible. On the phones that are "privileged" and allowed to BLF that number you just don't include the translation pattern partition. There are ways to allow it. This should be a user controllable option the same as others are. If you don't want users to be able to control BLF then turn it of, but if you do want to be able to then you should have the option to enable it.<br><br></div>-Adam<br><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 27, 2015 at 2:59 PM, Brian Meade <span dir="ltr"><<a href="mailto:bmeade90@vt.edu" target="_blank">bmeade90@vt.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I've seen a few that had every department in a different partition so we could easily send calls through translation patterns to change calling number info if needed. Definitely not very common though.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 27, 2015 at 3:45 PM, Ryan Ratliff (rratliff) <span dir="ltr"><<a href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
Do many deployments use different partitions for internal DNs?
<div><br>
</div>
<div>Not much more to add except that this isn’t something I see changing unless it becomes a priority for the PMs.</div><span><font color="#888888">
</font></span><div><span><font color="#888888"><br>
<div>-Ryan </div></font></span><div><div>
<br>
<div>
<div>On Mar 26, 2015, at 5:27 PM, Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>> wrote:</div>
<br>
<div>
<div dir="ltr">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?<br>
<div><br>
</div>
<div>That would be like saying: "We need to remove the CFA setting from Self Care Portal because we can't control where they forward to." Or am I missing a key point?</div>
</div>
<br>
<div class="gmail_quote">On Thu, Mar 26, 2015 at 4:06 PM Ryan Ratliff (rratliff) <<a href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">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.
<div><br>
</div>
<div>If you wanted to do your own it would have to be a tool that used AXL to make the update.</div>
<div><br>
<div>-Ryan </div>
<br>
<div></div>
</div>
</div>
<div style="word-wrap:break-word">
<div>
<div>
<div>On Mar 26, 2015, at 4:08 PM, Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>> wrote:</div>
<br>
</div>
</div>
</div>
<div style="word-wrap:break-word">
<div>
<div>
<div>
<div dir="ltr">
<div>All,</div>
<div><br>
</div>
I'm running up against the lack of support for BLF management in SCP:
<div><a href="https://tools.cisco.com/bugsearch/bug/CSCus02109" target="_blank">https://tools.cisco.com/bugsearch/bug/CSCus02109</a><br>
</div>
<div><br>
</div>
<div>Has anyone run into this and come up with a solution which both:</div>
<div><br>
</div>
<div>A) Maintains the BLF+Speed Dial functionality</div>
<div>B) Allows End Users to self manage the BLF+Speed Dial</div>
<div><br>
</div>
<div>Thanks.</div>
</div>
</div>
</div>
</div>
</div>
<div style="word-wrap:break-word">
<div>
<div>
<div>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<br>
</div></div></div>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div></div></div>