Re: [VoiceOps] Identity Header Test Tool

I can’t speak for the other sites, but telcodata.us updates 3 times a week from the CNAC, NANPA, and National Pooling. Often because of how much work it is to change ownership and networks and everything else, carriers who get acquired usually get attritioned off into one of the two over time,

Re: [VoiceOps] Identity Header Test Tool

It's a pain in the butt to change the OCN name on NXXs every time there is a merger. So most of the time the carriers just keep the name associated with the original company and just update the contact information and add a target OCN that ties them all together. I don't think the LERG lists

Re: [VoiceOps] Identity Header Test Tool

I was aware of Inteliquent's history as Neutral Tandem & then getting merged with Onvoy, who itself was also owned by Zayo at one point, etc. But had no idea they had been gobbled up by Sinch, or even who Sinch was...clearly I'm way behind on my news, lol. I did briefly glance at Sinch's page

Re: [VoiceOps] Identity Header Test Tool

Inteliquent was just got bought out by Sinch so they are one and the same. Inteliquent also bought out several companies like Onvoy several years back so it has multiple company names riding its network. It's my understanding that Sinch (fka Inteliquent) also sells DID services through several

Re: [VoiceOps] [EXTERNAL] Identity Header Test Tool

Mark Lindsey wrote: > The ATIS destination of the C-level attestation is for a situation > that, like flying pigs, doesn't appear to occur anywhere in reality. As a side-note, I have observed that when calling Lumen/Level3 DIDs of ours from an AT mobile, those calls arrive to us with "C"-level

Re: [VoiceOps] Identity Header Test Tool

This totally rocks; thank you for putting this together. In case anyone is interested, here is what I happen to see when calling any of these numbers through VoIP Innovations' T.38 deck; I will try other LCR rate decks of theirs, as well as other term providers, in the near future: Like others

Re: [VoiceOps] [EXTERNAL] Identity Header Test Tool

Carriers can host the signing of calls for other carriers, but every originating company needs its own token. VSPs can get fined big time for knowingly passing along robocalls of other carriers so just be very careful who you serve and make sure they have their own token. MARY LOU CAREY

Re: [VoiceOps] [EXTERNAL] Identity Header Test Tool

What are your opinions regarding intermediate carriers signing unattested calls? Not to say they are the source of the call, but to facilitate tracebacks and take accountability for transiting the call from whatever upstream didn't sign or preserve the signature. Calvin Ellison Systems

Re: [VoiceOps] [EXTERNAL] Identity Header Test Tool

Mark, Agreed. I guess it comes down to how to decide who the originating carrier is that should be doing the attestation. As an intermediate carrier, Bandwidth should just pass through whatever Identity header they get; but if there is no Identity header (stripped header, TDM link in the

Re: [VoiceOps] [EXTERNAL] Identity Header Test Tool

The primary problem to fix, in this scenario, is that Term Provider 2 is stripping the Identity header, and therefore violating 47 CFR § 64.6302(a) . So many engineers have configured SBCs to strip

Re: [VoiceOps] [EXTERNAL] Identity Header Test Tool

If that is the case, a scammer that should be either attested C, or not attested at all can game the system and upgrade their calls to any customer of Bandwidth to B. Granted, B attestation isn't much better than nothing, but still it violates both the intent and the letter of the law. David

Re: [VoiceOps] [EXTERNAL] Identity Header Test Tool

https://www.bandwidth.com/blog/abcs-of-attestation-and-analytics/ This may be helpful. Dave From: VoiceOps On Behalf Of Dovid Bender Sent: Tuesday, July 5, 2022 11:34 AM To: Zilk, David Cc: voiceops@voiceops.org Subject: Re: [VoiceOps] [EXTERNAL] Identity Header Test Tool It

Re: [VoiceOps] [EXTERNAL] Identity Header Test Tool

I expect Bandwidth is attesting that they know the identity of the SIP trunking provider that sent your call to Bandwidth. CDK Global -> [term provider 1] -> [term provider 2, Strips Identity Header] -> [term provider 3] -> [Bandwidth.com] ...And term provider 3 is a customer of

Re: [VoiceOps] [EXTERNAL] Identity Header Test Tool

It seems that BandWidth is currently signing all calls from their customer where the DID is not with BandWidth as B. On Tue, Jul 5, 2022 at 12:31 PM Zilk, David wrote: > I am getting results from a test to the Bandwidth number that are > confusing. It appears that our Identity header is not

Re: [VoiceOps] [EXTERNAL] Identity Header Test Tool

I am getting results from a test to the Bandwidth number that are confusing. It appears that our Identity header is not making it through to them, however the call does have an Identity header, certified by Bandwith, with B attestation. This is odd as we don't have any direct business