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
March 2026
- 15 participants
- 49 messages
Re: Lawful interception with Open-Source
by Henning Westerholt
Hello,
there are some companies selling (proprietary) add-ons in this area for Kamailio, RTPEngine etc..
I know of some companies that also developed something for it inhouse and got it certified in Europe. It was not open sourced for obvious reasons, mainly because it contains some internal knowledge about processes and/or infrastructure.
We had some open-source attempts on the Kamailio project side, but there were stopped also because of some "agencies" request I heard.
In the end it boils down in implementing the ETSI standards and then having it certified for a specific setup.
There is also this open-source project, which claims to be used from different providers. I don't have any particular experience with it, though: https://github.com/OpenLI-NZ/openli
Cheers,
Henning
--
Kamailio & VoIP services – https://gilawa.com
> -----Original Message-----
> From: Phil Lavin via VoiceOps <voiceops(a)voiceops.org>
> Sent: Donnerstag, 19. März 2026 12:38
> To: voiceops(a)voiceops.org
> Subject: [VoiceOps] Lawful interception with Open-Source
>
> Hi folks,
>
> Has anybody successfully achieved an LI implementation on Open Source
> voice infra (Asterisk, Freeswitch, RTPEngine, etc.)? I understand that we need
> a vendor (we have one but are open to other options) for the law enforcement
> integration but we’re trying to avoid using proprietary SBCs for the audio tap.
>
> Any advice would be greatly appreciated. Feel free to reach out off list if you
> don’t want to disclose on-list.
>
>
> Phil
> _______________________________________________
> 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 19, 2026
Lawful interception with Open-Source
by Phil Lavin
Hi folks,
Has anybody successfully achieved an LI implementation on Open Source voice infra (Asterisk, Freeswitch, RTPEngine, etc.)? I understand that we need a vendor (we have one but are open to other options) for the law enforcement integration but we’re trying to avoid using proprietary SBCs for the audio tap.
Any advice would be greatly appreciated. Feel free to reach out off list if you don’t want to disclose on-list.
Phil
March 19, 2026
Re: Spamming for a week: 463-20X-XXXX
by Jeff Brower
Hi Aaron,
Is that a Twilio "Voice Trace" pcap you can download ? I thought
those were for Twilio support engineer / internal viewing only. Or are
the ones you mention called something else ?
-Jeff
Quoting "Aaron C. de Bruyn via VoiceOps" <voiceops(a)voiceops.org>:
> I forgot Twilio lets you download PCAPs of calls.
> I grabbed one at random:
> P-Asserted-Identity: <sip:+14632018300@206.147.72.38:5060[1]>
> SIP PAI Address: sip:+14632018300@206.147.72.38:5060[1]
> 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[2]...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[3]
>>>
>>>
>>>
>>>
>>>
>>>> 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[4] CLEC LLC IN
>>>> +14632001925 - BANDWIDTH.COM[4] CLEC LLC IN
>>>> +14632004002 - BANDWIDTH.COM[4] CLEC LLC IN
>>>> +14632005772 - BANDWIDTH.COM[4] CLEC LLC IN
>>>> +14632006038 - BANDWIDTH.COM[4] CLEC LLC IN
>>>> +14632006422 - BANDWIDTH.COM[4] CLEC LLC IN
>>>> +14632006730 - BANDWIDTH.COM[4] CLEC LLC IN
>>>> +14632009587 - BANDWIDTH.COM[4] 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[4]
>>>> (as ID'd by telcodata.us[5]), 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[5]
>>>> 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
Links:
------
[1] http://sip:+14632018300@206.147.72.38:5060
[2] http://Bandwidth.com
[3] https://www.linkedin.com/in/markrlindsey/
[4] http://bandwidth.com/
[5] http://telcodata.us/
March 19, 2026
Re: Spamming for a week: 463-20X-XXXX
by Mike Johnston
On 2026-03-18 11:34, Shawn L via VoiceOps 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.
I look up the call while I'm talking to them to see which trunk it came
in on and to review the Identity header. In at least one instance, I
had a traceback request completely filled out before the call was over.
Just needed to end the call to download the audio file.
"So gift cards from the Walmart should work?"
"Yes."
"And just to be clear, you work for the US government, with the IRS?"
"Yes."
"Perfect. That should be everything I need to complete this traceback
form. You do realize you called a telephone company, right?"
March 19, 2026
Re: Spamming for a week: 463-20X-XXXX
by Brandon Martin
On 3/18/26 11:36, Mark R Lindsey via VoiceOps wrote:
> 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.
It's worth noting that the 463 area code in Indianapolis is pretty new -
only a couple years old in practice. I would expect records of who has
what to be pretty clean at this point. There shouldn't be a whole lot
of serial port (no not that kind) activity on 463 numbers yet, and if
you find it, that might be an indication of nefarious activity on its own.
One level of port from an established CLEC to a VoIP carrier is pretty
normal from my (limited) experience, though. Most VoIP carriers don't
have direct assignments even if they could get them. They mostly just
seem to get them from established CLECs.
March 19, 2026
Re: Spamming for a week: 463-20X-XXXX
by Aaron C. de Bruyn
On Wed, Mar 18, 2026 at 2:28 PM Calvin E. <calvine(a)gmail.com> wrote:
> The system you're describing takes money to operate and maintain. Who is
> going to pay for it?
>
Something something blockchain.
-A
March 18, 2026
Re: Spamming for a week: 463-20X-XXXX
by Calvin E.
The mobile carriers do this today via parties like First Orion, Hiya, TNS,
while YouMail and a few others do this for consumers/wholesale
carriers/enterprises. There are problems with false positives and redress.
Sadly, STIR/SHAKEN didn't end spoofing, and it's still possible for a bad
actor to sully the reputation of a legitimate party. That's why they set up
freecallerregistry.com to help people get their "SCAM LIKELY" caller ID
fixed. The system you're describing takes money to operate and maintain.
Who is going to pay for it?
On Wed, Mar 18, 2026 at 2:19 PM Aaron C. de Bruyn <aaron(a)heyaaron.com>
wrote:
> Seems like it would be a lot easier to get AI to write a simple app where
> people can dump known-bad numbers in, and automatically exchange them with
> other people...sorta like how it gets handled in the email world.
>
> It can be up to the receiving phone system to do something with it--drop
> the call, challenge the user to solve 3+4, mail in picture of them with a
> copy of their phone bill while holding a copy of tomorrow's newspaper
> signed and witnessed by a notary, etc...
>
> -A
>
>
>
>
> On Wed, Mar 18, 2026 at 1:59 PM Calvin E. <calvine(a)gmail.com> wrote:
>
>> Now you get to crowdsource/lobby your state Attorney General to have
>> the Anti-Robocall Litigation Task Force do something.
>>
>>
>> https://www.naag.org/our-work/center-for-consumer-protection/consumer-file-…
>>
>> https://www.naag.org/find-my-ag/
>>
>> While also CC'ing anything relevant to the FCC & FTC.
>>
>> It may take a critical mass of consumers/business owners in multiple
>> states to get anything done about the Google Listings spam.
>>
>> On Wed, Mar 18, 2026 at 1:46 PM Aaron C. de Bruyn via VoiceOps <
>> voiceops(a)voiceops.org> wrote:
>>
>>> 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*
>>>>
>>> _______________________________________________
>>> 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 Aaron C. de Bruyn
Seems like it would be a lot easier to get AI to write a simple app where
people can dump known-bad numbers in, and automatically exchange them with
other people...sorta like how it gets handled in the email world.
It can be up to the receiving phone system to do something with it--drop
the call, challenge the user to solve 3+4, mail in picture of them with a
copy of their phone bill while holding a copy of tomorrow's newspaper
signed and witnessed by a notary, etc...
-A
On Wed, Mar 18, 2026 at 1:59 PM Calvin E. <calvine(a)gmail.com> wrote:
> Now you get to crowdsource/lobby your state Attorney General to have
> the Anti-Robocall Litigation Task Force do something.
>
>
> https://www.naag.org/our-work/center-for-consumer-protection/consumer-file-…
>
> https://www.naag.org/find-my-ag/
>
> While also CC'ing anything relevant to the FCC & FTC.
>
> It may take a critical mass of consumers/business owners in multiple
> states to get anything done about the Google Listings spam.
>
> On Wed, Mar 18, 2026 at 1:46 PM Aaron C. de Bruyn via VoiceOps <
> voiceops(a)voiceops.org> wrote:
>
>> 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*
>>>
>> _______________________________________________
>> 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.
Now you get to crowdsource/lobby your state Attorney General to have
the Anti-Robocall Litigation Task Force do something.
https://www.naag.org/our-work/center-for-consumer-protection/consumer-file-…
https://www.naag.org/find-my-ag/
While also CC'ing anything relevant to the FCC & FTC.
It may take a critical mass of consumers/business owners in multiple states
to get anything done about the Google Listings spam.
On Wed, Mar 18, 2026 at 1:46 PM Aaron C. de Bruyn via VoiceOps <
voiceops(a)voiceops.org> wrote:
> 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*
>>
> _______________________________________________
> 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 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