UTF-8 Encoding Support
[FDS: https://intranet.genesys.com/display/RP/Iteration+9.23+%28a%29+Support+for+UTF-8+encoding+by+OCS]
Starting with 8.1.528.xx, Outbound Contact Server supports UTF-8 encoding for both Linux and Windows platforms.
OCS using Postgre SQL 10
Postgre SQL platform: Linux CentOS 7 x86_64
Postgre SQL version: 10.14
Database encoding: UTF8
Database collation: en_US.UTF-8
Database character set: en_US.UTF-8
DBServer platform: Linux CentOS 7 x86_64
DBServer version: 8.5.100.07
OCS platforms: Linux CentOS 7 x86_64, Windows Server 2008 R2 Standard
OCS version: 8.1.528.16 (which uses DBLib version 8.5.101.30)
Dialing mode: Preview
Both values (false and true) of dbserver-less-mode option were successfully tested.
OCS using MS SQL Server 2019
Microsoft SQL Server 2019: different editions are allowed, but it should not be lower than 2019.
Microsoft ODBC Driver 17 for SQL Server or higher is essential.
Database collation Latin1_general_100_CI_AS_KS_WS_SC_UTF-8. Suffix SC_UTF-8 is essential, other suffixes may differ: CI/CS, AI/AS, KI/KS, WI/WS.
DBServer version 8.5.100.07 or higher is essential, Windows platform probably is not essential.
DAP settings are essential: UTF-8 for MSSQL: checked dbclient/utf8-ucs2: true
OCS version and DBLib version are essential. OCS version should be not lower than 8.1.528.16 and used DBLib version should be nort lower than 8.5.101.30.
Dialing mode is not essential. dbclient/utf8-ucs2 option is not essential.
Microsoft SQL Server 2019 platform: Windows Server 2019 Standard
Microsoft SQL Server 2019 version: Developer Edition 15.0.2070.41
Microsoft ODBC Driver 17 for SQL Server
Database collation: Latin1_General_100_CI_AS_KS_WS_SC_UTF8
DBServer platform: Windows Server 2019 Standard
DBServer version: 8.5.100.07
DAP UTF-8 for MSSQL: checked
DAP option dbclient/utf8-ucs2: true
OCS platforms: Linux CentOS 7 x86_64, Windows Server 2008 R2 Standard
OCS version: 8.1.528.16 (which uses DBLib version 8.5.101.30)
Dialing mode: Preview
dbserver-less-mode option value is false.
