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
- 14 participants
- 10512 messages
STIR/SHAKEN warning!
by marylou@backuptelecom.com
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-1111
On 2023-07-06 03:07 PM, Markus via VoiceOps wrote:
> 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 (via
>>> SIP) who are calling to the US and who would like to signal their
>>> European A-number to the called party?
>>>
>>> If I try to register here -
>>> https://authenticatereg.iconectiv.com/register - "Country: United
>>> States" is hard-coded.
>>>
>>> Is there a way for Euro TSPs to get STIR/SHAKEN without creating a US
>>> entity/company just for this purpose?
>>
>> I'm pretty sure it's the job of whoever is providing gateway services
>> into the USA to sign the call, and that anyone in the STIR/SHAKEN
>> system in the US has some sort of regulatory nexus here where they
>> could be held legally responsible. It's all about finding a throat to
>> choke if there's misconduct.
>
> I asked iconectiv that question and now I have clarity:
>
> Me:
> "I have some fundamental questions about STIR/SHAKEN: 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? -> Do we need to get a STIR/SHAKEN
> certificate? [...]"
>
> iconectiv:
> "The revised SPC token Access Policy requires providers seeking to
> register with the STI-Policy Administrator (STI-PA) to:
> 1) Have a current form 499A on file with the FCC;
> 2) Have been assigned an Operating Company Number (OCN); [...]
>
> Me:
> "Since registering as 499A and getting an own OCN is only possible for
> US companies, I figure getting a STIR/SHAKEN certificate through you
> is currently not possible for non-US companies. Is that correct?"
>
> iconectiv:
> "That is correct."
>
> The confusion also came from the fact that many non-US companies that
> registered in the Robocall Mitigation Database -
> https://fccprod.servicenowservices.com/rmd?id=rmd_listings - chose
> "Complete STIR/SHAKEN implementation" or "Partial STIR/SHAKEN
> implementation", which, unless they also have a US subsidiary, seems
> to be a lie. Probably they chose something that looked cool in the
> dropdown box, or were too lazy to develop a Robocall Mitigation Plan
> (this is what you gotta upload as DOCUMENT if you choose "No
> STIR/SHAKEN implementation". I also noticed some non-US companies just
> uploaded some random document to the database, like a high school
> report or just some random letters or words... so much about the
> quality of that database.
>
> Good luck
> Markus
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
July 12, 2023
STIR/SHAKEN warning!
by dfrankel@zipdx.com
Nathan,
Regarding TFN's as caller-ID: This became quite popular more than a mere few
years ago. Many customer support operations (banks, brokerages, airlines,
insurance companies, credit card companies) place outbound calls using their
toll-free customer support number as caller-ID. In our RRAPTOR robocall
surveillance platform, we have captured many, many thousands of calls with a
TFN as the calling number. And the majority of those calls are signed, with
varying levels of attestation. Most enterprise calls these days that I'm
familiar with are initiated over SIP trunks (not PRI or analog trunks or
POTS lines) and include the calling (FROM) number in the SIP INVITE.
Regarding signatures on calls TO TFNs: This also definitely happens. Our
SHAKEN identity test tool (at
https://portal.legalcallsonly.org/Info/Identity) lets users call any of
several test numbers, including some TFNs. We see signatures on many calls
to those test TFNs. (We don't save data for calls that do NOT have
signatures, so I can't tell you the fraction.) I do know that there are some
toll-free providers that ALWAYS (or usually) have TDM in the call path.
Since IDENTITY headers don't travel over TDM, those calls will not have
signatures at the terminating end.
David
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Nathan Anderson
via VoiceOps
Sent: Friday, July 7, 2023 3:55 PM
To: Voice Ops <voiceops at voiceops.org>
Subject: Re: [VoiceOps] STIR/SHAKEN warning!
Thanks; I had no idea this was a thing.
-- Nathan
From: Paul Timmins [mailto:paul at 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.
We have it set up on customers who want to source from their TFNs, I haven't
seen many carriers actually look it up, but it does exist.
On Jul 7, 2023, at 5:34 PM, Nathan Anderson via VoiceOps
<voiceops at voiceops.org <mailto:voiceops at voiceops.org> > wrote:
I suspect things might be different now (& I just haven't kept up), but
although it is clearly *possible* to transmit a TFN as the calling number /
CID, I seem to remember that even just a mere few years ago, it was HIGHLY
discouraged, and if you ever were to receive a call bearing a TFN as its
CID, it had a very high likelihood of being fraudulent or spam. This was of
course back when the vast, vast majority of TFNs were essentially
implemented as a call forward or alias to a number that hung off of a local
exchange. So of course outbound calls that many? most? companies with TFNs
would make would typically be sourced from their local exchange number(s)
and not from the TFN(s) (unless maybe a given company had a PRI and their
provider allowed them to source calls from their TFN?). Thus the
expectation for a long time (as I understood it) was that TFNs were truly
inbound-only and should be treated as such.
Loosely tangentially related, as a purely anecdotal report, 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-bounces at voiceops.org>
mailto:voiceops-bounces at voiceops.org] On Behalf Of David Frankel via
VoiceOps
Sent: Friday, July 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 to use" the calling number.
The signer can "know" that in any of a variety of ways. For toll-free
numbers, the most sophisticated and secure is probably via Delegate
Certificates. SOMOS, the North American Toll-Free Number Administrator, has
commented about this in a current FCC proceeding:
<https://www.fcc.gov/ecfs/document/10605623514445/1>
https://www.fcc.gov/ecfs/document/10605623514445/1
As the signer, there are other ways you could determine that the caller is
authorized to use the number. For example, you could solicit some
documentation from them (like an invoice from their RespOrg and/or service
provider) and you could call the number and verify that your caller answers.
The regulations (today) do not specify exactly how you "know" so you (as the
signer) need to act in the spirit of the rules.
This problem is not unique to toll-free numbers. I might have a geographic
number that I obtain from provider A (and that's how I get inbound calls to
the number), but I make outbound calls from that number via providers B and
C for redundancy and cost reasons.
Bear in mind that providers can set their own rules for what calls they will
accept and what attestations they will assign, and those rules can be more
restrictive than what might be dictated by regulation. For example, a
provider might say "I will only assign A-level attestation to calls that use
calling numbers assigned by me." That's their prerogative. In fact, a
provider might say: "I will only accept calls that use calling numbers
assigned by me. Those calls will get A-level attestation. I will reject all
other calls." There are no rules (to my knowledge) that prohibit providers
from setting these kinds of rules.
From: VoiceOps < <mailto:voiceops-bounces at voiceops.org>
voiceops-bounces at voiceops.org> On Behalf Of Ivan Kovacevic via VoiceOps
Sent: Friday, July 7, 2023 7:27 AM
To: Voice Ops < <mailto:voiceops at voiceops.org> voiceops at voiceops.org>
Subject: Re: [VoiceOps] STIR/SHAKEN warning!
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 to receive inbound calls via the
same TFN)... RespOrgs is not necessarily a carrier - who and how checks that
RespOrg has the authority in case of delegated attestation. I may be
overcomplicating it in my mind.. but it doesn't feel like the regulation
maps 1-to-1 over to TFNs... Just wondering what everyone's experience is.
Thanks,
Ivan
_______________________________________________
VoiceOps mailing list
<mailto:VoiceOps at voiceops.org> VoiceOps at voiceops.org
<https://puck.nether.net/mailman/listinfo/voiceops>
https://puck.nether.net/mailman/listinfo/voiceops
July 7, 2023
STIR/SHAKEN warning!
by nathana@fsr.com
Thanks; I had no idea this was a thing.
-- Nathan
From: Paul Timmins [mailto:paul at 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. We
have it set up on customers who want to source from their TFNs, I haven't seen
many carriers actually look it up, but it does exist.
On Jul 7, 2023, at 5:34 PM, Nathan Anderson via VoiceOps <voiceops at voiceops.org
> wrote:
I suspect things might be different now (& I just haven't kept up), but
although it is clearly *possible* to transmit a TFN as the calling number /
CID, I seem to remember that even just a mere few years ago, it was HIGHLY
discouraged, and if you ever were to receive a call bearing a TFN as its CID,
it had a very high likelihood of being fraudulent or spam. This was of course
back when the vast, vast majority of TFNs were essentially implemented as a
call forward or alias to a number that hung off of a local exchange. So of
course outbound calls that many? most? companies with TFNs would make would
typically be sourced from their local exchange number(s) and not from the TFN
(s) (unless maybe a given company had a PRI and their provider allowed them to
source calls from their TFN?). Thus the expectation for a long time (as I
understood it) was that TFNs were truly inbound-only and should be treated as
such.
Loosely tangentially related, as a purely anecdotal report, 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-bounces at voiceops.org] On Behalf Of David
Frankel via VoiceOps
Sent: Friday, July 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 to use??? the calling number.
The signer can ???know??? that in any of a variety of ways. For toll-free numbers,
the most sophisticated and secure is probably via Delegate Certificates. SOMOS,
the North American Toll-Free Number Administrator, has commented about this in
a current FCC proceeding: https://www.fcc.gov/ecfs/document/10605623514445/1
As the signer, there are other ways you could determine that the caller is
authorized to use the number. For example, you could solicit some documentation
from them (like an invoice from their RespOrg and/or service provider) and you
could call the number and verify that your caller answers. The regulations
(today) do not specify exactly how you ???know??? so you (as the signer) need to
act in the spirit of the rules.
This problem is not unique to toll-free numbers. I might have a geographic
number that I obtain from provider A (and that???s how I get inbound calls to the
number), but I make outbound calls from that number via providers B and C for
redundancy and cost reasons.
Bear in mind that providers can set their own rules for what calls they will
accept and what attestations they will assign, and those rules can be more
restrictive than what might be dictated by regulation. For example, a provider
might say ???I will only assign A-level attestation to calls that use calling
numbers assigned by me.??? That???s their prerogative. In fact, a provider might
say: ???I will only accept calls that use calling numbers assigned by me. Those
calls will get A-level attestation. I will reject all other calls.??? There are
no rules (to my knowledge) that prohibit providers from setting these kinds of
rules.
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Ivan Kovacevic via
VoiceOps
Sent: Friday, July 7, 2023 7:27 AM
To: Voice Ops <voiceops at voiceops.org>
Subject: Re: [VoiceOps] STIR/SHAKEN warning!
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 to receive inbound calls via the
same TFN)... RespOrgs is not necessarily a carrier - who and how checks that
RespOrg has the authority in case of delegated attestation. I may be
overcomplicating it in my mind.. but it doesn't feel like the regulation maps
1-to-1 over to TFNs... Just wondering what everyone's experience is.
Thanks,
Ivan
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
July 7, 2023
STIR/SHAKEN warning!
by paul@timmins.net
Always worth pointing out that in March 2020, Somos rolled out TFNIdentity. We have it set up on customers who want to source from their TFNs, I haven't seen many carriers actually look it up, but it does exist.
> On Jul 7, 2023, at 5:34 PM, Nathan Anderson via VoiceOps <voiceops at voiceops.org> wrote:
>
> I suspect things might be different now (& I just haven't kept up), but although it is clearly *possible* to transmit a TFN as the calling number / CID, I seem to remember that even just a mere few years ago, it was HIGHLY discouraged, and if you ever were to receive a call bearing a TFN as its CID, it had a very high likelihood of being fraudulent or spam. This was of course back when the vast, vast majority of TFNs were essentially implemented as a call forward or alias to a number that hung off of a local exchange. So of course outbound calls that many? most? companies with TFNs would make would typically be sourced from their local exchange number(s) and not from the TFN(s) (unless maybe a given company had a PRI and their provider allowed them to source calls from their TFN?). Thus the expectation for a long time (as I understood it) was that TFNs were truly inbound-only and should be treated as such.
>
> Loosely tangentially related, as a purely anecdotal report, 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-bounces at voiceops.org] On Behalf Of David Frankel via VoiceOps
> Sent: Friday, July 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 to use? the calling number.
>
> The signer can ?know? that in any of a variety of ways. For toll-free numbers, the most sophisticated and secure is probably via Delegate Certificates. SOMOS, the North American Toll-Free Number Administrator, has commented about this in a current FCC proceeding: https://www.fcc.gov/ecfs/document/10605623514445/1
>
> As the signer, there are other ways you could determine that the caller is authorized to use the number. For example, you could solicit some documentation from them (like an invoice from their RespOrg and/or service provider) and you could call the number and verify that your caller answers. The regulations (today) do not specify exactly how you ?know? so you (as the signer) need to act in the spirit of the rules.
>
> This problem is not unique to toll-free numbers. I might have a geographic number that I obtain from provider A (and that?s how I get inbound calls to the number), but I make outbound calls from that number via providers B and C for redundancy and cost reasons.
>
> Bear in mind that providers can set their own rules for what calls they will accept and what attestations they will assign, and those rules can be more restrictive than what might be dictated by regulation. For example, a provider might say ?I will only assign A-level attestation to calls that use calling numbers assigned by me.? That?s their prerogative. In fact, a provider might say: ?I will only accept calls that use calling numbers assigned by me. Those calls will get A-level attestation. I will reject all other calls.? There are no rules (to my knowledge) that prohibit providers from setting these kinds of rules.
>
> From: VoiceOps <voiceops-bounces at voiceops.org <mailto:voiceops-bounces at voiceops.org>> On Behalf Of Ivan Kovacevic via VoiceOps
> Sent: Friday, July 7, 2023 7:27 AM
> To: Voice Ops <voiceops at voiceops.org <mailto:voiceops at voiceops.org>>
> Subject: Re: [VoiceOps] STIR/SHAKEN warning!
>
> 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 to receive inbound calls via the same TFN)... RespOrgs is not necessarily a carrier - who and how checks that RespOrg has the authority in case of delegated attestation. I may be overcomplicating it in my mind.. but it doesn't feel like the regulation maps 1-to-1 over to TFNs... Just wondering what everyone's experience is.
>
> Thanks,
>
> Ivan
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops
July 7, 2023
STIR/SHAKEN warning!
by nathana@fsr.com
I suspect things might be different now (& I just haven't kept up), but
although it is clearly *possible* to transmit a TFN as the calling number /
CID, I seem to remember that even just a mere few years ago, it was HIGHLY
discouraged, and if you ever were to receive a call bearing a TFN as its CID,
it had a very high likelihood of being fraudulent or spam. This was of course
back when the vast, vast majority of TFNs were essentially implemented as a
call forward or alias to a number that hung off of a local exchange. So of
course outbound calls that many? most? companies with TFNs would make would
typically be sourced from their local exchange number(s) and not from the TFN
(s) (unless maybe a given company had a PRI and their provider allowed them to
source calls from their TFN?).
Loosely tangentially related, as a purely anecdotal report, 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 and
for actual traffic.
-- Nathan
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of David
Frankel via VoiceOps
Sent: Friday, July 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 to use??? the calling number.
The signer can ???know??? that in any of a variety of ways. For toll-free numbers,
the most sophisticated and secure is probably via Delegate Certificates. SOMOS,
the North American Toll-Free Number Administrator, has commented about this in
a current FCC proceeding: https://www.fcc.gov/ecfs/document/10605623514445/1
As the signer, there are other ways you could determine that the caller is
authorized to use the number. For example, you could solicit some documentation
from them (like an invoice from their RespOrg and/or service provider) and you
could call the number and verify that your caller answers. The regulations
(today) do not specify exactly how you ???know??? so you (as the signer) need to
act in the spirit of the rules.
This problem is not unique to toll-free numbers. I might have a geographic
number that I obtain from provider A (and that???s how I get inbound calls to the
number), but I make outbound calls from that number via providers B and C for
redundancy and cost reasons.
Bear in mind that providers can set their own rules for what calls they will
accept and what attestations they will assign, and those rules can be more
restrictive than what might be dictated by regulation. For example, a provider
might say ???I will only assign A-level attestation to calls that use calling
numbers assigned by me.??? That???s their prerogative. In fact, a provider might
say: ???I will only accept calls that use calling numbers assigned by me. Those
calls will get A-level attestation. I will reject all other calls.??? There are
no rules (to my knowledge) that prohibit providers from setting these kinds of
rules.
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Ivan Kovacevic via
VoiceOps
Sent: Friday, July 7, 2023 7:27 AM
To: Voice Ops <voiceops at voiceops.org>
Subject: Re: [VoiceOps] STIR/SHAKEN warning!
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 to receive inbound calls via the
same TFN)... RespOrgs is not necessarily a carrier - who and how checks that
RespOrg has the authority in case of delegated attestation. I may be
overcomplicating it in my mind.. but it doesn't feel like the regulation maps
1-to-1 over to TFNs... Just wondering what everyone's experience is.
Thanks,
Ivan
July 7, 2023
STIR/SHAKEN warning!
by dfrankel@zipdx.com
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 sophisticated and secure is probably via Delegate Certificates. SOMOS, the North American Toll-Free Number Administrator, has commented about this in a current FCC proceeding: https://www.fcc.gov/ecfs/document/10605623514445/1
As the signer, there are other ways you could determine that the caller is authorized to use the number. For example, you could solicit some documentation from them (like an invoice from their RespOrg and/or service provider) and you could call the number and verify that your caller answers. The regulations (today) do not specify exactly how you ?know? so you (as the signer) need to act in the spirit of the rules.
This problem is not unique to toll-free numbers. I might have a geographic number that I obtain from provider A (and that?s how I get inbound calls to the number), but I make outbound calls from that number via providers B and C for redundancy and cost reasons.
Bear in mind that providers can set their own rules for what calls they will accept and what attestations they will assign, and those rules can be more restrictive than what might be dictated by regulation. For example, a provider might say ?I will only assign A-level attestation to calls that use calling numbers assigned by me.? That?s their prerogative. In fact, a provider might say: ?I will only accept calls that use calling numbers assigned by me. Those calls will get A-level attestation. I will reject all other calls.? There are no rules (to my knowledge) that prohibit providers from setting these kinds of rules.
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Ivan Kovacevic via VoiceOps
Sent: Friday, July 7, 2023 7:27 AM
To: Voice Ops <voiceops at voiceops.org>
Subject: Re: [VoiceOps] STIR/SHAKEN warning!
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 to receive inbound calls via the same TFN)... RespOrgs is not necessarily a carrier - who and how checks that RespOrg has the authority in case of delegated attestation. I may be overcomplicating it in my mind.. but it doesn't feel like the regulation maps 1-to-1 over to TFNs... Just wondering what everyone's experience is.
Thanks,
Ivan
July 7, 2023
STIR/SHAKEN warning!
by ivan.kovacevic@startelecom.ca
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 to receive inbound calls via
the same TFN)... RespOrgs is not necessarily a carrier - who and how checks
that RespOrg has the authority in case of delegated attestation. I may be
overcomplicating it in my mind.. but it doesn't feel like the regulation
maps 1-to-1 over to TFNs... Just wondering what everyone's experience is.
Thanks,
Ivan
On Thu, Jul 6, 2023 at 7:26?PM David Frankel via VoiceOps <
voiceops at voiceops.org> wrote:
> 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 to get a 499A Filer
> ID than it is an OCN.
>
> The good news is that in their Sixth Report and Order
> (https://docs.fcc.gov/public/attachments/FCC-23-18A1.pdf) the FCC wrote,
> at
> paragraph 48:
>
> "Finally, we require filers to submit their OCN if they have one. An OCN is
> a prerequisite to obtaining an SPC token, and we conclude that filing the
> OCN or indicating that they do not have one will allow us to more easily
> determine whether a provider is meeting its requirement to diligently
> pursue
> obtaining a token in order to authenticate their own calls and provides an
> additional way to determine relationships among providers."
>
> Presumably they will implement this shortly (the Order is pending some
> administrative reviews).
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
--
NOTE: This email message and
any attachments are for the sole use of the
intended recipient(s) and may
contain confidential and/or privileged
information. Any unauthorized review,
use, disclosure or distribution is
prohibited. If you are not the intended recipient,
please contact the
sender by replying to this email, and destroy all copies of
the original
message.
July 7, 2023
STIR/SHAKEN warning!
by dfrankel@zipdx.com
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 to get a 499A Filer
ID than it is an OCN.
The good news is that in their Sixth Report and Order
(https://docs.fcc.gov/public/attachments/FCC-23-18A1.pdf) the FCC wrote, at
paragraph 48:
"Finally, we require filers to submit their OCN if they have one. An OCN is
a prerequisite to obtaining an SPC token, and we conclude that filing the
OCN or indicating that they do not have one will allow us to more easily
determine whether a provider is meeting its requirement to diligently pursue
obtaining a token in order to authenticate their own calls and provides an
additional way to determine relationships among providers."
Presumably they will implement this shortly (the Order is pending some
administrative reviews).
July 6, 2023
STIR/SHAKEN warning!
by dfrankel@zipdx.com
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 entities with 499A filer IDs. For example:
https://apps.fcc.gov/cgb/form499/499detail.cfm?FilerNum=834713
Their address is in Singapore. You'll find that they have a SHAKEN token
(listed by iconectiv as an Authorized Provider).
Also this one in Hong Kong:
https://apps.fcc.gov/cgb/form499/499detail.cfm?FilerNum=834534
And this one in Canada:
https://apps.fcc.gov/cgb/form499/499detail.cfm?FilerNum=832443
Also both listed by iconectiv as Authorized Providers.
iconectiv may ask you for a US address, but they won't send you any mail.
Thus, you can see that foreign providers CAN get SHAKEN tokens. For 499A
filing, you'll probably need a US address for legal service of documents;
there are third party agents you can engage for this. Perhaps that address
is also good for iconectiv. Point is, you can navigate this if you so
choose, and I'm sure you can make it through the NECA process as well to
obtain an OCN. I don't have any reason to believe that the examples given
above were created through some nefarious process.
The best reason I heard (really) for a foreign entity being "unable" to
obtain a SHAKEN token: "We didn't attempt to get one."
That said, there are also plenty of specious Robocall Mitigation Database
filings, including false certification as to S/S implementation, and garbage
filed as a Robocall Mitigation Plan. Those providers are presumably on thin
ice, as the FCC has recently revised their own rules to make it easier for
them to delist such filings from the RMD.
July 6, 2023
STIR/SHAKEN warning!
by nathana@fsr.com
Good catch. I just casually scrolled through the list of companies in the Robocall Mitigation Database & stumbled across a Panamanian company and an Australian company that both claim to have "complete" STIR/SHAKEN implementations. Yet I can confirm that neither company shows up either in the 499 Filer ID database, nor in iconectiv's list of Service Provider accounts that they have authorized to have access to the STI-PA and to generate SP tokens. The FCC FRNs for both companies were also generated fairly recently.
I wonder if these foreign companies got concerned about making sure that international calls originating from their networks were getting signed with a high attestation on ingress into the U.S., arranged for this to be the case with whomever they are interconnecting with over on our shores, thought that they had to be listed in the RMD for some reason (do they? Are int'l telecoms required to be in the RMD and file an actual mitigation plan if they want to originate calls to the U.S.?), also assumed/misunderstood that having another party sign & attest their calls for them is enough to claim a "complete" implementation, and so that's why they filed the way they did. (Trying to be generous / assume the best here.)
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.
-- Nathan
-----Original Message-----
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Markus via VoiceOps
Sent: Thursday, July 6, 2023 1:07 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] STIR/SHAKEN warning!
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 (via SIP) who are calling to the US and who would like to signal their European A-number to the called party?
>>
>> If I try to register here - https://authenticatereg.iconectiv.com/register - "Country: United States" is hard-coded.
>>
>> Is there a way for Euro TSPs to get STIR/SHAKEN without creating a US entity/company just for this purpose?
>
> I'm pretty sure it's the job of whoever is providing gateway services into the USA to sign the call, and that anyone in the STIR/SHAKEN system in the US has some sort of regulatory nexus here where they could be held legally responsible. It's all about finding a throat to choke if there's misconduct.
I asked iconectiv that question and now I have clarity:
Me:
"I have some fundamental questions about STIR/SHAKEN: 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? -> Do we need to get a STIR/SHAKEN
certificate? [...]"
iconectiv:
"The revised SPC token Access Policy requires providers seeking to
register with the STI-Policy Administrator (STI-PA) to:
1) Have a current form 499A on file with the FCC;
2) Have been assigned an Operating Company Number (OCN); [...]
Me:
"Since registering as 499A and getting an own OCN is only possible for
US companies, I figure getting a STIR/SHAKEN certificate through you is
currently not possible for non-US companies. Is that correct?"
iconectiv:
"That is correct."
The confusion also came from the fact that many non-US companies that
registered in the Robocall Mitigation Database -
https://fccprod.servicenowservices.com/rmd?id=rmd_listings - chose
"Complete STIR/SHAKEN implementation" or "Partial STIR/SHAKEN
implementation", which, unless they also have a US subsidiary, seems to
be a lie. Probably they chose something that looked cool in the dropdown
box, or were too lazy to develop a Robocall Mitigation Plan (this is
what you gotta upload as DOCUMENT if you choose "No STIR/SHAKEN
implementation". I also noticed some non-US companies just uploaded some
random document to the database, like a high school report or just some
random letters or words... so much about the quality of that database.
Good luck
Markus
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
July 6, 2023