> What is the use of sending REGISTER with no contacts then? To fetch existing bindings with the registrar.
i.e 200 OK REGISTER will have those contacts that the registrar already has with it bounded to the AOR present in the To header of REGISTER. On Tue, Feb 2, 2010 at 12:18 PM, Sharanabasavaraj Mathapati <[email protected]> wrote: > > Thanks Vishal, >> The binding cannot take place (or get refreshed or removed) when > REGISTER doesn't have Contact header > What is the use of sending REGISTER with no contacts then? > > Thanks, > Sharan > > -----Original Message----- > From: Agrawal, Vishal [mailto:[email protected]] > Sent: Monday, February 01, 2010 10:00 PM > To: Sharanabasavaraj Mathapati; [email protected] > Subject: RE: Reg: REGISTRATION > > Hi Sharan, > > The binding cannot take place (or get refreshed or removed) when > REGISTER doesn't have Contact header. > > Per 3261 the registrar can either send the current binding(s) for the > AoR (with remaining expiry) in 200 OK or challenge the request first and > then send the binding(s) in response to the authenticated REGISTER > request. > > Regards, > Vishal > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Sharanabasavaraj Mathapati > Sent: Monday, February 01, 2010 8:53 AM > To: [email protected] > Subject: [Sip-implementors] Reg: REGISTRATION > > > Hi, > > > > 3261 says REGISTER message can have 0 or more contacts. > > what if REGISTER doesn't have "contact" header? With which the binding > takes place? > > > > Regards, > > Sharan > > > > > > ======================================================================== > ==================================================== > > Disclaimer: > > This message and the information contained herein is proprietary and > confidential and subject to the Tech Mahindra policy statement, you may > review the policy at <a > href="http://www.techmahindra.com/Disclaimer.html";>http://www.techmahind > ra.com/Disclaimer.html</a> externally and <a > href="http://tim.techmahindra.com/Disclaimer.html";>http://tim.techmahind > ra.com/Disclaimer.html</a> internally within Tech Mahindra. > > ======================================================================== > ==================================================== > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > ============================================================================================================================ > > Disclaimer: > > This message and the information contained herein is proprietary and > confidential and subject to the Tech Mahindra policy statement, you may > review the policy at <a > href="http://www.techmahindra.com/Disclaimer.html";>http://www.techmahindra.com/Disclaimer.html</a> > externally and <a > href="http://tim.techmahindra.com/Disclaimer.html";>http://tim.techmahindra.com/Disclaimer.html</a> > internally within Tech Mahindra. > > ============================================================================================================================ > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
