TAPI Compliant Telephony Device

The Hi-Phone Desktop product family is a CTI TAPI compliant USB / RS232 hardware ( external telephony card device ) and software platforms, featuring a complete telephony card functionality, and supported by a wide variety of well documented integration tools for most programming languages

Go to Device Manager (right click on My Computer, choose Manage and then find Device Manager in the left panel), or right click on Start Menu for Windows 10 and select Device Manager 3. Right click on the hardware device you wish to update and choose Update Driver Software.

The Way2call Hi-Phone is a USB Telephony Device (Board), telephony card device, and replaces a USB voice modem, or TAPI modem in voice Telephony applications for better performance and additional telephony features

When you connect a USB audio device to a Windows 10 Version 1703-based computer the first time, the operating system detects the device but loads the standard USB audio 2.0 driver (usbaudio2.sys) instead of the specific device driver. Write a driver only when necessary. More guidelines are included in Choosing a driver model for developing a USB client driver. USB Device classes. USB Device classes are categories of devices with similar characteristics and that perform common functions. Those classes and their specifications are defined by the USB-IF.

Connect your PC to a Telephone Line / Handset / Headset.
Develop your telephony applications using C, C++, VB, .NET, Delphi, Java and more.
Easy telephony API and fast integration with sample source codes.

Hi-Phone Maestro, external Telephony Card / Board Device Sample Setup Scenario

1. Make sure that an analog phone and analog line are used.
2. (A) - (D) Line 1 - Line 4
3. (E) Business Phone System
4. (F) (Optional ) Connect with telephony headset
5. (G) Connect with PC via USB
6. (H) Power Adapter
7. No PCI or PCI Express Slots required, but USB

*In some countries (e.g. U.K., Germany), and external adapter for the phone and line might be required. Please check whether your local telephony connection standards default to the U.S.

Way2Calls Hi-Phone telephony device product family are External telephony card / telephony board device using USB / RS232 for Plug and Play CTI (Computer Telephony Integration) solutions. Any software application or web page integrating Hi-Phone telephony devices, can have full-featured Telephony functionality such as Make call, Answer-incoming call, Call Progress Detection, Caller ID etc as you are using PCI / PCIe telephony card.

The Hi-Phone telephony devices family offer Integration SDK (Software Development Kit) for software developers with a variety of Simple, Fast and Easy Integration Proprietary API (Application Programming Interfaces) as well as standard API. This allows developers focus on their application instead of dealing with detailed telephony issues, using their favorite Programming Language. The SDK, Currently available for Microsoft Windows 2000/2008/XP/7, supports major industry standard programming languages including C, C++, Visual Basic, .NET (VC++, VB, C#, J#, etc.), Delphi, Java and any other language which can use Win32 API or ActiveX

Way2call and Hi-Phone are registered trademarks of Way2call Communications

Telephony Card Device Product Family Highlights

High Compatibility

Open Architecture

Modular Solution

Cost Effective

Plug and Play Telephony

External USB telephony board device, voice modem

Developer Resource

Community Forum

Applications Using Way2call Telephony Card / Board Device Hardware

• Windows 10 Compatible TAPI
• Call Center agent
• Personal Telephony center with PIM application
• Inbound and outbound calling
• Call Recording
• Voice Mail
• IVR (Interactive Voice Response)
• Caller ID display and Caller ID on call waiting
• Automated calls
• Home Automation
• Queue calls
• Telemarketing
• Central Office subscriber functionality control
• Internet VoIP (Voice Over IP) Converged with Analog Telephone Line
• TAPI PC Answering System/Machine Automation
• Way2call Hi-Phone products family comparison chart
• and more...

Important

This topic is for programmers. If you are a customer experiencing USB problems, see Troubleshoot common USB problems

This topic lists the Microsoft-provided drivers for the supported USB device classes.

• Microsoft-provided drivers for USB-IF approved device classes.
• For composite devices, use USB Generic Parent Driver (Usbccgp.sys) that creates physical device objects (PDOs) for each function.
• For non-composite devices or a function of a composite device, use WinUSB (Winusb.sys).

If you are installing USB drivers: You do not need to download USB device class drivers. They are installed automatically. These drivers and their installation files are included in Windows. They are available in the WindowsSystem32DriverStoreFileRepository folder. The drivers are updated through Windows Update.

If you are writing a custom driver: Before writing a driver for your USB device, determine whether a Microsoft-provided driver meets the device requirements. If a Microsoft-provided driver is not available for the USB device class to which your device belongs, then consider using generic drivers, Winusb.sys or Usbccgp.sys. Write a driver only when necessary. More guidelines are included in Choosing a driver model for developing a USB client driver.

USB Device classes

USB Device classes are categories of devices with similar characteristics and that perform common functions. Those classes and their specifications are defined by the USB-IF. Each device class is identified by USB-IF approved class, subclass, and protocol codes, all of which are provided by the IHV in device descriptors in the firmware. Microsoft provides in-box drivers for several of those device classes, called USB device class drivers. If a device that belongs to a supported device class is connected to a system, Windows automatically loads the class driver, and the device functions with no additional driver required.

Hardware vendors should not write drivers for the supported device classes. Windows class drivers might not support all of the features that are described in a class specification. If some of the device's capabilities are not implemented by the class driver, vendors should provide supplementary drivers that work in conjunction with the class driver to support the entire range of functionality provided by the device.

For general information about USB-IF approved device classes see the USB Common Class Specification

The current list of USB class specifications and class codes is documented in the USB-IF Defined Class Code List.

Device setup classes

Windows categorizes devices by device setup classes, which indicate the functionality of the device.

Microsoft defines setup classes for most devices. IHVs and OEMs can define new device setup classes, but only if none of the existing classes apply. For more information, see System-Defined Device Setup Classes.

Way2call Usb Devices Driver Vga

Two important device setup classes for USB devices are as follows:

• USBDevice {88BAE032-5A81-49f0-BC3D-A4FF138216D6}: IHVs must use this class for custom devices that do not belong to another class. This class is not used for USB host controllers and hubs.

• USB {36fc9e60-c465-11cf-8056-444553540000}: IHVs must not use this class for their custom devices. This is reserved for USB host controllers and USB hubs.

The device setup classes are different from USB device classes discussed earlier. For example, an audio device has a USB device class code of 01h in its descriptor. When connected to a system, Windows loads the Microsoft-provided class driver, Usbaudio.sys. In Device Manager, the device is shown under is Sound, video and game controllers, which indicates that the device setup class is Media.

Microsoft-provided USB device class drivers

Way2call Usb Devices Driver Updater

Related topics