ReleaseNotes8:TAPI: Difference between revisions
m regular roadmap update |
m regular roadmap update |
||
| Line 30: | Line 30: | ||
{| | {| | ||
|Status | |Status | ||
|<font><font color="green"> | |<font><font color="green">Closed</font></font> | ||
|- | |- | ||
|Id | |Id | ||
| Line 41: | Line 41: | ||
{| | {| | ||
|Status | |Status | ||
|<font><font color="green"> | |<font><font color="green">Closed</font></font> | ||
|- | |- | ||
|Id | |Id | ||
| Line 52: | Line 52: | ||
{| | {| | ||
|Status | |Status | ||
|<font><font color="green"> | |<font><font color="green">Closed</font></font> | ||
|- | |- | ||
|Id | |Id | ||
| Line 63: | Line 63: | ||
{| | {| | ||
|Status | |Status | ||
|<font><font color="green"> | |<font><font color="green">Closed</font></font> | ||
|- | |- | ||
|Id | |Id | ||
| Line 74: | Line 74: | ||
{| | {| | ||
|Status | |Status | ||
|<font><font color=" | |<font><font color="green">Resolved</font></font> | ||
|- | |- | ||
|Id | |Id | ||
| Line 85: | Line 85: | ||
{| | {| | ||
|Status | |Status | ||
|<font><font color="green"> | |<font><font color="green">Closed</font></font> | ||
|- | |- | ||
|Id | |Id | ||
| Line 96: | Line 96: | ||
{| | {| | ||
|Status | |Status | ||
|<font><font color="green"> | |<font><font color="green">Closed</font></font> | ||
|- | |- | ||
|Id | |Id | ||
| Line 107: | Line 107: | ||
{| | {| | ||
|Status | |Status | ||
|<font><font color="green"> | |<font><font color="green">Closed</font></font> | ||
|- | |- | ||
|Id | |Id | ||
| Line 113: | Line 113: | ||
|} | |} | ||
Allows users to park/unpark calls. | Allows users to park/unpark calls. | ||
=== Basic Logging in Release Version === | === Basic Logging in Release Version === | ||
| Line 178: | Line 167: | ||
|} | |} | ||
Allows users to set up a conference. Involves lineSetupConference, lineAddToConference,lineRemoveFromConference. This might be implemented using PBX bc-conf objects. | Allows users to set up a conference. Involves lineSetupConference, lineAddToConference,lineRemoveFromConference. This might be implemented using PBX bc-conf objects. | ||
=== Other new Features === | === Other new Features === | ||
Revision as of 00:30, 22 July 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
Support for LINECALLDISCONNECTMODE_*
| Status | Closed |
| Id | 6984 |
including LINECALLDISCONNECTMODE_PICKUP
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 SOAP
| 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-hool automatically (provided PBX configuration allows for it).
Other new Features
| 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
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 | [01.10.10] notify held/retrieved status on far end |