<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;Thanks!&#x27; in forum &#x27;&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Thanks-23282745</link>
<description></description>
<language>en</language>
<pubDate>Fri, 10 Feb 2012 14:43:41 EDT</pubDate>
<lastBuildDate>Fri, 10 Feb 2012 14:43:41 EDT</lastBuildDate>

<item>
<title>Re: Thanks!</title>
<link>http://www.dslreports.com/forum/Re-Thanks-23287633</link>
<description><![CDATA[jbcg posted : Yes--one of the first things I did after installing the device was to ensure my DHCP server would issue the VOIP IP address to the MAC address of the device Voipo sent me.  The firewall ports we're talking about are open only for this IP address.<br><br>Okay, based on three phone conversations today, the port work may have helped latency a bit.  I also had one call where I had to dial twice to get a connection; the first time I got a long delay and then a busy signal on a line that has phone company voice mail.<br><br>The sound quality (on this relatively limited test) did seem to get somewhat better--no garbled or "gritty" moments, at least on these three calls.  Two of the calls were fairly long ones.<br><br>Perhaps the device really does need to be outside of the firewall (or I need to turn off stateful inspection) in order to produce less latency.<br><br>When I sent the payment directly from PayPal it was credited promptly.<br><br>Thanks for your advice, Tim.<br><br>Joey]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Thanks-23287633</guid>
<pubDate>Tue, 03 Nov 2009 22:18:27 EDT</pubDate>
</item>

<item>
<title>Re: Thanks!</title>
<link>http://www.dslreports.com/forum/Re-Thanks-23287632</link>
<description><![CDATA[VOIPoTim posted : <div class="bquote"><small>said by <a href="/profile/475550" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=475550');">jbcg</a>:</small><br><br>I already had most of these ports open and routed from my last VOIP trial, but had to open the port ranges a bit. Do you also require port 69 (TFTP) for provisioning, or can I close that one?<br> </div>This may sound odd to ask, but we see it A LOT so I will anyway....<br><br>Do you have the new adapter set to the same IP that everything is forwarded to?<br><br>We've had a ton of customers have forwarding setup and then the new adapter gets a new IP but everything is forwarded to old.<br><br>We actually use http for provisioning, but it's a "pull" with the adapter initiating the request so it doesn't need to be forwarded.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Thanks-23287632</guid>
<pubDate>Tue, 03 Nov 2009 22:18:19 EDT</pubDate>
</item>

<item>
<title>Thanks!</title>
<link>http://www.dslreports.com/forum/Thanks-23282745</link>
<description><![CDATA[jbcg posted : Thanks for the quick and helpful response, Tim.  I'm sure you're aware, but good customer responsiveness is what it takes for a lot of us customers these days.  That's part of the reason I'm dropping MCI (and eventually AT&T)--these guys provide virtually no usable customer support at all.  I don't care how good their service is if I can't talk to them when I do have a problem.  You guys are very responsive and I appreciate that more than you know.<br><br>I already had most of these ports open and routed from my last VOIP trial, but had to open the port ranges a bit.  Do you also require port 69 (TFTP) for provisioning, or can I close that one?<br><br>I'm very wary of dropping stateful inspection . . . but I might try the adapter outside the firewall one day just for grins.  Would be interesting to see if that would eliminate latency altogether.<br><br>Oddly, I had a very good, low latency call with a friend today while I was downloading some large files.  That was before I tweaked the port settings.  Hmmm.<br><br>Re payments: This is one area where the online interface needs some work, or at least an explanatory message on the billings page.<br><br>I like PayPal because I'm very wary of giving service companies my credit card number.  First, I've lost control of my card number three times in the past 10 years after I've used it on the web, every time with a "reputable" merchant.<br><br>The second reason is the Compu$erve effect.  You sign up for a service with the promise that you can cancel at any time.  When you do cancel the service terminates immediately.  But the billings go on and on.  The credit card company doesn't care because the charge is so small, so you have to call to dispute the charge every month until the service company finally decides they've bled you enough.  This has happened to me with numerous subscription services (MSN charged me for almost two years!).  <br><br>A variation on this is the surprise "kiss off" fees some ISPs like to charge when you cancel.  One company charged my card for $25 because I returned their modem in a brown cardboard box rather than the white cardboard box they sent it to me in.  No joke!  Another ISP tried to charge me $280 for not returning my DSL modem after they merged with the ISP that sold me the modem outright as part of a package deal.  Presenting the terms of my original agreement didn't help--it took a letter from my attorney to resolve it.<br><br>So I really appreciate that Voipo allows payments via PayPal.<br><br>Thanks again.  I'll update this thread with how it works out.<br><br>Best,<br><br>Joey]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Thanks-23282745</guid>
<pubDate>Tue, 03 Nov 2009 02:39:51 EDT</pubDate>
</item>

</channel>
</rss>

