thanks Spencer and Pekka, a friend forwarded me a sipping draft for transfer which I also found useful (and maybe others will too...):
http://www.ietf.org/internet-drafts/draft-ietf-sipping-cc-transfer-03.txt thanks, Joel --- Spencer Dawkins <[EMAIL PROTECTED]> wrote: > Hi, Joel, > > > Hi all, > > > > In RFC 3515, section 2, second paragraph, it states, "Unless stated > > otherwise, the protocol for emitting and responding to a REFER > > request > > are identical to those for a BYE request in [1]." [1] is RFC 3261. > > > > In RFC 3261, section 15.1.1, it states, "The UAC MUST consider the > > session terminated (and therefore stop sending or listening for > > media) > > as soon as the BYE request is passed to the client transaction." > > > > So, if my UA sends a REFER, does it automatically stop > > sending/receiving RTP? > > I THINK what RFC 3515 is trying to say is, "the protocol for deciding > > whether you have to increment CSeq or send through a proxy, etc. is > identical to those for a BYE request used as an example in Section 16 > > of [1]", but I agree that the 3515 text is confusing on this point. > > I note that RFC 2976 (INFO) has text like > > 2.4 Behavior of SIP User Agents > > Unless stated otherwise, the protocol rules for the INFO > request > governing the usage of tags, Route and Record-Route, > retransmission and reliability, CSeq incrementing and message > formatting follow those in [1] as defined for the BYE request. > > and > > 2.5 Behavior of SIP Proxy and Redirect Servers > > 2.5.1 Proxy Server > > Unless stated otherwise, the protocol rules for the INFO > request at a proxy are identical to those for a BYE request > as > specified in [1]. > > 2.5.2 Forking Proxy Server > > Unless stated otherwise, the protocol rules for the INFO > request at a proxy are identical to those for a BYE request > as > specified in [1]. > > 2.5.3 Redirection Server > > Unless stated otherwise, the protocol rules for the INFO > request at a proxy are identical to those for a BYE request > as > specified in [1]. > > So I think 3515 is trying to say the same thing in one sentence, but > that sentence is just too overloaded... > > Spencer > > > _______________________________________________ > 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
