[cisco-voip] Strike 3 - Dead 7940G IP Phones - Update (Jason Aarons (US))

[FrogOnDSCP46EF]

As a part of trial and finding the causes - did you also tried putting a
non-Cisco phones in same environment?



On Tue, Jan 6, 2009 at 3:05 AM, Micah Bennett <mbennett at als-xtn.com> wrote:

>  Thanks everyone.
>
>
>
> 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.
>
>
>
> *Micah Bennett*
>
>   ------------------------------
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Fuermann, Jason
> *Sent:* Monday, January 05, 2009 9:52 AM
> *To:* 'FrogOnDSCP46EF'; 'jason.aarons at us.didata.com';
> cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Strike 3 - Dead 7940G IP Phones - Update
> (Jason Aarons (US))
>
>
>
> 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
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *FrogOnDSCP46EF
> *Sent:* Tuesday, December 30, 2008 9:06 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] Strike 3 - Dead 7940G IP Phones - Update (Jason
> Aarons (US))
>
>
>
> Hi Jason,
> Good recap!! Thanks for sharing this on this forum.
>
> To check EMI, you can use a good CAT5/6 cable tester.
>
> 1. Check EMI of your bad cable - make a note of all parameters, there are
> more than EMI.
> 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.
>
> HTH
>
>
> --
> Smile, you'll save someone else's day!
> Frog
>



-- 
Smile, you'll save someone else's day!
Frog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090106/13a5a5d0/attachment.html>