Identify Tserver application bounce scenario

[Mahe]

hi
I am new to genesys. right now in our application we are establshing tcp/ip connection to a tserver using Tserver protocol. and we register some set of DNs. the registration of Dns happens successfully and our application also starts receiving events for those Dns. at one point of time some application in the Tserver side goes down ie bounce occurs.. there after we do not recieve any events for the DNs. we hav to restart our application to register the Dns again and listen for the events
now we need to identify when the Tserver app went down  and based on this we need to register the Dns again to start receiving the events
we are using genesys 7.x voice protocols TserverProtocol and we tried to set Addp configuratins for the protocol and tested in genesys Tserver simulator. but we could nt implement it properly
does the Tserver also be configured with Addp settings. if so can u please let us know how to set those settings in the Tserver simulator side (we use Tserver simulator and PBX simulator)
configurin Addp may not help the above problem (not getting events aftr some Tserver app bounce) but still we were tryin to configure and test
Sorry if i m not clear in asking the question since i have no much idea about genesys

[Kubig]

Try to read about ADDP in documentation. ADDP is just a proprietary Genesys protocol for advanced detection of local/remote failure.

if the T-Server goes down and there is no HA, you have to re-register requested DNs from your application again. That is expected and right behavior.

[cavagnaro]

just do it on the TEvent LinkDisconnected

[Mahe]

there is an event com.genesyslab.platform.voice.protocol.tserver.events.EventLinkDisconnected.. the api tells it is disconnection between the tserver and the switch and we do not recieve this event when the application bounce occurs
Any other alternate to find the Tserver down and re-register the Dns

[Kubig]

When the HA-pair switch roles, the event EventPrimaryChanged or something like that (I am not at my PC to approve it). Just try to make a switchover and find out what events are generated.

[cavagnaro]

Wait but if he has HA then no need to re-register DNS...something else is wrong. HA should fire immediately without magic.

[zafzef.mourad]

Why u don't just send a mail to the support service if TServer or switch is down....so they can reboot ur application

I had developed a application to monitoring some DN and if TServer is down I send mail and I switch to the TServer backup

[zafzef.mourad]

Use EventServerDisconnected to check if TServer down or not

[mduran22]

I don't think rebooting or restarting the TServer each time is a good long term solution. You need to find why TServer is going down, especially if it is consistent. You should be able to use some out of the box alarms that send alerts when TServer goes down. Since TServer is a central part of Genesys all of the other applications connected should be complaining. Do you see anything in the logs that would indicate why TServer stops or do the logging lines just stop?