Reference8:Release Notes 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
Treat each PBX8 Device as a separate TAPI Line
| Status | Assigned |
| 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 | Assigned |
| Id | 52989 |
This allows users to generate DTMF tones during a call.
Support for lineSetupTransfer
| Status | Assigned |
| 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 | Assigned |
| Id | 52991 |
Allows users to dial extra digits during the call establishment phase. Also required for applications which use lineSetupTransfer.
Calling line ID in SOAP
| Status | Assigned |
| Id | 52992 |
This allows users to create calls with lineMakeCall or lineSetupTransfer which carry a different calling line id.
Support for lineSetupConference
| Status | Assigned |
| Id | 52993 |
Allows users to set up a 3PTY conference.
Support for linePark
| Status | Assigned |
| Id | 52995 |
Allows users to park/unpark calls.
Other new Features
| 52994 | ckl | Treat presence-only Devices as separate TAPI Lines |
| 52996 | admin | Support for RedirectionID, RedirectingID, CallerID, CalledID, ConnectedID, CalledParty |