[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Sun Sep 5 10:11:10 2004 -->
- <!--x-from-r13: xnsxn ng nagvpuev.fg (Urbetr Qneyrff) -->
- <!--x-message-id: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: 1094351218.2052.10.camel@redhead --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] Vonage? -->
- <li><em>date</em>: Sun Sep 5 10:11:10 2004</li>
- <li><em>from</em>: kafka at antichri.st (George Carless)</li>
- <li><em>in-reply-to</em>: <1094351218.2052.10.camel@redhead></li>
- <li><em>references</em>: <[email protected]> <[email protected]> <1094351218.2052.10.camel@redhead></li>
- <li><em>subject</em>: [ale] Vonage?</li>
I recently signed up for vonage, and I've been pretty happy with it.
(<shameless>Oh, and if anyone wants to sign up and to get a month free
for them and for me, let me know and we can do the 'referral' thing
;)</shameless>).. but at any rate, the recommended setup is indeed to
have the vonage stuff first in your chain, so that it can do its QoS
stuff to ensure that you get good call quality. The Vonage thingy
actually seems to work as a simple NAT device w/ dhcp serving - uin my
scenario what appeared to happen was that the Vonage thing served up an
IP to my router via DHCP; my router then used that and dutifully handed
out IPs to the other machines on my network; it did cause a moment of
confusion since my d-link router was configured to notify dyndns of new
IPs, which meant that my domain wound up with an internal IP assigned to
it in dyndns, but that was easy enough to tweak. The Vonage stuff can
be configured to use an internal machine[|router|whatever] for a DMZ,
which I suppose means that you can continue having your network
basically set up as-is (everything from the vonage box apart from the
voice data would get routed on to the next thing in your chain, as I
understand it).
Also, you *can* put the vonage stuff later in your chain (behind your
router or whatnot) but it involves some extra configuration and I guess
you wouldn't get the QoS stuff; however, Vonage do explicitly mention it
in their manual and, presumably, therefore support it. But it's not
something I've tried.
Anyhow, hope this helps - I'd say that the vonage line quality is at
least up to that of a cellphone, and the various gizmos -- not to
mention the price -- all make it a very worthwhile pursuit. In fact I'm
in the process of ditching my girlfriend's current phone line + dialup
setup, on the basis that cable + vonage will actually cost her lest
money and will give her high-speed internet access..
Cheers,
--George
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00134" href="msg00134.html">[ale] Vonage?</a></strong>
<ul><li><em>From:</em> miguelquintero at bellsouth.net (miguel)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00139.html">[ale] Fry's has the best return policy!</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00141.html">[ale] OT: does anyone have anymore gmail invites to spare?</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00134.html">[ale] Vonage?</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00144.html">[ale] Vonage?</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00140"><strong>Date</strong></a></li>
<li><a href="threads.html#00140"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>