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.
Known Issues in Component Products
This section includes relevant known issues found in pre-release versions of component products.
Interaction Concentrator
Note that an Unsupported operation error message appears in the Interaction Concentrator log file when ISCC call scenarios are reported via the ICON connection to the I-Proxy port of SIP Server. This is an informational message only; it does not affect Interaction Concentrator functionality. (ER# 313649461)
Interaction Concentrator stores an incorrect PARENTPARTYID in scenarios in which an inbound call is answered by an agent, who then makes and completes a blind conference call with a second agent. However, the correct PARENTPARTYID is stored in similar scenarios in which the agent makes and completes a non-blind conference call. A blind conference call is one in which the conference is completed before the consultation call is answered. (ER# 313672741)
After a double switchover of the primary SIP Server—from primary mode to backup mode and then returning to primary mode—SIP Server provides the same Agent LoginSessionId that was already used for the previous connection. Interaction Concentrator cannot store an agent login session ID that duplicates the prior one; instead, it generates error messages and no data is stored.
Workaround: After each switchover, restart the SIP Server that is running in backup mode. (ER# 313114856)
In a SIP Cluster environment, the sequence of PartyIDs stored in the G_PARTY table is the following: Ringing party is followed by Dialing party. In a non-Cluster environment, this sequence is reversed (first Dialing party, followed by Ringing party). Note that this reversal might affect Genesys Info Mart data. (ER# 312758237)
In some situations, DSS-related tables in IDB (the G_DSS_<role>_PROVIDER tables) might have an incorrect value in the DS_DBID field when Interaction Concentrator connects to an HA pair of SIP Servers. This might consequently affect Genesys Info Mart data.
Workaround: To store the correct value in this field, before you start Interaction Concentrator, make sure that the SIP Server specified in the Configuration Layer as the primary is running in primary mode and that the SIP Server specified as backup is running in backup mode. (ER# 312724952)
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.
Neither T-Lib nor SIP MWI messages are generated during dynamic and static Agent login.
During startup, the server is not sending MWI (Resync mwi).
Stat Server
A Stat Server node might terminate while it is being stopped from SCI. (ER# 313671997)
Stat Server might generate incorrect values for statistics requested with a sliding time interval and matching the following profile:
Objects=GroupAgents
Subject=AgentStatus or DNStatus
Category=TotalTime
(ER#s 313572759, 313572753)
In some cases, Stat Server fails to generate the CallConferenceJoined retrospective action for agent or agent-group objects. Stat Server does, however, correctly generate this action for regular DN objects. (ER# 313571037)
In some cases, Stat Server might fail to generate the CallTransferTaken retrospective action on Agent and GroupAgents objects. Stat Server does, however, correctly generate this action for regular DN objects.(ER# 313553549)
Stat Server might generate incorrect values for statistics requested matching the following profile:
Objects=GroupAgents
Category=CurrentNumberInTimeRange
(ER# 313362681)
Specifying the addp protocol for an Interaction-Proxy connection is currently not supported. (ER# 313080271)
Stat Server might fail to generate the CallConferenceOriginated action on a regular DN in common call-flow scenarios. (ER# 313007498)
Stat Server reports a mediation DN as being monitored only after Stat Server receives a call-related event for that DN. (ER# 312758316)
When configuring a Stat Server node for a Stat Server cluster, ensure that the Auto-Restart feature is enabled. You can set this option on the Start Info tab of the node's properties in Configuration Manager. (ER# 312425268)
Stat Server might exit if the underlying SIP switch (of the SIP Server listed among Stat Server's connections) is deleted from configuration. (ER# 310005751)
Under unknown circumstances, some Stat Server nodes might terminate upon being stopped by closing their application main windows using the Close button. (ER# 304458481)