Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-13 Thread Mike Johnston via VoiceOps
On 2023-07-12 16:37, Nathan Anderson via VoiceOps wrote: By the way, love your test tool service.  Thanks for putting it together and maintaining it...what a gift to the community. There are a handful of S/S testing tools out there, but yours is easily the most comprehensive...most just audibly

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-12 Thread Nathan Anderson via VoiceOps
, but gives you some idea of call paths that might be breaking transmission of your PASSporT and which ones are okay. Super helpful! From: David Frankel [mailto:dfran...@zipdx.com] Sent: Friday, July 7, 2023 3:21 PM To: Nathan Anderson; 'Voice Ops' Subject: RE: [VoiceOps] S

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-12 Thread Mary Lou Carey via VoiceOps
To answer your question regarding 499s and OCNs, foreign companies can acquire both. If you want to message me privately, I can give you the contact information of the person I refer foreign companies to. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796- On 2023-

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-07 Thread David Frankel via VoiceOps
on't travel over TDM, those calls will not have signatures at the terminating end. David From: VoiceOps On Behalf Of Nathan Anderson via VoiceOps Sent: Friday, July 7, 2023 3:55 PM To: Voice Ops Subject: Re: [VoiceOps] STIR/SHAKEN warning! Thanks; I had no idea this was a thing.

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-07 Thread Nathan Anderson via VoiceOps
Thanks; I had no idea this was a thing. -- Nathan From: Paul Timmins [mailto:p...@timmins.net] Sent: Friday, July 7, 2023 2:39 PM To: Nathan Anderson Cc: Voice Ops Subject: Re: [VoiceOps] STIR/SHAKEN warning! Always worth pointing out that in March 2020, Somos rolled out TFNIdentity

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-07 Thread Paul Timmins via VoiceOps
ur TFNs, via any of the 3 SIP wholesalers we have used as both > RespOrgs & for actual traffic. > > -- Nathan >   <> > From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of David > Frankel via VoiceOps > Sent: Friday, July 7, 2023 7:52 AM > To: 'I

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-07 Thread Nathan Anderson via VoiceOps
7, 2023 7:52 AM To: 'Ivan Kovacevic'; 'Voice Ops' Subject: Re: [VoiceOps] STIR/SHAKEN warning! Ivan asks: “How are you handling TFN atestations?” When the signer of a call gives A-level attestation, it means that the signer knows that the caller “is authorized

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-07 Thread David Frankel via VoiceOps
) that prohibit providers from setting these kinds of rules. From: VoiceOps On Behalf Of Ivan Kovacevic via VoiceOps Sent: Friday, July 7, 2023 7:27 AM To: Voice Ops Subject: Re: [VoiceOps] STIR/SHAKEN warning! Hopefully on-topic. How are you handling TFN atestations? Although a part

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-07 Thread Ivan Kovacevic via VoiceOps
Hopefully on-topic. How are you handling TFN atestations? Although a part of NANP - it's a different technology at the network level in terms of chain of authority and routing. RespOrg manages the number, but can provision and use many carriers to make outbound calls using the TFN Caller ID (and

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-06 Thread David Frankel via VoiceOps
Nathan wrote: "Since implementing S/S in the U.S. requires a 499 Filer ID, it is actually kind of infuriating that the RMD does not have 499 Filer ID as a required field on their form. That would nip this issue right in the bud if they did." Yes, that would be a good idea. Generally it is easier

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-06 Thread David Frankel via VoiceOps
I checked in with iconectiv to get a bit more clarification. iconectiv does not speak authoritatively as to what it takes to get a 499A filer ID, nor an OCN. Of course, I don't either. You should go to the respective authorities (USAC and NECA) to make your applications. There ARE foreign entiti

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-06 Thread Nathan Anderson via VoiceOps
nip this issue right in the bud if they did. -- Nathan -Original Message- From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of Markus via VoiceOps Sent: Thursday, July 6, 2023 1:07 PM To: voiceops@voiceops.org Subject: Re: [VoiceOps] STIR/SHAKEN warning! Am 04.07.2023 um 07

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-06 Thread Nathan Anderson via VoiceOps
nip this issue right in the bud if they did. -- Nathan -Original Message- From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of Markus via VoiceOps Sent: Thursday, July 6, 2023 1:07 PM To: voiceops@voiceops.org Subject: Re: [VoiceOps] STIR/SHAKEN warning! Am 04.07.2023 um 07

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-06 Thread Markus via VoiceOps
Am 04.07.2023 um 07:35 schrieb Paul Timmins: What if I'm an European telecom operator and have US-based end-users (via SIP) who are calling to the US and who would like to signal their United States A-number to the called party? What if I'm an European telecom operator and have Euro end-users

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-04 Thread David Frankel via VoiceOps
Some additional perspective on STIR/SHAKEN signing requirements. This is not legal advice; for that, turn to your qualified attorney well-versed in applicable telecommunications regulations (US Federal and State). Several relevant STIR/SHAKEN regulations are here: https://www.law.cornell.edu/cfr/t

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-03 Thread Paul Timmins via VoiceOps
> On Jul 3, 2023, at 8:05 PM, Markus via VoiceOps wrote: > > Am 30.06.2023 um 23:00 schrieb Mary Lou Carey via VoiceOps: >> I've heard from several clients that their upstream carrier told them they >> don't need to worry about being STIR/SHAKEN compliant because they are >> taking care of e

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-03 Thread Markus via VoiceOps
Am 30.06.2023 um 23:00 schrieb Mary Lou Carey via VoiceOps: I've heard from several clients that their upstream carrier told them they don't need to worry about being STIR/SHAKEN compliant because they are taking care of everything for them. THAT IS NOT CORRECT! Every phone company is required

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-03 Thread Mary Lou Carey via VoiceOps
My understanding is that they can still sign for you, but they should be signing with YOUR certificate/token and not their own. That only adds the cost of the certificate/token to your budget. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796- On 2023-07-03 01:45

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-03 Thread Carlos Alvarez via VoiceOps
I would love an update here. We are an ultra tiny MSP, and have been told all along by the major ULCs we use that we’re fine. They are signing, all good. This is a monstrous change relative to our size and capital. On Jul 3, 2023 at 11:09:33 AM, Mary Lou Carey via VoiceOps < voiceops@voiceops

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-03 Thread Mary Lou Carey via VoiceOps
Thanks for the input, Mark! I'm going to call my contacts at the FCC as well and ask specifically what their stance o this is because from what I've heard they plan to start enforcing STIR/SHAKEN in August. That could be devastating to many since so many of the underlying carriers have been tel

Re: [VoiceOps] STIR/SHAKEN warning!

2023-06-30 Thread Mark R Lindsey via VoiceOps
Like Mary Lou, I'd like to help all voice service providers get their STIR/SHAKEN implementations up and running. And it's crucial to do verification as well as attestation!

[VoiceOps] STIR/SHAKEN warning!

2023-06-30 Thread Mary Lou Carey via VoiceOps
I've heard from several clients that their upstream carrier told them they don't need to worry about being STIR/SHAKEN compliant because they are taking care of everything for them. THAT IS NOT CORRECT! Every phone company is required to have its own certificate/token! It doesn't matter if y