Hi, >>Outbound provides you with multiple flows to reach a user. >>I doesn't matter if each flow is not associated with the >>same contact, as long as the user can be reached on any of >>the flows. > >this is all true, but then it makes no sense for ob draft to >mandate registering via at least two ob proxies. the ua can >register with one and if that flow dies, register with >another one. your requirement is satisfied and there is no >need for ob draft to mandate two flows.
I have never said that a user should only register with one ob proxy. As specified, one should register with at least two ob proxies, but my point is that it doesn't matter if those two registrations are bound to the same contact, as long as the user can be reached on both of the registrations. Regards, Christer > > i'm sorry that i brought the "minimum two" issue up. the > current text does not help me to achieve my goal and it can > very well be removed. as side effect, it makes no sense to > implement outbound, because it does not add any value. UAs > are already using keepalives without outbound. > > -- juha > _______________________________________________ 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
