ReleaseNotes8:TAPI

This roadmap describes the V8 (that is, pbx800.wsdl based) TAPI driver implementation.

This article is generated automatically. Do not edit! Please see the disclaimer before using the information presented here!

V8 Release

The V8 TAPI Release Version. Definition

New Features

Support for LINECALLDISCONNECTMODE_*

Status	Closed
Id	6984

including LINECALLDISCONNECTMODE_PICKUP

Support for lineSendUserUserInfo

Status	Closed
Id	52198

Provides limited support for sending text messages to users.

Treat each PBX8 Device as a separate TAPI Line

Status	Closed
Id	52988

All user devices (incl. all fork destinations) of a single PBX object are represented as a separate TAPI line (all with same address). This allows to create and accept calls on individual devices. Also, TAPI applications can restrict monitoring to individual devices.

Support for lineGenerateDigits

Status	Closed
Id	52989

This allows users to generate DTMF tones during a call.

Support for lineSetupTransfer

Status	Closed
Id	52990

Compatibility for TAPI applications that insist on creating a consultation call instead of a normal call using lineMakeCall. Although this is not necessary with innovaphone TAPI, there are applications out there which use this function.

Support for lineDial

Status	Closed
Id	52991

Allows users to dial extra digits during the call establishment phase. Also required for applications which use lineSetupTransfer.

Calling line ID in lineMakeCall and lineSetupTransfer

Status	Resolved
Id	52992

This allows users to create calls with lineMakeCall or lineSetupTransfer which carry a different calling line id.

Support for lineCompleteTransfer LINETRANSFERMODE_CONFERENCE

Status	Closed
Id	52993

Allows users to set up a 3PTY conference using transfer mode LINETRANSFERMODE_CONFERENCE

Treat presence-only Devices as separate TAPI Lines

Status	Closed
Id	52994

There are SOAP based applications which synchronize the presence status of an extern device (e.g. a mobile phone not treated as a mobility target) with a PBX object's presence state. Such objects can now be monitored with standard TAPI applications (showing a virtual call when the presence activity is "on-the-phone").

Support for linePark/lineUnpark

Status	Closed
Id	52995

Allows users to park/unpark calls.

Basic Logging in Release Version

Status	Closed
Id	53100

Enables users to install a release version that provides basic logging with minimal impact on runtime performance and no risk of disk hogging.

Support for LINEADDRCAPFLAGS_ORIGOFFHOOK and LINEADDRCAPFLAGS_DESTOFFHOOK

Status	Closed
Id	54227

Enables applications to invoke calls where the destination phone goes off-hook automatically (provided PBX configuration allows for it).

Other new Features

52996

admin

Support for RedirectionID, RedirectingID, CallerID, CalledID, ConnectedID, CalledParty

V8 Change Requests

These are change requests applicable for TAPI V8, which are considered for implementation Definition

New Features

[!01.10.10] Support for multi-Party Conferences

Status	Assigned
Id	53063

Allows users to set up a conference. Involves lineSetupConference, lineAddToConference,lineRemoveFromConference. This might be implemented using PBX bc-conf objects.

Other new Features

53800

ckl

[15.02.11] tapi: notify held/retrieved status on far end

V8 Hotfix 1

The V8 TAPI, Hotfix 1. Definition

New Features

config option ClearFwdOnSet to accomodate different behaviour when setting call forwards

Status	Assigned
Id	60202

The tapi spec is somewhat unclear on how lineForward actually works. As a result, applications behave different. Some assume that setting call forwards actually modify the current settings. Others assume that they replace the settings. This cannot be known by the service provider.

To work around this issue, a new configuration option ClearFwdOnSet was introduced. If set to a non-zero DWORD value, the replace-semantic is assumed.

Bug Fixes

lineForward() did not work for lines with no registration

Status	Assigned
Id	60186

Call forwards could only be set if there was at least one registration on the line.

trap when monitoring user with very large user record

Status	Assigned
Id	60188

The TSP fails during startup when a user with a very large user record is monitored. This may happen for users which store larger personal phone configs. Moving the phone config fully or partly in to a template object may help to work around this problem.