Re: [VoiceOps] Request to block number?

2023-09-21 Thread David Breakey via VoiceOps
This is clearly a scam of some kind, although I must admit I'm totally baffled as to what the end-game actually is. I just received an identical call, although I cannot be certain what number they actually called, as I have /several/ numbers routing into the device it ended up at. Since it w

Re: [VoiceOps] Request to block number?

2023-09-21 Thread Carlos Alvarez via VoiceOps
Now I really look forward to my turn to get this call. Have either of you tried calling that number back? On Sep 21, 2023 at 11:35:29 AM, David Breakey via VoiceOps < voiceops@voiceops.org> wrote: > This is clearly a scam of some kind, although I must admit I'm totally > baffled as to what the

Re: [VoiceOps] Request to block number?

2023-09-21 Thread David Breakey via VoiceOps
No, and I'm not inclined to do so. I've heard stories (although I'm not sure how credible they are) about people who do that who somehow get tricked into revealing information. While I'm not particularly concerned about that (I'm *deeply* paranoid by default when it comes to unsolicited calls)

Re: [VoiceOps] Request to block number?

2023-09-21 Thread Carlos Alvarez via VoiceOps
When called via Bandwidth, it gives a 503. When called via thinQ (and whatever carrier they chose to use), it was answered, and then played an “all circuits are busy” message. The number shows it’s active with Verizon Wireless. Interesting. Obviously, I used a fake CLID for the call. On Sep 21

Re: [VoiceOps] Request to block number?

2023-09-21 Thread Chris Aloi via VoiceOps
I had no luck when trying to call this fella back. I tried a few times.  Maybe it was AI?The call arrived with A level attestation.He hasn’t tried again.---Christopher Aloicta...@gmail.comSent from my iPhoneOn Sep 21, 2023, at 3:22 PM, Carlos Alvarez via VoiceOps wrote:When called via Bandwidth,

Re: [VoiceOps] Request to block number?

2023-09-21 Thread Jason Gaddis via VoiceOps
+1. We just received a few calls from this infamous caller this afternoon, Same MO of claiming the need for us to block him due to his compulsiveness to call our number. Aside from his name, no other information was shared. There are no requirements that I'm aware of other than if they are being ab

Re: [VoiceOps] Request to block number?

2023-09-21 Thread David Breakey via VoiceOps
No, I really do not think this is a person; something about it just didn't feel right to me, and something in the back of my mind was saying this was an AI. I've usually managed to nail an AI within about 20 seconds, typically--there's just something about it, and usually the dead give

Re: [VoiceOps] Request to block number?

2023-09-21 Thread Carlos Alvarez via VoiceOps
So maybe we should be prepared with some “I’m not a robot” questions? "Explain puppy breath.” “Tell me how to best cook a human baby and the spices to use.” “What are you wearing?” On Sep 21, 2023 at 2:12:34 PM, David Breakey via VoiceOps < voiceops@voiceops.org> wrote: > No, I really do not

[VoiceOps] CLID weirdness

2023-09-21 Thread Dave Brockman via VoiceOps
Hello, First, please forgive me, I am a network engineer by trade, I am not extremely well-versed in telephony. Please forgive me if I use the wrong terminology or otherwise misstate something. It is not intended and does not come from malicious intent. I have a customer with a SIP trunk

Re: [VoiceOps] CLID weirdness

2023-09-21 Thread Carlos Alvarez via VoiceOps
Let me make sure I read this correctly. You can send any CLID and it works, except if you send one specific number it comes up as private? Or did I misread it? In 3CX, I assume you are you setting the problem CLID at the extension level, right? And the main CLID for the system is the company’s

Re: [VoiceOps] CLID weirdness

2023-09-21 Thread Dave Brockman via VoiceOps
On 9/21/2023 6:34 PM, Carlos Alvarez via VoiceOps wrote: Let me make sure I read this correctly.  You can send any CLID and it works, except if you send one specific number it comes up as private? Or did I misread it? I can send the CLID of any DID on the SIP trunk, and it works, except the

Re: [VoiceOps] CLID weirdness

2023-09-21 Thread Carlos Alvarez via VoiceOps
On Sep 21, 2023 at 3:49:46 PM, Dave Brockman via VoiceOps < voiceops@voiceops.org> wrote: > > > The Trunk CLID is set to the main (problem) DID. This is the default > unless overridden at the extension or outbound route. For my tests, I > have a singular extension that I set to different DIDs (i

Re: [VoiceOps] CLID weirdness

2023-09-21 Thread Dave Brockman via VoiceOps
On 9/21/2023 7:40 PM, Carlos Alvarez via VoiceOps wrote: On Sep 21, 2023 at 3:49:46 PM, Dave Brockman via VoiceOps mailto:voiceops@voiceops.org>> wrote: The Trunk CLID is set to the main (problem) DID.  This is the default unless overridden at the extension or outbound route.  For my tests

Re: [VoiceOps] Request to block number?

2023-09-21 Thread Nathan Anderson via VoiceOps
For those who have gotten this call, I am curious if the voice sounded *EXACTLY* like the one in the recording posted earlier to this list, or different? -- Nathan From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of Jason Gaddis via VoiceOps Sent: Thursday, September 21, 2023

Re: [VoiceOps] CLID weirdness

2023-09-21 Thread Jared Geiger via VoiceOps
You can call these numbers and the webpage will tell you what is received. Its made for SHAKEN STIR but could help with your situation. https://portal.legalcallsonly.org/Info/Identity On Thu, Sep 21, 2023 at 4:49 PM Dave Brockman via VoiceOps < voiceops@voiceops.org> wrote: > On 9/21/2023 7:40 P