Hi, >>That still dooesn't answer my question: why do you want forking? Why can't the registrar simply choose ONE working flow? > >forking increases changes that the call actually gets through, because one of the access networks may not be reachable at >the moment. also, if both 3g and wlan is reachable, call comes through many seconds earlier through wlan and is usually >also free. i understand that mobile operators don't have incentive to fork the call if one of the legs is free and the >other costs money.
Yes, because earning money is simply wrong :) >>And, the UA can make normal (non-outbound) registrations via each of the two ob proxies. They will still operate >>indepenent of each other - and > you will get forking. > >"can" but is not forced to, which breaks the whole thing. Even if you allow (if it is even forbidden, that is) forking for outbound it is still going to be a "can". No matter if you use outbound or not, you would need to configure your registrar if to do forking, whether to do serial- or paralell forking, etc etc etc. >>Even the UA has two contacts, and registers each once (using normal reg procedures), you will still have redundancy: if >>one contact doesn't work then the registrar will try anohter. > >yes, but then you have only one registrar, which breaks redundancy at server side. So, you want to register both contacts to both registars, right? Example: UA_Contact_wlan ----- OB_1 ----- REG_1 UA_Contact_wlan ----- OB_1 ----- REG_2 UA_Contact_3g ----- OB_2 ----- REG_1 UA_Contact_3g ----- OB_2 ----- REG_2 Regards, Christer _______________________________________________ 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
