Solved Privacy: id Withheld Caller ID

[antechs]

We have an "unsupprted" sip trunk we use.

The provider has asked for the below value for withholding the caller ID to be passed to the VoIP provider.
They have referenced the below RFC3325 standard which uses a privacy type value.

Any ideas how I can get 3CX to do this?


https://www.ietf.org/rfc/rfc3325.txt
(Copied from above link section 9.3)

9.3 The "id" Privacy Type

This specification adds a new privacy type ("priv-value") to the
Privacy header, defined in [2]. The presence of this privacy type in
a Privacy header field indicates that the user would like the Network
Asserted Identity to be kept private with respect to SIP entities
outside the Trust Domain with which the user authenticated. Note
that a user requesting multiple types of privacy MUST include all of
the requested privacy types in its Privacy header field value.

priv-value = "id"

Example:

Privacy: id

Thanks in advance for any suggestions...

 

[leejor]

So...at the moment, *5 does not work for you?
https://www.3cx.com/community/threa...onymous-not-compliant-with-regulations.49894/

Who is the provider, what country?

 

[antechs]

Not for all calls automatically ...

 

[antechs]

Sorry uk AQL

 

[leejor]

So...to be clear.... it does work, if you use prefix *5, but you want your number blocked on all calls automatically?

Does your provider allow you to block, using a prefix, like 141, that BT uses?

 

[antechs]

Not tested and to be honest rather irrelevant as far as I am aware as I dial code cannot be used in the outbound rule. Yes I need all outbound calls to be witheld, no 141 is not available it has to be done by the value above (which as far as I can see from reading *5 sets the value above on a one off basis)

 

[cobaltit]

So if it's all calls can't they just set it globally on their end? The Privacy ID you speak of is designed to be for 'on-demand' blocking. Typically if you want the caller-id blocked for all calls the provider should be able to do that. Otherwise putting a bogus caller-id will sometimes translate as private or blocked.

 

[antechs]

That was my thinking, apparently not...will retry a bogus caller id, didn’t work previously and they just came back and said use the value of Privacy ID.

 

[antechs]

*5 doesn’t work either (tested this AM)

 

[antechs]

I have tried using *5, sadly this didn't work, this might be something to do with Dialplans or outbound rules however.

Equally have confirmed provider cannot put withheld on all calls and must be done by Privacy Type as per the RFC of which by all circumstances appears 3CX doesn't support the RFC standard on an all calls as an option or a change in the outbound parameters as far as I can establish.

I have confirmed also the provider will spoof practically any UK number so you can't put something "wrong" in the outbound caller ID box, and equally the word anonymous fails if used as the outbound caller ID

K/R
Rob Childs

 

[leejor]

If your provider will spoof any number, just put in all eights, or ones, or a single digit, something obviously not a valid phone number in the UK.

 

[antechs]

They require a valid number on the sending of the number apparently with the privacy ID flag which then "makes it private" when leaving the network.

Technically, the 000 option would work, however they would probably consider this to be deliberate spoofing in a negative nature and cease the account (I would if i was them!)

Thanks

 

[leejor]

Well, most providers should be able to block the number for you, on all calls . I'm a bit surprised that they don't allow a prefix to block on a per call basis, which could then simply be added in the outbound rules.
I'm always leery about blocking the caller ID on all calls, and not able to allow the number when required. These days with so many Robo-calls, i find that many people will consitantly ignore "Private" or :"withheld" type calls, and rightly so. Blocking a number tends to create suspicion about the originator.

 

[antechs]

couldn't agree more with most of the last message.
Sadly the client operates an environment where it would potentially be a risk to life if the caller ID was identified on inbound calls and therefore its not an option to disclose.

 

[leejor]

Is there a fax number, in the office, or, some other number, that is not normally monitored for incoming calls, that, while still a legitimate number, could be sent instead.

How about the number of that coin phone down the street?

What about a Pay-as-you-go mobile number, then change it every so often?

 

[antechs]

Sounds like many a good idea sadly neither would work lol. Spoofing is rather regulated even if the ability to spoof isn’t, you have to own the number. No fax sadly! Client wants withheld it seems regardless.

 

[leejor]

Yiou may have to wait for an answer from someone at 3CX as to whether there is a work-around.

 

[cobaltit]

3CX is standards compliant. This is an extension which is not required. And there is no waiting for 3CX. You can put in a feature request in the ideas section but everything that can be changed as far as the parameters is on the outbound parameters tab of the trunk. Nothing that you can change there will make your provider happy the only option is to put a SBC type device down in front to accomplish this.

 

[YiannisH_3CX]

Hello @antechs

I am sure that *5 will work with some adjustments in your outbound rules but as i understand it this will not help you as you will need to dial if for every outbound call.
I believe the easiest and fastest way to achieve this is to switch to a provider that has a dial code for Anonymous calls which you can add to your outbound rules or can display Anonymous permanently for your account.

 

[antechs]

Hi @YiannisH_3CX
Provider switch isn't an option.
I have however found a workaround while putting Anonymous in caller ID on the extension or the trunk doesn't work, I have been advised we can set both "From: Display Name" and "From: User part" to custom field and put "Anonymous" as the value.

Thanks for everyone's suggestions.