Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Implemented *5 feature to call anonymous not compliant with regulations

Discussion in 'Ideas' started by Kay Reijnen, Jul 19, 2017.

  1. Kay Reijnen

    Jul 19, 2017
    Likes Received:
    Hi team,

    Due to regulations we are faced with issues not being able to dial-out using *5. This is due to the fact that TELCO's like ourselves do not allow to dialout without any CLI at all. In case of anonymous calling one should always send CLI with privacy header set on an external SIP trunk.

    This means that in my opinion using *5 should result in INVITE using regular CLI ruling within the configuration, by setting the number in the "P-Preferred-Identity", "P-Asserted-Identity" or "Remote-Party-ID" with an additional header "Privacy" with value "id". The "From" header can still be filled with value "Anonymous"
    This results in having the correct information below surface for regulatory reasons.

    In my opinion this should only be implemented on a SIP trunk level.

    Hope you guys can add this feature.
    3cx20 likes this.