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
August 2018
- 23 participants
- 82 messages
ANIs flagged as telemarketer/spammer/scammer
by caalvarez@gmail.com
LOL, well stock aside, I do want to get their customer service call to help
me resolve something. And I met a NASA PHD from the Apollo program at the
genius bar. Granted, he was another customer like me, but still AT the bar.
Their stock also helped by my house, so I'm biased (in at $38, out at $400).
On Fri, Aug 31, 2018 at 1:17 PM Ryan Delgrosso <ryandelgrosso at gmail.com>
wrote:
> I agree with this assessment. Using stock buy-backs to pump your own
> stock price and break 1T is shady, and I've never met an actual genius
> at a genius bar.
>
> Now back to your regularly scheduled thread...
>
>
> On 8/31/2018 11:00 AM, Carlos Alvarez wrote:
> > Oh, this week I needed help with an Apple issue. Their call went
> > straight to VM. Turns out TrueCaller has Apple's main national number
> > marked as scam/spam.
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Aug. 31, 2018
ANIs flagged as telemarketer/spammer/scammer
by ryandelgrosso@gmail.com
I agree with this assessment. Using stock buy-backs to pump your own
stock price and break 1T is shady, and I've never met an actual genius
at a genius bar.
Now back to your regularly scheduled thread...
On 8/31/2018 11:00 AM, Carlos Alvarez wrote:
> Oh, this week I needed help with an Apple issue.? Their call went
> straight to VM.? Turns out TrueCaller has Apple's main national number
> marked as scam/spam.
Aug. 31, 2018
ANIs flagged as telemarketer/spammer/scammer
by ryandelgrosso@gmail.com
So today its mostly reputation scoring aggregators.
The two biggest that come to mind are whitepages.com (they own Hiya) and
NextCaller.
There is some secret sauce, but the scoring algorithm is based on
incoming query volume, LERG lookups, LIDB lookups, and of course user
feedback from the freemium app Hiya which is in wide distribution.
I know nextcaller has some deeper hooks with major providers allowing
them more accurate info (such as correlating an active call on the
owning provider with the call youre dipping about etc), but their focus
isnt SPIT protection, its an enterprise focused product and is priced as
such.
Google (Android) now ships with this in the OS, and I presume they are
leveraging one of these datasources since the call classifications match
my whitepages dips. For network providers doing this, its generally just
an appserver the call passes through that will do the dip, and modify
the call headers for later behavioral changes (or at least that's how I
have built it and seen it implemented). In a freeswitch ecosystem I just
build the dialplan conditionally based upon the dip (so changing PAI or
potentially even punting to VM).
I have reached out to my contact with whitepages.com about how to
contest an inaccurate ranking in the past, and they dont see well
equipped to do much about it yet, BUT in my case it was a newly assigned
number that had been previously used by a bad actor and abandoned. It
righted itself pretty quick when the bad call volumes stopped.
On 8/30/2018 3:27 PM, Alex Balashov wrote:
> Hi,
>
> So, of course, it is a known problem in the legitimate side of the lead
> engagement call centre, survey, etc. business that ANIs get flagged as
> "telemarketer" pretty quickly and start showing up that way on people's
> phones.
>
> Your normative viewpoint on that may vary depending on what you think of
> lead gen calls, but regardless, a reasonable person would differentiate
> between:
>
> (1) Legitimate outbound dialing operations that are following up with
> leads who provided their phone number and agreed to be called (at least,
> as a matter of clicking "accept" on _something_), or for some other
> legitimate mass-dialing purpose, and who actually own the DID inventory
> from which they present local-market ANIs and can in fact be reached on
> those numbers;
>
> (2) Illegal spammers who use fake ANIs and call people who did not in
> any way consent to being called by them.
>
> I am trying to learn a bit more about how this is done and what a
> legitimate, above-board business can do about it.
>
> Ignoring the factor of third-party call-screening apps (which most
> people with a mobile don't use), where is this generally implemented? As
> I understand it, T-Mobile do it on the network level. I have T-Mobile
> myself, and probably 2/3rds of unfamiliar numbers, including quite
> legitimate ones, show up as "Scam Likely" ? I know that's come up on the
> list before. AT&T displays "Telemarketer"; do they do it that way too,
> or do they use a Google Android feature for that which they enable as
> part of their carrier defaults for carrier-issued phones? What about
> other carriers and Android?
>
> As far as I know, Apple don't do anything like this. Do people with
> iPhones just not receive this "service"? How does that work?
>
> Asking where the central, or the most influential authority lies and who
> provides it goes to the heart of the real question, which is: what can a
> legitimate business do if their number has been blacklisted this way? As
> I understand it, the maintainers of these lists, along with the criteria
> for getting on them, are elusive and inscrutable, and there's really no
> recourse and no appeals process. I furthermore understand that this has
> led to the widespread approach of rotating ANIs, but that's a losing
> battle; they get flagged too. I imagine it won't be long before the
> criteria for "Scam Likely" are just "number appears to call lots of
> numbers in this rate centre and otherwise hasn't been around very long".
>
> But this is all just conjecture on my part; I really don't know much
> about how my carrier, anyone's carrier, or some BigCo that's behind my
> mobile OS decides that a call is a "telemarketer" or "scam" call. If
> anyone can shed some light on how this really works and what, if
> anything can be done about it, I would be most appreciative.
>
Aug. 31, 2018
ANIs flagged as telemarketer/spammer/scammer
by caalvarez@gmail.com
I no longer work with telemarketing call centers at all for various
reasons. But I do work with a few who do different kinds of calling. One
in particular is especially challenged by these things, and I've talked to
Alex about building systems to rotate CLID for them regularly. They do
market research. For example, they will call people on behalf of the local
electric company to see how they can improve. Or do followup calls for a
major national medical group after appointments to assure satisfaction. If
you own one of the two major phone brands, they may contact you about
product improvements, overall satisfaction, and the like. Anyway, totally
legit, not sales.
But they MUST reach a person directly. It's not statistically valid
research if you call them back, or if you call them on your own. It's a
lengthy explanation, but basically if they leave a VM and wait for a call
back, the people who choose to call are the most biased. They are most
likely to have either praise or an axe to grind. They will be someone who
has something to say. They also need a balanced view from people who
wouldn't care enough to reach out.
The exact numbers are proprietary, but during a recent experiment on
rotating CLID, we found that production of valid calls went up by just over
triple against the number that had been marked spam/scam. That's no
exaggeration at all.
Oh, this week I needed help with an Apple issue. Their call went straight
to VM. Turns out TrueCaller has Apple's main national number marked as
scam/spam. What the hell people?
I have been saying that these filtering apps will at some point have marked
so many numbers that they will stop being useful. When Apple, who does
zero telemarketing, gets marked like that, it's already here. I've also
received "new" blocks that were already marked in some way.
On Fri, Aug 31, 2018 at 6:24 AM Ivan Kovacevic <
ivan.kovacevic at startelecom.ca> wrote:
> One thing that hasn't happened yet - and it should - is that networks, app
> providers and individual users are held responsible for labels they put
> (or help put) on numbers. Let's remember at least some of the
> telemarketing is conducted by legitimate organizations with valid (and
> legal) existing business relationships. Labeling a legitimate number as
> scam is detrimental to business and I am surprised there hasn't been a
> flurry of cease and desist letters to force carriers to stop doing it or
> at least introduce a validation/vetting mechanism.
>
> If someone posted a Yelp review saying they found rat feet in their
> hamburger, and this wasn't true, Yelp would have to remove this review and
> the restaurant would have legitimate grounds to go after the poster. The
> caller ID "screening" space is still a bit of Wild West... But as Glen
> pointed out, that could be just due to overall drop in interest and
> efficacy of legitimate telemarketing.
>
> Ivan Kovacevic
> www.startelecom.ca
>
>
>
> -----Original Message-----
> From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Alex Balashov
> Sent: August 30, 2018 11:37 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] ANIs flagged as telemarketer/spammer/scammer
>
> I agree with you, but, not running a call centre or a sales or marketing
> operation myself, I am not qualified to assess the business ROI of calling
> people.
>
> It clearly works well though or they wouldn't do it. From what I can see,
> there is widespread agreement that it only works 1) if you get to the lead
> first and 2) if you actually get a warm body on the phone.
>
> Leaving voicemails is seen to be a pointless waste of time from a
> conversion point of view, or in the case of lead gen where multiple
> providers buy the lead info (e.g. say you go to some site that quotes out
> auto insurance policy info and put in your contact details), coming in
> second or worse is also seen to be a pointless waste of time.
>
> On August 30, 2018 10:05:17 PM EDT, Glen Gerhard <glen at cognexus.net>
> wrote:
> >_______________________________________________
> >VoiceOps mailing list
> >VoiceOps at voiceops.org
> >https://puck.nether.net/mailman/listinfo/voiceops
>
> --
> Sent from mobile. Kindly excuse brevity and errors.
> _______________________________________________
> 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.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Aug. 31, 2018
ANIs flagged as telemarketer/spammer/scammer
by ivan.kovacevic@startelecom.ca
One thing that hasn't happened yet - and it should - is that networks, app
providers and individual users are held responsible for labels they put
(or help put) on numbers. Let's remember at least some of the
telemarketing is conducted by legitimate organizations with valid (and
legal) existing business relationships. Labeling a legitimate number as
scam is detrimental to business and I am surprised there hasn't been a
flurry of cease and desist letters to force carriers to stop doing it or
at least introduce a validation/vetting mechanism.
If someone posted a Yelp review saying they found rat feet in their
hamburger, and this wasn't true, Yelp would have to remove this review and
the restaurant would have legitimate grounds to go after the poster. The
caller ID "screening" space is still a bit of Wild West... But as Glen
pointed out, that could be just due to overall drop in interest and
efficacy of legitimate telemarketing.
Ivan Kovacevic
www.startelecom.ca
-----Original Message-----
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Alex Balashov
Sent: August 30, 2018 11:37 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] ANIs flagged as telemarketer/spammer/scammer
I agree with you, but, not running a call centre or a sales or marketing
operation myself, I am not qualified to assess the business ROI of calling
people.
It clearly works well though or they wouldn't do it. From what I can see,
there is widespread agreement that it only works 1) if you get to the lead
first and 2) if you actually get a warm body on the phone.
Leaving voicemails is seen to be a pointless waste of time from a
conversion point of view, or in the case of lead gen where multiple
providers buy the lead info (e.g. say you go to some site that quotes out
auto insurance policy info and put in your contact details), coming in
second or worse is also seen to be a pointless waste of time.
On August 30, 2018 10:05:17 PM EDT, Glen Gerhard <glen at cognexus.net>
wrote:
>_______________________________________________
>VoiceOps mailing list
>VoiceOps at voiceops.org
>https://puck.nether.net/mailman/listinfo/voiceops
--
Sent from mobile. Kindly excuse brevity and errors.
_______________________________________________
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.
Aug. 31, 2018
ANIs flagged as telemarketer/spammer/scammer
by abalashov@evaristesys.com
I agree with you, but, not running a call centre or a sales or marketing operation myself, I am not qualified to assess the business ROI of calling people.
It clearly works well though or they wouldn't do it. From what I can see, there is widespread agreement that it only works 1) if you get to the lead first and 2) if you actually get a warm body on the phone.
Leaving voicemails is seen to be a pointless waste of time from a conversion point of view, or in the case of lead gen where multiple providers buy the lead info (e.g. say you go to some site that quotes out auto insurance policy info and put in your contact details), coming in second or worse is also seen to be a pointless waste of time.
On August 30, 2018 10:05:17 PM EDT, Glen Gerhard <glen at cognexus.net> wrote:
>_______________________________________________
>VoiceOps mailing list
>VoiceOps at voiceops.org
>https://puck.nether.net/mailman/listinfo/voiceops
--
Sent from mobile. Kindly excuse brevity and errors.
Aug. 31, 2018
ANIs flagged as telemarketer/spammer/scammer
by glen@cognexus.net
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20180830/296f3d8d/at…>
Aug. 31, 2018
ANIs flagged as telemarketer/spammer/scammer
by compuwizz@gmail.com
T-Mobile definitely does it on the network level and my iPhone shows Scam
Likely sometimes.
On Thu, Aug 30, 2018 at 4:04 PM Alex Balashov <abalashov at evaristesys.com>
wrote:
> Thanks, David.
>
> Setting aside the question of "how" - I agree with your speculations on
> the "sauce", "where" is it done? Do the US mobile majors do this at the
> network level? Do some of them use Google's service for it, which as I
> understand is baked into the Android Phone app but may not be enabled?
> What about on iDevices?
>
> I'm not really concerned with people who use apps to screen
> telemarketers. They're just not a big factor for me; most people do not
> use these apps. I'm interested in what happens by default without the
> user's intervention.
>
> On Thu, Aug 30, 2018 at 11:00:49PM +0000, Hiers, David wrote:
>
> > Hi Alex,
> > I have no idea how it is actually done, but there are lots of useful
> metrics just lying around that one could use. Things like:
> >
> > The last time a specific terminating number called a specific
> originating number
> > Number of calls
> > Rate of calls
> > Ratio of originated/terminated calls
> > Time of day
> > ASR
> > Call duration
> >
> > Like any kind of dynamic reputation metric (credit score, IP Address
> reputation, credit card fraud detection, etc), I bet the actual
> secret-sauce is pretty closely held. Gotta be some patents in this area,
> though.
> >
> > I'll also bet double that you could come up with a wicked method for
> weeding out the "probably unwanted" calls!
> >
> >
> >
> > David
> >
> >
> >
> > -----Original Message-----
> > From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex
> Balashov
> > Sent: Thursday, August 30, 2018 3:27 PM
> > To: voiceops at voiceops.org
> > Subject: [VoiceOps] ANIs flagged as telemarketer/spammer/scammer
> >
> > Hi,
> >
> > So, of course, it is a known problem in the legitimate side of the lead
> engagement call centre, survey, etc. business that ANIs get flagged as
> "telemarketer" pretty quickly and start showing up that way on people's
> phones.
> >
> > Your normative viewpoint on that may vary depending on what you think of
> lead gen calls, but regardless, a reasonable person would differentiate
> > between:
> >
> > (1) Legitimate outbound dialing operations that are following up with
> leads who provided their phone number and agreed to be called (at least, as
> a matter of clicking "accept" on _something_), or for some other legitimate
> mass-dialing purpose, and who actually own the DID inventory from which
> they present local-market ANIs and can in fact be reached on those numbers;
> >
> > (2) Illegal spammers who use fake ANIs and call people who did not in
> any way consent to being called by them.
> >
> > I am trying to learn a bit more about how this is done and what a
> legitimate, above-board business can do about it.
> >
> > Ignoring the factor of third-party call-screening apps (which most
> people with a mobile don't use), where is this generally implemented? As I
> understand it, T-Mobile do it on the network level. I have T-Mobile myself,
> and probably 2/3rds of unfamiliar numbers, including quite legitimate ones,
> show up as "Scam Likely" ? I know that's come up on the list before. AT&T
> displays "Telemarketer"; do they do it that way too, or do they use a
> Google Android feature for that which they enable as part of their carrier
> defaults for carrier-issued phones? What about other carriers and Android?
> >
> > As far as I know, Apple don't do anything like this. Do people with
> iPhones just not receive this "service"? How does that work?
> >
> > Asking where the central, or the most influential authority lies and who
> provides it goes to the heart of the real question, which is: what can a
> legitimate business do if their number has been blacklisted this way? As I
> understand it, the maintainers of these lists, along with the criteria for
> getting on them, are elusive and inscrutable, and there's really no
> recourse and no appeals process. I furthermore understand that this has led
> to the widespread approach of rotating ANIs, but that's a losing battle;
> they get flagged too. I imagine it won't be long before the criteria for
> "Scam Likely" are just "number appears to call lots of numbers in this rate
> centre and otherwise hasn't been around very long".
> >
> > But this is all just conjecture on my part; I really don't know much
> about how my carrier, anyone's carrier, or some BigCo that's behind my
> mobile OS decides that a call is a "telemarketer" or "scam" call. If anyone
> can shed some light on how this really works and what, if anything can be
> done about it, I would be most appreciative.
> >
> > --
> > Alex Balashov | Principal | Evariste Systems LLC
> >
> > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
> > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
> _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
> >
> > ----------------------------------------------------------------------
> > 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.
>
> --
> Alex Balashov | Principal | Evariste Systems LLC
>
> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Aug. 31, 2018
LNP, tandems, etc.
by voiceops@ics-il.net
*nod* I remember you from the ISP-CLEC mailing list. I probably only lurked on that list, maybe the occasional question.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "BackUP Telecom Consulting" <marylou at backuptelecom.com>
To: "Mike Hammett" <voiceops at ics-il.net>
Cc: "Adam Vocks" <Adam.Vocks at cticomputers.com>, voiceops at voiceops.org
Sent: Thursday, August 30, 2018 1:05:35 PM
Subject: Re: [VoiceOps] LNP, tandems, etc.
Thanks for the vote of confidence Adam! LOL!
Mike......while I do have clients that I do everything for, I never
insist on operating that way because it makes both of us too dependent
on each other. I have a lot of clients that only seek my help from time
to time because they only need help from time to time, so I charge on a
per hour basis for service provided rather than a monthly basis. I've
found what works best for everyone involved is to train my clients on
the tasks that are simple or repetitive and advise / do the work for the
non-repetitive tasks that require more skill / experience. I've been
doing it this way for 18 years and I've never run out of work, so it
works well for everyone involved! If you''re interested feel free to
give me a call! If not, that's okay too.
Mary Lou Carey
BackUP Telecom Consulting
Office: 615-771-7868 (temporary)
Cell: 615-796-1111
On 2018-08-30 09:04 AM, Mike Hammett wrote:
> I'm looking for one part (perhaps even two parts) educational and one
> part get it fixed.
>
> Fixing it could be as simple as not sending sending that traffic to
> that tandem anymore. Easiest and cheapest (unless volume dictates
> otherwise) way, though perhaps not the best. I've also made inquiries
> to Frontier as to what services they have that could help solve this,
> be it some value-add to take it to that tandem for me anyway, a DS1 to
> that other tandem, etc. I've also reached out to others (including
> Centurylink) for quoting out that transport. Probably need some other
> paperwork as well (not sure if we have an ICA with them or not, I'm
> guessing not), but I'm sure they'll tell me what I need to connect
> when I ask to connect.
>
> I'm one of those guys that likes to understand a situation vs.
> outsourcing from the beginning. Sure, outsourcing may end up being the
> best way of implementing it, but I can't just always take everyone at
> their word and then not understand what's going on when things go
> sideways.
>
> The summary seems to be that Comcast did something wrong (or at least
> unconventionally) and now I have to do extra work\expense to work
> around it.
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
> -------------------------
>
> FROM: "Adam Vocks" <Adam.Vocks at cticomputers.com>
> TO: "Mike Hammett" <voiceops at ics-il.net>, paul at timmins.net
> CC: voiceops at voiceops.org
> SENT: Thursday, August 30, 2018 8:04:06 AM
> SUBJECT: RE: [VoiceOps] LNP, tandems, etc.
>
> Hi Mike, if you have money to throw at the problem, I think I'd just
> hire Mary to track down and fix the problem for you. She's obviously
> knowledgeable, probably has enough contacts and is now familiar with
> your problem.
>
> Adam
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of
> Mike
> Hammett
> Sent: Thursday, August 30, 2018 7:17 AM
> To: paul at timmins.net
> Cc: voiceops at voiceops.org
> Subject: Re: [VoiceOps] LNP, tandems, etc.
>
> 1) How do I find an appropriate contact to ask?
> 2) From what Mary has said, Comcast is doing it wrong in my area. I
> suppose it's useful to know how something is SUPPOSED to be done and
> acknowledge that it very well could be very different in production.
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
> ----- Original Message -----
> From: paul at timmins.net
> To: voiceops at ics-il.net, voiceops at voiceops.org,
> marylou at backuptelecom.com
> Cc: voiceops at voiceops.org, marylou at backuptelecom.com
> Sent: Wed, 29 Aug 2018 21:04:33 -0500 (CDT)
> Subject: Re: [VoiceOps] LNP, tandems, etc.
>
> <div dir="auto">The block owner often has a connection to the ILEC
> tandem for their block in that range, but that's not always
> necessary (I don't have any ilec FGD groups in the Chicago LATA,
> so
> it's not universally necessary).<div dir="auto"><br></div><div
> dir="auto">The only way to know for certain is to check the LERG or
> just
> ask the carrier, which is what I usually do because I don't like
> giving money to iconnectiv, since they tend to like to send me legally
> cartoonish Cease and Descists every few years for the last
> decade.</div></div><div class="gmail_extra"><br><div
> class="gmail_quote">On Aug 29, 2018 21:49, Mike Hammett
> <voiceops at ics-il.net> wrote:<br><html><head><style>p
> {
> margin: 0; }</style></head><body><div style="font-family:
> arial,helvetica,sans-serif; font-size: 10pt; color: #000000">So then
> in
> my situation:
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&
> amp;exchange=901<br><br><br>Comcast has 815-901 as
> well as
> 815-901-0. Verizon Wireless has 1k-8k. 9k I guess would be either
> not
> provisioned or default back to Comcast because they have the 10k
> block.
> Because they have the parent 10k block, are they then required to have
> a
> connection to the tandem I'm on anyway? The 1k block I now
> understand could be elsewhere, but the 10k?<br><br>Interesting that
> AT&T U-Verse voice isn't on legacy AT&T
> infrastructure.<br><br><div><span></span><br><br>-----<br>Mike
> Hammett<br>Intelligent Computing
> Solutions<br>http://www.ics-il.com<br><br><br><br>Midwest Internet
> Exchange<br>http://www.midwest-ix.com<br><br><span></span><br></div><br>
> <hr id="zwchr"><div
> style="color:#000;font-weight:normal;font-style:normal;text-decoration:n
> one;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From:
> </b>paul at timmins.net<br><b>To: </b>voiceops at ics-il.net,
> voiceops at voiceops.org, marylou at backuptelecom.com<br><b>Cc:
> </b>voiceops at voiceops.org, marylou at backuptelecom.com<br><b>Sent:
> </b>Wednesday,
> August
> 29, 2018 7:08:15 PM<br><b>Subject: </b>Re: [VoiceOps] LNP, tandems,
> etc.<br><br><div dir="auto">Thousands blocks are basically just a
> fancy
> LNP operation. Your tandem homing has to follow 10k blocks, and the 1k
> blocks are basically mass ported to your LRN. Even if the numbers are
> usually homed a certain way because they are in a ratecenter, they
> won't be in this case because they are ported numbers and supposed
> to be routed to your LRN. Example would be the Detroit LATA where
> there
> are about 6 or so AT&T and other tandems. I'm homed off
> WBFDMIMN20T. The local carrier has local/local toll trunks to me all
> over the place, but all intercarrier calls and out of area calls other
> than local traffic from AT&T LEC comes through my LRN 248-574-7678
> off WBFDMIMN20T. This saves me from having to create FGD trunking
> ports
> to all the other tandems in the region, only the barely used
> local/intra
> trunking from AT&T ILEC, who has moved most customers to their
> uverse VoIP
> affilia
> te here, and those don't use the local/intra trunks either.<div
> dir="auto"><br></div><div dir="auto">It lowers my capex and opex
> having
> potentially over provisioned/underutilized trunking all over the
> place,
> saves numbers and decreases the need for splits and overlays, and even
> saves at&t money. Only people who lose out are ribbon and
> metaswitch
> (and whoever supports at&ts 5ESS and EWSD deployments) on
> licensing
> and support costs for unneeded channels.</div></div><div
> class="gmail_extra"><br><div class="gmail_quote">On Aug 29, 2018
> 19:51,
> Mike Hammett <voiceops at ics-il.net>
> wrote:<br><blockquote><style>p
> { margin: 0; }</style><div style="font-family:
> arial,helvetica,sans-serif; font-size: 10pt; color: #000000"><font
> face="arial, helvetica, sans-serif"><span style="font-size:
> 10pt;">"</span></font><span style="font-family: "Times New
> Roman"; font-size: medium; background-color: rgb(255, 255,
> 255);">they give you market entry without the technic
> al need
> to establish extra homing arrangements that aren't beneficial to
> you."</span><div><br></div><div>Could you elaborate on
> that?<br><br><div style="font-family: arial, helvetica, sans-serif;
> font-size: 10pt;"><span></span><br><br>-----<br>Mike
> Hammett<br>Intelligent Computing
> Solutions<br>http://www.ics-il.com<br><br><br><br>Midwest Internet
> Exchange<br>http://www.midwest-ix.com<br><br><span></span><br></div><br>
> <hr id="zwchr" style="font-family: arial, helvetica, sans-serif;
> font-size: 10pt;"><div style="font-family: Helvetica, Arial,
> sans-serif;
> font-size: 12pt; color: rgb(0, 0, 0); font-weight: normal; font-style:
> normal; text-decoration: none;"><b>From:
> </b>paul at timmins.net<br><b>To:
> </b>marylou at backuptelecom.com, ptimmins at clearrate.com,
> voiceops at voiceops.org<br><b>Cc: </b>voiceops at voiceops.org,
> ptimmins at clearrate.com<br><b>Sent: </b>Wednesday, August 29, 2018
> 6:05:39 PM<br><b>Subject: </b>Re: [VoiceOps] LNP, tandems,
> etc.<br><br><div dir="auto">I've had some i
> nteresti
> ng arguments with other carriers regarding their obligation to
> connect
> to us. Oh, you aren't connected where I'm homed? Go order
> connectivity then.<div dir="auto"><br></div><div dir="auto">They have
> a
> little more power to make demands when you have more than 24 standing
> calls to them, but by and large with these stubborn providers we never
> do, and when they have complained i've given them a location they
> can install 1 way trunks to me at (as I have no desire to terminate
> traffic to them directly), and they always balk and find some other
> way
> of dealing with it because it was all well and good until it was their
> money they were spending instead of mine. The trick ends up being to
> never do 10k blocks when you don't have to. Thousands blocks
> aren't just great for number consolidation, they give you market
> entry without the technical need to establish extra homing
> arrangements
> that aren't beneficial to you. Sure sometimes you're the guy
> who
> has to own
> the 10k
> block, bu<blockquote><p>That's true if the ILEC has an agreement
> with the tandem provider. There
> are some little ILECs that have their own tandem and refuse to use the
>
> big ILEC tandem provider! You have to look at the routing of the ILEC
> switch in the LERG to figure that out.
>
> Mary Lou Carey
>
> BackUP Telecom Consulting
>
> Office: 615-771-7868 (temporary)
>
> Cell: 615-796-1111
>
> On 2018-08-29 11:38 AM, Paul Timmins wrote:
> > You don't actually have to establish connectivity to all
> ILECs
> in an
> > area, even if you are porting out numbers from their ratecenters.
> The
> > ILECs already have to have a way to reach any other tandem in the
> LATA
> > so as long as you have an LRN homed on A tandem in the area, and
> port
> > your numbers to that, you're good to go.
> >
> > The ILECs don't LIKE it, but if we cared what they truly
> liked
> we'd
> > all just leave the market.
> >
> > On Aug 29, 2018 12:33, BackUP Telecom Consulting
> > wrote:
> >
> > When there are multiple ILECs in a LATA like in LA - LATA 730,
> you
> > would
> > set up an interconnection point with each ILEC. So you'd have
> one for
> > the AT&T areas and one for the old Verizon areas. When you
> have
> trunks
> >
> > to both carriers in the LATA, you can use your own network to
> switch
> > traffic from the one LATA to the other LATA, but you can't
> deliver it
> > to
> > the ILEC and expect them to hand it off to the other ILEC. It
> would
> > work
> > the same with the third party providers.......as long as they
> have
> a
> > connection in both ILEC areas, then they can use their own
> network
> to
> > deliver the traffic from the one ILEC area to the other ILEC
> area.
> >
> > Mary Lou Carey
> >
> > BackUP Telecom Consulting
> >
> > Office: 615-771-7868 (temporary)
> >
> > Cell: 615-796-1111
> >
> > On 2018-08-28 08:18 PM, Mike Hammett wrote:
> >> I thought everyone connected to the ILEC-hosted tandem
> responsible
> > for
> >> the rate centers where the number blocks were assigned, but
> that
> > seems
> >> to not always be the case when there are multiple ILEC-hosted
> > tandems
> >> in a LATA.
> >>
> >> -----
> >> Mike Hammett
> >> Intelligent Computing Solutions
> >> http://www.ics-il.com
> >>
> >> Midwest Internet Exchange
> >> http://www.midwest-ix.com
> >>
> >> -------------------------
> >>
> >> FROM: "Erik"
> >> TO: "Mike Hammett"
> >> CC: voiceops at voiceops.org
> >> SENT: Tuesday, August 28, 2018 7:25:40 PM
> >> SUBJECT: Re: [VoiceOps] LNP, tandems, etc.
> >>
> >> Most providers simply connect to the tandem at the ILEC. The
> end
> >> office transit termination and origination cost is SO LOW
> that
> it
> >> doesn't make since to have a switch or access point at
> the
> end
> > office.
> >> Since most things are ILEC if not all are VOIP everything is
> coming
> >> from a centralize switch point. Hopefully all the 1970's
> billing
> >> methods will disappear.
> >>
> >> On Tue, Aug 28, 2018 at 1:00 PM, Mike Hammett
> >> wrote:
> >>
> >>> Meaning if I thought were true? I had just assumed that
> Inteliquent
> >>> did have the connections to every tandem in the LATAs
> they
> serve,
> >>> given that (my thought) that you could only port numbers
> on
> the
> > same
> >>> tandem, so universal coverage would require connections
> to
> every
> >>> tandem. We're actually looking at someone like
> Inteliquent to
> > expand
> >>> our footprint.
> >>>
> >>> So I'm supposed to be connected to every tandem in my
> LATA? In my
> >>> LATA, there are only two (I believe), but some LATAs
> (like
> Chicago)
> >>> have several. I'm supposed to drag a DS1 (or use
> Inteliquent, etc.
> >>> if available) to connect to each one, even if I don't
> provide
> >>> service in the rate centers traditionally served by that
> tandem? It
> >>> seems like Comcast threw a dart at a dart board in
> choosing
> which
> >>> tandem to connect to vs. going with the one that everyone
> else in
> >>> that town uses.
> >>>
> >>> So then I could port a number from any rate center in my
> LATA (say
> >>> Savanna) and point it to my LRN, living off of a tandem
> switch that
> >>> the Savanna ILEC isn't connected to (from my outside
> world
> >>> perspective)? Is there even the LATA constraint? Given
> the
> porting
> >>> limitations I had experienced in the VoIP world, I
> assumed
> it was a
> >>> tandem-by-tandem basis.
> >>>
> >>> So the LERG shows which tandem I need to send traffic to
> if
> I want
> >>> to talk to them, but they could send their outbound calls
> to a
> >>> different tandem? My current customer complaint is for
> calls that
> >>> we're sending to Comcast, apparently homed off of the
> other tandem.
> >>>
> >>> If everyone is supposed to be on every tandem, then why
> can't the
> >>> tandem I'm on just accept the calls I'm sending
> to
> Comcast, since
> >>> Comcast should be there? Obviously me not being on the
> other tandem
> >>> would affect inbound traffic to me.
> >>>
> >>> Is there another service I should be paying Frontier for
> to
> get me
> >>> to the other tandem with some value-add service? I know
> CenturyLink
> >>> hops through almost every town going that way (former
> LightCore and
> >>> others before route). Frontier or CenturyLink may be able
> to get me
> >>> a DS1 to the other tandem if I need that.
> >>>
> >>> I'm aware that I could still be completely missing
> the
> mark.
> >>>
> >>> BTW: Thanks for TelcoData. I subscribed a long time ago,
> but
> > haven't
> >>> for many ages.
> >>>
> >>> -----
> >>> Mike Hammett
> >>> Intelligent Computing Solutions
> >>> http://www.ics-il.com
> >>>
> >>> Midwest Internet Exchange
> >>> http://www.midwest-ix.com
> >>>
> >>> -------------------------
> >>>
> >>> FROM: "Paul Timmins"
> >>> TO: "Mike Hammett"
> >>> CC: voiceops at voiceops.org
> >>> SENT: Tuesday, August 28, 2018 5:19:11 PM
> >>> SUBJECT: Re: [VoiceOps] LNP, tandems, etc.
> >>>
> >>> If that were true, you wouldn't be able to use
> inteliquent (et al)
> >>> as your access tandem. Everyone is supposed to be
> directly
> or
> >>> indirectly connected to every tandem in the LATA (which
> you
> can't
> >>> independently verify, as telcodata and the LERG both show
> >>> terminating tandem information to reach that end office,
> not what
> >>> tandems the end office is hooked to to terminate calls.
> >>>
> >>> On Aug 28, 2018 17:47, Mike Hammett wrote:
> >>>
> >>> I thought you had to be on the same tandem to port a
> number, but
> >>> with what our tandem operator (Frontier) is telling me,
> this isn't
> >>> the case.
> >>>
> >>> Comcast ported a number from us in town A. The LRN they
> pointed to
> >>> is based in town B (per TelcoData). The tandem generally
> used by
> >>> carriers in both towns is based in town B. Naturally, we
> send
> >>> traffic to that tandem.
> >>>
> >>> The operator of that tandem is telling us that the LRN is
> actually
> >>> homed off of a different tandem in our LATA (operated by
> >>> CenturyLink) in town C. Unfortunately, I can't
> corroborate this
> >>> information with TelcoData the only rate center I see off
> of that
> >>> tandem in TelcoData is an AT&T town next door.
> >>>
> >>> Where can I read up authoritatively on the porting
> requirements
> > that
> >>> would apply to this and related bits of info I should
> know?
> >>>
> >>> I'm checking on our LERG access as I know that has
> the
> > authoritative
> >>> information, but I don't have that access at the
> moment. Maybe
> > we're
> >>> not subscribed to it.
> >>>
> >>> Number NPA-NXX in town A:
> >>>
> >>
> >
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&ex
> change=991
> > [1]
> >>>
> >>> LRN NPA-NXX in town B:
> >>>
> >>
> >
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&ex
> change=901
> > [2]
> >>>
> >>> Tandem in town B:
> >>>
> >>
> >
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILX
> A50T
> > [3]
> >>> Tandem in town C:
> >>>
> >>
> >
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILX
> A50T
> > [4]
> >>>
> >>> Thanks.
> >>>
> >>> -----
> >>> Mike Hammett
> >>> Intelligent Computing Solutions
> >>> http://www.ics-il.com
> >>>
> >>> Midwest Internet Exchange
> >>> http://www.midwest-ix.com
> >>>
> >>> _______________________________________________
> >>> VoiceOps mailing list
> >>> VoiceOps at voiceops.org
> >>> https://puck.nether.net/mailman/listinfo/voiceops
> >> _______________________________________________
> >> VoiceOps mailing list
> >> VoiceOps at voiceops.org
> >> https://puck.nether.net/mailman/listinfo/voiceops
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
> >
> >
> > Links:
> > ------
> > [1]
> >
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&ex
> change=991
> > [2]
> >
> https://www.telcodata.us/search-area-code-exchange-detail?npa=815&ex
> change=901
> > [3]
> >
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DKLBILX
> A50T
> > [4]
> >
> https://www.telcodata.us/search-switches-by-tandem-clli?cllicode=DIXNILX
> A50T
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
> </p><br>_______________________________________________<br>
> VoiceOps mailing
> list<br>VoiceOps at voiceops.org<br>https://puck.nether.net/mailman/listinf
> o/voiceops<br></div><br></div></div></div></div>
> </blockquote></div><br></div></div></div></body></html>
> </blockquote></body></html>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 30, 2018
ANIs flagged as telemarketer/spammer/scammer
by abalashov@evaristesys.com
Thanks, David.
Setting aside the question of "how" - I agree with your speculations on
the "sauce", "where" is it done? Do the US mobile majors do this at the
network level? Do some of them use Google's service for it, which as I
understand is baked into the Android Phone app but may not be enabled?
What about on iDevices?
I'm not really concerned with people who use apps to screen
telemarketers. They're just not a big factor for me; most people do not
use these apps. I'm interested in what happens by default without the
user's intervention.
On Thu, Aug 30, 2018 at 11:00:49PM +0000, Hiers, David wrote:
> Hi Alex,
> I have no idea how it is actually done, but there are lots of useful metrics just lying around that one could use. Things like:
>
> The last time a specific terminating number called a specific originating number
> Number of calls
> Rate of calls
> Ratio of originated/terminated calls
> Time of day
> ASR
> Call duration
>
> Like any kind of dynamic reputation metric (credit score, IP Address reputation, credit card fraud detection, etc), I bet the actual secret-sauce is pretty closely held. Gotta be some patents in this area, though.
>
> I'll also bet double that you could come up with a wicked method for weeding out the "probably unwanted" calls!
>
>
>
> David
>
>
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex Balashov
> Sent: Thursday, August 30, 2018 3:27 PM
> To: voiceops at voiceops.org
> Subject: [VoiceOps] ANIs flagged as telemarketer/spammer/scammer
>
> Hi,
>
> So, of course, it is a known problem in the legitimate side of the lead engagement call centre, survey, etc. business that ANIs get flagged as "telemarketer" pretty quickly and start showing up that way on people's phones.
>
> Your normative viewpoint on that may vary depending on what you think of lead gen calls, but regardless, a reasonable person would differentiate
> between:
>
> (1) Legitimate outbound dialing operations that are following up with leads who provided their phone number and agreed to be called (at least, as a matter of clicking "accept" on _something_), or for some other legitimate mass-dialing purpose, and who actually own the DID inventory from which they present local-market ANIs and can in fact be reached on those numbers;
>
> (2) Illegal spammers who use fake ANIs and call people who did not in any way consent to being called by them.
>
> I am trying to learn a bit more about how this is done and what a legitimate, above-board business can do about it.
>
> Ignoring the factor of third-party call-screening apps (which most people with a mobile don't use), where is this generally implemented? As I understand it, T-Mobile do it on the network level. I have T-Mobile myself, and probably 2/3rds of unfamiliar numbers, including quite legitimate ones, show up as "Scam Likely" ? I know that's come up on the list before. AT&T displays "Telemarketer"; do they do it that way too, or do they use a Google Android feature for that which they enable as part of their carrier defaults for carrier-issued phones? What about other carriers and Android?
>
> As far as I know, Apple don't do anything like this. Do people with iPhones just not receive this "service"? How does that work?
>
> Asking where the central, or the most influential authority lies and who provides it goes to the heart of the real question, which is: what can a legitimate business do if their number has been blacklisted this way? As I understand it, the maintainers of these lists, along with the criteria for getting on them, are elusive and inscrutable, and there's really no recourse and no appeals process. I furthermore understand that this has led to the widespread approach of rotating ANIs, but that's a losing battle; they get flagged too. I imagine it won't be long before the criteria for "Scam Likely" are just "number appears to call lots of numbers in this rate centre and otherwise hasn't been around very long".
>
> But this is all just conjecture on my part; I really don't know much about how my carrier, anyone's carrier, or some BigCo that's behind my mobile OS decides that a call is a "telemarketer" or "scam" call. If anyone can shed some light on how this really works and what, if anything can be done about it, I would be most appreciative.
>
> --
> Alex Balashov | Principal | Evariste Systems LLC
>
> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> ----------------------------------------------------------------------
> 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.
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Aug. 30, 2018