User guide

144 RealCT Direct API Developer Guide
Chapter 5: MVIP-90
Defining MVIP-90
Multi-Vendor Integration Protocol (MVIP) provides
communications standards that allow boards in a PC to
communicate with each other. MVIP works independently of
other computer buses. It can work in a PC, between PCs, in a
PBX, and in other computer-based hardware.
The MVIP bus provides a way to interconnect telephony
resources, even if those resources are provided by different
vendors. With voice, fax, video, and automatic speech
recognition cards connected in a single bus, you can develop
fully-integrated computer telephony applications.
MVIP is comprised of two main parts: the MVIP bus, and the
MVIP switch block. The MVIP bus provides the physical
connection between boards. The MVIP switch block provides the
mechanism for data switching between telephony resources.
Only the RTNI series network boards and Vantage PCI boards
provide a switch block and can make physical connections
between resources. RTNI series boards do not provide VP
resources, but they can switch calls to VP resources on other
boards. The Vantage VPS, Vantage VRS, and RDSP/xx000
boards do not have a switch block. They provide VP resources
over the MVIP bus.
Brooktrout supports two levels of MVIP: MVIP-90 and
MVIP-95. RDSP, Vantage VPS, Vantage VRS, and RTNI boards
all use the MVIP-90 software and hardware standard.
Applications written using the MVIP-90 software standard only
support MVIP-90 hardware. The Vantage PCI series boards
support the MVIP-95 software standard. The MVIP-95
standard supports both MVIP-90 and H.100 hardware.
The API for Windows operating systems has functions for both
the MVIP-90 and MVIP-95 standards. Be sure you use the
functions appropriate for the boards in your system.
w Use MVIP-90 functions for RTNI, RDSP, Vantage VPS
or Vantage VRS boards.
w Use MVIP-95 functions for Vantage PCI and
RealBLOCs PCI boards.
For more information about the MVIP-95 standard, see
Chapter 6, MVIP-95, on page 183.