CTArchitect 10.4.4
Version 10.4.4.12 (Not yet released)
- fix for blending
Version 10.4.4.11 (26/09/2017)
- Wrong detection of default sip port
Version 10.4.4.10 (24/08/2017)
- Fixed failure to detect Hasp Key during Remote Desktop
- Updated the way
INFOrequests are handled by CTArchitect. Some SIP-trunks useINFOrequests as a "ping" to check if the call is still active. This is a bad practice sinceSession-Timers/ re-INVITE/UPDATEare meant for this, as explained in RFC 4028 (implemented in CTArchitect 10.4.5). But since Dialogic puts theINFOmethod in theAllowheader, it is not prohibited. From now on, CTArchitect will respond to theINFOrequests with a200response (instead of ignoring theINFOrequest).
Version 10.4.4.9 (12/07/2017) (Happy Birthday Malala)
- Fix in order to keep question record info in case of reuse voice channel after previous record
- Rewrite Fix to prevent race condition on autdia mandia
Version 10.4.4.8 (16/06/2017)
- Fixed an issue with filenames used in plays/recordings when it contains ASCII characters between 128 and 255 (e.g.
é). The file was not found, and the logging contained incomplete/merged lines, and showed the character as a?. - Fixed race condition during Dial (
AUTDIA), ManualDial (MANDIA), LocationManualDial (LMANDI) and BlindTransfer (BLITRA). Several states were executed twice, which resulted in failure to call the number. This error was present in the logging:Internal Number <#> could not be found in CCA with ID <#>(or other errors regarding internal numbers).
Version 10.4.4.7 (29/05/2017)
- Fixed crash during Supervisor logon when CTArchitect is not completely started yet.
- Fixed possible crash when using OutboundCall that is already disconnected (e.g. when Agent status changes). Zendesk #32276.
Version 10.4.4.6 (20/04/2017)
- Fixed problem in setups while comparing versions which could cause e.g. v10 to be considered older than v2.7. This fix applies to CTArchitect, CTNode, GlobalCCA and WebProd setups, and was first seen on MDAC prerequisite check.
- Fixed some problems with Microsoft Visual C++ Redistributable in setups:
- When installing Microsoft Visual C++ Redistributable, in most cases multiple versions within the same track were installed. E.g. when installing Microsoft Visual C++ 2015 v14.0.24215, v14.0.24212 was also installed. This bug applies to Microsoft Visual C++ 2008 up till 2015. Except for the unneeded installation, there is no impact.
- Updated version-check of Microsoft Visual C++ 2015 Redistributable (both 32-bit and 64-bit), according to a new recommendation of Microsoft. This fixes problems when running the installer on systems where Microsoft Visual C++ 2017 Redistributable (14.10.x) or some versions of TFS testing framework are already installed. An error message box is displayed (errorcode 0x666 or 0x80070666), after which the setup continuous.
Version 10.4.4.5 (15/03/2017)
- Fixed startup problems with CTWatch because the packaged Visual C++ runtime is 2015 (vc14) and CTWatch was built with Visual Studio 2013 (vc12). CTWatch is now also built with Visual Studio 2015 (vc14). This is a fake release of CTArchitect to allow identification of the new setup containing the updated CTWatch. CTArchitect 10.4.4.5 and 10.4.4.4 are identical.
Version 10.4.4.4 (07/03/2017)
- Fixed problem with reading
stat<n>.cfgfiles, when the line contains more than 254 characters. The maximum limit is now increased to 1023 characters. In a later version, further improvements will be done (Unicode support, further robustness).
Version 10.4.4.3 (06/03/2017)
- Fixed a problem when updating configuration tables from CTArchitect in GUI-mode connected to a CTArchitect in service-mode, when the original configuration file didn't exist.
- Fixed possible corrupt data (or even crashes) on CCA when sending statistics. The maximum number of statistics being sent in a batch is reduced from 100 to 50.
Version 10.4.4.2 (08/02/2017)
-
Fixed problem in predictive dialing with randomly dangling calls to CATIs, right after starting the call setup to the agent. This line can be seen in logging:
Invalid line <channel> for agent <agentid> detected. This problem forces the agent to restart CATI, and try again. -
Fixed issue with time syncing because syncing direction of the CCA File Socket happened in the wrong direction.
-
Fixed wrong TaskID in statistics when using transfer. After transfer of call A to call B, TaskID of call B is stored in both calls A and B. Zendesk #26686.
Bug introduced in 10.3.3.26 / 10.3.5.17 / 10.4.0.1, when adding this fix:Fixed an issue with transfering an inbound call to an inbound number, which is put directly into a queue. The destination agent got the task associated with the original inbound number, instead of the transfer inbound number.
Version 10.4.4.1 (14/11/2016)
- Added more description on settings group "Logging". Fixes [TFS #2604].
- Added support for TCP. This needs to be enabled in the registry:
HKLM\SOFTWARE\WOW6432Node\MI4C\CTArchitect\HMP1_TcpEnabled= 1 (DWORD). On a stand-alone platform, this setting needs to be set on CTArchitect, after which CTArchitect must be restarted. On a multi-node platform, apply this setting to the CTNode(s). - Added support for logging incoming
OPTIONSrequests. IncomingOPTIONSrequests were already handled automatically by Dialogic, but now they can be seen in the logging. - Added support for handling media changes (on-hold / take-back) in re-invites.
- Fixed wrong port (and possibly IP-Address) was used when a non-default SIP listen port is defined in the registry.
In-dialog messages were sent to the default port by the remote side. - Fixed wrong message in logging after invalid password was entered.
- Fixed possible crash when empty param/extension block is received in GCEV_EXTENSION/GCEV_SERVICERESP (Central CTArchitect).
- Removed toolbar button to enable/disable outbound calls (BTrieve-based outbound call functionality was removed in 5.4.3).
- Refactored code to clean up old technologies and functionality. Isolate BTrieve logic.
- Removed requirement to enter activation code.
- Removed requirement to specify startup option
-swhen you want to enable the simulator while CTArchitect is running. The simulator is now always enabled.
- All fixes up to 10.4.3.3.