SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Voice-on-the-net (VON), VoIP, Internet (IP) Telephony -- Ignore unavailable to you. Want to Upgrade?


To: Stephen B. Temple who wrote (2368)1/13/1999 12:11:00 PM
From: Roger Bass  Respond to of 3178
 
Stephen and others,

Frank Coluccio and I started an exchange on the ATHM thread that perhaps belongs here. I'm very interested in VoIP, but more from an applications focus than a network/technology focus, as these posts will make clear. Here's Frank's post, and I'll copy my response in other post:

To: +ahhaha (4175 )
From: +Frank A. Coluccio Monday, Jan 11 1999 10:42PM ET
Reply # of 4265

AHhaha, re:

>>How is that different than having two lines bound together?

Let me count the ways...

Jay, re: your comment:

>>But I'm gathering from that discussion that we're still pretty far away from that.

For the sake of brevity, I'll attempt to answer both of you with one reply ;-)

True, the fancy appliance- and PC-based voice stuff, if it is going to be offered straight from T/TCI's menu of options, will be at least far enough into the future to be significant, at least for those of us who are impatiently anticipating those kinds of features.

This may be one of those areas that will greet some prospective users with some strange revelations and surprises. Especially for those of us who are anticipating the next level of voice and video to include significant enhancements to the experience.

Those will come, but they wont be the initial standard offerings right out of the gate, IMO. [They could be implemented at any time, however, on PCs, say, as individual users elect to do so. But it is not the intent of this post to discuss user initiatives on their PCs. This post addresses some of the parameters and the challenges that the next gen telco - in this case, T/TCI - must face, and overcome.]

One of the things that T must do, in addition to supplying adequate field powering for lifeline criteria, etc, if they are to be successful in supplanting the ILECs in the voice sector, is this:

They must devise methods of re-utilizing residential telephone cabling and wiring, as well as the telephone instruments themselves, in such a way as to ensure absolute transparency at the time of implementation, and beyond.

This means that there will be several modes of voice usage in the home over a cable modem connection:

(1) standard twisted pair premises distribution and the same-o same-o telephone extensions throughout the home (nothing changes here, in other words), and

(2) all other Internet-enabled forms of telephony. This mode has yet to be defined in its entirety, and never will.

Therefore, we are not talking about a simple, straightforward one-size-fits-all kind of voice feature here. Moreover, if I were to guess, I think that the priority will be to deliver the "nothing-fancy" Option 1 above first, with embellishments to follow (or implemented on an individual case basis by users independently, once their hooks are in place).

But for certain, in order to draw customers to the voice option, the MSO is going to have to guarantee to them that they will not have to go out and buy all new handsets and rewire the home for Ethernet. That'll come much later for most adopters.

Having said that, the solution is not straightforward, because the home STB or its adjunct unit will need to simulate many of the signaling conditions of the old copper loop. Ringing current, especially, will be needed to sound the ring.

Another differentiation will exist in the area of "web-tone" (always on) mode versus the legacy dial tone (per the present mode).

Explanation: Those who elect to continue to receive the legacy POTS variant of voice over the new cable-iphony STB infrastructure will see no difference. This will comprise the vast majority of new users, IMO. While those who take advantage of the "always on" attribute of IP networking will need to adapt in other yet-to-be-standardized ways.

We're all going to be in for a learning curve with the the latter option, because the IP address will follow you no matter where you go (i.e., your phone calls will always find you!). Learning how to administer this ubiquitous and omni-present shadow, in itself, is going to be a real trip.

I just thought that I would introduce these facts here, skimpy as they seem in this form (since I'm trying to keep it brief), and since we're discussing some relatively near term (next year) real possibilities, where T's intentions are concerned.

So, keep in mind that there are going to be many modes of voice, ranging from the oldest legacy POTS to the futuristic, where voice over cable-iphony is concerned. And where the former POTS variant is concerned, I don't see any reason why T/TCI or whomever can't realize at least the same revenues as those being garnered by the ILECs, minus an incentive (or savings pass-along) of 5%-to-10%, perhaps.

Why give away more, when you've already bagged the sub? This revenue stream, especially the one derived from the subscriber who elects the POTS variant, will last for quite a long time, with a gradually reducing cost to the carrier, and a correspondingly gradual reduction in charges to the subscriber.

That's the way it goes. Comments and corrections welcome.

Best Regards, Frank Coluccio



To: Stephen B. Temple who wrote (2368)1/13/1999 12:12:00 PM
From: Roger Bass  Read Replies (2) | Respond to of 3178
 
Stephen,

here's the post I made on ATHM, in response to Frank:

Frank,

your post made many of the points that I, in my more muddled way, was trying to get at. A couple of observations:

You divided voice usage over cable into two categories: (1) standard POTS plant and (2) all the rest. I believe that there is subvariant of (2) that is also medium-term accessible, because it also relies mostly on 'legacy' plant - namely the PC (plus, possibly a connected handset).

To set the scene: the IP network is always on, and so, potentially is the PC. In this case, one could imagine something looking very much like a phone handset being connected directly to the PC. There are several ways this could be used:

1) Outgoing call initiated from PC-phone
2) Outgoing 'call' initiated from PC
3) Incoming regular call, ie call to existing phone number
4) Incoming 'web-call', ie a call to a web-phone IP address (not the usual phone number)

I'll explore some characteristics and examples of each:

1) Outgoing PC-phone call
This can be used in much the same way as the regular phone handset, to dial any phone number. However, because calls would be placed through an internet telephony server, certain numbers (say telephone yellow pages), might initiate a web/call, ie a simultaneous web and voice connection. Here, the web session (on-screen) would probably be controlled by the called service (ie an agent, or voice / DTMF responses from the caller). For example, you might pick up the handset, press the 'Yellow Pages' button, and say 'Shoe repairers near to here'. (This might be to an agent, or could be an automated service). The service would have the address passed through, and would automatically find, and show a list and map of the 10 nearest businesses on screen, and start reading a voice description.

2) Outgoing call from PC. This is fairly similar to the scenario above, with two variants. One is that a local application (say an address book) would have buttons to initiate a call - you might hear the ringing tone over speakers, and then pick up the handset when it's answered. The other variant would be a call initiated from a button on a web page. In this case, the button could simply be saying 'dial this number' or, more interestingly, initiating a call to some combined web/phone CTI application. (There's potentially some ambiguity around who exactly is initiating the call, and indeed, paying for it). An application here might be while browsing around an e-commerce site (perhaps for some high-value product or service), this button would let you get help or advice from a customer service agent, who might also help you navigate around the site.

3) Incoming regular call. Mostly this is less interesting. The LEC, or the device that drives the old telephones and their wires, sends a 'ring' signal to the PC-phone too. However, if this were a call from someone who was also using a PC-phone (and ITSP), some kind of other connection could be started in mid-call (a video connection, whiteboard, sharing data, whatever). Even for calls from a regular telephone, the PC could use caller id to show (and perhaps announce) who was calling.

4) Incoming web call. Here, the call is placed to, essentially, an IP address not a phone number. The ring tone might be different, or only the PC phone might ring. On answering, the connection could be just voice, or a video call, or include some other kind of display on the screen. You might want to have some control of the session that you'd be accepting - the service might announce what kind of call this was, from whom, and let you decide.

Clearly some of the applications I describe are not first stage, especially those that depend on many people or companies having new equipment.

It does seem to me though that a relatively simple handset device connected to a PC (and perhaps a few compelling services on the back end) could be easy to deploy, once an installed base of PCs connected to always-on medium/broadband networks exists.

Incidentally, Microsoft recently launched a 'Microsoft phone' that does some of the things that relate just to phone, answering machine and address book functionality.

I'd be interested in any thoughts people have about how the phone connects to the PC. Could it work when the PC is off? Is the phone connected to the PC, which is connected to the network, or could it be the other way round?

- Roger