" /> Function 'JumpToStrategy' - Genesys CTI User Forum

Author Topic: Function 'JumpToStrategy'  (Read 4058 times)

This topic contains a post which is marked as Best Answer. Press here if you would like to see it.

James

  • Guest
Function 'JumpToStrategy'
« on: January 01, 1970, 12:00:00 AM »
Advertisement
I am using lots of 'JumpToStrategy' objects in my strategies, to reduce the number of route points required. I have just found what I think is a problem that everyone should be aware of.... If you save/resave a strategy to the config server, you need to also resave any strategy that uses the function 'JumpToStrategy' to jump to it. This (I think) is because the config server creates a new DBID for the object. Anybody else finding problems like this?

Katherine Locke

  • Guest
Function 'JumpToStrategy'
« Reply #1 on: January 01, 1970, 12:00:00 AM »
Hello James, we are using JumpToStrategy at our site. So far, we did nto encounter the problem you have mentioned so far. What version and platform of the configuration server and irserver are you using down there? There WAS a problem with the configuration server earlier in the year, I recall, when it limited strategy size to only 32KB. If your compiled strategy was more than 32K than if you ever had to reboot the configuration server you would need to reload ALL the strategies as well. Which brings me to the next point; I hope you are not using strategy loader to load the strategies, are you? KL

James

  • Guest
Function 'JumpToStrategy'
« Reply #2 on: January 01, 1970, 12:00:00 AM »
We identified the 32k limit problem, as we have some strategies that are around 90kb! We are not using the old loader. It seems that the problem occurs if you save your strategy to the config server, when you have calls being processed by the strategy...

Marked as best answer by on Today at 11:53:35 AM

victor

  • Guest
Function 'JumpToStrategy'
« Reply #3 on: January 01, 1970, 12:00:00 AM »
  • Undo Best Answer
  • From my experience, the strategy you have loaded to a config server would not be loaded by IR while IR has any active calls. In other words, the instance you have no calls in a queue, treated on this routing point , the new strategy will be loaded. I could not confirm the problem with strategy needing reloading in case a child strategy was changed. Vic