Dale,
Not sure if I read your comment right, but RFC3261 12.2.1.2 says
When a UAC receives a 2xx response to a target refresh request, it
MUST replace the dialog's remote target URI with the URI from the
Contact header field in that response, if present.
It does not say anything about 1xx responses here though...Regards,Jeroen
[EMAIL PROTECTED] wrote:
From: Nina Garaca <[EMAIL PROTECTED]>
Q1: Should I expect that these responses have a Contact header?
As Paul says, if it didn't have a Contact header, it couldn't
establish a dialog.
Q2: If they do so, should the remote target of the dialog be
refreshed by that Contact at the side that has received that 1xx
response and should the remote target of the dialog be refreshed by
the Contact in the INVITE request at the side that has received
that INVITE?
Responses are not "target refresh requests", so they don't change the
target address at their end of the dialog. But of course, the
responses to the dialog-initiating request establish the initial
target address.
Q3: If not, should the remote target of the dialog be refreshed by
the Contact in the INVITE request
at the side that has received that INVITE and has sent dialog
establishing 1xx response?
RFC 3261 section 12.2:
INVITE, the only target refresh request defined is re-INVITE (see
Section 14). Other extensions may define different target refresh
requests for dialogs established in other ways.
Dale
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
