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 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
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.
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
Trap when invalid destination address is dialled
| Status | Closed |
| Id | 68454 |
For example, a call to "^1" will cause a TSP trap.
Write Dump File when TSP crashes
| Status | Closed |
| Id | 68452 |
Enables better problem analysis
V8 Hotfix 3
The V8 TAPI, Hotfix 3. Definition
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 |
-
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
Failback from Slave-Standby may fail
| Status | Closed |
| 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 | Closed |
| Id | 88546 |
results in missing status updates from affected PBXs
3PTY detection broken for some type of phones (e.g. SoftwarePhone)
| Status | Closed |
| Id | 89654 |
results in being unable to drop the conference
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
Unability to write Windows Event Log
| Status | Closed |
| Id | 89679 |
Installer failed to setup registry keys for windows event log event source registration. This also prevented the Debug version to start up.
V8 Hotfix 6
The V8 TAPI, Hotfix 6. Definition
Call Forwarding State was empty on TSP Startup
| Status | Closed |
| Id | 90601 |
showed correct status only after a first change of the corresponding user object
ClearFwdOnSet Default now 1
| Status | Closed |
| Id | 90602 |
See Section ClearFwdOnSet in Reference8:TAPI_Service_Provider#Tweaks. Although this is a change that alters the behaviour in a non-upward compatible way, it does seem more as a bug that it used to be like it did before. So the risk has been taken.
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
TAPI continuously connects and disconnects slaves
| Status | Closed |
| Id | 91147 |
TAPI may connect and disconnect slaves endlessly under certain conditions. Only happens when slaves are monitored. This issue was introduced in hotfix 6.
Call Forward Status not shown correctly if no Registration on PBX Object
| Status | Closed |
| Id | 91156 |
-
TSP occasionally blocks for up to a minute
| Status | Closed |
| Id | 91317 |
In rare cases, when a TSP looses connection to a PBX, it may block for up to a minute before continueing.
false OUTOFSERVICE/DISCONNECTED line state
| Status | Closed |
| Id | 91318 |
race condition when reconnecting master and standby may result in false disconnected/outofservice line state, which recovers on next line activity only
catch exception when TSP Control is not allowed to write TSP config due to Windows UAC
| Status | Closed |
| Id | 91324 |
Now displays a message and advises to relax Windows' UAC settings.
Allow Blind Transfer and Park on Calls in state "Conferenced"
| Status | Closed |
| Id | 91431 |
Up til now, Conferenced calls did not have any call features enabled, except drop. Now we allow blind transfer and park too.
V8 Hotfix 8
The V8 TAPI, Hotfix 8, Build 8140.
Available in V8 applications hotfix14 Build 8000039.
Definition
Problems in Provider Termination
| Status | Closed |
| Id | 95288 |
Sometimes, provider termination failed with a trap or deadlock. This may have resulted in an inability to shut down and subsequently re-start the telephony service.
Installer installed default of 0xff for ProcessorMask
| Status | Closed |
| Id | 95289 |
See "ProcessorMask" in http://wiki.innovaphone.com/index.php?title=Reference8:TAPI_Service_Provider#Tweaks.
By default, the TSP was installed with a ProcessorMask of 0xFF. On systems with more than 8 cores, the TSP then would be locked on to the first 8 cores.
TSP8 failed to release some Thread Handles
| Status | Closed |
| Id | 95290 |
In certain situationes, the TSP failed to release some operating system handles. This results in accumulating resources.
Do not turn on DEBUG and DVL Trace Levels with "set recommended"
| Status | Closed |
| Id | 95291 |
creates too heavy trace load in larger installations
Useless Disconnect of not-yet-connected PBX
| Status | Closed |
| Id | 95292 |
newly learned PBXs suffered from a connect/disconnect/connect cycle during startup, resulting in slow startup with many or large slaves
Call Features did not correctly reflect No3PTY=1 configurations
| Status | Closed |
| Id | 95294 |
See "No3PTY" in http://wiki.innovaphone.com/index.php?title=Reference8:TAPI_Service_Provider#Tweaks
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
line state may become inaccurate if PBX object changes registration PBX
| Status | Closed |
| Id | 96433 |
This happens when the PBX attribute is changed in the PBX configuration. It may result in the lines wrong in-service state or inability to perform TAPI requests on it.
V8 Hotfix 10
The V8 TAPI, Hotfix 10, Build 8150.
Available in V8 applications hotfix16 Build 8000042.
Definition
impossible value for ProcessorMask in Registry floods traces
| Status | Closed |
| Id | 97607 |
impossible values for processor affinity mask in registry resulted in endless setting the mask (flooding the log with info messages)
TSP sometimes falsely sets a line to out-of-service
| Status | Closed |
| Id | 99200 |
rare race conditions may result in lines that still show call activity but can not be controled (out of service)
longer SOAP request timeout
| Status | Closed |
| Id | 99283 |
in very slow networks, the default SOAP request timeout of 5s could falsely trigger a pbx-has-trapped recovery cycle in the TSP. The timeout is 15s now.
race condition when Master PBX with Standby restarts
| Status | Closed |
| Id | 99306 |
When a master PBX with standby restarts, fail-over from master to standby and back can create a race condition where a line is erroneously considered out-of-service. This recovered upon next line activity (e.g. a call).
Installer failed on 32bit Windows XP (claiming a system protected file could not be updated)
| Status | Closed |
| Id | 104572 |
The installer then showed a pop-up saying "The windows installer cannot update the system file C:\\WINDOWS\\system32\\COMDLG32.dll because the file is protected by Windows."
HTTPS SOAP connections did not work on Windows8 / Server 2012
| Status | Closed |
| Id | 104969 |
Windows8 / Server2012 enforce TLS1.2 for secure channels by default. However, the PBX does support up to TLS1.1 only. TLS1.0 / TLS1.1 is now negotiated explicitly on all systems.
V8 Hotfix 11
The V8 TAPI, Hotfix 11, Build 8151.
Available in V8 applications hotfix17 Build 8000045.
Definition
TSP does not report dynamically added lines on Windows Server 2012 and Windows 8 64bit
| Status | Closed |
| Id | 113141 |
When a line is added (because a new member is added to the tapi group in the PBX), it is dynamically reported to the Windows TAPI subsystem. This did not work any more in newer 64bit OS platforms.
V8 Hotfix 12
The V8 TAPI, Hotfix 12, Build 8156.
Available in V8 applications hotfix18 Build 8000047.
Definition
TSP treats lines with active mobility as out-of-service
| Status | Closed |
| Id | 119197 |
Lines without registrations on it were treated as "out-of-service" even if there is mobility enabled for the user. Even more, the TSP got confused by reported mobility calls, resulting in disconnection of the reporting PBX.
V8 Hotfix 13
The V8 TAPI, Hotfix 13, Build 8157.
Available in V8 applications hotfix19 Build 8000049.
Definition
TSP traps on lineUnhold and call deletion race condition
| Status | Closed |
| Id | 123238 |
When a consultation call is unheld with lineUnhold while it is notified as terminated by the PBX, a trap may occur
V8 Hotfix 14
The V8 TAPI, Hotfix 14, Build 8159.
Available in V8 applications hotfix20 Build 8000052.
Definition
Do not report calls as diverted if the same local party is called
| Status | Closed |
| 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 | Closed |
| 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