AFAIU, Any proxy which forms part of the route-set during call setup. It must support backup and recovery mechanism.
One simple example where the proxy supports billing functionality could be part of the route-set and it shall support back and recovery. In this case it shall back back up all the necessary data to recover if there is any failure in the active unit. Otherwise it does not make sense to to be part of a route-set. On Mon, Jan 3, 2011 at 9:10 PM, aayush <[email protected]> wrote: > The route set cannot be changed mid dialog. > > Regarding the endpoint detecting the crash of an intermediate proxy,there > is a periodic session refresh mechanism available in SIP which the endpoint > must support. > > This mechanism is implemented by examining the Session-Expires and Min-SE > headers. > > Conversely if a backup proxy takes over the crashed one, then both proxies > (Active-Stabdby) must support Virtual IP failover for implementing this > fault tolerance use case. > > On Jan 3, 2011 8:59 PM, "Worley, Dale R (Dale)" <[email protected]> wrote: > > ________________________________________ > From: [email protected] [[email protected]] On Behalf Of Avshalom > Houri [[email protected]] > > > Assume that the first SIP proxy that is part of the route set (in SIP > outbound) > crashes and immedia... > > ________________________________________ > > As you phrase the question, the *dialog* cannot be kept alive if the > connection in question is lost because the route set cannot be changed. > > Dale > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is essentially closed and only used for finishing old business. > Use [email protected] for questions on how to develop a SIP > implementation. > Use [email protected] for new developments on the application of sip. > Use [email protected] for issues related to maintenance of the core SIP > specifications. > > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is essentially closed and only used for finishing old business. > Use [email protected] for questions on how to develop a SIP > implementation. > Use [email protected] for new developments on the application of sip. > Use [email protected] for issues related to maintenance of the core SIP > specifications. > -- Thanks, Nataraju A.B.
_______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is essentially closed and only used for finishing old business. Use [email protected] for questions on how to develop a SIP implementation. Use [email protected] for new developments on the application of sip. Use [email protected] for issues related to maintenance of the core SIP specifications.
