" /> MLink Backup & Genesys 6.5 - Genesys CTI User Forum

Author Topic: MLink Backup & Genesys 6.5  (Read 3593 times)

Sunny Nanda

  • Guest
MLink Backup & Genesys 6.5
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Hello everyone,

Can we install a second MLink to our PBX (Nortel 81C)? If yes, how can we configure in the Genesys environment? Also, how can we configure critical Genesys applications as a "hotstandby"?

Please contact me, if you are familiar with these installations.

Have a wonderful holiday season,

Vic

  • Guest
MLink Backup
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Sunny,

    first of all: with Symposium, you can only have ONE link connected at a time. You may have TWO TServers in hotstandby using TWO HA proxies connected to the same symposium link. Of course, Genesys does NOT support it any longer, because they failed to get it to work.

    As for Meridian link, MLink offers warm standby functionality.

    You will need TWO Mlinks configured as redundant.

    Here is Mlink manual says about redundancy:
    The redundancy feature increases the reliability of the CTI interface by supporting a redundant Meridian Link
    Protocol, one in active mode and the other in warmstandby mode.
    To set up a redundant Meridian Link, two AML links must be configured on the Meridian 1. On the host side,
    two communication paths must be set up to two separate Meridian Link Protocols. Once the redundant
    Meridian Link Protocols are set up, the CTI application must indicate its intention to use the feature in an
    ApplicationRegistration message. Currently, the Meridian Link Protocol supports optional application
    polling. The polling interval can be set between 10 seconds and 10 minutes. For a CTI application registered
    to use a redundant Meridian Link Protocol, it is mandatory that the polling interval be set to 5 seconds. To
    support the redundant Meridian Link Protocol, the Redundancy IE is added to the Polling message.
    If there is a problem with the active link, the standby link automatically becomes the active link. This event
    is called a Redundant Meridian Link Switchover. The host can also initiate a switchover by using the
    DisableLink message, followed by the EnableLink message. After a switchover, the active link becomes the
    standby link, and the standby link becomes the active link.

    So, with MLink you can only have warmstandby.

    BUT! According to Genesys (Framework 6.5 TServer and HA Proxy for Meridian 1 Reference Manual, page 85) you CAN have HOT standby for TServer when you use it with HA proxies. According to the picture, you should have HA Proxy 1 connected to CTI Link1 and HA Proxy 2 connected to CTI Link 2. Then TServer 2 is connected to HA2 and HA1.

    Since MLink does not support hotstandby, I fail to see the reason to have TServer in hotstandby...
    So, I guess when they say "CTI link" they mean "SCCS".
    SCCS 4.2 should be able to do it, BUT, I do recall reading somewhere that Genesys failed to get it to work... So, I guess, you have two choices: get Genesys to get it to work in G6.5 or just forget it.

    Drop me a note if you need info on how to setup Mlinks to operate in redundant modes.