Release Note

Contents

Introduction

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.genesyslab.com for more details.

This release note applies to all 8.1 releases of Call Progress Detection (CPD) Server.

• 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 functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me. Please contact your Genesys Customer Care representative if you have any questions.

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release.

• This release is compatible with Outbound Contact Server release 8.1.300.12..

Corrections and Modifications

This release does not include any corrections and modifications.

Top of Page

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of CPD Server:

• DTMF Tones Detection During and After Play of the Drop Announcement in ASM modes—Ability to detect DTMF tones during and after the playing of the drop announcement message in ASM modes when the called party presses buttons on the touch tone phone; ability to deliver string of detected tones to OCS.

• Enhanced Security features:

  • Ability to use the tag option to hide sensitive information contained in logs.
  • Support for Transport Layer Security (TLS).

• Enhanced Compliance with Regulatory Requirements:

  • Compliance with Federal Information Processing Standards (FIPS).

Corrections and Modifications

This release also includes the following corrections and modifications:

For HMP (Host Media Processing) deployments, this release of CPD Server should be run with HMP SU 328 or later. This HMP SU addresses the problem with one-way audio on calls. (ER# 316817822)

Note: Starting from this release, CPD Server might not start with releases of HMP SU earlier than 328.

CPD Server no longer incorrectly reports a call as transferred if an error is received for RequestCompleteTransfer. Previously when this error was received, the call was sometimes reported incorrectly as transferred. (ER# 316239948)

CPD Server Proxy now starts properly. Previously, it failed to start and the following message appeared: The program can't start because MSVCP80.dll is missing from your computer. Try reinstalling the program to fix this problem.. (ER# 311396924)

In HMP transfer mode with tscall = on, CPD Server does a proper cleanup for the DN associated with the HMP channel before using it again for outbound calls. Previously, the DN related to the channel was sometimes left in a busy state that caused an error during the next call. (ER# 309763567)

The accuracy of the call_timeguard_timeout has been improved to ensure that it starts at the correct time. Previously, the timeout might have been off by up to several hundred milliseconds. (ER# 300609261)

Top of Page

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of CPD Server:

• Detection of Answering Machine Final Beep—CPD Server used with DM3 boards or with HMP software can now detect the final beep following an answering machine greeting on a call. This ensures that a voice message left on the customer�s answering machine device is recorded from the beginning and not truncated.

• Enhanced Support for Caller ID and Display Name—CPD Server can now deliver Caller ID and Display Name to SIP Server in HMP transfer mode (as configured by the CPN Digits and CPN Display Name OCS settings). The Caller ID and Display Name information is then passed on further by SIP Server, so that it appears on the customer's phone display.

• Support for a Host with Multiple NICs on Board—CPD Server used with HMP software is now capable of properly supporting a host with multiple Network Interface Cards (NIC) on board.

Corrections and Modifications

This release also includes the following corrections and modifications:

CPD Server no longer considers the dialing phase of a call successfully completed in the following scenario:

1. The dialed call has been disconnected on the remote end, and pre-connection call-progress analysis (CPA) is completed with the cadence break call result.
2. The cadence break CPA result is received by CPD Server before a GCEV_DISCONNECTED event is received from the Dialogic API.

Previously in this scenario, CPD Server considered such a call as successfully dialed. As a result, CPD Server bridged this unsuccessful call with an engaging call in ASM mode, or attempted to transfer it to a Voice Transfer Destination DN in transfer mode.

This correction applies to the following line types: sip-hmp, sip-hmp-asm, line-side-dm3, and isdn-dm3.

(ER# 283721485)

CPD Server now correctly uses the value from the continuous-no-signal option to determine the timeout for detecting the No Ringback call result while performing post-connection call-progress analysis (CPA). Previously, CPD Server set a much longer timeout without reference to the continuous-no-signal option.

This correction is applicable to the following line types: isdn-dm3, sip-hmp, and sip-hmp-asm.

(ER# 277926453)

Call Progress Detection (CPD) now works properly with the FlexLM license manager, version 11.9, using IPv6. (ER# 276850880)

CPD Server now properly detects negative call results, such as SIT and Busy, in the following scenario:

• Dialogic returns negative pre-connect results, such as operator intercept or line busy.
• EventDestinationBusy does not arrive from T-Server.

Previously in this scenario, CPD Server erroneously detected a Transfer Error call result.

(ER# 276064227)

CPD Server now correctly handles Call Progress Analysis (CPA) of a channel when EventOffHook arrives after the time interval specified by the option off-hook-timeout expires, and the following conditions are both met:

• The option off-hook-delay is set to a negative value (-1).
• Dialing is done by T-Server (option tscall=true).

Previously, CPA was terminated on subsequent use of this channel.

(ER# 276064007)

Top of Page

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions in this release. No new features were introduced in the initial 8.1 release of CPD Server.

Corrections and Modifications

This release includes the following corrections and modifications that were made between 8.0 releases and the initial 8.1 release:

CPD Server now correctly supports Agent Assignment in Multiple Campaigns in engaging dialing modes for ISDN and ISDN-DM3 line types (that is when CPD Server option line-type is set to isdn or isdn-dm3 values). CPD Server now updates user data of the engaging call with the Campaign Group identifiers immediately after CPD Server receives the EventRouteRequest or EventQueued event on the Voice Transfer Destination DN.

Previously, CPD Server updated user data of the engaging call with the Campaign Group identifiers only after it received a CONNECT message from PSTN; that is, when the engaging call was already established on an agent�s DN. As a result, Universal Routing Server did not receive Campaign Group identifiers for the engaging call and could not route the call in accordance with the Agent Assignment. (ER# 264994438)

CPD Server now correctly reconnects to Configuration Server after a switchover from the primary Configuration Server to its backup. (ER# 263743705)

CPD Server is now able to properly switch from backup mode to primary mode in the following scenario:

1. A high-availability (HA) pair of CPD Servers (primary and backup) is configured and running.
2. The CPD Server that is running in primary mode is switched to backup mode.
3. The same CPD Server is switched back to primary mode from backup mode.

Previously, CPD Server was not able to properly re-initialize Dialogic subsystem upon switching from backup mode back to primary mode in this scenario. (ER# 260769780)

In the ASM mode, if the OCS asm_drop_announcement_data option is configured to play an announcement before a call is released, CPD Server now sends the Rsp_CallProgress message to Outbound Contact Server (OCS) before playing the announcement. This enables dialing optimization if the number of free channels is sufficient to dial the next outbound call(s).

Previously in this scenario, if CPD Server could not bridge the engaging and outbound calls, it sent the Rsp_CallProgress message to OCS after the announcement was played. For predictive algorithms, this delayed dialing for the length of the time it took to play the announcement, and especially impacted dialing when using the small group predictive algorithms. (ER# 226796328)

Top of Page

Known Issues and Recommendations

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

For some SIP endpoints, when an agent places a call on hold a second time, Music-on-hold (MOH) might not work due to improper Session Description Protocol (SDP) from SIP Server 7.6. In order to use MOH with SIP Server 7.6 for all call processing port DNs in the iptB<n> subfolders under HMP configuration folder (as specified in CPD Server's location option), do the following:

• Provision SIP URI in each DN's contact option. For instructions on how to provision SIP URI, see the "Configuring Endpoints" section of Chapter 5 in the SIP Server 7.6 Deployment Guide.
• Set the DN�s reinvite-requires-hold option to true.

Note: This requires that you use HMP SU 195 or higher.

(ER# 185277611)

In ASM (Active Switching Matrix) modes, CPD Server may send a message that the channel is released before it is actually released. This happens in the following situation:

1. One of the bridged calls is released.
2. CPD Server sends a notification to OCS immediately that both channels were released. However, the real channel release for the other call happens only after the channel disconnection procedure is completed by the Dialogic board.
3. OCS sends a request to CPD Server to make a new call before the Dialogic board has completed the channel disconnection procedure.
4. CPD Server may not be able to make the call due to a lack of available channels.

(ER# 122338771)

CPD Server Proxy improperly handles ports, returning No Ports Available messages when some are available. (ER# 165547292)

The SIP REFER method is not supported. (ER# 132746363)

The CPD Server Wizard always specifies the iptB parameter as 0, even if a number other than 0 is specified in the Wizard. (ER# 120709158)

The CPD Server Wizard DN Range properties window does not allow you to specify a Digital Resource DN. As a result, the DNs are numbered starting at 1. (ER# 120709165)

When the backup CPD Proxy becomes primary, all subsequent calls have a call_result of No Ports Available. (ER# 5369951)

When using the Wizard to install CPD Server, the License section is not included on the Options tab of the CPD Server application in Configuration Manager. (ER# 94932)

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 product.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no internationalization issues for this product.

Top of Page

Additional Information

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

• The Outbound Contact 8.1 Deployment Guide provides architectural information, instructions on how to install and configure Outbound Contact 8.1 components, configuration option descriptions, and other related information.

• The Outbound Contact 8.1 Reference Manual describes application features for Outbound Contact 8.1 and provides information about constants, communication protocols, and other information.

• The Framework Genesys Administrator Help file describes how to use Genesys Administrator.

• The Outbound Contact Manager 7.6 Help file describes how to use Outbound Contact Manager.

• The Framework Combined Log Events Help file describes log event messages for Outbound Contact Server and other Genesys products.

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

Note: For the DVD/CD, the New Documents on this DVD/CD 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