Jump to: navigation, search

New or Updated Option Descriptions

These option descriptions are new or replace descriptions in the Universal Routing 8.1 Reference Manual:

addp_timeout

ADDP is used to detect a loss of connection between the HTTPBridge and URS. The addp_timeout option is used to specify how often the HTTPBridge will send ADDP requests to URS and wait for responses. If no response is received, HTTPBridge will terminate within the defined timeout.

Location: web section of the URS Application object
Default Value: 30 (seconds)
Valid Values: Any positive integer
Changes Take Effect: After restart

If set to 0 or any invalid value, the ADDP functionality is disabled.

automatic_ideal_agent

If set to true, then when URS places the interaction into a queue for first time:

  • If this queue targets/agents are defined as a skill expression and
  • if function SetIdealAgent was not yet called for this call, then

URS will automatically call the SetIdealAgent function with the value of the skill expression used for this queue as a target. For more information, see Using Agent Skills for Agents/Calls Prioritization.

default_stat_server

The default_stat_server option is extended to allow you to specify a separate default Stat Server for every Virtual Queue. The extension covers cases where URS's Connections list contains multiple Stat Servers. An updated option description is presented below. For more information, see Associating Virtual Queues with Stat Servers.

def_http_proxy_host

Location in Configuration Layer by precedence: web section of the URS Application object
Default Value: An empty string
Valid Values: Any valid host name
Changes Take Effect: After restart

URS provides support of HTTP Proxies for an "http://" type of request. HTTP Proxies are specified globally at the URS Application level, in the web section, by the def_http_proxy_host and def_http_proxy_port configuration options. The def_http_proxy_host option specifies the HTTP Proxy host.

def_http_proxy_port

Location in Configuration Layer by precedence: web section of the URS Application object
Default Value: An empty string
Valid Values: TCP port
Changes Take Effect: After restart

This option specifies the HTTP Proxy port for an "http://" type of connection.

def_sec_protocol

Location in Configuration Layer by precedence: web section of the URS Application object
Default Value: As defined by Genesys Security Layer
Valid Values: SSLv23, SSLv3, TLSv1, TLSv11
Changes Take Effect: After restart

This option specifies which handshake protocol HTTP Bridge uses for outgoing HTTPS connections. This option can be used only on UNIX operating systems with Genesys Security Pack on UNIX 8.1.x, starting with 8.1.300.05. This option has no effect on Windows. Protocols are specified by the option values as follows:

  • SSLv23—SSL v2.0
  • SSLv3—SSL v3.0
  • TLSv1—TLS v1.0
  • TLSv11—TLS v1.2

Starting with 8.1.400.33, the def_sec_protocol configuration option now supports a new value, TLSv12. This option was originally introduced in URS 8.1.400.13 on 2/13/15.

http_log_size

Location in Configuration Layer by precedence: web section of the URS Application object
Default value: false
Valid Value: Size of log file in kilobytes
Changes Take Effect: After restart

This option specifies the HTTP Bridge maximum log file segment size in kilobytes. Once the specified file size is reached, a new segment/file is created and the new log output goes to this new file. You must configure the http_log_file option to use this option. Also, see the option log_remove_old_files.

log_file

Location in Configuration Layer by precedence: http section of the URS Application object
Default value: no default value
Valid Value: log file name
Changes Take Effect: After restart

This option specifies the name of the log file for HTTP Interface error and trace messages.

log_remove_old_files

Location in Configuration Layer by precedence: web section of the URS Application object
Default value: false
Valid Values: either false (meaning old log files are not deleted and all log files will be kept), or an integer specifying the number of log files that will be kept.
Changes Take Effect: After restart

This option specifies whether the previous segments/ files are to be deleted when the new segment/file is created. You must also configure the http_log_file option to use this option.

log_remove_old_files

Location in Configuration Layer by precedence: http section of the URS Application object
Default value: false
Valid Values: either false (meaning old log files are not deleted and all log files will be kept), or an integer specifying the number of log files that will be kept.
Changes Take Effect: After restart

This option specifies whether the previous segments/ files are to be deleted when the new segment/file is created. You must also configure the log_file option to use this option.

log_size

Location in Configuration Layer by precedence: http section of the URS Application object
Default Value: false (unlimited size of file)
Valid Value: size of log file in kilobytes
Changes Take Effect: After restart

This option specifies the HTTP Interface maximum log file segment size in kilobytes. Once the specified file size is reached, a new segment/file is created and the new log output goes to this new file.

max_loading

Location in Configuration Layer by precedence: DB Server/Custom Server/StatServer, Database Access Point
Default value: 0 (zero)
Valid value: any positive integer
Value changes: take effect immediately

Specifies the maximum number of unanswered requests that URS can send to a server; for example, the maximum number of unanswered opening statistic requests that URS can send to StatServer. Specifically prevents database access bottlenecks when there is high call volume and high customer request abandonment or when there is high call volume and low DBMS performance. The latter condition can be caused by an untuned or unoptimized database.

The default value of 0 (zero) indicates that URS is not tracking or limiting the number of requests to the server.

pickup_calls

Location in Configuration Layer by precedence: Annex properties of DN controlled by URS, T-Server, URS
Default Value: false
Valid Values: false, true, reverse
Changes Take Effect: Immediately

Starting with 8.1.400.36, the pickup_calls configuration option is now supported at the T-Server and URS Application levels, in addition to the Routing Point DN level. This option enables smart registration for routing points and depends on T-Server’s ability to provide information on all interactions pending on a routing point even before routing points are registered by URS at startup. For additional information on this option, refer to the Universal Routing 8.1 Reference Manual.

proxy_use_connect

Location in Configuration Layer by precedence: web section of URS
Default Value: true
Valid Values: true, false
Changes Take Effect: After restart

This option specifies the connection method to a secure web server through a HTTP proxy server.

  • A value of true uses the HTTP CONNECT method. URS communicates with web servers through HTTP proxy and performs TLS negotiations directly with the web server.
  • A value of false uses the legacy method (not recommended). URS communicates with web servers through HTTP proxy and performs TLS negotiations with the proxy server.

self_port

Location in Configuration Layer by precedence: default section of URS
Default Value: default
Valid Values: none or any valid TCP/IP Port ID
Changes Take Effect: After restart

Release 8.1.400.32 introduces a new option, self_port, which enables URS to establish a SELF connection when the default listening port is secured, since a SELF connection is not supported via a secured port.

  • A value of none instructs URS to not connect to itself so any related functionality, such as the RequestRouter function, will be unavailable.
  • A value of default instructs URS to use a default port to connect to itself.
  • If you not specify option self_port, then URS will use value default for this option.

skill_in_group_sync

Location in Configuration Layer by precedence: URS
Default Value: 10
Valid Values: Any non-zero positive integer
Changes Take Effect: After restart

This option specifies the maximum number of attempts for URS to execute GetSkillInGroupEx and CountSkillInGroupEx functions when their parameter sync is set to true.

start_primary

Location in Configuration Layer by precedence: URS Application object
Default Value: true
Valid Values: true, false
Changes Take Effect: After restart

This option specifies whether URS starts in primary mode or in backup mode in cases when a primary-backup URS pair is configured. If this option is set to true, then URS will start in primary mode. If this option is set to false, URS starts in backup mode. After the initial URS startup, Management Layer may switch the running mode of the URS Application depending on the startup order.

virtual_queue_attach

Location in Configuration Layer by precedence: URS Application object
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately

When set to true, URS propagates AttachedDataChanged events through Virtual Queue DNs, and does not when set to false. The purpose of this option is to reduce network traffic by limiting the amount of changed events in the attached data of calls. If deployed in a SIP Cluster environment (URS option environment contains value tcluster, then the default value of the option becomes false.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on September 17, 2018, at 11:19.