Author Topic: Doubling CTI-Link Cisco for safeguarding against failure  (Read 2164 times)

Offline HoFranki123

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
Doubling CTI-Link Cisco for safeguarding against failure
« on: July 25, 2014, 12:28:02 PM »
In use are a CUCM V8.5 (Primary, Subscriber) and Genesys V8.0. The existent CTI-Link has to be doubled for reasons of reliability. No warm standby, no hot standby.

In Genesys-web I see for subject of CTI-Links in Article 16475:

...
A.) For multi link non-redundant mode the following cfg example can be used:
link-tcp-1 [1] list {aux}  <+>
        protocol (uf:-1) = tcp <+>
        hostname (uf:2) = 'localhost' <+>
        port (uf:2) = 3021 <+>
        ccm-host = '10.20.30.5' <+>
        user-login = 'genesys1' <+>
        password = '********' <+>

link-tcp-2 [1] list {aux}  <+>
        protocol (uf:-1) = tcp <+>
        hostname (uf:2) = 'localhost' <+>
        port (uf:2) = 3022 <+>
        ccm-host = '10.20.30.4' <+>
        user-login = 'genesys2' <+>
        password = '********' <+>


B.) For single link non-redundant mode with two redundant CTI Managers the following cfg example can be used:
link-tcp [1] list {aux}  <+>
        protocol (uf:-1) = tcp <+>
        hostname (uf:2) = 'localhost' <+>
        port (uf:2) = 3021 <+>
        ccm-host = 10.20.30.1,10.20.30.2<+>
        user-login = 'genesys' <+>
        password = '********' <+>


Article 16475 remarks to subject "How to configure Multiple JTAPI links for Redundancy (non-loadbalancing)":
- Need to configure the 'ccm-host' option in the TServer section
- Option defined as a comma separated list of links: primary,secondary,tertiary,etc
- NOTE: the list must be comma separated with NO SPACES
- parameter is passed to the JTAPI process and the failover is controlled by the JTAPI process


Questions:
1.) Are the following statements correct?
For described purpose I proceed analog B.) and specify IP-adress of primary (x.x.x.x) and of subscriber (y.y.y.y) in ccm-host. So thats ccm-host = x.x.x.x,y.y.y.y". If one JTAPI-connection fails, JTAPI-process automatically takes other JTAPI-connection. No other actions are required.

2.) Is this correct?
When proceeding analog B.) - only JTAPI-side of CUCM is doubled, not JTAPI-side of Genesys host. So if there are problems on Genesys host with JTAPI problems will still stay alive.


3.) Are the following statements correct?
Explanation A.) is for purpose that multiple CTI-Links are required such as more than 2.500 DNs are configured. DNs in CUCM are linked to appropriate "user-login". Thats no subject to safeguarding against failure.


Regards