Dear ED team,

I would like to ask your help with the following configuration of Play & Collect:
- Plays announcement - "Choose 1,2 or 3 or wait for agent" - done
- Wait for 1 digit from the caller - done
- if I set the Timeout attribute of Play & Collect (5 sec) - if the caller does not push any button for 5 sec that cause the following:
* caller can push anything after the 5 sec nothing will happen
* the workflow stops there and never will go on

I would expect in this case the flow goes on and the Play&Collect OutputSchema:digits would be empty.

Thank you in advance for your help!

Kind regards:

Katalin Orban
korban@avaya.com

Hi,

I executed the similar use case, start-->Make one party call-->play and collect-->end
I had given number of digits as 2 ,termination key as # and timeout of 5 seconds.
After making the call, i heard the announcement and I didnt entered the digits, after 5 seconds, the instance is completed and the status form the play and collect task says:
{'ucid':'00005000291486366508','status':'TIMEOUT','digits':''},

We might need to look at logs as to whats happening in the setup. Could you please share the logs.
Enable logging on platform
ce dlogon

Enable logging on ED
ce dlogon EngagementDesigner

Run this tool,
ce-report

The above would generate the file containing all the logs, please attach .

Thanks,
Rajesh

Hi Rajesh,

is that possible that it is working in your latest not-released version but it is not working in Version 3.2.0.1.00013?

I just asked this because we were facing another 2 issues which are known issues, fixed, but not released yet and we are going to get a patch with these today or tomorrow (discussed with Prakash Natarajan).

If this is another known-fixed-not-released-yet issue than I would ask the patch with this fix as well from the ED team.

Thank you in advance!
Kind regards:
Katalin Orban
korban@avaya.com

Hi,

Am not sure on issues you are talking about, but i dont think there was any change to play and collect on timeout.
Need to look at the logs on your system,

On ED logs, cd /var/log/Avaya/services
vi EngagementDesigner.log

you should see the below line after the timeout,

2017-02-06 17:31:16,998 [SipContainerPool : 3] EngagementDesigner FINE - EngagementDesigner-3.2.2.0.9000 - Notification received for UUID: f84a66fb-cf95-4017-8455-7385874859b8 ucid: 00005000301486382467 received digits cause: TIMEOUT

Thanks,
Rajesh

Hi Rajesh,

I have this instead:
2017-02-06 10:42:42,397 [pool-96-thread-7] response.ProcessHttpResponseUtils ERROR - [M:processHttpResponseForGetData][T:12345678]. Exception: Error occurred extracting data - "No data found."
2017-02-06 10:42:42,397 [pool-96-thread-7] EngagementDesigner ERROR - EngagementDesigner-3.2.0.1.00013 - Invalid request, ERROR
2017-02-06 10:42:42,397 [pool-96-thread-7] EngagementDesigner ERROR - EngagementDesigner-3.2.0.1.00013 - The request failed response = ERROR
2017-02-06 10:42:56,485 [pool-96-thread-4] EngagementDesigner ERROR - EngagementDesigner-3.2.0.1.00013 - java.lang.RuntimeException: Error executing mapping from out.put:digits to CallerData:ServiceID. JSON does not allow non-finite numbers.

Kind regards:
Katlain Orban
korban@avaya.com

Hi Please share your wfd and logs to debug more on this, send complete logs, using ce-report tool


Also enable finest logging on ED and Breeze,you can do :


ce dlogon EngagementDesigner and


ce dlogon



And run your scenario, make a note of time , execute ce-report on breeze terminal, let us know the time when you executed the scenario.


send the log file which ce-report generated and will let you know our investigations.