Author Topic: DirectTalk IVR Question  (Read 4418 times)

This topic contains a post which is marked as Best Answer. Press here if you would like to see it.

Superglide

  • Guest
DirectTalk IVR Question
« on: January 01, 1970, 09:00:00 AM »
Hi,



Does any one run an AIX based DirectTalk IVR system using the d2is Custom Server provided by Genesys?  If so, did you have any problems implementing it or experiance any issues under load?  Our system seems to fail under load.  Perhaps it may be best if you email me direct so I can describe the sysmptoms in full.



Many Thanks

Marco

  • Guest
DirectTalk IVR Question
« Reply #1 on: January 01, 1970, 09:00:00 AM »
Hello,



We are using direct talk with this customer server.

But we don't have any problems with it.



greetings marco

Dana Lee

  • Guest
DirectTalk IVR Question
« Reply #2 on: January 01, 1970, 09:00:00 AM »
We recently had a problem with high call volumes.  Genesys gave us some tuning parameters for the d2is driver.



tserver

port

ivrserver

10

15

7



Make sure there are no spaces after any of the parameters.

If you send me an email, I can get you the meaning of the parameters.

Marked as best answer by on March 29, 2020, 02:24:50 AM

Kevin

  • Guest
DirectTalk IVR Question
« Reply #3 on: January 01, 1970, 09:00:00 AM »
  • Undo Best Answer
  • Also, check the version of the Driver you are running. We encountered issues during a stress test in December 2003, and we found one of the issues to be the version of the driver and server we were running  it was known to have issues under load.



    We updated the driver, rean the stress test, and passed with flying colors.

    Dana Lee

    • Guest
    DirectTalk IVR Question
    « Reply #4 on: January 01, 1970, 09:00:00 AM »
    In the D2IS settings the order of the parms are important.  I verified with Tech Support that the order is in fact kkk nnn lll.



    The following is from Tech Support:



    D2IS settings:



    HostName

    Port

    IVRDriverName

    kkk

    nnn

    lll





    A timing issue has been corrected that impacted IVR Driver performance

    during extreme loading. Three additional parameters for Custom Server

    Properties are now available. These additional parameters are not

    required and are intended for use only by advanced users or under

    direction from Genesys Technical Support. [ER #62924]



    nnnAmount of time in milliseconds that the IVR Driver waits between

    messages from the application's message queue and GetReply responses

    from the IVR Server before the IVR Driver continues processing. Default

    is 50. In all previous releases of this product, the default was 100.



    kkkNumber of messages the IVR Driver receives from the application's

    message queue before issuing a GetReply response. If the queue is empty,

    the IVR Driver proceeds directly to the GetReply response. Default is 1.







    lllNumber of times a GetReply response is issued before the IVR Driver

    returns to the application's message receive loop. Default is 255.



    Thanks,

    Dana Lee