Skip to main content

about failover

2 replies [Last post]
nijie8
Offline
Joined: 2005-06-09

i think if sipstack is transaction stateful ,it's very hard to handle mid-transaction failover.

in that case,we should replicate transaction state in sip stack. And could it be done?

And if we use stateless sip stack and store all stack state in sbb,it's also possible to solve the problem.

Anybody give me some suggestion.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
mranga
Offline
Joined: 2003-06-06

Making the stack transaction stateful, puts all the burden on the Sbb to track SIP state. This makes it hard to build an sbb and it greatly increases the amount of traffic that the SBB sees ( all retransmission of sip messages has to be handled by the SBB).

What is needed is to replicate some of the sip transaction ( in particular, the transaction state and the last message sent out via the transaction). We have not done that yet and hence we dont handle mid-invite failover. The resource adaptor needs to replicate the state of the invite transaction in order to enable that.

Ranga

nijie8
Offline
Joined: 2005-06-09

you are right