Hi All,
I dont believe this is a Genesys issue but we are getting calls queueing on a line and once they reach an hour they are getting cut off. I cant see any setting that would do this in Genesys or Alcatel. I know it’s not much to go on but anyone have any ideas??
cheers
Tambo
Depending on the TServer and Stat Server version you are running, check your settings for options related to Call Cleanup and Stuck calls.
Regardless whether this is a TServer or PBX issue, why would you leave a call waiting on a queue for an hour? What is your Service Level goal?
I only build what they ask, lets just say the SLAs are a distant memory.
We’re on vers 8.0.002.18 for TServer and 7.6.100.14 for Stats server. There are no settings for calls at an hour in either ?!?
Does your IRD strategy has a limit of 1 hour (generally we set it to 9999 sec in routing bulls eye). Also, do the agents have the right skill to take the customer calls (I believe you have this scenario when agents are available and they are not getting calls).
If you see nothing wrong with skills and strategy, just recreate the same strategy (IRD does behave weirdly once in a a while)
Can you provide an excerpt of your TServer log showing when the call is geing cut off?
Hi,
cant get logs as cant actually see when they are getting cut off and by the time they get through we have missed the log time. 
in the target block at “target agent group” the timeout = v_waitime. I’ve looked through most of the strategy and cant see anything obvious.
problem is that telecoms and the switch engineers say they are fine so must be Genesys >
in the target block at "target agent group" the timeout = v_waitime.
What is v_waitime? A variable? what value should it has when the call flow gets to the target block?
only thing I can find is that variable v_waitime = UDta[WaitTime] but cant see what it is looking for ???
just checked and this variable is used in all of our strategies, so cant be this as it appears only to be happening to 1 dept.
The expression v_waitime = UData[WaitTime] means that an attached data named WaitTime must exists and I believe it’s being attached to the call by an IVR script or a previous routing strategy.
If you can provide TServer and URS logs at least for the time a sample call is queued if would be much easier to help you.
Also please check your TServer options. Look for call-cleanup section.
What is the next object on the red point? Do you have ACD on your OXE? how is the RSI configured on the OXE?