As a part of trial and finding the causes - did you also tried putting a non-Cisco phones in same environment?<br><br><br><br><div class="gmail_quote">On Tue, Jan 6, 2009 at 3:05 AM, Micah Bennett <span dir="ltr"><<a href="mailto:mbennett@als-xtn.com">mbennett@als-xtn.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">Thanks everyone.</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">Yes, we have no way to test, and even if
we did, it seems to be intermittent. Like I said earlier, we went 4 months
with no issues and then 5 more phones died during our testing. I have removed
the phone from this station and I am looking at the options to move that
printer somewhere else if they decide they need a phone there. </span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<div>
<p><b><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy; font-weight: bold;">Micah Bennett</span></font></b><font color="navy"><span style="color: navy;"> <br>
<br>
</span></font></p>
</div>
<div>
<div style="text-align: center;" align="center"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr align="center" size="2" width="100%">
</span></font></div>
<p><b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma; font-weight: bold;">From:</span></font></b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma;"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b><span style="font-weight: bold;">On
Behalf Of </span></b>Fuermann, Jason<br>
<b><span style="font-weight: bold;">Sent:</span></b> Monday, January 05, 2009
9:52 AM<br>
<b><span style="font-weight: bold;">To:</span></b> 'FrogOnDSCP46EF';
'<a href="mailto:jason.aarons@us.didata.com" target="_blank">jason.aarons@us.didata.com</a>'; <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b><span style="font-weight: bold;">Subject:</span></b> Re: [cisco-voip] Strike 3
- Dead 7940G IP Phones - Update (Jason Aarons (US))</span></font></p>
</div><div><div></div><div class="Wj3C7c">
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></p>
<p><font color="#1f497d" face="Calibri" size="2"><span style="font-size: 11pt; font-family: Calibri; color: rgb(31, 73, 125);">We had a similar
problem with improperly shielded 7940's. Our mobile radios would cause
the phone to reset when we PTT. Never had any phones completely dead from it
though. I wouldn't count on a cable tester to pick up this RF
interference because it could be well out of range from the frequency the cable
tester is using. Cisco replaced all our phones as they said this was a defect
in earlier versions. Your best bet is probably going to be to move phone and
printer as far away from each other as possible. In our case this was about 6
ft. Hope this helps</span></font></p>
<p><font color="#1f497d" face="Calibri" size="2"><span style="font-size: 11pt; font-family: Calibri; color: rgb(31, 73, 125);"> </span></font></p>
<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><b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma; font-weight: bold;">From:</span></font></b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma;">
<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b><span style="font-weight: bold;">On Behalf Of </span></b>FrogOnDSCP46EF<br>
<b><span style="font-weight: bold;">Sent:</span></b> Tuesday, December 30, 2008
9:06 PM<br>
<b><span style="font-weight: bold;">To:</span></b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b><span style="font-weight: bold;">Subject:</span></b> [cisco-voip] Strike 3 -
Dead 7940G IP Phones - Update (Jason Aarons (US))</span></font></p>
</div>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></p>
<p><font face="Times New Roman" size="3"><span style="font-size: 12pt;">Hi Jason,<br>
Good recap!! Thanks for sharing this on this forum.<br>
<br>
To check EMI, you can use a good CAT5/6 cable tester.<br>
<br>
1. Check EMI of your bad cable - make a note of all parameters, there are more
than EMI.<br>
2. Check EMI of your any of other good cable - and then compare the parameter,
at least you can show that comparative to your customer.<br>
<br>
HTH<br>
<br clear="all">
<br>
-- <br>
Smile, you'll save someone else's day!<br>
Frog</span></font></p>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Smile, you'll save someone else's day!<br>Frog<br>