Hide CID for specific extensions (Flowroute SIP Trunk)

[Anthony R]

Hi team,

We're trying to hide our caller id when placing some outbound specific calls, nevertheless, calls are being forbidden.

We've tried the *5 method but the call isn't going out, e.g. calling to 1 234 456 7890 and dialing *5 1 234 456 7890.



So, we tried on the outbound rules apart putting the word anonymous or unavailable, but it also didn't work.



So we decided to contact flowroute and they responded the following:

"As part of ongoing efforts to reduce fraud and improve call authentication, regulations such as STIR/SHAKEN have been implemented. These protocols require calls to contain formatted values according to the E.164 standard, which includes the full 11-digit number (1 + 10 digits). Using the correct number format ensures that your calls pass authentication checks, preventing potential call blocking or misrouting, and helps your calls complete successfully.

STIR/SHAKEN protocols state that all outbound CallerIDs must contain a valid/working phone number in the PAI: Header (P-Asserted-Identity Header). So if you wanted to mask your CID or show all calls as "Anonymous," you would still need to configure your phone system to include a number in the actual packets. And according to our records, both of these calls are missing that PAI: Header (P-Asserted-Identity Header)".



And actually, I don't know what to edit, add or configure in the 3CX phone system to do that they're missing.

Have anyone else had this issue? How can I solve it?

Thanks in advance,
Anthony R.

 

[YiannisH_3CX]

Hello @Anthony R

Thank you for reporting. It seems Flowroute made some changes without letting us know which broke anonymous calls. We will look into it and make the necessary changes to account for this.

 

[Anthony R]

Hi Yiannish,

Thanks for replying my post.

I hope you guys can work back together and can account this, for some companies their privacy is also very important.

Please keep us posted, and thanks for your kindly support in advance.

Best,
Anthony R.

 

[Anthony R]

Hello @Anthony R

Thank you for reporting. It seems Flowroute made some changes without letting us know which broke anonymous calls. We will look into it and make the necessary changes to account for this.

Hi YiannisH,

I hope you'll be doing great.

Is there any update about this?

According to Flowroute:

"The FCC requires all voice service providers in the United States to be STIR/SHAKEN compliant. So we're not sure why 3CX would claim to not be aware of this".

Kind regards,

 

[YiannisH_3CX]

Is there any update about this?

If you have not already update your system to Update 6. We released a template update for Flowroute to fix another issue and that also includes the fix for this as well.
You will need to recreate your trunk though with the new template.

"The FCC requires all voice service providers in the United States to be STIR/SHAKEN compliant. So we're not sure why 3CX would claim to not be aware of this".

Yes the providers need to be STIR/SHAKEN compliant but how each provider does it is different. Providers use different SIP headers or SIP fields so when they make a change they need to inform us.

 

[Anthony R]

Hi Yiannish,

I followed your instructions, updated the 3CX to v6.



I deleted and readded the Flowroute trunk:





Then I made a regular call, it was made successfully, then I repeated it using *5 and it failed.





Did I do something wrong or incorrectly? Thanks for all your assistance in advance.

Best regards,
Anthony R.

 

[YiannisH_3CX]

Please navigate to the options tab of your trunks settings. Do you see the "Public IP in SIP via Header" option?
If so then add your public IP to that option. Save and try again.

If not navigate to System / Updates and look for updates. Do you see the Flowroute template? If so then download it.

 

[Anthony R]

Hi Yianish,

I've added my public IP as suggested.


I've also checked system updates,


I dialed the star dial *5 + number and now the call goes through.



Nevertheless, I'm still seeing the Call ID on the receiver when the call is done and not the word Unknown/Anonymous or just the call ID hidden.




I tried implementing an outbound rule and putting Unknown/Anonymous but same thing that in the past, the call is being forbidden.



Should I do something different on the outbound rule? I know we're getting close, but I still don't get the desired output.

Thanks for all the help you've been providing us.

Sincerely,
Anthony R.

 

[YiannisH_3CX]

We implemented the change as requested by Flowroute. Their suggestion was to only add the "privacy: id" header in the Invite and and let them anonymize the call so this is what we are doing.
You need to speak to them again and ask them why this is not showing as Anonymous.