> As we know a dialog is a peer-to-peer SIP relationship > between two UAs that persists for some time.
RFC 3261 section 6 provides the complete definition. "Dialog: A dialog is a peer-to-peer SIP relationship between two UAs that persists for some time. A dialog is established by SIP messages, such as a 2xx response to an INVITE request. A dialog is identified by a call identifier, local tag, and a remote tag. A dialog was formerly known as a call leg in RFC 2543." > 1.Dialog is identified with combination of TO, > FROM tag and call-id, REGISTER method also contains > TO, FROM tag and call-id so can we consider it > as a dialog ID for REGISTER method? REGISTER is not a dialog creating request. However since RFC 3261 section 10 indicates to use the same Call-ID with higher CSeq when refreshing the binding, some refer to this behavior as a pseudo dialog. I assume that your question was not asking about how to behave if REGISTER is unexpectedly received containing a To tag. > 2.Is REGISTER method is a dialog oriented? RFC 3261 section 10.2: "A REGISTER request does not establish a dialog." RFC 3261 section 12.1: "Within this specification, only 2xx and 101-199 responses with a To tag, where the request was INVITE, will establish a dialog." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
