I have a problem, i can’t configurin the input box in composer 8.1. I need that the locutions are dinamics and composer read the wav for the gax,
In gax, I created audio Resources and in composer I have a url when the wavs are, but I don´t know where gax guard the audio resources, we can help me!!!???
Try to read the documentation or use little bit effort
ARM has no URL by default, ARM just saves the announcement and music under specific folders (configured within arm section on gax application object). These folders (for announcement and music) has to be “mapped” from any web server (Tomcat, IIS, Apache, etc.). This URL you should use within Play Sound block as the ARM Base URL parameter.
The requested URL from Play Sound block is build as following:
the path is: “ipGAX/c$/GCTI/GenesysAdministratorExtension/arm/target/music/101900030.wav”,
in the documentation appears that this is the path where the music resources are published with the GAX :S
I see the wavs in this rute but the composer can`t see it.
No, I Kubig copy theory as calling utterances from the block .
In the Genesys’s documentation does not write anything for the published in the IIS,also the composer runs on a tomcat .
For the GAX is that the wavs has publish in the ISS.
You know you can configure IIS to use Tomcat to provide dynamic content, right? And leave IIS to do the static part? You need to learn a little bit more on the software you are using. Web components are more than just install and go
In the Genesys's documentation does not write anything for the published in the IIS,also the composer runs on a tomcat .
For the GAX is that the wavs has publish in the ISS.
You are not right:
Composer is not running on Tomcat or IIS. Composer is just a developer UI (plugin to Eclipse studio), where you can develop your SCXML or VXML applications and then deploy them on IIS or Tomcat
It stands for reason that if the wav files are generated locally they have to be published as to be available for using from “anywhere”. So, from my point of view, it is not necessary to document this as this is logical step within the deployment.