"Bob Penfield" <[EMAIL PROTECTED]> wrote:
> In general, dialog initiating requests and target refresh (in-dialog) > requests (and non-failure end-to-end responses) always carry the remote > target. There is no special case for in-dialog requests. The rules for > whether or not a Contact header is included do not depend on whether the > request is "in-dialog" or not. > > INVITE requests and 1xx/2xx (except 100 Trying) responses MUST have a > Contact header whether its an initial INVITE or a re-INVITE (even if it is > not changed). Other target refresh requests (UPDATE, SUBSCRIBE, and NOTIFY) > also require a Contact header in the request and non-failure responses. So if I establish an INVITE with Contact URI A and at some point later in the dialog send an INVITE with Contact URI B then that's a target refresh request? Put another way, the UAS knows the UAC has moved because the Contact in the UAC's INVITE differs from the UAS's dialog's remote URI? (Like in RFC 3665 section 3.7) frank _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
