Hi,
In the classroom, error.noresource is the 'generic' (not at all useful) error that the VoiceXML gateway returns when there's any kind of ASR problem with a grammar. It also occurs if the gateway times out waiting for an HTTP response (Media server slow to return a value, Vxml Server slow to return the next VXML page).
In your log, it looks like perhaps the gateway is timing out waiting for a reponse or a connection to the ASR resource.
Have you tried changing the VXML Gateway CLI to increase the MRCP timeouts, or the HTTP timeouts?
This is the amount of time the gateway waits for a response from the ASR:
mrcp client timeout connect 10
mrcp client timeout message 10
I've seen this occur in class during app development if the ASR can't retrieve (or times out retrieving) an external grammar, of if the grammar it retrieves is not valid.
Since this only happens occasionally, I'd guess it's a timeout of some sort (or possibly a load issue on the gateway).
It would be good to know whether this always occurs at the same place in the Studio application (ie, there's a bad or missing grammar file), or if it's random.
Do you know if the Studio application is changing the 'fetchtimeout' timer? This timer tells the gateway how long to wait for the next document to be retrieved.
You can search (using Notepad++) the VXMLServer/applications/<appname>/ folder for the word 'fetchtimeout'.
If it's not set in the application , then you CAN change the response timeout to a larger value in the gateway CLI (unfortunately, this will be overridden by any settings done in the Studio application):
http client connection timeout 10
http client response timeout 10
There might also be a way to configure the ASR to wait a little longer if it's loading an external grammar. Something similar to the 'fetchtimeout' timer. But, if you're not seeing any errors in your MRCP logs (on the ASR server), then the error's probably on the gateway side of things.
Janine
