<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: How To Avoid A Key Pitfall Of Voice and Data Convergence</title>
	<link>http://www.emailbattles.com/2006/03/17/security_aadbfbfbed_gc/</link>
	<description>Spam, Security, Privacy, Spyware, Phishing &#038; Viruses from the Front Lines.</description>
	<pubDate>Sun, 20 Jul 2008 00:49:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: je.saist</title>
		<link>http://www.emailbattles.com/2006/03/17/security_aadbfbfbed_gc/#comment-587</link>
		<pubDate>Wed, 22 Mar 2006 21:07:45 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/03/17/security_aadbfbfbed_gc/#comment-587</guid>
					<description>I work front lines support for Cox Communications, and I've run into this a lot with our VOIP customers. I'm not even sure where to start. First there are those who call in and can't get online, yet are using the VOIP phone to call in on. Explaining that if they can call on the VOIP phone, then there is no problem with the internet access, the problem is at the computer. Then explaining to them that if they happen to be talking on that VOIP, there isn't anything we can do to troubleshoot the problem because if I do anything to the modem I will terminate the phone call. Thus the customer needs to call on a completely seperate line. Nine times out of 10, they call back on another phone... also connected through the VOIP modem.&lt;br&gt; &lt;br&gt; Then there is the whole crowd who fall into the above mentioned problem. They only have "one" home phone, and it's their cable modem. When the modem fails, the network drop, the DNS serves have an issue, DHCP servers have an issue, or anything happens on the network, the phone is GOING to drop, period. If there is a power outage, the phone is going to DROP. Explaining this to customers after they have experienced the problems is a work in fustration.&lt;br&gt; &lt;br&gt; The problem, I presume, is made worse by over-eager sales people who don't think to realize that they may be causing more harm than good. As for me and myself, thanks to the problems I've had to fix, I refuse to have any part with VOIP outside of fixing the problems I get during work. It just is not with the trouble.</description>
		<content:encoded><![CDATA[<p>I work front lines support for Cox Communications, and I&#8217;ve run into this a lot with our VOIP customers. I&#8217;m not even sure where to start. First there are those who call in and can&#8217;t get online, yet are using the VOIP phone to call in on. Explaining that if they can call on the VOIP phone, then there is no problem with the internet access, the problem is at the computer. Then explaining to them that if they happen to be talking on that VOIP, there isn&#8217;t anything we can do to troubleshoot the problem because if I do anything to the modem I will terminate the phone call. Thus the customer needs to call on a completely seperate line. Nine times out of 10, they call back on another phone&#8230; also connected through the VOIP modem.</p>
<p> Then there is the whole crowd who fall into the above mentioned problem. They only have &#8220;one&#8221; home phone, and it&#8217;s their cable modem. When the modem fails, the network drop, the DNS serves have an issue, DHCP servers have an issue, or anything happens on the network, the phone is GOING to drop, period. If there is a power outage, the phone is going to DROP. Explaining this to customers after they have experienced the problems is a work in fustration.</p>
<p> The problem, I presume, is made worse by over-eager sales people who don&#8217;t think to realize that they may be causing more harm than good. As for me and myself, thanks to the problems I&#8217;ve had to fix, I refuse to have any part with VOIP outside of fixing the problems I get during work. It just is not with the trouble.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Big Red</title>
		<link>http://www.emailbattles.com/2006/03/17/security_aadbfbfbed_gc/#comment-586</link>
		<pubDate>Tue, 21 Mar 2006 08:24:05 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/03/17/security_aadbfbfbed_gc/#comment-586</guid>
					<description>Wisdom from old seems apropos - Don't put all your eggs in one basket.</description>
		<content:encoded><![CDATA[<p>Wisdom from old seems apropos - Don&#8217;t put all your eggs in one basket.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: d'OH</title>
		<link>http://www.emailbattles.com/2006/03/17/security_aadbfbfbed_gc/#comment-585</link>
		<pubDate>Fri, 17 Mar 2006 15:33:11 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/03/17/security_aadbfbfbed_gc/#comment-585</guid>
					<description>OMG! Where were you last week? Our ISP-foneco cratered and left us w/o fonz for 3 days:(</description>
		<content:encoded><![CDATA[<p>OMG! Where were you last week? Our ISP-foneco cratered and left us w/o fonz for 3 days:(
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
