real time displays not populating

[phonetech2012]

Hi we are getting the following error when accessing real time reports directly from the CCMA server and any other pc on the network. When I restart the RTD service, reports work for a few minutes then times out again. Any ideas?

Last server contact: 12/3/2017 9:03:32 PM
The system could not retrieve any data from the server because either the server connection is down, or there are currently no agents logged in. If the server connection is working, then try launching the display again later.
Transmit Mode = Multicast & Unicast.Page 1 of 1

 

[yyrkroon]

Run the RTD from the server - if it works there - you have a network issue not propagating multicast traffic to the client. If it doesn't work on the server, it could be several factors.

 

[phonetech2012]

Thanks for the reply. We tried this right from the CCMA server and got this error message. I read something on Avaya saying this could be a windows 2008 issue. "Windows 2008 R2 WinAPI sento() function taking 180 seconds"
It seems to make sense with my issue because the reports stops updating after 4 minutes.

 

[phonetech2012]

Anyone else ever have this issue and resolve it without re installing everything?

 

[mlozoveanu]

Not too many options, unfortunately

AACC CCMA Real Time Displays are slow to launch, timeout, and do not update frequently

Doc ID: SOLN222041
Version: 1.0
Status: Published
Published date: 27 Feb 2013
Author: Daniela Castillo

Details
Real Time Displays stop updating every 4 minutes or do not launch at all.
Verified not a firewall issue
Server Audit performed
Missing correct version of cystal Reports and Service Pack 1
Corrected but did not resolve issue
Data is not being sent out from CCMS consistently

Problem Clarification
Escalated to Avaya Design - Issue Not Product Defect - Issue Found With Windows API (WinAPI sento() function call. The function all takes 180 second so several SDP threads get stuck.

Not an Avaya Product Defect

Cause
Windows 2008 R2 WinAPI sento() function taking 180 seconds

Solution
Rebuild Windows Server 2008 R2 with SP1 from other media as originally used and migrated AACC database