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 Change Requests

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

Support for multi-Party Conferences

Status	Closed
Id	53063

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

tapi: notify held/retrieved status on far end

Status	Closed
Id	53800

allows for better visibility of transfer operations on the transferred end.

V8 Hotfix 1

The V8 TAPI, Hotfix 1. Definition

config option ClearFwdOnSet to accomodate different behaviour when setting call forwards

Status	Closed
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.

V8 Hotfix 2

The V8 TAPI, Hotfix 2. Definition

Write Dump File when TSP crashes

Status	Closed
Id	68452

Enables better problem analysis

V8 Hotfix 3

The V8 TAPI, Hotfix 3. Definition

Ability to configure an un-encrypted user/password

Status	Closed
Id	87155

See Rolling_out_First_Party_TSPs_to_multiple_PCs

Memory Debug Feature

Status	Closed
Id	87156

Debug Version only

Proprietary Support for SOAP UserRc

Status	Closed
Id	87158

Ability to send SOAP UserRc to arbitrary calls (abusing lineBlindTransfer with magic called name "USERRC" and facility in called subbaddress)

Ability to disable 3PTY special treatment for all lines

Status	Closed
Id	87161

The TSP will detect 3PTY situation on IP phones and announce them to the TAPI application appropriately. Some TAPI applications however get confused with 3PTY calls and cannot handle them correctly. If this feature is enabled, 3PTY calls will be shown as normal unrelated calls to the TAPI application.

V8 Hotfix 4

The V8 TAPI, Hotfix 4. Definition

Write info messages and warnings to windows event log

Status	Closed
Id	87549

Trace messages of type INFO and WARNING are sent to Windows Application Event Log.

Option to show full calling number from root

Status	Closed
Id	88544

Option to signal full calling number from root-node for incoming calls ("Show full E164 Numbers") in calling name, separated by "@" (e.g. name@497031730090). Requires V9 hotfix 19 or later on PBX.

V8 Hotfix 5

The V8 TAPI, Hotfix 5. Definition

V8 Hotfix 6

The V8 TAPI, Hotfix 6. Definition

Installer Package signed now

Status	Closed
Id	89860

The .msi packages are signed now.

Ability to send arbitrary remote control facilities in lineMakeCall

Status	Closed
Id	89903

Allows the invocation of 3rd party call control functions in call setup as per Reference:Remote Control Facility, e.g. call intrusion.

Allow HTTPS on non-standard Port

Status	Closed
Id	90581

TSP can now connect securely although HTTPS is not on standard port 443.

Ability to disable special disconnect Handling for monitored Lines

Status	Closed
Id	90604

See Reference8:TAPI_Service_Provider#Miscellaneous_Flags

V8 Hotfix 7

The V8 TAPI, Hotfix 7. Definition

V8 Hotfix 8

The V8 TAPI, Hotfix 8, Build 8140.

Available in V8 applications hotfix14 Build 8000039. Definition

Ability to suppress Recording Calls in TAPI Call States

Status	Closed
Id	95285

see HiddenRecordingNumber in http://wiki.innovaphone.com/index.php?title=Reference8:TAPI_Service_Provider#Tweaks

Ability to configure Log File Disposition in tsptray.exe

Status	Closed
Id	95286

option to "remove all", "keep last n" or "keep all" on telephony service shutdown

Enable hold without local Music-on-hold through Registry Tweak "SilentHold"

Status	Closed
Id	95287

See "SilentHold" in http://wiki.innovaphone.com/index.php?title=Reference8:TAPI_Service_Provider#Tweaks

V8 Hotfix 9

The V8 TAPI, Hotfix 9, Build 8141.

Available in V8 applications hotfix15 Build 8000040. Definition

V8 Hotfix 10

The V8 TAPI, Hotfix 10, Build 8150.

Available in V8 applications hotfix16 Build 8000042. Definition

V8 Hotfix 11

The V8 TAPI, Hotfix 11, Build 8151.

Available in V8 applications hotfix17 Build 8000045. Definition

V8 Hotfix 12

The V8 TAPI, Hotfix 12, Build 8156.

Available in V8 applications hotfix18 Build 8000047. Definition

V8 Hotfix 13

The V8 TAPI, Hotfix 13, Build 8157.

Available in V8 applications hotfix19 Build 8000049. Definition

V8 Hotfix 14

The V8 TAPI, Hotfix 14, Build xxxx.

Available in V8 applications hotfixXX Build 80000xx. Definition

Do not report calls as diverted if the same local party is called

Status	Assigned
Id	144246

When a party was called not using the shortest possible number (e.g. when calling a party in the same node by calling the destination's complete number from the root), the outgoing call was reported as being diverted (as the number received in the alert or connect message differed from the called number). This was confusing.
Now, such calls are no longer shown as diverted, if the called parties CN is known and does not change.

New Registry Tweak UseFirstLeg2

Status	Assigned
Id	144799

Option to modify the default behaviour when TAPI reports call forward information (leg2). See UseFirstLeg2 in http://wiki.innovaphone.com/index.php?title=Reference8:TAPI_Service_Provider#Tweaks