Closed kremio closed 3 years ago
After reading through the source code, I figured out that request-timeout
is not the appropriate setting to control the timeout in this case.
The list of MRCPv2 settings that can be set in a profile section in mrcp.conf can be found here app-unimrcp/ast_unimrcp_framework.c:process_mrcpv2_config
For this particular case, you can assign a duration in milliseconds to sip-t1x64
to control how long to wait before timing out the INVITE transaction.
Besides reading the source code, this article was very useful to figure this out.
May I suggest providing a more complete documentation about the supported MRCPv2 settings ? The usage manual makes no mention of them.
Feel free to close the issue if you wish.
Given your requirements, the best would be to set sip-t1x64.
If you use TCP as the SIP transport, then the client would return straightaway when the server is not available.
Hello,
I was testing the resilience of our system against different errors, and in a scenario where for some reason our MRCP server would not respond to an INVITE when establishing the MRCPv2 session, I noticed that whatever value I assign to the parameter
request-timeout
in mrcp.conf, the request timeout always occurs after about 30 seconds.Note that In the log trace below I have set
request-timeout
to 5 but I have tried with other values (10, 10000) and the effect is always the same.Can someone confirm that the
request-timeout
setting is being applied as expected on their installation?In advance, thank you.
Asterisk version: 17.4.0 Asterisk Unimrcp version: 1.7.0