PureEngage On-Premises

I'm building a Server Application with .net Platform SDK 8.1. I need to communicate with SIP Server, running in Hot Standby mode. I use the WarmStandby Application Block, as recommended, but I am unsure what I need to do in case of a primary/backup switch. As far as I can tell from the logged activity, the PSDK automatically connects to both servers and relays my RegisterDN Request to both of them. When we forced a failover with SCE, my Service kept running as if nothing had happened. But is this always the case? Or must I re-register my DNs in some cases? If yes - how to identify them?

Hi Rolf,

WarmStanby and HotStandby are implemented on different levels and not associated with each other.

Warm Standby is universal component, it can be used with any protocol to perform channel re-open. It doesn't know anything about T-Server (or any other protocol) events or requests to be able to proceed DN registration. WarmStanby listens to AbstractChannel.Closed event to open new connection if required.

HotStandby is a feature that only implemented in TServer protocol and more over - internally. It can make transparently to user reconnection, switchover, DN registration until at least one of T-Servers alive. With HA mechanism Tserver protocol encapsulates 2 connections to Primary and Backup. Until HA keeps connection to at least one of T-Servers - the channel remains opened. However, when both connections are lost – for example when both servers shutdown, channel fires AbstractChannel.Closed event and clears all session data. At this point, after your application opens connection again, it is also required to perform DN registration as if you opening connection for the first time.

--
Thanks,
Volodymyr Tsap