" /> CCP freezes after disconnect - Genesys CTI User Forum

Author Topic: CCP freezes after disconnect  (Read 3349 times)

Vic

  • Guest
CCP freezes after disconnect
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Hi, here is a brain easer for all of you:

we have Site A and Site B with all of Genesys on SITE A and CCP on Site B.

When we experience a network problem between Site A and Site B, CCP on Site B disconnects. When we try to reconnect, CCP@Site B freezes BETWEEN Login Screen and Select Stat Server screen.

Trying to start CCP on another PC on Site B, connecting to config server on site A and Stat Server on site B causes that CCP freeze as well.

CCP on Site A has no problem logging in and connecting to Stat Server on site B, yet trying to get any CCP@Site B to connect after that forces all of them to freeze between login and select statserver screens.

Here are some of the things we tried, which would sometimes work and sometimes wouldn't:

1. rebooting configserver: works sometimes
2. rebooting PC with CCP on it: never works
3. starting CCP on another CCP on site B: never works
4. rebooting statserver: never works
5. renaming CME template: sometimes works
6. moving configserver from site A to Site B: does not work
7. delete workspace.stg: worked once

We are using: CCP 7, StatServer 6.5, ConfigServer 7.0

Any clues?


sai

  • Guest
CCP freezes after disconnect
« Reply #1 on: January 01, 1970, 12:00:00 AM »
Hi,Vic.
Where is your DNS? Are you check DNS or network timeout on SiteB?

Marked as best answer by on May 02, 2025, 05:20:25 PM

Vic

  • Guest
CCP freezes after disconnect
« Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Undo Best Answer
  • Hi, Sai,

    thank you for your reply.

    Actually CCP does connect to configserver at site A, because I can see in configserver logs that it is logging in and getting some info. Unfortunately it stops getting info in a middle of it, and just freezes.

    According to the logs, CCP does receive info from configserver, but not all of it.
    So it is not DNS problem, but configserver problem, right?