<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="&#1;" 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;}
@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";
        mso-believe-normal-left:yes;}
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";}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle21
        {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 mso 9]>
<style>
p.MsoNormal
        {margin-left:3.0pt;}
</style>
<![endif]><!--[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 style='margin-left:3.0pt;margin-top:
3.0pt;margin-right:3.0pt;margin-bottom:.75pt'>

<div class=Section1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>What happens when you are running in this configuration &nbsp;is that
the auto negotiating end will possibly negotiate to 100/half. This
configuration is a really bad idea. <o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><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"'> STEVEN CASPER
[mailto:SCASPER@mtb.com] <br>
<b>Sent:</b> Tuesday, February 24, 2009 12:12 PM<br>
<b>To:</b> James Buchanan; cisco-voip@puck.nether.net<br>
<b>Subject:</b> RE: [cisco-voip] PC Port on Phone Fails During LargeData
Transfer<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'>This is our
standard at the moment<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'>Switch
---------Phone Switch Port---------Phone PC Port-------&nbsp;&nbsp; PC NIC<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'>Auto/Full&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Auto/Auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
100/Full&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
100/Full&nbsp; <o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'>There is a long
convoluted history behind these settings but we have not had any issues until
recently.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'>&nbsp;<o:p></o:p></p>

</div>

<div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#006600'>Please
consider the impact on our environment before printing this e-mail.</span> <o:p></o:p></p>

</div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><br>
<br>
&gt;&gt;&gt; &quot;James Buchanan&quot; &lt;jbuchanan@ctiusa.com&gt; 2/24/2009
12:07 PM &gt;&gt;&gt;<o:p></o:p></p>

</div>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>When you hardcoded to 100/Full, did you hardcode on the switch
end and inside the phone?<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><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>STEVEN CASPER<br>
<b>Sent:</b> Tuesday, February 24, 2009 9:49 AM<br>
<b>To:</b> 'cisco-voip@puck.nether.net'<br>
<b>Subject:</b> [cisco-voip] PC Port on Phone Fails During Large Data Transfer<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>&nbsp;Has anyone run
across the following scenario - <o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>&nbsp;When large
amounts of data are transferred between an IP Phone and an attached PC such as
during a Microsoft Office update the update fails. When the failure occurs the
phone shows the status of port 2 (PC Port)&nbsp;as no link. it was working fine
prior to the update starting. This fails consistently when the phone PC port
and the PC NIC is set for 100/full, always seems to work when both are set to
Auto/Auto or when the phone is bypassed and the PC is plugged directly into the
switch port.<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Tried multiple phones
7941/61/11s. Current phone under test is running phone load is 41.8-3-3SR2S and
we are connected to a 3750 running 12.2.25 SEE2. Going to do more testing but
wondering if any one else may have run across this.<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Thanks<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Steve<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#006600'>Please
consider the impact on our environment before printing this e-mail.</span><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <o:p></o:p></span></p>

</div>

<pre>************************************<o:p></o:p></pre><pre>This email may contain privileged and/or confidential information that is intended solely for the use of the addressee.&nbsp; If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission.&nbsp; If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy.&nbsp; This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act.&nbsp; You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.<o:p></o:p></pre><pre>There are risks associated with the use of electronic transmission.&nbsp; The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.<o:p></o:p></pre><pre>************************************<o:p></o:p></pre>

<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>No virus
found in this incoming message.<br>
Checked by AVG - www.avg.com<br>
Version: 8.0.237 / Virus Database: 270.11.3/1966 - Release Date: 02/22/09
17:21:00</span><o:p></o:p></p>

<pre>************************************<o:p></o:p></pre><pre>This email may contain privileged and/or confidential information that is intended solely for the use of the addressee.&nbsp; If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission.&nbsp; If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy.&nbsp; This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act.&nbsp; You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.<o:p></o:p></pre><pre>There are risks associated with the use of electronic transmission.&nbsp; The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.<o:p></o:p></pre><pre>************************************<o:p></o:p></pre>

<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>No virus
found in this incoming message.<br>
Checked by AVG - www.avg.com<br>
Version: 8.0.237 / Virus Database: 270.11.3/1966 - Release Date: 02/22/09
17:21:00</span><o:p></o:p></p>

</div>

</body>

</html>