Release Note

Stat Server

7.6.x

Genesys Telecommunications Laboratories, Inc. © 2008–2013

Contents

Introduction

Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows
7.6.100.45 [08/12/2011] – Hot Fix     X   X X
7.6.100.44 [04/04/2011] – Hot Fix       X    
7.6.100.43 [12/02/2010] – Hot Fix           X
7.6.100.42 [10/12/2010] – Hot Fix   X   X   X
7.6.100.41 [03/12/2010] – Hot Fix       X   X
7.6.100.40 [03/01/2010] – Hot Fix       X   X
7.6.100.37 [12/11/2009] – Hot Fix       X   X
7.6.100.35 [10/23/2009] – Hot Fix       X   X
7.6.100.34 [10/13/2009] – Hot Fix X X   X   X
7.6.100.33 [09/25/2009] – Hot Fix     X     X
7.6.100.32 [09/03/2009] – Hot Fix           X
7.6.100.31 [08/25/2009] – Hot Fix       X    
7.6.100.29 [08/12/2009] – Hot Fix X     X    
7.6.100.28 [07/21/2009] – Hot Fix         X  
7.6.100.26 [06/16/2009] – Hot Fix       X    
7.6.100.24 [05/12/2009] – Hot Fix X X   X   X
7.6.100.20 [02/25/2009] – Hot Fix           X
7.6.100.19 [01/27/2009] – Hot Fix X X X X X X
7.6.100.17 [11/20/2008] – Hot Fix   X   X   X
7.6.100.15 [10/15/2008] – Hot Fix           X
7.6.100.14 [08/15/2008] – Hot Fix X     X   X
7.6.100.12 [07/17/2008] – General X X X X X X
7.6.000.18 [02/15/2008] – General X X X X X X

Link to 7.5 Product Release Note (Cumulative)
Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


Introduction

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.genesyslab.com for more details.

This release note applies to all 7.6 releases of Stat Server. Information will be added to this release note as subsequent versions of the component are released.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For specific information on any third-party software used in this product, see the Read Me. Please contact your technical support representative if you have any questions.


Release Number 7.6.100.45 [08/12/2011] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release introduces no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


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.

(ER# 276248357)


Stat Server no longer leaks memory after handling GetStat requests via dynamic APIs that contain filters defined as an empty string (""). (ER# 277945991)


Top of Page


Release Number 7.6.100.44 [04/04/2011] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release introduces no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


Stat Server no longer exits in the following scenario:

  1. On startup, Stat Server reads about virtual agent group (VAG) defined by purely skills-based script with agents assigned to the VAG.
  2. Stat Server loses connection to Configuration Server or Configuration Server Proxy.
  3. During the period of disconnection, the VAG script was changed in such a way that no agents are reported under the VAG. In addition, more than 1,000 arbitrary configuration changes were applied in Configuration Server.
  4. Stat Server’s RestoreSession reconnection attempt fails with HistoryLogExpired message from Configuration Server.
  5. After the connection is finally reestablished, the VAG definition is changed to a nonskills-based script with no agents reporting under the VAG.
  6. An agent, who was a member of the VAG defined at Step 1, is deleted from Configuration Server.
  7. The VAG script is deleted.

Previously, Stat Server exited at step 7. (ER# 270151126)


Top of Page


Release Number 7.6.100.43 [12/02/2010] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This section describes new features that were introduced in this release of Stat Server:


Note: Neither option impacts values that Stat Server writes to the QINFO database table.


Corrections and Modifications

This release includes no other corrections or modifications.

Top of Page


Release Number 7.6.100.42 [10/12/2010] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release introduces no new features and functionality.


Corrections and Modifications

This release includes the following corrections and modifications:


Stat Server no longer fails to reflect the addition or removal of agents to/from agent groups in LoadBalance statistics that are requested on origination DNs for skill-based virtual agent groups or regular agent groups in an environment that uses a Nortel Meridian switch and has the agent logged in to a Position DN which is linked to an Extension DN. Previously, in order to obtain expected results for LoadBalance statistics given this configuration, agents had to log out and back in again following changes to the composition of agent groups. (ER# 260499628)


Stat Server no longer exits given the following scenario involving three virtual agent groups that are defined as follows:

script = LoggedIn( "queue2@switch" ), origination_dns = [ queue1 ]
script = LoggedIn( "queue2@switch" ), origination_dns = [ queue2 ]
script = LoggedIn( "queue3@switch" ), origination_dns = [ queue3 ]

where none of the queues are assigned as origination DNs to any other agent groups or place groups. Previously, when an agent logged into his DN and the three queues in queue1-queue2-queue3 order and then logged out, Stat Server exited. (ER# 260561051)


Top of Page


Release Number 7.6.100.41 [03/12/2010] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release introduces no new features or functionality.


Corrections and Modifications

This release includes the following corrections and modifications:


Stat Server no longer fails to generate the CallReleased action on virtual queue objects in some multi-site scenarios where CallEstablished on an origination site RegDN follows EventDiverted on the virtual queue but before CallEstablished is received at the destination site RegDN. (ER# 245119163)


Top of Page


Release Number 7.6.100.40 [03/01/2010] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release introduces the following new features and functionality.


Corrections and Modifications

This release includes the following corrections and modifications:


In scenarios where T-Server is connected to CTI Link and SCS through one network interface (for example, I1), and T-Server is connected to Stat Server through another interface (I2), Stat Server now correctly handles instances of T-Server switchover when network failure occurs on I1. (ER# 243509583)


Stat Server no longer consumes 100% CPU for a prolonged period of time after a disconnect/switchover associated with Interaction Server, when the operation is initiated from Solution Control Interface. (ER# 224813431)


Top of Page


Release Number 7.6.100.37 [12/11/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release introduces the following new features and functionality.


Corrections and Modifications

This release includes the following corrections and modifications:


Stat Server now correctly handles the scenarios associated with Nortel Switch Trunk Optimization (Trunk Anti-Tromboning) in which EventPartyChanged on the agent's DN accompanies CallState=RemoteRelease. Previously, Stat Server incorrectly incremented the current-number-of-interactions component of place capacity vectors associated with the given agent DN. (ER# 240373093)


Stat Server now provides a mechanism to significantly decrease CPU consumption in environments containing a large number of origination DNs. Set the queue-disable-dcid-for-missed-calls option to yes. Read more about this option under the New in This Release section. (ER# 240078514)


Stat Server no longer reports its backup file as corrupt if it contains Java statistics that were requested with a nondefault time profile. (ER# 234873924)


Top of Page


Release Number 7.6.100.35 [10/23/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release introduces no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


Stat Server now correctly recognizes business attributes in statistical requests where Category=JavaCategory. Previously, Stat Server might have misinterpreted the business attributes that accompanied such requests, which, in turn, resulted in Stat Server's generation of incorrect values. (ER# 236724402)


Top of Page


Release Number 7.6.100.34 [10/13/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release introduces the following new Sat Server configuration options:

Corrections and Modifications

This release includes no other corrections or modifications.

Top of Page


Release Number 7.6.100.33 [09/25/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release introduces the following new features and functionality:

Corrections and Modifications

This release includes no other corrections or modifications.

Top of Page


Release Number 7.6.100.32 [09/03/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


Stat Server no longer erroneously increments the current_number counter of interactions in agent and place capacity vectors under the following circumstances:

(ER# 231459958)


Top of Page


Release Number 7.6.100.31 [08/25/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


Statistic packages requested with NotificationMode=Reset no longer cause Stat Server to fail on Solaris platforms. (ER# 233867802)


Statistic packages requested with StatisticType=Any no longer cause Stat Server to fail on Solaris platforms. (ER# 232909725)


Top of Page


Release Number 7.6.100.29 [08/12/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


Stat Server no longer intermittently exits in scenarios where Stat Server clients submit multiple requests to open the same Java statistic. Previously, the Stat Server process either hung indefinitely or exited under these circumstances. (ER# 232140869)


Top of Page


Release Number 7.6.100.28 [07/21/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. There are no restrictions for this release, which contains the following new feature:

Corrections and Modifications

This release also includes the following corrections and modifications:


Stat Server now generates the following durable actions on mediation DNs belonging to the Environment tenant when these DNs are assigned as origination DNs to groups of agents or places that belong to some other tenant and the allow-vq-orig-dns-from-environment configuration option has been set to yes:

(ER# 230343418)


Top of Page


Release Number 7.6.100.26 [06/16/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. There are no restrictions for this release, which contains the following new feature:

Corrections and Modifications

This release also includes the following corrections and modifications:


Stat Server no longer generates a CallAnswered action for virtual queue objects if the ThirdPartyDN attribute of the corresponding EventDiverted (EventRouteUsed) TEvent points to another mediation DN which is not an ACD queue. If Stat Server cannot determine the destination DN type from the ThirdPartyDN attribute and the call is subsequently answered by an agent, Stat Server generates the CallAnswered action in accordance with the setting of the vq-treat-unknown-third-party-dn-as-agent-dn configuration option. (ER# 220667881)


Stat Server no longer miscalculates CurrentNumber statistics, where MediaType=email, that are requested for agent groups in some scenarios where the same statistic is requested for some other regular or virtual agent group and an agent is added to that group. (ER# 224391286)


Top of Page


Release Number 7.6.100.24 [05/12/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


Stat Server now recognizes the DND key of the AttributeExtensions attribute in EventRegistered/EventAddressInfo TEvents for both Position and Extension DNs on NEC switches. If the key's value is 1, Stat Server immediately starts do-not-disturb on the DN, which is reported with the NotReadyForNextCall action on the DN. (ER# 223563106)


Stat Server can now selectively suppress the transmission of userdata on DN and switch objects. To support this functionality, this release introduces a new configuration option, suppress-user-data, which you can configure in the statserver section of the Annex tab for switch and/or DN objects. The default value of this option is no, which indicates that Stat Server will continue to receive and transmit userdata to its clients. If this option's value is set to yes, however, Stat Server will instruct T-server not to transmit any EventAttachedDataChanged or AttributeUserData in any other TEvent. As a result, Stat Server will not send user-data to its clients for the associated DN or switch object. If this option is defined for a particular DN, its value overrides any value that may be specified at the switch.

The option is dynamic in the sense that new values for the option, at both the DN and switch levels, are taken into account only upon DN re-registration.

Note: The selective suppression of userdata is possible only with T-Server 7.6 and forward releases. (ER# 222201107)


Stat Server now generates an AfterCallWork status for agents on Avaya switches in scenarios where both the original inbound call and the consult call, at dialing, were placed on hold, the inbound call was retrieved from hold, EventAgentNotReady with ACW workmode was received for the agent’s DN, and the inbound call was released. (ER# 220829067)


Stat Server now correctly handles the following scenario related to the status of Extension DNs on NEC switches:

  1. Agent is logged in on a Position DN and not logged in to the Extension DN.
  2. DND begins on the Extension DN.
  3. DND ends on the Extension DN.

Previously, in such scenarios, Stat Server erroneously reported the status of the Extension DN as NotReadyForNextCall instead of WaitForNextCall—the actual status of the DN. (ER# 219074030)


Stat Server now sends to its clients a PackageError response if the requested package includes an invalid or unsupported statistic. (ER# 197638281)


Top of Page


Release Number 7.6.100.20 [02/25/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


When the position-extension-linked configuration option is set to yes, Stat Server now correctly updates agent status to AfterCallWork given the following scenarios:

Scenario 1

  1. An agent, AgentA, is logged on to a Position DN.
  2. A call is transferred to the agent's Extension DN.
  3. AgentA enters the NotReady state with workmode equal to ACW on the Position DN.
  4. AgentA performs a mute transfer to another agent with EventReleased occurring on the consult call before the original call is released.

Scenario 2

  1. An agent answers a call.
  2. Agent enters the NotReady state with workmode equal to ACW on the Position DN.
  3. The agent puts the call on hold.
  4. The call gets released while on hold.

In previous releases, Stat Server erroneously set the agent's status to NotReadyForNextCall under these circumstances. (ER# 214613117)


Top of Page


Release Number 7.6.100.19 [01/27/2009] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


For virtual–queue related multi-site scenarios, where there is significantly different network latency on connections between Stat Server and T-Servers, in-memory Stat Server data no longer experiences corruption. A typical scenario that might have produced this corruption in the past is as follows:

The virtual queue is located on site 1, and the route point and DN are located on site 2. The T-Server on site 1 has a fast connection with Stat Server, but the T-Server on site 2 has a slow connection with that same Stat Server.
t1: EventQueued ( VQ, Connid=CONNID1,TransferConnid=CONNID2 )
t1: EventRouteRequest( RP, Connid=CONNID1 )
t2: EventDiverted ( VQ, Connid=CONNID1, TransferConnid=CONNID2 )
t2: EventRouteUsed ( RP, Connid=CONNID1 )
t3: EventRinging ( DN, Connid=CONNID1 )
t4: EventQueued ( VQ, Connid=CONNID1,TransferConnid=CONNID2 )
t5: EventReleased ( DN, Connid=CONNID1 )
t6: EventRouteRequest( RP, Connid=CONNID1 )
...
For the above valid TEvent sequence, previously, Stat Server corrupted data in memory at moment t4.(ER# 198639704)


Stat Server now correctly implements the check-stuck-calls feature for T-Servers that are configured for load balancing on a single route point. Previously, Stat Server did not take into account the intentional distribution of calls for a single routing point across T-Servers deployed in a load-balancing configuration, and incorrectly deleted calls that were not stuck. (ER# 214934271)


Top of Page


Release Number 7.6.100.17 [11/20/2008] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


Stat Server now returns statistics' stat type names as well as their values for package requests where the notification mode had been set to immediate. Previously, in package responses, Stat Server failed to return the corresponding stat type names leaving clients unable to match returned values with the appropriate statistics. (ER# 208632361)


This release corrects a Stat Server memory leak which occurred under certain circumstances involving the ACD (or virtual) queue deleting user data (ThisDN=ThirdPartyDN=<queue>) which had been attached by some other party of a call. This leak affected all platforms on which Stat Server operates. (ER# 212876956)


A memory corruption problem, arising in some scenarios associated with the closing of Java statistics, has been fixed. (ER# 172763301)


Top of Page


Release Number 7.6.100.15 [10/15/2008] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


Stat Server no longer exits after an agent, who is a member of a virtual agent group, logs out from a queue when the virtual agent group, based on the LoggedInQueue expression recognizes this queue as an origination DN. (ER# 208284691)


Stat Server now correctly handles EventRinging in cases where the connection ID is not equal to the previous connection ID and CallState="Transferred". Previously, Stat Server failed to increment the current_number of interactions component of the capacity vector in such situations. Stat Server further decremented this component upon receipt of the subsequent EventReleased TEvent, which led to a negative current_number of interactions in the capacity vector. (ER# 206808159)


Stat Server now correctly handles EventRinging in cases where the connection ID is not equal to the previous connection ID and CallState="Conferenced". Previously, Stat Server failed to increment the current_number of interactions component of the capacity vector in such situations. Stat Server further decremented this component upon receipt of the subsequent EventReleased TEvent, which led to a negative current_number of interactions in the capacity vector. (ER# 207732201)


Stat Server now provides the correct capacity vector under the following scenario:

  1. AgentA at site S1 dials a consult call to routing point RP.
  2. From RP, the consult call is distributed to site S2.
  3. From S2, the consult call is forwarded back to S1 and is handled by AgentB.

Previously, given this scenario, Stat Server erroneously incremented the current_number of interactions component of the capacity vector for AgentA at Step 3 upon receipt of the EventPartyChanged TEvent. And, as a result, AgentA became nonrouteable after the call was released. With this hot fix, Stat Server correctly reports the current number of interactions in this scenario, finally as 0 for AgentA (instead of 1). (ER# 210239911)


Top of Page


Release Number 7.6.100.14 [08/15/2008] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


A problem was observed on several operating systems with prior versions of Stat Server generating exceptions upon reloading of a Java extension if such extension performed logging from multiple threads. This version of Stat Server fixes this problem for Windows operating systems. (ER# 199303363)


This release reduces the processing time required for adding and/or deleting skills in environments using virtual agent group definitions built on static script expressions. In previous releases, the combination of certain events contributed to a delayed processing time that exceeded the default addp timeout and caused Stat Server to disconnect from T-Server. (ER# 198160442)


Stat Server now associates the correct reason code with the WaitForNextCall action for a media channel at a place. Previously, the associated reason code in such a case was always equal to 3. (ER# 196142056)


Top of Page


Release Number 7.6.100.12 [07/17/2008] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in the initial 7.6.1 release of Stat Server.

Corrections and Modifications

This release also includes the following corrections and modifications:


Stat Server no longer generates incorrect values for CurrentNumber statistics on queue objects when the main mask includes the DNActive action and the queue is defined as an origination DN in scenarios where the DN is in AfterCallWork or the agent is actively involved in a call. (ER# 66175045)


Stat Server no longer increments TotalNumber statistics with MainMask=CallAnswered on routing points in scenarios where the ThirdPartyDN attribute of the EventRoutedUsed TEvent that Stat Server receives points to a mediation DN. (ER# 169297907)


Stat Server now supplies the correct maximum number to its clients for statistics having the following stat type profile:

Category=MaxNumber
MainMask=CallWait
Subject=DNAction
Mode=TimeBasedNotification

In previous releases, Stat Server might generate incorrect values for such statistics. (ER# 174444771)


Stat Server now generates correct values for statistics having the following stat type profile:

Category=MinNumber
MainMask=CallWait
Subject=DNAction
Objects=Queue

In previous releases, Stat Server might erroneously send to its clients 0 as an initial value when, in fact, the value was other than 0. Furthermore, Stat Server would continue sending zeros after that. (ER# 174444779)


Stat Server no longer sends to its clients an incorrect value upon opening a statistic in scenarios when the same statistic was already previously opened (such as by another client request or upon read from backup) for TotalNumber statistics using a time-based notification mode. (ER# 174444826)


Stat Server now correctly applies the MediaType filter to actions associated with user data. In previous releases, actions of a particular media type (MediaType=<media>) were erroneously filtered out if they had associated user data. (ER# 175164746)


Removing a media using the Genesys Agent Desktop application no longer triggers Stat Server to log an agent out from his place. Previously, upon receipt of event_media_removed from Interaction Server, Stat Server unlinked the agent-place association, which implicitly logged the agent out from the place. (ER#s 179960702, 194007997)


Stat Server now considers the value of the ThisQueue attribute for event_processing_stopped events received from Interaction Server. As such, statistics filtered by this attribute are now calculated properly. (ER# 181510003)


Stat Server no longer exits when the deletion of a queue object from configuration is followed by the enabling or disabling of places logged on to that queue. (ER# 182539771)


Stat Server now considers EventAttachedDataChanged TEvents that Stat Server may receive for virtual queue objects (as well as other TEvents, such as EventQueued, EventDiverted, EventReserved_2) in its determination of whether a particular call is stuck. In previous releases, if the conditions were satisfied, Stat Server would clear such calls despite receipt of this event. (ER# 190292157)


Stat Server now waits an additional 60 seconds before clearing calls that Stat Server determines to be stuck instead of immediately clearing them upon expiration of the URS heart-beat timeout (as reported by the EventReserved_2 TEvent). Previously, high network latency situations contributed to appearance of these calls as being stuck at virtual queues when they were not. (ER# 190629122)


Top of Page


Release Number 7.6.000.18 [02/15/2008] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents section, above.

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in the initial 7.6 release of Stat Server.

Corrections and Modifications

This release includes the following corrections and modifications that were made between Release 7.5 or earlier releases and the initial 7.6 release:


Stat Server now preserves the sequence in which key-value pairs with the same key are being attached to an interaction. In previous releases, the GetNumber function might return incorrect results in statistics that rely on the order in which key-value pairs with the same key are attached. (ER# 23241951)


Disabled agents or places no longer contribute to their groups' current status statistics when the ignore-disabled-objects-in-group-statistics configuration option is set to yes. Stat Server now recalculates current status for agent groups and place groups immediately following the object's return to an enabled state. (ER# 24842881)


In locales where the default decimal delimiter is a comma, Stat Server no longer reports string representations of floating-point values to its clients using a comma as a delimiter. Starting from this release, Stat Server uses decimal points in all cases and for all clients. Previously, the effect of Stat Server's string representations of floating-point values caused some clients, such as CCPulse+, to display incorrect values when the client's default decimal delimiter was a comma. (ER# 60550847)


Stat Server no longer writes records to the LOGIN table of the Stat Server database that are not associated with any login or logout activity. Previously, under some circumstances, Stat Server may have done just that. (ER# 60796391)


When the enable-binding configuration option is set to yes, Stat Server now considers the settings of the qinfo-table, login-table, and status-table configuration options before initializing binding for tables. Previously, Stat Server initialized bindings for all tables regardless of the values for these three options. As a result, Stat Server logged errors for one or more of those tables when it failed to initiate a binding, even if the corresponding option was set to off. (ER# 62682137)


In scenarios where an agent is removed from a group in the Configuration Layer and then re-added back to the same group, upon a change in status from Ready to NotReady, Stat Server no longer incorrectly computes TotalTime statistics based on an AgentStatus subject. (ER# 80547508)


Stat Server no longer incorrectly calculates TotalTime statistics with an AgentStatus or DNStatus subject requested for AgentGroup objects in scenarios associated with an agent's removal from the agent group. (ER# 80547867)


Stat Server no longer mistakenly discards data about multimedia logins if Stat Server disconnects from a T-Server that processes voice interactions. In previous releases, Stat Server incorrectly computed statistics that depended on this information. (ER# 86387245)


In blended environments where an agent is logged in to both a non-voice media channel and voice DN, after the agent goes out of service on the voice DN, Stat Server no longer fails to register Ready and LoggedIn DN actions on the media channel or to notify CCPulse+ clients of NotMonitored DN actions on the voice DN. (ER# 100394311)


After restart, Stat Server now correctly calculates the total number of Ready statuses on multimedia channels in time-based notification mode where Filter=PairExists("MediaType", "email"). (ER# 102787381)


Stat Server now adjusts TotalOrigDNCallWaitTime statistics with the time that the origination DN is configured for an agent or place group if this occurs after a CallWait action for the origination DN starts. Previously, Stat Server correctly counted this statistic only if the origination DN was continuously configured for agent or place group from the start to completion of a CallWait action for the origination DN. (ER# 115308310)


Stat Server now increments TotalNumbOrigDNCallWait statistics when the origination DN is removed from agent or place group configuration while the CallWait action is occurring at the origination DN. Previously, dynamic reconfiguration of an origination DN under these circumstances prevented the update of TotalNumbOrigDNCallWait statistics. (ER# 117692832)


Stat Server now correctly calculates CurrentNumber and CurrentTime values for OrigDNCallWait statistics when an origination DN is dynamically removed from agent group or place group configuration while a CallWait action is occurring at the origination DN. Stat Server decrements CurrentNumber values by 1 and increments CurrentTime values when the CallWait action completes. (ER# 117692834)


Stat Server no longer reports negative CurrentNumber or CurrentTime values for OrigDNCallWait statistics if an origination DN is added to agent group or place group configuration while a CallWait action is occurring at the origination DN. (ER# 117692881)


Stat Server now enables Extension DN objects containing @ in the name to serve as routable objects. Previously, Stat Server enabled routing to ACD Position, routing points, and ACD queues that contained this character in their names, but not to Extension DN objects. (ER# 119291561)


In response to client requests for historical or current statistics, Stat Server no longer sends EventPackageInfo before receiving SEventPackageAccepted. (ER# 119681645)


Upon T-Server restart and upon the presentation of at least one login on a non-voice media, Stat Server now reports the status of the voice DN as WaitForNextCall. Previously, Stat Server stopped monitoring media after shutdown of T-Server (voice) and reported the voice DN as NotReadyForNextCall. (ER# 120563021)


In the scenarios involving a lost connection with DB Server, Stat Server now correctly updates long-running statuses—whether started before or following DB Server disconnection and whether completed before or following DB server connection—upon successful reconnection to DB Server. Previously, instead of updating the timestamp for the record of the associated long-running status, Stat Server issued new INSERT statements at 10-minute intervals to record updates to the status. (ER# 120822427)


When the enable-binding configuration option is set to yes and upon reconnection to DB Server, Stat Server no longer tries to send to DB Server all of the data which had accumulated during the period of disconnect simultaneously. Instead, Stat Server transmits this data in smaller portions to decrease the possibility of subsequent data loss. (ER# 120823201)


Stat Server now correctly calculates statistics having the following stat type definition:

Category=TotalNumber
Formula=DistByConnID
MainMask=AfterCallWork
Objects=GroupAgents, GroupPlaces
Subject=AgentStatus

(ER# 123069489)


A memory corruption issue, apparent when one or more Stat Server Java Extensions are loaded, has been fixed. Previously, Stat Server may have exited because of this problem. (ER#s 127358623, 134596003)


In scenarios where an agent is removed from a group in Configuration Server, then added back to the same group, and then the group is reconfigured from regular agent group to a virtual agent group, Stat Server now correctly computes TotalTime statistics requested with Subject=AgentStatus. (ER# 130356742)


Stat Server no longer exits as a result of incorrectly processing EventPartyChanged TEvents against virtual queue objects. (ER#s 130992021, 135383059, 137753944)


For scenarios involving network-attended (two-step) transfers, Stat Server no longer computes an incorrect capacity vector for the agent receiving the transferred call. In previous releases, Stat Server failed to decrease the current-number-of-interactions component of the capacity vector for the destination agent/place after the transfer was completed and the corresponding (original) call was released. (ER#s 131812131, 130356688)


Stat Server no longer erroneously reports DN status as WaitForNextCall in the following scenario:

  1. Agent goes to a LoggedOut state on a DN from the WaitForNextCall state.
  2. Stat Server receives the EventDNDOff TEvent on the DN.

(ER# 135180985)


Stat Server now correctly decreases the current-number-of-interactions component of capacity vector for an agent/place in network attended transfer and conference scenarios. (ER#s 135181551, 140300245)


Stat Server now correctly computes statistics having the following stat type profile:

Category=CurrentNumber
Objects=Place,Agent,GroupPlaces,GroupAgents
MainMask=LoggedIn
MediaType=
Subject=DNAction
Previously, Stat Server failed to accurately calculate and report the current number of login actions for non-voice interactions, where the MediaType attribute was specified as part of the statistic's stat type definition. (ER# 136597519)


Stat Server now considers all diversions of non-voice interactions from virtual queues to agents. Previously, Stat Server computed statistics for calls answered or abandoned as they pertained to voice interactions only. (ER# 138848944)


Stat Server now correctly computes supervisor capacity to accept additional interactions in scenarios when:

Previously, the supervisor might not receive calls following this scenario and when the URS use_agent_capacity configuration option was set to yes. (ER# 141474946)


When the state of an interaction is CP_Detect (party state=13 or 0xD), Stat Server no longer erroneously reports the interaction as stuck on a routing point when diverted from that routing point. Previously, scenarios involving Outbound Contact predictive dialing mode gave rise to calls being stuck at the routing point. (ER# 147330948)


Stat Server no longer records sizeable and incorrect durations to the VOICE_REASON table in scenarios where an agent logs in, the system is reset to an earlier time (as little as a few minutes earlier), and then the agent logs out. (ER# 149292960)


Stat Server no longer exits after receiving the EventReserved_2 TEvent for ACD queues. Previously, Stat Server exited if URS distributed EventReserved_2 when the ACD queue was mistakenly specified in the strategy instead of the virtual queue definition. (ER#s 150205905, 130947520)


When Stat Server detects do-not-disturb on/off agent activity for non-voice media interactions, Stat Server will no longer incorrectly generate statistics based on the SMABlocked or Available actions. (ER# 151110239)


Previously, on Microsoft Windows platforms, Stat Server, operating as a 32-bit process, could only use 2 GB of memory. In this release, Stat Server can use 3 GB of memory on 32-bit platforms and 4 GB on 64-bit Windows platforms under the condition that the /3G option is set in the initialization boot file (boot.ini) and Physical Address Extension (PAE) support is enabled. PAE support is achieved by setting the IMAGE_FILE_LARGE_ADDRESS_AWARE bit in the Stat Server process image header. (ER#s 155106606, 151871614 )


If WaitForNextCall or AfterCallWork occurs at a DN for which EventRegistered or EventAddressInfo reports an AgentStatus of 5 (Walk_Away), Stat Server now ends the WaitForNextCall or AfterCallWork actions and starts a NotReadyForNextCall action. Previously, Stat Server ignored this agent status and WaitForNextCall or AfterCallWork continued. (ER# 155085035)


For those environments employing a large number of virtual agent group definitions, Stat Server now consumes much less CPU than in previous releases when it handles agent logins and logouts. Previously, in such scenarios, Stat Server performance and client connections were hindered by high CPU consumption. (ER# 163074112)


Now, the Stat Server log will always report two time ranges for statistical requests having the ServiceFactor1 statistical category in their stat type definition. If you do not specify either or both time ranges, as required by design, Stat Server will apply default values and log a message accordingly. (ER# 163202173)


Stat Server no longer incorrectly resets the duration of current object status in current state statistics to zero in the following scenario:

(ER# 163253481)


Stat Server now correctly generates CallReleased and ACWCompleted actions on the DN associated with an answered and observed consult call. Previously, Stat Server did not increment statistics having these actions defined in the main mask. (ER# 163877920)


Stat Server no longer fails to set up an addp protocol upon reconnecting to T-Server in the following and like scenarios:

  1. Both primary and backup T-Server applications are functioning in hot-standby mode with the backup T-Server operating as primary.
  2. Stat Server starts and registers DNs with the backup T-Server still operating in the primary role; addp is configured within both T-Server applications.
  3. Stat Server disconnects from the backup T-Server due to addp timeout or some other reason.
  4. Stat Server then reconnects to T-Server (either primary or backup).

In previous releases, upon reconnection to T-Server, Stat Server failed to preserve addp. (ER# 164112385)


In blended media environments, Stat Server now sends CurrentTargetState_TargetUpdated events to clients subscribed to receive CurrentTargetState statistic notifications in the following scenario:

  1. An agent logs in to a voice DN.
  2. The agent logs in to a non-voice media.
  3. The agent logs out from the voice DN.
(ER# 164687756)


Stat Server now correctly computes TotalNumber statistics with DCID for the following call-related, durable actions on regular DNs:

Previously, Stat Server failed to increment TotalNumber statistics if DCID was specified in the Formula of the underlying stat type definition. (ER# 167479461)


Stat Server no longer exits upon handling client requests of type GET (for example, GetStat) when the verbose log option is set to debug. (ER# 168728605)


Prior to opening statistics at startup, Stat Server now checks that the binary format of the backup file is compatible with the running instance of Stat Server. Previous releases of Stat Server tried to read backup files with newer binary format without performing this check, which may have caused Stat Server to exit. (ER# 170651294)


Stat Server is now able to issue SQL statements with values containing apostrophes (single quotes) to its database. Previously, if Stat Server encountered such a string [for example, ...VALUES (..., 'ReasonCode', 'Sup'sTasks', ...)] Stat Server disconnected from DB Server with an error and failed to record the data to the Stat Server database. (ER# 172382958)


Stat Server no longer exits when a tenant is removed from the Tenants tab in Configuration Manager and when there are opened Java statistics requested with business attributes (such as MediaType). (ER# 172763308)


For ASM_Engaged calls, Stat Server now generates the CallRinging action upon receipt of EventRinging. (ER# 173534511)


Top of Page


Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.


Stat Server generates exceptions following agent logout when the agent is a member of a virtual agent group that is defined as a LoggedIn expression for an ACD queue that is configured as an origination DN for the same virtual agent group. (ER# 261039051)

Found In:  7.6.100.41 Fixed In: 

Stat Server incorrectly calculates capacity for agents after performing network-attended transfers where URS routes the consult leg of the transfer. (ER# 241746025)

Found In:  7.6.100.32 Fixed In: 

Stat Server might fault after a call is mute-transferred to an agent and then forwarded from their ACD position. Following the Stat Server NCO fault, URS cannot route calls to the agents because Stat Server does not recalculate capacity snapshots for any of the agents from the time of the crash onwards. (ER# 243326095)

Found In:  7.6.100.31 Fixed In: 

Stat Server does not increment CallAnswered statistics on routing points if the call was waiting at both a routing point and external routing point simultaneously. On the other hand, Stat Server does increment CallAnswered statistics if the call enter the external routing point following distribution from routing point. (ER# 249984400)

Found In:  7.6.100.24 Fixed In: 

Stat Server mistakenly triggers the CallMissed and ACWMissed actions on ACD queue objects in multisite environments in the following scenario:

Stat Server correctly generates CallAnswered and then CallReleased following termination of after-call work. Stat Server, however, incorrectly triggers the CallMissed and ACWMissed actions on the ACD queue. (ER# 237204053)

Found In:  7.6.100.24 Fixed In: 

Stat Server does not trigger the CallReleased action on ACD queue objects in multisite environments in the following scenario:

Stat Server correctly generates CallAnswered and then CallReleased following termination of after-call work. Stat Server, however, does not trigger the CallReleased action on the ACD queue. (ER# 237204023)

Found In:  7.6.100.24 Fixed In: 

Stat Server double counts the number of NotReady agent statuses in blended environments (voice and email). (ER# 234076508)

Found In:  7.6.100.24 Fixed In: 

Stat Server ignores the renaming of filters in the Transactions folder in Configuration Server. (ER# 239003555)

Found In:  7.6.100.20 Fixed In: 

Stat Server sometimes reports the backup file as corrupt if it contains Java statistics that use other than the Default time profile. (ER# 234873924)

Found In:  7.6.100.20 Fixed In:  8.0.000.22

Stat Server cannot connect to the primary CS Proxy after changing CS-Proxy configuration and CS Proxy switchover. (ER# 241573821)

Found In:  7.6.100.19 Fixed In: 

For DNs that handle both IM and voice, you may encounter issues with the manner in which Stat Server calculates statistics for estimated waiting time and load balancing. For estimated waiting time, the calculation for Average Handling Time is based on both IM and voice media, instead of one or the other. In the case of load balancing and Stat Server’s understanding of agent availability, Stat Server does not use the “Wait for Next Call” concept (as it would with a voice-only DN), but, rather, the notion of capacity (consistent with multimedia DNs). (ER# 185281693)

Found In:  7.6.100.15 Fixed In:  7.6.100.24

Stat Server no longer consumes 100% CPU for a prolonged period of time after a disconnect/switchover associated with Interaction Server, when the operation is initiated from Solution Control Interface. (ER# 224813431)

Found In:  7.6.100.14 Fixed In:  8.0.000.24

When the status-table-update-end-time-at-end-only Stat Server configuration option is set to true, Stat Server does not always to set the end time upon shutdown for records in the STATUS for long running statuses of type LoggedOut (Status=23). (ER# 240527967)

Found In:  7.6.100.12 Fixed In: 

Stat Server erroneously increments the current_number counter of interactions in agent and place capacity vectors under conditions of overflow where T-Server detects that a transferred call was previously on a particular site and generates EventPartyChanged (CallState=0) to change the call's connection ID. (ER# 220680025)

Found In:  7.6.100.12 Fixed In:  8.0.000.22

Stat Server may generate incorrect values for MinNumber and MaxNumber statistics having the following main mask:

*, ~NotMonitored, ~LoggedOut

(ER# 197646409, 197301076)

Found In:  7.6.100.12 Fixed In:  8.0.000.22

Stat Server mistakenly increments TotalNumber statistics with MainMask=CallReleased and MainMask=ACWCompleted on routing points in scenarios where the ThirdPartyDN attribute of the EventRouteUsed TEvent that Stat Server receives points to a mediation DN. (ER# 197336277)

Found In:  7.6.100.12 Fixed In:  8.0.000.22

Stat Server mistakenly increments TotalNumber and TotalTime statistics where MainMask=CallAbandonedFromRinging on routing points in scenarios where the ThirdPartyDN attribute of the EventRouteUsed TEvent that Stat Server receives points to a mediation DN. (ER# 197336271)

Found In:  7.6.100.12 Fixed In:  8.0.000.22

For Extension DNs associated with a SIP Server, dynamically changing the value of the multimedia configuration option while Stat Server is running causes Stat Server to emulate removal of the DN. (ER# 185312732)

Found In:  7.6.100.12 Fixed In: 

Stat Server erroneously increments TotalNumber statistics with MainMask=CallAnswered on routing points in scenarios where the ThirdPartyDN attribute of the EventRoutedUsed TEvent points to a mediation DN. (ER# 169297907)

Found In:  7.5.000.25 Fixed In:  7.6.100.12

Under unknown circumstances, Stat Server may exit if the same time-based statistics with Category=JavaCategory are opened in several CCPulse+ applications when one of those applications exits. (ER# 174912389)

Found In:  7.5.000.21 Fixed In:  7.6.100.17

In highly loaded environments, Stat Server may fail to promptly send addp messages to T-Server. Performing time-consuming operations may delay timely addp notification. (ER# 119594837)

Found In:  7.5.000.16 Fixed In:  8.0.000.22

Under rare circumstances, Stat Server may generate a corrupt backup file, one that Stat Server cannot load upon a subsequent startup. (ER# 111713533)

Found In:  7.5.000.16 Fixed In: 

Stat Server may stop monitoring objects for a configured tenant during dynamic reconfiguration as when a tenant is removed from configuration (Tenants tab in Stat Server’s application properties) and then re-assigned to Stat Server. To avoid the problem, increase value of the addp-timeout configuration option in Stat Server connection with Configuration Server (ER# 91482225)

Found In:  7.5.000.16 Fixed In:  8.0.000.27

Stat Server may incorrectly compute CurrentNumber statistics on queue objects when the main mask includes the DNActive action and the queue is defined as an origination DN in a few scenarios where the DN is in AfterCallWork or actively involved in a call. (ER# 66175045)

Found In:  7.5.000.16 Fixed In:  7.6.100.12

In scenarios involving erroneous agent attempts to initiate "duplicate" network consult calls, such as depicted in the following scenario, Stat Server fails to decrement the "current number of interactions" component of a capacity vector for Agent2 after both inbound and consult calls end. As a result, Agent2 may become unrouteable.

  1. Agent1 (registered on premise TServer1) receives a call from the network.
  2. Agent1 originates a network consult to Agent2, who is registered on premise TServer2.
  3. A network consult interaction is established between Agent1 and Agent2.
  4. Agent2 originates a network consult to Agent3 (registered on premise TServer2). Premise TServer2 generates Unsupported operation error message.
  5. Agent1 completes the network transfer.
  6. Agent2 releases the inbound call after some conversation with the customer.

(ER# 134069971)

Found In:  7.2.002.23 Fixed In:  8.0.000.22

In some multi-site scenarios, Stat Server may incorrectly calculate statistics having the following stat type profile on virtual queues:

Category=TotalNumber
MainMask=CallReleased  and/or ACWCompleted
Formula =DCID

(ER# 101004281)

Found In:  7.2.002.23 Fixed In: 

Under unknown circumstances, Stat Server may incorrectly increment TotalNumber statistics with CallEntered for ACD queue and route point objects when the statistics are filtered by DNIS or ThisQueue call attributes. (ER# 102781841)

Found In:  7.2.002.21 Fixed In: 

Stat Server incorrectly calculates current logout time for voice media in blended media environments after login and logout on non-voice media. (ER# 104481419)

Found In:  7.2.002.05 Fixed In:  7.6.100.12

If the do-backup-in-background Stat Server configuration option is set to no, Stat Server may fail to generate valid backup file. So, upon a subsequent restart, Stat Server may not be able to load the file and log its corruption. (ER# 89084820)

Found In:  7.2.002.15 Fixed In: 

Stat Server does not calculate CallAnswered, Time to Answer, and TotalTalkTime statistics for virtual queue objects in remote IVR scenarios. (ER# 83411188)

Found In:  7.2.002.05 Fixed In: 

Stat Server ignores configuration changes that occur during initialization. As a result, Stat Server may provide incorrect statistical values to its clients. And, on some rare occasions, Stat Server may exit. (ER# 80707189)

Found In:  7.2.002.05 Fixed In: 

In some Abandon/Transfer/Conference scenarios involving origination DNs, Stat Server may return incorrect values for statistics with filters evaluating to TRUE and having the following profile:

Category=TotalTime
MainMask=OrigDNCallWait,OrigDNCallWaitInbound, OrigDNCallWaitOutbound, OrigDNCallWaitInternal,
         OrigDNCallWaitConsult, OrigDNCallWaitUnknown
Objects=GroupAgents, GroupPlaces
Subject=DNAction

(ER# 79740431)

Found In:  7.2.002.05 Fixed In:  7.5.000.20

In some Abandon/Transfer/Conference scenarios involving origination DNs, Stat Server accumulates CurrentNumber values as it does TotalNumber values and does not decrement the values of those statistics (when Stat Server should) with filters evaluating to TRUE and having the following profile:

Category=CurrentNumber
Formula=DCID
MainMask=OrigDNCallWait,OrigDNCallWaitInbound, OrigDNCallWaitOutbound, OrigDNCallWaitInternal,
         OrigDNCallWaitConsult, OrigDNCallWaitUnknown
Objects=GroupAgents, GroupPlaces
Subject=DNAction

(ER# 79549785)

Found In:  7.2.002.05 Fixed In:  7.5.000.20

After receiving EventQueued on an origination DN and regardless of the TEvent that follows, Stat Server accumulates CurrentTime values and never resets statistics with filters evaluating to TRUE and having the following profile:

Category=CurrentTime
MainMask=OrigDNCallWaitI,OrigDNCallWaitInbound, OrigDNCallWaitOutbound, OrigDNCallWaitInternal,
         OrigDNCallWaitConsult, OrigDNCallWaitUnknown
Objects=GroupAgents, GroupPlaces
Subject=DNAction

(ER# 79549755)

Found In:  7.2.002.05 Fixed In:  7.5.000.20

In some Abandon/Transfer/Conference scenarios involving origination DNs, Stat Server might return incorrect values for statistics with filters evaluating to TRUE and having the following profile:

Category=TotalNumber
MainMask=OrigDNCallWait,OrigDNCallWaitInbound, OrigDNCallWaitOutbound, OrigDNCallWaitInternal,
         OrigDNCallWaitConsult, OrigDNCallWaitUnknown
Objects=GroupAgents, GroupPlaces
Subject=DNAction

(ER# 79549748)

Found In:  7.2.002.05 Fixed In:  7.5.000.20

Current Agent state requested by statistics having AgentStatus subject will be shown as Monitored after an agent has been disabled in Configuration Server and before the start of Stat Server or at any time during normal work. This Monitored status should not be viewed as the agent's actual status, but rather a sign that Stat Server is continuing to monitor the object. The actual status will be shown after the agent becomes enabled in Configuration Server. (ER# 51946201)

Found In:  7.2.002.05 Fixed In:  8.0.000.22

When configuring stat types for Open Media statistics, be careful to set the MediaType attribute correctly. Stat Server does not process dynamic changes to MediaType. If you need to change the MediaType value, do one of the following:

  1. Restart Stat Server after making the change in configuration.
  2. Create a new stat type with the correct MediaType setting.
  3. Temporarily rename the incorrect stat type, correct the MediaType value, and change the stat type name back to the original name.

(ER# 38940783)

Found In:  7.2.000.10 Fixed In:  8.0.000.30

Keep in mind the following when setting the position-extension-linked option to no in an environment with the switches for which a single phones can be associated with multiple DNs (for example, Nortel Meridian and certain small NEC switches). Stat Server may report the Ready status for a place or an agent instead of the correct NotReady or ACW status when the agent is logged in at a position DN. (ER# 37055987)

Found In:  7.2.000.10 Fixed In: 

Genesys recommends that you avoid a configuration where multiple Stat Server applications write to the same Informix Stat Server database. With two or more such applications, one Stat Server application might inadvertently disconnect from the database to which the other Stat Server instance(s) writes. (ER# 36464797)

Found In:  7.2.000.10 Fixed In:  8.0.000.30

With the NEC-position-extension-linked configuration option set to yes, Stat Server calculates the ACWConsult statistic incorrectly when an agent logged in at a position DN starts after-call work for a consultation call that was established on the extension DN. (ER# 36348959)

Found In:  7.2.000.10 Fixed In: 

If an IVR performs a single-step transfer through a mediation DN and this transferred call is answered by an agent, Stat Server mistakenly increments statistics which calculate TransferTaken for this agent. This behavior is not apparent in scenarios involving two-step transfers. (ER# 99672)

Found In:  7.0.201.02 Fixed In:  7.5.000.20

After an agent logs in or logs out, Stat Server does not restart the calculations of statistics requested with the Selection time profile and LoggedOut mask. Instead, these statistics continue to constantly accumulate their values. (An example of the Selection time profile is 'SelectionTest,Selection' = '1'.) (ER# 25876291)

Found In:  7.0.200.07 Fixed In: 

When writing to the STATUS table, Stat Server sends a redundant Ready or NotReady status with zero duration given either of the following conditions:

(ER#s 75951, 75976)

Found In:  7.0.100.16 Fixed In:  8.0.000.22

Top of Page


Discontinued Support

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.


Windows NT operating system is no longer supported.

Discontinued As Of: November 2005

Stat Server 7.5 requires JRE 1.4 or higher for successful operation. Support for JRE 1.3 has been discontinued.

Discontinued As Of:  7.5

Support on the Solaris 2.6 and AIX 4.3 platforms has been discontinued.

Discontinued As Of:  7.5

Top of Page


Internationalization

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)


Top of Page


Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Deployment Guide first.

Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.

Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Technical Support website may 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.

Top of Page