" /> TServer on AIX cluster can't work with DefinityG3 - Genesys CTI User Forum

Author Topic: TServer on AIX cluster can't work with DefinityG3  (Read 7031 times)

JAG

  • Guest
TServer on AIX cluster can't work with DefinityG3
« on: January 01, 1970, 12:00:00 AM »
Advertisement
We are using G6.1 on AIX cluster platform. But TServer on backup SERVER B can't use the virtual ip to connect to the Definity G3r after SERVER A down although other components like config server work properly.
BTW, LCA installed on both SERVER A and SERVER B, but the Solution Control Server running on SERVER A try to connect to LCA on SERVER B, I don't know why and can't find any option to correct this problem?

Vic

  • Guest
TServer on AIX cluster can't work with DefinityG3
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • JAG,

    I am not sure how much of help it will be, but make sure that both IPs are registered in G3 so that they can be access from outside :) Also, how do you know that your TServer cannot access the link on G3? What does the log say?
    Vic

    JAG

    • Guest
    TServer on AIX cluster can't work with DefinityG3
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Thx.
    Let me introduce the environment 1st
    Primary Server A use ip=xxx.xxx.xxx.103 to connect to G3.
    Backup Server B use ip=xxx.xxx.xxx.123 to connect to G3.
    When Server A is down, the HA cluster will run scripts to make Backup Server B to continue run services as if it was on xxx.xxx.xxx.103. But when it try to run TServer on Server B, the link1's status is "connect down" shown on G3. After I changed the G3's setting to point CTI to xxx.xxx.xxx.123, the TServer works ok on Server B.
    Do you mean that I should enable 2 cti links on G3 to make both Server A and Server B to connect to G3?

    John

    • Guest
    TServer on AIX cluster can't work with DefinityG3
    « Reply #3 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • We were receiving this same type of error message and that's what we had to do define a seperate link for each TServer on the G3 in the Avaya connections config and modify the TServer config so that each TServer had a different link number. Avaya had told us we did not need to do this, but it's the only way we could make it work....

    JAG

    • Guest
    TServer on AIX cluster can't work with DefinityG3
    « Reply #4 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • So you mean I should use 2 different TServers to connect to G3H Also 2 ctilink sets in G3? Then how could cti client know which TServer to connect to?

    Vic

    • Guest
    TServer on AIX cluster can't work with DefinityG3
    « Reply #5 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Jag,

    by defining two separate IP addresses (local IP addresses for both of the machines in a cluster plus virtual IP, you make sure that both of the machines have access rights to the link.

    It seems like cluster even though uses a virtual IP for connections, TServer is using machines local ip, and not virtual in its transmissions. This would explain why you have troubles connecting to the link.

    I do not fully understand why you need to define two separate TServers. I was able to get it to work by having all the IP addresses of every possible proxy and virtual IPs defined in G3; however, I am sure there is always mor than one way of doing it :)
    What is the reason for two TServers with different links ids?
    Vic

    JAG

    • Guest
    TServer on AIX cluster can't work with DefinityG3
    « Reply #6 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • I am confused.
    So Vic you mean one Tserver but 2 links defined in G3 for both 103 and 123. But 103 and 123 are both virtual ips. It should be ok. I will test it.

    Ramesh Pitchumani

    • Guest
    TServer on AIX cluster can't work with DefinityG3
    « Reply #7 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Hi Jag:

    With G3, we need TWO HAproxies. You can have ONE CTIlink and have both HAproxies talking to the CTIlink. Both the HAproxies should run as PRIMARY.

    Both the Primary and the Backup Tserver should connect only to the HAproxies. They should not try connecting directly to the G3. The TCPIP section for the CTILink on the Tserver should be removed. The idea is to have HAProxy have a direct Link to the G3 and NOT to have Tserver a direct link to the G3. Thus you can accomplish a redundancy for failover from the Genesys side.

    But if you want redundany from the G3 side also, then you can have TWO CTIlinks created in G3. Have each HAProxy connect to separate CTI links. Have your PRIMARY Tserver connect to both HAproxies. Backup Tserver should automatically take care of the connections to the HAproxies.

    We have it working in our environment. If you have anymore questions, let me know.

    Thanks,
    Ramesh.

    Ramesh Pitchumani

    • Guest
    TServer on AIX cluster can't work with DefinityG3
    « Reply #8 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Hi Jag:

    It depends on the version of CTI client you are using. If you are using ActiveX 6.1 Desktop, then you are lucky. ActiveX is HAaware and so failover works properly.

    What I mean is this. You should have your CTI client talk to the PRIMARY Tserver. When the Primary Tserver fails, you should notice an event "EventPrimaryChanged" on your CTI client. Thus calls are not lost and the CTI client is now connected to the BACKUP Tserver automatically. But you need to have the Solution Control Server running and the LCA's running. Also when you have your PRIMARY and BACKUP Tservers startup, you should see "EventLinkConnected" message on BOTH Tservers. Only then the failover is seemless. If you do not see this message even in ONE Tserver, then you failover won't work properly.

    Thanks,
    Ramesh.

    JAG

    • Guest
    TServer on AIX cluster can't work with DefinityG3
    « Reply #9 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Thx for your advice. But the situation is that we didn't buy the HA proxy. Any other solutions?