<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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;}
span.gmailquote
{mso-style-name:gmail_quote;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
..MsoChpDefault
{mso-style-type:export-only;}
@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]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If it’s by design it would be in the release notes or
documented somewhere, ask the Cisco CSE to show where it’s documented. If
it’s not documented it’s a bug.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> I would give your Cisco AM the case number and have them
escalate, if you don’t have a Cisco AM ask to speak to the manager. I’m
with you, I think it’s a bug and they haven’t removed CFwdAll from
CCMUser. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I’ve found sometimes it takes 2-3 tries to find the right
person at TAC that is informed; when you have thousands of employees (some
outsourced) you sometimes have a problem with knowledge dissemination.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Ted Nugent<br>
<b>Sent:</b> Wednesday, October 10, 2007 1:40 PM<br>
<b>To:</b> Justin Steinberg<br>
<b>Cc:</b> cisco voip list<br>
<b>Subject:</b> Re: [cisco-voip] CM5.13 No More CFwdAll IN CCMUser?? WAD?<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>Thats exactly how it went down for us.. The customer is NOT
happy!<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>TAC is telling me that this was done purposely and that if
we want it back we need to "talk to our account team and file a <span
style='font-size:10.0pt'>PER (Product Enhancement Request). This is not
going to fly, I don;t even know how to have that conversation with my
customers... </span><br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span class=gmailquote>On 10/10/07, <b>Justin Steinberg</b>
<<a href="mailto:jsteinberg@gmail.com">jsteinberg@gmail.com</a>> wrote:</span>
<o:p></o:p></p>
<p class=MsoNormal>I can't believe this would be WAD, this must be a bug.<br>
<br>
In fact, I logged into my 5.1.3 lab box and saw the call fwd settings <br>
there. I then went to the Ent Params and saw that the param 'Show<br>
Call Forwarding' was set to false, which was weird because I just<br>
logged into ccmuser and saw the fwd settings. I changed this param
to <br>
'true' logged out of ccmuser and back in and now, like you, i dont see<br>
the fwd settings. I went back to ent params and set the param back
to<br>
false and still don't see fwd settings in ccmuser.<br>
<br>
<br>
<br>
<br>
<br>
On 10/10/07, Ted Nugent <<a href="mailto:tednugent73@gmail.com">tednugent73@gmail.com</a>>
wrote:<br>
> I upgraded a customer to 5.13 for various bug fixes and now the CFwdALL no<br>
> longer shows in the CCMUser page. I opened a TAC case and I'm being told <br>
> it's a WAD! CFwdAll has been in the CCMUser page for as long as I can<br>
> remember and now it's gone and I'm expected to tell my customers that
Cisco<br>
> decided you no longer need that… I've got many customers that use
this <br>
> religiously and if this is actually a WAD then they're stuck on 5.12 and<br>
> lower? That just doesn't add up?<br>
><br>
><br>
> Wes have you heard anything about this and/or can you shed some light on
it? <br>
> I understand that having all the CFwd options in CCMUser is not the best<br>
> solution but CFwdAll is really the only reason any of my customers use
it…<br>
><br>
><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">https://puck..nether.net/mailman/listinfo/cisco-voip
</a><br>
><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<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></BODY></HTML>