As of VBVoice 5.6, TAPI TTS is not supported anymore.
TAPI is a Microsoft standard for Windows telephony. It defines both a single front-end API for application or toolkit developers and a back-end SPI (Service Provider Interface) that allows Windows to access telephony hardware and telephony services. For a voice card or PBX to be accessible through TAPI, the hardware vendor must supply a TAPI Service Provider (i.e. a driver) specific for their hardware.
TAPI has existed for many years. Today, most telephony equipment on the market comes with a TAPI Service Provider and therefore may be accessed by TAPI applications.
However, it is important to understand that availability of a Service Provider does not guarantee a problem free integration. Although TAPI is a standard, the hardware vendors are free to pick and chose which parts of the specification they implement and which they leave out. Consequently, each TAPI application should be carefully tested with every Service Provides it is to work on.
VBVoice is integrated with TAPI. The TAPI interface is used primarily for PBX connectivity (for voice cards, a native API integration offers more flexibility and better performance). VBVoice does not support TAPI modems.
Pronexus has tested VBVoice with TAPI Service Providers for Mitel PBXs.
VBVoice on TAPI supports Nuance speech recognition Set the following INI file settings to configure Nuance for TAPI:
[Nuance]
NuanceCSP=0
DynamicAlloc=0
Each TAPI line is mapped to a VBVoice channel, which allows your application the same access as to the regular voice lines. As a result, TAPI is transparent to the VBVoice application.
Before running VBVoice on TAPI, you should verify the proper operation of the Service Provider and underlying hardware. Microsoft provides a good tool for manually exercising TAPI functionality, called TAPI Browser. However, working with the TAPI Browser requires advanced knowledge of the TAPI architecture and programming model.
|
Read About: |
|
|
|