cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
479
Views
0
Helpful
1
Replies

CALL_HELD Event 10 with Reason codes other then 0

wfranklin
Level 1
Level 1

Hello,

 

We have Finesse and CUCM 11.5 and Verint 15.1  Verint reads incoming event/reason codes from Cisco and converts them to activities for users adherence feed.  We have most of it mapped and working correctly, but I'm trying to track down what scenario sends a 10+Not Ready Code(like ACW or our Claims work status).  It seems like if someone makes a call and puts in on hold, 10+0 is sent, but other times 10+not ready code is sent.  I've been running test scenarios by switching my status to claims work (pending) and putting calls on hold but it seems 10+0 is always sent in my tests, but going back through logs we have had scenarios where 10+not ready code is sent and I can't figure out why.  I've tried putting calls on hold, conferencing, but have not been able to generate anything other then 10+0.

 

Does anyone know what would cause a 10+not ready code to be sent instead of 10+0?  I'm trying to figure out how to map them so our adherence(and payroll) is correct.

1 Reply 1

Gerry O'Rourke
Spotlight
Spotlight
Hi,

I do not believe Not Ready Codes themselves will occur when placing a call on hold?
Is this CCE or CCX?
Some Finesse logs might be useful showing an example with and without.

When you do a consult transfer does the issue occur?
Its an example where a call is placed on hold "automatically" instead of manually - might be possible option?

Gerry