North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: Vonage complains about VoIP-blocking

  • From: Hannigan, Martin
  • Date: Wed Feb 16 01:36:51 2005

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On Behalf Of
> John Levine
> Sent: Tuesday, February 15, 2005 9:02 PM
> To: [email protected]
> Subject: Re: Vonage complains about VoIP-blocking
> >
> >
> >The FCC is investigating -- it's not even clear if it's 
> illegal to do 
> >that.
> For what it's worth, my ISP is owned by my rural ILEC, and I just
> cancelled my Vonage service because it had become unusable.
> However, the problem was not TFTP, it was rotten inbound voice
> quality, combined with a complete inability to contact anyone at
> Vonage by e-mail or phone to do anything about it.  My link is a T1,
> and it has plenty of spare inbound capacity.  Traceroutes suggest that
> Vonage is suffering from packet loss problems at gateways between
> their NSP and mine, or perhaps the packet loss within my NSP (Sprint)
> was too much for it.
> I switched to Lingo which works fine.  Its box uses NTP to set the
> time, then http to configure.

Odd regarding the Vonage connection. Their sitting on UU from where I
can see and I have excellent transit to them from Comcast.

I've tested Vonage, only because I had it, with the Semena NE2000 Network
Test Device and introduced multiple error, path, and latency issues and it 
stood up very well. At one point, I jacked up the latency to 4000ms and I
still able to place, communicate, and drop calls effectively. I was 
very surprised at how it handled that large introduced latency.

I don't know about Vonage support. Never tried it.