VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- 14 participants
- 10512 messages
Re: Spamming for a week: 463-20X-XXXX
by Aaron C. de Bruyn
The tracebacks.org route was killed pretty quick.
Their response:
Thank you for the information. Tracebacks are generally run based on
evidence acquired from ITG members, enterprise partners, or government
partners, including data analytics companies, about illegal call campaigns,
so that our team can best prioritize tracebacks to ensure the greatest
impact. To ensure the broadest impact, the ITG typically cannot run
tracebacks based on a request from any individuals or enterprises. We
recommend that you provide this information via complaints to the FCC, FTC,
Law Enforcement and/or the office of your state attorney general. Such
authorities often aggregate complaints and make referrals to the ITG based
on what they are seeing most impacting consumers, in turn helping our team
prioritize accordingly.
-A
On Wed, Mar 18, 2026 at 9:04 AM Kili Land <kili.land(a)gtt.net> wrote:
> Submit traceback requests: https://tracebacks.org/traceback-requests/
>
> The form allows multiple entries
>
>
>
> *From:* Aaron C. de Bruyn via VoiceOps <voiceops(a)voiceops.org>
> *Sent:* Wednesday, March 18, 2026 10:23 AM
> *To:* voiceops(a)voiceops.org
> *Subject:* [VoiceOps] Spamming for a week: 463-20X-XXXX
>
>
>
> *NOTE:* This is an external message. Please use caution when replying,
> opening attachments or clicking on any links in this e-mail.
>
>
>
> *WARNING:* Replies to this message will go to
> voiceops-bounces(a)voiceops.org. If you believe this is malicious or are
> unsure if this is correct, please report it using the *Report Phish*
> button and our analysts will investigate it.
>
> A bunch of numbers out of Indiana have been spamming my customers for
> about a week.
>
>
>
> Most are automated recordings about how your Google business listing is
> wrong and needs to be fixed so customers can find you. Sometimes it's a
> human prefixed by the telltale "BWOOP" sound.
>
>
>
> +14632000068 - BANDWIDTH.COM CLEC LLC IN
> +14632001925 - BANDWIDTH.COM CLEC LLC IN
> +14632004002 - BANDWIDTH.COM CLEC LLC IN
> +14632005772 - BANDWIDTH.COM CLEC LLC IN
> +14632006038 - BANDWIDTH.COM CLEC LLC IN
> +14632006422 - BANDWIDTH.COM CLEC LLC IN
> +14632006730 - BANDWIDTH.COM CLEC LLC IN
> +14632009587 - BANDWIDTH.COM CLEC LLC IN
> +14632018300 - BHN IP ENABLED SERVICES LLC
> +14632018413 - BHN IP ENABLED SERVICES LLC
> +14632018586 - BHN IP ENABLED SERVICES LLC
> +14632018682 - BHN IP ENABLED SERVICES LLC
> +14632027042 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
> +14632027073 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
> +14632027200 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
> +14632027252 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
> +14632027397 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
> +14632027539 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
> +14632027678 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
> +14632027899 -LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
> +14632030946 - METROPCS INC (T-Mobile US)
>
>
>
> Kinda hard to believe the big boys haven't caught this abuse of their
> network yet.
>
>
>
> I tried reporting the numbers to bandwidth.com (as ID'd by telcodata.us),
> but their form only allows for a single entry at a time, and it says most
> of the numbers don't belong to them. Either their form is broken or
> telcodata.us is out of date.
>
>
>
> I can't find a reporting for Level3/Lumen. They seem to be geared towards
> "I'm a customer and need help figuring out the star code to block calls".
>
>
>
> -A
>
>
> *NOTICE: This e-mail is only intended for the person(s) to whom it is
> addressed and may contain confidential information. Unless stated to the
> contrary, any opinions or comments are personal to the writer and do not
> represent the official view of GTT Communications Inc or any of its
> affiliates. If you have received this e-mail in error, please notify us
> immediately by reply e-mail and then delete this message from your system.
> Please do not copy it or use it for any purposes, or disclose its contents
> to any other person. All quotes, offers, proposals and any other
> information in the body of this email is subject to, and limited by, the
> terms and conditions, signed service agreement and/or statement of work*
>
March 18, 2026
Re: Spamming for a week: 463-20X-XXXX
by Alex Balashov
Oh yeah, I've talked to them plenty. And if you've been on the list for any amount of time, you know I am not a man of few words.
But wasting their time with meandering and circuitous existential chats hasn't got them to stop calling.
-- Alex
> On Mar 18, 2026, at 12:34 PM, Shawn L via VoiceOps <voiceops(a)voiceops.org> wrote:
>
> It's always fun when they call one of our unpublished test numbers and
> one of the CO techs decides to stay on the line to talk to an agent
> and have some fun* with them.
>
> * Legal, legitimate fun -- ie: informing them that the call is being
> recorded for security and training purposes, quizzing them on how they
> got the number, etc.
>
> On Wed, Mar 18, 2026 at 12:28 PM Alex Balashov via VoiceOps
> <voiceops(a)voiceops.org> wrote:
>>
>>
>>
>>> On Mar 18, 2026, at 11:37 AM, Aaron C. de Bruyn <aaron(a)heyaaron.com> wrote:
>>>
>>> I wish my upstream (Twilio) had a big "Flag as Spam" button or API call that would send all the relevant info to whomever needs to know.
>>>
>>> E-mail sorta has spam reporting handled, but Voice/SMS doesn't appear to have that sorted out yet.
>>
>> I have been receiving the "tax resolution center" / "loan determination" / "debt consolidation" scam calls, many of them from TFNs, for close to a year at this point. They often overwhelm my phone, sometimes several come in at the same time from different DIDs, and they often interrupt other tasks or calls.
>>
>> I don't know what to do about it other than change my number (TMO), which I'm unwilling to do with how much 2FA and business stuff is tied to it. Turning on the iOS "ignore calls from unfamiliar numbers" is also totally not an option because I get lots of legitimate calls from unfamiliar numbers. It's really, really, really bad. I seem to have been singled out for an exceptional volume of these.
>>
>> I have on occasion pressed '2' on their IVR to speak to an "agent". The transfers are instant with no hold time. 100% of "agents" have been Indian.
>>
>> -- Alex
>>
>> --
>> Alex Balashov
>> Principal Consultant
>> Evariste Systems LLC
>> Web: https://evaristesys.com, https://www.csrpswitch.com
>> Tel: +1-706-510-6800
>>
>> _______________________________________________
>> VoiceOps mailing list -- VoiceOps(a)voiceops.org
>> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>> To unsubscribe send an email to voiceops-leave(a)voiceops.org
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com, https://www.csrpswitch.com
Tel: +1-706-510-6800
March 18, 2026
Re: Spamming for a week: 463-20X-XXXX
by Kili Land
This is what they were meaning by an Identity header:
INVITE sip:+ ____@____:5060 SIP/2.0
Via: SIP/2.0/UDP 4.55.24.161:5060;branch=z9hG4bK04Bca08abeb8b9b16fb
From: "PRIVATE" <sip:+ ____@____:5060>;tag=gK045a4816<mailto:____@4.55.24.161:5060%3e;tag=gK045a4816>
To: <sip:+ ____@____:5060>
Call-ID: 356802602_126328323@____
CSeq: 929670 INVITE
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,BYE,UPDATE,OPTIONS
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Contact: "PRIVATE" <sip:+ ____@____:5060<mailto:____@4.55.24.161:5060>>
P-Asserted-Identity: "PRIVATE" <sip:+ ____@____:5060>
Identity: ey____;info=<https://certificates.transnexus.com/706J/0ea0e4d8-____ae4a0.pem>;alg=ES256;ppt=shaken
Content-Length: 307
Content-Disposition: session; handling=required
Content-Type: application/sdp
This is on the invite header in from the carrier.
From: Aaron C. de Bruyn via VoiceOps <voiceops(a)voiceops.org>
Sent: Wednesday, March 18, 2026 10:58 AM
To: Mark R Lindsey <lindsey(a)e-c-group.com>
Cc: voiceops(a)voiceops.org
Subject: [VoiceOps] Re: Spamming for a week: 463-20X-XXXX
NOTE: This is an external message. Please use caution when replying, opening attachments or clicking on any links in this e-mail.
WARNING: Replies to this message will go to voiceops-bounces(a)voiceops.org<mailto:voiceops-bounces@voiceops.org>. If you believe this is malicious or are unsure if this is correct, please report it using the Report Phish button and our analysts will investigate it.
I forgot Twilio lets you download PCAPs of calls.
I grabbed one at random:
P-Asserted-Identity: <sip:+14632018300@206.147.72.38:5060<http://sip:+14632018300@206.147.72.38:5060>>
SIP PAI Address: sip:+14632018300@206.147.72.38:5060<http://sip:+14632018300@206.147.72.38:5060>
SIP PAI User Part: +14632018300
E.164 number (MSISDN): 14632018300
SIP PAI Host Part: 206.147.72.38
SIP PAI Host Port: 5060
-A
On Wed, Mar 18, 2026 at 8:44 AM Aaron C. de Bruyn <aaron(a)heyaaron.com<mailto:aaron@heyaaron.com>> wrote:
I did NOT know that. :)
I'm not a telco or service provider. Just part of a company that's unfortunate enough to help a handful of customers manage their own internal Asterisk or FreePBX systems.
Most of my customers use Twilio upstream. I don't think Twilio logs that header, and I don't see anything like it in the Asterisk logs. (Not sure if it even gets passed to us or if it just doesn't logs it.)
-A
On Wed, Mar 18, 2026 at 8:36 AM Mark R Lindsey <lindsey(a)e-c-group.com<mailto:lindsey@e-c-group.com>> wrote:
So...did you get any Identity headers? A traceback with ITG, or maybe an Identity header, is your only hope for tracing the origin.
I'm including the below, not to say that you, Aaron, don't know this, but just in case it's valuable to anyone else reading:
In the case of your first number, it belongs to a thousand block assigned initially to Bandwidth.com<http://Bandwidth.com>...but that's not even meaningful for routing a call to them today. You'd have to do an LRN lookup to find out how to deliver a call back to the legitimate owner of this number.
I did an LRN lookup for that first one, and it's currently ported to Onvoy, one of the brands of Sinch. But again, that only tells us how to get a call TO that legitimate owner.
What you want to know is how they're sending calls to you. And if you're getting an Identity header it would be at least interesting.
Failing that, you can file a report with the Industry Traceback Group to report illegal calls:
https://tracebacks.org/traceback-requests/
Mark R Lindsey | +1-229-316-0013 | mrl(a)ecg.co<mailto:mrl@ecg.co> | LinkedIn<https://www.linkedin.com/in/markrlindsey/>
On Mar 18, 2026, at 11:22, Aaron C. de Bruyn via VoiceOps <voiceops(a)voiceops.org<mailto:voiceops@voiceops.org>> wrote:
A bunch of numbers out of Indiana have been spamming my customers for about a week.
Most are automated recordings about how your Google business listing is wrong and needs to be fixed so customers can find you. Sometimes it's a human prefixed by the telltale "BWOOP" sound.
+14632000068 - BANDWIDTH.COM<http://bandwidth.com/> CLEC LLC IN
+14632001925 - BANDWIDTH.COM<http://bandwidth.com/> CLEC LLC IN
+14632004002 - BANDWIDTH.COM<http://bandwidth.com/> CLEC LLC IN
+14632005772 - BANDWIDTH.COM<http://bandwidth.com/> CLEC LLC IN
+14632006038 - BANDWIDTH.COM<http://bandwidth.com/> CLEC LLC IN
+14632006422 - BANDWIDTH.COM<http://bandwidth.com/> CLEC LLC IN
+14632006730 - BANDWIDTH.COM<http://bandwidth.com/> CLEC LLC IN
+14632009587 - BANDWIDTH.COM<http://bandwidth.com/> CLEC LLC IN
+14632018300 - BHN IP ENABLED SERVICES LLC
+14632018413 - BHN IP ENABLED SERVICES LLC
+14632018586 - BHN IP ENABLED SERVICES LLC
+14632018682 - BHN IP ENABLED SERVICES LLC
+14632027042 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
+14632027073 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
+14632027200 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
+14632027252 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
+14632027397 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
+14632027539 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
+14632027678 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
+14632027899 -LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
+14632030946 - METROPCS INC (T-Mobile US)
Kinda hard to believe the big boys haven't caught this abuse of their network yet.
I tried reporting the numbers to bandwidth.com<http://bandwidth.com/> (as ID'd by telcodata.us<http://telcodata.us/>), but their form only allows for a single entry at a time, and it says most of the numbers don't belong to them. Either their form is broken or telcodata.us<http://telcodata.us/> is out of date.
I can't find a reporting for Level3/Lumen. They seem to be geared towards "I'm a customer and need help figuring out the star code to block calls".
-A
_______________________________________________
VoiceOps mailing list -- VoiceOps(a)voiceops.org<mailto:VoiceOps@voiceops.org>
https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
To unsubscribe send an email to voiceops-leave(a)voiceops.org<mailto:voiceops-leave@voiceops.org>
NOTICE: This e-mail is only intended for the person(s) to whom it is addressed and may contain confidential information. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of GTT Communications Inc or any of its affiliates. If you have received this e-mail in error, please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person.
All quotes, offers, proposals and any other information in the body of this email is subject to, and limited by, the terms and conditions, signed service agreement and/or statement of work
March 18, 2026
Re: Spamming for a week: 463-20X-XXXX
by Alex Balashov
Ah no, you're looking for the Identity header. Not PAI.
> On Mar 18, 2026, at 11:58 AM, Aaron C. de Bruyn via VoiceOps <voiceops(a)voiceops.org> wrote:
>
> I forgot Twilio lets you download PCAPs of calls.
>
> I grabbed one at random:
> P-Asserted-Identity: <sip:+14632018300@206.147.72.38:5060>
> SIP PAI Address: sip:+14632018300@206.147.72.38:5060
> SIP PAI User Part: +14632018300
> E.164 number (MSISDN): 14632018300
> SIP PAI Host Part: 206.147.72.38
> SIP PAI Host Port: 5060
>
> -A
>
> On Wed, Mar 18, 2026 at 8:44 AM Aaron C. de Bruyn <aaron(a)heyaaron.com> wrote:
> I did NOT know that. :)
> I'm not a telco or service provider. Just part of a company that's unfortunate enough to help a handful of customers manage their own internal Asterisk or FreePBX systems.
>
> Most of my customers use Twilio upstream. I don't think Twilio logs that header, and I don't see anything like it in the Asterisk logs. (Not sure if it even gets passed to us or if it just doesn't logs it.)
>
> -A
>
> On Wed, Mar 18, 2026 at 8:36 AM Mark R Lindsey <lindsey(a)e-c-group.com> wrote:
> So...did you get any Identity headers? A traceback with ITG, or maybe an Identity header, is your only hope for tracing the origin.
>
> I'm including the below, not to say that you, Aaron, don't know this, but just in case it's valuable to anyone else reading:
>
> In the case of your first number, it belongs to a thousand block assigned initially to Bandwidth.com...but that's not even meaningful for routing a call to them today. You'd have to do an LRN lookup to find out how to deliver a call back to the legitimate owner of this number.
>
> I did an LRN lookup for that first one, and it's currently ported to Onvoy, one of the brands of Sinch. But again, that only tells us how to get a call TO that legitimate owner.
>
> What you want to know is how they're sending calls to you. And if you're getting an Identity header it would be at least interesting.
>
> Failing that, you can file a report with the Industry Traceback Group to report illegal calls:
> https://tracebacks.org/traceback-requests/
>
> Mark R Lindsey | +1-229-316-0013 | mrl(a)ecg.co | LinkedIn
>
>
>
>
>
>
>
>
>
>> On Mar 18, 2026, at 11:22, Aaron C. de Bruyn via VoiceOps <voiceops(a)voiceops.org> wrote:
>>
>> A bunch of numbers out of Indiana have been spamming my customers for about a week.
>>
>> Most are automated recordings about how your Google business listing is wrong and needs to be fixed so customers can find you. Sometimes it's a human prefixed by the telltale "BWOOP" sound.
>>
>> +14632000068 - BANDWIDTH.COM CLEC LLC IN
>> +14632001925 - BANDWIDTH.COM CLEC LLC IN
>> +14632004002 - BANDWIDTH.COM CLEC LLC IN
>> +14632005772 - BANDWIDTH.COM CLEC LLC IN
>> +14632006038 - BANDWIDTH.COM CLEC LLC IN
>> +14632006422 - BANDWIDTH.COM CLEC LLC IN
>> +14632006730 - BANDWIDTH.COM CLEC LLC IN
>> +14632009587 - BANDWIDTH.COM CLEC LLC IN
>> +14632018300 - BHN IP ENABLED SERVICES LLC
>> +14632018413 - BHN IP ENABLED SERVICES LLC
>> +14632018586 - BHN IP ENABLED SERVICES LLC
>> +14632018682 - BHN IP ENABLED SERVICES LLC
>> +14632027042 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027073 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027200 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027252 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027397 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027539 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027678 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027899 -LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632030946 - METROPCS INC (T-Mobile US)
>>
>> Kinda hard to believe the big boys haven't caught this abuse of their network yet.
>>
>> I tried reporting the numbers to bandwidth.com (as ID'd by telcodata.us), but their form only allows for a single entry at a time, and it says most of the numbers don't belong to them. Either their form is broken or telcodata.us is out of date.
>>
>> I can't find a reporting for Level3/Lumen. They seem to be geared towards "I'm a customer and need help figuring out the star code to block calls".
>>
>> -A
>> _______________________________________________
>> VoiceOps mailing list -- VoiceOps(a)voiceops.org
>> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>> To unsubscribe send an email to voiceops-leave(a)voiceops.org
>
>
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com, https://www.csrpswitch.com
Tel: +1-706-510-6800
March 18, 2026
Re: Spamming for a week: 463-20X-XXXX
by Calvin E.
Twilio does have the original Identity headers, assuming the call did not
originate on TDM. You can request that these be forwarded to you rather
than being replaced by their verstat TN-Validation headers.
On Wed, Mar 18, 2026 at 9:41 AM Aaron C. de Bruyn via VoiceOps <
voiceops(a)voiceops.org> wrote:
> I did NOT know that. :)
> I'm not a telco or service provider. Just part of a company that's
> unfortunate enough to help a handful of customers manage their own internal
> Asterisk or FreePBX systems.
>
> Most of my customers use Twilio upstream. I don't think Twilio logs that
> header, and I don't see anything like it in the Asterisk logs. (Not sure
> if it even gets passed to us or if it just doesn't logs it.)
>
> -A
>
> On Wed, Mar 18, 2026 at 8:36 AM Mark R Lindsey <lindsey(a)e-c-group.com>
> wrote:
>
>> So...did you get any Identity headers? A traceback with ITG, or maybe an
>> Identity header, is your only hope for tracing the origin.
>>
>> I'm including the below, not to say that you, Aaron, don't know this, but
>> just in case it's valuable to anyone else reading:
>>
>> In the case of your first number, it belongs to a thousand block
>> assigned initially to Bandwidth.com...but that's not even meaningful for
>> routing a call to them today. You'd have to do an LRN lookup to find out
>> how to deliver a call back to the legitimate owner of this number.
>>
>> I did an LRN lookup for that first one, and it's currently ported to
>> Onvoy, one of the brands of Sinch. But again, that only tells us how to get
>> a call TO that legitimate owner.
>>
>> What you want to know is how they're sending calls to you. And if you're
>> getting an Identity header it would be at least interesting.
>>
>> Failing that, you can file a report with the Industry Traceback Group to
>> report illegal calls:
>>
>> https://tracebacks.org/traceback-requests/
>>
>>
>> *Mark R Lindsey | +1-229-316-0013 | mrl(a)ecg.co <mrl(a)ecg.co> | LinkedIn
>> <https://www.linkedin.com/in/markrlindsey/>*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Mar 18, 2026, at 11:22, Aaron C. de Bruyn via VoiceOps <
>> voiceops(a)voiceops.org> wrote:
>>
>> A bunch of numbers out of Indiana have been spamming my customers for
>> about a week.
>>
>> Most are automated recordings about how your Google business listing is
>> wrong and needs to be fixed so customers can find you. Sometimes it's a
>> human prefixed by the telltale "BWOOP" sound.
>>
>> +14632000068 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>> +14632001925 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>> +14632004002 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>> +14632005772 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>> +14632006038 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>> +14632006422 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>> +14632006730 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>> +14632009587 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>> +14632018300 - BHN IP ENABLED SERVICES LLC
>> +14632018413 - BHN IP ENABLED SERVICES LLC
>> +14632018586 - BHN IP ENABLED SERVICES LLC
>> +14632018682 - BHN IP ENABLED SERVICES LLC
>> +14632027042 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027073 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027200 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027252 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027397 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027539 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027678 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632027899 -LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>> +14632030946 - METROPCS INC (T-Mobile US)
>>
>> Kinda hard to believe the big boys haven't caught this abuse of their
>> network yet.
>>
>> I tried reporting the numbers to bandwidth.com (as ID'd by telcodata.us),
>> but their form only allows for a single entry at a time, and it says most
>> of the numbers don't belong to them. Either their form is broken or
>> telcodata.us is out of date.
>>
>> I can't find a reporting for Level3/Lumen. They seem to be geared
>> towards "I'm a customer and need help figuring out the star code to block
>> calls".
>>
>> -A
>> _______________________________________________
>> VoiceOps mailing list -- VoiceOps(a)voiceops.org
>> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>> To unsubscribe send an email to voiceops-leave(a)voiceops.org
>>
>>
>> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
March 18, 2026
Re: Spamming for a week: 463-20X-XXXX
by Mark R Lindsey
Does Twilio give you an X-Twilio-Verstat? That might give you a clue.
You can try to get the Identity header. You can go directly to the Industry Traceback Group, but it sounds like in your situation you may not be eligible to receive the information (there are legitimate sensitivities, and the info is used for law enforcement.) Many ITG queries are launched by State Attorneys General, so if you file a complaint they may go that direction. It's always best to have a recording of the call with detailed call timestamps, when filing a traceback request or legal complaint.
The punchline is - LRN and number assignment are irrelevant for tracing the source of a call. They are involved when you are sending a call to that number. But the routing of calls from a particular source to you can take an entirely different path.
Mark R Lindsey | +1-229-316-0013 | mrl(a)ecg.co <mailto:mrl@ecg.co> | LinkedIn <https://www.linkedin.com/in/markrlindsey/>
> On Mar 18, 2026, at 11:58, Aaron C. de Bruyn <aaron(a)heyaaron.com> wrote:
>
> I forgot Twilio lets you download PCAPs of calls.
>
> I grabbed one at random:
> P-Asserted-Identity: <sip:+14632018300@206.147.72.38:5060 <http://sip:+14632018300@206.147.72.38:5060/>>
> SIP PAI Address: sip:+14632018300@206.147.72.38:5060 <http://sip:+14632018300@206.147.72.38:5060/>
> SIP PAI User Part: +14632018300
> E.164 number (MSISDN): 14632018300
> SIP PAI Host Part: 206.147.72.38
> SIP PAI Host Port: 5060
>
> -A
>
> On Wed, Mar 18, 2026 at 8:44 AM Aaron C. de Bruyn <aaron(a)heyaaron.com <mailto:aaron@heyaaron.com>> wrote:
>> I did NOT know that. :)
>> I'm not a telco or service provider. Just part of a company that's unfortunate enough to help a handful of customers manage their own internal Asterisk or FreePBX systems.
>>
>> Most of my customers use Twilio upstream. I don't think Twilio logs that header, and I don't see anything like it in the Asterisk logs. (Not sure if it even gets passed to us or if it just doesn't logs it.)
>>
>> -A
>>
>> On Wed, Mar 18, 2026 at 8:36 AM Mark R Lindsey <lindsey(a)e-c-group.com <mailto:lindsey@e-c-group.com>> wrote:
>>> So...did you get any Identity headers? A traceback with ITG, or maybe an Identity header, is your only hope for tracing the origin.
>>>
>>> I'm including the below, not to say that you, Aaron, don't know this, but just in case it's valuable to anyone else reading:
>>>
>>> In the case of your first number, it belongs to a thousand block assigned initially to Bandwidth.com <http://bandwidth.com/>...but that's not even meaningful for routing a call to them today. You'd have to do an LRN lookup to find out how to deliver a call back to the legitimate owner of this number.
>>>
>>> I did an LRN lookup for that first one, and it's currently ported to Onvoy, one of the brands of Sinch. But again, that only tells us how to get a call TO that legitimate owner.
>>>
>>> What you want to know is how they're sending calls to you. And if you're getting an Identity header it would be at least interesting.
>>>
>>> Failing that, you can file a report with the Industry Traceback Group to report illegal calls:
>>> https://tracebacks.org/traceback-requests/
>>>
>>> Mark R Lindsey | +1-229-316-0013 | mrl(a)ecg.co <mailto:mrl@ecg.co> | LinkedIn <https://www.linkedin.com/in/markrlindsey/>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>> On Mar 18, 2026, at 11:22, Aaron C. de Bruyn via VoiceOps <voiceops(a)voiceops.org <mailto:voiceops@voiceops.org>> wrote:
>>>>
>>>> A bunch of numbers out of Indiana have been spamming my customers for about a week.
>>>>
>>>> Most are automated recordings about how your Google business listing is wrong and needs to be fixed so customers can find you. Sometimes it's a human prefixed by the telltale "BWOOP" sound.
>>>>
>>>> +14632000068 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>>>> +14632001925 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>>>> +14632004002 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>>>> +14632005772 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>>>> +14632006038 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>>>> +14632006422 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>>>> +14632006730 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>>>> +14632009587 - BANDWIDTH.COM <http://bandwidth.com/> CLEC LLC IN
>>>> +14632018300 - BHN IP ENABLED SERVICES LLC
>>>> +14632018413 - BHN IP ENABLED SERVICES LLC
>>>> +14632018586 - BHN IP ENABLED SERVICES LLC
>>>> +14632018682 - BHN IP ENABLED SERVICES LLC
>>>> +14632027042 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>>>> +14632027073 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>>>> +14632027200 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>>>> +14632027252 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>>>> +14632027397 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>>>> +14632027539 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>>>> +14632027678 - LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>>>> +14632027899 -LEVEL 3 COMMUNICATIONS LLC IN (Lumen)
>>>> +14632030946 - METROPCS INC (T-Mobile US)
>>>>
>>>> Kinda hard to believe the big boys haven't caught this abuse of their network yet.
>>>>
>>>> I tried reporting the numbers to bandwidth.com <http://bandwidth.com/> (as ID'd by telcodata.us <http://telcodata.us/>), but their form only allows for a single entry at a time, and it says most of the numbers don't belong to them. Either their form is broken or telcodata.us <http://telcodata.us/> is out of date.
>>>>
>>>> I can't find a reporting for Level3/Lumen. They seem to be geared towards "I'm a customer and need help figuring out the star code to block calls".
>>>>
>>>> -A
>>>> _______________________________________________
>>>> VoiceOps mailing list -- VoiceOps(a)voiceops.org <mailto:VoiceOps@voiceops.org>
>>>> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>>>> To unsubscribe send an email to voiceops-leave(a)voiceops.org <mailto:voiceops-leave@voiceops.org>
March 18, 2026
Re: Spamming for a week: 463-20X-XXXX
by Carlos Alvarez
Never give any company your cell number. Just don’t. I’ve tracked this,
I generate new numbers for many common needs, such as recently, refinancing
a loan. The amount of garbage suddenly sent to that new number is unreal.
It was a number we’ve had for nearly ten years unused, clean. I have one
generic personal number that I use for companies. It just goes to VM. I
can’t picture what company needs to talk to me NOW instead of leaving a
message.
Funny story: An Indian-run dry cleaner, and Indian-run store have actually
been offended by this. They said they would text me, and I said they can’t
because it’s a landline. The dry cleaner in particular was super perturbed
that she “can’t send me coupons and reminders to get things cleaned” and
then more pissed when I said those are ads I don’t want. The c-store
nearly told me to just get out. WTF.
On Mar 18, 2026 at 8:40:47 AM, Alex Balashov via VoiceOps <
voiceops(a)voiceops.org> wrote:
>
>
> On Mar 18, 2026, at 11:37 AM, Aaron C. de Bruyn <aaron(a)heyaaron.com>
> wrote:
>
>
> I wish my upstream (Twilio) had a big "Flag as Spam" button or API call
> that would send all the relevant info to whomever needs to know.
>
>
> E-mail sorta has spam reporting handled, but Voice/SMS doesn't appear to
> have that sorted out yet.
>
>
> I have been receiving the "tax resolution center" / "loan determination" /
> "debt consolidation" scam calls, many of them from TFNs, for close to a
> year at this point. They often overwhelm my phone, sometimes several come
> in at the same time from different DIDs, and they often interrupt other
> tasks or calls.
>
> I don't know what to do about it other than change my number (TMO), which
> I'm unwilling to do with how much 2FA and business stuff is tied to it.
> Turning on the iOS "ignore calls from unfamiliar numbers" is also totally
> not an option because I get lots of legitimate calls from unfamiliar
> numbers. It's really, really, really bad. I seem to have been singled out
> for an exceptional volume of these.
>
> I have on occasion pressed '2' on their IVR to speak to an "agent". The
> transfers are instant with no hold time. 100% of "agents" have been Indian.
>
> -- Alex
>
> --
> Alex Balashov
> Principal Consultant
> Evariste Systems LLC
> Web: https://evaristesys.com, https://www.csrpswitch.com
> Tel: +1-706-510-6800
>
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
>
March 18, 2026
Re: Spamming for a week: 463-20X-XXXX
by Calvin E.
That's why YouMail works with the ITG and others :)
The problem with the Google Business Listing spam is proving that criminal
harm has actually happened to a real person. Our sensor network sees these
calls all day, but without proof of someone getting scammed there's little
interest in spending the resources. Someone would need to bait them with a
traceable financial transaction to make any headway, or prove the calls
alone are inflicting actual harm to a business or person. You could make
the case that the calls are costing your business, but that's just it,
*you* have to establish this before any LEA will act.
On Wed, Mar 18, 2026 at 9:23 AM Alex Balashov <abalashov(a)evaristesys.com>
wrote:
> I don't want to block, I want their skies to darken with fireballs of
> legal consequences.
>
> > On Mar 18, 2026, at 12:21 PM, Calvin E. <calvine(a)gmail.com> wrote:
> >
> > Shameless plug: for mobile devices, consider YouMail. If the ANI are
> already known, the free version should do a decent job of blocking them.
> For spoofed/one-and-done campaigns, the better option is the paid version
> with the captcha for non-contacts.
> >
> > On Wed, Mar 18, 2026 at 9:19 AM Alex Balashov via VoiceOps <
> voiceops(a)voiceops.org> wrote:
> >
> >
> >> On Mar 18, 2026, at 11:37 AM, Aaron C. de Bruyn <aaron(a)heyaaron.com>
> wrote:
> >>
> >> I wish my upstream (Twilio) had a big "Flag as Spam" button or API call
> that would send all the relevant info to whomever needs to know.
> >>
> >> E-mail sorta has spam reporting handled, but Voice/SMS doesn't appear
> to have that sorted out yet.
> >
> > I have been receiving the "tax resolution center" / "loan determination"
> / "debt consolidation" scam calls, many of them from TFNs, for close to a
> year at this point. They often overwhelm my phone, sometimes several come
> in at the same time from different DIDs, and they often interrupt other
> tasks or calls.
> >
> > I don't know what to do about it other than change my number (TMO),
> which I'm unwilling to do with how much 2FA and business stuff is tied to
> it. Turning on the iOS "ignore calls from unfamiliar numbers" is also
> totally not an option because I get lots of legitimate calls from
> unfamiliar numbers. It's really, really, really bad. I seem to have been
> singled out for an exceptional volume of these.
> >
> > I have on occasion pressed '2' on their IVR to speak to an "agent". The
> transfers are instant with no hold time. 100% of "agents" have been Indian.
> >
> > -- Alex
> >
> > --
> > Alex Balashov
> > Principal Consultant
> > Evariste Systems LLC
> > Web: https://evaristesys.com, https://www.csrpswitch.com
> > Tel: +1-706-510-6800
> >
> > _______________________________________________
> > VoiceOps mailing list -- VoiceOps(a)voiceops.org
> > https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> > To unsubscribe send an email to voiceops-leave(a)voiceops.org
>
> --
> Alex Balashov
> Principal Consultant
> Evariste Systems LLC
> Web: https://evaristesys.com, https://www.csrpswitch.com
> Tel: +1-706-510-6800
>
>
March 18, 2026
Re: Spamming for a week: 463-20X-XXXX
by Shawn L
It's always fun when they call one of our unpublished test numbers and
one of the CO techs decides to stay on the line to talk to an agent
and have some fun* with them.
* Legal, legitimate fun -- ie: informing them that the call is being
recorded for security and training purposes, quizzing them on how they
got the number, etc.
On Wed, Mar 18, 2026 at 12:28 PM Alex Balashov via VoiceOps
<voiceops(a)voiceops.org> wrote:
>
>
>
> > On Mar 18, 2026, at 11:37 AM, Aaron C. de Bruyn <aaron(a)heyaaron.com> wrote:
> >
> > I wish my upstream (Twilio) had a big "Flag as Spam" button or API call that would send all the relevant info to whomever needs to know.
> >
> > E-mail sorta has spam reporting handled, but Voice/SMS doesn't appear to have that sorted out yet.
>
> I have been receiving the "tax resolution center" / "loan determination" / "debt consolidation" scam calls, many of them from TFNs, for close to a year at this point. They often overwhelm my phone, sometimes several come in at the same time from different DIDs, and they often interrupt other tasks or calls.
>
> I don't know what to do about it other than change my number (TMO), which I'm unwilling to do with how much 2FA and business stuff is tied to it. Turning on the iOS "ignore calls from unfamiliar numbers" is also totally not an option because I get lots of legitimate calls from unfamiliar numbers. It's really, really, really bad. I seem to have been singled out for an exceptional volume of these.
>
> I have on occasion pressed '2' on their IVR to speak to an "agent". The transfers are instant with no hold time. 100% of "agents" have been Indian.
>
> -- Alex
>
> --
> Alex Balashov
> Principal Consultant
> Evariste Systems LLC
> Web: https://evaristesys.com, https://www.csrpswitch.com
> Tel: +1-706-510-6800
>
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
March 18, 2026
Re: Spamming for a week: 463-20X-XXXX
by Alex Balashov
I don't want to block, I want their skies to darken with fireballs of legal consequences.
> On Mar 18, 2026, at 12:21 PM, Calvin E. <calvine(a)gmail.com> wrote:
>
> Shameless plug: for mobile devices, consider YouMail. If the ANI are already known, the free version should do a decent job of blocking them. For spoofed/one-and-done campaigns, the better option is the paid version with the captcha for non-contacts.
>
> On Wed, Mar 18, 2026 at 9:19 AM Alex Balashov via VoiceOps <voiceops(a)voiceops.org> wrote:
>
>
>> On Mar 18, 2026, at 11:37 AM, Aaron C. de Bruyn <aaron(a)heyaaron.com> wrote:
>>
>> I wish my upstream (Twilio) had a big "Flag as Spam" button or API call that would send all the relevant info to whomever needs to know.
>>
>> E-mail sorta has spam reporting handled, but Voice/SMS doesn't appear to have that sorted out yet.
>
> I have been receiving the "tax resolution center" / "loan determination" / "debt consolidation" scam calls, many of them from TFNs, for close to a year at this point. They often overwhelm my phone, sometimes several come in at the same time from different DIDs, and they often interrupt other tasks or calls.
>
> I don't know what to do about it other than change my number (TMO), which I'm unwilling to do with how much 2FA and business stuff is tied to it. Turning on the iOS "ignore calls from unfamiliar numbers" is also totally not an option because I get lots of legitimate calls from unfamiliar numbers. It's really, really, really bad. I seem to have been singled out for an exceptional volume of these.
>
> I have on occasion pressed '2' on their IVR to speak to an "agent". The transfers are instant with no hold time. 100% of "agents" have been Indian.
>
> -- Alex
>
> --
> Alex Balashov
> Principal Consultant
> Evariste Systems LLC
> Web: https://evaristesys.com, https://www.csrpswitch.com
> Tel: +1-706-510-6800
>
> _______________________________________________
> VoiceOps mailing list -- VoiceOps(a)voiceops.org
> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
> To unsubscribe send an email to voiceops-leave(a)voiceops.org
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com, https://www.csrpswitch.com
Tel: +1-706-510-6800
March 18, 2026