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 | Restricted release; the release documentation is available from the installation package. |
| 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 Feature Server
SIP Feature Server currently has the following limitations:
- In the Telephone User Interface (TUI), User and Group mailboxes can be accessed only with mailbox credentials (mailbox number). DN, agent, and 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.
- Only users with the Group Mailbox Administrator role can use the web application or TUI to upload or change greetings and passwords.
- Calls fail after a user deletes an existing forwarding profile from a user.
- Calling profiles cannot be deleted.
- Implicit SIP MWI notification is not supported.
SIP MWI requires individual SIP subscriptions
To support SIP MWI notification, you must set up SIP subscriptions for individual mailboxes.
Group mailbox users trying to listen to deleted voicemails hear an unclear message
When group mailbox users try to listen to voicemails that another user has deleted, they hear the message "No vocal stream" instead of "This message has been deleted." (SIPVM-1433)
Owner of an Agent-login mailbox is displayed only if login is associated with a user
On the Mailboxes page of the Administrative web application, the Owners field does not display the owner name if the owner type is Agent-login and the login is associated with a user. (SIPVM-1379)
When the network is disabled on the host on which Feature Server is running, Windows may terminate unexpectedly
Windows may terminate unexpectedly if the host on which Feature Server is running is removed from the network by clicking Disable from the Windows Local Area Connection dialog box. (SIPVM-1333)
Workaround
Stop Feature Server before disconnecting the network.
Forwarding on busy not working as expected
The Forward on Busy rule works only when Call Waiting is enabled, so if Call Waiting is disabled, then the dial plan detects that the party is on a call, and either rejects the call or forwards it to voicemail (if voicemail is enabled and if mailboxes are available.) (SIPVM-1323)
Subscriptions accepted from unauthorized sources
SIP Feature Server currently accepts subscriptions from sources other than SIP Proxy, which is the only authorized source. (SIPVM-1317)
Unauthorized users can change the password and recording name for a group mailbox
Users who lack an individual mailbox and belong to an Agent Group can change the password and recording name for a group mailbox in the TUI, even when they are not assigned an administrator role. (SIPVM-1316)
Outbound calls not routing properly
If any of the outbound routing rules is configured with no trunks assigned, routing rules are not picked and the call is not routed properly. (SIPVM-1299)
Workaround
Assign at least one trunk to each outbound routing rule.
Maximum value supported for subscription expiration is one day, rather than the expected one week
The maximum value supported for the subscription expiration is one week, but Feature Server only supports a maximum value of one day. (SIPVM-1291)
Unconditional forwarding taking precedence over Do Not Disturb
When unconditional forwarding is enabled for a user, and the user sets Do Not Disturb from the device, the unconditional forwarding setting is incorrectly taking precedence over the DND setting. (SIPVM-1284)
Application of message priority during retrieval
The message priority selected during a call deposit is not taken into consideration during voicemail retrieval. (SIPVM-1248)
Harmless ExceptionInInitializerError Occurring
At startup, the version of Jython used in SIP Feature Server might throw an ExceptionInInitializerError that has no adverse effect on Feature Server. (SIPVM-1212)
Removing the default Place from the user in a configuration environment does not change the status of the DNs in the browser
Deleting the default Place (changing the value to None) does not change the status of the user in the browser. (SIPVM-1210)
Mailbox removal not synchronizing
In Configuration Manager or Genesys Administrator, if all sections including TServer are deleted from the Annex tab, the removal of a mailbox is not synchronized with the Feature Server (Cassandra) data repository.
Workaround
Do not delete the TServer section. Rename the section to, for example, #TServer. The renaming enables proper synchronization. (SIPVM-1059/SIPVM-1008)
A call is barred when any of the forwarding profiles is disabled through the UI
If any forwarding profile on a DN or a user is disabled (unchecked), and the Voicemail Enabled option is not set to Yes, then calls to this user are barred.
This limitation also applies to the default forwarding settings defined on the Dial Plan Settings configuration page. (SIPVM-1024)
Subscription replication at SIP stack level: recover and/or restore SIP Subscribe dialog on all Feature Servers
When a Feature Server instance shuts down, it cancels all MWI subscriptions that this Feature Server instance is responsible for. To continue receiving MWI notifications, SIP endpoints must re-subscribe. (SIPVM-804)
Stat Server
Stat Server's cluster mode is supported on Windows operating systems only.
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)