Recent change in Nomorobo or CC call treatment behaviors?

(1/4) > >>

Tooth:
First, thanks for everyone's contributions to this forum! I've referenced this forum extensively in the past to successfully configure my Obi200 with a GV and CallCentric accounts.

To thwart robocalls, I followed the advice here to set up a hunt group call treatment in my CC account where the first destination in the hunt group is Nomorobo via SIP BROKER (ring for 5 seconds) and the second destination is my CC extension. This has been working great for a few years now, but just recently all inbound robocalls now result in a single ring on my home phone before Nomorobo shuts it down. This didn't used to be the case. Previously, Nomorobo would intercept the robocall and my home phone would never ring.

Has anyone else experienced this? I've tinkered with my call treatment settings but I can't seem to figure out why this has suddenly started happening.

Any help is appreciated!

Taoman:
Please post the exact SIP Broker string you are using on Callcentric in your call treatment.

Also, check out the following thread. Pay attention to the last post. It works.

http://www.obitalk.com/forum/index.php?topic=18432.0

Tooth:
The first destination in my Nomorobo hunt group forwards to **275*18776593620 (Vonage). The second destination to my CC extension. The hunt group for Nomorobo is last in my list of call treatments.

Tooth:
Reading the last post of the thread that you referenced, I should modify my SIP broker forwarding to **275*1008518776593620?

Taoman:
Quote from: Tooth on August 28, 2021, 11:37:22 am

Reading the last post of the thread that you referenced, I should modify my SIP broker forwarding to **275*1008518776593620?


Yes, but you will be using alcazarnetworks.com via SIP Broker.

Navigation

[0] Message Index

[#] Next page