Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!wuarchive!mailrus!accuvax.nwu.edu!nucsrl!telecom-request From: vances@xenitec.on.ca (Vance Shipley) Newsgroups: comp.dcom.telecom Subject: Re: Host-to-Switch Interfaces, ANSI T1S1 Message-ID: <12658@accuvax.nwu.edu> Date: 27 Sep 90 01:29:19 GMT Sender: news@accuvax.nwu.edu Reply-To: vances@ltg.UUCP (Vance Shipley) Organization: SwitchView - The Linton Technology Group Lines: 74 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 10, Issue 683, Message 8 of 11 In article <12606@accuvax.nwu.edu> David Gurevich writes: >It seems that ANSII T1S1 subcommettee is trying to define a set of >specs called the Switch - to - Computer API (SCAI). SCAI would provide >common ground for any host to communicate to with any switch. Nothern Telecom have an interface of this type now; Meridian Link. AT&T, Mitel and others have them too. All are incompatable. >This means that all kinds of applications may be developed on the host >computer that would be able to add to the switch capability/ >functionality. A sophisticated development environment, rich in >labor-saving tools could be provided for this application development. >Data network interfaces could be easily added. IBM have a tool box called CIT (Computer Integrated Telephony) for the AS/400. DEC have a similiar offering. >Is there a large market for this kind of a product? I think there is. Today the best way to sell a switch, PBX or CO, is to be able to fit neatly into the customers business environment. This usually involves multi-vendor scenarios. With this new enabling technology it is possible to do things never before possible. When a customer presents a need for a feature that does not exist in the current switch software it may be possible to implement it on an AP (Auxiliary or Adjunct Proccessor). The AP might be a Unix PC or mini dedicated to the switch or an application running on the corporate mainframe. Five years ago many in this industry were trying to convince us that the PBX would be the office computer of tomorrow, doing both switching and business computing! Consumers were not, and are not, interested in this. What they want is equipment that does it's intended function reliably, economically and integrates with equipment from other vendors performing their functions. An AS/400 and a Meridian 1 make a better platform for office automation than a new ALLINONE by StartUp, Inc. The key of course is seamless integration, hopefully on an open interface (non-proprietary). >What would be common applications? The most often cited application is one in which incoming calls are routed to ACD (Automatic Call Distribution) agents while customer profiles are extracted from the computer and sent to the agents computer screen. This is based on the availability of the calling party number, an ISDN feature. Subsequent transfers to other agents would cause the computer to forward the customers account to the next agent's screen. Some more inventive applications include: - Database query from an LCD equipped phone (look up part number,etc.) - Display incurred call charges in real time on LCD display - E-Mail retreival from LCD phone - Enhanced call waiting information (Persons Name) >Who would buy it? No one without applications. >What are the potential regulatory problems? Sorry that's not my problem :-) Vance Shipley SwitchView - The Linton Technology Group 180 Columbia Street West Waterloo, Ontario N2L 3L3 CANADA (519) 746-4460 vances@ltg.on.ca.UUCP