Caller-ID Block Not Working

[MikeD]

My outgoing caller-id block does not work. *67, *81, or any other code I try to use.

I've had my FPL number for some time now and the outgoing caller-id did not work from day 1. When I contacted tech support, I was told that it was up to how the call was routed and sort of hit-or-miss if the outgoing caller-id info went through or not. Similarly, tech support said that the incoming was also hit-or-miss although most of the time it works.

Anyone else experiencing the same problem?

[leper1983]

Yep i've been in the same boat since i got it but just learned to live without the blocking

[FONGO_kris]

Hey guys, I'll look into this tomorrow and see what i can uncover! Please email me (admin@freephoneline) for updates

[brentw]

Yep I have the same problem.
Never been able to block the caller-id.
I thought maybe it was my ATA but I use a PAP2-NA which is what FPL sells so that doesn't really make sense.

[MikeD]

Everything points to a problem at FPL's end so I would leave it up to them to remedy (I assume they read these posts - right?).

Not that I am trying to deter you from trying, but any time spent making any changes at your end would most likely amount to a waste of time and possibly lead to other problems.

[FONGO_kris]

We read these posts, yes. I'm the head technician here at Freephoneline.ca. Caller-ID with Freephoneline is sometimes misunderstood; Incoming should always work, if not than that is an issue we'll have to look into. Outgoing should also always work, unless there is a) a carrier issue, which is out of our hands more or less, b) The ATA is not communicating the Caller-ID properly (or CID Block is on, in which case it may present as Unknown or our BTN number).

[MikeD]

It's good to know someone at FPL is reviewing the bug reports here. It's also good to know that you're not the only one having a certain problem so you can rule out your own individual setup. I'm sure constructive feedback & info makes it easier for FPL to sort things out from their end too.

I agree with the fact that it is a low priority issue but it sure is a handy feature when it's working. I'll post back when I notice it has been resolved just to let you know your hard work is much appreciated.

[FONGO_kris]

You're welcome, and of course the more complaints - as any provider; the more attention it gets, and subsequently the quicker any issue resolved.

[MikeD]

"The squeaky wheel gets the grease."

[Pirate]

I'm sure it will get fixed sooner or later. Just give it some time. After all, pretty much ALL SUCCESSFUL businesses depends on CUSTOMERS / CLIENTS. Basically, we, as customers, PAY their paycheques.

[FONGO_steve]

when you dial *67, etc. how does it not work?
Does the call complete? What number to they see?
does the call not complete? error? etc?

I have no issues caller-ID blocking on my grandstream here on my desk, so this this seem to related to your device, or isolated to your specific account.

[brentw]

I try both *67 and *81 as listed in my PAP2T-NA settings under the Regional tab.

The call just goes through like normal and my number shows up.
There is no error or anything.
But it doesn't block the number at all.

In my syslog server it shows that the ATA recognizes the command.
[0]Off Hook
2. Report digit * (1)(40 ms)
2. Report digit 8 (1)(40 ms)
2. Report digit 1 (1)(40 ms)
[0]block cid per call

I just reconfirmed on my ATA that under the Line tab - "Block CID Serv:" is set to Yes.

Let me know if you would like the more detailed logs from syslog and I can send them through.

Brent

[redge]

same as brentw, *67 fails to block number from showing

it worked fine up until FPL posted it made changes re: CRTC compliance

I'm sure CRTC compliance includes the *67 capability to protect ones number from being given out against ones wishes.

please re-enable the *67 call blocking feature or let us know how to re-enable it on the pap2

it may also be nice to warn or notify users and potential users that this feature currently does NOT work so that they do not inadvertently or unknowingly give their number out when making calls.

Although it has been suggested in posts that it is not an important issue certainly there are those that rely on this privacy feature as very important.

thank you

[FONGO_kris]

it may also be nice to warn or notify users and potential users that this feature currently does NOT work so that they do not inadvertently or unknowingly give their number out when making calls.

This has not yet been isolated as a Freephoneline.ca issue - A bug maybe, but I can garuntee you we've not changed anything to disable this feature since as said Steves post above his CID Block is working on our Grandstream in the office, as well as my Cisco IP Phone, Thomson TG784, and my SPA3102.

All we can do now is pull logs from test calls you guys make, as well as sys logs from devices which have them to isolate the issue quicker.

Although it has been suggested in posts that it is not an important issue certainly there are those that rely on this privacy feature as very important.

Though I personally fail to see the relevance of CID block (why have a phone number when you're going to block it); I along with my other colleagues don't diminish the fact that other users rely on this feature. We're certainly going to try and isolate the issue as best we can and figure out a way to satisfy all of your needs.

[MikeD]

Though I personally fail to see the relevance of CID block (why have a phone number when you're going to block it)

If I owed you money and didn't pick up when you called, I'll bet you might consider blocking your caller-id before calling me again! Anyways, there are many legitimate uses for caller-id blocking that I won't go into detail about but it is one of the features FPL advertises.

I also don't think it is limited to specific users or configurations and is more likely to be at FPL's side. Perhaps internally at FPL it is working O.K., but I am sure it is more than the few that have posted here that it is not working for and I am sure we all don't have the same configuration.

I can tell you that I have made no changes to my setup from the time that it was working, but perhaps there has been a change at FPL that requires a change in my setup to make it work again?

[Pirate]

No use blocking #'s anymore cuz there are interfaces that you can install to UNBLOCK a number now. I tried out the interface on "www.trapcall.com" and it works great!! You can unblock all Blocked numbers!!

My outgoing caller-id block does not work. *67, *81, or any other code I try to use.

I've had my FPL number for some time now and the outgoing caller-id did not work from day 1. When I contacted tech support, I was told that it was up to how the call was routed and sort of hit-or-miss if the outgoing caller-id info went through or not. Similarly, tech support said that the incoming was also hit-or-miss although most of the time it works.

Anyone else experiencing the same problem?