Noinput timeout happen too soon with slow connection

[GoogleCodeExporter]

Steps to reproduce the problem
1. Speech recognition, with res_speech_unimrcp module on Asterisk
2. Try having a slow connection (I tested with Siphon, on iPhone, and WAP)
3. Set noinput timeout to at least 2 seconds
4. When you place a call and recognition starts, recognition fails very soon 
with a noinput timeout MRCP error code. Even if noinput timeout is set to 10 
seconds, it fails after a period between 500ms and 1500ms.

It happened even if you talked to the VOIP client immediately.
The exact same configuration was tested with a wifi connection and the system 
was responding very well, recognition worked very well and noinput timeout was 
returned after the correct amount of time when I was not talking.

It seems that if the speech server has to wait for too much time before 
receiving the first sound packets, it simply responds with a noinput timeout 
(which makes sense). But I'd like him to wait a bit longer, how can I do 
configure that?
I tried to check jitter buffers and packet loss. Each time it happened, no 
packets were lost or dropped, and jitter was at an average of 25ms, which seems 
fine.

I'm using Asterisk 1.6 with uni-ast-package-0.3.1.

Original issue reported on code.google.com by ehj...@gmail.com on 22 Nov 2010 at 10:36

[GoogleCodeExporter]

Reading the description of the problem, I don't think it's possible to alter 
this behavior from the client. What one can do if the server responds with 
no-input-timeout, when it hasn't received an RTP packet within 1 sec or so with 
no-input-timeout set to 10 sec.

1. Which MRCP server did you use.
2. Is it possible to provide a network capture made on the server side to 
observe all the packets and timings from the server perspective. Asterisk 
console output with debug logs enabled would be a plus.

Original comment by achalo...@gmail.com on 30 Dec 2010 at 3:25

• Added labels: Component-Asterisk, OpSys-Linux, Priority-Medium

[GoogleCodeExporter]

I have a complete access to the server and may change server configuration.

No-input-timeout is set to 8 seconds, and when the connection is good, 
no-input-timeout is correctly sent after 8 seconds.

MRCP server is Nuance Speech Server 5.1.

I'll send you the logs soon.

Original comment by ehj...@gmail.com on 4 Jan 2011 at 9:27

[GoogleCodeExporter]

any updates on this?

Original comment by achalo...@gmail.com on 15 Jul 2011 at 8:19

[GoogleCodeExporter]

Timed out.

Original comment by achalo...@gmail.com on 6 Mar 2013 at 2:02

• Changed state: WontFix