Janine,
Using IIS logs you can see which wav files are causing the 404s.
But not which application caused it.
So I 100% agree that we should be able to see this error in CVP Studio activity logs and error logs.
i.e. so you can be sure its the application you are debugging which is causing the 404 and exactly where it has the issue.
So the enhancement would be for CVP VXML server to log correctly the 404 error details.
This would be better than having CVP studio audio element having to play out audio before continuing.
i.e. as this could have a negative performance impact or delay in future elements.
But if 404 error logs is not be possible, then I 100% agree, this should be a non default option.
Summary of Enhancement
Log the 404 error logs with the wav file URL in CVP Studio application logs.
Have an option (checkbox) in the play media element to clear DTMF buffer (unchecked by default)
Have an option (checkbox) to play out media before preceeding to next element (unchecked by default).
Note: Last feature should only be added if CVP cannot log wav file errors correctly (which they do not do today)
Gerry
