Release Note

Voice Platform
Call Control Platform

8.0.x

Genesys Telecommunications Laboratories, Inc. © 2008

Contents

Introduction

Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows
8.0.004.47 [06/27/08] – General (Under Shipping Control)           X

Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


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.0 releases of Voice Platform Call Control Platform.

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.


Release Number 8.0.004.47 [06/27/08] – General (Under Shipping Control)

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

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

New in This Release

This is the first release for this product. This release is under shipping control. This section describes new features that were introduced in the initial 8.0 release of Voice Platform Call Control Platform.

Corrections and Modifications

This release includes the following corrections and modifications:


No corrections or modifications have been made in this release.


Top of Page


Known Issues and Recommendations

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


When a CCXML application uses a <merge> tag, and the endpoint receiving the SIP REFER message sends a non-202 SIP response followed by a SIP NOTIFY message to the Call Control Platform (CCP), the merge failed event is sent to the CCXML application. However, if the CCXML application exits, a SIP BYE is not sent to the endpoint. (ER# 174430601)

Found In: 8.0.004.47 Fixed In: 

When a BYE message is received from a SIP endpoint while CCP is executing a join operation between that endpoint and another endpoint, the error.conference.join event is generated, but the reason property is not connection.disconnected. (ER# 174430521)

Found In: 8.0.004.47 Fixed In:  8.1.001.60

Using hints (hint.confmaxsize) to specify the maximum size for a conference in a <createconference> does not work correctly. The CCP uses the confmaxsize Request-URI parameter set to the configured value in the Request-URI to create the conference. (ER# 174561985)

Found In: 8.0.004.47 Fixed In:  8.1.001.60

If a <merge> event fails, the error.merge event is generated. This conforms to the 2005/06/29 Last Call Working Draft CCXML specification which specifies that the error.merge event is the correct event. The latest CCXML specification specifies that a connection.merge.failed should be thrown for failed merges. (ER# 174561929)

Found In: 8.0.004.47 Fixed In: 

A graceful shutdown followed by a stop in Solution Control Interface (SCI) for CCP does not clean up existing calls if the calls are held longer than the CCP option ccpccxml.shutdown_grace_period configured value. (ER# 183796651)

Found In: 8.0.004.47 Fixed In:  8.1.001.60

CCP does not send two connection.merged events for each connection if the <disconnect> event occurs immediately after the <merge> event within the same transition. Instead, CCP sends a connection.merged event and a connection.disconnected event to the application. (ER# 183951622)

Found In: 8.0.004.47 Fixed In: 

CCP incorrectly sends the connection.redirected event to the CCXML application instead of the connection.error event when a <redirect> fails because the endpoint does not acknowledge (ACK) the 302 Moved Temporarily response. (ER# 174561923, 173514335)

Found In: 8.0.004.47 Fixed In: 

If an initial bridge (A<->B) is overridden by a CCXML join (join A<-B), and one of the endpoints (B) disconnects in the middle of receiving a re-INVITE in order to establish the new bridge, CCP does not send the conference.unjoined event for the initial bridge (A<->B). However, CCP sends the connection.disconnected (for connection B) and error.conference.join (for join A<-B) correctly. (ER# 174561941)

Found In: 8.0.004.47 Fixed In: 

CCP accepts undeclared variables as the sessionid attribute value of the <createccxml> element without generating the error.semantic event. (ER# 174281990)

Found In: 8.0.004.47 Fixed In: 

CCP does not generate a 400 response when parameter names are repeated in an HTTP request to I/O processors. (ER# 174281929)

Found In: 8.0.004.47 Fixed In: 

If the fetch of the URI specified by the next attribute of <fetch> fails for any reason, the error.fetch event is generated. If the URI has a scheme of http:, the reason property of the event should read: Fetch failed: <error code> <reason phrase>, where <error code> is the HTTP error code and <reason phrase> is the HTTP reason phrase in the response. Currently, the reason phrase is missing. (ER# 174281799)

Found In: 8.0.004.47 Fixed In: 

AAI data passed to the CCP with an incoming Request URI in the SIP INVITE message cannot be accessed at the application level. (ER# 181815975)

Found In: 8.0.004.47 Fixed In:  8.1.001.60

When using Offer-Answer, an incoming connection cannot be joined to two outbound connections if the alerting connection is accepted in a later transition than the joins. (ER# 174430561)

Found In: 8.0.004.47 Fixed In: 

The src attribute is dropped when passing a query string of the original URL of the next element.

For example, in the following <fetch> tag: <fetch next="'next.jsp?t=5'" namelist="a b"/>

Parameters a and b are passed through the resulting query string: next.jsp?a=1&b=2. The parameter t should also be passed through the query string. (ER# 174281980)

Found In: 8.0.004.47 Fixed In: 

CCP allows the use of the <move> tag when the destination session has not been created when using the <createccxml> tag. (ER# 174282000)

Found In: 8.0.004.47 Fixed In: 

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 Technical Support website. The following documentation also contains information about this software. Please consult the Deployment Guide first.

Top of Page