Quantcast
Channel: VOIP Tech Chat forum - dslreports.com
Viewing all articles
Browse latest Browse all 6358

[Voip.ms] NoMoRoBo blocking good callers at VOIP.MS

$
0
0
BACKGROUND: NoMoRoBo is a service with a database of junk phone numbers. It checks the caller ID number of your inbound call against their database, and if there's a match, NoMoRoBo answers the call after one ring, plays a brief recording, and hangs up, sparing the recipient from the junk call. The user adds NoMoRoBo's number to a ring group (typically called "multi-ring" or "simultaneous ringing" or something similar by various telephone providers). --------------------------------------------------------------------------------------- I have NoMoRoBo on three VOIP.MS accounts: mine and those of two clients. In spurts over the last month, NoMoRoBo has been answering calls from non- junk numbers (family, friends) after 4 rings (instead of 1) and and playing silence. This prevents an answering machine or Google Voice voicemail from taking the call. When the problem is active, it happens to all three of us. I've tested various VOIP.MS DIDs in various states. I've tried switching from VOIP.MS's Dallas servers to their Houston servers. I've tried both of the NoMoRoBo numbers that I know of, 202-729-9229 and 202-813-1600. But none of these steps made a difference. I haven't tried NoMoRoBo on other phone services such as Vonage, so I don't know whether it happens there. The problem might be at VOIP.MS, but I can't tell. No matter where the problem originates, I suspect that it affects all VOIP.MS accounts that use NoMoRoBo (including yours). You might have a hard time duplicating the problem because it's sporadic. If you'd like to see the problem, your best bet would be to add NoMoRoBo to your VOIP.MS ring group, then occasionally check the VOIP.MS printable call detail record (CDR) for indications that NoMoRoBo is taking your calls inappropriately. Or you could wait until someone tells you, "I called you, it rang a few times, then I got silence [or got cut off]". Attached is an example of a defective call, from my VOIP.MS printable CDR. Does any of you know why the problem occurs? Has the problem been discussed elsewhere?

Viewing all articles
Browse latest Browse all 6358

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>