Combination View Flat View Tree View
Threads [ Previous | Next ]
Hello,
 
Does anybody know how to get the reason code chosen by the agent for a Not Ready of Logoff state?
 
Thanks in advance,
 
Paulo Silva

Can you please clarify your question? Are you asking about the CTI protocol for setting a reason code when changing state to not ready? Not sure what Logout has to do with it.



Regarding the CTI protocol, you specify a reason code on the SET_AGENT_STATE_REQ message. See Chapter 9 of the UCCX CTI protocol section on Agent State messages.

Hi David,

Thanks for your quick reply.

I am talking about reason codes that you create in Desktop Administrator which the agent will be presented with in CAD when he chooses to go Not Ready or Logoff; these are custom codes that customers use to track agent activity. If these are setup, every time the agent attempts to go Not Ready or Logged Off, a small dialog pops up with a list of reason codes, forcing the agent to make a choice. Typicall codes: Break, Faxing, Lunch, etc

Thanks,

Paulo Silva

That is a CAD question unrelated to UCCX CTI protocol. CAD has an internal database for storing these codes.

Hi David,

Are you saying that the reason code associated with the current Not Ready or Logoff agent state is not avaible through CTI?

If so, do you have suggestion as to how i may get to it?

Thanks!

You could connect a UCCX CTI client in bridge mode and receive the agent state change event for the agent. This event contains the reason code.

Note that this only provides UCCX CTI reason codes per table 10-19. It does not provide the CAD reason codes.

You can also access the UCCX database AgentStateDetail table as specified in the UCCX database schema here http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/user/guide/uccx85dbschema.pdf . Accessing the UCCX database is outside the scope of UCCX CTI protocol.

Hi David,

Thanks for all your replies!

I am aware of the database approach, but was wondering if there was any other way to get to them.

Thanks again,

Paulo Silva