Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: sshrikant on March 08, 2015, 06:55:21 PM

Title: Can Genesys Data Mart report on Avaya Call Work Codes?
Post by: sshrikant on March 08, 2015, 06:55:21 PM
Avaya CMS can report on Call Work Codes entered by Agents during a call. This is done by pressing a programmed button and then entering a code corresponding to the type of calll such as "Complaint", "Order", "Inquiry" etc.

Can Genesys Data Mart access and report on these codes? Has any one done this?
Title: Re: Can Genesys Data Mart report on Avaya Call Work Codes?
Post by: cavagnaro on March 09, 2015, 02:33:49 AM
Chech TServer logs and you can create filters
Title: Re: Can Genesys Data Mart report on Avaya Call Work Codes?
Post by: sshrikant on March 09, 2015, 10:57:39 PM
What am I looking for? Is there any attached or data attribute that shows up? I could not see anything but that's probably my ignorance.

Genesys support says Avaya does not pass any information about Call Work codes to TServers.

Thanks for your help
Title: Re: Can Genesys Data Mart report on Avaya Call Work Codes?
Post by: cavagnaro on March 10, 2015, 01:31:17 AM
Check on the NotReady event any data on Extension attribute or UserData attributes.
Title: Re: Can Genesys Data Mart report on Avaya Call Work Codes?
Post by: cavagnaro on March 10, 2015, 01:31:39 AM
But if Avaya support already cleared you down...not much to do
Title: Re: Can Genesys Data Mart report on Avaya Call Work Codes?
Post by: mduran22 on March 12, 2015, 11:51:14 PM
That is not entirely true. Avaya does pass reason code number as an integer entered on the phone in attributereasons as 'ReasonCode'. Avaya doesn't pass any reason names that you can define in Avaya.

Also, Avaya doesn't automatically pass even the reason code when you go from aux to aux with different reason codes (unless you pass through ready in between). However you can set Genesys up to query agent states for changes to pick up aux to aux changes. Look in the TServer deployment guide for the section describing how to set this up.