UTF-8 Encoding

[FDS: https://intranet.genesys.com/display/RP/Iteration+9.23+%28a%29+Support+for+UTF-8+encoding+by+OCS]

Starting with 8.1.528.21, Outbound Contact Server supports UTF-8 encoding of mixed calling lists on Linux and Windows platforms.

OCS Using PostgreSQL 10

Prerequisites

• PostgreSQL platform: Linux CentOS 7 or later
• PostgreSQL version: 10.14 or later
• DB Server platform: Linux CentOS 7 or later
• DB Server version: 8.5.100.07 or later
• OCS platforms: Linux CentOS 7, Windows Server 2008 R2 Standard

Database Settings

• Database encoding: UTF8
• Database collation: en_US.UTF-8
• Database character type: en_US.UTF-8

OCS Using Microsoft SQL Server 2019

Prerequisites

• Microsoft SQL Server 2019 or later
• Microsoft ODBC Driver 17 for SQL Server or later
• DB Server version 8.5.100.07 or later

Database Settings

• Database collation: Latin1_general_100_CI_AS_KS_WS_SC_UTF-8

  Note: Ensure the SC_UTF-8 suffix is added.

In these examples, genesys_ocs is the database name.

ODBC Settings

DAP Settings

• UTF-8 for MSSQL: select True.
• Set the dbclient/utf8-ucs2 option to true.

OCS Using Oracle 19c

Prerequisites

• Oracle 19c platform: Red Hat Enterprise Linux Server release 7.7 (Maipo)
• Oracle 19c version: 19.3
• Database character set: AL32UTF8
• DB Server platform: CentOS Linux release 7.5.1804 (Core)
• Oracle instant client version: 12.2
• DB Server version: 8.5.100.07

• OCS platforms: Linux CentOS 7 x86_64, Windows Server 2008 R2 Standard
• OCS version: 8.1.528.25 (which uses DBLib version 8.5.101.30)
• Dialing mode: Preview
• dbserver-less-mode option value is false.

Strictly required settings for UTF-8 support on Oracle 19c

The only Database AL32UTF8 encoding is strictly required for UTF-8 support on Oracle 19c. Oracle instant client version 19.10 probably will support UTF-8 too, but this use case is not well tested.

Additional scripts to make DBserver working properly

Following script files should be placed at /etc/profile.d directory at the Linux host where DB Server is resided:

• oracle_env.csh
• oracle_env.sh

These scripts should be adjusted if it is used a version of Oracle instant client other than 12.2. Following script file should be placed at the directory where DB Server binaries are resided: multiserver.oracle.sh

This script should be used in all cases which the multiserver executable generally used at. This script accepts all the same command line parameters as the multiserver executable does.