Blocking/Permitting via cid_patterns.yaml vs. web interface. Difference? #70
Replies: 1 comment
-
Hello. Sorry but I only saw this just now... There are blocked/permitted lists for specific numbers. And there are RE lists that offer blocking/permitted based upon partial numbers or the names presented via caller id (which - in this day of increasing wireless calling - are becoming less and less useful). They are totally unrelated to each other. CA checks each in a specific order of precedence which is (so far as I can tell from experience): permitted number list, blocked number list, permitted name and number RE lists (I am not sure which comes first), and lastly - blocked name and number lists (again, not sure which comes first). If none of these match (and if screening is enabled) the call is screened. So to do what you want, simply add the single 800 number to the permitted list using the Add New at the top. The precedence of checking will handle the rest. Anyone with more specific info can feel free to be more specific than I have been. |
Beta Was this translation helpful? Give feedback.
-
I've been blocking names and numbers using the cid_patterns.yaml file. But I noticed there is also a "Permitted" and "Blocked" option in the web interface. When I view the "Blocked", I don't see what I defined in the cid_patterns.yaml, which is probably fine. But I can click on the "Regex List" which does reflect what is in the cid_patterns.yaml file. Do these both work parallel and are cumulative?
I currently have a regex block in my cid_patterns.yaml file: "^8": "8xx Number",
However, if I wanted to allow a single 800 number, could I do this in the web interface? Or should I do it in the cid_patterns.yaml file? Or is this even a valid thing to do?
Beta Was this translation helpful? Give feedback.
All reactions