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.genesys.com for more details.
This release note applies to all 8.1 releases of Stat Server.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see the Read Me. Please contact your Genesys Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server no longer leaks memory upon receiving the EventPartyChanged
TEvent for a regular DN. Previously in a such scenario, Stat Server leaked 24 bytes of memory.
(SS-7094)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release introduces the following new features or functionality:
Client:4
instead of Client:5
.
This release includes the following correction and modification:
Stat Server no longer terminates unexpectedly in some scenarios when the EventLinkConnected
TEvent comes shortly after multiple T-Server switchovers. (SS-6915)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Stat Server no longer generates the Integrity violation detected...
message in the following VQ transfer scenario:
EventQueued
Connid=CONNID1
CallType=Inbound
Extensions
SIGNATURE=router
VERSION=(>= 7.5.000.00)
EventQueued
Connid=CONNID2
CallType=Inbound
Extensions
SIGNATURE=router
VERSION=(>= 7.5.000.00)
EventPartyChanged
Connid=CONNID2
PreviousConnid=CONNID1
CallType=Inbound
Extensions
SIGNATURE=router
VERSION=(>= 7.5.000.00)
EventDiverted
Connid=CONNID2
CallType=Inbound
Extensions
SIGNATURE=router
VERSION=(>= 7.5.000.00)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server no longer terminates unexpectedly in scenarios when it internally maintains two agent login sessions, associated with the same name. Such scenarios might occur when Stat Server is disconnected from Configuration Server, and cannot subsequently restore the session, so that configuration updates that were made during the disconnection are lost. (SS-6800)
Stat Server no longer intermittently terminates unexpectedly in the following scenario:
X
, associated with that agent-login. This might happen, for example, when the permissions are changed to No Access
on the agent-login object. X1, ..., XN
log in to DNs. X
is removed from the configuration. X1, ..., XN
.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
The call no longer gets stuck on a DN when the EventPartyChanged
event with Connid!=PreviousConnid
and CallState=Transferred
comes after the EventDialing
event. (SS-6547)
Stat Server no longer terminates unexpectedly in the rare case when the Deleting capacity rule
message appears in a Stat Server log without a prior Capacity rule manually deleted
message. (SS-6539)
Stat Server no longer terminates unexpectedly on Solaris and AIX in the following scenarios:
A
by the client C
(but not any other clients).A
is renamed to B
.B
is removed from the configuration.C
is disconnected from Stat Server.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction and modification:
Stat Server no longer terminates unexpectedly in some scenarios with updating or deleting a mediation DN during an active call. Previously, in some cases (for example, a disconnect of URS or changing DN alias after applying a strategy), Stat Server could terminate unexpectedly if a mediation DN is deleted during an active call. (SS-6403)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This section describes new features that were introduced in this release of Stat Server.
position-extension-linked
can be configured for any switch on the switch Annex in the statserver
section.
If this option is taken into account and is set to yes
(or is yes
by default), then the corresponding switch is treated as the Meridian-like switch (position and extension DNs on the same place are considered linked if no more than one position/extension pair is configured on a place and agent is logged into a position DN only).
Please note, that for some switches this new option is ignored (see table below).
Switch type | Default value | Comments |
---|---|---|
NortelMeridian | n/a | option is ignored |
NortelMeridianCallCenter | n/a | option is ignored |
NortelCommunicationServer2000/2100 | n/a | option is ignored |
CiscoCallManager | no |
|
IntecomIBX80 | yes |
|
EricssonMD110 | yes |
|
AastraMX1 | yes |
|
NEC | no |
NEC switch is treated as the Meridian-like switch if any (or both) of the following options are set to true :nec-position-extension-linked , configured on the Stat Server application,position-extension-linked , configured on the switch Annex. |
NECSV7000 | no |
NECSV7000 switch is treated as the Meridian-like switch if any (or both) of the following options are set to true :nec-position-extension-linked , configured on the Stat Server application,position-extension-linked , configured on the switch Annex. |
All other types | no |
Note 1: The Stat Server option position-extension-linked
is used completely independently.
Note 2: An attempt to log in an agent on an extension DN for the Meridian-like switch causes incorrect Stat Server behavior due to pending NotReady
state of this extension.
This release includes the following correction and modification:
Configurable association between position and extension DNs, which is now supported on the switch level, fixes the problem for the Cisco Call Manager switch when customers login agents to extension DN only. If the position-extension-linked
option is set to no
on the switch Annex by default or configured, Stat Server considers switch as non Meridian-like switch and propagates to virtual queue actions that are used in the ExpectedWaitTime
calculation. Previously, starting with release 8.1.200.46 Stat Server did not link to virtual queue the agent, logged into an extension DN on the Cisco Call Manager switch, considered as Meridian-like switch. (SS-6193)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
For the Meridian-like switch, Stat Server now correctly reports a place as non-routable, when it contains only an extension DN without an associated position DN and there is no agent logged in and ready on this extension DN. (SS-6172, SS-6171)
Stat Server now properly reports agent status for the Cisco Unified Communications Manager switch. Previously, in Stat Server release 8.1.200.46 or higher, an agent was non-routable while logged in and ready on a position DN. (SS-6168)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server now does not decrease the capacity current_number
when the Network Attended Transfer/Conference is completed with the EventNetworkCallStatus (NetworkCallState = 'NetworkCallStateTransferred')
event. Previously in such cases, Stat Server prematurely ended the CallInbound
action and reduced capacity current_number
by 1
leading to a negative current_number
later on receiving EventReleased
for original inbound call. (SS-6145)
Stat Server now correctly handles the following outbound scenario:
ASM_Engaged(CONNID1)
action coexists on a DN with the CallOnHold(CONNID1)
action.EventPartyChanged(CONNID1,CONNID2)
event arrives, the ASM_Engaged(CONNID1)
action ends, and the ASM_Outbound(CONNID2)
action starts.
CallOnHold(CONNID1)
action and starts the CallOnHold(CONNID2)
action. Previously, Stat Server failed to do so, and as a result, the CallOnHold(CONNID1)
action was stuck on a DN. (SS-6142)
Stat Server no longer considers the following switches to be Meridian-like:
Stat Server now correctly computes the following statistic:
Category=CurrentNumber
Objects=GroupAgents
MainMask=NotReadyForNextCall
(or contains NotReadyForNextCall
)Subject=AgentStatus
on
at the Agent's extension.0
. Previously, in this scenario, Stat Server incorrectly returned -1
for the statistic above.
(SS-6111)
The following switches are now treated as Meridian-like switches:
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server no longer reports the DN status as NotMonitored
after the following sequence of events:
EventDNOutOfService
event occurs.EventAbandoned
event.EventDNBackInService
event occurs.
Stat Server no longer terminates unexpectedly when an agent logs into a place without any medias. Previously, in release 8.1.200.38 or higher, Stat Server could terminate unexpectedly in the following scenarios:
The Cisco Call Manager switch is treated as a Meridian-like switch. As a result, the position and the extension DN assigned to a place are considered to be linked, and both DNs are associated with an agent who is logged in to the position. (SS-6089)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server now properly increments the following statistic when it is requested on a virtual agent group and when the script includes the LoggedIn()
expression:
Category=CurrentNumber Object=GroupAgents MainMask=NotReadyForNextCall Subject=AgentStatusStat Server release 8.1.200.41 decrements this statistic to a negative value in the following scenario:
NotReadyForNextCall
.WaitForNextCall
.Stat Server now correctly applies capacity rules in scenarios where a tenant has a capacity rule assigned, and the same capacity rule is assigned to an agent or a place, and this capacity rule is changed on the tenant. Previously in such scenarios, when a tenant capacity rule was changed from X to Y, Stat Server incorrectly applied the capacity rule Y to agents or places that were explicitly assigned the capacity rule X. (SS-6074)
Stat Server now correctly increments the following statistic:
Category=CurrentNumber Objects=GroupAgents MainMask=WaitForNextCall Subject=AgentStatusPreviously, for the
EventRegistered
, EventAddressInfo
, and EventAgentLogin
TEvents Stat Server could incorrectly increment this statistic on a virtual agent group with the LoggedIn()
expression in the script.
(SS-6067)
Stat Server now correctly processes Data Stream packets from Interaction Server. Previously, Stat Server running on 64-bit Windows platform could terminate unexpectedly while trying to print string messages. (SS-6051)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server no longer generates the OffHook
action on the DN upon receiving the EventAddressInfo
with status=1
in Extensions
, if there exist call parties (ps-
keys in Extensions
), and all of them are in the Alerting
(Ringing
) state. Previously, Stat Server generated the OffHook
action on this DN regardless of call parties states, which lead to the OffHook
action getting stuck in scenarios when ringing call was further abandoned or released without answering. (SS-6023)
Stat Server now correctly calculates the DN status when the EventDNOutOfService
is received on a DN, followed by the EventDNBackInService
. Previously, Stat Server set the DN status to NotMonitored
in such scenarios. (SS-6018)
Stat Server now correctly calculates CurrentMin/MaxTime
statistics with the MainMask
set to NotReadyForNextCall
in scenarios associated with the agent logout on a DN. (SS-5999)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server now recognizes the NEC SV7000
switch as a Meridian-like switch. To use the Meridian model, set the nec-position-extension-linked
option to yes
. (SS-5998)
Stat Server now correctly processes the request to open the CurrentContinuousTime
statistic for an agent with the PlaceStatus
subject. Previously, Stat Server could return the "Incorrect 'Subject' Parameter (3)" error to a client requesting this statistic. (SS-5997)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release introduces the following new features or functionality:
Support for the Windows 2012 64-bit.
This release includes the following corrections and modifications:
Stat Server now adjusts the Subject
parameter based on the Agent
or Place
object type provided in dynamic requests ("old API requests"). Previously, Stat Server adjusted the subject only for new API requests, which use the name of the stat type definition in the Stat Server application object. (SS-5982)
Stat Server improves the loading of statistics from the backup file. Previously, Stat Server could create duplicate requests when a statistic with specific options is loaded from the backup file. (SS-5976)
Stat Server no longer terminates unexpectedly under the following circumstances:
DNAction
. Agent
. CurrentCustomValue
.
Stat Server now correctly updates the CurrentState
statistic in the TimeBasedNotification
mode. In earlier 8.1.200.3x releases, Stat Server could fail to provide updates for the CurrentState
statistic in the TimeBasedNotification
mode.
(SS-5957)
The following cases no longer cause Stat Server to terminate unexpectedly while handling event_party_removed
:
The switch type CFGNortelDMS100=4 ("NortelCommunicationServer2000/2100" ) will be treated as the switch type CFGNortelMeridian=1("NortelMeridian"). As a result, position and extension DNs on the same place will be considered linked, and both DNs will be associated with an agent which is logged in to the position. (SS-5927)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server now correctly handles the large Interaction Server protocol message that contains Unicode key-value pairs (KVPs). Previously in this scenario, Stat Server could terminate unexpectedly. (EST-944)
Stat Server now correctly handles a change in capacity vector. Previously, after a change in the capacity vector for one media type, Stat Server also incorrectly updated the timestamp on capacity vectors for other media types. This negatively impacted URS, which uses those timestamps to select the most idle agent for any media. (SS-5950)
Changing the reason code for media no longer affects the reasons on unrelated actions. (SS-5945)
Stat Server now correctly provides the Agent
state in EventCurrentAgentStatus
messages that are distributed to Interaction Server. Previously, in EventCurrentAgentStatus
messages, Stat Server provided the Place
state. In general, Agent
and Place
states are different (for example when the associated capacity rules are different).
(SS-5934)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server now correctly retains ADDP settings on restored connections to Configuration Server after Configuration Server failover. Previously, in some Configuration Server failover scenarios, ADDP was not enabled on the restored connection. (SS-5917)
When an agent logs in and then logs out after a previous logout, Stat Server now correctly creates a new record in the STATUS
table corresponding to the latest agent logout. Previously, in some cases, Stat Server could update the record associated with the previous agent logout.
(SS-5913)
Stat Server now correctly handles the following scenario:
auto-backup-interval
configuration option expired, Stat Server terminated unexpectedly.
(SS-5820)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server now correctly sets the time-stamp in the value of statistic
[CurrentStateReasons] Category=CurrentStateReasons MainMask=* Objects=Agent,GroupAgents ReasonStartOverridesStatusStart=yes Subject=DNActionto the current time when a reason changes, but the status of the DN remains unchanged. (SS-5889)
Stat Server no longer terminates unexpectedly while trying to maintain internal information necessary for correct computation of DCID
statistics.
(SS-5868)
Stat Server now correctly calculates DN status in scenarios associated with the implicit network-attended transfer completion when the EventNetworkCallStatus
TEvent is not generated.
(SS-5859)
Stat Server no longer sets the LoginID
field to LoggedOut
in the CurrentState
statistic when an agent is logged into DN/media. Previously, Stat Server sometimes did this in scenarios associated with agent login/logout into/from multiple DNs/medias. This issue was visible on the Extended Status
tab in CCPulse+.
(SS-5858)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server now correctly updates statistics in the following scenario:
NotReady
and current Ready
state.
(SS-5814)
Stat Server now correctly updates statistics in the following scenario:
CurrentNumber
and CurrentTime
statistics with the MainMask
set to WaitForNextCall
or the MainMask
set to *
.
(SS-5807, SS-5783)
Stat Server no longer terminates unexpectedly when Places or Agents that are logged in to handle multimedia interactions are deleted from the configuration. Previously, in such scenarios an unexpected termination might occur. (SS-5780)
LoggedIn
action for media channels is now generated only when the actual login is confirmed by event_media_added
. Previously, such an action could be created implicitly after an agent received or created an interaction that did not require a login on the specific media. (SS-5778)
Stat Server now sends the correct, non-empty, PlaceID
attribute in the agent CurrentState
when the agent is logged into multimedia only. Previously, in such scenarios, Stat Server failed to provide the PlaceID.
(SS-5774)
Stat Server now correctly generates the CallInboundStarted
action upon receiving EventPartyChanged
on a regular DN when the ConnID
attribute is equal to the PreviousConnID,
and the CallType
=CallInbound.
(SS-5771)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Stat Server.
This release includes the following corrections and modifications:
Stat Server now connects to Interaction Server when adding connections to the configuration. Previously, in some cases, Stat Server version 8.1.200.27 failed to connect to Interaction Server, if the connection was added dynamically. (SS-5765)
Stat Server now properly reports the LoggedOut
agent status in blended environments including voice and multimedia interactions. Previously, in some scenarios involving a specific agent logout sequence with voice DN going out of service, Stat Server could report the agent status as NotMonitored
.
(SS-5762)
Stat Server now correctly calculates the RelativeTimePercentage
statistic with Subject=AgentStatus
. Previously, in some scenarios, Stat Server would incorrectly count the RelativeTimePercentage
statistic after the EventRegistered
or EventAddressInfo
events.
(SS-5756)
Stat Server now correctly calculates the MaxTime
status-based statistics for Agent
,
Place
, GroupAgents
, and GroupPlaces
objects when a sliding time profile
has been applied.
(SS-411)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server no longer has improper message "Source time-stamps will not be used: incompatible parameters" in its log when reading/writing statistics from/to the backup file. This message does not affect the functionality of Stat Server, but previously it appeared in Stat Server 8.1.200.24 log. (SS-5750)
REQ_ID
in the EventStatClosed
response from the CloseStat
request. Stat Server 8.1.200.24 used the value from the ASSOC_REQ_ID
field in the CloseStat
request for the REQ_ID
in the EventStatClosed
response.
(SS-5748)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Stat Server.
Support for Java Development Kit (JDK) version 1.7.
Support for the Red Hat Enterprise Linux 6 64-bit native.
Support for MCR and OCC Extensions running on Linux 6 64-bit.
Support for Windows 64-bit native.
An improved Agent-Place model.
A new statistical category TotalContinuousNumber
.
Note: Stat Server supports a restricted release of SIP Cluster. For information on Genesys SIP Cluster technology, contact your Genesys representative.
This release includes the following corrections and modifications:
As of Stat Server release 8.1.200.24, for the debug-level
configuration option, the Client:6
value replaces the ClientX
value.
Stat Server no longer terminates unexpectedly in some scenarios with dynamic Database Access Point (DAP) manipulations in configuration, when multiple DAPs are associated with the same DB Server. (SS-5734)
Stat Server no longer terminates unexpectedly when the CurrentCustomValue
statistic is requested on an agent or agent group with the Subject
set to AgentStatus
(which is an unsupported value) and the MainMask
set to *
.
(SS-5731)
Stat Server now correctly sends EventCurrentAgentStatus
to Interaction Server when a multimedia channel is removed. (SS-5719)
Stat Server now correctly checks the value ranges for the reg-delay
and reg-dns-chunk-delay
configuration options and correctly sets the option to their default values, if the provided values are not valid.
(SS-5709, SS-5708)
Stat Server now correctly checks the value range for the reconnect-timeout
option. Previously, setting this option to a large value could cause the Stat Server application to loop indefinitely.
(SS-5707)
Stat Server now correctly detects Java exceptions and unloads the MCR Extension. Previously, in some cases, Stat Server could terminate unexpectedly. (SS-5690)
Stat Server now correctly continues to update long-running statuses in the STATUS
table after the status-table
option is changed to off
and is then set back to on
.
(SS-5658)
For the MinTime
statistical category with the Subject
set to AgentStatus
or PlaceStatus
, the status durations are now correctly calculated from
start of the status or the moment when the statistic opens, whichever is later.
(SS-5646)
Stat Server now correctly calculates MinCustomValue
statistics on intervals in cases when the sequence of custom formula values that are evaluated for actions listed in MainMask
contains zero(s).
(SS-5629)
Stat Server now correctly updates the capacity on the agent or place in situations when a capacity rule is removed from the Tenant
, and this capacity rule was previously used for that agent or place.
(SS-5603)
Stat Server no longer attempts to register for a DN that is removed from the configuration. Previously, in some scenarios involving a removal of DNs, Stat Server could terminate unexpectedly. (SS-5511, SS-5259)
Stat Server no longer terminates unexpectedly when a new DN with a logged-in agent is added into configuration. (SS-5491)
An agent can now use different desktop applications to separately log into multimedia and voice DNs. Previously in this scenario, the agent would have to log into multimedia again if the notification about the voice login came last. (SS-5122)
Stat Server now correctly logs the ConnID
attribute for a call that is deleted as stuck in a virtual queue as a result of handling of an EventPartyChanged
TEvent.
(SS-4949)
Stat Server now correctly handles the renaming of filters in the Transactions
folder.
(SS-4932)
Stat Server now properly adds the CallReleased
and ACWCompleted
actions to virtual queue objects if the ThirdPartyDN
attribute of
EventDiverted
TEvents points to a known external routing point.
(SS-4898)
Stat Server now correctly writes the NotReadyForNextCall
place status into the database in cases when the agent logs out and then logs in again.
(SS-632)
After reconnecting to Configuration Server Proxy (CS Proxy), Stat Server no longer tries to reconnect to T-Server or T-Proxy if that connection was removed while Stat Server was disconnected from CS Proxy. (SS-291)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server on 64-bit AIX platforms no longer terminates if memory usage exceeds 3.25 GB. (SS-5688)
Stat Server no longer terminates unexpectedly on acceptance of the OpenPackageStat
request. (SS-5673; SS-5663)
Stat Server now correctly restores the Extension DN status to WaitForNextCall
when receiving an EventAddressInfo
TEvent with the dnd
Extensions
attribute set to 0
(zero).
(SS-5671)
Stat Server now correctly emulates agent logout in certain T-Server switchover scenarios, when an EventRegistered
TEvent has the AgentStatus
key with either a missing or 0 (zero) value in the Extensions
attribute.
(SS-5654)
For some network-attended transfer and conference scenarios, Stat Server now correctly clears the CallOnHold
durable action on a DN.
(SS-5515)
Stat Server now correctly generates Logout
records in the LOGIN
database table for multimedia scenarios, when EventMediaAdded
and EventMediaRemoved
events are not present in the interaction flow.
(SS-5063)
Stat Server now ends CallConferenceOriginated
action on the EventPartyChanged
TEvent using PreviousConnID
attribute in order to avoid stuck action on a DN after the call is released.
(SS-5062)
For CallConferenceOriginated
actions that are triggered by the EventPartyChanged
TEvent with the CallState
attribute set to Conferenced
, all attributes (ThisQueue, DNIS, and others) are now taken from this TEvent.
(SS-4446)
Stat Server now properly connects to the primary SIP Server after SIP Server switchover. Previously, in some scenarios, Stat Server did not try to connect to the primary SIP Server. (SS-685)
Stat Server now correctly processes AttributePreviousConnID
on the EventPartyChanged
TEvent in situations when it is different from the AttributeTransferConnID
. This prevents stuck calls on a virtual queue in some multi-site scenarios.
(SS-183)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Stat Server no longer terminates unexpectedly when multiple Database Access Points, which point to the same DB Server, are changed to point to a different DB Server or to no DB Server. (SS-5589; SS-660)
Stat Server no longer terminates unexpectedly when different requests come with the same REQ_ID
. Stat Server now refuses duplicates and sends the following error message to the client: "Duplicate 'REQ_ID
' Parameter."
(SS-5581; SS-5532)
Stat Server now reads java-config
options from its own application object only. In previous releases, Stat Server could possibly inherit option values from Interaction Server.
(SS-5170)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
In a scenario with supervisor intrusion, Stat Server no longer increments the number of answered interactions on a virtual queue when receiving an event_party_added
notification that indicates the supervisor intrusion into the existing interaction, regardless of the visibility mode that the supervisor specifies. Previously, Stat Server may have incremented the number of answered interactions when the supervisor joined, although the interaction was already answered and was being handled by an agent.
(SS-5535)
Stat Server no longer terminates unexpectedly when formatting unusually large messages from Interaction Server prior to printing them in the Stat Server log. Previously, a problem occurred when the verbose
log option was set to all
, and when the size of Interaction Server events exceeded 16 KB.
(SS-5494)
Handling of event_agent_place_status
has been corrected for situations where the event is associated with an agent who is logged into one or more media channels and who has one or more active interactions. Previously, Stat Server could write incorrect names for the media channels in the log and potentially terminate during subsequent handling of the interaction(s) reported in the event_agent_place_status
event. (SS-5523; SS-5519)
Stat Server now correctly updates statistics of the ExpectedWaitTime2
category in the scenarios in which agent groups' membership changes dynamically. Previously, the ExpectedWaitTime2
could become incorrect when an agent was added to, or removed from, an agent group associated with one or more virtual queues. (SS-5576; SS-5529)
Stat Server now correctly calculates statistics of the ExpectedWaitTime2
category in the scenarios in which a given mediation DN has only the missed calls and has no released calls.
(SS-5575)
Stat Server now correctly reports the DN and place status in case when the agent relogin to another place without an explicit logout from the current place. (SS-136)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release includes no new features or functionality.
This release includes the following corrections and modifications.
For some network-attended transfer and conference scenarios, Stat Server hides the real Inbound
action, while exposing CallConsult
and other actions in the log. Stat Server now correctly terminates the hidden action before executing the call-release handling procedure, to ensure correct status and capacity calculations after the call. Previously, Stat Server might have reported an incorrect status after the call was released.
(ER# 324523128, SS-684)
Stat Server does not support batch requests from clients. If legacy clients attempt to use a batch request, Stat Server ignores the request and now logs the following message in the Stat Server log: "Unsupported batch request from %d client!(ignored)". (ER# 324251613, SS-677)
Package clients can again connect to Stat Server and request statistics. Releases 8.1.000.12 through 8.1.000.39 did not support Package clients. However, Genesys strongly advises customers to rework any custom applications to use the latest Genesys PSDK. Stat Server will not support the Package API in releases later than 8.1.0. (ER# 322782888, SS-649)
As described in the Stat Server User's Guide, Stat Server always reports the status of disabled agents as Monitored
. The actual status is hidden, although it is used in calculations. Stat Server now correctly calculates statistics for disabled agents on restart. Previously, when Stat Server restarted, the hidden status was not correctly considered for statistics. For example, disabled agents who were logged out caused incorrect increments in the TotalTime
statistic.
(ER# 291527965, SS-5293)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release introduces the following new features or functionality:
Support for the Red Hat Enterprise Linux 6 64-bit native.
This release includes the following corrections and modifications.
Stat Server now properly handles the EventAgentNotReady
TEvent with AgentWorkMode=3
(AfterCallWork
) received when this agent is already in AfterCallWork
. Previously, Stat Server would report incorrect AfterCallWork
time despite agent status changes.
(ER# 323707225, SS-669)
If the EventEstablished
TEvent has different values in the FirstTransferConnID
and ConnID
attributes, and it is received before the EventDiverted
TEvent, Stat Server now correctly increments CallReleased
statistics in multisite transfer scenarios.
(ER# 321089784, SS-601)
Stat Server now correctly handles the EventAttachedDataChanged
TEvent, preserving information from the ThisQueue
attribute. As a result, Stat Server now correctly calculates filtered AfterCallWork
statistics. Previously in Stat Server releases 8.1.000.35–8.1.000.37, the EventAttachedDataChanged
TEvent caused cleanup of an attribute ThisQueue
, which resulted in incorrect filtered AfterCallWork
statistics.
(ER# 320478661, SS-587)
A zero value for the auto-backup-interval
option no longer prevents Stat Server from starting and running the procedure to remove old statistics. Previously, the procedure did not start if the value of auto-backup-interval
was 0
(zero).
(ER# 291904402, SS-5294)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release includes no new features or functionality.
This release includes the following corrections and modifications.
Stat Server now correctly processes EventPartyChanged
and EventPartyDeleted
TEvents in call-observing scenarios. Previously, Stat Server might hang if a call with an observer was
transferred or exit if the external party was released from a call with an observer.
(ER#s 319616322, 320151526)
Stat Server now correctly expires log files based on the number of days that have elapsed instead of based on the number of log files created. In previous releases, when the number of log files exceeded 2000, Stat Server stopped expiring the logs regardless of when they were created. (ER# 318914541)
Stat Server now logs the correct host name when Stat Server connects to the backup DB server. In previous releases, Stat Server continued to log the host name of the primary DB Server. (ER# 277212657)
Stat Server now correctly calculates TotalTime
statistics that are requested with
InteractionStoppedInbound
and/or InteractionStoppedOutbound
main masks. In previous releases, Stat Server always returned 0
(zero).
(ER# 256576982)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release includes no new features or functionality.
This release includes the following corrections and modifications.
The _we_event_current_agent_status
log message no longer attempts to provide
current agent status as it did in the previous release due to the fact that Stat Server completes
computing agent status only after this message is logged. (ER# 318969289)
Stat Server now correctly computes resource capacity upon restart. In previous releases, under some circumstances, Stat Server improperly recalculated agent capacity upon DN reregistration with an agent already logged onto it. (ER# 318590859)
Stat Server now correctly computes resource capacity when the
capacity-treat-acw-as-interaction
configuration option is set to true
.
Genesys' optimization of event distribution in previous releases led to Stat Server's mishandling
of capacity recalculation. (ER# 317828122)
The CallAnswered
action now properly inherits data and attributes of
EventEstablished
TEvents, which now enables correct filter evaluations based on
the ThisQueue
attribute. (ER# 317298019)
Stat Server use is no longer limited to 64-bit executables for platforms other than Microsoft
Windows in order to avoid an issue that was discovered for 32-bit executables and involved the proper
calculation of TotalTime
status-based statistics requested with DCID.
(ER#s 314672761, 311654910)
In rare cases where Stat Server fails to restore a prior connection to Configuration Server and then tries to create a new connection to the Configuration Server primary/backup pair, Stat Server now tries to create a new connection to Configuration Server it was connecting to first, before switching to the primary/backup pair. (ER# 313648378)
Stat Server now properly processes the attributes of the EventReleased
TEvent,
including consideration of an interaction's call type which provides expected handling
information. In previous releases, Stat Server did not consider the CallType
(or
UserData
) attribute for generation of the CallAbandonedFromDialingOutbound
action. (ER# 297456506)
Stat Server now uses two ways to interpret filter results:
MediaType
attribute (such as MediaType=chat
),
the assumption is that this filter is static and will not likely change. So, the statistic will use
the actual duration of the action or status. This is new behavior.UserData
attribute (such as
PairExists("MediaType","chat"))
, the assumption is that this filter is dynamic and
therefore can be changed any time. So, Stat Server treats the filter result as unknown and starts the
statistic at 0
.
(ER# 294788704)
In blended environments, Stat Server now sends fewer updates to Interaction Server regarding
current agent status when the suppress-agent-status-updates-for-ixn-server
configuration
option is set to no
. In previous releases, under some circumstances Stat Server
transmitted multiple updates. (ER# 289715219)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release includes no new features or functionality.
This release includes the following corrections and modifications.
Stat Server logic for handling scenarios that involve multiple call observers has been improved in
this release. In particular, call-related event processing now correctly recognizes multiple
CallObserved
actions whereas in previous releases, call-related event processing did not.
(ER# 288465225)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release includes no new features or functionality.
This release includes the following corrections and modifications.
Upon startup, Stat Server now correctly disconnects from DB Server when Stat Server receives a switch-to-backup message from LCA. (ER# 309704617)
Stat Server now accepts but ignores unsupported client batch requests. In previous releases, Stat Server terminated unexpectedly under this condition. (ER# 303879834)
Stat Server now updates the capacity vector upon the end of a call in network-attended
transfer and conference scenarios. In prior releases, the manner in which Stat Server
handled the CallConsult
action prevented capacity recalculation.
(ER# 302930850)
Stat Server's handling of filtered CallCleared
statistics has been corrected to now process
attached data. In previous releases, Stat Server failed to process data that was attached to the
EventDiverted
T-Event causing its miscalculation of CallCleared
statistics whenever
they were filtered. (ER# 298185351)
Stat Server now creates a sliding time profile when one is not provided within a statistical request only under the following conditions:
Stat Server logs the created time profile, along with other request attributes, with the following annotation:
generated from request attributes
(ER# 283667004)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release includes no new features or functionality.
This release includes the following corrections and modifications.
Stat Server now resumes writing to the QINFO
, STATUS
, LOGIN
, and
VOICE_REASONS
tables upon reconnection to DB Server, when prior to the disconnection, Stat Server
sent a COMMIT
transaction for submitted records but did not receive DB Server confirmation regarding
the commit. In prior releases, Stat Server stopped writing and did not resume writing to these tables under
these circumstances. (ER# 303024153)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release includes no new features or functionality.
This release includes the following corrections and modifications.
Processing of suspended TEvents has been improved on the Linux operating system. When running on the Linux operating system, Stat Server release 8.1.000.28 became unstable during suspended TEvent processing. (ER# 302841193)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release introduces the following new features or functionality:
This release improves Stat Server's algorithm of rebuilding skill-based virtual agent groups substantially reducing rebuild time. The algorithm in prior releases required that Stat Server review all virtual agent groups for any single change in skill—a time-intensive operation that potentially led to client disconnection due to timeout for environments employing large numbers of virtual agent groups. The improved algorithm shows much faster average rebuild times of virtual agent groups whose definitions are based on skills used and no lag at all for other than skill-based virtual agent groups.
This release includes the following corrections and modifications.
Stat Server's management of suspended TEvent processing has been changed to reduce the risk of Stat Server exit during transmission of time- or reset-based statistics to clients. In previous releases, the suspension of TEvents could cause Stat Server to exit under such circumstances. (ER# 302841193)
Stat Server now properly updates agent capacity upon agent login to another place in cases where
Stat Server did not first receive the EventAgentLogout
TEvent from the current place.
(ER# 300301135)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release introduces no new features or functionality.
This release includes the following corrections and modifications.
Stat Server now properly handles interaction property changes regardless of the value of
the interaction's attr_actor_type
attribute. In previous releases,
Stat Server considered agent-initiated changes only. (ER# 288796607)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release introduces no new features or functionality.
This release includes the following corrections and modifications.
Stat Server's management of Used Data KVList has been improved. Previously, in some cases, it could cause Stat Server to terminate. (ER# 288494749)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release introduces no new features or functionality.
This release includes the following corrections and modifications.
The algorithm for calculating statistics of the EstimWaitTime
category has been
corrected to avoid generating negative or zero values when Stat Server has yet processed no calls
from the queue. Under these circumstances, Stat Server, in this release, now uses the value of
1
(instead of 0
) for EP
(the effective portion of the algorithm). Refer to
the Framework 8.1 Stat Server User's Guide for a complete discussion about the
EstimWaitTime
statistical category and its algorithm.
(ER# 295067822)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release introduces no new features or functionality.
This release includes the following corrections and modifications.
Stat Server no longer erroneously increments the current-number-of-interactions component of the
capacity vector in scenarios where a call is involved in Switch Trunk Optimization (Trunk
Anti-Tromboning). Such scenarios are characterized by the EventPartyChanged
with a
CallState
attribute of RemoteRelease
preceding EventEstablished
.
(ER# 289204094)
Stat Server no longer erroneously starts a redundant CallWait
action on virtual queues
when both the original and consult calls are queued to the same virtual queue and a two-step
transfer is completed while both calls are still queued. (ER# 272977710)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release introduces no new features or functionality.
This release includes the following corrections and modifications.
Stat Server now properly changes an interaction's call type upon receipt of the
EventPartyChanged
TEvent with a same connection ID (ConnID
)
for the interaction. Previously, Stat Server failed to change the interaction's call
type under these circumstances leaving the agent, for example, in CallConsult
state following call transfer. (ER# 281344600)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release introduces the following new features and functionality.
This release introduces the consult-acw-mode
configuration option to control
whether Stat Server associates after call work with consult interactions. Upon termination of the consult call
(upon receipt of EventReleased
) and when this option's value is "last"
, Stat Server
generates ACW that is associated with the consult call only if the call being ended is the only call at the DN.
The default value, "always"
, preserves Stat Server legacy behavior.
Default value: "always"
Valid values: "always"
, "last"
Change takes effect: When Stat Server is restarted.
This release includes the following corrections and modifications.
Stat Server no longer erroneously increments statistics having the following stat type profile upon agent registration at a Position DN in Ready state.
Category=TotalNumber MainMask=NotReadyForNextCall Objects=Agent,GroupAgents Subject=AgentStatus
(ER# 283666611)
Stat Server is now capable of disassociating after call work with consult calls upon their termination..
To enable this functionality, set the consult-acw-mode
Stat Server configuration option to
"last"
. (ER# 280543891)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release introduces no new features or functionality.
This release includes the following corrections and modifications.
Stat Server no longer reports incorrect status of DNs following network disruption where paired T-Server applications in a high-availability environment both run in primary mode. (ER# 278399805)
Stat Server no longer leaks memory after handling GetStat
requests via dynamic APIs
that contain filters defined as an empty string (""
).
(ER# 278244394)
At your option, Stat Server generates the CallAnswered
action on virtual queues for
some single site-specific transfer scenarios. This behavior is controlled by the setting of the
[statserver]/vq-clean-call-details-upon-party-changed
logical configuration option,
which is introduced in this release. The default value of true
means that Stat Server will
not generate CallAnswered
in scenarios stated above. With a setting of false
,
Stat Server will not clear call details; and, as a result, Stat Server will generate
CallAnswered
on virtual queues leading to correct statistic calculation.
Default value: true
Valid values: true
, false
Change takes effect: When Stat Server is restarted.
Stat Server releases 7.6.x and 8.0.x were unable to generate CallAnswered
for virtual queue objects in such scenarios. (ER# 276328991)
Stat Server no longer exits in transfer scenarios where Stat Server receives EventReleased
on the original call after receiving EventPartyChanged
for a consult call (CallConsult
)
that was ringing on a DN while this consult call still persists on some other DN.
(ER# 274513176)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of Stat Server.
ReasonStartOverridesStatusStart
stat type
option. Set this option to true
to have Stat Server provide statistics based
on the timing of reason code changes rather than the timing of status changes. ExpectedWaitTime2
statistical
category for use in statistics to provide estimates of wait-time in virtual queue where agent
capacity to handle multiple, simultaneous, non-voice interactions is prevalent.[log-filter]
and [log-filter-data]
configuration sections.
Refer to Additional Information below.[statserver]/show-queued-interactions
(to show or hide details about queued
interactions in the log) [statserver]/media-type
(for configuration of logging activity of virtual
queue objects)[sml]/hangup-restart
[sml]/heartbeat-period
(for detection of implicit Stat Server hang ups)[common]/enable-ipv6
Refer to the Framework 8.1 Stat Server Deployment Guide for details.
This release includes the following corrections and modifications that were made between Release 7.6 or earlier releases and the initial 8.1 release:
A change in status from Ready
to NotReady
for a specific
media channel now impacts the overall Ready
status of an agent/place when
all other media channels are Ready
.
(ER#s 262616071, 277870254)
Stat Server now updates long-running statuses in the STATUS
table when Stat
Server switches from primary mode to backup or at shutdown. Previously, there was a gap in the
reported statuses during switchover or shutdown. (ER# 274513143)
On Solaris platforms, Stat Server no longer frequently updates long-running statuses as was the case in prior releases. Now, Stat Server limits the frequency of updates to less than every 10 minutes. (ER# 274035405)
Stat Server now properly checks the Operation
attribute of EventPartyAdded
Interaction Server events. As such, Stat Server will no longer generate the CallAnswered
action on the associated virtual queue in multimedia scenarios when this attribute's value is
Conference
. (ER# 270153916)
Stat Server no longer generates a redundant CallAnswered
action on
virtual queue objects in multimedia scenarios where the agent takes a transfer.
(ER# 270153913)
Stat Server no longer exits upon deletion of a database access point that is
configured either without a DB Server application at the Stat Server
Connections
tab or configured as None
.
(ER# 269739785)
The Stat Server application template for Genesys Administrator has been updated to
include default values for the workDirectory
and commandLine
parameters. (ER# 269020201)
Stat Server can now generate the CallAnswered
action on routing points
in scenarios both where a call is distributed to an agent DN on remote switch through
an external routing point and the EventRouteRequest
TEvent on the destination
external routing point is received before the EventRouteUsed
is received on
the originating routing point. (ER# 265502842)
Stat Server now correctly extracts an interaction's media type from custom event data to yield correct filter evaluation. (ER# 265227347)
Stat Server no longer provides an incorrect capacity vector upon receipt of additional
EventDialing
TEvents as is the case in some scenarios.
(ER# 264296165)
The asymmetric influence of change in a media's status on the overall status of a place or agent DN in prior releases has been eliminated. Now, Stat Server correctly evaluates any media status changes regardless of the order in which an agent has logged in to any of them. (ER# 262616076)
Stat Server no longer ceases writing to the LOGIN
table when the
status-table
configuration option is set to on
.
(ER# 261794435)
A time misconversion problem for events sourced from Interaction Server has been
corrected to no longer transmit the source-time monotonicity violated
warning message. (ER# 256576985)
Stat Server now monitors and accordingly applies run-time changes of the
suppress-agent-status-updates-for-ixn-server
configuration option.
(ER# 246523661)
An internal enhancement in call tracking through queues better handles the scenario where Stat Server receives events from external routing points and routing points in a different chronological order than which the events occurred. This misordering of events can cause two widely geographically displaced Stat Server applications to generate different values for statistics despite the fact that the events originate from the same T-Server application. (ER# 249984400)
Stat Server now correctly calculates capacity for agents after performing network-attended
transfers where URS routes the consult leg of the transfer. Previously, Stat Server provided an
incorrect capacity vector upon receipt of EventReleased
in this scenario.
(ER# 241746025)
This section provides the latest information on known issues and recommendations associated with this product.
Stat Server might terminate unexpectedly on Solaris and AIX in the following scenarios:
A
by the client C
(but not any other clients).A
is renamed to B
.B
is removed from the configuration.C
is disconnected from Stat Server.Found In: 8.1.200.51 | Fixed In: 8.1.200.53 |
Stat Server does not link the agent, logged into an extension DN on the Meridian-like switch, to virtual queue. Therefore, the ExpectedWaitTime
statistic on virtual queue produces incorrect values. (SS-6193)
Found In: 8.1.200.46 | Fixed In: 8.1.200.50 |
The CurrentTargetState
statistic, requested for an agent in a multimedia only environment, might contain non-empty place information after the agent logout. (SS-6105)
Found In: 8.1.200.46 | Fixed In: 8.5.000.24 |
When an agent logs out and then logs in, Stat Server does not correctly calculate a duration of agent's statistics for CurrentMinTime
and CurrentMaxTime
categories requested with the MainMask
set to NotReadyForNextCall
. (SS-5999)
Found In: 8.1.200.38 | Fixed In: 8.1.200.41 |
Stat Server returns the "Incorrect 'Subject' Parameter (3)" error to a client requesting to open the CurrentContinuousTime
statistic for an agent with the PlaceStatus
subject. (SS-5997)
Found In: 8.1.200.38 | Fixed In: 8.1.200.39 |
Stat Server sometimes sends an empty LoginID
attribute of the CurrentState
statistic value when an agent logs into multiple DNs and subsequently logs out from one of them. (SS-5897)
Found In: 8.1.200.33 | Fixed In: 8.5.000.24 |
Failure to import metadata for Stat Server into GAX. The Roles Import Failed
status message appears in GAX.
Workaround:
UTF-8
encoding.
Found In: 8.1.200.24 | Fixed In: 8.1.200.31 |
Stat Server fails to send the EventStatInvalid
to clients for statistics that are opened while disconnected from T-Server. (SS-5728)
Found In: 8.1.200.24 | Fixed In: |
As of Stat Server release 8.1.200.24, for the debug-level
configuration option, the Client:6
value replaces the ClientX
value.
For some network-attended transfer and conference scenarios, Stat Server does not end the CallConsult
action which leads to incorrect status after the call is released. (ER# 324523128)
Found In: 8.1.000.38 | Fixed In: 8.1.000.41 |
Genesys recommends that you use the 64-bit executable for platforms other than Microsoft Windows in order
to avoid a recently discovered issue on 32-bit platforms involving the proper calculation of
TotalTime
status-based statistics requested with DCID. (ER# 314672761)
Found In: 8.1.000.33 | Fixed In: 8.1.000.37 |
Stat Server might incorrectly tally MaxTime
status-based statistics for Agent
,
Place
, GroupAgents
, and GroupPlaces
objects when a sliding time profile
has been applied. (ER# 313855871; SS-411)
Found In: 8.1.000.33 | Fixed In: 8.1.200.29 |
During heavy load, Stat Server might occasionally disconnect from and reconnect to other servers, where connections are ADDP-enabled. (ER# 303085288)
Found In: 8.1.000.28 | Fixed In: 8.5.000.24 |
Agent relogin to another place without an explicit logout from the current place leaves a
LoggedIn
action instead of the LoggedOut
action on the former DN.
This leads to Stat Server's incorrect reporting of DN and place status. (ER# 302308759, SS-136)
Found In: 8.1.000.28 | Fixed In: 8.1.000.43 |
Interaction Server allows agents to log in to a place without any media. When encountered with this
scenario, Stat Server will not be able to record agent or place NotMonitored
status to the
Status
table, so time gaps in statuses might result.
(ER# 276012191)
Found In: 8.1.000.11 | Fixed In: |
When using Stat Server 8.1 on HP-UX IPF, you must preload the JVM shared library
to avoid Stat Server exit upon Java initialization. Preload this library by setting the
LD_PRELOAD
environment variable as follows:
$ LD_PRELOAD=${JAVA_HOME}/jre/lib/IA64W/server/libjvm.so $ export LD_PRELOADwhere
JAVA_HOME
points to JDK installation root (for example,
/opt/java1.5
).
If you fail to preload the JVM shared library on the HP-UX IPF platform, the
following error occurs:
/usr/lib/hpux32/dld.so: Unsatisfied data symbol 'UseSIGUSR2' in load module '/opt/java1.5/jre/lib/IA64W/native_threads/libhpi.so'. /usr/lib/hpux32/dld.so: Unsatisfied data symbol 'doCloseWithReadPending' in load module '/opt/java1.5/jre/lib/IA64W/native_threads/libhpi.so'. HPI shl_load failed: Unresolved external There was an error trying to initialize the HPI library. Please check libhpi in your java installation.
(ER# 270092433)
Found In: 8.1.000.11 | Fixed In: |
Stat Server cannot be installed on Windows 2008 64-bit platforms from the product CD. As a workaround, copy the CD image to your hard drive and install Stat Server from this location. (ER# 265960368)
Found In: 8.0.000.30 | Fixed In: |
Stat Server does not insert logout records in the LOGIN
table for Open Media
channels after agent logout. (ER# 259772050; SS-5063)
Found In: 8.0.000.26 | Fixed In: 8.1.000.45 |
Stat Server does not always end CallConferenceOriginated
actions upon
receipt of EventPartyChanged
TEvents as it should. As a result, statistics
measuring CallConference
durations will be overstated.
(ER# 259529432; SS-5062)
Found In: 8.0.000.26 | Fixed In: 8.1.000.45 |
Stat Server might receive a corrupt packed TEvent within the
Interaction Server event_custom
message. When this occurs, Stat Server logs the following message header, followed by a printout of the message content:
Server: WARNING: Interaction Server broken packet (size=(ER# 259494219)) dumped (size= ):
Found In: 8.0.000.26 | Fixed In: |
Stat Server incorrectly calculates TotalTime
statistics requested with
InteractionStoppedInbound
and/or InteractionStoppedOutbound
main masks. Stat Server always returns 0
(zero).
(ER# 256576982)
Found In: 8.0.000.26 | Fixed In: 8.1.000.38 |
Stat Server does not fully support interaction- and trace-level logging for Multimedia events. (ER# 256117875)
Found In: 8.0.000.26 | Fixed In: |
Interaction Server might disconnect from Stat Server in Multimedia environments that must handle a large number of agent logouts when clients are connected to Stat Server. (ER# 242157741)
Found In: 8.0.000.22 | Fixed In: |
Stat Server might incorrectly log the ConnID
attribute for a call that is
being deleted as stuck in a virtual queue as a result of handling an
EventPartyChanged
TEvent for the call. (ER# 240322862; SS-4949)
Found In: 8.0.000.22 | Fixed In: 8.1.200.24 |
Stat Server mistakenly attributes CallReleased
and ACWCompleted
actions to virtual queue objects if the ThirdPartyDN
attribute of
EventDiverted
TEvents points to a known external routing point.
(ER# 235720497; SS-4898)
Found In: 8.0.000.22 | Fixed In: 8.1.200.24 |
Under some circumstances, Stat Server might propagate ACWCompleted
and
CallReleased
actions incorrectly to origination DNs for Meridian Link
T-Servers. (ER# 214803547)
Found In: 8.0.000.22 | Fixed In: |
Action CallMissed
is not generated for a mediation DN at the time when a call is released on an agent's DN, if at that moment the agent's DN is no longer associated with the mediation DN, either through an agent group or place group. The action description in the Framework 8.1 Stat Server User’s Guide does not mention this exception. (SS-5584)
Found In: 81fr_us-statserver_07-2011_v8.1.001.00 | Fixed In: 81fr_us-statserver_12-2013_v8.1.201.00 |
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. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.
Stat Server no longer supports the Package API.
Discontinued As Of: 8.1.200.24 |
Packaged statistics, previously available through the Stat Server API, are now obsolete.
Discontinued As Of: 8.1.000.11 |
Stat Server operation on the following operating systems is no longer supported:
Discontinued As Of: 8.1.000.11 |
Stat Server operation on the Oracle 9 RDBMS is no longer supported.
Discontinued As Of: 8.1.000.11 |
Information in this section is included for international customers.
Stat Server is unable to process statistics for interaction queues if the corresponding tenant name is specified using the Japanese character set. (ER# 85971)
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
Refer to the "Hide Selected Data in Logs" chapter in the Genesys Security Deployment Guide for more information about hiding sensitive data from users.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).
Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website might 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.