CM restart - Avaya TServer Impact

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

Shouldn’t need it.

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?

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

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