As I mentioned last week, I've been using the Vonage IP phone over my DSL circuit. It's working nicely so far. The quality falls somewhere between hardwired POTS and cellphone, for the most part, though it does vary with the Internet weather. During a long interview the other day (52 minutes to Vancouver, BC, from Keene, NH, for $2.62), there were some really bad patches. As it happened, I was recording the interview for InfoWorld, and because of those rough spots I've decided to transcribe parts of it myself rather than send the recording to InfoWorld's transcriptionist. But at other times, I've forgotten that I'm talking over IP rather than POTS, until I wander by my DSL router and see all the lights blinking like crazy.
The system is so easy to use that the technically-inclined are likely to trip themselves up trying to find ways to make it harder. I assumed, for example, that I'd need to forward a port through my NAT to be able to accept inbound calls. Not so. Evidently it originates and then holds open a connection. The only requirement is that your DSL router offer DHCP service. You plug in the Cisco ATA 186, push its single button, pick up your phone handset, and type 80#. A voice speaks the IP address that was acquired, and then you get a dial tone.
The Web-based configuration service enables you to do some interesting things. If you tell it to handle your voicemail, the messages spool up at the website, where you can randomly select them for playback. What with buffering delays and audio file-format issues, though, this feature so far hasn't turned out to be as useful as I had imagined.
You can also forward calls to another number, and doing that in a self-serve manner is a real eye-opener. I was expecting a call over the weekend, then had to go out for a few hours, so I forwarded the Vonage to my cellphone, with the Vonage's answering service as a backup. Slick.
Web acccess to call logs is also extremely nice. The data isn't delivered as XML, but easily could be, and I can think of lots of useful things to do with it.
I spoke with the Vonage folks today about the prospects for getting direct access to the digitized voice or the SIP signalling. It's possible in theory, but in practice the packet headers are encrypted (a nice security precaution), and they haven't documented how to reproduce the decryption and packet assembly that currently happens inside the ATA 186. Right now, they're focused on building out a basic voice service. But they absolutely agree that lots of useful integration can, and eventually will, be done.
Assuming nothing happens to stop it, of course. Denton, Menard & Isenberg lay it out nicely:
IP Telephony (The Bellhead Vision of Telephony)
- Works from the existing business model of telephone calls time x distance x bandwidth = revenues;
- Relies on international settlements to allocate revenues between carriers;
- Relies on contribution and subsidies to achieve universal services;
- The network ends in the call agent, just as it used to end in the Class 5 switch;
- The protocols it operates upon are proprietary, and not end-to-end (E2E) in the sense that Microsoft uses a proprietary code;
- All state is kept away from the end-users device;
- Provides Quality of Service assurances;
- IP Telephony is a subset of Next Generation Networks, but, in view of its master-slave design philosophy, services continue to be defined from the centre of the network.
Internet Telephony (The Nethead View of Telephony)
- Works from a new business model: always on, the world is a large free calling area;
- Telephony is fully integrated into a portfolio of Internet services;
- The network ends in the end-users device;
- The end-user can define services;
- Protocols are end-to-end, and open. Linux is the example of an open code. TCP/IP is an example of an end-to-end protocol;
- Substitutes speed (bandwidth) for Quality of Service (QoS) and provides best efforts service;
- Internet Telephony is a part of Next Generation Internet Services, whose nature will be as various and unpredictable as was the addition and overlay of the World Wide Web on top of the Internet.
[ Bellheads versus Netheads]
I'm becoming intensely curious about how this is going to play out.
Former URL: http://weblog.infoworld.com/udell/2002/10/28.html#a489