Release Note

Contents

Introduction

As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesys.com for more details.

This release note applies to all 8.1 releases of Genesys Voice Platform (GVP) Resource Manager.

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Guide.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Contact your customer care representative if you have any questions.

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager (RM).

Corrections and Modifications

This release includes the following correction and modification:

Resource Manager now retries sending inter-node messages that receive the 10035 socket error (WSAEWOULDBLOCK) while being sent. (GVP-21475)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager (RM).

Corrections and Modifications

This release includes the following corrections and modifications:

Resource Manager is no longer unresponsive when calls are forwarded to resources that go offline between calls. (GVP-21176)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager (RM).

Corrections and Modifications

This release includes the following corrections and modifications:

Resource Manager no longer freezes when it receives a CANCEL request after a request timed out. Previously, this scenario caused a memory leak . (GVP-20961)

Resource Manager now correctly replicates the number of ports reserved on a resource for a conference call to the other node in an active-active HA configuration. As a result, both of the RM nodes uniformly maintain resource port usage. (GVP-20960)

Now Resource Manager correctly reports the rejection of a conference call to the other RM node in an active-active HA configuration, and the other RM in the configuration correctly releases the port occupied for that specific conference. Previously, this scenario caused a resource leak on the other node. (GVP-20959)

Resource Manager no longer terminates in a race condition when a timer thread and a sending thread attempt to send a response at the same time. (GVP-20906)

Resource Manager no longer freezes during replication of CallSession Data. (GVP-20905)

Resource Manager no longer freezes during replication of call data during recording. (GVP-20904)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

On the Linux platform, the Resource Manager (RM) no longer terminates in a race condition after handling an INVITE that is followed by a CANCEL. Previously, if the RM sent a recording request to the MCP but quickly terminated that request, the MCP sent an INVITE to the RM and then canceled it immediately. RM processed the canceled request anyway and forwarded the INVITE to a recording server, and then terminated after receiving a 200 OK response. (GVP-20741)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager is now configurable to pass or block the gvp-tenant-id parameter in the INVITE RURI, when it is targeted for a gateway resource, using the new configuration parameter [rm]Pass Tenant-ID to Gateway Resource.

Parameter: Pass Tenant-ID to Gateway Resource
Section: rm
Specifies handling of the gvp-tenant-id parameter in the INVITE RURI, when it is targeted for a gateway resource.
When set to true, RM will pass parameter.
When set to false, RM will not pass the tenant-id RURI parameter.

(GVP-20745)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Voice Platform Resource Manager.

• This release contains changes to support new functionality in Genesys Voice Platform 8.1.7.
• Support for Red Hat Linux 6.0, 64-bit.
• GVP deployments with SIP Server support Resource Manager High Availability Active-Active configuration.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager now supports status notification for resources that support any of the MSML services recordingclient, conference, cpd and treatment. (GVP-20349)

The Resource Manager no longer has a memory leak in an HA (Active-Active) configuration. (GVP-20291)

Resource Manager no longer terminates after receiving an INVITE for recording from MCP, then selecting and saving a list of targets. (GVP-20285 / ER# 324884854)

The Resource Manager in an Active-Active High Availability configuration mode no longer terminates unexpectedly when both nodes sync data following a consultation transfer. (GVP-20256)

The Resource Manager no longer selects SIP AOR for SIP calls when they are offline. The RM selects SIPS AORs when they are online. (GVP-20242)

The Resource Manager now treats the absence of the geo-location header in an incoming header, and in all LRGs having geo-location, as a no match when rm.?reject-recording-request-on-geo-?location-nomatch is set to true. (GVP-20241)

The Resource Manager no longer stops handling calls when duplicate call recording is enabled and third party recording servers are used. (GVP-19633 / ER# 323409481)

The Resource Manager no longer terminates when it must decrement a media-service counter twice because of a race condition during an RM HA failover. (GVP-19632 / ER# 323409055)

The Resource Manager no longer terminates in this situation: the RM received an inter-node cluster message from the other node and while processing this message, lost its connection with the other node. (GVP-19346 / ER# 319605591)

In an HA Active-Active configuration, the Resource Manager nodes now submit CDRs after a call is established for all service types. (GVP-19343 / ER# 319524781)

In an HA Active-Active configuration, the Resource Manager nodes no longer submit duplicate CDRs after receiving a replication message from the remote node saying that a call has ended. (GVP-19295 / ER# 318437461)

The Resource Manager, when deployed in an HA Active-Active configuration setup, no longer stops handling calls when the current call-handling active node is processing a high Call Arrivals Per Second (CAPS) load and the other node joins the HA cluster. (GVP-19288 / ER# 318380113, GVP-19287 / ER# 318380085)

The Resource Manager now correctly handles outbound requests according to the value set in the IVR profile for the parameter use-same-gateway. Previously, RM would use any available configured gateway resource to handle the outbound requests when use-same-gateway value was set to always. (GVP-19223 / ER# 317242201)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager in an Active-Active High Availability configuration mode no longer terminates unexpectedly when both nodes sync data following a consultation transfer. (ER# 323616460)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

When monitoring is enabled and a subscription is active, the Resource Manager no longer sends the status of resources as out-of-service in NOTIFY messages before it receives responses to its OPTION messages. (ER# 321701626)

The Resource Manager (RM) no longer terminates unexpectedly after it decrements the media-service counter twice due to a race condition during frequent failovers in High Availability mode(ER# 316946091)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager no longer stops handling calls when duplicate call recording is enabled and third-party recording servers are in use. (ER# 321478578)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager (RM) now correctly closes SIP TCP connections that have entered a CLOSE_WAIT state. Previously in this situation, the SIP TCP connections would remain unclosed; which could lead to the RM running out of usable TCP sockets, preventing further SIP messages being sent out over TCP. (ER# 320415330)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager nodes in a High Availability Active-Active configuration no longer submit duplicate CDRs when receiving a replication message from the remote node, saying that a call has ended. (ER# 313492233)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager, when deployed in an Active-Active High Availability (HA) configuration setup, no longer stops handling calls when the current call-handling active node is processing a high Call Arrivals Per Second (CAPS) load and the other node joins the HA cluster. (ER# 315264623, 317910250)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager (RM) now correctly handles outbound requests according to the value set in the IVR profile for the parameter use-same-gateway. Previously, RM would use any available configured gateway resource to handle the outbound requests when use-same-gateway value was set to always. (ER# 316394070)

The Resource Manager no longer terminates when it synchronizes data with its HA counterpart and the response comes back before the sending RM can update its transaction record. (ER# 314483785)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Voice Platform Resource Manager.

• The Resource Manager will allow configuring speech resource access policies in tenant/profile and pass that information to MCP.
• The Resource Manager will allow setting usage policies for media services
• Based on geo-location mismatch, the RM will either reject the call or retry another MCP/RecServer LRG.
• The Resource Manager will specify in the CDR which media-service was specified in the RURI of the INVITE from SIP-Server.
• The Resource Manager will support IP Takeover mechanism for active-standby HA in Windows.

Corrections and Modifications

This release includes the following corrections and modifications:

Resource Manager now correctly logs large port numbers in the SIP Message that is received from, or sent to, entries. (ER# 312619349)

Resource Manager (RM) now correctly handles a scenario where many NOTIFY messages are generated as the result of monitored resource status changes. Previously in this scenario, the RM might have become deadlocked. (ER# 311472011)

Resource Manager (RM) nodes no longer send duplicate CDR records in Active-Active High Availability configuration. Previously, because of an issue in RM's cluster logic, the RM node with a lower cluster-id wrongly became the "standby" in an Active-Active configuration, resulting in duplicate CDRs. (ER# 307964421)

Resource Manager (RM) no longer incorrectly reads #gvp.dnis-range as gvp.dnis-range. (ER# 303379005)

Resource Manager now correctly parses INVITEs that contain an empty quoted display name (""). (ER# 313525691)

A new configuration option enables Resource Manager to manage distribution of an outbound request for the same campaign-id to multiple Media Control Platforms (MCP).

Section: [RM]
Option: rm.treat-campaign-as-conference
Default Value: true
Valid Values: true, false
Changes take effect: At restart

Set to true to distribute an outbound request for the same campaign-id to the same MCP.
Set to false to distribute an outbound request for the same campaign-id to multiple MCPs.

Previously, Resource Manager routed the same campaign-id to the same MCP as long as a port was available.

(ER# 306773713)

Resource Manager no longer terminates in the following scenario:

1. Multiple calls with the same campaign ID (for example, OCS calls) are treated as conference calls and are put in a pending call list.
2. These calls are then disconnected before a resource session can be established.

(ER# 306463292)

Resource Manager now correctly updates the related tenant information when an existing resource group is updated. Previously, Resource Manager incorrectly used the root tenant as the related tenant for that group after such an update. (ER# 304506776)

When Resource Manager receives a configuration update, it now verifies whether the notification is received for a different application or for itself. Previously, Resource Manager's log setting was affected even if the log setting had been changed on any of the managed MCP applications. (ER# 301758790)

Resource Manager now correctly handles the condition when overlapping DN entries are configured in tenants. Previously in this situation, Resource Manager would terminate during initialization. (ER# 301594225)

Resource Manager no longer terminates unexpectedly while closing a SIP Transaction. Previously, this situation sometimes caused an assert in the stack. (ER# 301426636)

In Resource Manager (RM), CDR initialization now occurs independently of other module initializations, and occurs before other module initializations. This means that for RM High Availability (HA), the election process is no longer affected by delays that may occur during CDR initialization—as occurred previously. This eliminates the problem of both RMs becoming Master in an active-standby HA configuration. (ER# 298028341)

In High Availability (HA) Active-Active mode, Resource Manager now sends a NOTIFY message to subscribers when it receives a Media Control Platform resource status change through replication from the other Resource Manager node. Previously in this scenario, Resource Manager did not send NOTIFY messages for valid subscriptions. (ER# 297669040)

When Resource Manager is deployed with a single-tenant Configuration Server, it now correctly processes tenant configuration changes dynamically. Previously in this scenario, Resource Manager stopped processing calls and had to be restarted. (ER# 297669024 )

Resource Manager no longer leaks memory when a resource address is wrongly configured with a zero (0) port. (ER# 290372271)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

Resource Manager no longer terminates after receiving an INVITE for recording from MCP, then selecting and saving a list of targets. (ER# 324884854)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

Resource Manager no longer incorrectly sends NOTIFY messages for a SUBSCRIBE request from a SIP Server proxy. Previously, the Route header was not included in the NOTIFY messages, causing the proxy to be bypassed. (ER# 312334456)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This section describes new features that were introduced in this release of Voice Platform Resource Manager.

• This release of Resource Manager supports IP Address Takeover for Windows. To configure GVP Resource Manager (RM) High Availability (HA) using Virtual IP (VIP) Address Takeover for Windows, please follow these steps:
  
  
  1. New script files were added to the Resource Manager IP 8.1.502.87. Verify that the following four files are present in the installation-bin folder:
     
     a. INIT_IPTakeOver.bat
     b. IPTakeOver.bat
     c. Ping.vbs
     d. Check_Ip.vbs
     
     Follow the instructions inside INIT_IPTakeOver.bat (item "a." above) to set the parameters VirtualIP and VirtualInterface.
     
     Follow the instructions inside IPTakeOver.bat (item "b." above) to set the parameters VirtualIP, VirtualInterface, GatewayIP, mymemberid and InterfaceForArping (optional).
     
     IPTakeOver.bat (b.) also contains instructions that you should follow, for using the "arping" utility and other functions.
      
     
  2. In the RM's [cluster] section, set the failoverscript parameter to $InstallationRoot$/bin/IPTakeOver.bat.
     
     
  3. Create alarm-based reaction scripts to execute the failover script which would disable VIP in case of RM crash or shutdown.
     
     To create these scripts, follow these steps:
     
     a. Create a new Third Party Server template.
     b. Create two Reaction Applications.
     c. Create and configure two Alarm Reaction scripts.
     d. Create two Alarm Conditions, to send an alarm when either instance of the RM is stopped intentionally.
     e. Create two Alarm Conditions, to send an alarm when either instance of the RM stops unexpectedly.
     
     Note: Steps b. through e. above—about configuring alarm-based reaction scripts for Resource Manager High Availability—are discussed in detail, in "Appendix E: Resource Manager High Availability" of the GVP 8.1 Deployment Guide, with just one difference: the file to configure in the reaction scripts is NLB.bat in the appendix, and IPTakeOver.bat in these instructions.
     
     
  4. (Optional) Execute INIT_IPTakeOver.bat manually before starting RM in both HA nodes.
     
     

  Note: In some systems, the default heartbeat interval between the two RM nodes (2000 msec) is not suitable for the IP Takeover mechanism. To compensate, Genesys recommends setting the configuration option cluster.heartbeattimer to 8000.

  (ER# 298588431)

Corrections and Modifications

This release contains no corrections or modifications.

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This section describes new features that were introduced in this release of Voice Platform Resource Manager.

• The new configuration option reject-recording-request-on-geo-location-nomatch enables correct handling of non-matching geo-location information.

  Section: rm
  Option: reject-recording-request-on-geo-location-nomatch
  Default Value: true
  Valid Values: true, false
  Takes effect: after re-start

  In the above situation (non-matching geo-location information):

  • When the option is set to false, the Resource Manager retries with another resource group.
  • When the option is set to true, the Resource Manager rejects the call.

(ER# 304472871)

Corrections and Modifications

This release includes the following corrections and modifications:

When non-matching geo-location information is passed in a request to select either MCP or Recording Server, the Resource Manager will now either reject the call or retry another resource group. Previously in this situation, the Resource Manager always retried another resource group. This new behavior is enabled by the new configuration option rm.reject-recording-request-on-geo-location-nomatch, described in the New in This Release section. (ER# 304472871)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This section describes new features introduced in this release of Voice Platform Resource Manager.

• Resource Manager now has a configurable option to manage distribution of an outbound request for the same campaign-id across multiple MCPs.

  Section: RM
  Option: rm.treat-campaign-as-conference
  Default Value: True
  Valid Values: True, False
  Changes take effect: Upon restart

  • Set this option to True to distribute an outbound request for the same campaign-id to the same MCP.
  • Set this option to False to distribute an outbound request for the same campaign-id across multiple MCPs.

  Previously, RM Resource Manager routed the same campaign-id to the same MCP, as long as ports were available. (ER# 304648757)

Corrections and Modifications

This release includes the following corrections and modifications:

Now Resource Manager does not terminate due the following race condition: one thread detects a socket read failure and closes the socket, while another thread sends a message on the same socket at the same time. (ER# 305054141)

Now, Resource Manager does not require a restart for the dynamic addition of new tenants and resource connections. (ER# 304836580)

Resource Manager (RM) now correctly handles an invalid action that it receives in messages from another RM node in High Availability. Previously, RM could terminate in this situation. (ER# 304433067)

Now, Resource Manager does not terminate in this situation: Multiple calls with the same campaign ID (for example, OCS calls) are treated as conference calls, are put in to a pending call list, and are disconnected before a Resource session can be established. (ER# 298653442)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

Resource Manager now correctly handles the condition when overlapping DN entries are configured in tenants. Previously, in this case Resource Manager used to crash during initialization. (ER# 301180711)

When Resource Manager receives a configuration update, it verifies whether the notification is received for a different application or for itself. Previously, Resource Manager's log setting was affected even if the log setting was changed on any of the managed MCP applications. (ER# 300931591)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager no longer terminates while handling a cascaded update from Management Framework in SYNC mode within CCILib. (ER# 300256042)

Resource Manager now no longer terminates unexpectedly while closing a SIP Transaction. Previously, this situation sometimes caused an assert in the stack. (ER# 300007729)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. There are no new features in this release of Genesys Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager now does not unexpectedly terminate when a TLS connection cannot be set up. (ER# 298664814)

Now, when the Resource Manager (RM) receives a SUBSCRIBE message from SIP-Server while still initializing its modules, the message is ignored. Previously, in a similar situation, RM would terminate while trying to process the message. (ER# 296887052)

In Resource Manager (RM), the CDR initialization is now made independent of other module initializations and is done as the first thing when module initializations take place. This way, for RM High Availability (HA), the election process is not affected due to any delays for CDR initialization—as was seen earlier. Thus, the problem of both RMs becoming Master in an active-standby HA configuration is avoided. (ER# 275029916)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Voice Platform Resource Manager (RM).

• 32-bit and 64-bit GVP application binaries are available for Windows and Linux 32-bit operating systems and 64-bit operating systems, respectively.
• Dual stack IPv6, IPv4.
• RM now checks for speech resource status warning code in an error response from MCP. This behavior can be controlled by a configuration parameter.
• Recognition of leading zeros in the Dialed Number (DN).
• Operational parameters management support.
• Multi-site support for summary reporting and policy management.
• Cisco Unified Communications Manager (UCM) support.
• Context services authentication support.

Corrections and Modifications

This release includes the following correction and modification:

Deploying any GVP Windows IP through Genesys Administrator no longer results in an error. Previously, an error message might have occasionally occurred even when the deployment was completed successfully. (ER# 258776961)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager no longer terminates during a dynamic configuration update. (GVP-20563)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager (RM) now correctly handles the scenario where many NOTIFY messages are generated as the result of monitored resource status changes. Previously in this scenario, the RM could become deadlocked. (ER# 311020795)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager, in High Availability (HA) Active-Active mode, now sends a NOTIFY message to subscribers when it receives a Media Control Platform resource status change through replication from the other Resource Manager node. Previously in this scenario, the Resource Manager did not send NOTIFY messages for valid subscriptions. (ER# 295686805)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following correction and modification:

When Resource Manager is deployed with a single tenant Configuration Server, it now correctly processes tenant configuration changes dynamically. Previously in this scenario, the Resource Manager stopped processing calls and had to be restarted. (ER# 296157418)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now shuts down properly. Previously, Resource Manager would take too long to shut down. (ER# 292428771, 295431179)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now checks the state of all transactions before terminating them and, rather than assert after a previous transaction error, it now prints an error message during proper clean-up. Previously in this scenario, the Resource Manager terminated unexpectedly. (ER# 288667811)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. There are no new features introduced in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now makes changes to Logical Resource Groups (LRG) dynamically and changes appear immediately after they are saved. Previously, the Resource Manager had to be restarted before saved changes to LRGs could be seen. (ER# 283326693)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This section describes new features that were introduced in this release of Voice Platform Resource Manager.

• The following new option can be configured in the cluster section of the Resource Manager Application:

  initial-electiontimer
  Default Value: 10000 milliseconds (ms)
  Valid Values: 1000-60000 range, in milliseconds (ms)
  Changes Take Effect: At start/restart

  Use this option to set the time interval for the initial election process when Resource Manger is starting up in High Availability (HA) mode. The default value of this timer has been increased to avoid a race condition that can cause both Resource Manager nodes to be selected as active. Now, if there is no response from the active (master) Resource Manager, the standby Resource Manager becomes active after the expiration of the time interval that is set for this option value.

  Note: Genesys recommends that you wait until the master node becomes active (about 10 seconds) before you start the standby node.

  (ER# 281452279)

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now successfully performs cluster manager restarts. Previously, race conditions would sometimes occur during cluster restarts, which caused Resource Manager to terminate unexpectedly. (ER# 282935578)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now successfully processes bulk update notifications that are sent from Management Framework. Previously in this scenario, the Resource Manager sometimes terminated unexpectedly, due to a STACK_OVERFLOW condition. (ER# 281584848)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager's wildcard matching algorithm now matches incoming DNs with the IVR Profile that is associated with the wildcard prefix. Previously, the Resource Manager sometimes failed to find the IVR Profile. (ER# 281830777)

The sip.transport.localaddress configuration option in the proxy section of the Resource Manager Application has been removed from the default configuration, as this option is no longer used. (ER# 281286121)

Top of Page

Supported Operating Systems

New in This Release

This hot fix is based on an earlier release of the product and does not include new features or corrections made in higher-numbered releases. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

When Resource Manager is deployed as an Active-Active HA pair, it now successfully processes create conference requests from the Call Control Platform. Previously, in an Active-Active HA setup, the Resource Manager sometimes failed to process incoming conference requests and generated the following error message: Unable to allocate physical resource usage. Possibly non-matching security requirement or port usage exceeded. (ER# 280015053)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Voice Platform Resource Manager.

• The following new options can be configured in the rm section of the Resource Manager Application:

  options-errresp-on-noresources
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: At start/restart

  Use this option to send an error response to SIP Server when all resources are offline. When this option is set to true and the Resource Manager determines that all GVP resources are offline after receiving a SIP OPTIONS message, it sends an error response. The error response code is controlled by the rm.resource-unavailable-respcode option.

  resolve-addr-for-aor-match
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: At start/restart

  Use this option to resolve IP addresses to match with the Address of Record (AOR). When this option is set to true, the Resource Manager resolves the hostname or Fully Qualified Domain Name (FQDN) and matches the incoming resource AOR with the configured resource AORs. When this option is set to false, the Resource Manager performs direct-string matching between the AORs.

  invite-custom-header-cleanup
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: At start/restart

  Use this option to remove the Resource Manager-generated custom headers from the SIP Server INVITE request when a new inbound call arrives. When this option is set to true and the Resource Manager receives a new SIP Server INVITE request that contains RM-generated custom headers (from a previous call), it removes them. For example, custom headers X-Genesys-GVP-Session-ID, X-Genesys-GVP-Session-Data, X-Genesys-RM-Application-dbid, and X-Genesys-GVP-CTI-Params.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager now fully supports multiple DID ranges in a DID group. Previously, when multiple DID ranges were configured inside a DID group, the Resource Manager found the associated IVR Profile only if the DN matched the first DID range in the DID group. (ER# 277789001)

The Resource Manager now strips all X-Genesys-GVP-Session-ID custom headers from the incoming INVITE request and treats that call as a new call. Previously, the custom header from the first INVITE request was incorrectly applied to the subsequent MSML SIP call, causing the Resource Manager to reject the call. See the resolve-addr-for-aor-match configuration option description in the New n This Release section of this release. (ER# 277945051)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now adds resource references only after duplicate resources are removed from the Resource Provision table. Previously, the duplicate resources were removed from the table but the references were not, causing the count to exceed the limit and the Resource Manager to terminate unexpectedly. (ER# 277220150)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Voice Platform Resource Manager.

• Supports the Call Recording Solution through recording clients and servers.
• Supports F5 load balancers in High Availability (HA) Active-Active configurations.
• Supports Domain Name Service (DNS) procedure for HA routing as specified in Request For Comment (RFC) 3263.
• Supports Federal Information Processing Standard (FIPS) compliance on Transport Layer Security (TLS) interfaces.
• Supports a new failover mechanism for resources, including Media Server.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager now sends Session Initiation Protocol (SIP) NOTIFY and BYE messages in the correct order. Previously, the BYE message was sent before the NOTIFY message due to a multi-thread DNS resolution. (ER# 260437758)

Resource Manager HA failover now works correctly with CDR logging. Previously, Call Data Record (CDR) objects were kept inside the CDRServiceImpl class. When failover occurred and the standby node took over, a CDR object was not replicated. Therefore, when the BYE message was processed in the new active node (previously the standby node), the CDR object could not be found and call completion was not properly logged. (ER# 219215620)

The logging path for the ccilib.*.log has been changed in the log.all configuration option so that logs are now stored in a non-GVP directory. (ER# 268953628)

Resource Manager now calculates the least-percentage load balancing scheme so that the resource with the highest ratio is selected. Previously when least-percentage was calculated, the usage value was rounded up, which sometimes caused inaccuracies in resource selection. (ER# 267362491)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now accepts SIP INVITE messages that include Genesys custom headers with the same GVP-SESSION-ID as those from a previous session and treats them as new calls. Previously, when the Resource Manager received these custom headers, it assumed they were for orphaned calls and rejected the request, responding with a 480 Temporarily Unavailable error message. (ER# 272633796)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager no longer responds to OPTIONS messages from other components when it detects that all GVP resources (Media Control Platform, Call Control Platform, and CTI Connector) are offline. This issue has been resolved in this release.

Note: This behavior is configurable and is on by default.

(ER# 272132121)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now shuts down in the correct sequence during uninitialization. Previously, an incorrect shutdown sequence caused the Resource Manager to terminate unexpectedly. (ER # 269891403)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

When Resource Manager is configured for High Availability (HA), session information in the X-Genesys-GVP-Session-Data custom header is now serializes to correctly handle requests from the CTI Connector. Previously, when Resource Manager was in Active-Active HA mode and the session information was not yet replicated to the second Resource Manager, CTI Connector requests were mistaken for new call requests. (ER # 268617561)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now retains only one entry per SIP subscription in its internal map at HA failover. Previously at failover, the newly active Resource Manager would incorrectly add two entries for the same subscription in the HASHMAP; if an unsubscribed request then arrived for an existing subscription, the Resource Manager unexpectedly terminated. (ER # 264737038)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

Updates to connection objects in Resource Manager no longer cause the server to terminate unexpectedly. Previously in this scenario, when the connected object was a non-GVP resource, and the object update occurred someplace other than in the application parameters section of the connection, the server would sometimes terminate unexpectedly. (ER# 262919098)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager Common module now reconnects to Configuration Server when the primary Configuration Server instance in an HA environment unexpectedly terminates. Previously in this scenario, when the primary Configuration Server terminated, the connection to the backup Configuration Server could not be fully and correctly restored. (ER# 262670618)

Updates to the non-Logical Resource Groups (LRG) folders in Configuration Server no longer generate error logs and alarms in Resource Manager. Previously in this scenario, when the non-LRG folder object data was modified and updated, it generated an error log (and subsequent alarm) in Resource Manager, stating that the LRG map information could not be found. (ER# 262670559)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now correctly references a resource, such as Media Control Platform, when it is removed from a resource group. Previously in this scenario, the reference to the resource was released while the resource was still in use, which caused the Resource Manager to terminate unexpectedly. (ER# 262099461)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. There are no new features in this release of Voice Platform Resource Manager.

Corrections and Modifications

This release includes the following corrections and modifications:

To enhance Resource Manager performance, the size of the UDP socket buffer is now larger and configurable. (ER# 259891811)

The Resource Manager now correctly processes 200 OK responses to INVITE messages that are received after a BYE message. Previously in this scenario, the Resource Manager would unexpectedly terminate. (ER# 259876113)

The Resource Manager Installation Package (IP) now includes a gvp section in the installation template with default option values that are compatible with Windows and Linux operating systems. The gvp.nic.eth0 and gvp.nic.eth1 options values are empty (by default) for compatibility with Windows, and the gvp.nic.linkattribute and gvp.nic.up options (which are ignored by Windows OS) have default values. (ER# 260775555)

High Availability Resource Manager is improved by the inclusion of new NLB.bat scripts for Windows Network Load Balancing (NLB), which resolve the issue of latency in failover when the active Resource Manager host reboots.

Note: The new NLB.bat file must be used together with the recommended configuration in the Genesys Voice Platform 8.1 Deployment Guide, which instructs the user to configure the Default state parameter in the Initial Host State section of the NLB properties to Stopped for the correct NLB configuration of the HA environment.

(ER# 260635288)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Voice Platform Resource Manager.

• Support for Windows 2008, 64-bit OS in 32-bit compatibility mode.
• Support for Red Hat Enterprise Linux 5.4, 64-bit OS in 32-bit compatibility mode.
• Support for VSphere 4 Hypervisor, VMware.
• Support for static routing for active/backup resources, such as SIP Server.
• Support for Client Side Port Definition (CSPD) for the connection between GVP components and Configuration Server (Management Framework).

Corrections and Modifications

No corrections or modifications have been made in this release.

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now rejects the transfer request to CTI Connector when the transfer is disallowed. Previously in this scenario, the original service type for the call session was not valid, which caused the Resource Manager to terminate unexpectedly. (ER# 258009792)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

The Resource Manager installation template now includes a gvp section with default option values that are compatible with Windows and Linux operating systems. The gvp.nic.eth0 and gvp.nic.eth1 options have empty (or no) default values for compatibility with Windows, and the gvp.nic.linkattribute and gvp.nic.up options (which are ignored by Windows OS) have default values. (ER# 260630413)

The Resource Manager Common module now reconnects to Configuration Server when the primary Configuration Server instance in an HA environment unexpectedly terminates. Previously in this scenario, when the primary Configuration Server terminated, the connection to the backup Configuration Server could not be fully and correctly restored. (ER# 260092551)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Voice Platform Resource Manager (RM).

• Support for Hierarchical Multi-Tenancy (HMT).
• Support for TDM Configurations (T1 ISDN/RobbedBit, E1 ISDN/CAS) using Dialogic (JCT, DMV-A, DMV-B boards) with the PSTN Connector component.
• Support for multiple Media Control Platforms (MCP) installations on a single physical machine.
• Support for Reporting by Tenant for HMT.
• Support for Operational Reporting for PSTN Connector and CTI Connector components.
• Support for PSTN Connector and Supplementary Services Gateway (SSG) real-time dashboards.
• Support for Direct Inward Dialing (DID) Groups.
• Support for MSML for Media Server control including the following MSML elements: DTMF Gen, DMTF Collect, MSML Conference, and MSML Record.
• Support for setting the type-of-service priority for outbound SIP message packets for UDP, TCP, and TLS transport protocols.
• Support for enhanced outbound call distribution.
• Support for active cluster (Active-Active configuration) for Resource Manager High Availability.
• Support for Windows Server 2008.
• Support for Red Hat Enterprise Linux 5.4.

Corrections and Modifications

This release includes the following corrections and modifications:

Resource Manager no longer takes 3 to 5 minutes to start when deployed on a Red Hat Linux operating system. (ER# 224881075)

Resource Manager now distributes regular and engaging sessions over multiple Media Control Platforms in a way that reduces connection time when bridging is attempted between regular and engaging sessions in ASM Mode. (ER# 238671191)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

The Resource Manager now initiates the election process to determine active/standby status for each node, and enables Network Load Balancing (NLB) for the active node only. Previously, when the heartbeat-timer parameter timed out, the connection was lost and each node attempted to become active by disabling NLB on the other node, blocking all calls to the NLB cluster. When the connection was reestablished no further action was taken to determine the status and enable NLB for an active node. (ER# 247397832)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Voice Platform Resource Manager (RM).

• On Windows operating systems, RM is now installed as a Windows service and can be configured to start automatically.
• Supports outbound calling in the following ways:
  • Acts as a notifier, accepting SIP SUBSCRIBE requests from SIP Server.
  • Manages call information policies for outbound calls.
  • Accepts campaign, tenant, and IVR Profile information from SIP Server for outbound requests.
  • Supports the media dialog through the media server module of the MCP with the addition of a new msml service type.
• Supports conference failover.
• Supports active and passive resources, which allows additional high availability configurations.
• The Resource Group Wizard in Genesys Administrator has been enhanced to enable configuration of both SIP and SIPS ports, and enables redundancy configuration as active or passive.
  

Corrections and Modifications

This release includes the following corrections and modifications:

The SIP endpoint that initiates calls to Resource Manager (RM) no longer needs to be configured as one of the gateway resources when the IVR Profile has the gvp.policy.use-same-gateway parameter set to always. Previously, when this parameter was set to always, and RM could not identify a Gateway resource that had the same address as the sender's address, it failed that call. Now, RM falls back to select any available Gateway Resource. (ER# 218622753)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. This section describes new features that were introduced in the initial 8.1 release of Voice Platform Resource Manager.

• Support for the Red Hat Enterprise Linux 4 Operating System.
• Support for existing VoiceXML and call control applications deployed on GVP 7.6 through the GVP Interpreter (GVPi), the GVP 7.6 legacy VoiceXML interpreter.
• Support for a new Computer Telephony Integration (CTI) Connector to enable integration with the Genesys IVR Server, allowing access to the larger Genesys suite of products, and supporting CTI with the legacy GVP VoiceXML Interpreter and TXML.
• High availability enhancements, including support for Resource Manager hot-standby failover.
• Support for installing and configuring multiple instances of the same component with the Genesys Administrator Installation Wizard.
• Support for easy creation of IVR Profiles with the Genesys Administrator IVR Profile Wizard.
• Support for easy creation of Logical Resource Groups with the Genesys Administrator Resource Group Wizard.
• Addition of bursting policies and related reporting.

Corrections and Modifications

This release includes the following corrections and modifications:

Resource Manager (RM) now reads the ccxml-usage-limit-exceeded-alarm parameter correctly and writes the alarm-level event 20112 to the logs. (ER# 192095539)

RM no longer ignores the Min-SE header in incoming messages. Previously, RM used the value configured in either the sip.sessiontimer parameter of the tenant or IVR Profile, or the value configured in the proxy.sip.sessionexpires option in the SIP messages as the Session-Expires header. This caused confusion for some SIP clients. (ER# 192961047)

RM no longer unexpectedly exits if the SIP From header exceeds more than 2000 characters. (ER# 173250259)

RM now retries the request with another resource if it cannot establish a TCP socket connection to a SIP resource. (ER# 194138143)

Top of Page

Documentation Corrections

This section provides corrections and updates for issues found in currently released documentation for this product. The changes described here will be included in future published versions of the document.

When SIPS is used in an RM HA Active-Active configuration, there is a limitation:

All calls going to the RM will be sent with the specified transport that is set in the VoIP service DN (TCP or UDP) that is specified in the setting for contact=::msml. (SIP-6584 / ER# 324235051)

Top of Page

Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.

When DNS High Availability routing is enabled, the Resource Manager may terminate if the hosts are not resolvable when a DNS query fails.

Workaround: Make sure that the hosts are resolvable all the time. One way to accomplish that is to add them to the hosts file. (GVP-20353 / ER# 325245910)

GVP SIP components may begin rejecting TCP connections after extended periods of TCP usage. (GVP-19552 / ER# 322734450)

The Resource Manager MIB data (scalar table) may not reflect the correct number when running in an Active-Active configuration. (GVP-20257)

In a Resource Manager Active-Active cluster, during the brief period when a node with higher priority comes online, one of the RMs may respond to OPTIONS pings with a 503. The result: calls are directed to that RM for a brief period of time. (GVP-19668 / ER# 323890741)

When the Monitor method is enabled and subscription is active, the Resource Manager no longer sends the status of resources as out-of-service in NOTIFY messages before it receives actual responses for OPTION messages. (GVP-19634 / ER# 323409487)

Resource Manager (RM) sometimes terminates unexpecedly when a user attempts to shut down RM while it is receiving configuration updates from Configuration Server. (ER# 310757131)

Resource Manager currently does not support OPM parameters that have a key name in capital letters at a solution level. (ER# 308408081)

Virtual IP (VIP) Address Takeover for Windows is less reliable than a Windows NLB cluster configuration.

Adding or removing an IP address using VIP Address Takeover is more complicated than enabling or disabling a port in the Windows NLB configuration. VIP Address Takeover fails when either command fails on the backup or the primary. By comparison, in the Windows NLB configuration there is no dependency on the backup command to succeed for most of the failover scenarios.

It takes longer for Netsh (the Microsoft utility that is used for IP Address Takeover) to modify the network configuration than it takes to enable or disable a port in the NLB configuration. In addition, the time may depend on a particular NIC and its configuration. Normally, modification takes less than 15 seconds to execute, but in this situation it can take as long as 30-45 seconds.

Note: The Netsh command can fail if the NIC configuration is already being accessed through the Network Properties User Interface.

Changes to the Windows Server 2008 ARP cache updating mechanism interfere with VIP Address Takeover.

In short, when a gratuitous ARP is sent by Windows Server 2008, it sets the SPA field in the initial request to 0.0.0.0. As a result, the ARP of neighbor caches of systems receiving this request is not updated, and the problem for HA systems (systems that use GARP to facilitate moving the VIP when a system goes down) is that the system will now have to wait for the OS to time-out the neighbor cache. This adds excessive additional time to the failover, causing some functions to fail for RM HA.

To resolve this, Genesys offers three recommendations:

1. Install Microsoft HotFix 2582281 (http://support.microsoft.com/kb/2582281) when running one of the following operating systems:
   - Windows Server 2008 Service Pack 2 (SP2)
   - Windows Server 2008 R2 Service Pack 1 (SP1)
   
   
2. Use the arping utility for Windows Server 2008; this function generates a regular ARP request (not a GARP) on demand. A regular ARP does not specify set the SPA field to 0.0.0.0 and thus, the neighbor cache is updated immediately.
   
   In the case of RM HA, arping is used to send an ARP to the gateway/router, to update its ARP cache.
   
   There is no native arping implementation for Windows (unlike Linux). Genesys recommends the following implementation to use it for testing: http://www.habets.pp.se/synscan/programs.php?prog=arping
   
   The pre-built download location of the latest "arping" binary for Windows is: http://mathieu.carbou.free.fr/pub/arping/2.06/arping.zip
   
   The IPTakeOver.bat file itself contains instructions for how to use arping.
   
   Note that the Windows arping implementation works with IPv4 only.
   
   
3. Place the SIP UA that sends a request to the RM (in this case, SIP-Server) into a different subnet than the RM nodes. This recommendation is based on #2 above. Since the RM can be provisioned to handle a relatively large number of SIP-Servers, that configuration would require the RM to send an ARP request using arping to all those SIP-Servers. That would require the user to configure those SIP-Servers in the IP Address Takeover script, and to update the script as new servers are introduced. Do so requires care to succeed.
   
   Instead, Genesys recommends that you use arping to send ARP (after failover) to the default gateway/router, only to minimize the list of servers to which ARP should be sent. If the gateway/router is in an HA configuration (primary-backup pair) then send ARP to both nodes. In that case, when a request from SIP-Servers that are located in different subnets comes to the gateway/router, it is sent to the correct RM node because its ARP cache is already updated.

The InterfaceForArping requires the user to specify the correct device for the virtual interface. Follow these steps to get this information from the registry:

1. Start Regedit and go to the HKLM\SYSTEM\CurrentControlSet\Control\Network\ directory.
2. Identify the Key with the value {Default} and the data Network Adapters.
3. If the virtual interface is set for Local Area Connection, then search the listed adapter (in the registry) for the value name that contains the data Local Area Connection.
   The Key that contains Local Area Connection is the reference to the physical device identifier.
4. Pre-append \Device\NPF_ to the Key and set this value for InterfaceForArping.

Example: \Device\NPF_{85FEBE1C-9EEF-4E61-974B-1158DB270F6E}
From this key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{85FEBE1C-9EEF-4E61-974B-1158DB270F6E}

Find these scripts on your Installation CD or in the IP 8.1.502.87 package that you downloaded over the internet:

Ping.vbs

• Ping host and return 1 if ping successful, 0 if not, -1 if target not specified.

Check_ip.vbs

• Check if IP address (arg0 ) can be found on host (arg1 )
• Return 1 if found, 0 if not, -1 if address and host not specified

INIT_IPTakeOver.bat

• Optional. You can manually execute this batch script, to disable the Virtual IP interface in the RM box before starting the RM process.

IPTakeOver.bat

• Enable or disable the Virtual IP interface in the RM box, during RM's own internal election process or when a failover event occurs.

(ER# 298588431)

Resource Manager crashes in a race condition while processing CANCEL . The race condition is caused by SIP Server sending CANCEL after a Media Control Platform crash. (ER# 305137359 )

If RM receives a SUBSCRIBE message from SIP Server while still initializing, an unexpected shutdown may be observed in RM's DataModule, and RM then terminates. This is a random occurrence depending on some timings. (ER# 296887052)

In active-standby HA mode for RM, if the DataModule cluster initialization is delayed for any reason, the election message processing can be affected and both RMs try to become active. In this scenario, you can check for one or two things:

• A possible network issue.
• If the Reporting client is timing out while trying to connect to the Reporting Server, and therefore affecting initialization.

(ER# 275029916)

The following corrections (in red below) have not yet been made to the Genesys Voice Platform 8.1 Deployment Guide:

• Page 8 (table of contents) and page 399: The procedure title should read, "Creating Alarm Reaction Scripts, Conditions, and Reaction Applications (Linux and Windows)".
  
• Page 407: In the procedure "Creating an Alarm Condition for RM stopped unexpectedly," Step 1 should read,
  1. In Genesys Administrator, go to Provisioning > Environment > Scripts Alarm Conditions.
  
• Page 407: In the procedure "Creating an Alarm Condition for RM stopped unexpectedly," the second bullet point under Step 3 should read, "Description: primary RM stopped unexpectedly or backup RM stopped unexpectedly."

(ER# 299905181)

Deploying any GVP Windows IP through Genesys Administrator may occasionally result in the following error, although the actual deployments are completed successfully:

Execution of installation failed. Retcode = 1

(ER# 258776961)

Resource Manager High Availability failover does not work correctly with CDR logging. Currently, CDR objects are kept inside the CDRServiceImpl class. When failover occurs and the standby node takes over, this CDR object is not replicated. Therefore, when BYE is processed in the new active node (previously standby), the CDR object cannot be found and the call end will not be logged properly. (ER# 219215620)

Resource Manager could still route calls to an unassigned GVP Configuration Unit (CU) because Configuration Server does not dynamically update the deletion of the gvp.resources section in that CU if that is the last section to be deleted. To work around this, manually create a dummy section in the CU, with a dummy parameter, so that Configuration Server will always send notifications of deletions when the gvp.resources section is deleted from the CU. (ER# 242188298)

When cloning from VMWare images, Genesys recommends that you change the Address of Record (AOR) manually on the connections for Resource Manager. (ER# 240076331)

Resource Manager does not distribute regular and engaging sessions over multiple Media Control Platforms in a way that reduces connection time when bridging is attempted between regular and engaging sessions in ASM Mode. (ER# 238671191)

Resource Manager (RM) continues to accept announcement calls when the announcement-allowed option is set to false in the IVR Profile. This issue occurs under the following conditions:

• Calls comes to RM from a Gateway resource that has CTI Usage set to Based on DN Lookup in the logical group it belongs to.
• The mapped IVR Profile has CTI Allowed set to CTI using IVR Server is not allowed.

(ER# 230809547)

The RM application, when deployed on a Red Hat Linux operating system, might typically take 3 to 5 minutes to start. (ER# 224881075)

If an IVR Profile has the gvp.policy.use-same-gateway parameter set to always, Resource Manager (RM) forwards the outbound request to exactly the same gateway resource already associated with the RM session. Therefore, the SIP endpoint (which would be the SIP Server in a typical deployment) that initiates calls to RM must be configured as one of the gateway resources when this configuration parameter is set to always. (ER# 218622753)

In RM High Availability (HA) configuration, calls are not processed in the first 15 seconds when an HA pair is started simultaneously. To workaround this issue, start RM instances in a safe interval of 15–30 seconds apart, or if started simultaneously, allow some startup time (approximately 15 seconds) for the RM algorithm to elect the active node before taking live traffic. (ER# 214740001)

When a SIP resource sends a redirection response (301 or 302) back to RM, if the SIP resource returns multiple SIP destinations to redirect to, RM takes the first of these SIP destinations to redirect the request to. (ER# 193841929)

Top of Page

Discontinued Support

This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list.

There are no discontinued items for this release.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no known internationalization issues for this product.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Genesys Voice Platform 8.1 Deployment Guide first.

• Genesys Voice Platform 8.1 Deployment Guide, which provides information about installing and configuring Genesys Voice Platform (GVP).

• Genesys Voice Platform 8.1 User's Guide, which provides information about configuring, provisioning, and monitoring GVP and its components.

• Genesys Voice Platform 8.1 Genesys VoiceXML 2.1 Reference Help, which provides information about developing Voice Extensible Markup Language (VoiceXML) applications. It presents VoiceXML concepts, and provides examples that focus on the GVP Next Generation Interpreter (NGI) implementation of VoiceXML.

• Genesys Voice Platform 8.1 Legacy Genesys VoiceXML 2.1 Reference Manual, which describes the VoiceXML 2.1 language as implemented by the Legacy GVP Interpreter (GVPi) in GVP 7.6 and earlier, and which is now supported in the GVP 8.1 release.

• Genesys Voice Platform 8.1 CCXML Reference Manual, which provides information about developing Call Control Extensible Markup Language (CCXML) applications for GVP.

• Genesys Voice Platform 8.1 Troubleshooting Guide, which provides troubleshooting methodology, basic troubleshooting information, and troubleshooting tools.

• Genesys Voice Platform 8.1 Configuration Options Reference, which replicates the metadata available in the Genesys provisioning GUI, to provide information about all the GVP configuration options, including descriptions, syntax, valid values, and default values.

• Genesys Voice Platform 8.1 Metrics Reference, which provides information about all the GVP metrics (VoiceXML and CCXML application event logs), including descriptions, format, logging level, source component, and metric ID.

• Genesys Voice Platform 8.1 SNMP and MIB Reference, which provides information about all of the Simple Network Management Protocol (SNMP) Management Information Bases (MIBs) and traps for GVP, including descriptions and user actions.

• Genesys Voice Platform 8.1 Web Services API wiki, which describes the Web Services API that the Reporting Server supports.

• Voice Platform Solution 8.1 Integration Guide, which provides information about integrating GVP 8.1, SIP Server 8.0, and, if applicable, IVR Server.

• Composer 8.1 Deployment Guide, which provides installation and configuration instructions for Composer.

• Composer 8.1 Help, which provides online information about using Composer, an Integrated Development Environment used to develop applications for Genesys Voice Platform and Universal Routing.

• Framework 8.1 Deployment Guide, which provides information about configuring, installing, starting, and stopping Framework components.

• Framework 8.1 Genesys Administrator Deployment Guide, which provides information about installing and configuring Genesys Administrator.
• Framework 8.1 Genesys Administrator Help, which provides information about configuring and provisioning contact center objects by using the Genesys Administrator.

• Framework 8.1 Configuration Options Reference Manual, which provides descriptions of the configuration options for Framework components.

• Framework 8.1 SIP Server Deployment Guide, which provides information about configuring and installing SIP Server.

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).

Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page