Hi, i have a situation where agent is not ready for reason(1) (is an example) and i need to put him not ready for reason(2), how can i do this ?
Avoiding the sequence not ready → ready → not ready because it can cause an inbound call to agent.
Thanks for any help !
Pachu
If You are using Genesys for routing please use verification_time options in URS.
Short description from documentation:
“A positive value is useful when it is possible for an agent to pass through ready
state in a transition between ending a call and making himself unavailable by a
manual command. This option specifies the time, in seconds, that must elapse
after an agent ends a call before the agent is reported as ready to receive calls
again.”
This options works only if CheckAgentState is true.
Paul
Agreed, verification_time would be good here. It will allow your agents to pass through the ready state and not be selected for a call.
Well if you are still using alcatel OXE on the RSI you can put a pause between calls so agent can go ready for an instant and then go to not ready.
but one question, what happen if you go from notready(1) to notready(2)? I believe it should work…
On Alcatel it dosen’t work - 
tried it - not with software 6.1.1 and PBX defined reasons. If You switch off PBX reasons everything works fine - You can go from not ready(reason=xxx) to not ready(reason=yyy) but when You define withdrawal type > 1 on Processing Group You encounter problem described by Pachu.
I try to get more info to this problem, currently we are waiting Alcatel’s guy to add the reasons to OXE, i try send two not ready in a row but without reasons (Activex) and i get (on the second) a AgentNotReady event but with a “Legal Pause” in extension or something like that…
I still get error if i use the TExtension.TSetReasons, i try it with a list of one pair and “ReasonCode” as key and 1 as NumValue before call TNotReady
Im wrong ?
Will not work the reasons of the Processing Group on the OXE. Genesys can’t use those. So it will be useless apart from confusing the agent when looking his phone screen.
On CME go to action codes, here create for example
Lunch with value 1
Break with value 2
etc
See attached picture
Then use the code i gave last time on your previous question about this.
It should work.
What error do you get?
Hi Cav, sorry the delay to respond i was busy in other issues.
I try your code and i think it works… but im not sure.
I attach the image of the log of changing the reasoncode, but this are my doubts:
I have no idea how are the parameters in configurationserver or in the OXE, i really dont know if PBX reasons are on or off the only thing i know is Alcatel´s guy tell me he has to add to OXE the reasons, i have to pass the list of reasons and he is going to put them in the OXE…
Other things…
The WorkMode = AutoIn, and the GCTI_INFO_STR = legal pause what this mean ???
Its right, its wrong ?
Normally when going NotReady i receive:
Extensions → ReasonCode = 0
wich i see diferent to receive:
Reasons → ReasonCode = 0
Why the difference ?
…
Thanks!
Pachu
The log
Legal pause is NotReady triggered by the agent on OXE language.
It’s ok.
As said, OXE Not Types will work ONLY if you extract statistics using CCS (Call Center Supervisor) from Alcatel PBX directly. This are not reflected on Genesys under any circumstance. No CSTA integration about this.
The only reason i will think about it is that you have an Alcatel CCD backup in case Genesys goes down, that if you are using CCD agents and not RSI agents. If using RSI agents i don’t see why to configure it.
Just in case,
CCD Agents = Pilot > Queue > Processing Group > CCD Agent
RSI Agents = Genesys > RSI > Processing Group > Genesys Agent
It’s a licensing issue.
Regards
Hi,
PBX NotReady reasons work very well with and without RSI ( using Genesys). They are reported through ReasonCode and GCTI_NOT_READY_ACTIVATION, can be seen in CCP and reported using filters. They can be used when there is no need for CTI console.
Hum, according to Genesys directly Reason Codes doesn’t work with Genesys.
Weird, will try on my lab
One more thing I forgot to add both keys are from Extensions not Reasons
Did not understand…
With every request send to TServer You can attach key-value pairs in 3 different places - UserData, Reasons, Extensions. For switch reasons to work with A4400 You must add following key-value pair: “ReasonCode” with value ( 0..9 ) to Extenions not to Reasons or UserData.
And with this wil be the same as if agent press the reason code on his phone? May be able to extract data from CCS too?
Im lost with the Reasons, i dont understand why are they in several places…
As always ask…
There is some doc where this things are explained ?
No, there is no document.
They doesn’t exist in many places.
The reasons are nothing more than KeyValue Pairs. Where you attach them makes the difference, always will finish reflecting the agent but will make different stuff on the DN applied.
Regards
Yes - that’s correct