ReleaseNotes8:TAPI: Difference between revisions
Jump to navigation
Jump to search
m regular roadmap update |
m regular roadmap update |
||
| Line 24: | Line 24: | ||
|[http://mantis.innovaphone.com/view.php?id=53063 53063] | |[http://mantis.innovaphone.com/view.php?id=53063 53063] | ||
|} | |} | ||
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. <!----> | ||
=== tapi: notify held/retrieved status on far end === | === tapi: notify held/retrieved status on far end === | ||
| Line 35: | Line 35: | ||
|[http://mantis.innovaphone.com/view.php?id=53800 53800] | |[http://mantis.innovaphone.com/view.php?id=53800 53800] | ||
|} | |} | ||
allows for better visibility of transfer operations on the transferred end. | allows for better visibility of transfer operations on the transferred end.<!----> | ||
== Bug Fixes == | == Bug Fixes == | ||
| Line 58: | Line 58: | ||
|[http://mantis.innovaphone.com/view.php?id=60202 60202] | |[http://mantis.innovaphone.com/view.php?id=60202 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. <br/><br/>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. | 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. <br/><br/>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 == | == Bug Fixes == | ||
| Line 73: | Line 73: | ||
|[http://mantis.innovaphone.com/view.php?id=60186 60186] | |[http://mantis.innovaphone.com/view.php?id=60186 60186] | ||
|} | |} | ||
Call forwards could only be set if there was at least one registration on the line. | 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 === | === trap when monitoring user with very large user record === | ||
| Line 84: | Line 84: | ||
|[http://mantis.innovaphone.com/view.php?id=60188 60188] | |[http://mantis.innovaphone.com/view.php?id=60188 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. | 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 = | = V8 Hotfix 2 = | ||
| Line 103: | Line 103: | ||
|[http://mantis.innovaphone.com/view.php?id=68452 68452] | |[http://mantis.innovaphone.com/view.php?id=68452 68452] | ||
|} | |} | ||
Enables better problem analysis | Enables better problem analysis<!----> | ||
== Bug Fixes == | == Bug Fixes == | ||
| Line 118: | Line 118: | ||
|[http://mantis.innovaphone.com/view.php?id=68454 68454] | |[http://mantis.innovaphone.com/view.php?id=68454 68454] | ||
|} | |} | ||
For example, a call to "^1" will cause a TSP trap. | For example, a call to "^1" will cause a TSP trap. <!----> | ||
= V8 Hotfix 3 = | = V8 Hotfix 3 = | ||
| Line 137: | Line 137: | ||
|[http://mantis.innovaphone.com/view.php?id=87155 87155] | |[http://mantis.innovaphone.com/view.php?id=87155 87155] | ||
|} | |} | ||
See [[Reference8:TAPI_Service_Provider#Rolling_out_First_Party_TSPs_to_multiple_PCs | Rolling_out_First_Party_TSPs_to_multiple_PCs]] | See [[Reference8:TAPI_Service_Provider#Rolling_out_First_Party_TSPs_to_multiple_PCs | Rolling_out_First_Party_TSPs_to_multiple_PCs]]<!----> | ||
=== Memory Debug Feature === | === Memory Debug Feature === | ||
| Line 148: | Line 148: | ||
|[http://mantis.innovaphone.com/view.php?id=87156 87156] | |[http://mantis.innovaphone.com/view.php?id=87156 87156] | ||
|} | |} | ||
Debug Version only | Debug Version only<!----> | ||
=== Proprietary Support for SOAP [[Reference9:Concept_SOAP_API#UserRc.28integer_c |UserRc]] === | === Proprietary Support for SOAP [[Reference9:Concept_SOAP_API#UserRc.28integer_c |UserRc]] === | ||
| Line 159: | Line 159: | ||
|[http://mantis.innovaphone.com/view.php?id=87158 87158] | |[http://mantis.innovaphone.com/view.php?id=87158 87158] | ||
|} | |} | ||
Ability to send SOAP UserRc to arbitrary calls (abusing lineBlindTransfer with magic called name "USERRC" and facility in called subbaddress) | 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 === | === Ability to disable 3PTY special treatment for all lines === | ||
| Line 170: | Line 170: | ||
|[http://mantis.innovaphone.com/view.php?id=87161 87161] | |[http://mantis.innovaphone.com/view.php?id=87161 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. | 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 == | == Bug Fixes == | ||
| Line 185: | Line 185: | ||
|[http://mantis.innovaphone.com/view.php?id=87162 87162] | |[http://mantis.innovaphone.com/view.php?id=87162 87162] | ||
|} | |} | ||
Changed calling sequence of [[Reference9:Concept_SOAP_API#UserTransfer_.28int_acall.2C_integer_bcall.29 | UserTransfer]] arguments to ensure a consistent und useful setting of the CALLIDs of the calls remaining after a transfer. | Changed calling sequence of [[Reference9:Concept_SOAP_API#UserTransfer_.28int_acall.2C_integer_bcall.29 | UserTransfer]] arguments to ensure a consistent und useful setting of the CALLIDs of the calls remaining after a transfer. <!----> | ||
=== performance improvements for slow networks === | === performance improvements for slow networks === | ||
| Line 196: | Line 196: | ||
|[http://mantis.innovaphone.com/view.php?id=87163 87163] | |[http://mantis.innovaphone.com/view.php?id=87163 87163] | ||
|} | |} | ||
handles line initializations and destructions asynchronously, avoiding sluggish response times when PBXs come and go | 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 === | === allow more parallel threads to work with a higher number of PBXs === | ||
| Line 207: | Line 207: | ||
|[http://mantis.innovaphone.com/view.php?id=87164 87164] | |[http://mantis.innovaphone.com/view.php?id=87164 87164] | ||
|} | |} | ||
when maximum number of threads is exceeded, response times will be slow. See [[Reference8:TAPI_Service_Provider#System_Requirements | System Requirements]] | when maximum number of threads is exceeded, response times will be slow. See [[Reference8:TAPI_Service_Provider#System_Requirements | System Requirements]]<!----> | ||
=== Do not retrieve user configuration for objects named '*' === | === Do not retrieve user configuration for objects named '*' === | ||
| Line 218: | Line 218: | ||
|[http://mantis.innovaphone.com/view.php?id=87165 87165] | |[http://mantis.innovaphone.com/view.php?id=87165 87165] | ||
|} | |} | ||
Possible trap when calling Admin() on objects named '*'. | Possible trap when calling Admin() on objects named '*'. <!----> | ||
=== Trap on long PBX Admin() Result === | === Trap on long PBX Admin() Result === | ||
| Line 229: | Line 229: | ||
|[http://mantis.innovaphone.com/view.php?id=87166 87166] | |[http://mantis.innovaphone.com/view.php?id=87166 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. | 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 === | === re-initialize pbx connector when connect fails (solves some COM initialization problems === | ||
| Line 240: | Line 240: | ||
|[http://mantis.innovaphone.com/view.php?id=87167 87167] | |[http://mantis.innovaphone.com/view.php?id=87167 87167] | ||
|} | |} | ||
- | -<!----> | ||
= V8 Hotfix 4 = | = V8 Hotfix 4 = | ||
| Line 259: | Line 259: | ||
|[http://mantis.innovaphone.com/view.php?id=87549 87549] | |[http://mantis.innovaphone.com/view.php?id=87549 87549] | ||
|} | |} | ||
Trace messages of type INFO and WARNING are sent to Windows Application Event Log. | Trace messages of type INFO and WARNING are sent to Windows Application Event Log.<!----> | ||
=== Option to show full calling number from root === | === Option to show full calling number from root === | ||
| Line 270: | Line 270: | ||
|[http://mantis.innovaphone.com/view.php?id=88544 88544] | |[http://mantis.innovaphone.com/view.php?id=88544 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. | 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.<!----> | ||
== Bug Fixes == | == Bug Fixes == | ||
| Line 285: | Line 285: | ||
|[http://mantis.innovaphone.com/view.php?id=88545 88545] | |[http://mantis.innovaphone.com/view.php?id=88545 88545] | ||
|} | |} | ||
fix for #87163 which made fail-back from slave-standby to slave impossible | fix for #87163 which made fail-back from slave-standby to slave impossible<!----> | ||
=== possible deadlock when re-connecting or disconnecting failed PBXs === | === possible deadlock when re-connecting or disconnecting failed PBXs === | ||
| Line 296: | Line 296: | ||
|[http://mantis.innovaphone.com/view.php?id=88546 88546] | |[http://mantis.innovaphone.com/view.php?id=88546 88546] | ||
|} | |} | ||
results in missing status updates from affected PBXs | results in missing status updates from affected PBXs<!----> | ||
=== 3PTY detection broken for some type of phones (e.g. SoftwarePhone) === | === 3PTY detection broken for some type of phones (e.g. SoftwarePhone) === | ||
| Line 307: | Line 307: | ||
|[http://mantis.innovaphone.com/view.php?id=89654 89654] | |[http://mantis.innovaphone.com/view.php?id=89654 89654] | ||
|} | |} | ||
results in being unable to drop the conference | results in being unable to drop the conference<!----> | ||
= V8 Hotfix 5 = | = V8 Hotfix 5 = | ||
| Line 330: | Line 330: | ||
|[http://mantis.innovaphone.com/view.php?id=89679 89679] | |[http://mantis.innovaphone.com/view.php?id=89679 89679] | ||
|} | |} | ||
Installer failed to setup registry keys for windows event log event source registration. This also prevented the Debug version to start up. | 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 = | = V8 Hotfix 6 = | ||
| Line 349: | Line 349: | ||
|[http://mantis.innovaphone.com/view.php?id=89860 89860] | |[http://mantis.innovaphone.com/view.php?id=89860 89860] | ||
|} | |} | ||
The .msi packages are signed now. | The .msi packages are signed now.<!----> | ||
=== Ability to send arbitrary remote control facilities in lineMakeCall === | === Ability to send arbitrary remote control facilities in lineMakeCall === | ||
| Line 360: | Line 360: | ||
|[http://mantis.innovaphone.com/view.php?id=89903 89903] | |[http://mantis.innovaphone.com/view.php?id=89903 89903] | ||
|} | |} | ||
Allows the invocation of 3rd party call control functions in call setup as per [[Reference:Remote Control Facility]], e.g. call intrusion. | 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 === | === Allow HTTPS on non-standard Port === | ||
| Line 371: | Line 371: | ||
|[http://mantis.innovaphone.com/view.php?id=90581 90581] | |[http://mantis.innovaphone.com/view.php?id=90581 90581] | ||
|} | |} | ||
TSP can now connect securely although HTTPS is not on standard port 443. | TSP can now connect securely although HTTPS is not on standard port 443.<!----> | ||
=== Ability to disable special disconnect Handling for monitored Lines === | === Ability to disable special disconnect Handling for monitored Lines === | ||
| Line 382: | Line 382: | ||
|[http://mantis.innovaphone.com/view.php?id=90604 90604] | |[http://mantis.innovaphone.com/view.php?id=90604 90604] | ||
|} | |} | ||
See [[Reference8:TAPI_Service_Provider#Miscellaneous_Flags]] | See [[Reference8:TAPI_Service_Provider#Miscellaneous_Flags]]<!----> | ||
== Bug Fixes == | == Bug Fixes == | ||
| Line 397: | Line 397: | ||
|[http://mantis.innovaphone.com/view.php?id=90601 90601] | |[http://mantis.innovaphone.com/view.php?id=90601 90601] | ||
|} | |} | ||
showed correct status only after a first change of the corresponding user object | showed correct status only after a first change of the corresponding user object<!----> | ||
=== ClearFwdOnSet Default now 1 === | === ClearFwdOnSet Default now 1 === | ||
| Line 408: | Line 408: | ||
|[http://mantis.innovaphone.com/view.php?id=90602 90602] | |[http://mantis.innovaphone.com/view.php?id=90602 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. | 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.<!----> | ||
= V8 Hotfix 7 = | = V8 Hotfix 7 = | ||
| Line 431: | Line 431: | ||
|[http://mantis.innovaphone.com/view.php?id=91147 91147] | |[http://mantis.innovaphone.com/view.php?id=91147 91147] | ||
|} | |} | ||
TAPI may connect and disconnect slaves endlessly under certain conditions. Only happens when slaves are monitored. This issue was introduced in hotfix 6. | 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 === | === Call Forward Status not shown correctly if no Registration on PBX Object === | ||
| Line 442: | Line 442: | ||
|[http://mantis.innovaphone.com/view.php?id=91156 91156] | |[http://mantis.innovaphone.com/view.php?id=91156 91156] | ||
|} | |} | ||
- | -<!----> | ||
=== TSP occasionally blocks for up to a minute === | === TSP occasionally blocks for up to a minute === | ||
| Line 453: | Line 453: | ||
|[http://mantis.innovaphone.com/view.php?id=91317 91317] | |[http://mantis.innovaphone.com/view.php?id=91317 91317] | ||
|} | |} | ||
In rare cases, when a TSP looses connection to a PBX, it may block for up to a minute before continueing. | 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 === | === false OUTOFSERVICE/DISCONNECTED line state === | ||
| Line 464: | Line 464: | ||
|[http://mantis.innovaphone.com/view.php?id=91318 91318] | |[http://mantis.innovaphone.com/view.php?id=91318 91318] | ||
|} | |} | ||
race condition when reconnecting master and standby may result in false disconnected/outofservice line state, which recovers on next line activity only | 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 === | === catch exception when TSP Control is not allowed to write TSP config due to Windows UAC === | ||
| Line 475: | Line 475: | ||
|[http://mantis.innovaphone.com/view.php?id=91324 91324] | |[http://mantis.innovaphone.com/view.php?id=91324 91324] | ||
|} | |} | ||
Now displays a message and advises to relax Windows' UAC settings. | Now displays a message and advises to relax Windows' UAC settings.<!----> | ||
=== Allow Blind Transfer and Park on Calls in state "Conferenced" === | === Allow Blind Transfer and Park on Calls in state "Conferenced" === | ||
| Line 486: | Line 486: | ||
|[http://mantis.innovaphone.com/view.php?id=91431 91431] | |[http://mantis.innovaphone.com/view.php?id=91431 91431] | ||
|} | |} | ||
Up til now, Conferenced calls did not have any call features enabled, except drop. Now we allow blind transfer and park too. | Up til now, Conferenced calls did not have any call features enabled, except drop. Now we allow blind transfer and park too.<!----> | ||
Revision as of 13:27, 14 December 2012
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.
tapi: notify held/retrieved status on far end
| Status | Closed |
| Id | 53800 |
allows for better visibility of transfer operations on the transferred end.
Bug Fixes
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
New Features
Write Dump File when TSP crashes
| Status | Assigned |
| Id | 68452 |
Enables better problem analysis
Bug Fixes
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 | 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.
Bug Fixes
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
V8 Hotfix 5
The V8 TAPI, Hotfix 5. Definition
New Features
Bug Fixes
Unability to write Windows Event Log
| Status | Resolved |
| 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
New Features
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
Bug Fixes
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.
V8 Hotfix 7
The V8 TAPI, Hotfix 7. Definition
New Features
Bug Fixes
TAPI continuously connects and disconnects slaves
| Status | Assigned |
| 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 | Assigned |
| Id | 91156 |
-
TSP occasionally blocks for up to a minute
| Status | Assigned |
| 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 | Assigned |
| 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 | Assigned |
| Id | 91324 |
Now displays a message and advises to relax Windows' UAC settings.
Allow Blind Transfer and Park on Calls in state "Conferenced"
| Status | Assigned |
| Id | 91431 |
Up til now, Conferenced calls did not have any call features enabled, except drop. Now we allow blind transfer and park too.