Revision as of 21:12, June 17, 2016 by Vivian (talk | contribs) (Update with the copy of version: 8.1.5DRAFT)
Jump to: navigation, search

Document Change History

This section lists content that is new or that has changed significantly since the first release of this document. The most recent changes appear first.

Important
There was no 8.1.3 release of Interaction Concentrator.

New in Document Version 8.1.509.00

  • Added a note in the description of the use-server-partyuuid configuration option explaining that the parent parties identified by ICON and SIP Server might not correspond.

New in Document Version 8.1.508.00

  • Added a short explanation of the new functionality that enables ICON to correctly store the value for otherDN when both an internal (local) DN and an external DN have the same name. This functionality requires you to configure the new Switch-level same-dn configuration option.
  • Added a description of the new use-server-partyuuid configuration option, which enables Interaction Concentrator to support multiple routing scenarios in single-site and multi-site environments running SIP Server release 8.1.102.13 or higher.
  • Added information about the settings required for internationalization on the PostgreSQL RDBMS.
  • Updated a number of ICON configuration options to indicate that the values 0 and 1 are valid as well as the already-documented values of false and true.

New in Document Version 8.1.507.00

  • Updated the descriptions of the store-event-data and EventData options to indicate the settings required to report on EventCustomReporting data (which can be used to report on interaction focus time).
  • Created a Log Events Appendix, which contains full documentation of all Interaction Concentrator log events that have been added since the latest publication of the Framework Combined Log Events Help.
  • Corrected the list of user data keys that must be explicitly specified in the attached data specification file to capture all possible Universal Routing Server (URS) attached data. For details, see Universal Routing Server Attached Data.
  • Updated the description of the ring-divert option to indicate that ICON can identify the PARENTPARTYID and the PARENTLINKTYPE of the Ringing party even if the ring-divert option is set to 0, as long as the lookup-queue-on-ringing option is set to 1.

New in Document Version 8.1.506.00

  • ICON now enables you to run multiple ICON Applications from the same directory using the same executable. See Running Multiple ICON Applications from the Same Directory in the Options tab toggle section for details. The new cfg-dbname option must be configured to support this functionality.
  • The description of the store-releasing-party configuration option has been updated to specify that ICON supports this functionality for all switches that provide the necessary information. To determine whether your switch supports this functionality, check your T-Server/SIP Server documentation.
  • Added a recommendation to set the NLS_LANG environment variable in all installations using an Oracle database.

New in Document Version 8.1.505.00

New in Document Version 8.1.504.00

  • Added a brief statement of support for Hunt Groups, with links to the relevant configuration information.
  • The valid value for minimum re-registration timeout in the gcti-re-registration-tout configuration option has been corrected. 0 is now included as a valid value.

New in Document Version 8.1.503.00

New in Document Version 8.1.502.00

  • Edited the instructions for adding a connection to Interaction Server to indicate that you can now add an Interaction Server type Application object to the ICON Connections tab. See "Configure the Connections tab" on the ICON tab of the Configuration and Installation page. Previously, you had to add a connection to an Application object of the type T-Server, which was a stand-in for the Interaction Server Application object. For the instructions on how to configure the T-Server connection required by previous releases, see "ICON Application" on the Multimedia tab of the Special Configuration Requirements page.
  • Added a new tab—the Multimedia tab—to the Supported Deployment Scenarios page, describing the support for connections to multiple Interaction Servers.
  • Edited descriptions of the following configuration options:
  • Removed the following obsolete configuration options:
    • min-tsync-roundtrip (formerly configured on the Switch configuration object)
    • tsync-threshold (formerly configured on the ICON Application object)
    To view the descriptions of these options, see the 8.1.4 version of the Interaction Concentrator Deployment Guide.

New in Document Version 8.1.501.00

  • Added descriptions of the following configuration options:
  • Added a note about support for single-step conference scenarios to the description of the ring-divert option.
  • Revised the information about the attached data specification file to indicate that changes to the file are now made dynamically. See the Attached Data tab on the Special Configuration Requirements page and the About tab on the Attached Data Specification File page.
  • Updated the configuration recommendations for License Reporting Manager (LRM) to include the updated instructions on how to configure the ICON lrm role for LRM reporting. See the Recommended Role Assignments tab on the ICON Roles page and the License Reporting Manager tab on the Special Configuration Requirements page.

New in Document Version 8.1.401.00

  • The Deployment Guide was converted from PDF-only format to this online format, with the option of printing a PDF, if desired.
  • Added descriptions of two new configuration options, cfg-annex in the Configuration functional group under the [callconcentrator] section and do-not-register, which is configured on the DN configuration object.
  • Updated the name of the new migration script name format used in releases 8.1.4 and higher. For details on the migration scripts, see the Interaction Concentrator 8.1 Deployment Procedure.
  • Added an item to the About Interaction Concentrator topic noting support for encrypted RDBMSs and support for having TEvent attached data hidden in log files. For details on this functionality and how to configure it, see the Genesys Security Deployment Guide.

New in Document Version 8.1.201.00

  • Added information on how to configuring IDB on PostgreSQL and specified the details of DAP configuration appropriate to PostgreSQL.
  • Added notes stating new ICON support for dynamic updates to T-Server host and port changes.
  • Added a section on security features and configuration requirements to the section on Deployment Planning.
  • Added a recommendation to install ICON on the same host as the T-Server or Interaction Server for which it writes data.
  • Added information about the option to purge the persistent queue file upon ICON startup to the information on the Persistent Queue file.
  • Added notes to indicate that the gsysIRMerge and gsysIRMerge2 stored procedures are compatible with Genesys Info Mart 7.x but are not needed by Genesys Info Mart 8.x.
  • Added notes to indicate that the gsysIRMerge and gsysIRMerge2 stored procedures are not applicable to the PostgreSQL RBDMS.
  • Configuration option additions, updates and corrections:
    • Added descriptions of the cseq-adjustment, gls-enforce-reason-code, pq-startup-purge, ring-divert, and gls-improve-data-for-agent configuration options.
    • Added a reference to the information about the GSYS_EXT_INT1 field in the G_PARTY_HISTORY table to the description of the ivr configuration option.
    • Added notes to the om-memory-optimization and calls-in-the-past options stating the releases in which the om-memory-optimization setting could override the calls-in-the-past setting.
    • Corrected and clarified the wording for the gls-acw-first option descriptions for the ICON Application object and the Switch configuration object.
    • Corrected and amplified the description for the sst-options configuration option.
    • Added notes to advise users that the values for the role option must be set in lowercase only, not uppercase or mixed case.
  • Updated the name of the Genesys eServices product by changing it from eServices/Multimedia simply to eServices, its current name. Multimedia was the former product name.
  • Added notes instructing readers to restart the ICON server after any change to the attached data specification file.

New in Document Version 8.1.101.00

  • Purge by Truncating Partitions
    • Described new scripts and stored procedure, purgePartitions811, for creating and using a partitioned Oracle RDBMS that is set up so as to be able to purge data by truncating partitions:
    • Added the purgePartitions811 stored procedure to the list of purge procedures.
    • Noted important considerations to take into account before implementing the purge by truncating partitions functionality.
    • Added deployment instructions for creating a partitioned Oracle IDB that can then be purged using the purgePartitions811 stored procedure.
    • Listed the new initialization scripts used to partition IDB and to enable purging by truncating partitions.
Important
In this release, partitioning is supported only on Oracle 11 or higher.
  • New Configuration Options—Added descriptions of the following configuration options:
    • cfg-auto-resync
    • advanced-ext-party-reconstruction
    • dest-busy-processing
    • x-server-http-trace-level
    • x-server-smtp-trace-level
    • x-server-dbw-debug-level
    • third-party-queue-in-divert
  • Corrected Configuration Option Values
    • Corrected the Changes Take Effect values for the pq-backlog-alarm-threshold and pq-backlog-clearance-threshold options from Immediately to After restart.
  • Added Information on IDB Update Scripts for Genesys Info Mart—Added descriptions of the update_idb_for_gim.sql and update_idb_for_gim_mm.sql scripts, required for environments running Genesys Info Mart.
  • New PQ File Requirement—Added a note informing users of the requirement to locate persistent queue files on a local drive.

Comments or questions about this documentation? Contact us for support!