SIP Cluster 8.1.1 Issues and Supported Components
Contents
This document contains issues, recommendations, and supported components for SIP Cluster version 8.1.1.
SIP Cluster 8.1.1 Supported Components
The supported components table below includes:
- the components that contribute to the SIP Cluster system
- the version number of the latest supported release of each component
- links to the current Release Note for each component
Important: The linked release notes might list later releases of these components, but SIP Cluster 8.1.1 supports only the versions listed in the table below.
| Component Name | Latest Supported Component Version | Release Note |
| Genesys Info Mart | 8.1.201.02 | Genesys Info Mart 8.1.x |
| Genesys Info Mart Administration Console | 8.1.100.01 | Genesys Info Mart Administration Console 8.1.x |
| Genesys Interactive Insights | 8.1.101.05 | Genesys Interactive Insights 8.1.x |
| Interaction Concentrator | 8.1.100.25 | Interaction Concentrator 8.1.x |
| Interaction Workspace | 8.1.401.05? | Interaction Workspace 8.1.x |
| Local Control Agent | 8.1.200.09 | Local Control Agent 8.1.x |
| SIP Proxy | 8.1.100.41 | SIP Proxy 8.1.x |
| SIP Server | 8.1.100.73 | SIP Server 8.1.x |
| SIP Feature Server | 8.1.200.57 | SIP Voicemail 8.1.x |
| Stat Server | 8.1.100.39 | Stat Server 8.1.x Restricted release; the release documentation is available from the installation package or through ftp. |
| Universal Routing Server | 8.1.300.18 | Universal Routing Server 8.1.x |
Features Not Supported
This section includes SIP Cluster component features that are not supported in the 8.1.1 release.
Known Issues in Component Products
This section includes relevant known issues found in component products since the general SIP Cluster 8.1.x release, organized by component. For more information, see the Release Note for the component by clicking its link in the Release Note column above.
Genesys Info Mart
There are no known issues for this product that are specific to SIP Cluster functionality.
Genesys Interactive Insights
There are no known issues for this product that are specific to SIP Cluster functionality.
Interaction Concentrator
THIS IS PLACEHOLDER FOR ER# 320020271 (CL: Icon can receive only custom userdata that are defined in attached data specification file).
THIS IS PLACEHOLDER FOR ER# 320020253 (CL: Icon can receive userdata from IProxy only in EventCallCreated and EventCallDataChanged messages).
THIS IS PLACEHOLDER FOR ER# 319956791 (CL: In G_ROUTE_RESULT the field DESTENDPOINTDN has value 'notKnown' instead of 'null').
THIS IS PLACEHOLDER FOR ER# 319983841 (CL: Error appears in icon log during switchover PR/BK SIP Server.).
THIS IS PLACEHOLDER FOR ER# 313731283 (ICON detects problem with pq file but connects to SIP Server Cluster).
Interaction Workspace
Interaction Workspace SIP Endpoint 8.0 is not supported in a SIP Cluster environment.
SIP Proxy
ER# 322709234 placeholder
SIP Server
In cluster mode, if a supervisor initiates call supervision of an agent using the all calls type, monitors one or more calls for this agent, and then there is an HA switchover, then no more calls will be monitored for this agent unless the supervisor initiates call supervision again. (ER# 323240371)
SIP Voicemail
All SIP Voicemail issues for this pre-release are referenced in ER#313548181.
SIP Voicemail might not immediately complete the import of a large number of users from Configuration Server.
Calling profiles and Forwarding profiles with a specific time/date profile do not take effect until the following day. For example, a profile that you define on Monday will take effect on Tuesday.
The SIP Voicemail Administrator Web application currently has the following limitations:
- User and Group mailboxes can be accessed only by mailbox credentials (mailbox number). DN/agent/user credentials to access mailboxes is not supported.
- Use IP Address or local host name, not FQDN, to access the Web application. FQDNs can cause unexpected logouts.
- Users cannot use the Web page to upload or change greetings, passwords, delete messages, or reset mailboxes to Group mailboxes.
- Calls fail after a user deletes an existing forwarding profile from a user.
- All users have Administrator rights.
- Calling and routing profiles cannot be deleted.
- Mailbox definitions work only for user mailboxes, not for devices.
Any agents in a group can use the phone interface to upload or change greetings, passwords, delete messages, or reset mailboxes to a Group mailbox.
SIPVM checks for the DND state only if any one of the following options is set for a user: Forward on busy, Reject call in call, and Reject call not ready.
When deposit/retrieval is done, a Notify message is generated from where the Subscription was originally placed. When deposit/retrieval is done on a non-subscribed server, the subscribed server does not generate a Notify message.
The SIP Message Waiting Indicator (MWI) is supported only for individual mailboxes. For group mailboxes, only T-Lib MWI is supported. To support SIP MWI notification, the user's mailbox number must be the same as the associated device number or the SIP endpoints must be configured to subscribe to the voicemail box number directly.
During startup, the server is not sending MWI (Resync mwi).
Stat Server
When run in cluster mode, Stat Server instances might fail to start on Linux operating systems, if they are run under a user account that is different from the one previously used. (ER# 319399583)
A Stat Server, operating in cluster mode, might fail to generate the CallConferenceOriginated action on a regular DN in common call-flow scenarios. (ER# 313007498)
A Stat Server cluster reports a routing point or virtual queue as monitored only after having received the very first call-related event for that routing point or virtual queue. In prior releases, Stat Server reported these objects as not monitored. (ER# 312758316)
To operate Stat Server in cluster mode, Genesys recommends the following sizing guidelines:
CPU—1 node/1 core per 1 million open statistics. RAM—1 GB RAM per 1 million open statistics. (ER# 306561286)