Is there any way to identify further what the error below means ? and what could be causing it.
We have an integration with Genesys for Routing calls.
I have looked at the TSAPI reference guide can't find something related.
Any help would be appreciate it.

12:53:10 ERROR:CRITICAL:TSAPI:TSERVER:ClientHandler.cpp/433 11 PROCESS PKT[0]: Received message from 10.248.xx.xx is too large, rcv_count -1711079442 bytes 900 message class 25974 message type 29554
12:53:12 ERROR:CRITICAL:TSAPI:TSERVER:ClientHandler.cpp/433 11 PROCESS PKT[0]: Received message from 10.248.xx.xx is too large, rcv_count -1711079442 bytes 900 message class 25974 message type 29554
12:53:15 ERROR:CRITICAL:TSAPI:TSERVER:ClientHandler.cpp/433 11 PROCESS PKT[0]: Received message from 10.248.xx.xx is too large, rcv_count -1711079442 bytes 900 message class 25974 message type 29554
12:53:17 ERROR:CRITICAL:TSAPI:TSERVER:ClientHandler.cpp/433 11 PROCESS PKT[0]: Received message from 10.248.xx.xx is too large, rcv_count -1711079442 bytes 900 message class 25974 message type 29554
12:53:19 ERROR:CRITICAL:TSAPI:TSERVER:ClientHandler.cpp/433 11 PROCESS PKT[0]: Received message from 10.248.xx.xx is too large, rcv_count -1711079442 bytes 900 message class 25974 message type 29554
12:53:21 ERROR:CRITICAL:TSAPI:TSERVER:ClientHandler.cpp/433 11 PROCESS PKT[0]: Received message from 10.248.xx.xx is too large, rcv_count -1711079442 bytes 900 message class 25974 message type 29554
12:53:23 ERROR:CRITICAL:TSAPI:TSERVER:ClientHandler.cpp/433 11 PROCESS PKT[0]: Received message from 10.248.xx.xx is too large, rcv_count -1711079442 bytes 900 message class 25974 message type 29554
12:53:25 ERROR:CRITICAL:TSAPI:TSERVER:ClientHandler.cpp/433 11 PROCESS PKT[0]: Received message from 10.248.xx.xx is too large, rcv_count -1711079442 bytes 900 message class 25974 message type 29554
12:53:27 ERROR:CRITICAL:TSAPI:TSERVER:ClientHandler.cpp/433 11 PROCESS PKT[0]: Received message from 10.248.xx.xx is too large, rcv_count -1711079442 bytes 900 message class 25974 message type 29554

I am afraid I don't have the means to investigate the message class and message type values to tell you if there is any useful information... If you had TSAPI tracing on you could see if they were route request related, as you would see no response behavior out of TSAPI. If they are requests that the application is making, I am unable to unravel any meaningful information out of the messages.

My only suggestion is that because this is probably a field site, is to open a Avaya Global Services support request and get them to investigate... but I anticipate a stock reply that the application's message is too large, although with TSAPI I am not sure how you can create a message that is too large for AE Services to accept..

Thank you John for your reply, I will open a Avaya Global Services support request.

Hi Julio,

Have you got that problem resolved?
What was it?
I'm having the exact same message.

Thanks,

Marcos