With the maze of technologies, products, and standards to choose from, what are you to do when faced with designing a system or picking components? Consider the following issues when choosing a CTI (computer telephony integration) platform:
-- Flexibility of the network. Is it compatible with TCP/IP, IPX/SPX, and NetBEUI?
-- Applications. Is the environment robust enough for multimedia and
telephony applications development?
-- Multitasking. Does the environment allow for multiple and
simultaneous functions to avoid putting calls on hold?
-- Reliability. Is the environment stable enough to ensure that a
mission-critical application, such as call control, won't crash?
-- Open design. Is the API compatible with a wide range of PBX
systems?
-- Media stream. Will the environment handle multiple media devices,
including fax, data, voice, and video equipment?
-- Pricing. Is the API bundled with a comprehensive operating
environment?
-- Scalability. Does the environment support a range of form factors,
platforms, and multimedia applications, as well as high-volume
user traffic?
Flexible C++
Matthew Wilson
My approach to software engineering is far more pragmatic than it
is
theoretical--and no language better exemplifies this than C++.
BYTE Digest editors every month analyze and evaluate the best articles from Information Week, EE Times, Dr. Dobb's Journal, Network Computing, Sys Admin,
and dozens of other CMP publications—bringing
you critical news and information about wireless communication,
computer security, software development, embedded systems,
and more!
A Checklist for Making CTI Decisions
