Aravind, Thanks for your report - your analysis looks correct - I've raised Sprout Issue 1514 to cover correcting this - https://github.com/Metaswitch/sprout/issues/1514
Looking at the code, I believe that the options will only get stripped if the MMTel application server is being invoked, as that looks to be the only place we will fully parse and control the Privacy header options. If you don't need this function, then removing the MMTel application server might be a workaround for you. We don't normally use this MMTel application server in production environments. You should be able to prevent this being invoked by modifying the subscriber's configured initial filter criteria. If you aren't running the MMTel Application Server, can you clarify the scenario in which you are seeing the Privacy options being modified by Clearwater? Richard From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Shirabur, Aravind Ashok (CMS) Sent: 22 August 2016 08:09 To: Clearwater@lists.projectclearwater.org Subject: [Project Clearwater] Privacy header delimiter ',' Hi, We are testing project clear water (clearwater-infrastructure 1.0-160518.173307) , we find that "," is used as delimiter for separating multiple values of the Privacy header (example: "Privacy: id, user, history"). As per RFC-3323 (https://www.ietf.org/rfc/rfc3323.txt) privacy header values must be separated by ";". [cid:image001.jpg@01D1FC6C.B0A81CD0] Impact of this multiple Privacy header like "Privacy: id;user;history"; this has been removed by the Clearwater IMS network. Can you please comment on if this observation is correct ? Thanks Aravind
_______________________________________________ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
