PDA

View Full Version : Anonymous, Restriced & blocked calls not being blocked



MisterEd
11-08-2011, 05:08 PM
This has been happening for the last couple weeks. Calls marked anonymous and restricted are not being blocked. There has never been any problem with these type calls being blocked before. I am assuming most of them are political robo-dialed calls but they never got through in the past. All settings in vPanel are correct (same as they have been for 2 years).

Anyone else having this problem? With the political season in full swing I am getting a lot of these calls. Very annoying.

I have submitted a ticket but curious if anyone else is having this problem.

tritch
11-08-2011, 11:13 PM
My father had a similar issue a couple of months ago even though vPanel was setup to block such numbers under the Features tab. It appears these callers are really not blocking their numbers but instead spoofing the CID field with a name instead of number. Very tricky!

On his phone CID display, these type of calls showed up as:

Restricted in the CID field instead of a phone number
Unavailable in the CNAM field

He submitted a ticket and they simply applied a incoming call route rule to block "Restricted". I learned something new, I didn't know you could put a name in the number field instead of phone number.

Go to vPanel, Features tab, select Call Routes, and apply an incoming call route like this:

Call Route Type: Phone Number
Custom Number: Restricted (type a name here instead of phone number)
Call Route Action: your choice

I'm not sure about your Anonymous calls but if they are showing up on your CID display the same way above, then I would try setting up a similar call route rule as well.

robhouston
11-09-2011, 06:27 AM
Yes, I'm having the same problem. I haven't yet opened a ticket, but you've reminded me that I need to do so.

MisterEd
11-09-2011, 11:06 AM
Interesting Tip ... didn't know you could use a name in the field. Thanks.



My father had a similar issue a couple of months ago even though vPanel was setup to block such numbers under the Features tab. It appears these callers are really not blocking their numbers but instead spoofing the CID field with a name instead of number. Very tricky!

On his phone CID display, these type of calls showed up as:

Restricted in the CID field instead of a phone number
Unavailable in the CNAM field

He submitted a ticket and they simply applied a incoming call route rule to block "Restricted". I learned something new, I didn't know you could put a name in the number field instead of phone number.

Go to vPanel, Features tab, select Call Routes, and apply an incoming call route like this:

Call Route Type: Phone Number
Custom Number: Restricted (type a name here instead of phone number)
Call Route Action: your choice

I'm not sure about your Anonymous calls but if they are showing up on your CID display the same way above, then I would try setting up a similar call route rule as well.

MisterEd
11-09-2011, 11:07 AM
Interesting Tip ... didn't know you could use a name in the field.&nbsp; Thanks.<br><br><br>
My father had a similar issue a couple of months ago even though vPanel was setup to block such numbers under the Features tab. It appears these callers are really not blocking their numbers but instead spoofing the CID field with a name instead of number. Very tricky!<br>
<br>
On his phone CID display, these type of calls showed up as:<br>
<br>
<strong>Restricted</strong> in the CID field instead of a phone number<br>
<strong>Unavailable</strong> in the CNAM field<br>
<br>
He submitted a ticket and they simply applied a incoming call route rule to block "Restricted". I learned something new, I didn't know you could put a name in the number field instead of phone number.<br>
<br>
Go to vPanel, Features tab, select Call Routes, and apply an incoming call route like this:<br>
<br>
Call Route Type: Phone Number<br>
Custom Number: <strong>Restricted</strong> (type a name here instead of phone number)<br>
Call Route Action: your choice<br>
<br>
I'm not sure about your Anonymous calls but if they are showing up on your CID display the same way above, then I would try setting up a similar call route rule as well.

MisterEd
11-11-2011, 08:27 PM
These are calls I am getting that I assume should be blocked:



http://img845.imageshack.us/img845/9209/p1010221kz.jpg

tritch
11-12-2011, 12:25 PM
It looks like they are spoofing the CID display with Unavailable. If you set up an incoming call route using the name Unavailable as noted in my earlier post, do you still get these type of calls? If so, then I would open a support ticket.

It should look something similar to the highlights in my attachment.

MisterEd
11-12-2011, 01:11 PM
I know how. I did.

Thanks.

Tooth
08-07-2012, 12:37 PM
My father had a similar issue a couple of months ago even though vPanel was setup to block such numbers under the Features tab. It appears these callers are really not blocking their numbers but instead spoofing the CID field with a name instead of number. Very tricky!

On his phone CID display, these type of calls showed up as:

Restricted in the CID field instead of a phone number
Unavailable in the CNAM field

He submitted a ticket and they simply applied a incoming call route rule to block "Restricted". I learned something new, I didn't know you could put a name in the number field instead of phone number.

Go to vPanel, Features tab, select Call Routes, and apply an incoming call route like this:

Call Route Type: Phone Number
Custom Number: Restricted (type a name here instead of phone number)
Call Route Action: your choice

I'm not sure about your Anonymous calls but if they are showing up on your CID display the same way above, then I would try setting up a similar call route rule as well.

Thanks for this tip, tritch. Its helping to prevent those annoying telemarketer and political robo calls from getting through.

voipinit
08-08-2012, 02:47 PM
I believe VOIPo call routes block by alphanumeric characters in the CID field, therefore if you make a rule with "unavailable", it will not be blocked as it is in the CNAM field and not the CID. Adding a call route of "restricted" may work since this is in the CID field.