Genesys Cloud - Main

Hello there,

We have some clients alerting us that some agente are receiving the following error message:

"You are using an outdated signalling service. Contact the Administrator"

Any clue about this message?

Regards,

#Telephony

------------------------------
Mario Sanchez
Servicios en Tecnología de la Informacion SETEINFO del Ecuador C.A.
------------------------------

Hi Mario,

I saw this with one user, but it only happened once. We had logging running, but it had been left on for days and was eating up resources. The only thing I could gather from the logs were some DNS resolution issues. I don't know if that was related or if we just overloaded their machine and this was a resource issue.

With that being said, I believe the root cause of this message is due to the deprecation of long polling (see below). Something is likely causing websockets failures and it cannot fallback to long polling.
https://help.mypurecloud.com/articles/deprecation-long-polling-for-purecloud-clients-and-network-configurations/

That's just my guess. I'd try to grab some logs and open a ticket if it becomes problematic.

Thanks,

------------------------------
Daniel McLeod
Qsect LLC
------------------------------

Thanks Daniel,

Will keep an eye on this issue.

Regards,


------------------------------
Mario Sanchez
Servicios en Tecnología de la Informacion SETEINFO del Ecuador C.A.
------------------------------

Original Message:
Sent: 05-28-2020 12:03
From: Daniel McLeod
Subject: Outdated signaling service message

Hi Mario,

I saw this with one user, but it only happened once. We had logging running, but it had been left on for days and was eating up resources. The only thing I could gather from the logs were some DNS resolution issues. I don't know if that was related or if we just overloaded their machine and this was a resource issue.

With that being said, I believe the root cause of this message is due to the deprecation of long polling (see below). Something is likely causing websockets failures and it cannot fallback to long polling.
https://help.mypurecloud.com/articles/deprecation-long-polling-for-purecloud-clients-and-network-configurations/

That's just my guess. I'd try to grab some logs and open a ticket if it becomes problematic.

Thanks,

------------------------------
Daniel McLeod
Qsect LLC
------------------------------

If it helps I've seen this on a user's machine and it came up when a GPO forced their proxy to be turned back on.

------------------------------
Vaun McCarthy
NTT New Zealand Limited
------------------------------

Original Message:
Sent: 05-28-2020 16:29
From: Mario Sanchez
Subject: Outdated signaling service message

Thanks Daniel,

Will keep an eye on this issue.

Regards,


------------------------------
Mario Sanchez
Servicios en Tecnología de la Informacion SETEINFO del Ecuador C.A.
------------------------------


Original Message:
Sent: 05-28-2020 12:03
From: Daniel McLeod
Subject: Outdated signaling service message

Hi Mario,

I saw this with one user, but it only happened once. We had logging running, but it had been left on for days and was eating up resources. The only thing I could gather from the logs were some DNS resolution issues. I don't know if that was related or if we just overloaded their machine and this was a resource issue.

With that being said, I believe the root cause of this message is due to the deprecation of long polling (see below). Something is likely causing websockets failures and it cannot fallback to long polling.
https://help.mypurecloud.com/articles/deprecation-long-polling-for-purecloud-clients-and-network-configurations/

That's just my guess. I'd try to grab some logs and open a ticket if it becomes problematic.

Thanks,

------------------------------
Daniel McLeod
Qsect LLC