Hello there,
When trying to identify the Mandatory account on the Nice Perform 2 portal from a remote desktop (site 2), an authentification problem occurs. It's working fine on the site 1 for all the desktops.
That's not a multiple site configuration because we don't need it.
Both of them are...
Fixed.
The customer did not follow what I told him in the screen agent installation : "CLS initiates connection" and not "Screen Agent initiates connection".
Bye
Hi all,
Since 2 weeks, we can't record screens with our Nice Perform II.
It was working well but still 2 weeks, it did not.
We deinstalled MML then reinstall it but screen recording still fails.
If my rule is dedicated to voice only, it works.
The voice recording is OK, only screen recording...
Hi,
Well, in order to fix everything and following what you told me about the unique agent username (windows username) for the screen agent identification method, I've done it.
I deinstalled screen agent and choosed unique agent username method for the new screen agent installation.
It works...
No, I did not at the same time, of course.
But I've done it (last week) with the same agent (ROD user) but at different time to check the fact that even if I'm using another computer, I can logged into the system because of my unique O/S login ID (Windows login) and Agent ID (Telephony - Avaya)...
First, thanks for the time you're giving me.
Well, I'm using an association between the O/S login ID (Windows login) and a Agent ID (Telephony - Avaya) in the User Administrator for each Nice Agent I've created.
On each computer registry, I've added 3 differents Agent ID because 1 computer is...
Hi all,
Well, I have some errors regarding my screen recording and the channel mapping of it (I think!).
In order to use a digital matrix for the voice/trunk recording of the Nice Perform 2 solution, I changed the option ReadMappingFromFile = Yes (RCM Configuration of the CLS Server).
I did...
In addition:
In the Avaya TS Spy tool, there is no Agent Login/Logout events with AgentID, only events about deviceID xxxx (station/extension) I've added the "nicecti" group!
(The TS Spy tool displays all the events
that were reported by the Avaya CT/AES TSAPI server)
Hi,
First, thanks for your help because Nice support did not!
Well, I've already add station & vdn numbers in the "nicecti" group but I did not get any Agent Login/Logout events (that's why I thought something missing in the "nicecti" group).
I've put the right AgentId on the ROD desktop and...
In addition:
I added the Hunt Group (also called Skills) extension numbers in the "nicecti" group but the error is still the same:
"CMonitor::GetDeviceType - Failed to get device type for device xxxx 4 times"
Help, please ;)
Hi everybody,
Well, I'm stuck and the Nice support didnt't enough help.
In an Avaya CT 1.3 integration, I need to identify my ROD users with AgentID (it works with Extension but that's a free setting call center) but when adding such ACD object in the "nicecti" group, I have trouble in the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.