VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
July 2022
- 31 participants
- 83 messages
Identity Header Test Tool
by jared@compuwizz.net
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 <dfrankel at zipdx.com> 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 at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
July 6, 2022
TCPA SMS Short Code Spam Violations: Recommended Law Firm for Suit?
by beckman@angryox.com
One of my customers attempted to opt-out of some SMS Short Code campaign,
sent "STOP" and several other attempted keywords, all of which were
ignored, until we escalated with the carrier.
164 total SMS messages were sent to the customer AFTER sending STOP to the
short code over several months. $82,000 worth of fines.
I'd like to ensure that the senders are fined.
Can anyone recommend a firm to handle the TCPA violations law suit? I'm in
the Washington DC area and would prefer local, but will take a good firm
anywhere.
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
July 6, 2022
[EXTERNAL] Identity Header Test Tool
by abalashov@evaristesys.com
Allowing the unrestricted laundering of all calls placed through their network under their own ?B? attestation, uncritically and without differentiation, and without regard to any already-present attestation, is becoming a common intermediate service provider decision.
> On Jul 5, 2022, at 3:02 PM, Calvin Ellison <calvin.ellison at voxox.com> wrote:
>
> 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 Architect
> calvin.ellison at voxox.com
> +1 (213) 285-0555
>
>
>
>
> The information contained herein is confidential and privileged information or work product intended only for the individual or entity to whom it is addressed. Any unauthorized use, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately.
>
>
> On Tue, Jul 5, 2022 at 11:47 AM Zilk, David <David.Zilk at cdk.com> wrote:
> 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 path, originating carrier not attesting, etc.) then the only assumption they can make is that the partner originated the call (even if they didn?t) and ?B? is the only proper attestation they can apply.
>
>
>
> Bandwidth making the assumption that they are an intermediate carrier (and the unattested calls came from some other (non-partner) service provider) isn?t a reasonable assumption.
>
>
>
> David
>
>
>
> From: Mark Lindsey <lindsey at e-c-group.com>
> Sent: Tuesday, July 5, 2022 10:16 AM
> To: Zilk, David <David.Zilk at cdk.com>; voiceops at voiceops.org
> Subject: 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 every header except the handful they want to carry, but Identity needs to be added to those lists.
>
>
>
> The secondary problem to fix is that 47 CFR ? 64.6302(b) allows intermediate providers to legally opt out of STIR/SHAKEN in any practical fashion.
>
>
>
> I am speculating in the example call flow shown below, but I wouldn't see Bandwidth's behavior as a key problem. The ATIS destination of the C-level attestation is for a situation that, like flying pigs, doesn't appear to occur anywhere in reality. Nobody just accepts SIP traffic from random, anonymous sources for termination. I'm glad Bandwidth is adding the attestation that it can add.
>
>
>
> Mark R Lindsey | SMTS | +1-229-316-0013 | mark at ecg.co
>
> Schedule a meeting
>
>
>
>
> On Jul 5, 2022, at 13:01, Zilk, David <David.Zilk at cdk.com> wrote:
>
>
>
> 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 Zilk
>
> CDK Global/IP Networked Services
>
>
>
> From: Mark Lindsey <lindsey at e-c-group.com>
> Sent: Tuesday, July 5, 2022 9:58 AM
> To: Zilk, David <David.Zilk at cdk.com>
> Cc: voiceops at voiceops.org
> Subject: 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 Bandwidth.com.
>
>
>
>
>
>
>
> Mark R Lindsey | SMTS | +1-229-316-0013 | mark at ecg.co
>
> Schedule a meeting
>
>
>
>
>
> On Jul 5, 2022, at 12:19, Zilk, David <David.Zilk at cdk.com> wrote:
>
>
>
> 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 relationship with Bandwidth. How can they claim B attestation?
>
> David Zilk
> CDK Global/IP Networked Services
>
> -----Original Message-----
> From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of David Frankel
> Sent: Sunday, July 3, 2022 8:05 AM
> To: voiceops at voiceops.org
> Subject: [EXTERNAL] [VoiceOps] Identity Header Test Tool
>
> CAUTION: This email originated from outside of the CDK organization. Exercise caution when clicking links or opening attachments, especially from unknown senders.
>
> 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 at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
--
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/
July 6, 2022
Identity Header Test Tool
by paul@timmins.net
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20220706/8673295e/at…>
July 6, 2022
[EXTERNAL] Identity Header Test Tool
by alec.fenichel@transnexus.com
C level attestation is the appropriate attestation level for an intermediate provider to use when signing a call.
Below is the text from ATIS-1000074.v002 regarding B level attestation:
==============================================================
B. Partial Attestation: The signing provider shall satisfy all of the following conditions:
* Is responsible for the origination of the call onto the IP-based service provider voice network.
* Has a direct authenticated relationship with the customer and can identify the customer.
* Has NOT established a verified association with the telephone number being used for the call.
NOTE: By populating this value, the service provider attests that it can trace the source of the call to a customer for policy enforcement purposes.
==============================================================
An intermediate provider is not ?responsible for the origination of the call onto the IP-based service provider voice network?.
An intermediate provider does not have ?a direct authenticated relationship with the customer and can identify the customer?.
The FCC worded it slightly differently, but perhaps more clearly, in the First Report and Order (FCC-20-42A1):
==============================================================
8. The STIR/SHAKEN framework relies on the originating voice service provider attesting to the subscriber?s identity. The SHAKEN specification allows an originating voice service provider to provide different ?levels? of attestation. Specifically, the voice service provider can indicate that (i) it can confirm the identity of the subscriber making the call, and that the subscriber is using its associated telephone number (?full? or ?A? attestation); (ii) it can confirm the identity of the subscriber but not the telephone number (?partial? or ?B? attestation); or merely that (iii) it is the point of entry to the IP network for a call that originated elsewhere, such as a call that originated abroad or on a domestic network that is not STIR/SHAKEN-enabled (?gateway? or ?C? attestation).
==============================================================
An intermediate provider cannot ?confirm the identity of the subscriber?.
Sincerely,
Alec Fenichel
From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Nathan Anderson <nathana at fsr.com>
Date: Tuesday, July 5, 2022 at 19:04
To: 'Mark Lindsey' <lindsey at e-c-group.com>, voiceops at voiceops.org <voiceops at voiceops.org>
Subject: 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&T mobile, those calls arrive to us with "C"-level attestation, signed with a CenturyLink/Lumen SHAKEN cert.
-- Nathan
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.neth…
July 6, 2022
Identity Header Test Tool
by marylou@backuptelecom.com
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-1111
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:marylou at backuptelecom.com]
> Sent: Tuesday, July 5, 2022 4:27 PM
> To: Nathan Anderson <nathana at fsr.com>
> Cc: 'David Frankel' <dfrankel at zipdx.com>; voiceops at 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-1111
>
> 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-bounces at voiceops.org] On Behalf Of
>> David Frankel
>> Sent: Sunday, July 3, 2022 8:05 AM
>> To: voiceops at 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 at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
July 6, 2022
Identity Header Test Tool
by nathana@fsr.com
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:marylou at backuptelecom.com]
Sent: Tuesday, July 5, 2022 4:27 PM
To: Nathan Anderson <nathana at fsr.com>
Cc: 'David Frankel' <dfrankel at zipdx.com>; voiceops at 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-1111
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-bounces at voiceops.org] On Behalf Of
> David Frankel
> Sent: Sunday, July 3, 2022 8:05 AM
> To: voiceops at 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 at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
July 6, 2022
Identity Header Test Tool
by marylou@backuptelecom.com
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-1111
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-bounces at voiceops.org] On Behalf Of
> David Frankel
> Sent: Sunday, July 3, 2022 8:05 AM
> To: voiceops at 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 at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
July 5, 2022
[EXTERNAL] Identity Header Test Tool
by nathana@fsr.com
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&T mobile, those calls arrive to us with "C"-level attestation, signed with a CenturyLink/Lumen SHAKEN cert.
-- Nathan
July 5, 2022
Identity Header Test Tool
by nathana@fsr.com
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-bounces at voiceops.org] On Behalf Of David Frankel
Sent: Sunday, July 3, 2022 8:05 AM
To: voiceops at 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 at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
July 5, 2022