16 May
2014
16 May
'14
9:15 p.m.
Thanks for this information, clear with comparison. However, more
specific to what I am looking for:
If I add in INVITE:
Record-Route: <sip:1.2.3.4;abc=XYZ>
Is allowed to the other party to set next header in BYE?
Route: <sip:1.2.3.4;abc=xyz>
Cheers,
Daniel
On 16/05/14 19:56, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
For a specific example, is it allowed that the
value of a parameter in
contact header uri is changed to upper/lower case when building the
sequential request (so this appears in request uri)? Same would be for
Recor-Route uri parameter that would appear later in Route headers...
i found this
from rfc3261:
19.1.4 URI Comparison
...
• Comparison of the userinfo of SIP and SIPS URIs is
case-sensitive. This includes userinfo containing passwords or formatted
as telephone-subscribers. Comparison of all other components of the URI
is case-insensitive unless explicitly defined otherwise.
and
7.3.1 Header Field Format
...
When comparing header fields, field names are always
case-insensitive. Unless otherwise stated in the defi- nition of a
particular header field, field values, parameter names, and parameter
values are case-insensitive. Tokens are always case-insensitive. Unless
specified otherwise, values expressed as quoted strings are case-
sensitive.
and example:
Content-Disposition: session;handling=optional
is equivalent to
content-disposition: Session;HANDLING=OPTIONAL
-- juha