Sameer, Understood, but what we're trying to do is document the procedures for out-of-dialog OPTIONS that is intended to ping the operational status of a neighboring device. We're not focused on pinging a device that is three SIP proxy hops away. The purpose of that document is, for example, to allow a B2BUA that is peered with another B2BUA to know whether the peer is up and able to accept new sessions.
Paul > -----Original Message----- > From: Sameer Sawhney [mailto:ssawh...@cisco.com] > Sent: Wednesday, August 25, 2010 1:14 PM > To: 'Paul E. Jones'; 'mustafa rifaee'; sip- > implement...@lists.cs.columbia.edu > Cc: 'Gonzalo Salgueiro' > Subject: RE: [Sip-implementors] Using SIP OPTIONS Message with IMS > > Hi Paul, > > The draft document talks about procedures to check operational status of > SIP elements which support OPTIONS. > > In network, there might be some SIP elements which do not support OPTIONS > and they will respond appropriately with 405 (Method Not Allowed) to > OPTIONS ping, proving that they are operational and can process further > requests. > > So I think there should not be any limitation that remote end point MUST > support OPTIONS in order to check the operational status. > > In case remote end point does not support OPTIONS, this should not bar the > originating sip element to send further requests. > > Regards > Sameer Sawhney > > > Extract: > > To comply with procedures described in this document, all SIP entities, > including SIP user agents and proxy servers, MUST support the OPTIONS > message when received outside of a dialog in accordance with this memo. > > -----Original Message----- > From: sip-implementors-boun...@lists.cs.columbia.edu > [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Paul > E. > Jones > Sent: Wednesday, August 25, 2010 9:36 PM > To: 'mustafa rifaee'; sip-implementors@lists.cs.columbia.edu > Cc: Gonzalo Salgueiro > Subject: Re: [Sip-implementors] Using SIP OPTIONS Message with IMS > > Mustafa, > > Not specific to IMS, there is a general need to query for operational > status. Unfortunately, we're finding every variant of SIP (or even > products targeted for the same environment) use OPTIONS to query for > operational status, but they all do it differently. What we're trying to > do is write a document or two that defines something everybody can live > with. > > Here's the draft we currently have: > http://tools.ietf.org/html/draft-jones-sip-options-ping > > Marius is also working on text for in-dialog OPTIONS and, unfortunately, > I've not had a moment to review what was produced. > > Paul > > > -----Original Message----- > > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > > implementors-boun...@lists.cs.columbia.edu] On Behalf Of mustafa > > rifaee > > Sent: Wednesday, August 25, 2010 11:17 AM > > To: sip-implementors@lists.cs.columbia.edu > > Subject: [Sip-implementors] Using SIP OPTIONS Message with IMS > > > > Hello all; > > i would ask you about the draft of Using OPTIONS to Query for > > Operational Status in SIP. > > Can we use OPTIONS message with IMS to Query for Operational Status > > in SIP? > > > > Please Help me; > > Thanks > > Mustafa > > _______________________________________________ > > Sip-implementors mailing list > > Sip-implementors@lists.cs.columbia.edu > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
