Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Vic on January 01, 1970, 12:00:00 AM
-
Hi everybody!
Does anyone know if HA Proxy can be used with Meridian?
I was under impression that with G6.1 we can use HA Proxy with Meridian Link only. I played around with the software a little bit and have noticed that I can connect two HA proxies to the same link, and run two TServers in hot standby mode.
Has anyone else been able to do that on Meridian?
I really would like to hear any opinion you might have about HA.
Thanks,
Vic
-
Hi Vic:
I have used HAProxy with a Lucent G3. Yes, you can use TWO HAProxies with ONE CTI link. But if you need redundancy even at the LINK level, then it is better to have both the HAProxies connect to TWO different CTI links. In this case, it would provide complete redundancy, even failure of the LInk.
Advantage of HAProxy is we can have staging/QA Tservers also connect to the PRD links by mentioning the ports of the PRD HAproxies. In this way, we can atleast have FOUR Tservers connect to the HAProxies and it elminates the need of the Tserver to be in the same physical room as the switch.
I also think that the HAProxies for Lucent G3 and Meridian work the same way.
Thank you,
Ramesh.
-
The information that I have is that HotStandby can not be used for the Meridian Link due to Link restrictions. Apparently a DN can not be acquired by more than one line. Due to this you are not able to use Hot Standby at least for 6.1, however you can use Warm Standby.
-
I would agree with this as well. The Meridian can only support warm standby mode unless you put in two Link modules?? (not sure whether this is possible and how it relates to Symposium) Even if this is possible, would need to be careful about aquiring and deaquiring DNs during the switch over.
Rory
-
Ok, I have played with HA Proxy on MLink and I am stuck!
I have nothing connected to my link (here is the result of "get associations")
mlusr> get associations
Association ID: 4
Application ID: CCR03.55
Host Link ID: NONE
Meridian 1 Link ID: 0
Meridian 1 Name: SL16
Meridian 1 Customer Number: 0
Meridian Mail Link ID: NONE
Registered Services: 99
Association ID: 15
Application ID: ADMIN.6021
Host Link ID: NONE
Meridian 1 Link ID: NONE
Meridian 1 Customer Number: NONE
Meridian Mail Link ID: NONE
Registered Services: 1
Yet, when I try to start HA Proxy I get:
<< 1 ff 0a 00 0e 00 80 00 7f 01 4a 78 04 00 04
s< 1 Invalid Message Received (Cause:4)
18:38:23.8374, mlink: Another application found
I do not have TServer connected to HA proxy yet...
Is it telling me that I have another application connected because I have CCR there???? (I hope not!)
Or is it something to do with "Redundancy" attribute I found in its Application Registration request? (log below)
s> 1 Application Registration (Application Protocol:1 & Application ID:HA_Proxy & Host ID:Lanlink & Service ID List:97, 98, 100 & Meridian 1 Machine Name:SL16 & Meridian 1 Customer Number:4 & Redundancy:40)
Any one has a suggestion?
-
I have a Lucent/Avaya G3R switch, so unfortunately I can't help you with Meridian, but I can tell you I've had 2 haproxy apps and 2 tserver apps running without many issues. One thing you have to keep in mind is that Solution Control Server MUST be running if you have indicated hot standby mode in your TServer apps in CME. If you don't have SCS running, it can't negotiate primary from secondary and nothing will work. I learned that one the hard way.
-
I played a little bit eith G3 HA proxy and it was really easy to setup and get it to work.
One of the things I haven't checked was what happens to the calls that are already queued by URS? Also, what happens to a call that just started to be routed to a remote site when TServer switches?
Do you have some kind of testing matrix, evaluation info, etc that you could share?
-
The reason why I could not get them to work is because I was using MLink 5 not 5c, and MLink 5 does not support redundancy.
Since 5c is not offered here, I guess we cannot do it.