Sign up
 Vonage  

       
 
Vonage Forum Menu

Vonage Forums
Vonage VoIP Forum
mikebrown Posted:
Hello, I think
you should consult
it with the Expert
they can surely
help you
...

In The Forum:
Hard Wiring - Installation
Topic:
Hardwiring in a Rental House
On Jun 24, 2017 at 09:15:34

Haniltery Posted:
For wipe call
history also some
of the offline, in
gengral , it
usually apply to
...

In The Forum:
Vonage
Topic:
How to Delete call history from online account?
On May 09, 2017 at 06:14:26

diana87 Posted:
You have to use
VPN service to
bypass
Geo-restrictions
and get free
access while
...

In The Forum:
Vonage
Topic:
Recent calling problem from Egypt
On May 02, 2017 at 17:28:06

dconnor Posted:
What is the main
number on the
account? And
which one is the
virtual number?
...

In The Forum:
Vonage UK
Topic:
How do you call 999
On Apr 27, 2017 at 18:52:02

Trafford Posted:
Seems like a
simple
question. We
rely exclusively
on a Vonage system
for our
...

In The Forum:
Vonage UK
Topic:
How do you call 999
On Apr 27, 2017 at 10:42:50

diazou Posted:
Hello, It's
compatible with
Android your phone
software
? Thanks!
...

In The Forum:
Vonage
Topic:
IP PBX for small business
On Mar 28, 2017 at 12:42:33

jeddaisg Posted:
Hi all We have
a Vonage VOIP
system for our
office. Lately,
our call quality
...

In The Forum:
Vonage
Topic:
Ethernet Cable; Wiring schematic? 568-B?
On Feb 23, 2017 at 18:33:52

beast321 Posted:
I don't know if
you heard, that
many more
Dreamcast games
are opened up
recently.
...

In The Forum:
Fax - Tivo - Alarms
Topic:
Using phone as a dial up modem for Dreamcast Gaming
On Feb 16, 2017 at 03:16:51

Av8rix Posted:
Sorry to start a
new thread on an
old topic but when
I google “Vonage
MAC address
...

In The Forum:
Vonage
Topic:
New adapter and router -- MAC change
On Jan 11, 2017 at 01:07:21

tplink Posted:
Im trying to add
my HT802 vonage
adapter to my home
network. I
currently have
...

In The Forum:
Hard Wiring - Installation
Topic:
Vonage behind switch
On Dec 05, 2016 at 12:35:11


Vonage VoIP Forums

Vonage In The News
Vonage Expands International Presence with Investments in Asia Pacific Region

Vonage to Present at the Oppenheimer 20th Annual Technology, Internet & Communications Conference

Syndication

Vonage Customer Reviews
Salt Lake City: impressions after several months
Salt Lake City: impressions after several months



Review: My First Day With Vonage, Excellent!
Review: My First Day With Vonage, Excellent!



Great Price, No Complaints
Great Price, No Complaints



You need some common sense.
You need some common sense.



Vonage Customer Review: One month with Vonage, and...
Vonage Customer Review: One month with Vonage, and...




Vonage Reviews


Post new topic   Reply to topic  Vonage® VoIP Forum - Vonage News, Reviews And Discussion » Vonage
Author Message
sundardba
Vonage Forum Associate
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15

PostPosted: Wed May 06, 2009 12:57 pm    Post subject: unable to hear voice of other person Reply with quote Back to top

1. Your location : New jersey
2. Your ISP name and type (cable, DSL, wireless etc) Cable - Comcast
3. Upload and download speeds - 3 Mbs upload and 2.73 Mbs download
4. Modem make and model - Dlink DCM 202 cable modem-
5. Type of Vonage adapter used ie RT31P2 or PAP2 - Motorola VT2142 -V0
6. Setup of Network ie Cable Modem---->Vonage Adapter-->PC
7. Issue you are experiencing ie dropped calls, choppy audio etc - Every 10 minutes or so I am able to hear the other person voice but he is not able to hear my voice -
8. Run this Voip Test: I am not able to run this test -

I am getting this issue during the past two weeks. Can any one help me with this issue?


Last edited by sundardba on Wed May 06, 2009 6:44 pm; edited 2 times in total
View user's profile Send private message
ksig
Vonage Forum Master
Vonage Forum Master


Joined: Jul 07, 2008
Posts: 183
Location: Illinois

PostPosted: Wed May 06, 2009 1:31 pm    Post subject: Reply with quote Back to top

I'm confused. Why can't you run the test? There isn't a lot we can help you with in your previous post. It is like saying my car won't start and I live in NJ. It doesn't tell the mechanic much of anything.
View user's profile Send private message
kdf55
Vonage Forum Evangelist
Vonage Forum Evangelist


Joined: Jun 30, 2007
Posts: 373
Location: Highland, IL

PostPosted: Wed May 06, 2009 4:43 pm    Post subject: Reply with quote Back to top

When you try to run the speed test, all is says is "License Expired"
View user's profile Send private message
sundardba
Vonage Forum Associate
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15

PostPosted: Wed May 06, 2009 6:35 pm    Post subject: Reply with quote Back to top

Yes that is correct When I try to run speed test I get License Expired.
I ran the test in another site http://www.testyourvoip.com/

MOS Analysis From You TO San Jose
****************************************
Media Quality MOS 4.2 / 5.0
(Best with G.711 is 4.4)

Degradation Sources
Codec 0.57 68.1%
Latency 0.00 0.0%
Packet Discards 0.27 31.9%
Packet Loss 0.00 0.0%

Codec G.711 (PCM at 64kbps,
20ms RTP payload,
80kbps IP BW)
Round-Trip
Latency 178 ms
Packet Discards 1.1%
Packet Loss 0.0%
Loss Periods Min: 20 ms
Avg: 20 ms
Max: 80 ms
Burst Loss

Jitter Min: 0 ms
Avg: 5 ms
Max: 26 ms

Signaling Quality Post-Dial Delay 109 ms
Call Setup Time 109 ms
Media Delay 265 ms
*********************************************
MOS Analysis FROM San Jose To You

Media Quality MOS 4.4 / 5.0
(Best with G.711 is 4.4)


Degradation Sources
Codec 0.58 100.0%
Latency 0.00 0.0%
Packet Discards 0.00 0.0%
Packet Loss 0.00 0.0%

Codec G.711 (PCM at 64kbps,
20ms RTP payload,
80kbps IP BW)
Round-Trip
Latency 178 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 152 ms
Call Setup Time 127 ms
Media Delay 182 ms
**************************************
View user's profile Send private message
sundardba
Vonage Forum Associate
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15

PostPosted: Wed May 06, 2009 6:40 pm    Post subject: Reply with quote Back to top

PLease note that I have corrected the modem name and Vonage adapter. I am vaonage user for past two years. I never had any issue. Recentlyt I moved to new appartment. For the past two to three weeks I am getting the issue. I spoke with Comcast CSR and he confirmed that signal strength and speed is good.
I have panasonioc cordless phone Comcast CSR was siuggesting that cordless phone may have some issues.
Also I read that there shgould be minimum of 4 feet distance between TA and phone, wireless etc .. Which will be difficult for me since my table is small ..
Can you please help me in exact issue?
View user's profile Send private message
trekologer
Vonage Forum Evangelist
Vonage Forum Evangelist


Joined: Dec 04, 2005
Posts: 350

PostPosted: Wed May 06, 2009 8:44 pm    Post subject: Reply with quote Back to top

The testyourvoip.com test result mirrors exactly what you describe is occurring on calls: the remote party cannot hear you for several seconds. The test shows outbound jitter resulting in burst loss. Essentially what this means is that for several seconds at a time, the data you send takes much longer to get to the destination that it should, long enough that the data gets lost. Despite what Comcast says, it looks like you have a problem with the quality of your internet connection (saying you have great "signal" typically means absolutely nothing).

Can you run a ping and traceroute to these IP addresses from your computer and post the results: 69.59.248.70, 69.59.241.11, 69.59.239.70.

In Windows, go to the command prompt (usually Start > Accessories > Command Prompt) and type:

ping -n 100 <ip address>

tracert <ip address>
View user's profile Send private message
sundardba
Vonage Forum Associate
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15

PostPosted: Wed May 06, 2009 10:19 pm    Post subject: Reply with quote Back to top

Here is the output

C:\>ping -n 100 69.59.248.70

Pinging 69.59.248.70 with 32 bytes of data:

Reply from 69.59.248.70: bytes=32 time=14ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=14ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=15ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=19ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=19ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=10ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240

Ping statistics for 69.59.248.70:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 19ms, Average = 12ms
Control-C
^C
C:\>
C:\>ping -n 100 69.59.241.11

Pinging 69.59.241.11 with 32 bytes of data:

Reply from 69.59.241.11: bytes=32 time=84ms TTL=240
Reply from 69.59.241.11: bytes=32 time=87ms TTL=240
Reply from 69.59.241.11: bytes=32 time=96ms TTL=240
Reply from 69.59.241.11: bytes=32 time=84ms TTL=240
Reply from 69.59.241.11: bytes=32 time=87ms TTL=240
Reply from 69.59.241.11: bytes=32 time=84ms TTL=240
Reply from 69.59.241.11: bytes=32 time=84ms TTL=240
Reply from 69.59.241.11: bytes=32 time=83ms TTL=240
Reply from 69.59.241.11: bytes=32 time=86ms TTL=240
Reply from 69.59.241.11: bytes=32 time=86ms TTL=240
Reply from 69.59.241.11: bytes=32 time=84ms TTL=240
Reply from 69.59.241.11: bytes=32 time=84ms TTL=240
Reply from 69.59.241.11: bytes=32 time=83ms TTL=240
Reply from 69.59.241.11: bytes=32 time=88ms TTL=240
Reply from 69.59.241.11: bytes=32 time=84ms TTL=240
Reply from 69.59.241.11: bytes=32 time=86ms TTL=240
Reply from 69.59.241.11: bytes=32 time=96ms TTL=240

Ping statistics for 69.59.241.11:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 96ms, Average = 86ms
Control-C
^C
C:\>

C:\>ping -n 100 69.59.239.70

Pinging 69.59.239.70 with 32 bytes of data:

Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=99ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=92ms TTL=244
Reply from 69.59.239.70: bytes=32 time=88ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244

Ping statistics for 69.59.239.70:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 99ms, Average = 90ms
Control-C
^C
C:\>
C:\>tracert 69.59.248.70

Tracing route to media-relay-48.klga1.s.vonagenetworks.net [69.59.248.70]
over a maximum of 30 hops:

1 3 ms <1 ms <1 ms 192.168.10.1
2 3 ms <1 ms <1 ms 192.168.15.1
3 * * * Request timed out.
4 9 ms 9 ms 10 ms 68.85.76.153
5 11 ms 10 ms 11 ms te-0-0-0-4-ar01.plainfield.nj.panjde.comcast.net [68.86.210.22]
6 14 ms 11 ms 11 ms pos-0-6-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.25]
7 21 ms 13 ms 13 ms br02.klga1.comcast.vonagenetworks.net [68.86.89.130]
8 12 ms 17 ms 12 ms ve252.sw02.klga1.m.vonagenetworks.net [69.59.251.42]
9 12 ms 12 ms 11 ms e4-2.sw05.klga1.m.vonagenetworks.net [69.59.250.138]
10 12 ms 13 ms 14 ms media-relay-48.klga1.s.vonagenetworks.net [69.59.248.70]

Trace complete.

C:\>

C:\>tracert 69.59.241.11

Tracing route to media-relay-05.klax2.s.vonagenetworks.net [69.59.241.11]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.10.1
2 1 ms <1 ms <1 ms 192.168.15.1
3 * * * Request timed out.
4 11 ms 26 ms 9 ms 68.85.76.153
5 12 ms 13 ms 10 ms te-0-0-0-4-ar01.plainfield.nj.panjde.comcast.net [68.86.210.22]
6 12 ms 11 ms 11 ms pos-0-6-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.25]
7 10 ms 11 ms 11 ms xe-10-1-0.edge1.NewYork2.Level3.net [4.78.169.45]
8 13 ms 29 ms 11 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
9 14 ms 17 ms 17 ms ae-6-6.ebr4.NewYork1.Level3.net [4.69.141.21]
10 23 ms 17 ms 17 ms ae-74-74.csw2.NewYork1.Level3.net [4.69.134.118]
11 12 ms 11 ms 11 ms ae-2-79.edge6.NewYork1.Level3.net [4.68.16.74]
12 36 ms 14 ms 16 ms VONAGE-HOLD.edge6.NewYork1.Level3.net [4.78.189.10]
13 14 ms 24 ms 12 ms ae0.0.br01.klga1.m.vonagenetworks.net [69.59.250.125]
14 41 ms 39 ms 40 ms so-3-0-0.br01.kord1.m.vonagenetworks.net [69.59.251.54]
15 49 ms 40 ms 40 ms ae0.br02.kord1.m.vonagenetworks.net [69.59.239.250]
16 84 ms 83 ms 84 ms so-2-1-0.br01.klax1.m.vonagenetworks.net [69.59.245.45]
17 86 ms 83 ms 87 ms sw01.klax1.m.vonagenetworks.net [216.115.28.14]
18 85 ms 83 ms 86 ms media-relay-05.klax2.s.vonagenetworks.net [69.59.241.11]

Trace complete.

C:\>
C:\>tracert 69.59.239.70

Tracing route to media-relay-01.kord1.s.vonagenetworks.net [69.59.239.70]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.10.1
2 1 ms <1 ms <1 ms 192.168.15.1
3 * * * Request timed out.
4 14 ms 15 ms 9 ms 68.85.76.153
5 13 ms 12 ms 11 ms te-0-0-0-4-ar01.plainfield.nj.panjde.comcast.net [68.86.210.22]
6 12 ms 11 ms 12 ms pos-0-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.29]
7 17 ms 30 ms 18 ms pos-1-15-0-0-cr01.mclean.va.ibone.comcast.net [68.86.85.89]
8 25 ms 16 ms 16 ms br02.kiad0.comcast.vonagenetworks.net [68.86.89.122]
9 22 ms 23 ms 18 ms 0.ae0.br01.kiad0.m.vonagenetworks.net [69.59.229.229]
10 86 ms 85 ms 91 ms so-2-1-0.br02.klax1.m.vonagenetworks.net [69.59.245.49]
11 97 ms 86 ms 88 ms br01.klax1.m.vonagenetworks.net [216.115.28.9]
12 89 ms 90 ms 90 ms so-3-0-0.br02.kord1.m.vonagenetworks.net [69.59.245.46]
13 92 ms 92 ms 98 ms ae0.br01.kord1.m.vonagenetworks.net [69.59.239.249]
14 90 ms 90 ms 88 ms ve251.sw01.kord1.m.vonagenetworks.net [69.59.239.194]
15 91 ms 90 ms 95 ms media-relay-01.kord1.s.vonagenetworks.net [69.59.239.70]

Trace complete.

C:\>
View user's profile Send private message
trekologer
Vonage Forum Evangelist
Vonage Forum Evangelist


Joined: Dec 04, 2005
Posts: 350

PostPosted: Thu May 07, 2009 6:33 am    Post subject: Reply with quote Back to top

Using the "-n 100" option will causing ping to repeat 100 times. The point of doing that is to run it for a slightly extended period in hopes of catching the connection issue since the problem is not continuous. Unfortunately, the high jitter wasn't seen. Can you do them again?
View user's profile Send private message
sundardba
Vonage Forum Associate
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15

PostPosted: Thu May 07, 2009 7:25 am    Post subject: Reply with quote Back to top

Ok.. Sorry I didn't know that

C:\>ping -n 100 69.59.248.70

Pinging 69.59.248.70 with 32 bytes of data:

Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=27ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=10ms TTL=240
Reply from 69.59.248.70: bytes=32 time=21ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=20ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=16ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=10ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=17ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=14ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=22ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=14ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=12ms TTL=240
Reply from 69.59.248.70: bytes=32 time=11ms TTL=240
Reply from 69.59.248.70: bytes=32 time=13ms TTL=240

Ping statistics for 69.59.248.70:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 27ms, Average = 12ms

C:\>

***************************************
C:\>ping -n 100 69.59.241.11

Pinging 69.59.241.11 with 32 bytes of data:

Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=87ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=87ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=87ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=87ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=87ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=87ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=93ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=87ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=87ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=91ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=86ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=85ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236
Reply from 69.59.241.11: bytes=32 time=84ms TTL=236

Ping statistics for 69.59.241.11:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 93ms, Average = 85ms

C:\>
*********************************************
C:\>ping -n 100 69.59.239.70

Pinging 69.59.239.70 with 32 bytes of data:

Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=92ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=92ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=102ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=94ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=92ms TTL=244
Reply from 69.59.239.70: bytes=32 time=92ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=88ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=88ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=90ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244
Reply from 69.59.239.70: bytes=32 time=91ms TTL=244
Reply from 69.59.239.70: bytes=32 time=95ms TTL=244
Reply from 69.59.239.70: bytes=32 time=89ms TTL=244

Ping statistics for 69.59.239.70:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 102ms, Average = 90ms

C:\>
View user's profile Send private message
sundardba
Vonage Forum Associate
Vonage Forum Associate


Joined: Dec 15, 2007
Posts: 15

PostPosted: Thu May 07, 2009 12:35 pm    Post subject: Reply with quote Back to top

Could any one help me on this?
is it the intenet connection that is causing the issue?
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic

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 List Members
New patsykf3
New Today 0
Yesterday 0
Total 101029

Who Is On Site
Visitors 1
Members 0
Total 1


Vonage VoIP Forum Members:
Login Here
Not a Member? You can Register Here
As a registered member you will have access to the VoIP Speed Test, Vonage Service Announcements and post comments in the
Vonage VoIP Forums

Site Search
 






†AK and HI residents pay $29.95 shipping. ††Limited time offer. Valid for residents of the United States (&DC), 18 years or older, who open new accounts. Offer good while supplies last and only on new account activations. One kit per account/household. Offer cannot be combined with any other discounts, promotions or plans and is not applicable to past purchases. Good while supplies last. Allow up to 2 weeks for shipping. Other restrictions may apply.

1Unlimited calling and other services for all residential plans are based on normal residential, personal, non-commercial use. A combination of factors is used to determine abnormal use, including but not limited to: the number of unique numbers called, calls forwarded, minutes used and other factors. Subject to our Reasonable Use Policy and Terms of Service.

2Shipping and activation fees waived with 1-year agreement. An Early Termination Fee (with periodic pro-rated reductions) applies if service is terminated before the end of the first 12 months. Additional restrictions may apply. See Terms of Service for details.

HIGH SPEED INTERNET REQUIRED. †VALID FOR NEW LINES ONLY. RATES EXCLUDE INTERNET SERVICE, SURCHARGES, FEES AND TAXES. DEVICE MAY BE REFURBISHED. If you subscribe to plans with monthly minutes allotments, all call minutes placed from both from your home and registered ExtensionsTM phones will count toward your monthly minutes allotment. ExtensionsTM calls made from mobiles use airtime and may incur surcharges, depending on your mobile plan. Alarms, TTY and other systems may not be compatible. Vonage 911 service operates differently than traditional 911. See www.vonage.com/911 for details.

** Certain call types excluded.

www.vonage-forum.com is not an official Vonage support website & is independently operated.
All logos and trademarks are property of their respective owners. All comments are property of their posters.
All other www.vonage-forum.com content is © Copyright 2002 - 2013 by 4Sight Media LLC.

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 Promotion Code or Coupon Codes are required at www.vonage.com to receive any special,
best Vonage cheap deals, free sign up offers or discounts.

[ | | | | | ]

Vonage Forum Site Maps

Vonage | VoIP Forum | How VoIP Works | Wiring and Installation Page Two | International Rate Plans 2 | Internet Phone
Promotion | Vonage Review | VoIP | Broadband Phone | Free Month | Rebate | Vonnage | Vontage | VoIP | Phone Service
Phone | llamadas ilimitadas a Mexico | Latest News | VoIP Acronyms | Deal | Philippines Globe Phone | Site Maps

The Vonage Forum provides the Vonage sign up Best Offer Promotion Deal.
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 Sign up page.


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.33 Seconds and Pages In The Last 60 Seconds
The Vonage VoIP Forum