Anonymous calls not respected

[anco73]

We have a registered a SIP trunk. Calls coming in to 3CX, run true a call flow app, and go out on the same SIP trunk. We can manage the invite by setting the Inbound and Outbound rules on the trunk settings, but unfortunately anonymous is not working as expected:

The invite into 3CX we see as follows:
Remote-Party-ID: Anonymous <sip:31xxxxxxxxx@sip>;party=calling;privacy=full

The invite out of 3CX the "privacy=full" is missing.

So the callers number is displayed to the called party, however is is calling anonymous.

Anybody any idea how we can solve this?

 

[AWS2P]

Your goal is to make ougoing calls anonymously all the time?
if so , why not setting this on your SIP provider side?

Anonymous calls are not liked by lot of callee or even filtered or dropped before reaching other end, so is it a good idea ?

 

[anco73]

No we need CLI when caller is "not" calling anonymous, so this is not a good idea

 

[anco73]

Some additional info. Hopefully somebody can help out here?

Invite send into 3CX contains the privacy flag:
Remote-Party-ID: Anonymous <sip:[email protected]>;party=calling;privacy=full

Invite out of 3CX contains no privacy flag:
Remote-Party-ID: <sip:[email protected]>;party=calling

Does anybody has any idea how to respect this privacy flag and send it out?

Thanks.