Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IPOCC - Agent status (Telephony) problem 2

Status
Not open for further replies.

sstevancevic

Technical User
Aug 22, 2011
67
RS
Hi,

I have IPO 500 V2 R9.1.7 and virtual IPO CC 9.1.7. Agent status for Group 1 stops working after some time. Agent profile is used for all agents and it happens that some agents see Agent status and others not. When Administrator change something (turn in or turn off some privileges) in Agent profile it is going to make it work. Looks like a bug.
Has anyone had similar problems?

Thanks in advance,
Slobodan
 
I don't recognize having this issue.

Are you using the Web or Client UI?
Which element are you using to display the information?

"Trying is the first step to failure..." - Homer
 
I'm using Client UI and Agent status (AG) (Telephony):
Agent group:
- Group 1
Display content
- All agents
Number of columns
- Automatic

Call with double-click
 
I'm using the Agent Status (Team).

Is it set to only show "Present agents" or "All agents"?
Also the agent needs to have it's Authorizations set to be allowed to view the agents (or team) in question or preferably All.

"Trying is the first step to failure..." - Homer
 
It is set to "All agents"
Display content:
- All agents

Agent Profile - Authorizations
- All Agent are under Agent tab
- Group 1 is under Agent group tab
Is there anything else that needs to be included?

Is there anything under Agent Profile-Privileges that need to be included for using this feature?

 
Nothing special should be needed under Privileges.
Might be an issue with that element.

Try creating Teams and use the Agent Status (team) instead if it works better, I've only used that.

Meanwhile it might be worth to report the issue to Avaya to see if it's a known bug.

"Trying is the first step to failure..." - Homer
 
Probably might be an issue with that element, because for example, it works when the same agent log in at one pc and doesn't work when log in to other pc and when Administrator change something to Agent privileges, log in/log out an agent at pc where doesn't work, it starts working.

I'll try with Teams, it's a good idea.

Thank you very much for help.
Regards,
Slobodan
 
Let me know how it goes.

It could be a windows firewall issue or something the the local pc.

I have an issue where it doesn't display variables in the Client UI on some PCs, we're still trying to find out what causes it.

"Trying is the first step to failure..." - Homer
 
OK I will, but it is strange, because we nothing change on pc, only something on privileges and log in/out, start working.
 
Hi Janni78,

As I have promised, just to let you know that Agent Status (team) works without any problems. I solved my problem.

Thanks once again for help,
Slobodan
 
Thanks for reporting how the issue was solved.

If I get some time I'll try Agent Status (AG) in my system, might be a bug with that which need to be reported to Avaya.

"Trying is the first step to failure..." - Homer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top