[Freeswitch-users] Problems with privacy settings on invite

[Vallimamod Abdullah]

Hi,

You can manage the PID and privacy headers manually with something like this:

bridge {origination_uuid=...,sip_cid_type=none,sip_h_P-Asserted-Identity=sip:499132xxxxx at 88.198.223.120,sip_h_Privacy=id}sofia/...

You can add "sip_from_uri=sip:Anonymous at Anonymous.invalid" if the from header is not as you want it.

You don't need to create a new profile for every carrier, just the corresponding gateway. Even if there is no registration, you can monitor the gateways with sip options and do failover if needed. In your case, the gateway also allows you to define "caller-id-in-from" parameter which tells freeswitch to not use the pid as the outgoing from. But the same is achieved with the "sip_cid_type=none" setting above.

Best Regards,
-- 
Vallimamod Abdullah
VOIP Consultant
vma at vallimamod.org
.

> On 6 Feb 2017, at 10:50, Christoph Russow <russow at emtex.de> wrote:
> 
> Hi,
> 
> it seems that one of our carriers sees the number in the FROM: field
> (which freeswitch pulled from inbound P-Asserted-Identity Header) and
> forwards them to the enduser.
> 
> Inbound is:
> From: "Anonymous" <sip:Anonymous at Anonymous.invalid>;tag=gK0d356f75
> P-Asserted-Identity: <sip:499132xxxxx at 217.110.38.229:5060>
> 
> Outbound is:
> From: "Anonymous" <sip:499132xxxxx at 88.198.223.120>;tag=eDe24j5Hp5cvm
> P-Asserted-Identity: "Anonymous" <sip:499132xxxxx at 88.198.223.120>
> 
> Wanted on Outbound:
> From: "Anonymous" <sip:Anonymous at Anonymous.invalid>;tag=gK0d356f75
> P-Asserted-Identity: <sip:499132xxxxx at 217.110.38.229:5060>
> 
> 
> So i now want to tell freeswitch either to make the outbound call totaly
> anonymous (how?) and i set the P-Asserted-Identity manually.
> 
> Or tell freeswitch to not pull the P-Asserted-Identity Contents into
> from field on the outbound call.
> 
> Do you mean Setting the origination_caller_id_number or sip_from_user to
> anonymous would work here? is it the preferred way for privacy?
> 
> Our Carriers don't require registering and so i did not see any
> advantage to create a profile for every carrier we start to use as it
> needs manual accessing the server and not only adding it into our
> database and let the scripts decide which one to use.
> 
> Best Regards
> Christoph
> 
> Am 03.02.2017 um 18:08 schrieb Vallimamod Abdullah:
>> Hi,
>> 
>> You can try to set origination_caller_id_number or sip_from_user variables in your bridge dial-string.
>> Normally, with "Privacy:id", the caller-id should appear fully restricted to the callee. Is it not the case?
>> 
>> Is there any specific reason why you do not define a gateway for your provider and dial by ip instead? 
>> If you define a gateway, you can set the caller-id-in-from param to use the inbound callerid in the from field of the outgoing call.
>> 
>> Best Regards,