Abstract
It is argued that ISDN computer-aided telephony requires properly architected platforms to satisfy changing application needs during the 1990s. Proper architecting necessitates the use of functionally rich and consistent telephony application programming interfaces (APIs). Other APIs are also needed to support integrated applications. The coexistence of telephony and other APIs must be accommodated in the ISDN driver architecture to make efficient use of D-channel signaling and voice, data, or image communications on the associated B/H channels. This driver may support Open Systems Interconnection (OSI), Systems Network Architecture (SNA), X.25, or other protocol stacks in the same computer using a single ISDN access link. Applications being currently explored show that significant benefits can be realized using incoming call management and LAN-based image server access by means of ISDN. It is envisioned that by the year 2001, a common API will facilitate multimedia applications on multivendor platforms architected within the OSI framework. These platforms will support interconnections of public and private ISDNs and bridging to BISDNs.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">></ETX>
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
