- VoiceOps - lists.voiceops.org

LRN and valid values
by Jamie.Montgomery＠comporium.com May 26, 2021

May 26, 2021

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…

1 0

Caveat to the 2023 STIR/SHAKEN extension for small companies
by marylou＠backuptelecom.com May 26, 2021

May 26, 2021

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

1 0

Robocall mitigation SCAM!
by marylou＠backuptelecom.com May 26, 2021

May 26, 2021

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

4 5

STIR SHAKEN requirement due by June 30th
by marylou＠backuptelecom.com May 24, 2021

May 24, 2021

Just wanted to give everyone an update on STIR/SHAKEN because the due date to be compliant is June 30th and a few changes have been made to the process recently (Last one was May 10th). I just spoke with Michael Nemcik at the FCC on Friday and with Brent Struthers with the STI-GA this morning to verify all this information because there's been a lot of confusion about the process. The first change is that EVERY CARRIER needs to sign up for the mitigation database! Before you can comply with this final mitigation database step, you'll need: 1. 499 account (and FRNs for each associated company) 2. Company Code (aka OCN) 3. Robocall Mitigation Database plan NOTE: If you have not gotten a STIR/SHAKEN certificate AND/OR are not 100% compliant yet you'll have to submit the Robocall Mitigation Plan when you register for the database. There are only guidelines as to what your plan must include so you can write your own or get a consultant to help you! Follow the process below to sign up for the Mitigation Database. There is no pre-registration process to qualify for a token. You'll register and note that you are either fully compliant, partially compliant or not compliant at all. Don't tell them what you plan to be on June 30th - list what you are today. ONCE YOU ARE FULLY COMPLIANT, THEN YOU CAN LOG BACK IN AND CHANGE YOUR STATUS! Second change made earlier this year is that your company no longer needs to be certified as a CLEC, ILEC, IPES, or Wireless Carrier to get a STIR/SHAKEN certificate! If you' file 499s and have an agreement with a DID provider, you can get an OCN assigned and qualify for the STIR/SHAKEN certificate by completing the mitigation database process. Once your name has been published on the FCC site for the mitigation database, you can register with the STI-PA and work with a Certificate Authority to get a token and test your traffic. ------------------------------------------------------------------------- Below are the links for the Mitigation Database piece -------------------------------------------------------------------------: a. Associate your FRNs with your 499 filer ID. https://apps.fcc.gov/cores/html/Associate_Username_to_FRN.htm b. Sign up for Mitigation Database https://www.fcc.gov/licensing-databases/fcc-user-login?fromURI=https%3A%2F%… parm_uri%253D%25252Fnav_to.do%25253Furi%25253D%2525252Frmd%2525253Fid%2525253Drmd_landing 1). Answer your current status: (fully compliant, partially compliant, non-compliant) 2). Submit your "Robocall Mitigation Plan" 4. Register with the STI-PA https://authenticate.iconectiv.com/service-provider-authenticate 5. Select a Certificate Authority to assign your token and test with: https://authenticate.iconectiv.com/certification-authority-authenticate 6. If you have not filed as 100% compliant, go back into the mitigation database when you are done testing and revise your status to "100% compliant!" If you have any questions, just give me a call! MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796-1111

2 3

9-1-1 outage, NPA843 SC
by jra＠baylink.com May 20, 2021

May 20, 2021

I've had a CMAS alert relayed to me this afternoon saying that 9-1-1 service is inop in Berkeley, Charleston, Colleton and Dorchester counties, South Carolina... which seem *suspiciously* alphabetical to me -- and no, that's not intended as humor. Cheers, -- jra -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274

1 0

Teams Telephony and custom music on hold
by cboyd＠gizmopartners.com May 12, 2021

May 12, 2021

Has anyone found a way to implement custom music on hold for Teams Telephony? Apparently MS overlooked a basic function. ?Chris

2 1

Malformed Caller ID
by voiceops＠ics-il.net April 22, 2021

April 22, 2021

Have any of you noticed an increase in customer complaints of malformed caller ID? We do a test call out as the customer, whether it's to one of our cell phones or one of the incumbent's POTS lines. Everything shows up as expected. The number is formatted correctly. The Caller ID name is formatted correctly. However, we're getting customer complaints that the caller ID is saying Japan (we have nothing to do with Japan), United States, blank, or some other combination. We're just not able to confirm that. Of course customers are reluctant to tell us what the numbers are of the remote parties having these issues, so we can't really look for common denominators. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com

4 4

Reputation Score Aggregator
by ciscoplumber＠gmail.com April 21, 2021

April 21, 2021

Does anyone know of a company that allows you to search the reputation of an ANI across the various robocall mitigation companies and/or carriers? For example instead of querying TNS, Neustar, Hiya, etc individually which may not be possible without having their service, is there a company that allows you to check the ANI against a variety of providers in one place? Right now if a customer reports a mislabeled spam call we need to determine the terminating carrier and work with them. This issue could also be happening on multiple carriers (or robocall mitigation companies) and it would be nice to see them all in one place. Thanks

1 0

Phase III clinical trials of Kamailio DMQ
by abalashov＠evaristesys.com April 1, 2021

April 1, 2021

For immediate release: GAINESVILLE, Florida (1 April 2021)--Evariste Systems, in partnership with Posner | Palner Pharmaceuticals, are pleased to announce the eagerly anticipated start of Phase III clinical trials of Kamailio DMQ module replication. In this stage of the investigation of the promising replication scheme, which was developed in record time, DMQ will be tested in a rigourous, double-blind, controlled CI/CD process for large-scale efficacy and continually monitored for safety in shorter and longer terms. The now-concluded second phase established basic safety and Phase 2b entailed a dose-finding study for the optimal number of batched `dmq_usrloc` contacts per kilogram of cloud computing resource. The main cohort of the main sequence of the Phase III trial will enroll 380 randomly selected, statistically representative Floridian SIP registrars and 5700 SIP dialogs, also in the state of Florida. When asked about the disparity in the number of registrars versus dialogs, Alex Balashov of Evariste said, "It is reflective of the small number of SIP registrars in Florida; not to be indelicate, but consider the median age of the population." As previously remarked upon in proceedings of the World SIP Organisation (WSO), the choice of Florida as a venue attracted some questions. We asked Fred Posner of Posner | Palner about the clinical background informing this choice of replication study cohort: "Florida is a good place to find eventual consistency failures; the open climate and reluctance to accept traditional data integrity science would have sealed the deal, but when people started to drink bleach here, I saw an opportunity." Evariste and Posner | Palner are aiming for a US Food & Drug Administration EUA (Emergency Use Authorisation) for DMQ replication as a prophylactic data redundancy and failover measure to ward off the development of moderate to severe viral Sonus Haemorrhagic Fever symptoms. Phase II studies have painted a promising a picture of the DMQ architecture's ability to reduce moderate to severe symptoms and associated 28-day mortality by more than 90%, albeit over a small sample size and in enterprise patients with known pre-existing comorbidities such as Session Border Controller and BroadSoft Multi-System Inflammatory Syndrome. Phase III trials seek to bolster quantums of broader efficacy, including efficacy for localised outbreaks of small to medium business softswitch. Of the control group, Balashov said, "They will receive a standard pipe-to-/dev/null placebo protocol, but with identical '200 OK' confirmation messages. We proudly developed this approach in early 2020 in consultation with the highest levels of the Trump presidential administration; it is called TENP, or 'The Emperor's New Potion.' It is a successor to that administration's previous approved placebo protocol, SHTI - Small Hands, Tremendous Initiatives." Despite speculative autism and packet fragmentation claims by Florida Governor Ron DeSantis, Balashov was quick to provide reassurance about side effects from DMQ in the Phase III trial. "The incidence of severe allergies to plain-text UDP was within standard deviation over the mean for all insecure replication, and there's support for other transports on the way. Anyway, we have a robust adverse effects reporting system in our issue tracker and solid surveillance. Don't let partisan politics dissuade you from allowing request lines with the KDMQ method." Other industry sources have reported that DMQ is not the only replication investigation undertaken by Evariste and Posner | Palner, although it is the only prophylactic suitable for the early infection development and inflammatory phases of a broad class of SBC-complex syndromes typically afflicting service providers. A recent IETF preprint by the same authors has shown high-quality preliminary data suggesting statistically significant improvement in morbidity outcomes from Perimeta and Nokia via a later-stage therapeutic intervention with a monoclonal, monorepo Github cocktail administered intravenously. -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

6 9

988 - Suicide prevention hotline
by dovid＠telecurve.com March 25, 2021

March 25, 2021

Hi, We got word about 988 being a new code for the Suicide prevention hotline. Does anyone know where there are listings as to where that code should be forwarded to?

2 1