Re: [VoiceOps] Identity Header Test Tool
Thanks for this, David, very helpful. Earlier Lee asked, *"If term provider 2 has TDM trunks with term provider 1, there would be no headers to pass, correct?"* This is one of the (many) flaws to the SHAKEN implementation. It ignores the fact that there's still tons of legacy telco networking out there. And as such, an awful lot of traffic is having its attestation stripped. There's an out-of-band API lookup that can be used, but I don't think anyone's using it, really. Today, a small percentage of traffic we receive is attested. It's hard to turn on verification if most of the traffic is going to get flagged as possible spam -- it's like the boy who cried wolf. On Sun, Jul 3, 2022 at 11:13 AM David Frankel wrote: > Last week I was forwarded a note from this list regarding tools to test and > debug SHAKEN Identity headers. That prompted us to stitch together some > modules we already had in an attempt to help. > > What we have is at http://identity.legalcallsonly.org. You can call one of > the test numbers listed on that page, and if we receive your header, we'll > read you a six-digit code. Disconnect and then plug the code into the box > on > the web form, and we'll show you details of that Identity header. > > Perhaps most importantly, you'll be able to see if the header we received > is > the one you sent. In addition, we parse the header and try to tell you if > it > is correctly formatted and valid. > > Currently we have a couple of geographic DIDs and three toll-free numbers > (each using different underlying providers). So far we aren't having a lot > of success getting the Identity headers on the TFNs; we're working to > improve that. > > Suggestions welcome. We hope the tool provokes more discussion about best > practices regarding making the Authentication Framework as functional and > useful as possible. > > Happy 4th of July! > > David Frankel > ZipDX LLC > St. George, UT USA > > > ___ > VoiceOps mailing list > VoiceOps@voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops > ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] Identity Header Test Tool
Thank you for building this. It helped us verify that we are correctly passing the Identity headers. I've found that no one is universally passing the headers end to end to all the test numbers. Some of our vendors will make it all the way to most but not all. I also think that some of the inbound validation is failing because of how the DID is routed to the end device. If a trunk is set to deliver e164 with a + in the From but the Identity header doesn't contain that, the validation match fails. I've tested the ZipDX numbers, Sansay, and Voxbeam numbers from full LCR and "OnNet" trunks via ANI, Bandwidth, Comcast, Intrado, Peerless, Sinch, and Level3. The closest to perfect is ANI's Toll Free passes validation to all 3 of ZipDX's TF DIDs. Bandwidth OnNet passes validation to all the numbers that are reachable via that route. ~Jared On Sun, Jul 3, 2022 at 8:12 AM David Frankel wrote: > Last week I was forwarded a note from this list regarding tools to test and > debug SHAKEN Identity headers. That prompted us to stitch together some > modules we already had in an attempt to help. > > What we have is at http://identity.legalcallsonly.org. You can call one of > the test numbers listed on that page, and if we receive your header, we'll > read you a six-digit code. Disconnect and then plug the code into the box > on > the web form, and we'll show you details of that Identity header. > > Perhaps most importantly, you'll be able to see if the header we received > is > the one you sent. In addition, we parse the header and try to tell you if > it > is correctly formatted and valid. > > Currently we have a couple of geographic DIDs and three toll-free numbers > (each using different underlying providers). So far we aren't having a lot > of success getting the Identity headers on the TFNs; we're working to > improve that. > > Suggestions welcome. We hope the tool provokes more discussion about best > practices regarding making the Authentication Framework as functional and > useful as possible. > > Happy 4th of July! > > David Frankel > ZipDX LLC > St. George, UT USA > > > ___ > VoiceOps mailing list > VoiceOps@voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops > ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
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, whichever one has the network they want to keep. The contracts, carrier relationships, OCNs, SPIDs and other stuff may have common administrative control, but remain legally distinct for regulatory reasons. (For example, Global Crossing’s network was gradually shut down while new services were provisioned solely on Level 3’s networks, and customers were moved with some small incentives at first, and once it reached critical mass, the incentive was just “your service will keep working” – parts of it likely still exist anyway, at least on paper. And I took over codeholder ownership this month at my day job of an NPA/NXX that belonged to a carrier that went defunct in 2004-2006 or thereabouts. It takes a LONG time for some of that stuff to shake out. I did so because we held numbers in the range that had been ported-in that would have been removed if we did not) Sent from Mail for Windows From: Nathan AndersonSent: Tuesday, July 5, 2022 8:09 PMTo: 'Mary Lou Carey'Cc: voiceops@voiceops.orgSubject: 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 before posting, but it just struck me as a Twilio clone, and I simply assumed they were using IQ numbers. I don't have a subscription to LERG, and it's not clear to me how often publicly-available resources (e.g., telcodata.us) are updated. But in most places, the IQ OCNs still seem to be listed as "ONVOY, LLC", and from looking at the IQ web site which is still a separate thing, it appears Sinch is looking to preserve the IQ branding for that set of products. So absent some change in marketing strategy or yet another set of acquisitions, I'm guessing that the OCN name is unlikely to change in the foreseeable future... -- Nathan -Original Message- From: Mary Lou Carey [mailto:mary...@backuptelecom.com] Sent: Tuesday, July 5, 2022 4:27 PM To: Nathan Anderson Cc: 'David Frankel' ; voiceops@voiceops.org Subject: 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 different affiliate companies. So you can't always go by the name associated with the OCN. A better way to tell which NXXs are part of each carrier's network is to pay attention to the AOCN number associated with each of the NXXs in the LERG. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796- On 2022-07-05 05:52 PM, Nathan Anderson wrote: > 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 here have observed happening to them, calling the > Bandwidth.com number results in the call being shown as attested, but > our original signed attestation has gone missing and been replaced > with a "B"-level attestation by Bandwidth themselves. So perhaps VI > does not send any term traffic to Bandwidth, or they just aren't > included in the T.38 LCR (very likely, since VI's portal indicates > that Bandwidth does not support T.38 on origination, so it's equally > likely they don't for term, either, especially since it's much tricker > to support for term if you aren't doing the T.38 gatewaying for all > TDM- or POTS-destined traffic yourself), and either some intermediate > provider is stripping our Identity header out or it's going > IP-to-TDM-to-IP with no STI-CPS/OOB-SHAKEN. > > The Sinch number seems to be hosted by Inteliquent, and our own signed > "A"-level attestation arrives at the destination unmolested. Makes > sense since VI does a ton of business with IQ. > > None of our calls to any of the toll-free numbers are attested at all. > Somewhat surprising in the case of Lumen/L3, even more surprising > with Sinch/IQ. > > -- Nathan > > -Original Message- > From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of > David Frankel
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 the target OCN so really the only way someone who doesn't have direct access to BIRRDS can tell is by looking up the AOCN number in the LERG. All the big guys have been operating this way for years so it's pretty much a big mess because of all the mergers. I only know about Sinch because I have a dedicated sales rep I work with for the majority of my consulting clients. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796- On 2022-07-05 07:09 PM, Nathan Anderson wrote: 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 before posting, but it just struck me as a Twilio clone, and I simply assumed they were using IQ numbers. I don't have a subscription to LERG, and it's not clear to me how often publicly-available resources (e.g., telcodata.us) are updated. But in most places, the IQ OCNs still seem to be listed as "ONVOY, LLC", and from looking at the IQ web site which is still a separate thing, it appears Sinch is looking to preserve the IQ branding for that set of products. So absent some change in marketing strategy or yet another set of acquisitions, I'm guessing that the OCN name is unlikely to change in the foreseeable future... -- Nathan -Original Message- From: Mary Lou Carey [mailto:mary...@backuptelecom.com] Sent: Tuesday, July 5, 2022 4:27 PM To: Nathan Anderson Cc: 'David Frankel' ; voiceops@voiceops.org Subject: 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 different affiliate companies. So you can't always go by the name associated with the OCN. A better way to tell which NXXs are part of each carrier's network is to pay attention to the AOCN number associated with each of the NXXs in the LERG. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796- On 2022-07-05 05:52 PM, Nathan Anderson wrote: 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 here have observed happening to them, calling the Bandwidth.com number results in the call being shown as attested, but our original signed attestation has gone missing and been replaced with a "B"-level attestation by Bandwidth themselves. So perhaps VI does not send any term traffic to Bandwidth, or they just aren't included in the T.38 LCR (very likely, since VI's portal indicates that Bandwidth does not support T.38 on origination, so it's equally likely they don't for term, either, especially since it's much tricker to support for term if you aren't doing the T.38 gatewaying for all TDM- or POTS-destined traffic yourself), and either some intermediate provider is stripping our Identity header out or it's going IP-to-TDM-to-IP with no STI-CPS/OOB-SHAKEN. The Sinch number seems to be hosted by Inteliquent, and our own signed "A"-level attestation arrives at the destination unmolested. Makes sense since VI does a ton of business with IQ. None of our calls to any of the toll-free numbers are attested at all. Somewhat surprising in the case of Lumen/L3, even more surprising with Sinch/IQ. -- Nathan -Original Message- From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of David Frankel Sent: Sunday, July 3, 2022 8:05 AM To: voiceops@voiceops.org Subject: [VoiceOps] Identity Header Test Tool Last week I was forwarded a note from this list regarding tools to test and debug SHAKEN Identity headers. That prompted us to stitch together some modules we already had in an attempt to help. What we have is at http://identity.legalcallsonly.org. You can call one of the test numbers listed on that page, and if we receive your header, we'll read you a six-digit code. Disconnect and then plug the code into the box on the web form, and we'll show you details of that Identity header. Perhaps most importantly, you'll be able to see if the header we received is the one you sent. In addition, we parse the header and try to tell you if it is correctly formatted and
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 before posting, but it just struck me as a Twilio clone, and I simply assumed they were using IQ numbers. I don't have a subscription to LERG, and it's not clear to me how often publicly-available resources (e.g., telcodata.us) are updated. But in most places, the IQ OCNs still seem to be listed as "ONVOY, LLC", and from looking at the IQ web site which is still a separate thing, it appears Sinch is looking to preserve the IQ branding for that set of products. So absent some change in marketing strategy or yet another set of acquisitions, I'm guessing that the OCN name is unlikely to change in the foreseeable future... -- Nathan -Original Message- From: Mary Lou Carey [mailto:mary...@backuptelecom.com] Sent: Tuesday, July 5, 2022 4:27 PM To: Nathan Anderson Cc: 'David Frankel' ; voiceops@voiceops.org Subject: 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 different affiliate companies. So you can't always go by the name associated with the OCN. A better way to tell which NXXs are part of each carrier's network is to pay attention to the AOCN number associated with each of the NXXs in the LERG. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796- On 2022-07-05 05:52 PM, Nathan Anderson wrote: > 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 here have observed happening to them, calling the > Bandwidth.com number results in the call being shown as attested, but > our original signed attestation has gone missing and been replaced > with a "B"-level attestation by Bandwidth themselves. So perhaps VI > does not send any term traffic to Bandwidth, or they just aren't > included in the T.38 LCR (very likely, since VI's portal indicates > that Bandwidth does not support T.38 on origination, so it's equally > likely they don't for term, either, especially since it's much tricker > to support for term if you aren't doing the T.38 gatewaying for all > TDM- or POTS-destined traffic yourself), and either some intermediate > provider is stripping our Identity header out or it's going > IP-to-TDM-to-IP with no STI-CPS/OOB-SHAKEN. > > The Sinch number seems to be hosted by Inteliquent, and our own signed > "A"-level attestation arrives at the destination unmolested. Makes > sense since VI does a ton of business with IQ. > > None of our calls to any of the toll-free numbers are attested at all. > Somewhat surprising in the case of Lumen/L3, even more surprising > with Sinch/IQ. > > -- Nathan > > -Original Message- > From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of > David Frankel > Sent: Sunday, July 3, 2022 8:05 AM > To: voiceops@voiceops.org > Subject: [VoiceOps] Identity Header Test Tool > > Last week I was forwarded a note from this list regarding tools to > test and debug SHAKEN Identity headers. That prompted us to stitch > together some modules we already had in an attempt to help. > > What we have is at http://identity.legalcallsonly.org. You can call > one of the test numbers listed on that page, and if we receive your > header, we'll read you a six-digit code. Disconnect and then plug the > code into the box on the web form, and we'll show you details of that > Identity header. > > Perhaps most importantly, you'll be able to see if the header we > received is the one you sent. In addition, we parse the header and try > to tell you if it is correctly formatted and valid. > > Currently we have a couple of geographic DIDs and three toll-free > numbers (each using different underlying providers). So far we aren't > having a lot of success getting the Identity headers on the TFNs; > we're working to improve that. > > Suggestions welcome. We hope the tool provokes more discussion about > best practices regarding making the Authentication Framework as > functional and useful as possible. > > Happy 4th
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 different affiliate companies. So you can't always go by the name associated with the OCN. A better way to tell which NXXs are part of each carrier's network is to pay attention to the AOCN number associated with each of the NXXs in the LERG. MARY LOU CAREY BackUP Telecom Consulting Office: 615-791-9969 Cell: 615-796- On 2022-07-05 05:52 PM, Nathan Anderson wrote: 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 here have observed happening to them, calling the Bandwidth.com number results in the call being shown as attested, but our original signed attestation has gone missing and been replaced with a "B"-level attestation by Bandwidth themselves. So perhaps VI does not send any term traffic to Bandwidth, or they just aren't included in the T.38 LCR (very likely, since VI's portal indicates that Bandwidth does not support T.38 on origination, so it's equally likely they don't for term, either, especially since it's much tricker to support for term if you aren't doing the T.38 gatewaying for all TDM- or POTS-destined traffic yourself), and either some intermediate provider is stripping our Identity header out or it's going IP-to-TDM-to-IP with no STI-CPS/OOB-SHAKEN. The Sinch number seems to be hosted by Inteliquent, and our own signed "A"-level attestation arrives at the destination unmolested. Makes sense since VI does a ton of business with IQ. None of our calls to any of the toll-free numbers are attested at all. Somewhat surprising in the case of Lumen/L3, even more surprising with Sinch/IQ. -- Nathan -Original Message- From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of David Frankel Sent: Sunday, July 3, 2022 8:05 AM To: voiceops@voiceops.org Subject: [VoiceOps] Identity Header Test Tool Last week I was forwarded a note from this list regarding tools to test and debug SHAKEN Identity headers. That prompted us to stitch together some modules we already had in an attempt to help. What we have is at http://identity.legalcallsonly.org. You can call one of the test numbers listed on that page, and if we receive your header, we'll read you a six-digit code. Disconnect and then plug the code into the box on the web form, and we'll show you details of that Identity header. Perhaps most importantly, you'll be able to see if the header we received is the one you sent. In addition, we parse the header and try to tell you if it is correctly formatted and valid. Currently we have a couple of geographic DIDs and three toll-free numbers (each using different underlying providers). So far we aren't having a lot of success getting the Identity headers on the TFNs; we're working to improve that. Suggestions welcome. We hope the tool provokes more discussion about best practices regarding making the Authentication Framework as functional and useful as possible. Happy 4th of July! David Frankel ZipDX LLC St. George, UT USA ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
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 here have observed happening to them, calling the Bandwidth.com number results in the call being shown as attested, but our original signed attestation has gone missing and been replaced with a "B"-level attestation by Bandwidth themselves. So perhaps VI does not send any term traffic to Bandwidth, or they just aren't included in the T.38 LCR (very likely, since VI's portal indicates that Bandwidth does not support T.38 on origination, so it's equally likely they don't for term, either, especially since it's much tricker to support for term if you aren't doing the T.38 gatewaying for all TDM- or POTS-destined traffic yourself), and either some intermediate provider is stripping our Identity header out or it's going IP-to-TDM-to-IP with no STI-CPS/OOB-SHAKEN. The Sinch number seems to be hosted by Inteliquent, and our own signed "A"-level attestation arrives at the destination unmolested. Makes sense since VI does a ton of business with IQ. None of our calls to any of the toll-free numbers are attested at all. Somewhat surprising in the case of Lumen/L3, even more surprising with Sinch/IQ. -- Nathan -Original Message- From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of David Frankel Sent: Sunday, July 3, 2022 8:05 AM To: voiceops@voiceops.org Subject: [VoiceOps] Identity Header Test Tool Last week I was forwarded a note from this list regarding tools to test and debug SHAKEN Identity headers. That prompted us to stitch together some modules we already had in an attempt to help. What we have is at http://identity.legalcallsonly.org. You can call one of the test numbers listed on that page, and if we receive your header, we'll read you a six-digit code. Disconnect and then plug the code into the box on the web form, and we'll show you details of that Identity header. Perhaps most importantly, you'll be able to see if the header we received is the one you sent. In addition, we parse the header and try to tell you if it is correctly formatted and valid. Currently we have a couple of geographic DIDs and three toll-free numbers (each using different underlying providers). So far we aren't having a lot of success getting the Identity headers on the TFNs; we're working to improve that. Suggestions welcome. We hope the tool provokes more discussion about best practices regarding making the Authentication Framework as functional and useful as possible. Happy 4th of July! David Frankel ZipDX LLC St. George, UT USA ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] Identity Header Test Tool
I see you have Bandwdith there. As an FYI when you *send* calls via BandWidth if you send the identity header with compact SIP headers they drop it. This is a known issue by them that they are working on. On Sun, Jul 3, 2022 at 11:13 AM David Frankel wrote: > Last week I was forwarded a note from this list regarding tools to test and > debug SHAKEN Identity headers. That prompted us to stitch together some > modules we already had in an attempt to help. > > What we have is at http://identity.legalcallsonly.org. You can call one of > the test numbers listed on that page, and if we receive your header, we'll > read you a six-digit code. Disconnect and then plug the code into the box > on > the web form, and we'll show you details of that Identity header. > > Perhaps most importantly, you'll be able to see if the header we received > is > the one you sent. In addition, we parse the header and try to tell you if > it > is correctly formatted and valid. > > Currently we have a couple of geographic DIDs and three toll-free numbers > (each using different underlying providers). So far we aren't having a lot > of success getting the Identity headers on the TFNs; we're working to > improve that. > > Suggestions welcome. We hope the tool provokes more discussion about best > practices regarding making the Authentication Framework as functional and > useful as possible. > > Happy 4th of July! > > David Frankel > ZipDX LLC > St. George, UT USA > > > ___ > VoiceOps mailing list > VoiceOps@voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops > ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Re: [VoiceOps] Identity Header Test Tool
My call to the Sinch TFN resulted in a valid Identity header. Calls to other TFNs received no identity header. Calls to Sinch 1-425 ## answer & disconnect immediately Thanks for setting this up From: VoiceOps on behalf of David Frankel Date: Sunday, July 3, 2022 at 11:13 AM To: voiceops@voiceops.org Subject: [VoiceOps] Identity Header Test Tool CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe. Last week I was forwarded a note from this list regarding tools to test and debug SHAKEN Identity headers. That prompted us to stitch together some modules we already had in an attempt to help. What we have is at http://identity.legalcallsonly.org. You can call one of the test numbers listed on that page, and if we receive your header, we'll read you a six-digit code. Disconnect and then plug the code into the box on the web form, and we'll show you details of that Identity header. Perhaps most importantly, you'll be able to see if the header we received is the one you sent. In addition, we parse the header and try to tell you if it is correctly formatted and valid. Currently we have a couple of geographic DIDs and three toll-free numbers (each using different underlying providers). So far we aren't having a lot of success getting the Identity headers on the TFNs; we're working to improve that. Suggestions welcome. We hope the tool provokes more discussion about best practices regarding making the Authentication Framework as functional and useful as possible. Happy 4th of July! David Frankel ZipDX LLC St. George, UT USA ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
[VoiceOps] Identity Header Test Tool
Last week I was forwarded a note from this list regarding tools to test and debug SHAKEN Identity headers. That prompted us to stitch together some modules we already had in an attempt to help. What we have is at http://identity.legalcallsonly.org. You can call one of the test numbers listed on that page, and if we receive your header, we'll read you a six-digit code. Disconnect and then plug the code into the box on the web form, and we'll show you details of that Identity header. Perhaps most importantly, you'll be able to see if the header we received is the one you sent. In addition, we parse the header and try to tell you if it is correctly formatted and valid. Currently we have a couple of geographic DIDs and three toll-free numbers (each using different underlying providers). So far we aren't having a lot of success getting the Identity headers on the TFNs; we're working to improve that. Suggestions welcome. We hope the tool provokes more discussion about best practices regarding making the Authentication Framework as functional and useful as possible. Happy 4th of July! David Frankel ZipDX LLC St. George, UT USA ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
