P2P or ENUM Saves Vonage?

VonageWe've been down this road before with claims of a Vonage workaround to get past the Verizon patent issue, only to have our hopes dashed. But now word comes today late yesterday from Bloomberg that Vonage has a patent workaround that could save its VoIP service from being shutdown over the Verizon patent litigation. Apparently its new technology can be installed through software downloads and shouldn't be costly to deploy, according to Jeffrey Citron, CEO of Vonage.

"We will begin rolling these workarounds out shortly, hopefully in the next few weeks, and we believe they will work," Chief Executive Officer Jeffrey Citron said on a conference call today.

I would really like to know how a software download helps bypass the Verizon patents and why didn't Vonage think of this before? And what precisely is Vonage installing on customer's ATA (analog telephone adaptor) that supercedes Verizon patents? I have to review the Verizon patents, but I believe one of them involves mapping an IP address to a phone number. Currently, Vonage does this in a centralized fashion using their centralized servers. So when someone calls a Vonage customer, the Vonage servers map the PSTN call to the customer's IP address and then route the call over IP to the customer's ATA device. It is highly plausible that the Verizon patent specifically mentions this query process as being performed in a "centralized" fashion. So it is my hypothesis that Vonage is getting around the patent issue by moving from a centralized query method to a decentralized query method.

There are two possibilities for this. One, Vonage could be downloading to each ATA some sort of peer-to-peer (P2P) technology that moves the query database down to each subscriber's ATA device. This is a bit risky from a security and reliability standpoint and I don't know if this could scale to millions of users. Though Skype is an example of a large-scale fairly reliable P2P network. I'm also not sure each ATA's firmware could handle this type of upgrade. Vonage literally has dozens of different kinds of ATAs or phone devices, such as a the Cisco ATA-186 to stand-alone Vonage phones such as the Uniden Vonage phone, as well as all-in-one wireless routers with Vonage capabilities such as the Linksys WRTP54G.

The second option is that Vonage is downloading to each ATA the ability to query a third-party ENUM server, such as ones run by Stealth Communications, Verisign, and NetNumbers. ENUM, is a standard protocol for resolving phone numbers into IP addresses. It was originally developed to link consumers' phone numbers to various IP services, but the protocol is being used extensively to interconnect carriers’ VoIP networks. No doubt Verizon uses the technology to interconnect with other carriers. Verizon would be hard pressed to sue Vonage if Vonage switched to a 100% ENUM environment considering all the carriers use ENUM.

Whether it is P2P or ENUM to skirt the Verizon patent issue is still a hypothesis on my part and I apologize for not researching Verizon's patents in more detail since I've been working on some other projects. There could be a third option which escapes me at the moment. I'll try and do some more research and post what I find here. Stay tuned...
| 1 Comment | 0 TrackBacks

Listed below are links to sites that reference P2P or ENUM Saves Vonage?:

P2P or ENUM Saves Vonage? TrackBack URL : http://blog.tmcnet.com/mt/mt-tb.cgi/32481

1 Comment

I wonder how the workaround does actually work. I read the two name tranlations and there's so much legal mumbo jumbo that it's hard to tell exactly what it's about. But from what I understand it's not name translation (telephone number to IP address, URL to IP address, vice versa) that Verizon claims in the patent. The claim is a domain name server that makes a conditional analysis and translates to a particular IP address based on the aforementioned (legal patent word!) analysis. In the order of injunction, in particular, Vonage is enjoined from using the XML script on the inbound proxy, and what I guess is that the XML script is what processes inbound calls.
So maybe this script will be on the customer's telephone adapter instead of on a centralized server, thus working around the patent. What I'm wondering is what will happen if the customer's equipment is down, I have no idea how certain features like call forwarding while the network's down will work - or how it can go to a message without going to a different server.
The claim, incidentally also pertains to non-realtime packet-switched traffic (non-voice).
I'm not incredibly familiar with domain name servers, but what are NAPTR records, and if they point to a different IP address based on an user-set analysis, wouldn't this be considered infringement as well?
I don't think there is any real innovation with this patent - Verizon got to it first. And I think infringement of this patent exists in several applications on the internet. Even my router's domain name server is infringing. That's because it runs a conditional analysis of the URL and if it's not in it's tables will give another domain server's IP address. And what about DDNS?
Look at this from dyndns.org:
"Offline URL feature allows HTTP requests to your domain to be redirected to another site when your server is offline "

This is a centralized conditional name server, isn't it? If your server is offline, you get the option to redirect to another IP address. HMMMM - infringement.
Why so much infringement of this patent?
Because it's obvious that anyone skilled in the art can do it.

Leave a comment

Recent Activity

Friday

  • Tom Keating queued Star Trek
  • Tom Keating queued Stardust
  • Tom Keating queued The Fountain

Thursday

Wednesday

  • Tom Keating tweeted, "Worst Google News Headline Ever! - No public viewing at Neverland, but Michael Jackson may get laid: I was happi.. http://tinyurl.com/nrlsjo"

More...

Recent Comments

  • http://openid.aol.com/drdaraban: Yes, I confirm antonioj's comment, both skype and the app read more
  • cmytroops: I was browsing the net and cam across a great read more
  • mike: Sorry if this is off topic but I’m thinking of read more
  • @NumberGarage: Our military service men and women should be driving new read more
  • https://www.google.com/accounts/o8/id?id=AItOawlacBYIyCFI8mz5HS_pdsnSDV1wLz6Vgc8: We have implemented over 50 VoIP systems in the last read more
  • Theo Barton: Its a good phone. I have had a lot of read more
  • https://me.yahoo.com/a/ea7WMvNu2Mlud7dBwQPAAus9JCfo9qE-#27391: I don't want to go through all the problems, I read more
  • Claudio G.: I contacted these folks via e-mail recently (June 2009)and they read more
  • Kinjudah De- Morgan: I am using a strong satelite receiver and a Gateway read more
  • dell gx620: I have just had my second Dell. Thinking by spending read more

Subscribe to Blog

    View my Microsoft MVP Profile:

Blogroll

Entry Archives

Around TMCnet Blogs

  • Communications and Technology Blog - Tehrani.com:
    Problems at Joost
  • On Rad's Radar?:
    Bells Giving Up on Landlines?
  • VoIP & Gadgets Blog:
    Worst Google News Headline Ever! - No public viewing
  • Communications and Technology Blog - Tehrani.com:
    Heading to Rhode Island
  • First Coffee:
    SugarCRM Studied, Broadband 'Crucial,' EGain, OOCOSPI, NetSuite's Zander
  • On Rad's Radar?:
    Why Can't DC See What We See
  • The Readerboard:
    Tougher Actions To Save Telemarketing
  • VoIP & Gadgets Blog:
    eBuddy for iPhone Supports Push Notifications
  • Latest Whitepapers

    TMCnet Videos