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
Bandwidth API Outage 11m 45s April 15, 2026 21:47:11 to 21:58:56 UTC
by Peter Beckman
Just FYI since Bandwidth has NOT posted an Incident as of yet
https://status.bandwidth.com/
My monitoring detected that Bandwidth API began returning both 502 Bad
Gateway and 504 Gateway Time-Out errors starting at 21:47:11 UTC on April
15, 2026.
I monitor both v1 and v2 APIs.
21:47:11 UTC First host alert of API issues
21:48:49 UTC Second host alert of API issues
21:55:08 UTC First host sees success (Second does not)
21:56:08 UTC First host sees failures again
21:58:56 UTC Second host sees recovery
21:59:12 UTC First host sees recovery
21:59:22 UTC Second host confirms recovery
11m 45s Observed Outage
Our logging confirmed that API calls that normally complete without issue
failed during this period.
Cheers
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman(a)angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
April 15, 2026
Re: Spamming for a week: 463-20X-XXXX
by Aaron C. de Bruyn
Just to follow up on this...
Twilio doesn't expose the headers, so I have no way of knowing which
carrier is allowing these spam calls to originate.
Contacting Twilio and asking them to report it results in their techs
asking for a detailed list of every zarking call SID and account SID,
followed by "Sorry, those calls don't originate from Twilio".
When pushed to contact the offending carrier on my behalf they say they
don't store that information on their systems so they can't do anything,
just block the prefix in your phone system.
I guess it's in Twilio's best interests to let the spammers keep calling as
they get to nickle and dime me for each call.
-A
On Wed, Mar 18, 2026 at 8:22 AM Aaron C. de Bruyn <aaron(a)heyaaron.com>
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
>
March 30, 2026
Invites available - AI-searchable databases on VoIP & US Voice regulations
by Mark Lindsey
ECG offers curated two AI-searchable databases and you’re invited to get
access:
*Voice/VoIP standards, including IMS and Media*
Have you ever wondered “is there an RFC on that?” Or “why does it only use
odd numbered UDP port numbers?” Or “What’s the difference between
P-Asserted-Identity and P-Preferred-Identity?” Or “what’s the Ro
interface?” You can just google - or use a chatbot - but the accuracy on
tedious details is pretty low. This database contains both Internet
standards and books.
*USA voice regulations and tech standards on Robocalling, STIR/SHAKEN, SIP
NNI*
This curated database has FCC sources, regulation text, ATIS standards and
other official documents. You could ask, “does an intermediate provider
have to sign every call?” Or “what’s the true definition of B level
attestation?” Or “is ATIS-10000999 incorporated into the law?” Or “what did
Telnyx say about the new caller-ID rules?”
We’re using a RAG database so for each answer you get an exact quote and
citation of the wording of the original source.
If you would like access for your own queries, you can reply here to me
(not to the list) to request an invite.
Mark Lindsey
Lindsey(a)e-c-group.com • ECG Inc • https://ecg.co
March 29, 2026
US Cellular
by Jeremy Lizzotte
Does anybody else struggling with outbound calls to US Cellular mobile
numbers?
March 20, 2026
Re: Spamming for a week: 463-20X-XXXX
by Alex Balashov
I did devise a new one yesterday that seems to get them to hang up quickly. I request a transfer to a live agent, then:
Me: [seemingly ignoring the call centre agent and talking to someone across the room]
"Sandy, go ahead and conference the FBI in on this one, huge fraud."
-- Alex
> On Mar 19, 2026, at 12:10 AM, Mike Johnston via VoiceOps <voiceops(a)voiceops.org> wrote:
>
>
> "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?"
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com, https://www.csrpswitch.com
Tel: +1-706-510-6800
March 20, 2026
Re: Spamming for a week: 463-20X-XXXX
by Jeff Brower
Hi Kili, thanks for this heads up.
Quoting Kili Land <kili.land(a)gtt.net>:
> You can get media from Twilio but be careful - the last time I dealt
> with them on this I had several calls with them where I requested
> features be added because at the time (2023) it was all or nothing.
> You could not have them enable RTP capture on a single test number.
>
> This may have changed, but definitely something to keep in mind
> and get clarity on if you do want media from them.
>
> Kili
>
>
>
> -------------------------
> FROM: Jeff Brower via VoiceOps <voiceops(a)voiceops.org>
> SENT: Thursday, March 19, 2026 9:35:10 AM
> TO: Aaron C de Bruyn <aaron(a)heyaaron.com>
> CC: voiceops(a)voiceops.org <voiceops(a)voiceops.org>
> SUBJECT: [VoiceOps] Re: Spamming for a week: 463-20X-XXXX
> Hi Aaron,
>
> Ok thanks. So what they make available from their dashboard is SIP
> traffic, not media.
>
> -Jeff
>
> Quoting "Aaron C. de Bruyn via VoiceOps" <voiceops(a)voiceops.org>:
>
>> It's available under their Logs -> Calls -> <pick a call> menu.
>>
>> Screenshots:
>>
>> https://cdn-ctrl-alt-it-com.sfo3.cdn.digitaloceanspaces.com/production/cdnf…
>>
>> https://cdn-ctrl-alt-it-com.sfo3.cdn.digitaloceanspaces.com/production/cdnf…
>>
>> It's just the SIP packets between Twilio and your phone
>> server when you're using their SIP Trunking product.
>>
>> -A
>>
>>
>> On Wed, Mar 18, 2026 at 9:23 PM Jeff Brower
>> <jbrower(a)signalogic.com> wrote:
>>
>>> _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@voiceops.org[6]_
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/
[6] mailto:voiceops-leave@voiceops.org
March 19, 2026
Re: Spamming for a week: 463-20X-XXXX
by Aaron C. de Bruyn
Correct.
But I can opt to record calls on my end after making sure it says "Calls
may be recorded for quality and training purposes"....which is funny
because the stupid automated spam just talks right over the message.
-A
On Thu, Mar 19, 2026 at 7:35 AM Jeff Brower <jbrower(a)signalogic.com> wrote:
> Hi Aaron,
>
> Ok thanks. So what they make available from their dashboard is SIP
> traffic, not media.
>
> -Jeff
>
> Quoting "Aaron C. de Bruyn via VoiceOps" <voiceops(a)voiceops.org>:
>
> It's available under their Logs -> Calls -> <pick a call> menu.
>
> Screenshots:
>
> https://cdn-ctrl-alt-it-com.sfo3.cdn.digitaloceanspaces.com/production/cdnf…
>
> https://cdn-ctrl-alt-it-com.sfo3.cdn.digitaloceanspaces.com/production/cdnf…
>
> It's just the SIP packets between Twilio and your phone server when you're
> using their SIP Trunking product.
>
> -A
>
>
> On Wed, Mar 18, 2026 at 9:23 PM Jeff Brower <jbrower(a)signalogic.com>
> wrote:
>
>>
>>
>>
>>
>>
>>
>> *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 <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
>> <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
>> <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
>>> <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 <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/
>>>> <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 <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 <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 <VoiceOps(a)voiceops.org>
>>>> https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/
>>>> <https://lists.voiceops.org/postorius/lists/voiceops.voiceops.org/> To
>>>> unsubscribe send an email to voiceops-leave(a)voiceops.org
>>>> <voiceops-leave(a)voiceops.org>*
>>>>
>>>>
>>
>>
>>
>
>
>
>
March 19, 2026
Re: Spamming for a week: 463-20X-XXXX
by Kili Land
You can get media from Twilio but be careful - the last time I dealt with them on this I had several calls with them where I requested features be added because at the time (2023) it was all or nothing. You could not have them enable RTP capture on a single test number.
This may have changed, but definitely something to keep in mind and get clarity on if you do want media from them.
Kili
________________________________
From: Jeff Brower via VoiceOps <voiceops(a)voiceops.org>
Sent: Thursday, March 19, 2026 9:35:10 AM
To: Aaron C de Bruyn <aaron(a)heyaaron.com>
Cc: voiceops(a)voiceops.org <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. 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.
Hi Aaron,
Ok thanks. So what they make available from their dashboard is SIP traffic, not media.
-Jeff
Quoting "Aaron C. de Bruyn via VoiceOps" <voiceops(a)voiceops.org<mailto:voiceops@voiceops.org>>:
It's available under their Logs -> Calls -> <pick a call> menu.
Screenshots:
https://cdn-ctrl-alt-it-com.sfo3.cdn.digitaloceanspaces.com/production/cdnf…
https://cdn-ctrl-alt-it-com.sfo3.cdn.digitaloceanspaces.com/production/cdnf…
It's just the SIP packets between Twilio and your phone server when you're using their SIP Trunking product.
-A
On Wed, Mar 18, 2026 at 9:23 PM Jeff Brower <jbrower(a)signalogic.com<mailto:jbrower@signalogic.com>> wrote:
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<mailto:voiceops@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<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 19, 2026
Re: Spamming for a week: 463-20X-XXXX
by Jeff Brower
Hi Aaron,
Ok thanks. So what they make available from their dashboard is SIP
traffic, not media.
-Jeff
Quoting "Aaron C. de Bruyn via VoiceOps" <voiceops(a)voiceops.org>:
> It's available under their Logs -> Calls -> <pick a call> menu.
> Screenshots:
>
> https://cdn-ctrl-alt-it-com.sfo3.cdn.digitaloceanspaces.com/production/cdnf…
>
> https://cdn-ctrl-alt-it-com.sfo3.cdn.digitaloceanspaces.com/production/cdnf…
>
> It's just the SIP packets between Twilio and your phone server
> when you're using their SIP Trunking product.
>
> -A
>
>
> On Wed, Mar 18, 2026 at 9:23 PM Jeff Brower
> <jbrower(a)signalogic.com> wrote:
>
>> _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@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: Lawful interception with Open-Source
by Jeff Brower
Hi Phil,
I was about to mention OpenLI but Henning beat me to it. I know the
guys there, have worked with them since 2021. For their commercial
projects they operate as SearchLight, let me know if you want contact
info.
We have numerous customers in Europe, a few use this and also use
Mediashark software to test/verify their setup and output to their
govt LEAs. If you try it, you can test what you tap:
https://github.com/signalogic/SigSRF_SDK/blob/master/mediaTest_readme.md#us…
-Jeff
Quoting Phil Lavin via VoiceOps <voiceops(a)voiceops.org>:
> 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