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.nether.net%2Fmailman%2Flistinfo%2Fvoiceops&data=04%7C01%7Cjamie.montgomery%40comporium.com%7C534982314cb34db4c82908d92082d6ed%7C4c52dc5e4ed54645a209ed3c32f5ec3c%7C0%7C0%7C637576712042937226%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jwExmLUtviQjk9Gcinrmdkmx%2FZXgJFoa3W%2BgXp7OCkQ%3D&reserved=0 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.angryox.com%2F&data=04%7C01%7Cjamie.montgomery%40comporium.com%7C534982314cb34db4c82908d92082d6ed%7C4c52dc5e4ed54645a209ed3c32f5ec3c%7C0%7C0%7C637576712042937226%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zKJMJFMTepkCz8OVP30617%2FObvN9p7v%2BCZ0ZKaLa0oc%3D&reserved=0 --------------------------------------------------------------------------- ------------------------------ 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.angryox.com%2F&data=04%7C01%7Cjamie.montgomery%40comporium.com%7C534982314cb34db4c82908d92082d6ed%7C4c52dc5e4ed54645a209ed3c32f5ec3c%7C0%7C0%7C637576712042937226%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zKJMJFMTepkCz8OVP30617%2FObvN9p7v%2BCZ0ZKaLa0oc%3D&reserved=0 --------------------------------------------------------------------------- _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fvoiceops&data=04%7C01%7Cjamie.montgomery%40comporium.com%7C534982314cb34db4c82908d92082d6ed%7C4c52dc5e4ed54645a209ed3c32f5ec3c%7C0%7C0%7C637576712042937226%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jwExmLUtviQjk9Gcinrmdkmx%2FZXgJFoa3W%2BgXp7OCkQ%3D&reserved=0

------------------------------ 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.angryox.com%2F&data=04%7C01%7Cjamie.montgomery%40comporium.com%7C534982314cb34db4c82908d92082d6ed%7C4c52dc5e4ed54645a209ed3c32f5ec3c%7C0%7C0%7C637576712042937226%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zKJMJFMTepkCz8OVP30617%2FObvN9p7v%2BCZ0ZKaLa0oc%3D&reserved=0 --------------------------------------------------------------------------- _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fvoiceops&data=04%7C01%7Cjamie.montgomery%40comporium.com%7C534982314cb34db4c82908d92082d6ed%7C4c52dc5e4ed54645a209ed3c32f5ec3c%7C0%7C0%7C637576712042937226%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jwExmLUtviQjk9Gcinrmdkmx%2FZXgJFoa3W%2BgXp7OCkQ%3D&reserved=0

------------------------------ 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.cisa.gov%2Fsites%2Fdefault%2Ffiles%2Fpublications%2FAA20-245A-Joint_CSA-Technical_Approaches_to_Uncovering_Malicious_Activity_508.pdf&data=04%7C01%7Cjamie.montgomery%40comporium.com%7C534982314cb34db4c82908d92082d6ed%7C4c52dc5e4ed54645a209ed3c32f5ec3c%7C0%7C0%7C637576712042937226%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=n6VzViYE4ouyJZYHMSIBb05HSZMTDh3MlXOvDMvE8Bc%3D&reserved=0 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%2Flindsey%2F&data=04%7C01%7Cjamie.montgomery%40comporium.com%7C534982314cb34db4c82908d92082d6ed%7C4c52dc5e4ed54645a209ed3c32f5ec3c%7C0%7C0%7C637576712042937226%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5wUL1A4Zw%2B7szpNCYBIzdSCFAFqJayz9R3dKgSYC1gM%3D&reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fecg.co%2Flindsey%2F&data=04%7C01%7Cjamie.montgomery%40comporium.com%7C534982314cb34db4c82908d92082d6ed%7C4c52dc5e4ed54645a209ed3c32f5ec3c%7C0%7C0%7C637576712042937226%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5wUL1A4Zw%2B7szpNCYBIzdSCFAFqJayz9R3dKgSYC1gM%3D&reserved=0>

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.nether.net%2Fmailman%2Flistinfo%2Fvoiceops&data=04%7C01%7Cjamie.montgomery%40comporium.com%7C534982314cb34db4c82908d92082d6ed%7C4c52dc5e4ed54645a209ed3c32f5ec3c%7C0%7C0%7C637576712042937226%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jwExmLUtviQjk9Gcinrmdkmx%2FZXgJFoa3W%2BgXp7OCkQ%3D&reserved=0