<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
x1 allows you to see BLF status of calling party in
missed/placed/received directories. Personally, this is one of my
favorite features.<br>
<br>
x1 - will be around much longer and get new features including midlets.<br>
x0 - no more feature development.<br>
<br>
/Wes<br>
<br>
Jason Aarons (US) wrote:
<blockquote
cite="mid:C1FE15183DA37645BC0633BC604E44F00707EA77@USNAEXCH.na.didata.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
..shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
..MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Any
benefits if they used 79x1 over 7960 for Speed Dial Presence?
They are about to order more 7960s over 7961s due to costs. I wish
there was
some motivating one-reason issue to get customers to buy 79x1s. I know
the
benefits of 79x1, and would only buy this model myself, but costs are
sometimes
the winner with customers over logic. Can’t we end of life the 7960s
and
make the 7961 same price!<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">
Wes Sisk [<a class="moz-txt-link-freetext" href="mailto:wsisk@cisco.com">mailto:wsisk@cisco.com</a>] <br>
<b>Sent:</b> Monday, October 08, 2007 4:01 PM<br>
<b>To:</b> Jason Aarons (US)<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] 5.1 Speed Dial Presence<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">native. no CUPS required. /wes<br>
<br>
Jason Aarons (US) wrote: <o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">I
think what they want is DSS/BLF, does it require a dedicated
presence server or can CCM 5.1 do this natively?</span><o:p></o:p></p>
<p class="MsoNormal">Cisco Unified CallManager Speed Dial Presence <br>
<br>
Cisco Unified CallManager supports the ability for a speed dial to have
presence capabilities via a busy lamp field (BLF) speed dial. BLF speed
dials
work as both a speed dial and a presence indicator. Only the system
administrator can configure a BLF speed dial; a system user is not
allowed to
configure a BLF speed dial. <br>
<br>
States are: <br>
<br>
Idle <br>
<br>
Busy <br>
<br>
Unknown <br>
<br>
<a moz-do-not-send="true"
href="javascript:newWin('http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guide_chapter09186a008070bc02.html#wp1070507')">http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guide_chapter09186a008070bc02.html#wp1070507</a><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> </span><o:p></o:p></p>
<div>
<div
style="border-style: solid none none; border-color: -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif";">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif";"> Jason
Aarons (US) <br>
<b>Sent:</b> Monday, October 08, 2007 2:05 PM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> 79x0 vs 79x1 (BLF?)</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Customer
has all SCCP 79x0s with CCM 5.1 and are asking for a
button to have “auto dial and appearance”, they have been using the
7940 a week, along with CCMUser and don’t think
AbbrDial/FastDials/Personal Directory meets their needs. Their old
phone had
lots of buttons, etc.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">What
is the CallManager 5.1 feature called where a button can be
both a Shared Line and Speed Dial? I’m trying to find the URL if it
requires a 79x1 or would it work with a 7960.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">What
are the caveats? Can they setup/manage via CCMUser? </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-right: 7.5pt;"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">I’ve
been stuck on 4.1
a long time and recall seeing something about this in 5.x, but can’t
find
the details. I know 4.1 you could have either a shared line or a speed
dial but not both.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-right: 7.5pt;"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"> -jason</span><o:p></o:p></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"> <o:p></o:p></p>
<div class="MsoNormal"
style="margin: 0in 0in 0.0001pt; text-align: center;" align="center">
<hr align="center" size="1" width="100%"></div>
<p><strong>Disclaimer: This e-mail communication and any attachments
may
contain confidential and privileged information and is for use by the
designated
addressee(s) named above only. If you are not the intended addressee,
you are
hereby notified that you have received this communication in error and
that any
use or reproduction of this email or its contents is strictly
prohibited and
may be unlawful. If you have received this communication in error,
please
notify us immediately by replying to this message and deleting it from
your
computer. Thank you. </strong><o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre style="text-align: center;">
<hr align="center" size="4" width="90%">
</pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>cisco-voip mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck..nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre>
</div>
<hr size="1">
<p><strong>Disclaimer:
This e-mail communication and any attachments may contain confidential
and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee,
you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to
this message and deleting it from your computer. Thank you.
</strong></p>
</blockquote>
</body>
</html>