If you want to keep up to date on this, join the ATIS IP NNI and SIP Forum
mailing lists. You'll see frequent notifications as the policy and protocol
documents get updated.
On Tue, Dec 17, 2019 at 3:49 PM Peter Beckman wrote:
> In my case, we use different termination carriers than our
On Tue, 17 Dec 2019, John Levine wrote:
In article you write:
Sure, but have you ever tried to contact a carrier for which you do not
have a business relationship and get them to do something, and you are
smaller and less consequential than they are?
We can block Hooli, but now OUR
"The ALG fixed everything!" -- said nobody, ever.
But ALGs are increasingly meddling in TCP streams too. Some of them even
do insidious fingerprinting to where switching ports won't throw them.
For those pathological cases, TLS is the only solution.
On Tue, Dec 17, 2019 at 06:34:43PM -0500,
On 12/17/19 6:24 PM, Alex Balashov wrote:
There are many other reasons why SIP messages are getting bigger and
bigger, of which STIR/SHAKEN is not the first, second or fifth: other
standards, WebRTC interop, more/wideband codecs in SDP bodies,
SRTP(-SDES/DTLS), support for other features and
On Tue, Dec 17, 2019 at 03:38:39PM -0500, Dovid Bender wrote:
> The bigger issue you are going to have is the larger packets. So many
> devices out there can't seem to fragment packets correctly.
There are many other reasons why SIP messages are getting bigger and
bigger, of which STIR/SHAKEN is
In article you write:
> Sure, but have you ever tried to contact a carrier for which you do not
> have a business relationship and get them to do something, and you are
> smaller and less consequential than they are?
>
> We can block Hooli, but now OUR customers are livid, and Hooli doesn't
>
On Tue, 17 Dec 2019, Paul Timmins wrote:
I see it as stopping fraud the same way SPF and DKIM stopped spam.
Yes! Agreed. It makes legit traffic easier to identify, but does nothing
to stop spam.
On 12/17/19 3:38 PM, Dovid Bender wrote:
Mike beat me to it. It's going to stop fraud. The
On Tue, 17 Dec 2019, Dovid Bender wrote:
Mike beat me to it. It's going to stop fraud. The bigger issue you are
going to have is the larger packets. So many devices out there can't seem
to fragment packets correctly.
How is it going to stop fraud?
On Tue, Dec 17, 2019 at 3:28 PM wrote:
On Tue, 17 Dec 2019, m...@astrocompanies.com wrote:
Good question. First, if you're using Hooli, you'll have to migrate to
Pipernet sooner or later. Their middle-out compression provides much better
call quality so it's worth the effort to migrate.
Doh! What's their Weissman score?
But
I knew Gavin Belson was behind this.
—
Sent from mobile, with due apologies for brevity and errors.
> On Dec 17, 2019, at 4:07 PM, Paul Timmins wrote:
>
>
> I see it as stopping fraud the same way SPF and DKIM stopped spam.
>
> On 12/17/19 3:38 PM, Dovid Bender wrote:
>> Mike beat me to it.
I see it as stopping fraud the same way SPF and DKIM stopped spam.
On 12/17/19 3:38 PM, Dovid Bender wrote:
Mike beat me to it. It's going to stop fraud. The bigger issue you are
going to have is the larger packets. So many devices out there can't
seem to fragment packets correctly.
On Tue,
Mike beat me to it. It's going to stop fraud. The bigger issue you are
going to have is the larger packets. So many devices out there can't seem
to fragment packets correctly.
On Tue, Dec 17, 2019 at 3:28 PM wrote:
> Hi Peter,
>
> Good question. First, if you're using Hooli, you'll have to
Hi Peter,
Good question. First, if you're using Hooli, you'll have to migrate to
Pipernet sooner or later. Their middle-out compression provides much better
call quality so it's worth the effort to migrate.
But to the issue you raised, the purpose of STIR/SHAKEN is not to block
robocalls per
A few months ago I attended an FCC STIR/SHAKEN discussion in Washington DC.
They didn't get deep into the technical details but there were a bunch of
big carrier representatives there.
If you haven't followed STIR/SHAKEN, it's really just an additional SIP
header that contains
yup. I tried it already. It seems there is no solid system for intl.
On Tue, Dec 17, 2019 at 2:35 PM Peter Beckman wrote:
> Nomorobo has an API as a paid service. Still only US-based AFAIK.
>
> On Tue, 17 Dec 2019, Dovid Bender wrote:
>
> > The options that Twillios has is actually not that
Nomorobo has an API as a paid service. Still only US-based AFAIK.
On Tue, 17 Dec 2019, Dovid Bender wrote:
The options that Twillios has is actually not that bad for the US. Our
issue is that we have a large customer presence in Europe and there isn't
really a service that works for us. I wish
The options that Twillios has is actually not that bad for the US. Our
issue is that we have a large customer presence in Europe and there isn't
really a service that works for us. I wish TrueCaller would allow access to
their API.
On Tue, Dec 17, 2019 at 12:56 PM Brandon Svec
wrote:
> I fear
I fear that is an endless game of whack-a-mole now. Neighbor scams that use
the same NPA/NXX as the called number and using legitimate number spoofs (like
IRS, Utility Company, etc.) are really impossible to just outright block.
I have been following and reading some things about this company
18 matches
Mail list logo
