Re: [reSIProcate-users] Does "transport=TCP" in Contact Header is case-sensitive?

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

In general URI parameters are not case sensitive.  There is text on page 155 of RFC3261 that illustrates this:

The URIs within each of the following sets are equivalent:

sip:%61lice@xxxxxxxxxxx;transport=TCP
sip:alice@xxxxxxxxxxx;Transport=tcp

The base grammar however shows the transport parameter in lowercase, so using a lowercase transport parameter is likely to give you a higher level of interoperability with endpoints that ignore the fact that uri parameters are not case sensitive.

I think it is a good idea to change resip to use lowercase transport types in the transport URI parameter - any objections to this?  Also I found a couple of cases in resip where we don't properly to a case insensitive parse of the transport parameter and we are looking for upper case only - I'll fix these.

Scott

On Fri, Jan 14, 2011 at 7:59 PM, Karlsson <boost.regex@xxxxxxxxx> wrote:

Hi, I noticed that the "TCP" is upper-case in the "Contact" header once TCP transport using, in RFC standard does it case-sensitive ?

REGISTER sip:sip.example.com SIP/2.0
Via: SIP/2.0/TCP 192.168.1.168:7545;branch=z9hG4bK-d8754z-882a07326842fc18-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:137244491822@xxxxxxxxxxxxx:7545;rinstance=405113f40e6faed4;transport=TCP>

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/