Good afternoon everyone!
I'm wondering if anyone has extended the 'you are Number1 in Q' wav file to a longer announcement?
We have a rather long disclaimer message I was hoping to put right before the 'Number 1 in Q' message and I am finding that after it plays and I route to my CallbackQueue app I receive the dreaded Unable to retrieve GUID status. Almost like the servlet is expiring in a very short time just in this part of the call flow.
If I keep the message small I don't get this error, so I am assuming there must be some timeout somewhere that I'm missing. I tried breaking the announcement up into smaller chunks and added a Get_Status call to hopefully keep it alive, but not much luck.
10.129.172.71.1488909026481.455.CallbackQueue,03/07/2017 12:50:28.012,Get Status_01,enter,
10.129.172.71.1488909026481.455.CallbackQueue,03/07/2017 12:50:28.012,Get Status_01,custom,Callback_Get_Status,ELEMENT_ENTRY
10.129.172.71.1488909026481.455.CallbackQueue,03/07/2017 12:50:28.075,Get Status_01,element,warning,doDecision- "Error: Unable to retrieve GUID status" returned from sending Callback_Get_Status request to CallbackServlet
10.129.172.71.1488909026481.455.CallbackQueue,03/07/2017 12:50:28.075,Get Status_01,custom,Callback_Get_Status,ELEMENT_EXIT
10.129.172.71.1488909026481.455.CallbackQueue,03/07/2017 12:50:28.075,Get Status_01,exit,error
If I look at all of the call back apps combined and the reporting server I can track my GUID all through the call. I'm just not sure how it seems to be getting lost.
Thanks for your help!
The CallbackEntry app's SetQueueDefaults element, has a configurable timeout that has to be longer than the audio played in the BillingQueue app. But, that doesn't seem to be your problem.
Is your CallbackQueue node going thru the UpdateStatus_01 node (with Setting value: AddToQueue) before executing the GetStatus_01?
Can you post the activity log from the CallbackWait and CallbackQueue app for a call that experiences the problem?