Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: koverzin@ntmtv.uucp (Raymond Koverzin)
Newsgroups: comp.dcom.telecom
Subject: Re: Host-to-Switch Interfaces, ANSI T1S1
Message-ID: <13493@accuvax.nwu.edu>
Date: 8 Oct 90 17:38:15 GMT
Sender: news@accuvax.nwu.edu
Organization: Northern Telecom, Mtn. View, CA
Lines: 26
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 732, Message 8 of 11


In article <12658@accuvax.nwu.edu>, vances@xenitec.on.ca (Vance
Shipley) writes: 

>In article <12606@accuvax.nwu.edu> David Gurevich <dgurevic@
 dhlmis.dhl> writes:

>>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.

>IBM have a tool box called CIT (Computer Integrated Telephony) for the
>AS/400.  DEC have a similiar offering.

CIT is actually an offering from DEC.  I used to work at Mitel on the
switch-to-computer link Mitel calls, Host Command Interface (HCI).  We
were working with DEC to help them define the application interface
for CIT, which was for their VAX minis.

I believe IBM's version is called Callpath.


Raymond Koverzin