2009/1/28 Brett Tate <[email protected]>: >> So is there any plan to revise the RFC 3725 based on REFER? > > RFC 3725 indicates the following: > "This document serves as a best current practice for implementing third party > call control without usage of any extensions specifically designed for that > purpose." > > Because of the above text, I doubt anyone would update RFC 3725 to use REFER. > However someone might eventually create a draft to fully document using > REFER (or another mechanism) as an alternative to the current RFC 3725 > approach.
Hi, that's not necessary at all as it's already documented in the same RFC 3515 (REFER method): http://tools.ietf.org/html/rfc3515#section-4.1 4. Examples 4.1 Prototypical REFER callflow Agent A Agent B | | | F1 REFER | |----------------------->| | F2 202 Accepted | |<-----------------------| | F3 NOTIFY | |<-----------------------| | F4 200 OK | |----------------------->| | | | | | |-------> | | (whatever) | |<------ | | | F5 NOTIFY | |<-----------------------| | F6 200 OK | |----------------------->| | | | | Here are examples of what the four messages between Agent A and Agent B might look like if the reference to (whatever) that Agent B makes is successful. The details of this flow indicate this particular REFER occurs outside a session (there is no To tag in the REFER request). If the REFER occurs inside a session, there would be a non-empty To tag in the request. Am I wrong? -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
