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

Timeout in Application Transfer


Hi All,

I am facing a very unusual issue.  I have a series of applications that have been fully tested in a UAT environment.  I deployed the applications to our production environment and found that App1 worked but I got a timeout when the call transfers to application 2.

Thinking I had an issue with App2 I routed the DN to that app directly and it worked immediately.  I then changed application transfer in App1 or point to App3 and this also worked.  I also discovered that I can go from App 1 to App 3 and back to App2 and this is also working but I have tried everything and cannot go from application 1 to application 2.  I re-deployed the same code back to our UAT and there is no issue there.

Application 2 is getting stuck on a audio element ;blank' when source is application 1

The same element plays fine when the source is application 2 or called directly.  All projects have the same default audio path,

MY current workaround is that the call goes from Application 1 to Application 3.  I use a decision element to determine if the call has come from application 1 and if so I route to application 2.  This fixes the issue.  Interesting I also had to play a blank audio prompt in application 3 in order for this to work - otherwise the call timed out out again in application 2.  I tried playing the blank file in App 1 and routing to app 2 but that made no difference.  I am at a loss so if anyone has any ideas or has seen this before it would be greatly appreciated

This is running on CVP 10.  The first applications contains a web service to authenticate with a third party.

Thanks!

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:24:46.041,,start,source,BNK_LogonMenu

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:24:46.041,,start,ani,0xxxxxx8000

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:24:46.041,,start,areacode,NA

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:24:46.041,,start,exchange,NA

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:24:46.041,,start,dnis,48914

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:24:46.041,,start,uui,NA

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:24:46.041,,start,iidigits,NA

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:24:46.041,Blank,enter,

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:28:07.768,Blank,element,warning,A session has timed out after 3 minutes. This is most likely caused by a start of call class or action element at the top of the callflow not completing before the voice browser's fetch timeout occurred. To resolve it ensure this class executes in a timely manner or run it in the background. Session timeouts may also occur under high load or if there are issues with a load balancer or voice browser.

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:28:07.768,,end,how,app_session_complete

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:28:07.768,,end,result,timeout

10.187.2.75.1424669065604.182.BNK_MainMenu,02/23/2015 16:28:07.768,,end,duration,202

Same

10.187.2.75.1424669698506.186.BNK_MainMenu,02/23/2015 16:35:09.723,,start,source,BNK_BPAY

10.187.2.75.1424669698506.186.BNK_MainMenu,02/23/2015 16:35:09.723,,start,ani,0xxxxxx8000

10.187.2.75.1424669698506.186.BNK_MainMenu,02/23/2015 16:35:09.723,,start,areacode,NA

10.187.2.75.1424669698506.186.BNK_MainMenu,02/23/2015 16:35:09.723,,start,exchange,NA

10.187.2.75.1424669698506.186.BNK_MainMenu,02/23/2015 16:35:09.723,,start,dnis,48914

10.187.2.75.1424669698506.186.BNK_MainMenu,02/23/2015 16:35:09.723,,start,uui,NA

10.187.2.75.1424669698506.186.BNK_MainMenu,02/23/2015 16:35:09.723,,start,iidigits,NA

10.187.2.75.1424669698506.186.BNK_MainMenu,02/23/2015 16:35:09.723,Blank,enter,

10.187.2.75.1424669698506.186.BNK_MainMenu,02/23/2015 16:35:09.723,Blank,interaction,audio_group,initial_audio_group

10.187.2.75.1424669698506.186.BNK_MainMenu,02/23/2015 16:35:10.893,Blank,exit,done

1 Reply 1

Hi All,

I actually discover the issue.  I had a fetchtimeout set in Root Doc Settings to 30 instead of 30s.  I am not sure why this did not impact our lab environment though or why I could route back from App 3 to App 2 but it does fix the issue and I can reproduce it by adding and removing the s.