Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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 : LAST MILE TECHNOLOGIES - Let's Discuss Them Here -- Ignore unavailable to you. Want to Upgrade?

To: Frank A. Coluccio who wrote (4959)	8/12/1999 6:51:00 PM
From: DenverTechie	Read Replies (1) \| Respond to of 12823

Frank, I knew it would be just a matter of time before you weighed in on this one. I am by no means an expert on this topic, and figured that most, if not, all of these items have already been debated on the VoIP thread. By experts like you who know many of these endless details of push and shove regarding IP issues. You're right of course, that my response was fairly unbounded, and it was from the "let's look at what the common cable operator sees when he thinks about loading up his HFC network with IP telephone" perspective. Really, I don't think your average cable system operator in any of those trial cities I mentioned in my response would even know those questions to ask in your feedback, from what I've seen at the system level. Maybe at the corporate level, like AT&T Labs or Bell Labs, but not the cable guy in Salt Lake. This can be seen in the system's reliance for cable modem technology from RoadRunner, Excite@Home, and HSAC. This is a major learning curve at the system level for anything spelled IP. The response I gave was by no means exhaustive, just illustrative at an extremely high level of some of the very sticky technical and operational issues confronting VoIP for cable systems, and some reasons why a migration plan from circuit-switched cable telephone to IP based cable telephone is the logical way to go for the next several years. Cable just can't wait for VoIP to be ready for prime-time. They need to deploy voice/data services now, while preparing for IP telephone. And do it without having millions of dollars of stranded circuit-switched voice equipment in their plant.

To: Frank A. Coluccio who wrote (4959)	8/13/1999 11:34:00 AM
From: Frank A. Coluccio	Read Replies (1) \| Respond to of 12823

OT - Re: Service Provider Disaster Recovery/Business Continuation Some notes of interest concerning the Chicago power outage from the NANOG List: Date: Thu, 12 Aug 1999 16:31:15 -0500 From: <SD> Subject: Re: POWER: Chicago, IL power problems [As of yesterday at 4PM:] Commonwealth Edison now estimates it will be 18-22 hours before the power is restored. The blackout area has already expanded once, and CE may have to shutdown more areas to complete repairs. The affected area is bound by Adams Street on the north, Roosevelt Road on the South, Dearborn Street on the West and Michicgan Avenue on the east. ISP/Telco infrastructure affected: Currently ISPs are reporting that Ameritech ISDN service center can't test any ISDN lines. Two major CLEC/IXC facilities are in the blackout area, and are on backup power. Several smaller CLEC/ISPs also report they are on backup power. If you get out your Mapquest, the Chicago NAP is outside the current blackout area, and is currently unaffected. It has its own backup generator just in case (see, some good things do come from Y2K :-) Since the 18-22 hour estimate exceeds the normal 4-8 battery life telco's use on equipment in non-CO office buildings, there may be some additional outages as muxes and equipment in out-of-the-way places run out of power.