acd 8.0.8.8

[james1982]

hi

have an issue!!!

3300mxe clustered network, with acd configured.
Basically the ACD2000 logout agent no answer timer in the cos for the agents is been ignored.

I.E a call comes in rings on an agent, the ACD2000 logout timer is set for 15secs, ive sat there and the call wont logout the ext, it just rings and rings.

Has anyone else seen this on 8.0.8.8????????

Thoughts? only thing i can think of doing is data save data restore?

 

[kwbMitel]

Is this the only agent logged in?

What is the status of the option for Logout of last agent?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[james1982]

no theres 20+ agents logged in and available?????????

it doesnt log any of them out..........

 

[kwbMitel]

Is the call being presented to the Agent via a PATH or by some other method?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[james1982]

yes the call is been presented via a path...

 

[kwbMitel]

Some COS options are based on the calling device and some the called device.

I am unsure which applies in this case.

I suggest you check the timer on the trunks COS and make sure it is not set to zero.

Is there anything in your programming that would prevent the logout of the agent?

This is one of those things that just works. Never had an issue with it.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitel100]

The way round this is to ensure that you first RAD is set to a timer shorter that your logout timer.

So if your logout timer is set for 15 Secs, set the RAd to play at about 10 secs.

I hope this info helps.

__________________________

There is no 'I' in 'Team'
__________________________