Revision History

TeleTools 3.7

TeleTools v3.7.0.0 EEP

In this major new release of ExceleTel TeleTools we have focused on fine tuning the wave audio controls, etPlay and etRecord. These are not your average wave audio tools. With features such as memory buffers, fast-forward and rewind, imbedded information, and editing tools, these audio controls are designed specifically for use with telephony devices and telephony applications.

  • Large and even small multi line systems can get bogged down accessing wave data from the disk. Some telephony tools solve this problem by using indexed audio files, often referred to as VOX. The TeleTools approach of using memory buffers is far more flexible. By allowing multiple line devices to share audio data TeleTools reduces the number of open files and virtually eliminates disk access delays, all this while using standard wave file formats supported by many other telephony and non-telephony applications.

Wave data storage is flexible with memory buffers. No longer are you or your application limited to only storing wave files to disk. Wave data may be stored in a database, as resource items within executables, or as standard wave files for use with other applications that support wave files.

  • Voice mail systems and prompt management require the ability to fast forward and rewind while playing wave files. TeleTools allows for flexible positioning of audio playback by seconds, bytes and event percentage!

  • Lots of new logging features have also been added to aid in debugging telephony hardware and software issues.

  • Previous versions of TeleTools automatically allowed the etPlay and etRecord controls to utilize audio CODECs. In some cases this would cause problems. When working with telephony devices it is best to utilize wave files that are in a format that is natively supported by the audio device. For this reason we have added the properties etPlay.Device.CODECsEnabled and etRecord.Device.CODECsEnabled. By default these properties are set to False so that only the native audio formats will be supported. When these properties are set to True then Windows will utilize any available CODEC to convert the audio data in a realtime manner.

  • Help File Changes

We have made a number of improvements to the help file. Some things have moved, some have expanded and others have been added.

  •  The How Do I Do That / FAQ has been flatten to make it easier to find what you are looking for. We have also added similar sections for each of the controls in the "Controls Reference" section.

  • The Programming with TeleTools section has be reorganized to contain the subsections; "Basic Concepts", "Advanced Concepts" and "Completing and Deploying Your Application."

  • The Debugging Telephony Issues section has been added to help you solve telephony hardware and software problems faster.

  • A bunch of topics have been moved from the Appendix to new locations. For example Working with Modems has been moved to "Basic Concepts" under "Programming with TeleTools."

  • A Glossary has been added.

  • Licensing

Previous versions of ExceleTel had limitations to the number of lines for any given edition of the product. For example:

ExceleTel TeleTools 3.6 Express supported 1 line only
ExceleTel TeleTools 3.6 Standard supported 2 line only
ExceleTel TeleTools 3.6 Professional supported 4 lines only
ExceleTel TeleTools 3.6 Enterprise supported unlimited lines

With ExceleTel TeleTools v3.7 we have made this much more flexible.  Any edition can now support a number of different line count configurations.  This has allowed us to provide more economical price points for systems that require only basic features, but more lines.  Click here for details.

  • Changed Properties


  • New Methods



  • New Properties



Recommendation:  Continue reading.

TeleTools v3.7.0.2 EEP

  • WAV_ERROR_INVALIDSTATE was added to errors. If etPlay.Device.Loop is true then setting any of the etPlay.Position properties will cause this error. This was done because you should never fast forward or rewind while the loop option is activated.

  •  Sometimes the etRecord control was causing a GPF when it was destroyed.

  •  When appending to a buffer with etRecord.Device.Append a new buffer handle entry with the same value was placed in the etRecord and etPlay property Source.Buffer.List.

New Properties


Recommendation:  Continue reading.

TeleTools v3.7.1.0

  • This is the first release of TeleTools v3.7 that is available to the general public. The Early Experience Promotion (EEP) is no longer available.

  • The etLine and etPlay Error.Text contained incorrect information.

  • The etPlay and etRecord Source.Buffer.DeleteAfter method was curupting the wave file.

  • Setting etPlay and etRecord TeleScope.Visible property to True while etPlay.Device.Pause was set to True would cause the application to hang.

  • Using the etPlay and etRecord Source.Buffer.DeleteBefore and/or Source.Buffer.DeleteAfter multiple times would cause the buffer to become corrupt.

New Events


New Methods


New Properties


  • A combined log has been added to the TeleScope utility program.

Recommendation:  This is currently the most recent version of TeleTools 3.7.  If you are using an earlier version of 3.7, you should download and install TeleTools v3.7.1.0.   Watch this site for future updates.

End of TeleTools 3.7 version history.


TeleTools v3.6

TeleTools v3.60 EEP (Build 1)

  • Added properties:
        etLine.Call.List      TStrings
        etLine.Call.Count      Integer
        etLine.Connected      TDateTime
        etLine.Disconnected      TDateTime

  • New methods:

  • The following events have had the "CallHandle: Integer" parameter. This indicates for which call caused the event to fire:

Recommendation:  Continue reading.

TeleTools v3.60 EEP (Build 2)

  • New events:

  • New methods:

  • Property changes:
       etLine.Address.BusyModes   etLine.Address.Capabilities.BusyModes
       etLine.Address.CalledIDFlags   etLine.Address.Capabilities.CalledIDFlags
       etLine.Address.CallerIDFlags   etLine.Address.Capabilities.CallerIDFlags
       etLine.Address.CallInfoStates   etLine.Address.Capabilities.CallInfoStates
       etLine.Address.CallStates   etLine.Address.Capabilities.CallStates
       etLine.Address.Capabilities   etLine.Address.Capabilities.Flags
       etLine.Address.ConnectedIDFlags   etLine.Address.Capabilities.ConnectedIDFlags
       etLine.Address.DialToneModes   etLine.Address.Capabilities.DialToneModes
       etLine.Address.DisconnectModes   etLine.Address.Capabilities.DisconnectModes
       etLine.Address.RedirectionIDFlags   etLine.Address.Capabilities.RedirectionIDFlags
       etLine.Address.RedirectingIDFlags   etLine.Address.Capabilities.RedirectingIDFlags
       etLine.Device.CallCount   etLine.Device.ActiveCalls
       etLine.Device.BearerModes   etLine.Device.Capabilities.BearerModes
       etLine.Device.LineFeatures   etLine.Device.Capabilities.LineFeatures
       etLine.Device.RingModes   etLine.Device.Capabilities.RingModes
       etLine.Device.Specific   etLine.Device.Capabilities.DevSpecific
       etLine.Device.SpecificSize   etLine.Device.Capabilities.DevSpecificSize
       etLine.Device.Tones   etLine.Device.Capabilities.Tones

  • New properties:

  • The Transfer sample program has been added for Visual Basic and Delphi.

Recommendation:  Continue reading.

TeleTools v3.60 EEP (Build 3)

  • Conferencing and consultation transfer has been enhanced. If you are using these features make sure to look at the new Transfer sample program.

  •  New events:

  • New methods:

  • New properties:

  • Method changes:
       etLine.Call.CompleteTransfer   etLine.Transfer.Complete
       etLine.Call.Complete3Way   etLine.Transfer.ThreeWay
       etLine.Call.ConsultTransfer   etLine.Transfer.Dial
       etLine.Call.SwapHold   etLine.Transfer.SwapHold

  • This build adds the capability to use the TeleTools controls in a Delphi/C++ Builder TDataModule or Frame.

Recommendation:  Continue reading.

TeleTools v3.60 EEP (Build 4)

  • The etLine.Call.CallerID.Name property will now be updated each time that the etLine.Call.CallerID.FormatName property is modified.

  • The etLine.Call.CallerID.Number property will now be updated each time that the etLine.Call.CallerID.NumberMask property is modified.

  • The same holds true for the following properties:
    etLine.CalledID, etLine.ConnectedID, etLine.RedirectingID, etLine.RedirectionID.

  • The C++ Builder sample applications have been updated from TeleTools v3.5 to v3.6.

Recommendation:  Continue reading.

TeleTools v3.60 EEP (Build 5)

  • The etLine.CallerID.MaskNumber issue which was only present in the ActiveX for  Build 4 was resolved.

Recommendation:  Continue reading.

TeleTools v3.60 EEP (Build 6)

  • The etLine.CallerID.MaskNumber and other similar properties default values have been changed to "000-000-0000;0".

  • New events:

  • New properties:

Recommendation:  Continue reading.

TeleTools v3.60 (Build 7)

  • The State parameter for the etLine.OnAddressForward event has been removed.

Recommendation:  Continue reading.

TeleTools v3.60 (Build 8)

    property etLine.Device.Active is automatically set to False.
  • The etTTConst.hpp file for C++ Builder contained incorrect references to the following TAPI functions:


Recommendation:  Continue reading.

TeleTools v3.60 (Build 9)

  • Visual Fox Pro samples have been added to the installation.
  • ExceleTel TeleTools v3.5 did not trap the  LINE_LINEDEVSTATE/LINEDEVSTATE_REINIT message, version 3.6 does. When this message is received all etLine components will stop firing events. As you may have noticed the parameter cbInst is always x0. This parameter is used by TeleTools to identify which etLine component the message is associated with. Unfortunately TAPI does not offer this information with this message therefore we do not have any 
    way to fire an event!  In a future version we will have a way to handle this better but for now we have decided to turn this off!
  • The following properties were being set to false just before the etLine.OnConnected event:

  • The following property values were lost after the etLine.OnIdle event fired: 

Recommendation:  Continue reading.

TeleTools v3..60 (Build 10)

  • Monitoring for media mode changes with outbound calls now begins during the etLine.OnProceeding event instead of the etLine.OnConnected event. The allows fax detection on out bound calls to be more accurate.
  • In each of the TeleScopes the SpinEdit controls have been converted to Edit controls. The SpinEdit controls was creating problems with C++ Builder and some international versions of Delphi 5.
  • The Borland C++ Builder 3 VCL and samples applications have been added to the installation.

Recommendation:  Continue reading.

TeleTools v3..60 (Build 11)

  • The installation was not properly updating the sample applications if a pervious version of ExceleTel TeleTools was present.
  • The etLine.Call.Connected and etLine.Call.Disconnected properties were not always updated properly when working with only one call.
  • ExceleTel TeleTools was set to work with TAPI versions 1.4 - 2.2. It has been modified to include 1.3 - 2.2. This does not mean that TeleTools will not work with TAPI 3.x.According to Microsoft all applications that support TAPI 2.x will work properly with TAPI 3.x. We have tested this and found it to be true.
  • The etLine TeleScope Log was displaying etLine.OnCallMediaModeChange as etLine.OnMediaModeChange.

    Recommendation:  Continue reading.

TeleTools v3.60 (Build 12)

  • With some devices the call was not being removed from the call list after calling etLine.Call.Transfer (Blind Transfer). The problem had to do with the etLine.OnIdle event firing before TAPI returned the reply message indicating if the transfer was successful.
  • In some cases the etPlay and etRecord controls would cause the CPU utilization to spike for 10 - 50 milliseconds.
  • Setting the etPlay and etRecord property Popup.OnError to true now causes the Windows messages to be logged. The allocation and deallocation of windows handles is also logged.

Recommendation:  Continue reading.

TeleTools v3.60 (Build 13)

  • Delphi 6 support was added.

Recommendation:  Continue reading.

TeleTools v3.60 (Build 14)

  • In some cases spontaneous calls were not appearing in the etLine.Call.List property. In rare cases this could cause an application violation.

Recommendation:  Continue reading.

TeleTools v3.61 (Build 7)    (October 25, 2001)

Builds 1-6 were considered beta.

  • Property changes:
    etLine.TAPI.Version and etPhone.TAPI.Version now hold both the major and minor version numbers. For example TAPI 2.1 will appear as hex 00020001.
  • etLine.TAPI.Subversion and etPhone.TAPI.Subversion have been eliminated.
  • New Methods:
  • New properties:
    etLine, etPhone, etPlay & etRecord now all have an Enabled property
    etLine, etPhone, etPlay & etRecord now all have an ID property
         This is the same as Phone.HookSwitchDevs which will be removed in a later version
         This is the same as Phone.Device.States which will be removed in a later version
  • Event changes:
    etLine.OnCallState, parameters have changed.
    etLine.OnCallInfo, parameters have changed.

  • New events:
  • The documentation has been updated to indicate that the etPlay.Device.Active property should not be set to False in the etPlay.OnLoop event. Instead you should set the property etPlay.Device.Loop = False.
  • In previous versions setting etPlay.Device.Loop = False in the etPlay.OnLoop event handler routine would cause the wave file to play one additional time before stopping.
  • In some cases when the etPlay control would return the error WAV_ERROR_FILEOPEN it would continue to report the error after changing the property etPlay.Source.FileName.

Recommendation:  Continue reading.

TeleTools Version 3.62 (November 15, 2001)

  • New Methods:

Several new methods have been added to make it even easier to access the device specific features of your telephony hardware.


  • Other Issues:

The properties etPlay.Timer.Enabled and etPlay.Volume.Enabled properties would interfere with the etPlay.Enabled property. If either of these properties where set to false then the etPlay.Enabled property would also be set to false causing a number of problems including the etPlay.Device.Count property to have a value of zero.

Recommendation:  Continue reading.

TeleTools Version 3.62 Build 3 (February 15, 2002)

  • Property changes:

    The following properties are no longer available at design time, they are only available at run time. These properties will be forced to False when the etLine.OnOffering event fires. These values may be modified in the etLine.OnConnected event:



This will cause an "Error Reading Form" with Borland's Delphi and Borland's C++ Builder. Ignoring this error will cause the form to be updated properly. 

In the ActiveX the property etLine.TransferConsultCall has been changed to be Read/Write. This may cause a problem when upgrading with some environments such as
Visual Fox Pro. You may need to recreate the etLine control. Be careful because environments like Visual Fox Pro will cause the event handler routines to be lost. This is not a problem with other environments such as Visual Basic. 

In some cases the etLine.Call.Hangup event would time out and a strange error message would occur. This problem was discovered when Dialogic slightly changed the way they were returning some TAPI reply messages. TeleTools has been modified to handle situations of this nature.

You may now set the etLine.Device.MediaModes.Active property to any value. We stopped doing the validating this against etLine.Device.MediaModes.Available because of bugs reported in TSP's that do not report the available media modes properly.

If you attempt to place a call when the etLine.Device.Active property is set to False you may experience an Access Violation error. Now you will received the error LINEERR_UNINITIALIZED.

A "Dump Properties" button has been added to the TeleScope Log tab. Clicking this button cause the current property values for the control to be listed in the the log. This is a helpful debugging tool.

A "Marker" button has been added to the TeleScope Log tab. Clicking this button puts a line of stars in the log. This is a helpful debugging tool.

A "Print" button has been added to the TeleScope Log tab. Clicking this button cause the log to be printed. This is a helpful debugging tool.

When the TeleScope.Log.Active property is set to false the log is no longer cleared. This is a helpful debugging tool.

The TeleScope utility will now save the property values for etPlay.Source.FileName and etRecord.Source.FileName.

Recommendation:  Continue reading.

TeleTools Version (March 15, 2002)

  • Property Changes

etLine.ConferenceRemoveCall was not available in the ActiveX.

The property etLine.Address.Name is now Read/Write.

The property etLine.Call.ID is now Read/Write. This is useful when creating and using ExceleTel TeleTools AddOns.

  • Other Issues

In some cases setting etLine.Call.GatherDigits.Active to false would cause the error LINEERR_INVALDIGITMODE.

When more than one application would have access to a single line device the error LINEERR_INVALCALLHANDLE would be generated in some cases. This would happen because after the message LINE_CALLSTATE with the parameter IDLE is received that the message LINE_CALLINFO message for the same call is received. ExceleTel TeleTools disposes of the call structure when the IDLE message is received. Microsoft defines LINECALLSTATE_IDLE as "The call exists but has not been connected. No activity exists on the call, which means that no call is currently active. A call can never transition out of the idle state." Since the call is finished it should be safe to assume that no further messages would be forthcoming. However this is not true. For some reason TAPI has decided to inform one or more of the applications that the number of monitors for this call has changed. When this message is received by TeleTools, etLine looks in it's list of available calls. When the call is not found it creates a new one. Next etLine calls the TAPI function lineGetCallInfo to gather the latest information about the call. This is the function that would returning the error LINEERR_INVALCALLHANDLE. We have take this situation into consideration and modified etLine to automatically dispose of the new call. However the error will still be reported.

  • New Methods:





Recommendation:  Continue reading.

TeleTools Version (March 27, 2002)

  • This release includes support for Microsoft's Visual Studio .NET and sample applications for Visual Basic .NET.

  • Visual Studio .NET creates a wrapper for ActiveX's. Several of the TeleTools methods have a function parameter named "Params". It turns out that this is a reserved word in VS.NET. To resolve this conflict the TeleTools parameters named "Params" have been changed to "sParams". This should not cause any problem with code that you already have in place because the parameter names are used by the code completion pop-ups in the IDE.

  • In some cases the property etLine.Call.CallerID.Number would contain a null character at the end. All spaces and control characters are now trimmed from all TeleTools string type properties.

Recommendation:  Continue reading.

TeleTools Version (October 21, 2002)

  • The sample programs have been modified to be a bit more modem friendly.

Recommendation:  Most users should upgrade to TeleTools v3.7.  There is a fee for upgrading to TeleTools v3.7.  For upgrade fee information, click here.

Support for TeleTools v3.6 will no longer be available after November 30, 2003.

If you do not require TeleTools v3.7 or do not wish to upgrade at this time, and you are using a version prior to TeleTools v3.6.3.2, most users should download and install TeleTools v3.6.3.2.  There is no fee for this update.

Please note that a password is required for access to discontinued and retired products.  To obtain the password please contact us at +1 (919) 233-2232 or [etPasswords (at)].

End of TeleTools 3.6 version history.

TeleTools v3.5

Beginning with v3.5, the TeleTools product line was unified under a single code base.  That is, all editions -- Express, Standard, Professional, and Enterprise -- use the same installation file.  Feature availability is determined by your license key.

TeleTools v3.50 EEP (Pre 106)

  • No revision information is available prior to build 106.
  • Due to direct update link limitations, you may link here even if you have a later build.

TeleTools v3.50 EEP (Build 106)

  • Support for Delphi 5 has been added.
  • Documentation has been added for each of the sample applications.
  • Vast improvement in the time required to create the etLine and etPhone controls.
  • When the property etLine.Device.Active was set to False the etLine.Terminal properties were attempting to call the TAPI functions to update their state. This was causing an error since the device was no longer active.
  • When the event etLine.OnMediaModeChange fired TeleScope was not displaying the new value of etLine.Call.MediaMode.
  • etPlay and etRecord TeleScopes were not displaying ".." as part of paths when the SourceFileName properties were set.
  • The TeleScope program menu options for selecting the development environment where not working properly.
  • The etLine.Comm.Enabled property was added to allow the etLine.Comm properties to be enabled and disabled.
  • The etLine.Call.BearerMode property is now Read / Write. It use to be Read only.
  • The following methods would not work properly with the ActiveX in Windows 95 and Windows 98: etLine.DeviceConfigure, etLine.SetLocation, etPhone.DeviceConfigure.
  • With a TeleTools Express and Standard license the etLine.Terminal properties are not available. etLine was automatically enabling etLine.Terminal which could cause a License Exceeded error.
  • etLine.Terminal.Enabled now defaults to False.
  • etLine.Call.ID has been added to show the value of the TAPI dwCallID that is returned by the lineGetCallInfo function.
  • The property etLine.TranslatePhoneNumber was added to allow the TAPI function lineTranslateAddress to be used. When this property is set to true the etLine.Call.PhoneNumber property will be translated according to the current location's dialing properties.
  • The etLine.Address.ID property is no longer saved at design time. This helps to speed up the creation of the etLine control at design time and run time.
  • etLine.Call.Owner is now a Read/Write property. It was Read Only.
  • etLine.Call.MediaMode is not reset after a call. It can now also be set prior to making a call. This is especially important when making data calls with modems. This property needs to be set to LINEMEDIAMODE_DATAMODEM just prior to calling etLine.Call.Dial for data calls.
  • etLine.Address.ID was not being used when calling etLine.Call.Dial. The etLine.Call.MediaMode must be set to a value other than zero for etLine.Call.Dial to use etLine.Address.ID. This is important when you need to select the Address to be called on. For example some telephony line devices have multiple address. Use this property to select the address to be used. For example the Nortel USB 2 line phone has one TAPI line device with two addresses. Each address is a physical telephone line.
  • The installation automatically registers the etTT35.OCX file. The "ActiveX Register" and "ActiveX Unregister" menu options have been removed from the installation.
  • The STDVCL32.DLL and STDVCL40.DLL files have been added to the installation. You may now use the STDVCL32.TLB and STDVCL40.TLB or DLL files for redistribution of the ActiveX file (etTT35.ocx). See the redist.rtf file in the Help subdirectory for details.
  • etPlay.Device.Pause would only work once.
  • If the AboutSerialNumber property for any of the TeleTools controls is not set then the INVALID_SERIAL_NUMBER error will occur when the controls' Device.Active property is set to true.
  • In some cases the ActiveX would not work properly when redistributed to a computer that did not have TeleTools v3.5 installed.

TeleTools v3.50 EEP (Build 108)

  • The draft help file has been added to the installation.   The Help.xls  spreadsheet and the TeleTools v2.33 help files have been removed from the installation.
  • A minor memory leak has been repaired in the etRecord control.   Approximately 18 bytes would be lost with each recording. The memory would be freed when the application was closed.
  • Modifying the Windows Dialing Properties would cause an exception in applications written with the etLine control.
  • The etLine.Terminal properties are now able to be set multiple times allowing for a wider range of settings. See the etLine.Terminal documentation for details.

TeleTools v3.50 (Build 110 - Final Release)

  • When setting the TeleScope utility program menu option "TeleScope | Log | Count", all TeleScopes had to be visible otherwise an error would occur.  This has been repaired.
  • The help files will continue to be enhanced over the next few weeks.  Please check back for updated versions.

TeleTools v3.50 (Build 112)

  • The changes in this build do not effect the VCL's for C++ Builder or Delphi.
  • The Visual Basic sample applications now display a message box if the INVALID_SERIAL_NUMBER error is received. This happens when the About.SerialNumber property for a control has not been set properly. See the following help topics:
    1. Recommended Reading | ExceleTel TeleTools Serial Numbers,
    2. Controls | Features that are Common to all Controls | Properties Common to all Controls | Common Properties - About
  • Visual Basic works a little differently than other development environments in that it stores non-browsable type properties in the form definition. This causes properties such as the etLine.LineAppHandle to be stored. If the value of 0 is stored in this property then everything is fine. If any other value is stored then you will receive the LINEERR_INVALIDAPPHANDLE error. This can happen when your save your application while the Form containing the etLine or etPhone controls is being edited. To resolve this issue the etLine.LineAppHandle and etPhone.LineAppHandle properties are now Read Only.

TeleTools v3.51

  • The help file has undergone major changes.  A large amount of new information has been added.
  • The etPhone.Speakerphone.SpeakerOnly property was not working properly.
  • The etLine.Terminal.Enable property has been eliminated.
  • The etLine.TerminalActiveModes works differently. It is a set of bit flags that indicate if the individual modes are active or inactive. The flags may also be set to modify the states of the Terminal Modes.
  • The etLine.Call.Active property was not being updated properly.
  • The etLine.Call.Active property was added to the Call tab of the etLine TeleScope.
  • The hints for the TeleScope.Log.Lines was incorrect for etPhone, etPlay and etRecord.
  • etLine calls the TAPI function lineSetStatusMessages. When used with a system from Telia this would cause the error LINEERR_OPERATIONUNAVAIL when etLine.Device.Active was set to True. This is a non-critical error and no longer causes the operation to fail.
  • etLine.Call.MediaMode and etLine.Call.BearerMode properties are now reset to zero after a call is idle.
  • Setting etLine.Call.BearerMode when a call did not exist would cause the error LINEERROR_INVLAIDCALLSTATE.
  • In the ActiveX the properties etLine.PopupOnTAPIMessage and etLine.PopupOnTAPIReply were not working properly.
  • In the ActiveX the property <>.TeleScopeLogLine is now available.

TeleTools v3.52

  • Borland C++ Builder 5 support has been added.
  • The sample applications have undergone minor changes.
  • The help file has undergone minor changes.

TeleTools v3.53

  • The etLine.OnCallEnded event would not fire in some cases.
  • In some cases etRecord would cause a exception when recording with voice modems on Windows 2000.
  • The Delphi sample applications were not being installed correctly.

Recommendation:  Most users should upgrade to TeleTools v3.7.  There is a fee for upgrading to TeleTools v3.7.  For upgrade fee information, click here.

Support for TeleTools v3.5 will no longer be available after March 31, 2002.

If you do not require TeleTools v3.7 or do not wish to upgrade at this time, and you are using a version prior to TeleTools v3.53, most users should download and install TeleTools v3.53.  There is no fee for this update.

Please note that a password is required for access to discontinued and retired products.  To obtain the password please contact us at +1 (919) 233-2232 or [etPasswords (at)]. 

End of TeleTools v3.5 version history.

TeleScope v3.5

TeleScope v3.5 EEP (Pre 106)

  • No revision information is available prior to build 106.
  • Due to direct update link limitations, you may link here even if you have a later build.  Please find your current version below and continue reading. 

TeleScope v3.5 EEP (Build 106)

  • Changes are consistent with those detailed above for TeleTools v3.5 EEP (Build 106).

TeleScope v3.5 EEP (Build 108)

  • Changes are consistent with those detailed above for TeleTools v3.5 EEP (Build 108).

TeleScope v3.5 (Build 110)

  • Changes are consistent with those detailed above for TeleTools v3.5 (Build 110).

TeleScope v3.51

  • Changes are consistent with those detailed above for TeleTools v3.51.

This is currently the most recent version of TeleScope v3.5.  If you are using an earlier version, you should download and install TeleScope v3.51.

Please note that a password is required for access to discontinued and retired products.  To obtain the password please contact us at +1 (919) 233-2232 or [etPasswords (at)].

End of TeleScope v3.5 version history.

TeleTools Express

TeleTools Express v1.20 - 9/29/97

  • This was the original release of TeleTools Express v1.20 dated September 29, 1997. You may link to this spot even if you already have the 10/21/97 release described below. We will resolve this linking issue in a future release.

TeleTools Express v1.20 - 10/21/97

  • This release includes 2 redistributables that were inadvertently omitted from the prior release (9/29/97). They are STDVCL32.DLL and STDVCL32.TLB. These files are required only to support the etLine.DeviceList property and only if you are using the ActiveX component (not the VCL). They are required for your development environment only to support the sample applications included with TeleTools (because the sample apps use the etLine.DeviceList property) or to support your use of etLine.DeviceList in your applications. You only need to redistribute these files if you use the ActiveX component and the etLine.DeviceList property in your applications.
  • There were some minor additions and enhancements in the help system that are of use to most users.
  • There were no code changes in the components, so the version number did not change.

Do not upgrade to TeleTools Express v3.00 or higher if you are using multiple lines in your application.  Multi-line users who wish to upgrade will need the appropriate license of TeleTools v3.7.

TeleTools Express v3.00 - 3/8/98

  • TeleTools Express no longer supports multiple active lines. If you require the ability to simultaneously support more than one telephony line then you will need to use TeleTools Standard.
  • Support for Visual C++ and Access has been added.
  • When using Visual Basic 4 make sure that the etLine.TeleScopeVisible property is set to False before exiting your application (or the IDE if you are in development mode). Otherwise an application error will be reported. This is due to an issue with how VB4 closes an application.
  • ExceleTel TeleTools Express will not work with FoxPro at the current time. ExceleTel TeleTools Standard v2.2 does work with FoxPro.
  • An application error would sometimes occur when exiting your application if the TeleScope had been in use, this has been fixed (except for VB4 applications per note above).
  • With some telephony devices the etLine.Dial and etLine.Hangup methods would sometimes cause an error due to a timing problem, this has been fixed.

TeleTools Express v3.03 - 7/8/98

  • Support for Delphi 4 and C++Builder 3 has been added.
  • Support for capturing caller ID information before the first ring (when available) has been added.
  • Buffer sizes increased for capturing of device information for devices that do not return proper errors.

TeleTools Express v3.04 - 10/20/98

  • The version number of the controls used for Delphi2, Delphi4, C++ Builder 1 and C++ Builder 3 remained 3.03.
  • A minor visual change was made to the TeleScope for the Delphi3 and ActiveX controls.
  • For development environments that do not automatically load the etLine.AboutSerialNumber property you can now enter it manually in the property editor. This includes Microsoft Access and Visual FoxPro 6.
  • TeleTools Express now supports Microsoft Access and Visual FoxPro 6.
  • Due to a known bug in Microsoft Visual FoxPro 5, TeleTools Express 3.04 will not work. Microsoft repaired the problem in Visual FoxPro 6.
  • A bug was fixed in the sample program that would cause the "Not 100% TAPI Compliant" message to be missed.
  • In some cases a DAX error would appear when the etLine control was created or first placed on a form.

Recommendation:  Most users should upgrade to TeleTools v3.7.  There is a fee for upgrading to TeleTools v3.7.  For upgrade fee information, click here.

Support for TeleTools Express v3.0 will no longer be available after March 31, 1999.

If you do not require TeleTools v3.7 or do not wish to upgrade at this time, and you are using a version prior to TeleTools Express v3.04, most users should download and install TeleTools Express v3.04.   There is no fee for this update.  However, if you are currently using TeleTools Express v1.20 or earlier, and you are using multiple lines in your application, do not upgrade to TeleTools Express v3.00 or higher.  Multi-line users who wish to upgrade will need the appropriate license of TeleTools v3.7.

Please note that a password is required for access to discontinued and retired products.  To obtain the password please contact us at +1 (919) 233-2232 or [etPasswords (at)].

End of TeleTools Express version history.

TeleTools Standard

TeleTools Standard replaces and is the current upgrade path for these discontinued products: TeleTools-VCL32, TeleTools-Delphi 32, TeleTools-ActiveX, and TeleTools-OCX32.

TeleTools-Delphi 32

TeleTools-OCX 32

  • These products were renamed to TeleTools-VCL32 and TeleTools-ActiveX.  Later, they were both incorporated into the TeleTools Standard product.



  • TeleTools Standard replaces and is the current upgrade path for these discontinued products.

TeleTools-Delphi 32 v2.10

TeleTools-OCX 32 v2.10

  • The etPlay and etRecord controls have been added to allow you to play and record wave files on any valid Windows wave device including properly equipped voice modems and other telephony devices.
  • All methods now return a boolean (True or False) value to indicate if they were successful.
  • All TeleTools controls have four properties for returning error information, Error, ErrorString, DeviceError and DeviceErrorString.
  • Some etTAPI methods have been transformed into properties.
  • A number of etTAPI methods and properties that were only available after a line device was opened are now available before the open method is called.
  • The etTAPI.OnRinging event as been changed to fire every time that a ring is been detected.
  • The etTAPI.OnOffering event has been added to supply the same functionality as the old etTAPI.OnRinging event.
  • You can now monitor for changing media modes of a call.
  • Calls can be handed off to other applications. This is very useful for sharing a line with your fax application.
  • The MonitorOnly property has been changed to PrivilegeMonitor. This along with PrivilegeNone property and the the addition of the PrivilegeOwn property give you a great deal of flexibility for working with multiple telephony applications.
  • A call can now be ignored without being dropped (hung up) by setting the etTAPI.PrivilegeMonitor and etTAPI.PrivilegeOwn properties to false.
  • The etTAPI.CallOwer property indicates if your application is the owner of a call.

TeleTools-Delphi 32 v2.10a

TeleTools-OCX 32 v2.10a

  • The VMail sample program has been added to show how a voice mail system can be created.
  • The etPlay.AvgBytesPerSec and etPlay.BlockAlign properties have been added to allow for finer analysis of the format of a wave file.
  • The etPlay.DelaySeconds property was added. The default value is 0. This can be used to force a delay when the playing of a wave file finishes. This is not needed for most telephony hardware.
  • The etPlay.FileName property assumes the file extension '.wav' if none is given.
  • The etPlay.FileName property can now accept multiple files. This allows several files to be played without a delay between each file. Each file is separated by a comma.
  • The etPlay.FileName property assumes the path of the first file for all files not given a path. Example legal values for the etPlay.FileName property:     c:\data\wave\1,100,30,2,dollars,and,50,3,cents     c:\data\wave\YouHave.wav,3,c:\moredata\Messages
  • The etPlay.Start method now has a boolean parameter that indicates if it should wait for the file to finish playing before continuing execution. For example:
  • The etRecord.DelaySeconds property was added. The default value is 0. This can be used to force a delay when the recording of a wave file finishes. This is not needed for most telephony hardware.
  • In some cases the etRecord.Save method would save the format header information improperly. This would cause a problem playing a wave file created with etRecord.

TeleTools-VCL32 v2.11

TeleTools-ActiveX v2.11

  • The main purpose for this release of TeleTools is to officially change the name of TeleTools-Delphi 32 to TeleTools-VCL 32. This version fully supports Borland C++ Builder, so "Delphi" in the name is misleading.

TeleTools-VCL32 v2.12

TeleTools-ActiveX v2.12

  • A problem with destroying the etRecord control while recording has been fixed. This would cause the wave device to lock up until the application was closed.

TeleTools Standard v2.20

  • TeleTools-VCL 32 and TeleTools-ActiveX have been combined to create TeleTools Standard.
  • The etPlay and etRecord controls have been modified to work better in multi-threaded applications.
  • The property etRecord.BufferSeconds now defaults to 1 second.
  • The etTAPI.TransferCall method has been added for telephony devices that support the TAPI call lineBlindTransfer. First set the etTAPI.PhoneNumber field to the number to be transferred to then call the etTAPI.TransferCall method.
  • The etTAPI.HoldCall method has been added for telephony devices that support the TAPI call lineHold.
  • The etTAPI.UnholdCall method has been added for telephony devices that support the TAPI call lineUnhold.
  • The etTAPI.Dial and etTAPI.Hangup methods now wait until the Telephony Service Provider (TSP) indicates that the request is complete before continuing execution of your code.
  • The etTAPI.CallBegin and etTAPI.CallEnd properties are now read/write instead of read only.
  • Additional error messages were added for etPlay and etRecord. In some cases the earlier releases would only display a number.
  • The etTAPI.OnTAPIReply event is used to capture Windows LINE_REPLY messages that are generated by calls to TAPI functions. This is useful when accessing the TAPI.DLL's directly. Also see the etTAPI.CallHandle, etTAPI.LineHandle and etTAPI.LineAppHandle properties.
  • The etTAPI.SetLocation method causes the "Dialing Properties" dialog box to be displayed allowing users to modify the location settings.
  • When the method etPlay.Stop is called the event etPlay.OnStopped will not be fired.
  • Under normal operations etPlay saves the current device volume setting prior to playing a wave file then restores it when finished. When set to False the etPlay.VolumeEnabled property allows this process to be skipped. The default value is True. This is especially useful when working with a multi-line telephony board that offers a way to set the volume for all lines such as Music Telecom (NewVoice) cards from MUSIC Telecom.
  • Although the new etTT2.ocx ActiveX file uses the same name as in the previous version the internal version number is different as are the CID registry entries. This will cause a problem in some development environments such as Visual Basic. You will need to Unregister the previous version of the ActiveX and Register the new. To unregister the old version use the TeleTools-ActiveX | Unregister ActiveX option on your start menu to unregister the ActiveX with the Windows operating system. To register the new ActiveX use the ExceleTel TeleTools Standard | ActiveX Register option.
  • After registering the new etTTS22.ocx file you may need to modify your source code so that it will recognize the new ActiveX. For example in Visual Basic each of our controls will now appear as a blank-looking control. These will need to be deleted from the form then add back the etTAPI, etPlay and etRecord controls (as needed).
  • The new etTT2.ocx file can be used by your old applications without recompiling.

TeleTools Standard v2.21

  • The etPlay.VolumeEnabled property now defaults to False. This was done to alleviate some confusion due to the fact that voice modems using the UnimodemV Telephony Service Provider (TSP) do not support the Windows API call "waveOutSetVolume". Therefore the volume can not be set for playing wave files over the phone line.
  • The etPlay.Volume property now reports errors properly.
  • Errors related to setting the volume are now reported properly when the etPlay.VolumeEnabled property is set to True and etPlay.Start is called.
  • CallerID was not available with the Altigen phone system due to an error message being presented differently than with other telephony equipment vendors. Altigen actually is returning the information more accurately than some other telephony equipment vendors. This change will alleviate future problems if other telephony equipment vendors decide to report CallerID information in the same fashion.
  • The etTAPI.OnTAPIReply event is now triggered when the etTAPI.Answer, etTAPI.Hangup, etTAPI.HoldCall, etTAPI.UnholdCall and etTAPI.TransferCall methods are used.
  • The property etTAPI.CallAddress has been added. It is used to indicate the address that a given call is utilizing.
  • Support for Borland C++ Builder version 3 has been added. The etTT2.hpp file for Borland's C++ Builder 3 is located in the directory "C:\Program Files\ExceleTel\TeleTools Standard\Bin\CppBuilder3".
  • If the telephony device makes the Caller ID information available at the beginning of a call, it is now available in the etTAPI.CallerIDName, etTAPI.CallerIDNumber and etTAPI.CallerIDFlags properties.
  • All directory references to Borland's C++ Builder 1 have been changed from "C++Builder" to "CppBuilder1".
  • The etTT2.hpp file for Borland's C++ Builder 1 has been moved to the directory "C:\Program Files\ExceleTel\TeleTools Standard\Bin\CppBuilder1".

TeleTools Standard v2.30 - 7/24/98

  • TeleTools is now licensed based on the number of lines supported. TeleTools Standard (2-line) supports 2 lines. TeleTools Standard (Unlimited) supports as many lines as are practical based on your configuration and TAPI.  TAPI is capable of supporting 128 lines. However, other limitations in your configuration may limit the number of lines practical to less than 128. If you purchased a license for a prior version of the TeleTools Standard product line (including TeleTools-Delphi32, TeleTools-VCL32, TeleTools-OCX32, and TeleTools-ActiveX), your existing serial number will provide unlimited line support for version v2.3.
  • This version incorporates some significant help file enhancements. Most of the information that was previously available only in the release notes is now also included at the appropriate place in the main body of the help file.
  • A significant new sample program has been added. It is called IVR4Line. This program provides significant information in the following areas:
        - multi-line applications
        - concatenating wave files to play a phrase
        - capturing and acting on DTMF digits
        - interrupting waves files during play over phone line
        - auto answer
        - remote disconnects
        - simple IVR tree
  • The etPlay.DelaySeconds and etRecord.DelaySeconds properties are being supplemented by the etPlay.Delay and etRecord.Delay properties. These new properties are in milliseconds rather than seconds.  In this release of TeleTools both types of properties may be used. Although you will notice that the DelaySeconds properties will cause the Delay properties to change.  Additionally the Delay properties will cause the DelaySeconds to change, although it will be rounded.  TeleTools uses the value in the Delay properties.
  • etTAPI.Comm, etTAPI.CommClass, and etTAPI.CommHandle have been added to allow TeleTools to perform async data transfer in conjunction with the Windows Comm API. You will need to be familiar with the use of this API in order to utilize this functionality. Future versions of TeleTools will include more complete and easier to use object based access to this functionality.

TeleTools Standard v2.31 - 7/29/98

  • A problem with the etTAPI.OnCallEnd event and the etTAPI.CallEnd property has been fixed.

TeleTools Standard v2.33 - 10/22/98

  • The etTAPI.CommHandle was not being closed in some situations.  This would cause the LINEERR_RESOURCEUNAVAIL error to be reported when the etTAPI device was closed after processing a call, and then reopened.  This CommHandle issue could also manifest itself in other situations.  For instance, CallerID may have been reported correctly on the first call, but not reported correctly on subsequent calls.  This issue is only applicable to devices that support a CommHandle, such as modems.
  • There were also some updates to the help file and sample applications.

Recommendation:  Most users should upgrade to TeleTools v3.7.  There is a fee for upgrading to TeleTools v3.7.  For upgrade fee information, click here.

Support for TeleTools Standard v2.x and its precursors will no longer be available after March 31, 2000.

If you do not require TeleTools v3.7 or do not wish to upgrade at this time, and you are using a version prior to TeleTools Standard v2.33,   most users should download and install TeleTools Standard v2.33.  There is no fee for this update.

Please note that a password is required for access to discontinued and retired products.  To obtain the password please contact us at +1 (919) 233-2232 or [etPasswords (at)].

End of TeleTools Standard version history.


TeleTools-VCL16 replaces and is the current upgrade path for these discontinued products: TeleTools-Delphi 16 and TeleTools-Delphi.

This version supports only Delphi 1 and may only be used to create 16-bit applications.

TeleTools-VCL16 v1.13 - 5/29/98

Recommendation:  Most users should upgrade to TeleTools v3.7.  There is a fee for upgrading to TeleTools v3.7.  For upgrade fee information, click here.

Support for TeleTools-VCL16 and its precursors is no longer available.

If you do not require TeleTools v3.7 or do not wish to upgrade at this time, and you are using a version prior to TeleTools-VCL16 v1.13, most users should download and install TeleTools-VCL16 v1.13.   There is no fee for this update.

Please note that a password is required for access to discontinued and retired products.  To obtain the password please contact us at +1 (919) 233-2232 or [etPasswords (at)]. 

End of TeleTools-VCL16 version history.