Reference8:Release Notes TAPI: Difference between revisions
m (regular roadmap update) |
m (regular roadmap update) |
||
| Line 115: | Line 115: | ||
|} | |} | ||
== Bug Fixes == | |||
= V8 Change Requests = | |||
These are change requests applicable for TAPI V8, which are considered for implementation | |||
[http://mantis.innovaphone.com/view.php?id=53097 Definition] | |||
== New Features == | |||
=== Basic Logging in Release Version === | |||
{| | |||
|Status | |||
|<font><font color="red">Assigned</font></font> | |||
|- | |||
|Id | |||
|[http://mantis.innovaphone.com/view.php?id=53099 53099] | |||
|} | |||
Enables users to install a release version that provides basic logging with minimal impact on runtime performance and no risk of disk hogging. | |||
== Bug Fixes == | == Bug Fixes == | ||
Revision as of 12:56, 8 June 2010
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 | Resolved |
| 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 using transfer mode LINETRANSFERMODE_CONFERENCE
Support for linePark
| Status | Assigned |
| Id | 52995 |
Allows users to park/unpark calls.
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
| 52994 | admin | Treat presence-only Devices as separate TAPI Lines |
| 52996 | admin | Support for RedirectionID, RedirectingID, CallerID, CalledID, ConnectedID, CalledParty |
Bug Fixes
V8 Change Requests
These are change requests applicable for TAPI V8, which are considered for implementation Definition
New Features
Basic Logging in Release Version
| Status | Assigned |
| Id | 53099 |
Enables users to install a release version that provides basic logging with minimal impact on runtime performance and no risk of disk hogging.