Re: [reSIProcate] DUM and Privacy

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

Thanks for reporting this.  I think I see what's causing it.  

Are you able to try out the following fix and see if it works for you?

Modify the following code around line 1000 in dum/Dialog.cxx

   if (mDialogSet.mUserProfile->isAnonymous())

   {

       request.header(h_Privacys).push_back(PrivacyCategory(Symbols::id));

   }

to be

   if (mDialogSet.mUserProfile->isAnonymous())

   {

       request.remove(h_Privacys);

       request.header(h_Privacys).push_back(PrivacyCategory(Symbols::id));

   }

Thanks,

Scott

On Tue, Apr 18, 2017 at 6:13 AM, Jan Granqvist via resiprocate-devel <resiprocate-devel@xxxxxxxxxxxxxxx> wrote:

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@resiprocate.org
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

---------- Forwarded message ----------
From: Jan Granqvist <jan_granqvist@xxxxxxxxx>
To: "resiprocate-devel@xxxxxxxxxxxxxxx" <resiprocate-devel@xxxxxxxxxxxxxxx>
Cc: 
Bcc: 
Date: Tue, 18 Apr 2017 10:13:17 +0000 (UTC)
Subject: DUM and Privacy

Hi all,

Noticed an undesirable effect making an outbound call when the user profile returns true for method isAnonymous, that is DUM adds the privacy header to the INVITE signal.

For each following reINVITEs in the dialog method Dialog::makeRequest keeps adding another 'id' to the privacy header.

I'm using version 1.10.0.

BR

/Janne