 Reviews:
·RoadRunner Cable
·ViaTalk
1 edit | Incoming Call Routing Have a callerid pattern filter that filters all calls with callerid "TOLL FREE CALL" and dumps them into voicemail.
Now I have a call I would like to get past this filter callerid is "TOLL FREE CALL" with a number "1877xxxyyyyy" anyway to force only that call to ring my phone and keep the rest of "TOLL FREE CALL"s going to voicemail? |
|
 dmolaviPremium join:2005-04-11 Sewell, NJ | Have you tried to just white list just the one number in question? |
|
 Reviews:
·RoadRunner Cable
·ViaTalk
1 edit | Never thought of that! 
Was wondering what would happen if I gave the number a custom callerid. Does that process before the callerid pattern filter?
Edit: Added the number to whitelist and checked pattern match. According to description that should do what I need. |
|
 | reply to dcurrey Just an update. It didn't work.  |
|
|
|
 Reviews:
·RoadRunner Cable
·ViaTalk
1 edit | reply to dcurrey Can't be done with whitelist.
Here is response from the trouble ticket.
Currently, the Pattern Match option on the Whitelist page only allows overriding entries in the "Route By Pattern Match Filters" section of the incoming call routing page, where you block incoming calls based on area codes or partial numbers.
At this time, there isn't a way to whitelist numbers that would be blocked based on their caller ID name.
I will suggest that our developers add this capability.
|
|
 unknvoipRIP goosePremium join:2006-07-25 Rochester, NY kudos:1 Reviews:
·ViaTalk
| Thanks for keeping us posted. I am very surprised that the whitelist won't override ALL of the other blocking features.
I might just have to submit a ticket on that myself, although I tend to use the Pattern Match Filter over the Caller ID Name filter.
I know in the past I have had some issues with the order of precedence of the various call routing rules and they have evolved to become more 'natural'. I hope that is the case with this one. My example is that I block numbers with pattern matching (1800, 1877, etc.), but I am in a group that sends out notifications from a 1877 number. Originally the whitelist was lower priority than the pattern match, but they changed it after I reported it (but not necessarily because I reported it). I think originally the White List only applied to DND.
For your particular case, could you do what you want by blocking 18XX numbers and whitelisting the number you want to pass? |
|
 spal join:2010-04-15 Ventura, CA | reply to dcurrey Did you try the Custom Callerid route ? Put your special 1877xxxyyyyy number and put the Custom Caller ID as "My Special Number". So, when you are getting a call from that special number , caller id shows "My Special Number" and it does not get blocked by that call routing. I am assuming - you would like to make the hole for a specific 877 number. If you are trying to make a hole on any 877 number - the above mentioned method won't work. |
|
 Reviews:
·RoadRunner Cable
·ViaTalk
| Yea I tried the custom callerid trick. Pattern filters still send it to voicemail. I will either have to deal with it, hope VT makes a change or try unkvoip suggestion and block the pattern number 1877, 1800 etc. Have to look to make sure I don't want any other 800 calls passing. "TOLL FREE CALLS" and "800 Service" covered what I needed. |
|
 unknvoipRIP goosePremium join:2006-07-25 Rochester, NY kudos:1 Reviews:
·ViaTalk
| I think the custom caller ID doesn't work because the pattern matching works on the real caller ID and not the ID that you tell it to display to you.
Keep in mind that at the end of the day what is really important is that you receive the calls you want to receive and you can block the calls you want to block.
I block a few very specialized caller ID strings, but use the number blocking for most. Even at that, I send those calls to VM on the chance they are legit. That way they can leave a VM. When I see a number call more than once without leaving VM, I sometimes FWD to my cell so I can figure out who they are.
To reiterate, I am surprised the VT white list does not work against blocks by Caller ID, but there are more ways than one to skin this cat. |
|