Call Privacy

[Matthew Main]

Hey all,

I am either being an idiot or not seeing the option, I have a number of exts that are required to call out anonymously, now I know the *67 works but want to know if there is a way to turn on call privacy for each ext individually for every call.

Found a few guides to mod the default caller id, but to no avail.

Any help would be greatly appreciated.

Kr

Matt

 

[whut]

You have a few options. If you want extension 10102 to have privacy turned on all of the time you can build a dialplan looks like this.




Adjust the condition sip from user to your desired extension or group of extensions.

You could build an outbound route that runs before the final outbound route and is a continue = true

 

[agree]

No need for dialplan the simplest is to use extension settings.

 

[Matthew Main]

No need for dialplan the simplest is to use extension settings.

View attachment 3546

This did not work.

 

[Matthew Main]

You have a few options. If you want extension 10102 to have privacy turned on all of the time you can build a dialplan looks like this.

View attachment 3545


Adjust the condition sip from user to your desired extension or group of extensions.

You could build an outbound route that runs before the final outbound route and is a continue = true

No option to add the conditions on my version of Fusion 5.1.0 RC1

 

[whut]

Every version of fusion has the ability to add any number of conditions to a dialplan.

 

[Matthew Main]

I figured out how to get the dial plan in, but I can't get it to work, I have reloaded XML, but it's not picking it up.

 

[DigitalDaz]

Which bit is not working? eg, is the privacy id set in the outbound invite, etc?

 

[Matthew Main]

Yeh I set the dial plan as whut as described but its not acting in anyway, still showing outbound / emergency cli

 

[agree]

What do you mean it doesn't work? Does the sip message show that privacy is set? It is up to the upstream carrier to handle the private call. If they don't handle it properly the caller ID will still show up.

 

[Matthew Main]

Privacy is not being marked in the invite.

 

[agree]

Privacy is not being marked in the invite.

Can you share the INVITE message and the logs?

 

[whut]

You might also share what the privacy dialplan looks like that you crafted.

 

[Matthew Main]

I was playing with it, but I did complete the way whut suggested and still no luck.

 

[Lim00n]

Is your call hitting the dialplan? You can see in the fs_cli. Is your caller_id_name anonymous? Is it possible another dialplan is setting the Privacy to none later?

 

[Matthew Main]

Does not look the call is even touching the dial plan. I have setup a stable branch box to test further.

 

[whut]

I was playing with it, but I did complete the way whut suggested and still no luck.

View attachment 3577


View attachment 3578

The first item I see that is probably causing this dialplan to not work is the order set at 200. The order needs to be a lower number than your outbound route. Otherwise, this dial plan will never be executed. Your existing outbound route is probably order 100, or similar. Change your new dial plan to order 99, 98, 97, etc. so it can be executed.

 

[Matthew Main]

Good to know!

I will make the changes and test

 

[Matthew Main]

So the dial plan is now working, but the From is not being set correctly. Meaning that a carrier that is pulling the CLI from the FROM is still displaying the number.

its currently <sip:host@domain> it should be <sip:anonymous@anonymous.invalid>

Does anyone have any ideas?