" /> Avaya INDeX TServer disconnects - Genesys CTI User Forum

Author Topic: Avaya INDeX TServer disconnects  (Read 5745 times)

Marc

  • Guest
Avaya INDeX TServer disconnects
« on: January 01, 1970, 12:00:00 AM »
Advertisement
We have installed Genesys Express Voice 2.5 onto an Win2k server (sans TServer) and then additionally installed TServer for Avaya INDeX (6.5.200.02). Following this, we installed the Avaya CTI Integrator 2.06 Client onto the same server. This is connected via the coporate LAN to another Windows 2000 machine which has the CT Integrator Server software installed. This is in turn connected via the same LAN to another Windows 2000 PC running CT Access which is in turn connected to the INDeX via a serial cable (38400 baud I believe).

We can now start up our server with the Genesys components and bring up Genesys Express and the INDeX TServer. We do get a CTI connection between both the switch and the TServer and we can log in the standard ActiveX Desktop to an extension and dial out to external numbers etc using the ActiveX Desktop interface.

Our main problem is that every few minutes (the problem has occurred anywhere from 1 minute to 6 minutes after TServer being started), events start timing out (e.g. we try and release a call from the extension or try and make a dial) and we get an error: 'Request timeout: no acknowledgement' and shortly afterwards, we get an EventLinkDisconnected. It then usually remains in this state for anything up to a minute or so.

One other thing we noticed was that sometimes after the eventlinkdisconnected message, we see an error 'ACCESS VIOLATION' appear in the TServer log following by lines of what looks like garbage. This garbage reflects what we see in the file NCOfault.log which is being recorded in the TServer folder on the server, although we're not sure what exactly is writing this log file. In the CT Integrator event viewer/logger, we can see the disconnects and sometimes in these disconnects, the application name shown is 'TServer' and other times it looks like garbage/corrupt data.

A final thing that I am curious about is that we currently have a few virtual queues, 1 routing point, 1 extension and 1 agent login added under this switch in CME and yet we are seeing activity for what looks like all of the telephony objects in the call centre in the TServer log. I'm not sure if this is supposed to happen but I am more used to the Lucent Definity G3 switch where we only see events for swtich objects that we have added in CME. I am also concerned about this much data being passed through the serial connection between the CT Access PC and the switch although the CT Integrator server log shows no errors or disconnects except for those between our Genesys Server and the CT Integrator Server PC.

I've racked my brains trying to get around this problem but cannot see what is causing the issue. Has anyone got any experience of this switch or problem? Any advice would be greatly appreciated.

Marked as best answer by on March 19, 2025, 11:33:03 PM

Vic

  • Guest
Avaya INDeX TServer disconnects
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Undo Best Answer
  • Hi, Marc,

    we have tested Genesys with Index and it passed the tests with flying colors. The thing was working just fine.

    Can I ask you what version of TServer are you using?
    Also, can you paste the part of the log where you get the error?

    I will have to get back to you about whether or not you should be receiving events for all DNs instead of the ones you have registered for, but my first guess would be have your PBX engineers look through the settings again.

    I know it is not much help, so let me look around and find what else we had to do to get it to work.

    PapaBear

    • Guest
    Avaya INDeX TServer disconnects
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
    what's your link protocol option set to in cme?

    Marc

    • Guest
    Avaya INDeX TServer disconnects
    « Reply #3 on: January 01, 1970, 12:00:00 AM »
    We finally got this problem licked it turns out that the version of TServer we were using had issues with both the frequency of link reconnect attempts and also the NCO functionality. We have now installed TServer INDeX 6.5.302 and it appears to have fixed the problem.

    Now all I need to do is figure how these 'emulated agents' work with Outbound.