<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Do many deployments use different partitions for internal DNs?
<div class=""><br class="">
</div>
<div class="">Not much more to add except that this isn’t something I see changing unless it becomes a priority for the PMs.</div>
<div class=""><br class="">
<div class="">-Ryan </div>
<br class="">
<div>
<div class="">On Mar 26, 2015, at 5:27 PM, Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com" class="">avholloway+cisco-voip@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">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 class="">
<div class=""><br class="">
</div>
<div class="">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 class="">
<div class="gmail_quote">On Thu, Mar 26, 2015 at 4:06 PM Ryan Ratliff (rratliff) <<a href="mailto:rratliff@cisco.com" class="">rratliff@cisco.com</a>> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word" class="">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 class=""><br class="">
</div>
<div class="">If you wanted to do your own it would have to be a tool that used AXL to make the update.</div>
<div class=""><br class="">
<div class="">-Ryan </div>
<br class="">
<div class=""></div>
</div>
</div>
<div style="word-wrap:break-word" class="">
<div class="">
<div class="">
<div class="">On Mar 26, 2015, at 4:08 PM, Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank" class="">avholloway+cisco-voip@gmail.com</a>> wrote:</div>
<br class="">
</div>
</div>
</div>
<div style="word-wrap:break-word" class="">
<div class="">
<div class="">
<div class="">
<div dir="ltr" class="">
<div class="">All,</div>
<div class=""><br class="">
</div>
I'm running up against the lack of support for BLF management in SCP:
<div class=""><a href="https://tools.cisco.com/bugsearch/bug/CSCus02109" target="_blank" class="">https://tools.cisco.com/bugsearch/bug/CSCus02109</a><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Has anyone run into this and come up with a solution which both:</div>
<div class=""><br class="">
</div>
<div class="">A) Maintains the BLF+Speed Dial functionality</div>
<div class="">B) Allows End Users to self manage the BLF+Speed Dial</div>
<div class=""><br class="">
</div>
<div class="">Thanks.</div>
</div>
</div>
</div>
</div>
</div>
<div style="word-wrap:break-word" class="">
<div class="">
<div class="">
<div class="">_______________________________________________<br class="">
cisco-voip mailing list<br class="">
<a href="mailto:cisco-voip@puck.nether.net" target="_blank" class="">cisco-voip@puck.nether.net</a><br class="">
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank" class="">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br class="">
</div>
</div>
<br class="">
</div>
</div>
</blockquote>
</div>
</div>
</div>
<br class="">
</div>
</body>
</html>