Release Note

Genesys SIP Voicemail

8.1.x

Genesys Telecommunications Laboratories, Inc. © 2012

Contents

Introduction

Release Number AIX HP-UX PA HP-UX IPF Linux Solaris Windows
8.1.100.17 [02/29/12] – General       X   X
8.1.000.27 [11/28/11] – General       X    
8.1.000.20 [08/31/11] – General       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.1 releases of Genesys SIP Voicemail.

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. Please contact your technical support representative if you have any questions.


Release Number 8.1.100.17 [02/29/12] – General

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

When updating the versions of GSVM Server, you must copy existing voicemail data from the current server instance to the new server instance. For details, see the SIP Voicemail Migration Procedure.

Genesys recommends that you use SIP Server version 8.1.000.61 or later for the Voicemail SIP Server instance in your deployment.

There are no restrictions for this release. This release contains the following new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


For HA deployments in Linux environments, the LCA now automatically starts as required for a successful Solution HA switchover. Previously for run levels other than 3, a manual restart of the LCA was required. (ER# 295400524)


The GSVM Server is now able to resolve the hostname in both the premise SIP Server and the Voice over IP Service voicemail DN. Previously, you had to set both values to a consistent setting, IP address or hostname, or MWI did not work. (ER# 286859243)


Users are now correctly locked out of their account after three failed password attempts. This applies to entries made from either the GUI or the TUI. (ER# 286859237)


Top of Page


Release Number 8.1.000.27 [11/28/11] – General

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

There are no restrictions for this release. This release contains the following new features or functionality.

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page


Release Number 8.1.000.20 [08/31/11] – General

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

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of Genesys SIP Voicemail.

Corrections and Modifications

There are no corrections or modifications in the initial 8.1 release.

Top of Page


Known Issues and Recommendations

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


For HA deployments on Windows, a java exception sometimes occurs in the following scenario:

  1. All the components are installed using the Complete Install tool.
  2. GSVM Server is subsequently upgraded using manual IP installation.
  3. Primary GSVM Server is started first, then backup server is started.
  4. After a few minutes, a Java exception occurs in the console of the backup GSVM Server instance.

(ER# 295610751)

Found In: 8.1.100.17 Fixed In: 

Solution Control Interface (SCI) is unable to start the GSVM Server after a machine reboot. To solve this issue, Genesys recommends the following workaround:

Workaround

  1. Stop the LCA process.
  2. Start LCA manually.
  3. Start GSVM Server from SCI.

(ER# 295563431)

Found In: 8.1.100.17 Fixed In: 

The GSVM Server is sometimes unable to start when it is installed in standalone (non-HA) mode. If this problem occurs, Genesys recommends the following workaround.

Workaround
Open the launcher.xml file and set execmode to primary. (ER# 295460979)

Found In: 8.1.100.17 Fixed In: 

Re-synchronization of Message Waiting Indicator (MWI) might not work if the backup Voicemail Server has been restarted in primary mode, and the primary server is still unavailable. This problem can occur in the following scenario:

  1. The GSVM Server on the backup host (GSVM Server-B) is running in primary mode (after a solution switchover from primary to backup host).
  2. GSVM Server-B sends a Request register address 9999 message to SIP Server on the backup host (SIP Server-B).
  3. During message deposit, retrieval, and deletion, mailboxes successfully receive TPrivateService requests.
  4. However, while the GSVM Sever is being restarted, or during machine reboot, configured mailboxes do not receive TPrivateServeice messages. This includes both agent and DN mailboxes.

(ER# 295455471)

Found In: 8.1.100.17 Fixed In: 

In HA deployments, Solution Control Server (SCS) is sometimes unable to execute scripts in response to a 4563 log event from SIP Server or GSVM Server. This problem can occur when the script is linked to the third-party application that is used to enable or disable the Virtual IP. (ER# 295420691)

Found In: 8.1.100.17 Fixed In: 

In High Availability (HA) deployments on Windows, the GSVM Server port (8080) sometimes bonds incorrectly to the physical IP address instead of the Virtual IP address when it is started as a Windows service. Currently, Genesys instructs you to set -vms_host=0.0.0.0 in the Command Line Arguments to prevent this bonding issue. However, in some cases the service path to the executable is set to the hostname during installation, causing the bonding problem to occur regardless of the Command Line Argument. In this case, use the following workaround to fix the issue.

Workaround
Change the service path in the Windows registry, by using the following command:

sc config SIPVoiceMSrv64 binpath= "c:\Program Files\GCTI\VM\SIPVoicemailServer_811\launcher.exe -host dev-tigrisV3 -port 2020 -app VM-SIPVoicemailServer -service SIPVoiceMSrv64 -vms_host 0.0.0.0

(ER# 295420683)

Found In: 8.1.100.17 Fixed In: 

For HA deployments in Linux environments, the LCA will only automatically start if the run level is set to 3. This is required for a successful Solution HA switchover. For run levels other than 3, a manual restart of the LCA is required. (ER# 295400524)

Found In: 8.1.100.17 Fixed In: 8.1.100.18-install

GSVM Server in Linux deployments can incorrectly send a constant value (for example, 0/0) in the NOTIFY message. This problem occurs when trying to re-synchronize MWI, as well as during deposit, retrieval, and delete operations.

Workaround
Genesys recommends the following workaround to resolve this issue:

  1. Remove the files from the storage/data folder.
  2. Start both primary and backup GSVM Servers.

(ER# 295400521)

Found In: 8.1.100.17 Fixed In: 

For HA deployments in Windows environments, a language pack issue sometimes prevents the GSVM Server from restarting automatically after a reboot. If this problem occurs, Genesys recommends the following workaround.

Workaround

  1. In Windows Services, set the service property for the GSVM Server to "Log on as administrator".
  2. Restart the service.
(ER# 295400511)

Found In: 8.1.100.17 Fixed In: 

A user does not get locked out from their account after three failed password attempts, as required. This issue affects password entry attempts on either the GUI or the TUI. (ER# 286859237)

Found In: 8.1.000.20 Fixed In: 8.1.100.17

The user is unable to set greetings or change options in their personal menu when their mailbox is full. (ER# 286859240)

Found In: 8.1.000.20 Fixed In: 

Currently, you must set both the sip-address in the SIP Server Application and the contact in the Voice over IP Service DN to a consistent value: IP address or hostname. If the values are inconsistent (IP address in one, hostname in the other), then the Message Waiting Indicator (MWI) will not work. (ER# 286859243)

Found In: 8.1.000.20 Fixed In: 8.1.100.17

You can use only positive integers to designate a mailbox. No letters or symbols; numbers only. (ER# 281038087)

Found In:  8.1.000.20 Fixed In: 

Localization is available only for the Telephony User Interface (TUI). Although language settings can be changed using the Web User Interface (WUI), the WUI itself is available only in English. (ER# 281037969)

Found In:  8.1.000.20 Fixed In: 

When a caller finishes leaving a message, Genesys SIP Voicemail gives the option to confirm, replay, or erase and re-record (by pressing 1, 2, or 3). If the caller gives an incorrect answer three times, the message is deleted and the caller is disconnected. (ER# 281037966)

Found In:  8.1.000.20 Fixed In: 

When you delete a mailbox using the Genesys SIP Voicemail User Interface, you must also delete it manually from the configuration environment, to prevent the mailbox from reappearing after a SIP Voicemail Server restart. Use Genesys Administrator or Configuration Manager. (ER# 281037961)

Found In:  8.1.000.20 Fixed In: 

Playback does not distinguish between messages with normal priority and high priority. (ER# 276907573)

Found In:  8.1.000.20 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 product.


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 Administration Guide first.

Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, 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 Technical Support 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