> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Juha Heinanen > Sent: 08 October 2008 07:36 > To: Christer Holmberg > Cc: [email protected]; Paul Kyzivat; Dean Willis > Subject: Re: [Sip] Dual registration without Outbound > > Christer Holmberg writes: > > > I don't agree. In my opinion the important thing is the number of > > registartions for the instance-id. Whether different > contacts are used > > or not is irrelevant. > > i don't know what instance-id is and i don't even care to know at this > point. [JRE] I thought we were discussing sip-outbound. Instance-id is a fundamental part of sip-outbound, so please read the draft. Christer is correct - the important thing is whether the UA registers as one instance-id or as two instance-ids (in the latter case, effectively behaving as two UAs within the same device). This is a device decision, and I don't believe we need normative statements in the draft to address this. Some informative hints might be appropriate.
John > > the only thing that matters to me as a user is that if UA is connected > to IP networks and thus has two contacts, it must register > both of them > via both of its two outbound proxies (either in a single register > request listing both contacts or in two separate register requests > listing one each). > > this guarantees that if the two outbound proxies are implemented as > independent proxy/registrar pairs, inbound call to the UA via either > proxy is able to fork the call to both contacts. > > -- 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
