On Oct 17, 2008, at 9:55 AM, Dean Willis wrote:
So the general solution for two instances, each of which has two registration flows through different edge proxies, would appear to require for REGISTER requests. This model provides full single- failure interface redundancy, flow redundancy, edge-proxy redundancy, transport redundancy, and possibly (depending on the registrar design) registrar redundancy, and provides multiple- failure redundancy in a number of scenarios. More importantly, it allows survivability for a dialog in the event of any single failure (except perhaps a total registrar failure).
That should have been a "four register requests", not "for register requests":
So the general solution for two instances, each of which has two registration flows through different edge proxies, would appear to require four REGISTER requests. This model provides full single- failure interface redundancy, flow redundancy, edge-proxy redundancy, transport redundancy, and possibly (depending on the registrar design) registrar redundancy, and provides multiple-failure redundancy in a number of scenarios. More importantly, it allows survivability for a dialog in the event of any single failure (except perhaps a total registrar failure).
-- Dean _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
