Actually, custom headers are added to the REST request instead of the request sent to the OAuth URL. Please provide us your WFD here.

Hi Yidi,

The vxml doc is built using the UTF-8 encoding.

Rgds,
Bill

Hi, You have to reboot all the servers in the cluster after you added/modified JDBC Sources. There is a message displayed on JDBC Sources page.

Rgds,
Bill

Screenshots of JDBC Providers and JDBC Sources configuration please. You may cover/erase sensitive info on the picture.

Hi Rangari,

What do you mean by "configured my database in Avaya System manager"? What type of DB server is it? Can you access it from other client, e.g. DB tools?

Can you please provide detail configuration information of your JDBC Providers and JDBC Sources? BTW, as shown on the error message window, you need to reboot all the nodes in the cluster after you configured/modified the JDBC Sources.

Rgds,
Bill

Hi Arjen, As I mentioned in the email, if you use ED 3.3, you need to uncheck the “Only allow secure web communications” checkbox in your ED Cluster settings. A reboot of all nodes in the cluster might be required once you made a change in cluster setting.

You are welcome. Have fun! We appreciate your feedback.

Hi Andrew, It works now after we fixed the configurations, but the speech server supports only one language, en-US. I created a simple WFD, testIVR, and tested it. The WFD I sent you last time has fr-CA prompt configured in its second IVR task and it is a language selection use case, so you would need to modify it.

Not likely, as no one would need MRCP without actually using VXML. The fact that you heard that error message is a good indication that AMS was not configured properly for VXML.

More screenshots.

Then you need to configure MRCP to use the same TTS server. Screenshots attached.

Do you have TTS server configured on AMS? Again, please try to have the Play Announcement and Play and Collect tasks work first in your setup if you know how to use them well.

Hi Andrew, you might need to modify the WFD to use TTS only as you do not have the pre-recorded audio file in your AMS.

That was built with 3.4 where the IVR task was moved to a separate task bundle. please try this one attached.

Hi Andrew, If you already had the "Play Announcement" and "Play and Collect" task working in your setup then you should be able to try the IVR task, which would do the similar things, e.g. play prompts and collect inputs, via VoiceXML. Otherwise, you need to make sure that you have Avaya Media Server and a speech server, e.g. Nuance, in your setup.
Attached please find a WFD example.