That error indicates that you have an <audio> tag without the required attributes (src, expr or stream). In order for an audio tag to function you have to specify the URL for that audio. Typically this would either be a src (statically defined URL) attribute or an expr attribute (dynamically defined URL). If you are just using Text-to-Speech only you should not be providing an <audio> tag. For example the following will throw a run-time error:

Thanks for your explanation, but I don't see any <audio> tags without the required attributes (src, expr or stream). Also, I used the "validate" button in Application Configuration and it didn't return any error for the URL below. Do you mind to take a look at the URL below and let me know which line number I should change? Thanks

The second <audio> tag does not contain any attributes. The sole purpose of the audio tag is to reference an external audio file, if that file is not available then the contents of the <audio> tag will be played as text-to-speech. However, in this case since you are only using text-to-speech the <audio> tag is not appropriate. Instead you should be using the <prompt> tag which is required in order to use the <say-as> tag. For example your code should look like this:

As we mentioned previously there are three sections in that link that follow this similar pattern of using an <audio> tag with no attributes for text-to-speech when a <prompt> tag should be used instead. You will need to correct all three sections for this application to execute correctly.

Thanks again, I was able to fixed it. One more question...I've noticed that the log entry shows full credit card number (please check below). Since we must be in compliance with PCI Security Council standards, we should not allow any sensitive data to be stored in the logs. We used <voxeo:logcontrol mode="disable"/> for this purposes, but I had to remove it because I was getting an error for this tag. Is there any solution you can offer us?

Yes we offer a similar approach using the <property> tag in VoiceXML. Here is the link to our documentation on the topic: http://www.plumvoice.com/docs/dev/voicexml:properties:logging. Essentially you will need to set a <property name="logging" value="private"/> at any scope where the data needs to be kept private.

We found another issue, it looks like our application stopped logging [session.id] and [session.telephone.ani] values. We use <var name = "fldSession" expr = "session.id" /> in global.vxml file. Can you please help to resolve this issue. Thanks

Could you provide us with a bit more context for this? It would be helpful to have some sample code as well as the expected / experienced results? It is difficult to determine the issue without these additional details.

You would reference the session.id within the VMXL application. Outside of that, you would use whatever value you stored the session ID in, which appears to be fldSession based upon the sample URLs we found.

Have you verified that you are sending the fldSession variable or have access to that variable (potentially via a session) to the script that is attempting to log the session ID? We would expect that fldSession would be correct if you are attempting to log this value within MainIntro.aspx.

Please check below the information from our debugger about the raw request we are getting from you when call starts. We don't see any session id in there. Can you please let us know where we should look for it?