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.

Microcap & Penny Stocks : FNet=Internatl Voice/Fax/Data&Video Services ViaInternet -- Ignore unavailable to you. Want to Upgrade?

To: EdH who wrote (281)	6/2/1998 1:34:00 AM
From: RinConRon	Respond to of 609

Ed... www.computertelephony.org. I can thank Temp for it.

To: EdH who wrote (281)	6/3/1998 11:47:00 PM
From: Stephen B. Temple	Respond to of 609

If you have any serious questions, don't hestitate to e-mail ken after going through his web site. This is what he posted on Yahoo a few days back. computertelephony.org If you look at the "new" PBX market with UnPBX's (PC based PBX's) and the traditional PBX's that open up more and more to standards. You will easily see which the most likely path will be concerning IP-based telephony in the corporate environment. Today you network the PBX's with e.g. least lines . You often do this in parallel with the corporate WAN. It don't take a genius to see the advantage with a single infrastructure. (smaller monthly fees, less administration and more...) These corporate PBX networks offer Network ACD's, centralised operator and other functionality you don't get if the PBX's were connected over the POTS. If you would "just" connect these PBX's over traditional stand alone IP-telephony gateways your of just as bad as the POTS. What needs to added is a more advanced protocol like QSIG. By adding a QSIG compliant Gateway on the backplane in the PBX you could handle about 15 or more simultaneous calls on a 2Mbit leased line instead of 30 as of today. Using IP based routing you always have "direct" contact with all networked PBX's, as it works today with least lines you could have several tandem nodes. By putting the gateway function in the PBX you can use the PBX's LCR-software to route the calls. You have a single point of administration. You don't have to buy E1/T1 for connecting stand-alone gateways. You don't have to dial 8 for a IP-telephony outside line the LCR will take care of that business. Look out for IP-telephony on the backplane from Nortel (they will take the MICOM gateway product and implement the technology on the Meridian 1 backplane) and Ericsson (the will do QSIG on the backplane!). This is not far away! mid 1999! If you look at the concept UnPBX, again you don't have to be a professional annalist to figure out these PC-based PBX's will have both traditional POTS trunks and Ethernet H.323 trunks. If you have both trunks you better be able to route traffic from one trunk to another,,, so they will act as an IP/PSTN gateway. How about the terminal side then ? Of course they will there have to be both H.323 terminals as well as standards POTS phones. In best cases they will also have digital system phones. You can get a PC-based systems with analogue phones that can answer calls from the internet and make / receive POTS calls. (combine 2 PC-based products like Interactive Intelligent Enterprise Interaction Center and Netspeaks gateway and you have a webbased Call Center that could connect calls to the EIC's phones. WAIT A MINUTE, I just had a look at Interactive Intelligent homepage. They actually have IP-telephony in their next version. Here's a clip from their site (www.inter-intelli.com): EIC 2.0 also breaks new ground with its built-in support for voice over IP (VoIP If EIC use the 2.4 Kbit/s per concurrent call, you could have some fun calculating how many calls a 10Mbit Ethernet can hold. If you get 25% performance out of your Ethernet, you can carry over 1000 simultaneous calls, not bad! If you look at computertelephony.org you find some pictures of UnPBX's and traditional PBX configurations with both POTS and IP trunks. Regards Ken Persson