Search results for query: *

Starting last week, we started having error messages when changing some agent skills. We got a message saying the feature wasn't enabled in the switch. I can change the agent skills in CM, but then of course, the reps have to log out and log back in.

We have agents using OneX agent through a rap device. They're on auto answer. If they don't restart the phone and/or the rap a few times every day, the quality of service is terrible. If we use physical phones, they can't use auto answer with a rap. Has anyone else run across this?

Has anyone else had this problem? This is what we get on our display when we make an outbound call: Eap7IFNFoJFbP You actually can hit redial and it dials the actual number, but this has been going on for 3 months and Avaya points to Ingate, who has no idea what they're talking about. It's...

Yeah we thought it was odd, which is why we decided to try it in custom reports after it failed in report designer.

Actually, I'm working with someone who does custom reports professionally, and knows there's a bug in this version. So I'm not looking for help in correcting the query, because we tried it in both report designer and custom and we know it's correct. I'm really just looking for someone who has...

No that wasn't all there was to it - but that was the database item in question that it was getting the syntax error. Since it's actually IN the database, it shouldn't be getting an error. From what someone told me, this is a known bug in my version of CMS (16.2), but I need the patch and my...

The query was: sum(TI_AUXTIME10)

Do you use wallboards or a reporting software? If so, then it's fairly easy to see who is still logged in. But the bottom line is - under variable closing hours, the last agent logged in has to be responsible for making sure everyone is logged out. Unless you want to put a TOD step, say after...

In both report designer and custom report options, I'm getting a syntax error (despite double checking the query). I was told this was a bug and there was a patch. My vendor says there isn't. Does anyone know of this issue?