" /> ISERVER7 - Genesys CTI User Forum

Author Topic: ISERVER7  (Read 3576 times)

Offline north

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
    • R-MAD
ISERVER7
« on: November 22, 2007, 03:04:41 PM »
Advertisement
Hi all
I kinda stuck on something ! I have ISERV1 as primary and ISERV2 Secondary .
When I start the application ISERV1 start and set itself to mode Primary and status Started on SCI.
When i start ISERV2 and set itself to Mode Secondary but status is Service Unavailable on SCI. All call flow works perfectly going through IServer1

When I switch down ISERV1 then ISERV2 is switch over from Secondary  to Primary mode and also it set itself to STARTED MODE. All test calls works perfectly. But now my IServer1 is set to secondary and Service unavailable.

My issue is why when the ISERVER is set to Backup is show Service Unavailable ?
Any idea pls? ???

ahmad

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: ISERVER7
« Reply #1 on: November 22, 2007, 09:41:48 PM »
Hi Ahmad,

the status "Service Unavailable" means that the application is running but connection to switch/IVR is missing. I would say that your IVR system (IVR driver) is configured to connect to one (primary) IServer only and that's the reason why you see that status.

René

Offline jbobinsk

  • Jr. Member
  • **
  • Posts: 87
  • Karma: 1
Re: ISERVER7
« Reply #2 on: November 23, 2007, 06:44:26 PM »
It may be a little different reason - I've never installed IServer with HA architecture, but as I remember IServer works only in Worm Standby - so only wan can provide service at the moment.


Regards

Jacek Bobinski

Offline north

  • Newbie
  • *
  • Posts: 9
  • Karma: 0
    • R-MAD
Re: ISERVER7
« Reply #3 on: November 28, 2007, 10:55:50 PM »
Hi All

I got it solve . Infact that the way genesys behave on a HA environment.

Check link
http://genesyslab.com/support/dl/retrieve/default.asp?item=B7C732AA32AA32AA32AA3241B7C43345&view=item


A problem with inconsistent T-Server synchronization status has been corrected. Now T-Server will be in status Service Not Available when started in Warm Standby mode, regardless of the value of option ha-sync-dly-lnk-conn. (ER# 98729726)

So, my situation was  normal IVR Server behavior.

Thanks