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
September 2020
- 33 participants
- 86 messages
Question about SS7 routing
by marylou@backuptelecom.com
I'll try to make this as short and sweet as possible even though it's
pretty complicated. Point Codes are the 10 digit addresses for a
particular switch and LRNs are the 10 digit addresses for a particular
connection point that switch is associated with. In the PSTN world, all
connections are dedicated and implemented by LATA / Tandem area for
Local / IntraLATA traffic. When you get your first NPA-NXX for a LATA /
tandem area, you enter it in the LERG (National Routing Database) and
populate the tandems (Local, IntraLATA and FGD) that you are connecting
to. Then you assign a 10 digit phone number from your NXX block to be
your LRN. You add that to both the LERG and NPAC (National Porting
Database).
Once you've published all your switch information in the LERG and NPAC,
then you establish your ISUP trunks with each ILEC you're
interconnecting with. You can set up additional trunks with other
carriers if you want a cheaper option for routing traffic, but the
minimum required is the ILEC. Each carrier's switch will have a distinct
point code associated with it so you'll order ISUP trunks to each switch
(point code route) you need to be connected to. You'll also associate
the distinct LRN for that LATA / carrier tandem area with that trunk
group. Usually there's multiple trunk groups per LATA / tandem area so
you'll program your routing tables with the NPA-NXXs each trunk group
serves. That way when a customer originates a call, your switch can do
the LNP dip to find the LRN and send it over the route that the NPA-NXX
of the LRN is associated with. Routing tables can get complicated
depending on how many carriers you're connected to. Companies that
operate in more than one ILEC area or LATA usually purchase Least Cost
Routing software so they can send their originating traffic out over the
cheapest route.
IXC traffic is routed a little differently because it is routed by CIC
(4 digit code that identifies the IXC) rather than by NPA-NXX. They
connect to all the ILEC carriers just like the CLECs do, but they
populate their routing information in the SMS database instead of the
NPAC database. Once the call is dipped, the traffic is delivered in
pretty much the same way.....by dedicated trunk group / tandem area.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-09-02 04:46 PM, Ross Tajvar wrote:
> Hi all,
>
> I'm trying to understand how routing works in SS7-land. I am familiar
> with portability, and I know (at least in the US) the first step in
> routing a call is doing an LNP dip to get the LRN.
>
> However, it looks like addresses in MTP3 are "point codes" (PCs) which
> are assigned to switches. Calls are set up with ISDN-UP, which is
> transported via MTP3. So in order for a call to be set up, the
> destination switch's PC must be known. How is the destination PC
> determined from the destination LRN?
>
> Thanks,
> Ross
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Sept. 3, 2020
Mobile HD Voice interop status?
by hartnett.tom@gmail.com
Does anyone have any updates or experiences in bridging AT&T or VZW HD
Voice calls over to any non-mobile (VoIP) service and keeping the call
wideband? It's discussed from time-to-time (with no real success reported)
but it's been a while.
Sept. 3, 2020
Question about SS7 routing
by ptimmins@clearrate.com
1. You route it to the one that's least expensive, or provides the highest quality, or whatever your target market is. This part's really up to you and it's part of the differentiator of your product.
2. Apply for the blocks with NANPA/National Pooling after getting all the right licensure, interconnection agreements with whoever the local tandems are run by, then make a relationship with an AOCN (NANPA runs one) that can input your blocks into the LERG.
3. Reach out to your local tandem operators before doing this to work out the finer details of routing inbound calls. There are usually the local ILEC, but there are alternative tandem providers such as Inteliquent.
4. Realize that regardless, you may have to connect with many tandems, and several local phone companies to get proper inbound coverage for your numbers. Connecting in the Chicago LATA, this can be something like a minimum of 10-11 T1s to various tandems and trunk groups, in the Upper Penninsula of Michigan this could be two T1s to Marquette, MI, one for local/intralata calling, one for interlata calls.
-Paul
________________________________
From: Ross Tajvar <ross at tajvar.io>
Sent: Wednesday, September 2, 2020 6:10 PM
To: Paul Timmins
Cc: VoiceOps
Subject: Re: [VoiceOps] Question about SS7 routing
I see, that makes sense. So then I have two follow-up questions:
1. If you are connected to multiple carriers, e.g. multiple long distance carriers, how do you populate your routing table? (Obviously "it depends" but I'd be interested to hear an example.)
2. If you are setting up equipment for the first time, with a new number block, how do you make sure other people include you/your block in their routing tables?
On Wed, Sep 2, 2020 at 5:56 PM Paul Timmins <ptimmins at clearrate.com<mailto:ptimmins at clearrate.com>> wrote:
You only send calls to point codes you're connected to with ISUP trunks (what is a control network without bearer channels?), so you don't really do it that way. You would look at your usual LCR/routing table, and the adjacent switch you want to pass it to, be it a local end office, feature group D regional ILEC tandem, or long distance carrier wholesale circuit, and you would send it to the point code of the switch you're connected to that is the appropriate next hop for the call.
________________________________
From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> on behalf of Ross Tajvar <ross at tajvar.io<mailto:ross at tajvar.io>>
Sent: Wednesday, September 2, 2020 5:46 PM
To: VoiceOps
Subject: [VoiceOps] Question about SS7 routing
Hi all,
I'm trying to understand how routing works in SS7-land. I am familiar with portability, and I know (at least in the US) the first step in routing a call is doing an LNP dip to get the LRN.
However, it looks like addresses in MTP3 are "point codes" (PCs) which are assigned to switches. Calls are set up with ISDN-UP, which is transported via MTP3. So in order for a call to be set up, the destination switch's PC must be known. How is the destination PC determined from the destination LRN?
Thanks,
Ross
Sept. 2, 2020
Question about SS7 routing
by abalashov@evaristesys.com
Your number block homing arrangements should be published in the LERG.
?
Sent from mobile, with due apologies for brevity and errors.
> On Sep 2, 2020, at 6:12 PM, Ross Tajvar <ross at tajvar.io> wrote:
>
> ?
> I see, that makes sense. So then I have two follow-up questions:
> If you are connected to multiple carriers, e.g. multiple long distance carriers, how do you populate your routing table? (Obviously "it depends" but I'd be interested to hear an example.)
> If you are setting up equipment for the first time, with a new number block, how do you make sure other people include you/your block in their routing tables?
>
>> On Wed, Sep 2, 2020 at 5:56 PM Paul Timmins <ptimmins at clearrate.com> wrote:
>> You only send calls to point codes you're connected to with ISUP trunks (what is a control network without bearer channels?), so you don't really do it that way. You would look at your usual LCR/routing table, and the adjacent switch you want to pass it to, be it a local end office, feature group D regional ILEC tandem, or long distance carrier wholesale circuit, and you would send it to the point code of the switch you're connected to that is the appropriate next hop for the call.
>>
>>
>>
>> From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Ross Tajvar <ross at tajvar.io>
>> Sent: Wednesday, September 2, 2020 5:46 PM
>> To: VoiceOps
>> Subject: [VoiceOps] Question about SS7 routing
>>
>> Hi all,
>>
>> I'm trying to understand how routing works in SS7-land. I am familiar with portability, and I know (at least in the US) the first step in routing a call is doing an LNP dip to get the LRN.
>>
>> However, it looks like addresses in MTP3 are "point codes" (PCs) which are assigned to switches. Calls are set up with ISDN-UP, which is transported via MTP3. So in order for a call to be set up, the destination switch's PC must be known. How is the destination PC determined from the destination LRN?
>>
>> Thanks,
>> Ross
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Sept. 2, 2020
Question about SS7 routing
by ross@tajvar.io
I see, that makes sense. So then I have two follow-up questions:
1. If you are connected to multiple carriers, e.g. multiple long
distance carriers, how do you populate your routing table? (Obviously "it
depends" but I'd be interested to hear an example.)
2. If you are setting up equipment for the first time, with a new number
block, how do you make sure other people include you/your block in their
routing tables?
On Wed, Sep 2, 2020 at 5:56 PM Paul Timmins <ptimmins at clearrate.com> wrote:
> You only send calls to point codes you're connected to with ISUP trunks
> (what is a control network without bearer channels?), so you don't really
> do it that way. You would look at your usual LCR/routing table, and the
> adjacent switch you want to pass it to, be it a local end office, feature
> group D regional ILEC tandem, or long distance carrier wholesale circuit,
> and you would send it to the point code of the switch you're connected to
> that is the appropriate next hop for the call.
>
>
> ------------------------------
> *From:* VoiceOps <voiceops-bounces at voiceops.org> on behalf of Ross Tajvar
> <ross at tajvar.io>
> *Sent:* Wednesday, September 2, 2020 5:46 PM
> *To:* VoiceOps
> *Subject:* [VoiceOps] Question about SS7 routing
>
> Hi all,
>
> I'm trying to understand how routing works in SS7-land. I am familiar with
> portability, and I know (at least in the US) the first step in routing a
> call is doing an LNP dip to get the LRN.
>
> However, it looks like addresses in MTP3 are "point codes" (PCs) which are
> assigned to switches. Calls are set up with ISDN-UP, which is transported
> via MTP3. So in order for a call to be set up, the destination switch's PC
> must be known. How is the destination PC determined from the destination
> LRN?
>
> Thanks,
> Ross
>
Sept. 2, 2020
Question about SS7 routing
by ptimmins@clearrate.com
You only send calls to point codes you're connected to with ISUP trunks (what is a control network without bearer channels?), so you don't really do it that way. You would look at your usual LCR/routing table, and the adjacent switch you want to pass it to, be it a local end office, feature group D regional ILEC tandem, or long distance carrier wholesale circuit, and you would send it to the point code of the switch you're connected to that is the appropriate next hop for the call.
________________________________
From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Ross Tajvar <ross at tajvar.io>
Sent: Wednesday, September 2, 2020 5:46 PM
To: VoiceOps
Subject: [VoiceOps] Question about SS7 routing
Hi all,
I'm trying to understand how routing works in SS7-land. I am familiar with portability, and I know (at least in the US) the first step in routing a call is doing an LNP dip to get the LRN.
However, it looks like addresses in MTP3 are "point codes" (PCs) which are assigned to switches. Calls are set up with ISDN-UP, which is transported via MTP3. So in order for a call to be set up, the destination switch's PC must be known. How is the destination PC determined from the destination LRN?
Thanks,
Ross
Sept. 2, 2020
Question about SS7 routing
by ross@tajvar.io
Hi all,
I'm trying to understand how routing works in SS7-land. I am familiar with
portability, and I know (at least in the US) the first step in routing a
call is doing an LNP dip to get the LRN.
However, it looks like addresses in MTP3 are "point codes" (PCs) which are
assigned to switches. Calls are set up with ISDN-UP, which is transported
via MTP3. So in order for a call to be set up, the destination switch's PC
must be known. How is the destination PC determined from the destination
LRN?
Thanks,
Ross
Sept. 2, 2020
Outsourcing STIR/SHAKEN Setup
by dfrigen@wabash.net
So far this trail of emails is correct. All calls have to be traceable back to the origination provider (via PA registered certificates) for legal enforcement purposes. So each SP will need to authenticate (guarantee validity of) their own calls. You just don?t necessarily need access to your own phone numbers if you lease.
I would add that not only will a network likely be blocked for monkey business, it will be prosecuted too. And with the recent passing of the Traced Act and all the hype at the FCC lately they?re likely to impose big penalties on bad-actors.
Dave
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Mark Lindsey
Sent: Wednesday, September 2, 2020 2:01 PM
To: Alex Balashov <abalashov at evaristesys.com>
Cc: VoiceOps <voiceops at voiceops.org>
Subject: Re: [VoiceOps] Outsourcing STIR/SHAKEN Setup
SHAKEN doesn't record the chain (like you'd see with Via headers, for example) of Intermediate Providers who handle the call. There's only one Identity header and it is to be passed unchanged from the origin point to the terminating Voice Service Provider.
When the Identity header with PASSporT arrives at the final Voice Service Provider, that recipient can determine who created the PASSporT and then make judgments. For example, there has been a lot of discussion in FCC filings about "reputation" of service providers. Perhaps you could subscribe to a Reputation database to determine what to do with the calls.
For example, "This call got an A level attestation from XYZTelecom, but XYZTelecom has a 5% score in the reputation database, so I'm going to treat it as if this call is likely a nuisance call."
Mark R Lindsey, SMTS | +1-229-316-0013 | mark at ecg.co <mailto:mark at ecg.co> | <https://ecg.co/lindsey/> https://ecg.co/lindsey/
On Sep 2, 2020, at 2:52 PM, Alex Balashov <abalashov at evaristesys.com <mailto:abalashov at evaristesys.com> > wrote:
Thank you, that?s very clear and sums it all up!
One lingering question: even without providing a fully attestable chain of custody, if the call took a route A -> B -> C, are signatures cumulative such that I could block calls attested by B coming through C? Or am I constrained to blocking a certain level of attestation only through the last/proximate peering hop (C) that directly touches me?
I suppose success is going to come down to the on-the-ground realities, political viability, etc of taking that ?block attested calls from carrier X? step.
?
Sent from mobile, with due apologies for brevity and errors.
On Sep 2, 2020, at 2:47 PM, Paul Timmins <ptimmins at clearrate.com <mailto:ptimmins at clearrate.com> > wrote:
?
The solution is that you sign your calls with your certificate. Carriers aren't doing LNP dips to verify the number is really yours, they're trusting your attestation (A: yes, the caller id is verified, B: it comes from our customer, but not verified, C: "this touched our switches, good luck with it"). If you attest total nonsense as A, or send tons of nonsense in general, people start blocking calls you sign.
It really verifies who is sending the call, and what that company says the call is verified, not a full chain of custody of the number back to the NANPA/PA. Could you attest A a call from "0" or "911", or "999-999-9999"? Yes, you could. It'd work for a while, til someone said "Wow, Alex's SPID is signing tons of bullshit. Let's block attested calls from his SPID"
-Paul
_____
From: VoiceOps <voiceops-bounces at voiceops.org <mailto:voiceops-bounces at voiceops.org> > on behalf of Alex Balashov <abalashov at evaristesys.com <mailto:abalashov at evaristesys.com> >
Sent: Wednesday, September 2, 2020 2:42 PM
To: VoiceOps
Subject: Re: [VoiceOps] Outsourcing STIR/SHAKEN Setup
LCR or no LCR, using a termination vendor that is different to one?s origination vendor for a given CID is more normal than not in VoIP. I would guess it?s the default wholesale use-case. Origination and termination are very different business models with radically different economics.
I?m not clear on what the official STIR/SHAKEN solution to this is. I assume it?s delegated certificates as Jared suggested.
?
Sent from mobile, with due apologies for brevity and errors.
On Sep 2, 2020, at 2:39 PM, Carlos Alvarez <caalvarez at gmail.com <mailto:caalvarez at gmail.com> > wrote:
?
If I understand correctly, no as long as your providers are all supporting this. What I think you mean is that you get origination/DIDs from say Bandwidth, and you use LCR to route calls to whoever is cheapest? There are ways to work with that challenge as long as your carriers are ready to do so.
On Wed, Sep 2, 2020 at 11:28 AM Jared Geiger <jared at compuwizz.net <mailto:jared at compuwizz.net> > wrote:
If we purchase our numbers through wholesalers, would we need delegated certificates if we are sending an outbound call through a vendor that is not the wholesaler we got the number from?
On Wed, Sep 2, 2020 at 7:22 AM Dave Frigen <dfrigen at wabash.net <mailto:dfrigen at wabash.net> > wrote:
There is a STIR-SHAKEN process of registering and testing with the Policy
Administrator (PA) as a certified Service Provider (SP) before you can
purchase SHAKEN token certificates from a Certificate Authority (CA) and
begin to engage in using the technology. This is not a walk in the park.
Transnexus is one of two public CA's in the U.S. today. They are experts on
the subject and can help you through both processes. In order to get the
best call attestation you must prove to the PA and CA that you are a bono
fide service provider and not a bad-acting enterprise on a network that
deserves lesser attestation levels.
One of the registration requirements is a SP 's access to valid national
phone number pools. This has been very confusing for some resale providers
that purchase and use numbers from wholesalers only. If your organization
does not have it's own numbering resources, you can register using your
wholesale provider's numbering pool data. Don't assume you have to register
with the FCC and possess your own pool of numbers to become a registered
SHAKEN SP.
SHAKEN ROBO call mitigation is a new frontier, and obtaining the best
attestation level possible for a SP is essential to the SP and the SHAKEN
ecosystem. Register and test for the best attestation level possible.
Transnexus is a seasoned expert on the subject and a U.S. registered CA with
the PA.
Dave
-----Original Message-----
From: VoiceOps <voiceops-bounces at voiceops.org <mailto:voiceops-bounces at voiceops.org> > On Behalf Of Mary Lou Carey
Sent: Tuesday, September 1, 2020 5:36 PM
To: Dovid Bender <dovid at telecurve.com <mailto:dovid at telecurve.com> >
Cc: Voiceops.org <http://Voiceops.org> <voiceops at voiceops.org <mailto:voiceops at voiceops.org> >
Subject: Re: [VoiceOps] Outsourcing STIR/SHAKEN Setup
I'm a Carrier Consultant who's been helping CLEC, IXC, Paging, Wireless and
VOIP carriers install and maintain their PSTN networks for the the last 20
years. I can help clients get their FCC Certification to become a
STIR/SHAKEN carrier as well as Numbering Resources, NPAC / LSR training, etc
(if you need those pieces). Once my clients get their certification, I refer
them to TransNexus. Jim and his team can help you with the process of
turning your STIR/SHAKEN services up.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-08-31 05:37 AM, Dovid Bender wrote:
> Hi,
>
> Does anyone have a recommendation for a company that get us everything
> needed for STIR/SHAKEN setup? By setup I mean helping us file to get a
> cert etc. From the small research I have done there is a lot of
> fragmented information out there and it would be easier for us to pay
> someone else to do this then invest our own time to take care of this.
>
> TIA.
>
> Regards,
>
> Dovid
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
Mark R Lindsey, SMTS | +1-229-316-0013 | mark at ecg.co <mailto:mark at ecg.co> | <https://ecg.co/lindsey/> https://ecg.co/lindsey/
Sept. 2, 2020
Outsourcing STIR/SHAKEN Setup
by David.Zilk@cdk.com
Replace ?robocalls? with ?spoofed calls? and you would be correct. A service provider can legitimately provide A attestation to calls that turn out to be illegal robocalls, as long as the caller can legitimately use the number they are calling from. At that point the traceback functionality of STIR/SHAKEN can be invoked and trace the call back to the robocaller for prosecution. The service provider would not be on the hook for attesting the illegal calls.
However, if the calling number is spoofed and is not one that the end user can legitimately use, the service provider could have their SHAKEN certificate revoked for attesting that traffic at the A level (presumably after a certain period of warning and if they were not responsive to resolving the situation).
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins
Sent: Wednesday, September 2, 2020 12:12 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] Outsourcing STIR/SHAKEN Setup
Exactly that. The idea is collateral pain for misbehavior. Or attorneys general knocking on doors wondering why they're allowing robocalls through their network. Ideally both.
On 9/2/20 3:06 PM, Alex Balashov wrote:
That?s what I thought, thank you for clarifying. I was just confused because of the language in Paul?s previous explanation?no fault of his.
But in the bottom of the barrel, it will leave some folks with a conundrum about what to do when XYZTelecom sends their good conversational traffic through their peer A, and their crappier traffic through their peer B. But I suppose that is the very dilemma that this technique is meant to force.
?
Sent from mobile, with due apologies for brevity and errors.
On Sep 2, 2020, at 3:01 PM, Mark Lindsey <lindsey at e-c-group.com><mailto:lindsey at e-c-group.com> wrote:
?SHAKEN doesn't record the chain (like you'd see with Via headers, for example) of Intermediate Providers who handle the call. There's only one Identity header and it is to be passed unchanged from the origin point to the terminating Voice Service Provider.
When the Identity header with PASSporT arrives at the final Voice Service Provider, that recipient can determine who created the PASSporT and then make judgments. For example, there has been a lot of discussion in FCC filings about "reputation" of service providers. Perhaps you could subscribe to a Reputation database to determine what to do with the calls.
For example, "This call got an A level attestation from XYZTelecom, but XYZTelecom has a 5% score in the reputation database, so I'm going to treat it as if this call is likely a nuisance call."
Mark R Lindsey, SMTS | +1-229-316-0013 | mark at ecg.co<mailto:mark at ecg.co> | https://ecg.co/lindsey/<https://urldefense.proofpoint.com/v2/url?u=https-3A__ecg.co_lindsey_&d=DwMD…>
On Sep 2, 2020, at 2:52 PM, Alex Balashov <abalashov at evaristesys.com<mailto:abalashov at evaristesys.com>> wrote:
Thank you, that?s very clear and sums it all up!
One lingering question: even without providing a fully attestable chain of custody, if the call took a route A -> B -> C, are signatures cumulative such that I could block calls attested by B coming through C? Or am I constrained to blocking a certain level of attestation only through the last/proximate peering hop (C) that directly touches me?
I suppose success is going to come down to the on-the-ground realities, political viability, etc of taking that ?block attested calls from carrier X? step.
?
Sent from mobile, with due apologies for brevity and errors.
On Sep 2, 2020, at 2:47 PM, Paul Timmins <ptimmins at clearrate.com<mailto:ptimmins at clearrate.com>> wrote:
?
The solution is that you sign your calls with your certificate. Carriers aren't doing LNP dips to verify the number is really yours, they're trusting your attestation (A: yes, the caller id is verified, B: it comes from our customer, but not verified, C: "this touched our switches, good luck with it"). If you attest total nonsense as A, or send tons of nonsense in general, people start blocking calls you sign.
It really verifies who is sending the call, and what that company says the call is verified, not a full chain of custody of the number back to the NANPA/PA. Could you attest A a call from "0" or "911", or "999-999-9999"? Yes, you could. It'd work for a while, til someone said "Wow, Alex's SPID is signing tons of bullshit. Let's block attested calls from his SPID"
-Paul
________________________________
From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> on behalf of Alex Balashov <abalashov at evaristesys.com<mailto:abalashov at evaristesys.com>>
Sent: Wednesday, September 2, 2020 2:42 PM
To: VoiceOps
Subject: Re: [VoiceOps] Outsourcing STIR/SHAKEN Setup
LCR or no LCR, using a termination vendor that is different to one?s origination vendor for a given CID is more normal than not in VoIP. I would guess it?s the default wholesale use-case. Origination and termination are very different business models with radically different economics.
I?m not clear on what the official STIR/SHAKEN solution to this is. I assume it?s delegated certificates as Jared suggested.
?
Sent from mobile, with due apologies for brevity and errors.
On Sep 2, 2020, at 2:39 PM, Carlos Alvarez <caalvarez at gmail.com<mailto:caalvarez at gmail.com>> wrote:
?
If I understand correctly, no as long as your providers are all supporting this. What I think you mean is that you get origination/DIDs from say Bandwidth, and you use LCR to route calls to whoever is cheapest? There are ways to work with that challenge as long as your carriers are ready to do so.
On Wed, Sep 2, 2020 at 11:28 AM Jared Geiger <jared at compuwizz.net<mailto:jared at compuwizz.net>> wrote:
If we purchase our numbers through wholesalers, would we need delegated certificates if we are sending an outbound call through a vendor that is not the wholesaler we got the number from?
On Wed, Sep 2, 2020 at 7:22 AM Dave Frigen <dfrigen at wabash.net<mailto:dfrigen at wabash.net>> wrote:
There is a STIR-SHAKEN process of registering and testing with the Policy
Administrator (PA) as a certified Service Provider (SP) before you can
purchase SHAKEN token certificates from a Certificate Authority (CA) and
begin to engage in using the technology. This is not a walk in the park.
Transnexus is one of two public CA's in the U.S. today. They are experts on
the subject and can help you through both processes. In order to get the
best call attestation you must prove to the PA and CA that you are a bono
fide service provider and not a bad-acting enterprise on a network that
deserves lesser attestation levels.
One of the registration requirements is a SP 's access to valid national
phone number pools. This has been very confusing for some resale providers
that purchase and use numbers from wholesalers only. If your organization
does not have it's own numbering resources, you can register using your
wholesale provider's numbering pool data. Don't assume you have to register
with the FCC and possess your own pool of numbers to become a registered
SHAKEN SP.
SHAKEN ROBO call mitigation is a new frontier, and obtaining the best
attestation level possible for a SP is essential to the SP and the SHAKEN
ecosystem. Register and test for the best attestation level possible.
Transnexus is a seasoned expert on the subject and a U.S. registered CA with
the PA.
Dave
-----Original Message-----
From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> On Behalf Of Mary Lou Carey
Sent: Tuesday, September 1, 2020 5:36 PM
To: Dovid Bender <dovid at telecurve.com<mailto:dovid at telecurve.com>>
Cc: Voiceops.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__Voiceops.org&d=DwMDaQ&c…> <voiceops at voiceops.org<mailto:voiceops at voiceops.org>>
Subject: Re: [VoiceOps] Outsourcing STIR/SHAKEN Setup
I'm a Carrier Consultant who's been helping CLEC, IXC, Paging, Wireless and
VOIP carriers install and maintain their PSTN networks for the the last 20
years. I can help clients get their FCC Certification to become a
STIR/SHAKEN carrier as well as Numbering Resources, NPAC / LSR training, etc
(if you need those pieces). Once my clients get their certification, I refer
them to TransNexus. Jim and his team can help you with the process of
turning your STIR/SHAKEN services up.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2020-08-31 05:37 AM, Dovid Bender wrote:
> Hi,
>
> Does anyone have a recommendation for a company that get us everything
> needed for STIR/SHAKEN setup? By setup I mean helping us file to get a
> cert etc. From the small research I have done there is a lot of
> fragmented information out there and it would be easier for us to pay
> someone else to do this then invest our own time to take care of this.
>
> TIA.
>
> Regards,
>
> Dovid
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
Mark R Lindsey, SMTS | +1-229-316-0013 | mark at ecg.co<mailto:mark at ecg.co> | https://ecg.co/lindsey/<https://urldefense.proofpoint.com/v2/url?u=https-3A__ecg.co_lindsey_&d=DwMD…>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
----------------------------------------------------------------------
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.
Sept. 2, 2020
Outsourcing STIR/SHAKEN Setup
by ptimmins@clearrate.com
Exactly that. The idea is collateral pain for misbehavior. Or attorneys
general knocking on doors wondering why they're allowing robocalls
through their network. Ideally both.
On 9/2/20 3:06 PM, Alex Balashov wrote:
> That?s what I thought, thank you for clarifying. I was just confused
> because of the language in Paul?s previous explanation?no fault of his.
>
> But in the bottom of the barrel, it will leave some folks with a
> conundrum about what to do when XYZTelecom sends their good
> conversational traffic through their peer A, and their crappier
> traffic through their peer B. But I suppose that is the very dilemma
> that this technique is meant to force.
>
> ?
> Sent from mobile, with due apologies for brevity and errors.
>
>> On Sep 2, 2020, at 3:01 PM, Mark Lindsey <lindsey at e-c-group.com> wrote:
>>
>> ?SHAKEN doesn't record the chain (like you'd see with Via headers,
>> for example) of Intermediate Providers who handle the call. There's
>> only one Identity header and it is to be passed unchanged from the
>> origin point to the terminating Voice Service Provider.
>>
>> When the Identity header with PASSporT arrives at the final Voice
>> Service Provider, that recipient can determine who created the
>> PASSporT and then make judgments. For example, there has been a lot
>> of discussion in FCC filings about "reputation" of service providers.
>> Perhaps you could subscribe to a Reputation database to determine
>> what to do with the calls.
>>
>> For example, "This call got an A level attestation from XYZTelecom,
>> but XYZTelecom has a 5% score in the reputation database, so I'm
>> going to treat it as if this call is likely a nuisance call."
>>
>>
>>
>> *Mark R Lindsey, SMTS**| **+1-229-316-0013****|****mark at ecg.co
>> <mailto:mark at ecg.co>**|**https://ecg.co/lindsey/*
>> *
>> *
>>
>>
>>
>>> On Sep 2, 2020, at 2:52 PM, Alex Balashov <abalashov at evaristesys.com
>>> <mailto:abalashov at evaristesys.com>> wrote:
>>>
>>> Thank you, that?s very clear and sums it all up!
>>>
>>> One lingering question: even without providing a fully attestable
>>> chain of custody, if the call took a route A -> B -> C, are
>>> signatures cumulative such that I could block calls attested by B
>>> coming through C? Or am I constrained to blocking a certain level of
>>> attestation only through the last/proximate peering hop (C) that
>>> directly touches me?
>>>
>>> I suppose success is going to come down to the on-the-ground
>>> realities, political viability, etc of taking that ?block attested
>>> calls from carrier X? step.
>>>
>>> ?
>>> Sent from mobile, with due apologies for brevity and errors.
>>>
>>>> On Sep 2, 2020, at 2:47 PM, Paul Timmins <ptimmins at clearrate.com
>>>> <mailto:ptimmins at clearrate.com>> wrote:
>>>>
>>>> ?
>>>>
>>>> The solution is that you sign your calls with your certificate.
>>>> Carriers aren't doing LNP dips to verify the number is really
>>>> yours, they're trusting your attestation (A: yes, the caller id is
>>>> verified, B: it comes from our customer, but not verified, C: "this
>>>> touched our switches, good luck with it"). If you attest total
>>>> nonsense as A, or send tons of nonsense in general, people start
>>>> blocking calls you sign.
>>>>
>>>>
>>>> It really verifies who is sending the call, and what that company
>>>> says the call is verified, not a full chain of custody of the
>>>> number back to the NANPA/PA. Could you attest A a call from "0" or
>>>> "911", or "999-999-9999"? Yes, you could. It'd work for a while,
>>>> til someone said "Wow, Alex's SPID is signing tons of bullshit.
>>>> Let's block attested calls from his SPID"
>>>>
>>>>
>>>> -Paul
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>> *From:* VoiceOps <voiceops-bounces at voiceops.org
>>>> <mailto:voiceops-bounces at voiceops.org>> on behalf of Alex Balashov
>>>> <abalashov at evaristesys.com <mailto:abalashov at evaristesys.com>>
>>>> *Sent:* Wednesday, September 2, 2020 2:42 PM
>>>> *To:* VoiceOps
>>>> *Subject:* Re: [VoiceOps] Outsourcing STIR/SHAKEN Setup
>>>> LCR or no LCR, using a termination vendor that is different to
>>>> one?s origination vendor for a given CID is more normal than not in
>>>> VoIP. I would guess it?s the default wholesale use-case.
>>>> Origination and termination are very different business models with
>>>> radically different economics.
>>>>
>>>> I?m not clear on what the official STIR/SHAKEN solution to this is.
>>>> I assume it?s delegated certificates as Jared suggested.
>>>>
>>>> ?
>>>> Sent from mobile, with due apologies for brevity and errors.
>>>>
>>>>> On Sep 2, 2020, at 2:39 PM, Carlos Alvarez <caalvarez at gmail.com
>>>>> <mailto:caalvarez at gmail.com>> wrote:
>>>>>
>>>>> ?
>>>>> If I understand correctly, no as long as your providers are all
>>>>> supporting this. What I think you mean is that you get
>>>>> origination/DIDs from say Bandwidth, and you use LCR to route
>>>>> calls to whoever is cheapest?? There are ways to work with that
>>>>> challenge as long as your carriers are ready to do so.
>>>>>
>>>>> On Wed, Sep 2, 2020 at 11:28 AM Jared Geiger <jared at compuwizz.net
>>>>> <mailto:jared at compuwizz.net>> wrote:
>>>>>
>>>>> If we purchase our numbers through wholesalers, would we need
>>>>> delegated certificates if we are sending an outbound call
>>>>> through a vendor that is not the wholesaler we got the number
>>>>> from?
>>>>>
>>>>> On Wed, Sep 2, 2020 at 7:22 AM Dave Frigen <dfrigen at wabash.net
>>>>> <mailto:dfrigen at wabash.net>> wrote:
>>>>>
>>>>> There is a STIR-SHAKEN process of registering and testing
>>>>> with the Policy
>>>>> Administrator (PA) as a certified Service Provider (SP)
>>>>> before you can
>>>>> purchase SHAKEN token certificates from a Certificate
>>>>> Authority (CA) and
>>>>> begin to engage in using the technology. This is not a
>>>>> walk in the park.
>>>>> Transnexus is one of two public CA's in the U.S. today.
>>>>> They are experts on
>>>>> the subject and can help you through both processes. In
>>>>> order to get the
>>>>> best call attestation you must prove to the PA and CA that
>>>>> you are a bono
>>>>> fide service provider and not a bad-acting enterprise on a
>>>>> network that
>>>>> deserves lesser attestation levels.
>>>>>
>>>>> One of the registration requirements is a SP 's access to
>>>>> valid national
>>>>> phone number pools. This has been very confusing for some
>>>>> resale providers
>>>>> that purchase and use numbers from wholesalers only. If
>>>>> your organization
>>>>> does not have it's own numbering resources, you can
>>>>> register using your
>>>>> wholesale provider's numbering pool data. Don't assume you
>>>>> have to register
>>>>> with the FCC and possess your own pool of numbers to
>>>>> become a registered
>>>>> SHAKEN SP.
>>>>>
>>>>> SHAKEN ROBO call mitigation is a new frontier, and
>>>>> obtaining the best
>>>>> attestation level possible for a SP is essential to the SP
>>>>> and the SHAKEN
>>>>> ecosystem. Register and test for the best attestation
>>>>> level possible.
>>>>> Transnexus is a seasoned expert on the subject and a U.S.
>>>>> registered CA with
>>>>> the PA.
>>>>>
>>>>> Dave
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: VoiceOps <voiceops-bounces at voiceops.org
>>>>> <mailto:voiceops-bounces at voiceops.org>> On Behalf Of Mary
>>>>> Lou Carey
>>>>> Sent: Tuesday, September 1, 2020 5:36 PM
>>>>> To: Dovid Bender <dovid at telecurve.com
>>>>> <mailto:dovid at telecurve.com>>
>>>>> Cc: Voiceops.org <http://Voiceops.org>
>>>>> <voiceops at voiceops.org <mailto:voiceops at voiceops.org>>
>>>>> Subject: Re: [VoiceOps] Outsourcing STIR/SHAKEN Setup
>>>>>
>>>>> I'm a Carrier Consultant who's been helping CLEC, IXC,
>>>>> Paging, Wireless and
>>>>> VOIP carriers install and maintain their PSTN networks for
>>>>> the the last 20
>>>>> years. I can help clients get their FCC Certification to
>>>>> become a
>>>>> STIR/SHAKEN carrier as well as Numbering Resources, NPAC /
>>>>> LSR training, etc
>>>>> (if you need those pieces). Once my clients get their
>>>>> certification, I refer
>>>>> them to TransNexus. Jim and his team can help you with the
>>>>> process of
>>>>> turning your STIR/SHAKEN services up.
>>>>>
>>>>> MARY LOU CAREY
>>>>> BackUP Telecom Consulting
>>>>> Office: 615-791-9969
>>>>> Cell: 615-796-1111
>>>>>
>>>>> On 2020-08-31 05:37 AM, Dovid Bender wrote:
>>>>> > Hi,
>>>>> >
>>>>> > Does anyone have a recommendation for a company that get
>>>>> us everything
>>>>> > needed for STIR/SHAKEN setup? By setup I mean helping us
>>>>> file to get a
>>>>> > cert etc. From the small research I have done there is a
>>>>> lot of
>>>>> > fragmented information out there and it would be easier
>>>>> for us to pay
>>>>> > someone else to do this then invest our own time to take
>>>>> care of this.
>>>>> >
>>>>> > TIA.
>>>>> >
>>>>> > Regards,
>>>>> >
>>>>> > Dovid
>>>>> > _______________________________________________
>>>>> > VoiceOps mailing list
>>>>> > VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>>>>> > https://puck.nether.net/mailman/listinfo/voiceops
>>>>> _______________________________________________
>>>>> VoiceOps mailing list
>>>>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>>>
>>>>> _______________________________________________
>>>>> VoiceOps mailing list
>>>>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>>>
>>>>> _______________________________________________
>>>>> VoiceOps mailing list
>>>>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>>>
>>>>> _______________________________________________
>>>>> VoiceOps mailing list
>>>>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>> *Mark R Lindsey, SMTS*| +1-229-316-0013|mark at ecg.co
>> <mailto:mark at ecg.co>|*https://ecg.co/lindsey/*
>> *
>> *
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Sept. 2, 2020