More to the point, your packet discards are pretty up there (meaning a lot of data that is sent from your computer INTENDED for the server never made it, and your burst loss is pretty bad (meaning that when packets are lost, they are lost in large numbers all at once, rather than a steady loss). This will cause chop rather than just lousy voice quality.
One slight correction to your description (which is otherwise spot-on). Packet Loss is where the packets don't get to the destination. Packet Discards are where the packets DO get to the destination but they are received late or out of order so that they are as good as lost... in most cases. The never Vonage devices have the ability to correct for jitter. Jitter is the term for packets being received in an order and spacing other than what they were sent out as. By default, their jitter buffer is 60ms. This can be increased but it can add delay to the audio.
If anyone is interested in hearing what different levels of packet discards sounds like, here is a website with sample audio files (plus more than you probablly ever wanted to know about jitter):
UtterChaos, I believe that your cable modem is an Ambit. They don't like putting their name on the modems. Probablly because they don't want you contacting them for support. Their website pretty much says "go away" to the end user (their contact us page says don't contact us).
This is the simplest installation with an existing router. However, it is possible that your router can be causing some of your connection problems. Could you try connecting the Vonage device directly to the cable modem and see if the audio problems continue? Alternatively, you can try connecting your computer directly to the cable modem and run the testyourvoip.com test again. If you do this, you will need to power down the cable modem when you are changing the connections (so that it will give an IP address to the new thing you connect to it).
Also, if you PM me your account number I will check out the jitter correction settings on your Vonage device and run some tests to it.
Codec G.711 (PCM at 64kbps, 20ms RTP payload, 80kbps IP BW) Round-Trip Latency 97 ms Packet Discards 0.5% Packet Loss 0.0% Loss Periods Min: 20 ms Avg: 20 ms Max: 40 ms Random Loss
Jitter Min: 0 ms Avg: 6 ms Max: 26 ms
Signaling Quality Post-Dial Delay 47 ms Call Setup Time 63 ms Media Delay 141 ms MOS Analysis FROM Boston To You
Media Quality MOS 4.4 / 5.0 (Best with G.711 is 4.4)
Codec G.711 (PCM at 64kbps, 20ms RTP payload, 80kbps IP BW) Round-Trip Latency 97 ms Packet Discards 0.0% Packet Loss 0.0% Loss Periods Min: 0 ms Avg: 0 ms Max: 0 ms No Loss
Jitter Min: 4 ms Avg: 6 ms Max: 20 ms
Signaling Quality Post-Pickup Delay 63 ms Call Setup Time 76 ms Media Delay 96 ms
Could someone have access to my IP via my wireless router/network at night??
Should I change the security settings on my Router (mail computer), and wireless card (sons computer)?
Would this help, have any effect.?
_________________ The World Is Full of Kings and Queens, Who Blind Your Eyes, Then Steal Your Dreams!!!
NateHoy Vonage Forum MVM
Joined: Nov 01, 2005 Posts: 2257
Location: New England
First, yes, it is quite possible that someone is using your connection if your wireless router is unsecured. Set up WPA wireless security on the router and that will prevent that from happening again.
Second, it's possible that your ISP is overwhelmed in the evenings. People get home, they have supper, and they surf the net. During the day, you'll tend to have fewer problems because people are at work (except for those of us who telecommute - we're a problem all the time - grin).
When you are having problems, hook a single computer up directly to your modem, then re-run your test. If the numbers are significantly better, it may be your router and you can check to see if someone is using your bandwidth. If not, then your connection is just getting bad, call your ISP with the detailed results and hope they care.
_________________ Comcast Cable (3m down / 256k up) -> Linksys BEFCMU10 v2 (DOCSIS 1.0) -> WRT54G v4 ("Tomato" firmware) -> the rest of my network including a WRTP54G (Firmware: 5.01.04) My Vonage Self-Help Guides: http://vonage.nmhoy.net
BRadius New Forum Member
Joined: Jan 10, 2006 Posts: 5
Location: San Bruno, CA
From the investigation I've done into my own choppy audio, other end not hearing me, type issues, I believe the major problem is the connection from Vonage to Global Crossing and to a lesser extent, delay and packet loss going throught Global Crossing's backbone.
Here's some pings and traces to the I've done to my media gateway. From my host to near-end gblx is fine, to far-end gblx is OK but 60ms additional delay (expected), then to Vonage near-end router where I get 10% packet loss! Personally I think Vonage has grown faster then they expected and they haven't upgraded the infrastructure to meet the demand (but that's pure conjecture on my part).
Code:
1 myrouter 1.313 ms 1.253 ms 1.348 ms 2 myisp_router1 29.433 ms 12.064 ms 12.902 ms 3 myisp_router2 21.417 ms 11.806 ms 18.040 ms 4 myisp_egress_router 15.516 ms 23.886 ms 30.222 ms 5 sl-gw23-ana-1-3.sprintlink.net (144.228.17.41) 42.031 ms 29.358 ms 26.046 ms 6 sl-bb23-ana-12-1.sprintlink.net (144.232.1.153) 32.863 ms 28.297 ms 28.327 ms 7 sl-bb21-ana-10-0.sprintlink.net (144.232.1.185) 29.866 ms 31.362 ms 27.443 ms 8 sl-st20-la-13-0.sprintlink.net (144.232.20.67) 29.358 ms 28.449 ms 27.756 ms 9 so1-2-0-2488M.ar1.LAX2.gblx.net (208.50.13.1) 31.814 ms 27.970 ms 31.709 ms 10 so5-0-0-2488M.ar1.NYC1.gblx.net (67.17.64.146) 101.151 ms 103.139 ms 186.807 ms 11 Vonage-Holdings-Corp-Vonage-Toll-Free-NWRK.ge-2-3-0.403.ar1.NYC1 (64.210.19.18) 98.756 ms 90.652 ms 92.160 ms 12 * * * 13 69.59.249.154 (69.59.249.154) 110.690 ms 109.101 ms 105.984 ms
# ping -c 50 208.50.13.1 PING 208.50.13.1 (208.50.13.1): 56 data bytes 64 bytes from 208.50.13.1: icmp_seq=0 ttl=247 time=103.9 ms 64 bytes from 208.50.13.1: icmp_seq=1 ttl=247 time=28.9 ms 64 bytes from 208.50.13.1: icmp_seq=2 ttl=247 time=52.2 ms 64 bytes from 208.50.13.1: icmp_seq=3 ttl=247 time=27.2 ms 64 bytes from 208.50.13.1: icmp_seq=4 ttl=247 time=122.3 ms 64 bytes from 208.50.13.1: icmp_seq=5 ttl=247 time=23.8 ms 64 bytes from 208.50.13.1: icmp_seq=6 ttl=247 time=28.9 ms 64 bytes from 208.50.13.1: icmp_seq=7 ttl=247 time=48.8 ms 64 bytes from 208.50.13.1: icmp_seq=8 ttl=247 time=24.7 ms 64 bytes from 208.50.13.1: icmp_seq=9 ttl=247 time=28.8 ms 64 bytes from 208.50.13.1: icmp_seq=10 ttl=247 time=29.9 ms 64 bytes from 208.50.13.1: icmp_seq=11 ttl=247 time=24.2 ms 64 bytes from 208.50.13.1: icmp_seq=12 ttl=247 time=105.1 ms 64 bytes from 208.50.13.1: icmp_seq=13 ttl=247 time=27.0 ms 64 bytes from 208.50.13.1: icmp_seq=14 ttl=247 time=24.2 ms 64 bytes from 208.50.13.1: icmp_seq=15 ttl=247 time=40.6 ms 64 bytes from 208.50.13.1: icmp_seq=16 ttl=247 time=28.3 ms 64 bytes from 208.50.13.1: icmp_seq=17 ttl=247 time=26.4 ms 64 bytes from 208.50.13.1: icmp_seq=18 ttl=247 time=23.7 ms 64 bytes from 208.50.13.1: icmp_seq=19 ttl=247 time=28.1 ms 64 bytes from 208.50.13.1: icmp_seq=20 ttl=247 time=29.4 ms 64 bytes from 208.50.13.1: icmp_seq=21 ttl=247 time=37.7 ms 64 bytes from 208.50.13.1: icmp_seq=22 ttl=247 time=31.0 ms 64 bytes from 208.50.13.1: icmp_seq=23 ttl=247 time=23.5 ms 64 bytes from 208.50.13.1: icmp_seq=24 ttl=247 time=25.4 ms 64 bytes from 208.50.13.1: icmp_seq=25 ttl=247 time=26.5 ms 64 bytes from 208.50.13.1: icmp_seq=26 ttl=247 time=28.7 ms 64 bytes from 208.50.13.1: icmp_seq=27 ttl=247 time=46.3 ms 64 bytes from 208.50.13.1: icmp_seq=28 ttl=247 time=24.6 ms 64 bytes from 208.50.13.1: icmp_seq=29 ttl=247 time=29.2 ms 64 bytes from 208.50.13.1: icmp_seq=30 ttl=247 time=22.8 ms 64 bytes from 208.50.13.1: icmp_seq=31 ttl=247 time=28.5 ms 64 bytes from 208.50.13.1: icmp_seq=32 ttl=247 time=28.4 ms 64 bytes from 208.50.13.1: icmp_seq=33 ttl=247 time=31.9 ms 64 bytes from 208.50.13.1: icmp_seq=34 ttl=247 time=30.6 ms 64 bytes from 208.50.13.1: icmp_seq=35 ttl=247 time=26.6 ms 64 bytes from 208.50.13.1: icmp_seq=36 ttl=247 time=31.7 ms 64 bytes from 208.50.13.1: icmp_seq=37 ttl=247 time=28.5 ms 64 bytes from 208.50.13.1: icmp_seq=38 ttl=247 time=30.5 ms 64 bytes from 208.50.13.1: icmp_seq=39 ttl=247 time=25.0 ms 64 bytes from 208.50.13.1: icmp_seq=40 ttl=247 time=25.9 ms 64 bytes from 208.50.13.1: icmp_seq=41 ttl=247 time=34.1 ms 64 bytes from 208.50.13.1: icmp_seq=43 ttl=247 time=31.9 ms 64 bytes from 208.50.13.1: icmp_seq=44 ttl=247 time=26.4 ms 64 bytes from 208.50.13.1: icmp_seq=45 ttl=247 time=23.2 ms 64 bytes from 208.50.13.1: icmp_seq=46 ttl=247 time=33.3 ms 64 bytes from 208.50.13.1: icmp_seq=47 ttl=247 time=25.9 ms 64 bytes from 208.50.13.1: icmp_seq=48 ttl=247 time=27.2 ms 64 bytes from 208.50.13.1: icmp_seq=49 ttl=247 time=23.7 ms
--- 208.50.13.1 ping statistics --- 50 packets transmitted, 49 packets received, 2% packet loss round-trip min/avg/max = 22.8/34.3/122.3 ms
# ping -c 50 67.17.64.146 PING 67.17.64.146 (67.17.64.146): 56 data bytes 64 bytes from 67.17.64.146: icmp_seq=0 ttl=240 time=99.3 ms 64 bytes from 67.17.64.146: icmp_seq=1 ttl=240 time=93.6 ms 64 bytes from 67.17.64.146: icmp_seq=2 ttl=240 time=93.8 ms 64 bytes from 67.17.64.146: icmp_seq=3 ttl=240 time=92.5 ms 64 bytes from 67.17.64.146: icmp_seq=4 ttl=240 time=92.1 ms 64 bytes from 67.17.64.146: icmp_seq=5 ttl=240 time=99.6 ms 64 bytes from 67.17.64.146: icmp_seq=6 ttl=240 time=99.9 ms 64 bytes from 67.17.64.146: icmp_seq=7 ttl=240 time=94.1 ms 64 bytes from 67.17.64.146: icmp_seq=8 ttl=240 time=89.2 ms 64 bytes from 67.17.64.146: icmp_seq=9 ttl=240 time=92.5 ms 64 bytes from 67.17.64.146: icmp_seq=10 ttl=240 time=96.9 ms 64 bytes from 67.17.64.146: icmp_seq=11 ttl=240 time=92.8 ms 64 bytes from 67.17.64.146: icmp_seq=12 ttl=240 time=91.0 ms 64 bytes from 67.17.64.146: icmp_seq=13 ttl=240 time=90.4 ms 64 bytes from 67.17.64.146: icmp_seq=14 ttl=240 time=97.8 ms 64 bytes from 67.17.64.146: icmp_seq=15 ttl=240 time=89.4 ms 64 bytes from 67.17.64.146: icmp_seq=16 ttl=240 time=89.1 ms 64 bytes from 67.17.64.146: icmp_seq=17 ttl=240 time=91.3 ms 64 bytes from 67.17.64.146: icmp_seq=18 ttl=240 time=99.3 ms 64 bytes from 67.17.64.146: icmp_seq=19 ttl=240 time=95.6 ms 64 bytes from 67.17.64.146: icmp_seq=20 ttl=240 time=134.5 ms 64 bytes from 67.17.64.146: icmp_seq=21 ttl=240 time=90.0 ms 64 bytes from 67.17.64.146: icmp_seq=22 ttl=240 time=100.4 ms 64 bytes from 67.17.64.146: icmp_seq=23 ttl=240 time=91.9 ms 64 bytes from 67.17.64.146: icmp_seq=24 ttl=240 time=115.0 ms 64 bytes from 67.17.64.146: icmp_seq=25 ttl=240 time=92.9 ms 64 bytes from 67.17.64.146: icmp_seq=26 ttl=240 time=89.1 ms 64 bytes from 67.17.64.146: icmp_seq=27 ttl=240 time=93.3 ms 64 bytes from 67.17.64.146: icmp_seq=28 ttl=240 time=91.8 ms 64 bytes from 67.17.64.146: icmp_seq=29 ttl=240 time=123.5 ms 64 bytes from 67.17.64.146: icmp_seq=30 ttl=240 time=92.4 ms 64 bytes from 67.17.64.146: icmp_seq=31 ttl=240 time=90.3 ms 64 bytes from 67.17.64.146: icmp_seq=32 ttl=240 time=99.7 ms 64 bytes from 67.17.64.146: icmp_seq=33 ttl=240 time=91.2 ms 64 bytes from 67.17.64.146: icmp_seq=34 ttl=240 time=176.9 ms 64 bytes from 67.17.64.146: icmp_seq=35 ttl=240 time=98.1 ms 64 bytes from 67.17.64.146: icmp_seq=36 ttl=240 time=93.0 ms 64 bytes from 67.17.64.146: icmp_seq=37 ttl=240 time=95.4 ms 64 bytes from 67.17.64.146: icmp_seq=38 ttl=240 time=93.2 ms 64 bytes from 67.17.64.146: icmp_seq=39 ttl=240 time=95.6 ms 64 bytes from 67.17.64.146: icmp_seq=40 ttl=240 time=92.3 ms 64 bytes from 67.17.64.146: icmp_seq=41 ttl=240 time=92.3 ms 64 bytes from 67.17.64.146: icmp_seq=42 ttl=240 time=92.9 ms 64 bytes from 67.17.64.146: icmp_seq=43 ttl=240 time=92.9 ms 64 bytes from 67.17.64.146: icmp_seq=44 ttl=240 time=89.4 ms 64 bytes from 67.17.64.146: icmp_seq=45 ttl=240 time=97.8 ms 64 bytes from 67.17.64.146: icmp_seq=46 ttl=240 time=90.3 ms 64 bytes from 67.17.64.146: icmp_seq=47 ttl=240 time=104.1 ms 64 bytes from 67.17.64.146: icmp_seq=48 ttl=240 time=91.8 ms 64 bytes from 67.17.64.146: icmp_seq=49 ttl=240 time=165.1 ms
--- 67.17.64.146 ping statistics --- 50 packets transmitted, 50 packets received, 0% packet loss round-trip min/avg/max = 89.1/98.7/176.9 ms
# ping -c 50 64.210.19.18 PING 64.210.19.18 (64.210.19.18): 56 data bytes 64 bytes from 64.210.19.18: icmp_seq=0 ttl=241 time=92.2 ms 64 bytes from 64.210.19.18: icmp_seq=1 ttl=241 time=99.8 ms 64 bytes from 64.210.19.18: icmp_seq=2 ttl=241 time=100.8 ms 64 bytes from 64.210.19.18: icmp_seq=3 ttl=241 time=98.5 ms 64 bytes from 64.210.19.18: icmp_seq=5 ttl=241 time=111.1 ms 64 bytes from 64.210.19.18: icmp_seq=6 ttl=241 time=97.9 ms 64 bytes from 64.210.19.18: icmp_seq=7 ttl=241 time=89.2 ms 64 bytes from 64.210.19.18: icmp_seq=8 ttl=241 time=94.9 ms 64 bytes from 64.210.19.18: icmp_seq=9 ttl=241 time=90.9 ms 64 bytes from 64.210.19.18: icmp_seq=10 ttl=241 time=100.6 ms 64 bytes from 64.210.19.18: icmp_seq=12 ttl=241 time=91.0 ms 64 bytes from 64.210.19.18: icmp_seq=14 ttl=241 time=94.8 ms 64 bytes from 64.210.19.18: icmp_seq=15 ttl=241 time=96.2 ms 64 bytes from 64.210.19.18: icmp_seq=16 ttl=241 time=93.6 ms 64 bytes from 64.210.19.18: icmp_seq=18 ttl=241 time=91.7 ms 64 bytes from 64.210.19.18: icmp_seq=19 ttl=241 time=97.2 ms 64 bytes from 64.210.19.18: icmp_seq=20 ttl=241 time=89.4 ms 64 bytes from 64.210.19.18: icmp_seq=21 ttl=241 time=100.4 ms 64 bytes from 64.210.19.18: icmp_seq=22 ttl=241 time=88.5 ms 64 bytes from 64.210.19.18: icmp_seq=23 ttl=241 time=87.3 ms 64 bytes from 64.210.19.18: icmp_seq=24 ttl=241 time=89.6 ms 64 bytes from 64.210.19.18: icmp_seq=25 ttl=241 time=96.4 ms 64 bytes from 64.210.19.18: icmp_seq=26 ttl=241 time=128.3 ms 64 bytes from 64.210.19.18: icmp_seq=27 ttl=241 time=91.7 ms 64 bytes from 64.210.19.18: icmp_seq=28 ttl=241 time=254.7 ms 64 bytes from 64.210.19.18: icmp_seq=29 ttl=241 time=307.3 ms 64 bytes from 64.210.19.18: icmp_seq=30 ttl=241 time=247.1 ms 64 bytes from 64.210.19.18: icmp_seq=31 ttl=241 time=105.0 ms 64 bytes from 64.210.19.18: icmp_seq=32 ttl=241 time=92.8 ms 64 bytes from 64.210.19.18: icmp_seq=33 ttl=241 time=88.7 ms 64 bytes from 64.210.19.18: icmp_seq=34 ttl=241 time=101.3 ms 64 bytes from 64.210.19.18: icmp_seq=35 ttl=241 time=115.1 ms 64 bytes from 64.210.19.18: icmp_seq=36 ttl=241 time=96.0 ms 64 bytes from 64.210.19.18: icmp_seq=37 ttl=241 time=92.3 ms 64 bytes from 64.210.19.18: icmp_seq=38 ttl=241 time=89.3 ms 64 bytes from 64.210.19.18: icmp_seq=40 ttl=241 time=88.6 ms 64 bytes from 64.210.19.18: icmp_seq=41 ttl=241 time=87.8 ms 64 bytes from 64.210.19.18: icmp_seq=42 ttl=241 time=92.3 ms 64 bytes from 64.210.19.18: icmp_seq=43 ttl=241 time=104.8 ms 64 bytes from 64.210.19.18: icmp_seq=44 ttl=241 time=88.1 ms 64 bytes from 64.210.19.18: icmp_seq=45 ttl=241 time=92.8 ms 64 bytes from 64.210.19.18: icmp_seq=46 ttl=241 time=91.6 ms 64 bytes from 64.210.19.18: icmp_seq=47 ttl=241 time=89.3 ms 64 bytes from 64.210.19.18: icmp_seq=48 ttl=241 time=101.8 ms 64 bytes from 64.210.19.18: icmp_seq=49 ttl=241 time=104.0 ms
--- 64.210.19.18 ping statistics --- 50 packets transmitted, 45 packets received, 10% packet loss round-trip min/avg/max = 87.3/107.6/307.3 ms
Well, I found out how to change my security settings on my router/network card. It appeared that I DID NOT have a secure network...There was NO security key chosen. So I guess my network could have been accessed by anyone within range..
When I checked on my son's computer, there were 3 other networks displayed..SO maybe i got accessed sometime? Who knows..
We'll have to wait and see tonight...I used the phone all day( Thats a surprise), and there appears to be NO problem now..
Time will tell...I guess I'll get a phone call at work if its NOT working.. Well at least if its not working, I'll only hear 1/2 the **** ROTFLMAO.....
Thanks all, I will post again on the situautions position!!
_________________ The World Is Full of Kings and Queens, Who Blind Your Eyes, Then Steal Your Dreams!!!
BRadius New Forum Member
Joined: Jan 10, 2006 Posts: 5
Location: San Bruno, CA
Well, I found out how to change my security settings on my router/network card. It appeared that I DID NOT have a secure network...There was NO security key chosen. So I guess my network could have been accessed by anyone within range..
When I checked on my son's computer, there were 3 other networks displayed..SO maybe i got accessed sometime? Who knows..
We'll have to wait and see tonight...I used the phone all day( Thats a surprise), and there appears to be NO problem now..
Time will tell...I guess I'll get a phone call at work if its NOT working.. Well at least if its not working, I'll only hear 1/2 the **** ROTFLMAO.....
Thanks all, I will post again on the situautions position!!
If you have the option, use WPA authentication and TKIP (or AES) encryption and make sure to use a passphrase that is at least 20 characters long.
Not sure of the other settings you mentioned..I only saw WEP..
What is passphrase? I asked the linksys tech as we were fixing the security issue, he said nothing about it?
I also have a selection to have it generated for me...
If I use a passphrase, what needs to be done to the other computer with the wireless card in it?
Yes, the Linksys BEFW11S4 only supports WEP. It's not very secure, but it's FAR better than what you have today (open network), so use it.
All you should have to do is tell the router to use WEP, and pick a secure password/passphrase. This will generate an encryption key. Depending on your client, you either have to key the passphrase or the long encryption key into the client to get it talking to the router.
You may also want to turn off "SSID broadcast", which will make your router somewhat less visible to the casual WiFi user.
_________________ Comcast Cable (3m down / 256k up) -> Linksys BEFCMU10 v2 (DOCSIS 1.0) -> WRT54G v4 ("Tomato" firmware) -> the rest of my network including a WRTP54G (Firmware: 5.01.04) My Vonage Self-Help Guides: http://vonage.nmhoy.net
rdstoll Full Forum Member
Joined: Dec 29, 2005 Posts: 63
Location: Des Plaines, IL
I too have experienced call quality issues in the last week. First I was hearing a loud buzz on the line after being on the phone for about five minutes (happend more than once) and just today I had a call dropped. Is Vonage doing some sort of upgrade? I figured it was my line but saw this post and wondered if it was something else.
Thanks.
rdstoll Full Forum Member
Joined: Dec 29, 2005 Posts: 63
Location: Des Plaines, IL
NateHoy: Is there a reason to specify Boston when doing this test? I didn't see the original poster say that he was from Boston and I am going to run this test tonight, although I live in Chicago.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
All times are GMT - 5 Hours
Vonage Service Plans
Vonage VoIP Members
Members New HorpDrype New Today 7 Yesterday 18 Total 63405 Who Is On Site Visitors 196 Members 0 Total 196
1 Unlimited calling and other services for all residential plans are based on normal residential use by single-family household members. A combination of factors are used to determine abnormal use, including but not limited to: the number of unique numbers called, international calls forwarded, minutes used and other factors. Subject to our Reasonable Use Policy and Terms of Service.
HIGH SPEED INTERNET REQUIRED. † LIMITED TIME OFFER, VALID FOR NEW LINES ONLY. RATES EXCLUDE INTERNET SERVICE, SURCHARGES, FEES AND TAXES. As a subscriber to Vonage service, you agree to be bound by the Terms of Service. See www.vonage.com/tos for details. ¤ Where available. The number transfer process takes approximately 10 business days from the time you confirm your transfer request. Alarms, TTY and other systems may not be compatible. Vonage 911 service operates differently than traditional 911. See www.vonage.com/911 for details.
Thinking of signing up for Vonage but have questions? Business and Residential customers can call Toll Free 24 hours a day at: 1-888-692-8074 No Vonage Promotional Codes or Coupon Codes are required at www.vonage.com.
The Vonage Forum provides the Vonage sign up Best Offer Promotion Deal as a means to offset
our cost. If you are considering signing up for Vonage and have found our Vonage
News, Customer Reviews, Forums & all other parts of this site useful, please
use our Vonage FREE Month sign up offer Deal Coupon.
Vonage VoIP Phone Service is redefining communications by offering consumers & small business VoIP Internet phones, an affordable alternative to traditional phone service.
The Vonage VoIP Forum Generated This Page In: 0.51 Seconds and 356 Pages In The Last 60 Seconds The Vonage VoIP Forum
Members
New 
New Today 7
Yesterday 18
Total 63405
Who Is On Site
Visitors 196
Members 0
Total 196
+0.13