Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: water235 on December 01, 2017, 06:23:32 PM

Title: CM restart - Avaya TServer Impact
Post by: water235 on December 01, 2017, 06:23:32 PM

All,
IF CM is bounced and AES is not being touched, is it needed to restart Avaya TServer - is there a chance for it go out of SYNC -  please comment. i would think - but need some help here.
Thanks
water

Title: Re: CM restart - Avaya TServer Impact
Post by: hsujdik on December 01, 2017, 06:32:12 PM

[quote author=water235 link=topic=10778.msg49014#msg49014 date=1512152612]
is it needed to restart Avaya TServer
[/quote]
Shouldn't need it.

[quote author=water235 link=topic=10778.msg49014#msg49014 date=1512152612]
is there a chance for it go out of SYNC
[/quote]
It is unlikely. T-Server for Avaya CM queries the DNs from time to time (3 seconds by default) in order to know the current state of each DN.

Do you have T-Server logs to illustrate better your needs?

Title: Re: CM restart - Avaya TServer Impact
Post by: water235 on December 02, 2017, 01:00:00 AM

this activity is yet to be done, looking for proactive measures

Title: Re: CM restart - Avaya TServer Impact
Post by: water235 on December 04, 2017, 02:40:41 PM

Looks like it is required -
post CM restarts, Agents Phone (which was expected to be auto restarted) did not get restarted, TServer had the wrong Status of these DN after those phones where manually restarted  -
so TServer had to be restarted to get it clean - AES did have a connection blip as well.

Thanks
water