Encoding of RCS-e capabilities in Contact Header

[GoogleCodeExporter]

Current code codifies capabilities in Contact Header repeating the feature tag:
Contact: 
XXXX;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.im";+g.3gpp.
iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.ft"

This is against SIP RFC3261, that clearly states that

"Even though an arbitrary number of parameter pairs may be attached to a header 
field value, any given parameter-name MUST NOT appear more than once."

RFC 3840 and 3GPP TS 24.229 (section 7.9.3) mandate the format of the feature 
tags: the value MUST be separated by "," (and then probably encoded using the % 
format).

Example, using an example given the RFC3840, this is what the RFC3840 says is 
the proper way to encode a "methods" tag:

Contact: <sip:user@host.example.com>;audio;video
     ;actor="msg-taker";automata;mobility="fixed"
     ;methods="INVITE,BYE,OPTIONS,ACK,CANCEL"

This is what we the client would be doing:

Contact: <sip:user@host.example.com>;audio;video
     ;actor="msg-taker";automata;mobility="fixed"
     ;methods="INVITE";methods="BYE";methods="OPTIONS";methods="ACK";methods="CANCEL"

I think this formatting is against IARI 3GPP and RFC, and also against basic 
SIP formatting rules.

Original issue reported on code.google.com by josemre...@gmail.com on 24 May 2011 at 4:47

[GoogleCodeExporter]

Thanks for your feedback
We plan to correct it in the next release (2.2.5, end of May)

Original comment by jmauffret@gmail.com on 25 May 2011 at 12:08

• Changed state: Started

[GoogleCodeExporter]

Original comment by jmauffret@gmail.com on 31 May 2011 at 8:55

• Changed state: Fixed