On 08.02.2010 17:48, zabi wrote:
> Dear All,
>
> If the REQUEST_URI/ TO / FROM /CONTACT has escaped sequence, does the
> response have to have the same escaped sequence or it may have its
> parsed values.
>
> For e.g if the username in sip request had b%[email protected].
>
> can the response have [email protected]????
Zabi,
There's no Request-URI in _response_. Contact has other meaning, check
paragraph 8.1.1.8 in RFC 3261.
As to From/To see RFC 3261 8.2.6.2 Headers and Tags:
The From field of the response MUST equal the From header field of
the request. The Call-ID header field of the response MUST equal the
Call-ID header field of the request. The CSeq header field of the
response MUST equal the CSeq field of the request. The Via header
field values in the response MUST equal the Via header field values
in the request and MUST maintain the same ordering.
If a request contained a To tag in the request, the To header field
in the response MUST equal that of the request. However, if the To
header field in the request did not contain a tag, the URI in the To
header field in the response MUST equal the URI in the To header
field; additionally, the UAS MUST add a tag to the To header field in
the response (with the exception of the 100 (Trying) response, in
which a tag MAY be present).
Also about CANCEL request: 9.1 Client Behavior
The following procedures are used to construct a CANCEL request. The
Request-URI, Call-ID, To, the numeric part of CSeq, and From header
fields in the CANCEL request MUST be identical to those in the
request being cancelled, including tags. A CANCEL constructed by a
client MUST have only a single Via header field value matching the
top Via value in the request being cancelled. Using the same values
for these header fields allows the CANCEL to be matched with the
request it cancels (Section 9.2 indicates how such matching occurs).
So To and From should be universally the same.
--
Sincerely,
Andrew Pogrebennyk
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors