Controller is a web-application that acts as the “front door” or flow-controlling mechanism, and receives and directs (HTML GET) requests coming from the VoiceXML browser, e.g. Genesys MCP, associates these requests with the stored session information.
So, what we expect is to run the following scenario:
Genesys receives the phone call and diverts it to GVP;
After running the related routing scripts, GVP invokes Controller (http://:9081/voicePortal/controller, or through http:///voicePortal/index.vxml);
Controller generates the related JSP that contains VoiceXML based on the actual status of the call and some business rules, and respondes Genesys;
Genesys interprets and follows this VoiceXML.
As far as we know, MCP does not support such integration. Could you please inform us regarding any workaround or method, so we can integrate this VoicePortal service with our Genesys Platform?
Unless I’m reading it completely wrong… GVP works in the way you had described it - it interprets VoiceXML code provided by web server. It doesn’t matter if it is static or dynamic code as far as GVP can interpert it.
Could it be that you need to call it as a subcallflow from a composer generated one? I guess the main call flow might need some genesys-specific stuff?
GVP is a VXML browser, no matter who provides the VXML, Composer will browse and execute it.
Imagine it as a PHP and ASPX in backend, but at the end both send HTML to your browser.
The PHP can call the ASPX and so on…doesn’t matter.
So you just create a IVR Profile and point to that VXML and done.
Now, if that VXML is or is not compatible with GVP, is another thing.
As already said, in your Composer project you can also call this external VXML (generated by whatever is behind) and call it by using a block.
Read more about the architecture so you get a better idea on what you need to do.
If you can’t figure out how to call your external VXML, ask the provider maybe, as they should have some application ideas based on what you asked for them to do.