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
May 2021
- 15 participants
- 24 messages
CSR BTN
by caalvarez@gmail.com
+1 to all that, Vonage for example often gives us a basic Excel sheet as a
CSR. It's like they're a mom and pop shop with an admin assistant typing
into Excel.
Centurylink will sometimes give us hundreds of numbers on a CSR, some of
which don't actually seem to belong to the customer.
On Sat, May 29, 2021 at 12:50 PM Robert Schoneman via VoiceOps <
voiceops at voiceops.org> wrote:
> As a customer doing porting from one carrier to another my experience has
> been the CSR is just a record of everything (phone number, circuit, trunk,
> etc) on an account or BTN. It's not a verification document, per se. But is
> often used during porting to verify information if the port order gets
> rejected by the losing carrier or if the port order is somehow incomplete
> or fails an initial verification.
>
> All the CSRs I've ever seen were just everything on the BTN and weren't
> specific to the port order in question. That is, if I was porting 5 numbers
> from a BTN and there's 100 numbers on the BTN, the CSR would include all
> 100 numbers regardless of the port order.
>
> I've not seen any consistency with regards to what details are on the CSRs
> from one carrier to another. Some are quite verbose, and others are little
> more than a list of numbers.
>
> ------------------------------
> *From:* VoiceOps <voiceops-bounces at voiceops.org> on behalf of Mike
> Hammett <voiceops at ics-il.net>
> *Sent:* Friday, May 28, 2021 10:51 PM
> *To:* VoiceOps <voiceops at voiceops.org>
> *Subject:* [VoiceOps] CSR BTN
>
> Does a CSR have to have the specific number being ported or just any
> number on the account?
>
> We're testing a third party network that we'll utilize in the short-term
> for out-of-area usage.
> We ported some of our own numbers to our account at the third party.
> The CSRs arrived with the main BTN on the account, not the number being
> ported.
> Our porting person rejected the CSRs because they weren't for the number
> being ported. Of course she knew what number was being attempted because it
> was an internal operation, but normally she wouldn't.
>
>
> It's my thought that the CSR is a customer information verification
> process. We wouldn't know the number actually being ported until the LSR
> came. Does the name, address, account number, TN, etc. match an account you
> have? If so, great.
>
>
> Where can I find a good resource on the process and what's normally
> acceptable for rejections?
>
>
> Of course I said, "Let me verify this before we do anything" and then she
> replied to the CSRs rejecting. *sigh* I guess we'll really be testing all
> scenarios.
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ics-2Dil.com&d=DwQF…>
>
>
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.midwest-2Dix.com&d=…>
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
May 30, 2021
STIR/SHAKEN - Robocall Mitigation Plan
by marylou@backuptelecom.com
I've had several people ask some great questions about the Robocall
Mitigation plan since I sent out my last e-mail so I just wanted to
clarify who needs to file a Robocall Mitigation plan by June 30, 2021.
All companies that sell or resell voice services of any type (VOIP, TDM,
Wireless) OR any company that has an end user customer they provide DIDs
to are considered telecom carriers. It does NOT matter if you use
upstream providers or not. It does not matter if you use another
carrier's certificate or not! If you provide DIDs to a paying customer
for any reason you are considered a telecom carrier so you need to file
a Robocall Mitigation Plan.
For those of you who aren't familiar with me, you may be wondering why I
bother to post about this. I've been a Telecom Carrier Consultant for
the last 21 years and have helped over a hundred carriers (CLECs, ILECs,
Paging, Satellite, and Wireless) install and maintain their facilities
based networks. The reason I post information about this is not because
I don't have enough work to do. It is because over the years I have seen
certain parties we won't mention do anything and everything they can to
put the small carriers out of business and I don't want anyone to be
taken out because they didn't realize they needed to do something to
comply. I am a firm believer that no company can be everything to
everyone so there is a place in the world for all carriers that provide
good services.
I've had people coming to me from the beginning asking for help getting
their STIR/SHAKEN certificate so I'm very familiar with the process and
what the upstream carriers are telling their underlying carriers. I'm
also very familiar with the many changes that have been made to the
requirements for getting a certificate. It's been confusing for everyone
involved and especially the mitigation plan because that started out as
an alternative to getting a certificate but it's turned into something
that is required of every carrier. So regardless of whether you've
already turned up STIR/SHAKEN or you're using someone else's
certificate.......make sure you file your Robocall Mitigation Plan. I am
not the only consultant helping people get their paperwork done so they
can qualify for a certificate, so there's no obligation to use my
services. All I'm saying is that whether you do it on your own or you
hire someone to help you, make sure you file your Robocall Mitigation
plan by June 30th. For those of you who are already STIR/SHAKEN
compliant, it just means you sign in and mark your company as compliant!
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
May 30, 2021
CSR BTN
by rschoneman@blumenthalarts.org
As a customer doing porting from one carrier to another my experience has been the CSR is just a record of everything (phone number, circuit, trunk, etc) on an account or BTN. It's not a verification document, per se. But is often used during porting to verify information if the port order gets rejected by the losing carrier or if the port order is somehow incomplete or fails an initial verification.
All the CSRs I've ever seen were just everything on the BTN and weren't specific to the port order in question. That is, if I was porting 5 numbers from a BTN and there's 100 numbers on the BTN, the CSR would include all 100 numbers regardless of the port order.
I've not seen any consistency with regards to what details are on the CSRs from one carrier to another. Some are quite verbose, and others are little more than a list of numbers.
________________________________
From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Mike Hammett <voiceops at ics-il.net>
Sent: Friday, May 28, 2021 10:51 PM
To: VoiceOps <voiceops at voiceops.org>
Subject: [VoiceOps] CSR BTN
Does a CSR have to have the specific number being ported or just any number on the account?
We're testing a third party network that we'll utilize in the short-term for out-of-area usage.
We ported some of our own numbers to our account at the third party.
The CSRs arrived with the main BTN on the account, not the number being ported.
Our porting person rejected the CSRs because they weren't for the number being ported. Of course she knew what number was being attempted because it was an internal operation, but normally she wouldn't.
It's my thought that the CSR is a customer information verification process. We wouldn't know the number actually being ported until the LSR came. Does the name, address, account number, TN, etc. match an account you have? If so, great.
Where can I find a good resource on the process and what's normally acceptable for rejections?
Of course I said, "Let me verify this before we do anything" and then she replied to the CSRs rejecting. *sigh* I guess we'll really be testing all scenarios.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ics-2Dil.com&d=DwQF…>
Midwest Internet Exchange
http://www.midwest-ix.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.midwest-2Dix.com&d=…>
May 29, 2021
CSR BTN
by voiceops@ics-il.net
Does a CSR have to have the specific number being ported or just any number on the account?
We're testing a third party network that we'll utilize in the short-term for out-of-area usage.
We ported some of our own numbers to our account at the third party.
The CSRs arrived with the main BTN on the account, not the number being ported.
Our porting person rejected the CSRs because they weren't for the number being ported. Of course she knew what number was being attempted because it was an internal operation, but normally she wouldn't.
It's my thought that the CSR is a customer information verification process. We wouldn't know the number actually being ported until the LSR came. Does the name, address, account number, TN, etc. match an account you have? If so, great.
Where can I find a good resource on the process and what's normally acceptable for rejections?
Of course I said, "Let me verify this before we do anything" and then she replied to the CSRs rejecting. *sigh* I guess we'll really be testing all scenarios.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
May 29, 2021
LRN and valid values
by paul@timmins.net
> I don't know. I cannot seem to get my carrier to identify a situation where
> I would want to terminate a call and the LRN I would get back would be
> 732040xxxx or similar.
It never will. The code is unrouteable. I'm sure it exists in the LERG somewhere for some sort of pANI or billing purpose, but that doesn't make it a routable code.
> I'm trying to figure out if I don't know something or if my termination carrier is mildly nutso.
The people making the rate deck have no idea how the network actually works. They just think it costs X to terminate a call to pac bell or whatever so they include it, despite it not being a dialable code.
> Unless it will occur and there's something I don't know or understand.
In 20 years of running telcodata.us <http://telcodata.us/>, and 15 years of running the network of a regional CLEC, I've never seen any code like that in the network outside of AT&T's weird BTNs (313-K60-xxxx and such) but those again, aren't billable and in that case aren't even really numbers and in any case, don't appear in the PSTN at all, just in category 11 files and on bills and ASRs and LSRs)
-Paul
> On May 27, 2021, at 12:08 AM, Peter Beckman <beckman at angryox.com> wrote:
>
> On Wed, 26 May 2021, Alex Balashov wrote:
>
>> Where does this conflict emerge in practice? Do customers call numbers in
>> this exchange? Do you get billed for calls (less any LRN dip fees) to this
>> exchange even though none of your wholesale termination vendors can route it?
>
> I don't know. I cannot seem to get my carrier to identify a situation where
> I would want to terminate a call and the LRN I would get back would be
> 732040xxxx or similar. They keep telling me that it exists in the LERG6 and
> LERG6ATC and LERG6ODD, and that's fine, but why would it be in an NPANXX
> rate deck???
>
> On Wed, 26 May 2021, Paul Timmins wrote:
>
>> How are you even getting operator assisted calls onto your network to begin
>> with? Do you have an operator service you still pay for?
>
> I'm not, AFAIK. This is a termination deck. I don't even know of a phone
> number that would return an LRN like this. I'm trying to figure out if I
> don't know something or if my termination carrier is mildly nutso.
>
> On Thu, 27 May 2021, Jamie Montgomery wrote:
>
>> There is an entry for 732040A.. OCN refers back to Verizon of Jew Jersey. The
>> Rate Center is all X's, so it's a special code of some kind.. cant be assinged
>> to an originating number, I dont believe.
>
> And that's what I'm trying to figure out. I believe the same, but if this
> is true, why would a termination rate deck include 732040 as an LRN prefix
> so we can do LCR? Why include a rate in a deck that will never occur?
>
> Unless it will occur and there's something I don't know or understand.
>
> Thus this thread. :-)
>
> Beckman
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com http://www.angryox.com/
> ---------------------------------------------------------------------------
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
May 27, 2021
LRN and valid values
by beckman@angryox.com
On Wed, 26 May 2021, Alex Balashov wrote:
> Where does this conflict emerge in practice? Do customers call numbers in
> this exchange? Do you get billed for calls (less any LRN dip fees) to this
> exchange even though none of your wholesale termination vendors can route it?
I don't know. I cannot seem to get my carrier to identify a situation where
I would want to terminate a call and the LRN I would get back would be
732040xxxx or similar. They keep telling me that it exists in the LERG6 and
LERG6ATC and LERG6ODD, and that's fine, but why would it be in an NPANXX
rate deck???
On Wed, 26 May 2021, Paul Timmins wrote:
> How are you even getting operator assisted calls onto your network to begin
> with? Do you have an operator service you still pay for?
I'm not, AFAIK. This is a termination deck. I don't even know of a phone
number that would return an LRN like this. I'm trying to figure out if I
don't know something or if my termination carrier is mildly nutso.
On Thu, 27 May 2021, Jamie Montgomery wrote:
> There is an entry for 732040A.. OCN refers back to Verizon of Jew Jersey. The
> Rate Center is all X's, so it's a special code of some kind.. cant be assinged
> to an originating number, I dont believe.
And that's what I'm trying to figure out. I believe the same, but if this
is true, why would a termination rate deck include 732040 as an LRN prefix
so we can do LCR? Why include a rate in a deck that will never occur?
Unless it will occur and there's something I don't know or understand.
Thus this thread. :-)
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
May 27, 2021
LRN and valid values
by Jamie.Montgomery@comporium.com
There is an entry for 732040A.. OCN refers back to Verizon of Jew Jersey. The Rate Center is all X's, so it's a special code of some kind.. cant be assinged to an originating number, I dont believe.
Jamie M.
________________________________
From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of voiceops-request at voiceops.org <voiceops-request at voiceops.org>
Sent: Wednesday, May 26, 2021 4:12 PM
To: voiceops at voiceops.org <voiceops at voiceops.org>
Subject: [EXTERNAL] VoiceOps Digest, Vol 140, Issue 3
Send VoiceOps mailing list submissions to
voiceops at voiceops.org
To subscribe or unsubscribe via the World Wide Web, visit
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.neth…
or, via email, send a message with subject or body 'help' to
voiceops-request at voiceops.org
You can reach the person managing the list at
voiceops-owner at voiceops.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of VoiceOps digest..."
Today's Topics:
1. LRN and valid values (Peter Beckman)
2. Re: LRN and valid values (Alex Balashov)
3. Re: LRN and valid values (Paul Timmins)
4. Robocall mitigation SCAM! (Mary Lou Carey)
5. Re: Robocall mitigation SCAM! (Mark Lindsey)
6. Re: Robocall mitigation SCAM! (Matthew Yaklin)
----------------------------------------------------------------------
Message: 1
Date: Tue, 25 May 2021 22:47:24 -0400
From: Peter Beckman <beckman at angryox.com>
To: VoiceOps <voiceops at voiceops.org>
Subject: [VoiceOps] LRN and valid values
Message-ID: <alpine.BSF.2.20.2105252244540.46257 at nog2.angryox.com>
Content-Type: text/plain; format=flowed; charset=US-ASCII
Carrier A provided us a US NPANXX Rate Deck that had some values in it that
were not valid, such as 732040.
When asked about it, they claim that Access Tandem Codes are valid LRN
values for operator services calls.
Carrier B provides an API for us to query to get the LRN for a termination
number, so we can rate it properly and implement our own LCR. Carrier B
says LRNs will always be valid NPANXX values, and 732040 and similar would
never be returned.
I don't have access to the LERG, and frankly, even if I did, I'm not sure
where I'd look to see who wins the conflict.
Any suggestions?
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.angryo…
---------------------------------------------------------------------------
------------------------------
Message: 2
Date: Wed, 26 May 2021 00:02:51 -0400
From: Alex Balashov <abalashov at evaristesys.com>
To: VoiceOps <voiceops at voiceops.org>
Subject: Re: [VoiceOps] LRN and valid values
Message-ID: <0D4FB8A5-31EB-42C3-82BB-E76A88E4B820 at evaristesys.com>
Content-Type: text/plain; charset=utf-8
Where does this conflict emerge in practice? Do customers call numbers in this exchange? Do you get billed for calls (less any LRN dip fees) to this exchange even though none of your wholesale termination vendors can route it?
?
Sent from mobile, with due apologies for brevity and errors.
> On May 25, 2021, at 10:48 PM, Peter Beckman <beckman at angryox.com> wrote:
>
> ?Carrier A provided us a US NPANXX Rate Deck that had some values in it that
> were not valid, such as 732040.
>
> When asked about it, they claim that Access Tandem Codes are valid LRN
> values for operator services calls.
>
> Carrier B provides an API for us to query to get the LRN for a termination
> number, so we can rate it properly and implement our own LCR. Carrier B
> says LRNs will always be valid NPANXX values, and 732040 and similar would
> never be returned.
>
> I don't have access to the LERG, and frankly, even if I did, I'm not sure
> where I'd look to see who wins the conflict.
>
> Any suggestions?
>
> Beckman
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.angryo…
> ---------------------------------------------------------------------------
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.neth…
------------------------------
Message: 3
Date: Wed, 26 May 2021 04:54:19 +0000
From: Paul Timmins <ptimmins at clearrate.com>
To: Peter Beckman <beckman at angryox.com>
Cc: VoiceOps <voiceops at voiceops.org>
Subject: Re: [VoiceOps] LRN and valid values
Message-ID: <8EB46E7D-53C6-4675-BDCC-DD3D7511E989 at clearrate.com>
Content-Type: text/plain; charset="us-ascii"
How are you even getting operator assisted calls onto your network to begin with? Do you have an operator service you still pay for?
> On May 25, 2021, at 10:47 PM, Peter Beckman <beckman at angryox.com> wrote:
>
> Carrier A provided us a US NPANXX Rate Deck that had some values in it that
> were not valid, such as 732040.
>
> When asked about it, they claim that Access Tandem Codes are valid LRN
> values for operator services calls.
>
> Carrier B provides an API for us to query to get the LRN for a termination
> number, so we can rate it properly and implement our own LCR. Carrier B
> says LRNs will always be valid NPANXX values, and 732040 and similar would
> never be returned.
>
> I don't have access to the LERG, and frankly, even if I did, I'm not sure
> where I'd look to see who wins the conflict.
>
> Any suggestions?
>
> Beckman
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.angryo…
> ---------------------------------------------------------------------------
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.neth…
------------------------------
Message: 4
Date: Wed, 26 May 2021 14:38:53 -0500
From: Mary Lou Carey <marylou at backuptelecom.com>
To: voiceops at voiceops.org
Subject: [VoiceOps] Robocall mitigation SCAM!
Message-ID: <978d2c6b8d26de81c4686156b823f5b3 at backuptelecom.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
I just heard through the grapevine that several companies have been shut
down and/or threatened with the confiscation of their equipment for
passing Robocall traffic. The companies that this happened to all
claimed someone contacted them and told them to keep the TN/traffic up
so they could help catch the offenders. Unfortunately, whoever is
advising carriers to keep the traffic up is not on the up and up. The
ITG and large carriers came in and shut them down because they continued
to pass traffic that was identified as robocalls.
If someone contacts your company about a trace back and advises you to
keep the TNs / traffic up, DO NOT LEAVE IT UP! Document everything and
turn down the Robocall traffic as soon as possible! Then send both the
ITG and large carrier involved the account number and CDRs for the calls
in question.
Be safe out there.....it's getting crazy!
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
------------------------------
Message: 5
Date: Wed, 26 May 2021 15:50:58 -0400
From: Mark Lindsey <lindsey at e-c-group.com>
To: Mary Lou Carey <marylou at backuptelecom.com>
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] Robocall mitigation SCAM!
Message-ID: <CBAAC14A-7815-4D2C-ADEA-64946F8F52C7 at e-c-group.com>
Content-Type: text/plain; charset="us-ascii"
Good tips, Mary Lou!
Do you think there's potentially any good intentions behind the advice to leave the traffic up?
In the cybersecurity space, authorities will say that if your network has been compromised, you shouldn't immediately shutdown the hacked systems. For example, just this past September, this Joint Cybersecurity Advisory (AA20-245A) from the US and a few other governments...
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fus-cert.c…
Under actions to avoid:
"Mitigating the affected systems before responders can protect and recover data
- This can cause the loss of volatile data such as memory and other host-based artifacts.
- The adversary may notice and change their tactics, techniques, and procedures."
Mark R Lindsey, SMTS | +1-229-316-0013 | mark at ecg.co | https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fecg.co%2F… <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fecg.co%2F…>
> On May 26, 2021, at 3:38 PM, Mary Lou Carey <marylou at backuptelecom.com> wrote:
>
> I just heard through the grapevine that several companies have been shut down and/or threatened with the confiscation of their equipment for passing Robocall traffic. The companies that this happened to all claimed someone contacted them and told them to keep the TN/traffic up so they could help catch the offenders. Unfortunately, whoever is advising carriers to keep the traffic up is not on the up and up. The ITG and large carriers came in and shut them down because they continued to pass traffic that was identified as robocalls.
>
> If someone contacts your company about a trace back and advises you to keep the TNs / traffic up, DO NOT LEAVE IT UP! Document everything and turn down the Robocall traffic as soon as possible! Then send both the ITG and large carrier involved the account number and CDRs for the calls in question.
>
> Be safe out there.....it's getting crazy!
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.neth…
May 27, 2021
Caveat to the 2023 STIR/SHAKEN extension for small companies
by marylou@backuptelecom.com
One more thing.....I also found out that there's a caveat to the June
30, 2023 extension for small carriers. Although the FCC granted smaller
carriers an extension to implement STIR/SHAKEN, that does not exempt
your company from filing your Robocall Mitigation Plan by June 30th,
2021. So smaller carriers should get registered with the Robocall
Mitigation Database ASAP and file your Robocall Mitigation plan by June
30, 2021. Then you will be given until June 30, 2023 to implement it.
The mitigation database registration requires that you to have your FRNs
and your 499 filing completed in order to submit your plan. Just trying
to pass on all the information I run across because there's been so much
confusion surrounding the process!
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
May 26, 2021
Robocall mitigation SCAM!
by marylou@backuptelecom.com
All I know is that I was told it happened to several legitimate carriers
that were small companies. Just be careful is all I'm saying because its
not worth losing your business over.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2021-05-26 03:12 PM, Matthew Yaklin wrote:
> Mary Lou,
>
> Are you referring to the super sketchy voip providers who list a US
> address but in reality are based overseas?
> Like the ones where you google search the US street address on their
> website using maps and find out it is just a run down apartment
> building?
>
> Or are you talking about more respectable outfits?
>
> Matt
>
> -----Original Message-----
> From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Mary Lou
> Carey
> Sent: Wednesday, May 26, 2021 3:39 PM
> To: voiceops at voiceops.org
> Subject: [VoiceOps] Robocall mitigation SCAM!
>
> I just heard through the grapevine that several companies have been
> shut down and/or threatened with the confiscation of their equipment
> for passing Robocall traffic. The companies that this happened to all
> claimed someone contacted them and told them to keep the TN/traffic up
> so they could help catch the offenders. Unfortunately, whoever is
> advising carriers to keep the traffic up is not on the up and up. The
> ITG and large carriers came in and shut them down because they
> continued to pass traffic that was identified as robocalls.
>
> If someone contacts your company about a trace back and advises you to
> keep the TNs / traffic up, DO NOT LEAVE IT UP! Document everything and
> turn down the Robocall traffic as soon as possible! Then send both the
> ITG and large carrier involved the account number and CDRs for the
> calls in question.
>
> Be safe out there.....it's getting crazy!
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
May 26, 2021
Robocall mitigation SCAM!
by marylou@backuptelecom.com
I understand it might provide helpful information, but from the sound of
it these carriers were punished for keeping the traffic up as they were
instructed to do. No one at the ITG or large carrier took responsibility
for advising the carrier to keep the traffic up so either the right hand
didn't know what the left hand is doing or there's some funny business
going on. I'd say document the calls as much as possible and then turn
them down. Better to not let it go through than to keep passing it and
open yourselves up for retaliatory actions. You can always remove the
block once the investigators get involved, and help them at that point
but when you do nothing to stop it then it makes you look guilty even if
you were just trying to help.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2021-05-26 02:50 PM, Mark Lindsey wrote:
> Good tips, Mary Lou!
>
> Do you think there's potentially any good intentions behind the advice
> to leave the traffic up?
>
> In the cybersecurity space, authorities will say that if your network
> has been compromised, you shouldn't immediately shutdown the hacked
> systems. For example, just this past September, this Joint
> Cybersecurity Advisory (AA20-245A) from the US and a few other
> governments...
>
>>
> https://us-cert.cisa.gov/sites/default/files/publications/AA20-245A-Joint_C…
>
> _Under actions to avoid: _
>
>> _"Mitigating the affected systems before responders can protect and
>> recover data _
>> _ - This can cause the loss of volatile data such as memory and
>> other host-based artifacts._
>> _ - The adversary may notice and change their tactics, techniques,
>> and procedures."_
>
> Mark R Lindsey, SMTS | +1-229-316-0013 | mark at ecg.co |
> https://ecg.co/lindsey/
>
>> On May 26, 2021, at 3:38 PM, Mary Lou Carey
>> <marylou at backuptelecom.com> wrote:
>>
>> I just heard through the grapevine that several companies have been
>> shut down and/or threatened with the confiscation of their equipment
>> for passing Robocall traffic. The companies that this happened to
>> all claimed someone contacted them and told them to keep the
>> TN/traffic up so they could help catch the offenders. Unfortunately,
>> whoever is advising carriers to keep the traffic up is not on the up
>> and up. The ITG and large carriers came in and shut them down
>> because they continued to pass traffic that was identified as
>> robocalls.
>>
>> If someone contacts your company about a trace back and advises you
>> to keep the TNs / traffic up, DO NOT LEAVE IT UP! Document
>> everything and turn down the Robocall traffic as soon as possible!
>> Then send both the ITG and large carrier involved the account number
>> and CDRs for the calls in question.
>>
>> Be safe out there.....it's getting crazy!
>>
>> MARY LOU CAREY
>> BackUP Telecom Consulting
>> Office: 615-791-9969
>> Cell: 615-796-1111
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
May 26, 2021