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 : Voice-on-the-net (VON), VoIP, Internet (IP) Telephony -- Ignore unavailable to you. Want to Upgrade?

To: Frank A. Coluccio who wrote (292)	3/16/1998 9:58:00 AM
From: Frank A. Coluccio	Read Replies (1) \| Respond to of 3178

All, Some more important news. Here is the notice of the official creation of the iptel Working Group with its purpose and time line. It's interesting to see how the IETF's time lines are beginning to extend over time, similar to the way the old Bell System's did when it was at its height. Yeah, I know... it aint that bad yet. But very large scale orchestration of services that affect the masses will do that. Also, take note of where the first chair person mentioned works. Also, a click on the highlighted bell-labs link will bring you to some interesting places. Frank Coluccio ---- Re: IP Telephony (iptel) A new working group has been formed in the Transport Area of the IETF. For additional information, contact the Area Directors or the WG Chair. IP Telephony (iptel) -------------------- Current Status: Active Working Group Chair(s): Jonathan Rosenberg <jdrosen@bell-labs.com> Transport Area Director(s): Scott Bradner <sob@harvard.edu> Allyn Romanow <allyn@mci.net> Transport Area Advisor: Allyn Romanow <allyn@mci.net> Mailing Lists: General Discussion:iptel@lists.research.bell-labs.com To Subscribe: iptel-request@lists.research.bell-labs.com Archive: bell-labs.com Description of Working Group: Before Internet telephony can become a widely deployed service, a number of protocols must be deployed. These include signaling and capabilities exchange, but also include a number of "peripheral" protocols for providing related services. The primary purpose of this working group is to develop two such supportive protocols and a frameword document. They are: 1. Call Processing Syntax. When a call is setup between two endpoints, the signaling will generally pass through several servers (such as an H.323 gatekeeper) which are responsible for forwarding, redirecting, or proxying the signaling messages. For example, a user may make a call to j.doe@bigcompany.com. The signaling message to initiate the call will arrive at some server at bigcompany. This server can inform the caller that the callee is busy, forward the call initiation request to another server closer to the user, or drop the call completely (among other possibilities). It is very desirable to allow the callee to provide input to this process, guiding the server in its decision on how to act. This can enable a wide variety of advanced personal mobility and call agent services. Such preferences can be expressed in a call processing syntax, which can be authored by the user (or generated automatically by some tool), and then uploaded to the server. The group will develop this syntax, and specify means of securely transporting and extending it. The result will be a single standards track RFC. 2. In addition, the group will write a service model document, which describes the services that are enabled by the call processing syntax, and discusses how the syntax can be used. This document will result in a single RFC. 3. Gateway Attribute Distribution Protocol. When making a call between an IP host and a PSTN user, a telephony gateway must be used. The selection of such gateways can be based on many criteria, including client expressed preferences, service provider preferences, and availability of gateways, in addition to destination telephone number. Since gateways outside of the hosts' administrative domain might be used, a protocol is required to allow gateways in remote domains to distribute their attributes (such as PSTN connectivity, supported codecs, etc.) to entities in other domains which must make a selection of a gateway. The protocol must allow for scalable, bandwidth efficient, and very secure transmission of these attributes. The group will investigate and design a protocol for this purpose, generate an Internet Draft, and advance it to RFC as appropriate. Goals and Milestones: May 98 Issue first Internet-Draft on service framework Jul 98 Submit framework ID to IESG for publication as an RFC. Aug 98 Issue first Internet-Draft on Call Processing Syntax Oct 98 Submit Call processing syntax to IESG for consideration as a Proposed Standard. Dec 98 Achieve consensus on basics of gateway attribute distribution protocol Jan 99 Submit Gateway Attribute Distribution protocol to IESG for consideration as a RFC (info, exp, stds track TBD)

To: Frank A. Coluccio who wrote (292)	3/17/1998 8:45:00 AM
From: Darren DeNunzio	Read Replies (2) \| Respond to of 3178

VoIP Gateway Hardware. Take a look at this Cisco brochure: cisco.com And this Cisco Press Release: cisco.com =============== Voice Over IP: PBX Consolidation The Cisco 3600 is Cisco's first router to support voice over IP which will allow voice traffic to be transported over existing WAN infrastructures including ISDN, leased line, ATM, and Frame Relay. This solution gives you the opportunity to save long-distance tariffs normally incurred using the Public Switched Telephone Network (PSTN) while providing both the quality and reliability you expect from your telephone service. Additional features include support for fax relay and future interoperability with other H.323 applications. Bandwidth efficiencies include: Voice compression using standard compression techniques such as G.729 Silence suppression Resource Reservation Protocol (RSVP), Weighted Fair Queing (WFQ), multilink fragmentation and interleave ================ Netcom, one of the leading international Internet Service Providers, is currently evaluating VoIP. "We were very impressed with Cisco's 3600 VoIP capability," said Mike Kallet, Netcom's senior vice president of products, technology and business development. "We tested the Cisco equipment over Netcom's backbone between Denver, Colorado and San Jose, California by conducting a business call over the Internet using a speaker phone. The quality of the call was very good." Cisco also will offer new integration capabilities in enterprise networks by extending voice-over-IP technology into high-density voice gateways to aggregate branch offices and enable packet telephony gateways. Cisco's voice-over-IP software architecture will be extensible across many existing Cisco platforms and will provide extremely low latency to enable the highest-quality voice-over-IP solutions available. ================ Do you think this technology could make some of the current VoIP gateway solutions unnecessary ?