Leo, "should" means UAs might do it differently...-)
I think the key point is that from UA perspective, another registration means another "virtual" phone and therefore it "should" use a different call-id. >From the registrar point of view the primary problem (as I think) is to find out if that that registration will replace an already existing registration. In SIP, it's ok that an AOR has several registrations; therefore the registrar must find out if the REGISTER replaces an already existing registration - and that could be done using the call-id. For example, imagine that the IP address of a user-agent changes and the user agent wants to update its address. (Of course, the clean way to do this would send a unregister request first). BTW registering phones on the same domain with alias should be done with alias set up on the proxy. This is a common practice with email accounts today and I envision the same will happen in SIP. Christian > -----Urspr�ngliche Nachricht----- > Von: [EMAIL PROTECTED] [mailto:sip-implementors- > [EMAIL PROTECTED] Im Auftrag von Papadopoulos, Leo > Gesendet: Mittwoch, 12. M�rz 2003 23:06 > An: [EMAIL PROTECTED] > Betreff: [Sip-implementors] Multi-AOR Registrations > > Dear Implementors, > > I have one phone that wants to REGISTER for TWO addresses of record > (sip:2111 & sip:2110). > > I think this is done by sending two REGISTRATIONS from the same UAC as > follows: > REGISTER sip:159.63.70.148 SIP/2.0 > From: sip:[EMAIL PROTECTED];tag=29344c29344 > To: sip:[EMAIL PROTECTED] > Call-Id: c9012720dd1e48e4262f40437eba7b21 > Cseq: 1 REGISTER > Contact: <sip:[EMAIL PROTECTED];LINEID=09b9dc0322b74342bbdb8b973a7ac8c5> > Expires: 3600 > Date: Mon, 10 Mar 2003 16:23:53 GMT > Accept-Language: en > Supported: sip-cc, sip-cc-01, timer, replaces > User-Agent: Some-UA > Via: SIP/2.0/UDP 159.63.70.218 > Content-Length: 0 > > REGISTER sip:159.63.70.148 SIP/2.0 > From: sip:[EMAIL PROTECTED];tag=17834c17834 > To: sip:[EMAIL PROTECTED] > Call-Id: 0ce49d480dcfc3ca9435a48804548031 > Cseq: 1 REGISTER > Contact: <sip:[EMAIL PROTECTED];LINEID=ea99e11a59e22dcac96d7f957e9770a3> > Expires: 3600 > Date: Mon, 10 Mar 2003 16:23:53 GMT > Accept-Language: en > Supported: sip-cc, sip-cc-01, timer, replaces > User-Agent: Some-UA > Via: SIP/2.0/UDP 159.63.70.218 > Content-Length: 0 > > However the SIP RFC3261 section 10.2 says that all registrations from the > same UAC should use the same Call-ID. I am pretty sure that the spec > should > instead read as follows: "all registrations from the same UAC should use a > different Call-ID for each AOR they are registering, however the call ID > for > registrations for the same AOR should NOT change." > > Implementation from Pingtel and SNOM back me up on this, but my stack > vendor > disagrees. Can anyone help resolve this issue? > > ________________________________________ > Leo Papadopoulos > IPC Information Systems, Inc. > VP Systems & Architecture > 777 Commerce Drive > Fairfield, CT 06432-5500 > E-Mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > Web Page: http://www.ipc.com > Yahoo IM: leopapadopoulos > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
