Re: [VoiceOps] TF CPR dip?

2023-08-09 Thread David Frankel via VoiceOps
An additional morsel to bear in mind is that a "direct routed" TFN (via the CPR) can use percent allocation to different CICs. We do this with our TFNs to provide diversity. So for one of our TFNs, you can query from the same originating exchange, at the same time of day and day of week, and get b

Re: [VoiceOps] Call term misrouting?

2023-07-26 Thread David Frankel via VoiceOps
Mark's reference to the RCC regs is pointing in the right direction. The problem stems from sketchy providers trying to save money routing via circuitous pathways, which often end up with the misbehaviors cited in this thread. Nathan's comments that he's been through TWELVE rounds of provider bla

Re: [VoiceOps] Update on STIR/SHAKEN

2023-07-12 Thread David Frankel via VoiceOps
Nathan: Thanks for sharing your thinking and a specific example. I can't speak for the FCC or the ITG (obviously) and they probably won't weigh in here. But, as Mary has done, I can share what I hope is a reasonably accurate perspective. I hope, Nathan, that the key is your statement: "But sans a

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-07 Thread David Frankel via VoiceOps
ort, I will note that I have yet to see a S/S signature/PASSporT attached to ANY calls made *to* ANY of our 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> mailto:voiceops-boun..

Re: [VoiceOps] STIR/SHAKEN warning!

2023-07-07 Thread David Frankel via VoiceOps
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 to use” the calling number. The signer can “know” that in any of a variety of ways. For toll-free numbers, the most sophist

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-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] All carriers must get their STIR/SHAKEN certificate by June 30th!

2023-06-01 Thread David Frankel via VoiceOps
I don't want to go too far into the weeds on what "facilities-based" means, because it 30 days it isn't going to matter. A brief abbreviated history (others can chime in if I've left out something of substance or mis-characterized): When STIR/SHAKEN was about to be mandated mid-2021, there was a c

Re: [VoiceOps] All carriers must get their STIR/SHAKEN certificate by June 30th!

2023-06-01 Thread David Frankel via VoiceOps
I am not an attorney; this is not legal advice. The (primary) purpose of STIR/SHAKEN was not to help the ITG. The purposes are to (at the terminating or called-party end of the call) identify the entity responsible for originating the call, and allow that entity to signal what they know about the