dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
12
adatech
join:2010-04-23

adatech to MartinM

Member

to MartinM

Re: [Voip.ms] CallerID filter not working

said by MartinM See Profile
Is there a reason why you want to filter spam a phone book? Wouldn't a import feature in the filtering section be a cleaner solution? I can understand the appeal of a phone book group to apply filtering rules such as time conditions, ivr etc but for spam, not sure, unless there's something I am missing? If you could "enlighten me" that would be great Thanks

:

It's mostly a matter of elegance. Right now, for example, I have about 20 different filters -- the majority of which are individual spam entries. When I get a telemarketing call, or a persistent mis-dial, I add a new filter sending it to a "No Service" message.

What would be easier, at least in my view, would be to have a filter that operated on a "Spam" group in my Phone Book. Then, you just have to add the number to the group, and voila -- instant filtering.

I understand that some may see this as cluttering up their Phone Book, which I think is an understandable objection. But I can also see the benefit of filtering groups in other contexts. For example, you could have a "Close friends" or "Work" group with a set of numbers, and operate a filter based on that (e.g., calls from numbers in the work group go to voicemail after 5:00PM).

I guess the bottom line is that, in my personal work-flow, I see the spam filtering aspect as a by-product of a useful feature (like you mentioned -- time conditions for groups of numbers, etc.) I think a group feature in the phone book (independently useful for sorting large phone books) and the ability to filter on groups (useful for many things, one of which is spam filtering).

Alternatively, I could see the benefit of a specific SPAM blacklisting feature. This could be implemented via the web portal (add a number, it gets blacklisted on your account) and/or through star-codes (*XX adds last inbound caller ID to the blacklist). Long-term, and I'm sure much more complicated, this could be used to start building some sort of system-wide grey-listing ability, with users having the option of filtering (e.g., to voicemail) caller ID's that have been reported as SPAMy by other Voip.ms users.

That got really long, sorry about that! Just some ideas for future features that would improve my workflow, and possibly others.


ctaranto
join:2011-12-14
MA

ctaranto

Member

I'll +1 what adatech is saying.

While grouping doesn't provide any additional "feature set", it makes life a heck of a lot easier when adding numbers to block, whitelist, etc, especially when adding failover options to each entry manually.

For example, I have 32 entries in my CallerID filter for spam numbers (System Disconnect). They are scattered throughout my entire list. It would be great to have a single entry, SPAM, apply the appropriate filters to it, and separately add a bunch of numbers to the group. Likewise for whitelisting family, or restricting calls from colleagues, etc.

-Craig

horacebork
Premium Member
join:2011-03-17
09001

1 edit

horacebork to adatech

Premium Member

to adatech
+1 on adatech. my caller id filter is short at the moment, but growing.
i put in a feature request a couple weeks ago on exactly this topic:

allow multiple numbers added to a specific filter for spam calls.

-------------
is there a difference from the spammer's point of view if they get 'system: number disconnected' or 'system: number not in service'?
i'm trying to figure out what would be the best reply to spammers.
i feel a busy signal tells them the number is valid, just unavailable.
Radar73
join:2008-01-20
Ajax, ON

Radar73 to adatech

Member

to adatech
I also like this.