I wouldn't say it's all that easy because you have to be certified as a
CLEC, Interconnected VOIP, or Wireless provider in order to get access
to numbering resources. A lot of people missed that part in the
guidelines because it was not worded clearly and they didn't know that
you can't get NXX
On Tue, Dec 31, 2019 at 8:54 AM Mark Lindsey wrote:
>
> My presentation focused Bad Actors who don't register with anybody. But
> after my presentation, Jon Peterson (who wrote much of the SHAKEN RFCs)
> added another security gap in the American implementation: anybody can get
> an OCN and CLLI
> The idea of "authenticating the incoming calls" only applies if you're
really going to block incoming calls.
Sort of. Even if the goal is to update the CLID (e.g. Spam likely) one
needs to authenticate it. That is, to do the verify the Identity.
> anybody can get an OCN and CLLI code
Agreed.
Yes, I did conflate Goldfield Telecom with Goldfield Telephone in the original
post.
Sorry.
The site with the busted SSL also seems to have been hijacked. The first
several times I tried getting to it, it redirected me to a bunch of BS.
I did find this site: http://www.goldfieldaccess-ia.co
In article <1464181553.3249.1577818986090.JavaMail.mhammett@ThunderFuck> you
write:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>The entity I'm calling is based out of Goldfield, so in this particular case,
>it isn't malicious. I'm not going to deny
>that there could be other malicious uses of that exchange.
A
Could it have something to do with the FCC sounding the death knell for
access stimulation? "their end user relationships with high volume calling
providers were terminated"
https://prodnet.www.neca.org/publicationsdocs/wwpdf/fcc1994.pdf
from: NECA Washington Watch
reply-to: washingtonwa...@neca
The entity I'm calling is based out of Goldfield, so in this particular case,
it isn't malicious. I'm not going to deny that there could be other malicious
uses of that exchange.
-
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http:/
On 12/31/19 09:16, Mike Hammett wrote:
Is anyone else seeing odd routing when calling Goldfield Telecom in
Iowa? Yes, I'm almost positive no one here has had that need.
Today when I call from Sprint, I get a guy that just keeps saying, "Hello".
When I call with T-Mobile, I get through to the
Is anyone else seeing odd routing when calling Goldfield Telecom in Iowa? Yes,
I'm almost positive no one here has had that need.
Today when I call from Sprint, I get a guy that just keeps saying, "Hello".
When I call with T-Mobile, I get through to the desired conference brdige.
When
> On Dec 31, 2019, at 11:06 AM, Pete Eisengrein wrote:
>
> Thoughts on implementation/technologies? Where in the network would you do
> your assertion (softswitch, SBC, other?),
Many of the implementations allow SHAKEN over SIP, using a 302 to add the
Identity header. This is much more conven
> The solution, of course, is to use SIP over TCP.
Agreed, but that too has implications. Maybe your carriers support TCP,
maybe they don't. Also, the memory footprint on gear just got bigger to
manage the TCP overhead. We've also seen odd incidents around TCP (not
releasing sessions and exhausti
11 matches
Mail list logo
