Author Topic: OCS dials too quickly then stops  (Read 2901 times)

Alan Sharp

  • Guest
OCS dials too quickly then stops
« on: January 01, 1970, 12:00:00 AM »
Guys,

Have any of you who run OCS noticed a tendence to overdial for a while then stop dialling for 25 minutes in predictive mode? This is happening on a couple of our sites, Definity switches & completely seperate CTI environments. It seems to dial very quickly, with the result that it gets ahead of its target parameter (ie achieves say 15 seconds wait time instead of the requested 30 seconds), and then stops dialling until the measured value for the stat gets closer to the target value?

Wondered if any of you have seen this or been able to do anything about it...

Cheers
Alan

Vic

  • Guest
OCS dials too quickly then stops
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • There was an option for OCS that allowed you to set how often OCS updates its predictive algorithm statistics. By default it is set to 10 seconds. Try playing with it first.
    main_timer_interval is the option, and Genesys does not recommend changing it...

    What version of OCS are you using, and how many seats do you have?
    Does it happen all the time or only in specific situations?