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

New Features

[!12.10.11@13] 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.

Other new Features

53800

ckl

[17.06.11@13] 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	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.

Bug Fixes

lineForward() did not work for lines with no registration

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

V8 Hotfix 2

The V8 TAPI, Hotfix 2. Definition

Bug Fixes

Write Dump File when TSP crashes

Status	Assigned
Id	68452

Enables better problem analysis

Trap when invalid destination address is dialled

Status	Assigned
Id	68454

For example, a call to "^1" will cause a TSP trap.

V8 Hotfix 3

The V8 TAPI, Hotfix 3. Definition

New Features

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.

Bug Fixes

Changed generation of Call-IDs when transferring calls

Status	Closed
Id	87162

Changed calling sequence of UserTransfer arguments to ensure a consistent und useful setting of the CALLIDs of the calls remaining after a transfer.

performance improvements for slow networks

Status	Closed
Id	87163

handles line initializations and destructions asynchronously, avoiding sluggish response times when PBXs come and go

allow more parallel threads to work with a higher number of PBXs

Status	Closed
Id	87164

when maximum number of threads is exceeded, response times will be slow. See System Requirements

Do not retrieve user configuration for objects named '*'

Status	Closed
Id	87165

Possible trap when calling Admin() on objects named '*'.

Trap on long PBX Admin() Result

Status	Closed
Id	87166

long pbx Admin() result may trap TSP. This happens when there is a monitored line where the name starts with asterisk ('*') when using PBX firmware prior to V9 hotfix 17.

re-initialize pbx connector when connect fails (solves some COM initialization problems

Status	Closed
Id	87167

-

V8 Hotfix 4

The V8 TAPI, Hotfix 4. Definition

New Features

Write info messages and warnings to windows event log

Status	Assigned
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	Assigned
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 18 or later on PBX.

Bug Fixes

Failback from Slave-Standby may fail

Status	Assigned
Id	88545

fix for #87163 which made fail-back from slave-standby to slave impossible

possible deadlock when re-connecting or disconnecting failed PBXs

Status	Assigned
Id	88546

results in missing status updates from affected PBXs