Just to add one more thing, when I was simply using the XML dialplan I didn't seem to have this issue. It may be an issue with my lua ivr script. Im just learning to program in lua and have hacked something together. So if you want to have a look maybe you will see an issue with it. http://pastebin.com/Bagn8ESS From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Glen Ganderton Sent: Tuesday, 13 September 2011 3:30 PM To: freeswitch-users@lists.freeswitch.org Subject: [Freeswitch-users] Speech Input Timeout issue Hi Guys, I am in the process of configuring an speech recognition IVR using freeswitch and nuance, with the module unimrcp to link them. This seems to be working fine, I have create a basic IVR script that works well however around 50% - 60% of calls fail with some sort of input timeout issue. Here is a few relevant lines of the log file for a successful call: 2011-09-11 09:07:18.017882 [DEBUG] mrcp_stream.c:382 Parsed MRCP Message [70] 2011-09-11 09:07:18.017882 [DEBUG] mrcp_client.c:1104 Signal Connection Task Message 2011-09-11 09:07:18.017882 [DEBUG] mrcp_client.c:974 Receive Connection Task Message [3] 2011-09-11 09:07:18.017882 [INFO] mrcp_client_session.c:504 Raise App MRCP Response 0xb7252778 <160> 2011-09-11 09:07:18.017882 [DEBUG] mod_unimrcp.c:3094 (ASR-16) RECOGNIZE IN PROGRESS 2011-09-11 09:07:18.017882 [DEBUG] mod_unimrcp.c:1488 (ASR-16) READY ==> PROCESSING 2011-09-11 09:07:18.017882 [DEBUG] apt_consumer_task.c:90 Wait for Task Messages [MRCP Client] 2011-09-11 09:07:18.017882 [DEBUG] switch_core_media_bug.c:360 Attaching BUG to sofia/internal/1000@10.3.5.80<mailto:sofia/internal/1000@10.3.5.80> 2011-09-11 09:07:18.690084 [DEBUG] mpf_timer_manager.c:180 Timer Elapsed 0xb7252d18 [1000] 2011-09-11 09:07:18.690084 [DEBUG] mpf_timer_manager.c:111 Set Timer 0xb7252d18 [2000] 2011-09-11 09:07:19.446976 [INFO] mrcp_client_connection.c:525 Receive MRCPv2 Stream 10.3.5.80:49844 <-> 10.3.15.180:6075 [136 bytes] MRCP/2.0 136 START-OF-INPUT 2 IN-PROGRESS Channel-Identifier: 160@speechrecog Proxy-Sync-Id: 0-160@speechrecog Input-Type: speech Here are a few lines for an unsuccessful call: 2011-09-11 09:07:44.605658 [DEBUG] mrcp_stream.c:382 Parsed MRCP Message [70] 2011-09-11 09:07:44.605658 [DEBUG] mrcp_client.c:1104 Signal Connection Task Message 2011-09-11 09:07:44.606901 [DEBUG] mrcp_client.c:974 Receive Connection Task Message [3] 2011-09-11 09:07:44.606901 [INFO] mrcp_client_session.c:504 Raise App MRCP Response 0xb72d8228 <161> 2011-09-11 09:07:44.606901 [DEBUG] mod_unimrcp.c:3094 (ASR-17) RECOGNIZE IN PROGRESS 2011-09-11 09:07:44.606901 [DEBUG] mod_unimrcp.c:1488 (ASR-17) READY ==> PROCESSING 2011-09-11 09:07:44.606901 [DEBUG] apt_consumer_task.c:90 Wait for Task Messages [MRCP Client] 2011-09-11 09:07:44.606901 [DEBUG] switch_core_media_bug.c:360 Attaching BUG to sofia/internal/1000@10.3.5.80<mailto:sofia/internal/1000@10.3.5.80> 2011-09-11 09:07:44.814845 [INFO] mrcp_client_connection.c:525 Receive MRCPv2 Stream 10.3.5.80:49845 <-> 10.3.15.180:6075 [141 bytes] MRCP/2.0 141 RECOGNITION-COMPLETE 2 COMPLETE Channel-Identifier: 161@speechrecog Waveform-URI: Completion-Cause: 002 no-input-timeout It seems to me the main difference is that in the successful call there is a timer that is set. Has anybody seen this issue or have any idea's on how to resolve it?