Sample Programs

Technical Notes

Sample Programs

Click here for a complete list available sample programs provided by ExceleTel.

Here is a list of sample programs written specifically for the Way2CallHi-Phone:

Technical Notes

The following is found in the Help File for ExceleTel TeleTools

Using Non-voice Modems for Voice Calls

There are some issues involved in using non-voice modems to dial voice calls. These issues become apparent with TeleTools and/or TeleScope, but they are originating at a lower level within Windows Telephony and the modem hardware.

The issues of working with non-voice modems to dial voice calls are related to differences between the actual capabilities of the modem device and the capabilities that are reported by the Windows Telephony API (TAPI) and the Unimodem (or UnimodemV) Telephony Service Provider (TSP). These reported capabilities originate with the INF file used during modem installation. The first symptom of this issue appears when the property etLine.Device.Active is set to True and the error LINEERR_INVALMEDIAMODE [8000002F] is returned.

NOTE: If you are using a voice modem and Windows 95 or Windows 98 and the LINEERR_INVALMEDIAMODE error message is returned then you should check with your modem manufacturer to see if they have updated INF files for your modem. In many cases they make the INF files available on their web site. From time to time manufacturers will update these files so be sure to check regularly. You may also need to install the UnimodemV TSP if you are using Windows 95. UnimodemV is installed as part of Windows 98.

So what causes this error? One of the first steps required when using TeleTools (and TeleScope) is to select which telephony device is to be used (in TeleTools, this is via setting etLine.DeviceID or etLine.DeviceName). At this point TeleTools (or TeleScope) queries TAPI for all media modes reported as available for this device. TeleTools then sets the etLine.Device.MediaModes.Available and etLine.Device.MediaModes.Active properties to contain all of the media modes reported as available. This coupled with the fact that the default settings for the etLine.Privilege properties are as follows causes the previously mentioned error.

     etLine.Privilege.Monitor True
     etLine.Privilege.None False
     etLine.Privilege.Owner True

The Possible Resolutions:

Modifying the etLine.Device.MediaModes.Active and etLine.Privilege properties prior to setting etLine.Device.Active to true may allow you to get some limited functionality. The table below explains the capabilities that will be available with different combinations of property settings. Some details about the etLine