On Thu, Apr 05, 2012 at 10:26:11AM -0700, George B. wrote:
> On Thu, Mar 29, 2012 at 4:32 AM, Matt Ryanczak wrote:
>
> > I too had with nesol years ago. It required special phone calls to
> > special people to update. Customer support never knew what was going on
> > regarding or IPvWha
I have to respond with the sentiments of Robert: "large" is a very relative
term. Also, are we talking about origination or termination here? How many
minutes a day of each? What's your ACD? What are your top destinations? If
it's bursty like a call center how many concurrent calls?
You can'
Thank you for the reply.
Yes an aggregator, large deployment.
Initially this is discovery, though price is always important it is most about
understanding operations and implementation at this point.
- Original Message -
From: "Robert E. Seastrom"
To: "Elijah Savage"
Cc: "NANOG list"
That's probably a better idea.
I moved "into" a /24 ip block that was SWIPed to me that they reported was
"dynamic cable/DSL users" (no spam history, mind you). Didn't matter, I
couldn't send e-mail.
When trying to get it delisted I had a TTL on the zone that was
"incompatible" with their standa
"SIP trunking consolidation" is buzzword heavy and context-light.
What problem are you trying to solve and at what scale? Do you have a
requirement to have the provider be a traditional TDM-based
organization or is an aggregator sufficient? How price-sensitive are
you?
At fairly small scale (1
On 05/04/2012 17:48, goe...@anime.net wrote:
> But they will care about a /24.
I'm curious as to why they would want to stop at /24. If you're going to
take the shotgun approach, why not blacklist the entire ASN?
Nick
On Thu, Mar 29, 2012 at 4:32 AM, Matt Ryanczak wrote:
> I too had with nesol years ago. It required special phone calls to
> special people to update. Customer support never knew what was going on
> regarding or IPvWhat?.
>
> I suspect all of the people there that know about these types
>
> On Thu, 5 Apr 2012, Drew Weaver wrote:
>
> Now, if we could only teach Senderbase that if their customers receive
>> 'questionable' smtp traffic from 1 IP address in a /24 it doesn't mean that
>> all IP addresses in that /24 are malicious we'd really be living it up in
>> 2012.
>>
>>
On 5 Apri
This is often the only way to get peoples attention and get action.
Providers dont care about individual /32's and will let them sit around
and spew nigerian scams and pill spams without any consequences.
But they will care about a /24.
-Dan
On Thu, 5 Apr 2012, Drew Weaver wrote:
Now, if
Anyone here that have gone through the process of SIP trunking consolidation
care to comment offline on
Whom do you utilize?
What has been your experience operationally?
What was your experience during transition/implementation?
Thank you ahead of time.
Now, if we could only teach Senderbase that if their customers receive
'questionable' smtp traffic from 1 IP address in a /24 it doesn't mean that all
IP addresses in that /24 are malicious we'd really be living it up in 2012.
-Original Message-
From: Sam Oduor [mailto:sam.od...@gmail.
Some of the IP's I manage got blacklisted and its true they were spamming
and Sorbs had a very valid reason for blacklisting them.
I got this response response from sorbs after resolving the problem
amicably. Sorbs responded well on time.
*Your request appear to have been resolved. If you have an
12 matches
Mail list logo
