GAD Status issue?

[starscream2009]

GAD status doesn't go from ready to not ready after each call,  it stays in the ready state and i am getting calls.
I have one instance of GAD which is working fine and second instance is configured in the same way but this one doesn't work as expected. i have checked the options tab of new Gad and it has the same config as new one, i have verified the custom.xml file and web.xml too they are same
can any one please suggest me something

[cavagnaro]

Check after call work for those agents

[starscream2009]

We do not use action code folder from CME, any other way we can verify?

[cavagnaro]

??  Please read your TServer deployment guide, I'm not talking about those.

[Steve]

After Call Work or wrapup time is normally set against your ACD queue in the switch config, and applies to all agents who login to that queue - get your switch (PBX) people to check.
Genesys allows this to be overridden on a per agent basis, you can set wrapup for each agent when you set thier ACD login in CME - check the settings here too.

[starscream2009]

we have configured the second instance in the same way as the first instance
where as first instance works fine with out any probs, the first instance  places the agent in not ready state when call is disconnected

[RoboH]

Hi

In this case the only trouble shooting can be to execute the same test for GAD1 and GAD2 and compare the TServer logs after call is finished. There must be requestAgentNotReady from some Genesys component after call is finished. If you find this request in GAD1 you can be 100% that the NotReady comes after iniciative of GAD. But if you will not find it and Agent is going to Not Ready, it has been set by TServer/Switch action.

Then it isn't GAD issue.

Robert