set speech channel timeout to a more realistic value #68
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No one expects to wait 30 seconds for a response on their phone (because for example asterisk-unimrcp could not open a speech channel with the asr server).
In the real world, users will abandon an unresponsive system long before that.
A more realistic approach would be to set a minimum timeout to 2 seconds (or 1 second) allowing the next commands or the dialplan or the agi script (or agi-java) to transfer the call.
This can go unnoticed even from very experienced developers (real case scenario) for years (because no one expects that the default value of the minimum timeout of a real time system will be 30 seconds )...
So, my suggestion is 2 seconds of minimum speech channel timeout.