 nunyaWho is John Galt?Premium,MVM
join:2000-12-23
O Fallon, MO
kudos:8
 ·Charter
 ·surpasshosting
 ·voip.ms
| [Voip.ms] Blocked calls getting through I use the VoIP.ms caller ID filtering extensively in lieu of my PBX blacklist. I like keeping the calls "off my system" as much as possible.
Today, a rather annoying local salesman, who won't take no for an answer, somehow got through. My first thought - perhaps he's calling from a different number.
So I look in the VoIP.ms CDR and the the CID filter - huh? The numbers match exactly, but the call still made it through.
As I mentioned, I use the filtering extensively. Is there a limit to the number of entries in the VoIP.ms filters?
As I recall, this is the first time something like this has happened.
--
If someone refers to herself / himself as a "guru", they probably aren't. |
|
jobr
join:2004-10-21
Halifax, NS | I'm not sure if there's a limit, but it shouldn't be hard to test. Try adding your own cellphone number to the filter list, then call the VoIP.ms number. Do you get through? |
|
nunyaWho is John Galt?Premium,MVM
join:2000-12-23
O Fallon, MO
kudos:8 Reviews:
·Charter
·surpasshosting
·voip.ms
| I figured out my mistake.
I have "local" numbers whitelisted. If someone calls from my service area of 636, 314, 217, or 573, the call goes straight through. All callers from other area codes get an IVR prompt. This stops about 80% of my unwanted calls.
The caller in this case is in the 314 area code, so his call is treated by the whitelist first.
Thinking logically, I thought the filter would handle specific numbers before wildcard numbers.
Guess I'll have to handle all local "blacklist" calls on my PBX.
--
If someone refers to herself / himself as a "guru", they probably aren't. |
|
Mangowww.toao.net
join:2008-12-25
Alberta
kudos:11 | Try whitelisting 314XXXXXXX instead of 314*; does that do what you want? |
|
nunyaWho is John Galt?Premium,MVM
join:2000-12-23
O Fallon, MO
kudos:8 | No, didn't work. |
|
PX EliezerPremium
join:2008-08-09
Hutt River
kudos:13 Reviews:
·callwithus
·voip.ms
·Optimum Voice
·Vitelity VOIP
·Gizmo5
| If you've created multiple custom call filters, the system will probably work from the "top down" and make a hit on the first match.
Your more specific rules should come before the more general rules.
For example, a blacklist for 314-555-5555 should come before (higher) than a whitelist for 314*
We know that in a similar call treatment system with a competitor, rules are prioritized from the top down.
Similarly, we know that ATA dial plans are prioritized from first to last, the first "match" will score a hit regardless of what comes later. |
|
nunyaWho is John Galt?Premium,MVM
join:2000-12-23
O Fallon, MO
kudos:8 Reviews:
·Charter
·surpasshosting
·voip.ms
|
For example, a blacklist for 314-555-5555 should come before (higher) than a whitelist for 314*
That's what I was assuming as well. One of the few things I remember from "Logic and Programming" during my college days (does that date me?).
Unfortunately, for whatever reason, that's not how it works with voip.ms.
In asterisk, for example, inbound routes are handled in order of specificity. A call from 314-555-5555 would be handled before 314-555-XXXX, and that before 314-XXX-XXXX.
If were simply list order, that would satisfy my curiosity, but it appears that is not the case either.
Anyway, voip.ms lists the filters in numeric sequence.
--
If someone refers to herself / himself as a "guru", they probably aren't. |
|
MartinMVoIP.msPremium,VIP
join:2008-07-21 | If you can PM me your account 6 digits, the DID Number and CallerID, I can check the database query to figure out how are the results sorted, and if the programmers approve, we could change the way it is currently sorted.
Let me know, thanks.
--
Martin - VoiP.ms |
|
