Hi, >>And, as you say, the edge proxies may be "access network dependent", so it may not even be possible to e.g. register the >>wlan contact via the 3g edge proxy, etc. > >So you are saying that the contact addresses are themselves access network dependent??? So that the ip address of the >contact is only accessible via a particular access network and proxy? > >This *really* isn't the internet, is it!!!
I am not sure I understand. Typically each access network assigns IP addresses to the UA independent from each other. The wlan network has a no idea what IP address the 3g network assigns to the UA, and vice versa. Regards, Christer > Regards, > > Christer > > > > > > Thanks, > Paul > > Christer Holmberg wrote: >> Hi, >> >> > 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 >> >>> no, like this: >> > UA_Contact_wlan ----- OB_1 ----- REG_1 > UA_Contact_wlan ----- >> OB_2 ----- REG_2 >> > UA_Contact_3g ----- OB_1 ----- REG_1 >> > UA_Contact_3g ----- OB_2 ----- REG_2 >> >> Now, in your example, if OB_1 and REG_2 fail you don't still don't >> have redundancy :) >> >>> if outbound does not mandate that UA must register each contact with >> both ob proxies, my pleasant surprise was a too >>> early one and ob draft falls back to the useless bin. >> I don't have the spec in front of me, but I don't think it currently >> talks about multiple contacts. >> >> I guess this all comes back to Dean's question whether we need some >> new text into the draft. >> >> In order to avoid delaying the Outbound spec even more, I guess it >> could also be an extension draft:"Outbound with multiple contacts", >> or > >> something like that... >> >> Regards, >> >> Christer >> >> >> >> >> >> -- 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 >> > _______________________________________________ > 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 > _______________________________________________ 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
