Jump to: navigation, search

Outbound Contact and HTTP Server

OCS supports communication with OCS clients, such as GVP using HTTP requests and responses. This enables an HTTP client to send requests to update records over HTTP or HTTPS.

Configuring HTTP/HTTPS

To configure HTTP support, see the procedure Configuring OCS for HTTP.

Support for HTTPS

OCS supports communication over HTTPS, or strictly speaking, HTTP over Transport Layer Security (TLS) connection, using a Genesys TLS implementation.

For a detailed description of a Genesys TLS implementation, see the Genesys Security Deployment Guide, Part 3, Server Integrity - Transport Layer Security. For information about the operating systems that are supported by a Genesys TLS implementation, see the Genesys Security Deployment Guide, in the "Environment Prerequisites" section.

For the installation procedure of Genesys Security Pack on UNIX, see the Genesys Security Deployment Guide, "Security Pack Installation". On Windows platforms, support for SSL/TLS is integrated into the operating system.

How Outbound Contact Uses HTTP/HTTPS

The HTTP server-side interface in OCS, HTTP Proxy, is a gateway between HTTP version 1.1 and outbound protocols (the Desktop protocol and the Third Party protocol).

At its startup, when OCS determines that an HTTP port is configured, it automatically starts HTTP Proxy. As the end user, you do not need to start this child process manually.

In OCS, this HTTP Proxy translates:

  • HTTP requests into OCS proprietary protocols.
  • OCS proprietary protocols responses into HTTP responses.

HTTP Proxy supports UTF-8 encoding. OCS sends the value of the encoding option value to HTTP Proxy, which can transcode (or convert) the JSON body of HTTP requests or responses (such as AddRecord and PreviewRecord events, or pre-dial validation requests) according to the value specified. If no value is specified, no conversion takes place.

At OCS startup, OCS starts HTTP Proxy, and HTTP Proxy opens the associated port that is configured in the OCS application object. If HTTP Proxy cannot open the port, it shuts down. If HTTP Proxy terminates unexpectedly, OCS tries to restart it after the Reconnect Timeout expires. This Reconnection Timeout is specified on the OCS Configuration tab/Server Info section (in Genesys Administrator).

HTTP Proxy does not have its own log, but passes log messages to OCS, which logs them into the OCS log file.

Note: Be aware that using NMAP or similar port scanners can cause OCS to close HTTP ports.

Configuring OCS for HTTP


  • To configure the OCS application object to communicate with clients using HTTP requests/responses.


  1. In Genesys Administrator, go to Provisioning > Environment > Applications and double-click your OCS application object.
  2. Configure a separate listener port on the Configuration tab/Server Info section with the Connection Protocol set to http.


Configuration Changes

Dynamic changes to this port are not supported. As a result, any such changes are not communicated to an HTTP Proxy that is already running. However, any HTTP Proxy started that is after that port change will reflect the change.

HTTP terminates if the HTTP listener port is removed from the OCS Configuration tab/Server Info section or if the connection is lost between OCS and HTTP Proxy.

Primary and Backup OCS and HTTP Proxy

If you have configured primary and backup OCS applications, the primary instance starts an associated HTTP Proxy and opens a listening port. The backup OCS only starts HTTP Proxy and opens a listening port when it is switched into primary mode.

Comment on this article:

blog comments powered by Disqus
This page was last modified on 18 May 2017, at 11:06.