" /> Problems with the integrations gax and composer - Genesys CTI User Forum

Author Topic: Problems with the integrations gax and composer  (Read 4864 times)

Offline yolyoly

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
Problems with the integrations gax and composer
« on: September 22, 2015, 10:53:46 AM »
Advertisement
Hi,

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!!!??? :'(

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Problems with the integrations gax and composer
« Reply #1 on: September 23, 2015, 06:55:13 AM »
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:

"ARM Base URL" + "TenantId" + "AnnouncementID" + "PersonalityID" + "file suffix"

For example:

http://www.genlabdemo.com/1100110.wav

where:
http://www.genlabdemo.com = ARM Base URL
1 = Tenant ID (Environment, MT)
1001 = Announcement ID
10 = PersonalityID
wav = file extension

Offline yolyoly

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
Re: Problems with the integrations gax and composer
« Reply #2 on: September 24, 2015, 07:26:08 AM »
Good morning Kubig ,

It may be that I have not explained clearly, excuse me .

I have read the documentation and that's how I'm trying to find the audios. But for some reason composer can not reach them.

In composer show this error: "fetch_end Fail (Unable to retrieve fech content) file://path of wavs.."

I tried to start the Tomcat user with user admininstrador but neither works.

Thanks you

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Problems with the integrations gax and composer
« Reply #3 on: September 24, 2015, 07:54:03 AM »
It should be caused by incorrect configuration of the block. So, what path are you using for ARM audio within Composer?

Offline yolyoly

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
Re: Problems with the integrations gax and composer
« Reply #4 on: September 24, 2015, 08:24:47 AM »
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.

Offline yolyoly

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
Re: Problems with the integrations gax and composer
« Reply #5 on: September 24, 2015, 08:25:58 AM »
I 've checked the path used for composer in the vxml generated and this path is correct.

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Problems with the integrations gax and composer
« Reply #6 on: September 24, 2015, 08:27:06 AM »
Do not user path like that - use webapp, network share folder or local files.

Offline yolyoly

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
Re: Problems with the integrations gax and composer
« Reply #7 on: September 24, 2015, 09:12:39 AM »
Now we have solved the problem . The gax runs on IIS and we must publish the audio folder in ISS, for audio can be heard running the composer.

thanks you

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Problems with the integrations gax and composer
« Reply #8 on: September 24, 2015, 12:26:37 PM »
Wasn't that first idea that Kubig gave? Lol

Enviado de meu C6603 usando Tapatalk


Offline yolyoly

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
Re: Problems with the integrations gax and composer
« Reply #9 on: September 24, 2015, 01:48:56 PM »
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.

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Problems with the integrations gax and composer
« Reply #10 on: September 24, 2015, 01:55:52 PM »
[quote]
These folders (for announcement and music) has to be "mapped" from any web server (Tomcat, IIS, Apache, etc.).
[/quote]

What you mention is obvious if you read the arquitecture diagrams...anyway, good you learned something new

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Problems with the integrations gax and composer
« Reply #11 on: September 24, 2015, 01:57:38 PM »
[quote author=yolyoly link=topic=9114.msg40930#msg40930 date=1443102536]
,also the composer runs on a tomcat .
For the GAX is that the wavs has publish in the ISS.
[/quote]

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

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Problems with the integrations gax and composer
« Reply #12 on: September 25, 2015, 06:53:01 AM »
[quote]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.[/quote]

You are not right:

[list]
[li]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[/li]
[li]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.[/li]
[/list]