SIP Cluster 8.1.1 Issues and Supported Components
Contents
SIP Cluster 8.1.1
This document contains issues, recommendations, and supported components for SIP Cluster version 8.1.1.
SIP Cluster 8.1.1 Issues and Recommendations
This section includes SIP Cluster recommendations applicable to the 8.1.1 release.
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.xxx | Genesys Info Mart 8.1.x |
| Genesys Info Mart Administration Console | 8.1.xxx | Genesys Info Mart Administration Console 8.1.x |
| Genesys Interactive Insights | 8.1.100.31 | Genesys Interactive Insights 8.1.x |
| Interaction Concentrator | 8.1.xxx | Interaction Concentrator 8.1.x |
| Interaction Workspace | 8.1.xxx | Interaction Workspace 8.1.x |
| Reporting and Analytics Aggregates | 8.1.100.31 | Reporting and Analytics Aggregates 8.1.x |
| Solution Control Server | 8.1.xxx.xx | Solution Control Server 8.1.x |
| SIP Proxy | 8.1.1xx.xx | |
| SIP Server | 8.1.1xx.xx | SIP Server 8.1.x |
| SIP Voicemail | 8.1.200.xx | SIP Voicemail 8.1.x |
| Stat Server | 8.1.xxx | Stat Server 8.1.x |
| Universal Routing Server | 8.1.200.18 | Universal Routing Server 8.1.x |
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
Interaction Concentrator
Interaction Workspace
Interaction Workspace SIP Endpoint 8.0 is not supported in a SIP Cluster environment.
Agents cannot call, transfer to, or consult with an agent who is logged into a different data center of the SIP Cluster after finding that agent by using the Team Communicator to search by name. In this scenario, agents must contact agents in other data centers by entering the phone number of the other agent in the Team Communicator or Interaction Workspace must be configured to support a Routing Based procedure for Call, Transfer, Consult, Conference. (ER# 313629698)
The Team Communicator does not display the Presence of agents that are not logged in the same data center of the SIP Cluster. (ER# 313629696)
Interaction Workspace cannot check the availability of a phone number when an agent logs in. (ER# 312589941)
SIP Server
SIP Server may not apply the call forwarding setting correctly. (ER# 312574880)
SIP Server may ignore requests coming from SIP Proxies located at another data center. (ER# 313257731)
If SIP Server is acting as ISCC proxy (cluster-role=iscc-proxy) in a cluster environment, the proxy-name configuration option in the extrouter section must be configured (non-empty), otherwise, SIP Server terminates. (ER# 313196711)
SIP Server may incorrectly process calls if the SIP Voicemail Server/Feature Server is not available. (ER# 309863323)
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).