Jump to: navigation, search

8.5.102.22

Stat Server Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
07/05/16 Hot Fix X X

Helpful Links

What's New

This release includes only resolved issues.



Resolved Issues

This release contains the following resolved issues:


Stat Server now correctly increments the following statistic in scenarios when there exist multiple instances of action type in MainMask and all those actions instances end:

Category=MaxTime
Subject=AgentStatus

(SS-6882)


Stat Server no longer terminates unexpectedly in scenarios associated with additions/removals of multiple Database Access Point (DAP) objects. (SS-6875)


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)

(SS-6874)


Stat Server no longer terminates unexpectedly upon receiving an event from Interaction Server in scenarios related to corresponding place removal in configuration. (SS-6844)


Stat Server no longer computes an incorrect status for multimedia agents after reconnecting to Interaction Server. (SS-6796)


Stat Server no longer intermittently terminates unexpectedly in the following scenario:

  1. An agent-login is removed from the configuration, so that no more notifications come for the agent X, associated with that agent-login. This might happen, for example, when the permissions are changed to No Access on the agent-login object.
  2. One or many agents X1, ..., XN log in into DNs.
  3. Agent X is removed from the configuration.
  4. Call activity takes place on agents X1, ..., XN.

(SS-6697, SS-6694)




Upgrade Notes

No special procedure is required to upgrade to release 8.5.102.22.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on July 5, 2016, at 18:32.