" /> WVR and Genesys CTI integration - Genesys CTI User Forum

Author Topic: WVR and Genesys CTI integration  (Read 2989 times)

Offline dragoncool

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
WVR and Genesys CTI integration
« on: October 06, 2011, 02:18:15 PM »
Advertisement
Hi guys,

I'm trying to integrate a WVR with genesys CTI here in my company, but I'm having big issues with that.
In the past, we used a different connector, but now with the WVR 6.1 we have the connector already embedded and looking the WVR webpage, we need to use the routeRequest in the way that is showed in the example:
[code]
<form id="gcti_routerequest">}}
  <object name="gcti" classid="method://com.ibm.wvr.vxml2.NativeAppSupport/invokeGCTI"
          type="javacode-ext">
    <param name="setGCTIActionToInvoke" value="RouteRequest"/>
    <param name="setGCTIRouteDN" value="3000"/>
    <param name="setGCTIRouteCED" value="1234567890"/>
    <filled>
      <log>Number is: <value expr="gcti.routeNumber"/></log>
    </filled>
  </object>
  <block>
    <log>Completion code is: <value expr="gcti.completionCode"/></log>}}
  </block>
</form>[/code]

But nothing is received in the Genesys CTI.
Do you guys have any info about the necessary configuration that is necessary to be done in the WVR and/or Genesys side?
I will appreciate it a lot!

PS: the official explanation is here: [url=http://publib.boulder.ibm.com/infocenter/wvraix/v6r1m0/index.jsp?topic=%2Fcom.ibm.wvraix.vxmlpg.doc%2Fgenesyscti.html]http://publib.boulder.ibm.com/infocenter/wvraix/v6r1m0/index.jsp?topic=%2Fcom.ibm.wvraix.vxmlpg.doc%2Fgenesyscti.html[/url]
PS2: The setGCTIRouteCED is obligatory, even when the documentation is saying that is not.

Thanks for your help,
Steven Meiner


Offline Kevin S

  • Full Member
  • ***
  • Posts: 145
  • Karma: 4
Re: WVR and Genesys CTI integration
« Reply #1 on: October 07, 2011, 04:01:41 PM »
It looks to me like you still need to install the Genesys I-Server for that version of WVR. It looks like they added support into the VoiceXML code, so you could connect to it there instead of having to connect to the IServer driver via State Tables, like you had to before.