*67 Witholding my Caller ID

[andysiddell]

Forgive me if this has been covered elsewhere, but I couldn't find anything recently about this issue.

I am using FPL with an Elastix phone server. I have one Bell line and one FPL attached to the server. I have the dial strings configured to accept *67 before a dialled number so that it will block my caller ID information. This works perfectly for my Bell line, but although I see people saying in this forum that by prefixing a call with *67 on FPL it will withold my Name & Number, this is not the case.

My caller ID information still comes up on the other person's phone.

Can anyone give me any helpful information on what I need to do to make it work?

Thanks

Andy

[FONGO_steve]

Hi Andy,
At present time we do not support caller-ID blocking on our service. There's a couple posts here that explain in detail why, but long story short, a lot of people were abusing this with their free numbers.

We may or may not add this again in future, but right now, it's not supported. Sorry for any inconvenience.

[cu2o2o2]

Forgive me if this has been covered elsewhere, but I couldn't find anything recently about this issue.

I am using FPL with an Elastix phone server. I have one Bell line and one FPL attached to the server. I have the dial strings configured to accept *67 before a dialled number so that it will block my caller ID information. This works perfectly for my Bell line, but although I see people saying in this forum that by prefixing a call with *67 on FPL it will withold my Name & Number, this is not the case.

My caller ID information still comes up on the other person's phone.

Can anyone give me any helpful information on what I need to do to make it work?

Thanks

Andy

You should confirm that *67 is the feature code of Elastix for blocking caller ID. I already gave up on Asterisk-based ip-pbxes (Trixbox, Elastix and PIAF [oh, how I miss the IVR, phonebook and call recording features did I mention DISA? ]) because of security issues and constant attack of netbots on my phone server, therefore I can not verify it for you.

Depending on how you configured your Outbound and Trunk dialing patterns, dialing a star feature code before a phone number may or may NOT work.

[andysiddell]

It's a shame that because of the actions of a few, the majority of sensible users have to suffer.

My initial plan was to use FPL for a few months and then ditch my Bell line completely.

However, I pay for an unlisted number with Bell and do make use of *67 from time to time.

I will have to wait and see if you decide to offer this feature again before I decide which direction I want to go with my phone service.

[FreePhoneUser]

My ATA seems to randomly alternate between sending my Caller ID and not. Right now anyone I call sees "unknown".

[SirTaki]

FPL-steve wrote:

Hi Andy,
At present time we do not support caller-ID blocking on our service. There's a couple posts here that explain in detail why, but long story short, a lot of people were abusing this with their free numbers.

We may or may not add this again in future, but right now, it's not supported. Sorry for any inconvenience.

That means, I cannot use *67 to prevent my number from being displayed?! Sorry, to me that is a deal breaker, and you just helped me make decision whether or not I should spend $50 dollars to buy the configuration file.

[Ice]

Back to this... up until recently (last few months?), *67 allowed me to block my outgoing caller id and re-endabled with *82.
Now it doesn't, and I'm wondering if we can request this feature to be enabled again? I miss it!

[FONGO_kris]

Ice, please see this topic for more details, http://forum.freephoneline.ca/viewtopic ... 98&start=0 and for a more concise to-the-point answer, see here: http://forum.freephoneline.ca/viewtopic ... 383#p11383.

Please also post any further correspondence in this thread as it is the most complete... Also this one is locked