AACC (SIP, CM) - Ready/Not Ready state

[maxtsvetov]

Hi!

We have AACC 6.2 SP5 with Avaya CM 5.2.1 , AES and SES.

Sometimes, mostly during high load, there is problem with Ready/Not Ready state.

Some agents receive calls from CDN when they are in Not Ready state,
on contrary some other agents don't receive calls in Ready state.

To solve the problems agents have to change their status to the opposite and back.

Maxim

[neumanna]

Hi,
having similar issues. Possible causes: not enough performant Agent PC, Agents phonesets just off hook - without active call - while in this moment the AACC is trying to present skillset call to agent.
May you compare RTD and AAAD status.
Have SR's opened for those issues. Issues still in SU05 RU1... lineup seen.
Best to escelate your events as well to Avaya.
BR Andreas

[ahmadty1984]

Hi!

We have AACC 6.2 SP5 with Avaya CM 5.2.1 , AES and SES.

Sometimes, mostly during high load, there is problem with Ready/Not Ready state.

Some agents receive calls from CDN when they are in Not Ready state,
on contrary some other agents don't receive calls in Ready state.

To solve the problems agents have to change their status to the opposite and back.

Maxim

seems this issue happen everywhere , i have the same did you manage to solve it ?

[bbcom]

I've seen this behavior as well

I have seen this behavior as well. A couple things I've learned on my own:

* if Agent Desktop PC loses network connectivity Agent Desktop will show agent still ready when CCMS does not.

* it appears (Avaya should confirm) that going Not Ready when a multimedia contact is up does not take affect until MM contact is gone. This means AAAD shows agent "Not Ready" when they actully in a pending state waiting for the active MM to complete, giving the appearance of receiving a voice contact when AAAD shows Not Ready. (think blinking aux button in Elite)