AddTapi.NET 5.0 adds support for conference calls with three or more parties. The application can use TapiLineSetupConference(TapiCall, TapiCall, Int32) or TapiCallCompleteTransfer(TapiCall, Boolean) resolved as a 3-way conference to setup a conference call. Additional parties can be added to the conference using TapiCallPrepareAddToConference and TapiCallAddToConference(TapiCall) methods.

This version includes new audio engine that supports audio playback and text-to-speech in applications that run as a service. With AddTapi.NET 5.0 you can develop Windows services that play .wav files and speak to the callers using text-to-speech. Both TapiCallPlay(String) and TapiCallSpeak(String) can be used in Windows service applications without any problems.

New version adds TapiAppLineDeviceState event that fires when the state of the line device changes. The application can use this event to find out when the line goes out-of-service and back in-service (TapiLineDeviceStatusIsInService property), when the line is connected/disconnected to TAPI (TapiLineDeviceStatusIsConnected property) or when the message waiting indicator turns on/off (TapiLineDeviceStatusIsMsgWaitOn property).

Version 5.0 adds TapiLineDeviceStatusDeviceSpecificInfo property to obtain device-specific information about the line status. Avaya IP Office system uses this property to provide a lot of additional information about the line/extension, including call forwarding/DND information, number of read/new voicemail messages, user login information and much more. Please contact us for more informaiton and we will provide a code sample that shows how to use this feature of the Avaya IP Office phone system.

Starting from version 5.0, AddTapi.NET assemblies located in the installation folder are compiled for .NET 4.0 and will not work with earlier versions of .NET Framework. If your applicaiton is targeting .NET 2.0 or 3.x, please reference Traysoft.AddTapi.dll located in the NET2 folder of your AddTapi.NET installation.

- Incoming calls were reported as outgoing on some phone systems with non-standard TAPI drivers.

- Implemented a workaround for outgoing calls on Tadiran Coral IP PBX. The TAPI driver for the Coral system does not list any addresses that support outgoing calls and AddTapi was showing an error.

- Version 5.0 uses 8kHz 16-bit audio format on Avaya IP Office for better audio quality.

- TapiAppOutgoingCall event was not fired when establishing dial-up connection.