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 : 3Com Corporation (COMS) -- Ignore unavailable to you. Want to Upgrade?

To: Ken D who wrote (35898)	11/1/1999 2:19:00 PM
From: The Phoenix	Read Replies (1) \| Respond to of 45548

I understand. It looks like the COMS solution is a two box solution... one - the NBX which does call processing; and two the ConeXtions box which does the gateway function. This gateway is an NT platform. The question is what API is the call control/call processing written to. If it is TAPI then NBX isn't Unix. If it's say Java API or some proprietary API then it is Unix. HOWEVER, doing so could limit the number of applications available to NBX since most application developers are writing telephony apps to TAPI. Furthermore I believe Nortel (don't know about CSCO) has an integrated gateway/call control product - a one box solution built on NT and using TAPI API's. I understand that client telephony features are written to TAPI and in fact I believe NetMeeting is written to TAPI as well...but the underlying application control is at the server. The apps could be written to any API. The question is what API is NBX using. It's not clear from the documentation. I did however get confused since the telephony solution COMS is using is two boxes... one is NT the other - NBX is ... I guess Unix. OG