Robocall blocking with Nomorobo
Taoman:
Quote from: SteveInWA on July 01, 2020, 06:42:26 pm
It also stopped working if I simply add it as a simulring call treatment on Callcentric itself.
Instead of whatever string you were using for the Callcentric simulring call treatment try using this string instead:
**275*18667326185
This string routes to Sip Broker which Callcentic peers with and what I've used for years. Very reliable.
Also, you can make a speed dial with a known spam number to check if Nomorobo is working as expected. Make a speed dial for this where X is your Callcentric SP number:
spX(18667326185@tollfree.alcazarnetworks.com;ui=2007653876)
SteveInWA:
Quote from: Taoman on July 01, 2020, 07:53:30 pm
Quote from: SteveInWA on July 01, 2020, 06:42:26 pm
It also stopped working if I simply add it as a simulring call treatment on Callcentric itself.
Instead of whatever string you were using for the Callcentric simulring call treatment try using this string instead:
**275*18667326185
This string routes to Sip Broker which Callcentic peers with and what I've used for years. Very reliable.
Also, you can make a speed dial with a known spam number to check if Nomorobo is working as expected. Make a speed dial for this where X is your Callcentric SP number:
spX(18667326185@tollfree.alcazarnetworks.com;ui=2007653876)
Thanks, as always! So, I've eliminated everything I can think of, as a user error. I thought it might be an incorrect digit map, so I got rid of that, and went back to using CC's simulring call treatment, ringing my extensions and the nomorobo number. That didn't work. I substituted your SIP Broker string; that didn't work. I then systematically deleted each of my extensions, one at a time, retested, and that didn't work. I then deleted all of the extensions and added a cell phone number as a forward (along with your string). That didn't work. I then removed the cell phone number, leaving only the SIP Broker forward-to. That didn't work! I confirmed that, if I call some other number from the CC number, it properly sends its caller ID.
I'm stumped. I do a lot of testing for the forums, and I thought I had made some bonehead error, but I have now completely removed the OBiTALK devices as extensions, set it to ring an ordinary phone number and the nomorobo number, and it fails.
Taoman:
Quote from: SteveInWA on July 02, 2020, 12:48:02 pm
I then removed the cell phone number, leaving only the SIP Broker forward-to. That didn't work!
but I have now completely removed the OBiTALK devices as extensions, set it to ring an ordinary phone number and the nomorobo number, and it fails.
Are you positive you don't have a call treatment above the one you made that might be intercepting the call and it's never even getting to the call treatment in question? For testing purposes, I would disable all other call treatments but the one you're working on.
How are you determining that it's not routing thru Sip Broker? In the CC report log, on the far right-hand sign under Destination it will say "Callcentric peering."
I use a hunt group instead of simulring so I don't ever get that first ring if Nomorobo gets a hit on the incoming call. I've attached a graphic of what my call treatment looks like. I just tested it again by spoofing a known spam number (5205187375) by calling my CC number directly and I immediately got the message:
"Your call has been intercepted by Nomorobo" so I know it works.
SteveInWA:
Sonofabitch! I didn't notice that I had recently added a test rule to send "medium" and "high" risk calls to TrueCNAM. So, that rule (processed before the main rule for my extension) was causing the failure. I've now removed that rule, and all's well again. I guess that proves one thing: TrueCNAM does work, at least for some numbers.
Thanks so much, and take care!
Navigation
[0] Message Index
[*] Previous page