Janine,
Need your expert advice on this issue. We are getting "no resource" errors on the VXML logs on a speech input element. How do we find out if this is a network error or mismatched grammar or ASR purely running out of licenses? I know that we can put the VXML Gateway into extended logging to figure out the exact cause. Could you send me the commands as to how to put the Gateway into the extended logging mode. Secondly, If we put the a Production VXML Gateway into extended logging mode, will it cause any additional gateway delays. Thank you for any suggestions you may have. Not sure which one of the following commands will work best:
MRCP:
MRCP client session
MRCP client error
VXML:
debug voip application vxml error call
debug voip application vxml trace
debug voip application vxml log
