[cisco-voip] [EXTERNAL] Re: PSTN Calls Incorrectly Flagged as "Potential SPAM"

[Ryan Huff]

That is correct, however, your carrier has far more capabilities to compel other carrier than you do. Just calling 1-800–my-carrier and opening a support ticket probably won’t cut it. It’s a good and likely necessary start, but ultimately, in my experience, things like this with carriers only get solved when you get the money folks (account managers) involved.

No one in the carrier world cares about you till money is involved.

Sent from my iPhone

On Apr 3, 2020, at 13:58, JASON BURWELL <JASON.BURWELL at foundersfcu.com> wrote:


The problem is my carrier says they just deliver the call, its up to the called party end carrier to do the CID Name dip to deliver the CID name, City/State -or- in this case, substitute it with “Potential SPAM” and delver with the call. Which as I understand it, is correct information. On the end carrier side I have spoken with Verizon and AT&T and they basically said there is nothing they can do and pointed the blame to 3rd party app providers which as I said before, I know is not the truth based on my own personal experience. I guess I’ll try to get it escalated at Verizon. I think I have it about up as far as I can with AT&T. Thanks for all the input from everyone.

Jason

From: Ryan Huff <ryanhuff at outlook.com>
Sent: Friday, April 3, 2020 1:52 PM
To: JASON BURWELL <JASON.BURWELL at foundersfcu.com>
Cc: cisco-voip at puck.nether.net
Subject: Re: [EXTERNAL] Re: [cisco-voip] PSTN Calls Incorrectly Flagged as "Potential SPAM"

You need to become a thorn in the side of the AM for your upstream carrier. It’s a carrier -2- carrier fight at that point.
Sent from my iPhone


On Apr 3, 2020, at 13:49, JASON BURWELL <JASON.BURWELL at foundersfcu.com<mailto:JASON.BURWELL at foundersfcu.com>> wrote:

Thanks for all the replies thus far. To answer a couple of the questions that have come up, we are using valid, working DID numbers that we own for all outbound Calling Number Masks. And none of the DIDs forward to other carriers, they are all pointed from the PSTN to our various gateways.

One thing that was mentioned is that a SPAM autodialer bot has at some point spoofed some of our numbers causing them to be flagged as SPAM which is certainly a possibility and nothing we can do about that. I regularly get calls even on my cell phone with the whole “hey I missed a call form you” from the caller and they get irritated when I tell them, sorry I did not call you.

I know there is nothing we can do from a configuration perspective. I was just hoping there was some managed whitelist these carriers used that I was unaware of. I know there are various 3rd party apps that do this but its definitely something being done at the carrier level as well because I frequently get these messages as well on a Verizon phone and I do not have and SPAM apps or subscriptions.

As more and more numbers are spoofed for SPAM calls I imagine at some point all numbers will be flagged at potential SPAM at this rate.

So unless I missed something, it sounds like there is really nothing we can do about it?

Jason



From: Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>>
Sent: Friday, April 3, 2020 12:30 PM
To: JASON BURWELL <JASON.BURWELL at foundersfcu.com<mailto:JASON.BURWELL at foundersfcu.com>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [EXTERNAL] Re: [cisco-voip] PSTN Calls Incorrectly Flagged as "Potential SPAM"

CAUTION: This email originated outside of Founders Federal Credit Union. Do not click links or open attachments unless you recognize the sender and know the content is safe.
________________________________
I’ve seen this happen on my Verizon cell recently. Was very surprised, it was the first time I had ever seen it.

CNAME dips and presentation are done by the called party’s carrier, so there isn’t anything (functionally) the calling party’s PBX can do to influence that. CNAME inserts are done by your upstream carrier, so if something has actually been modified in the CNAME database for your ANI, your upstream carrier would have done it.

The only real actionable thing I think you can do (besides changing your ANI to something else), is what you’ve done. Call your upstream carrier and give them call samples where your call was delivered by the called party’s carrier and masked with incorrect ANI. Let the carriers fight each other on the carrier level.
Sent from my iPhone



On Apr 3, 2020, at 12:13, JASON BURWELL via cisco-voip <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>> wrote:

More and more I have users reporting that their outbound PSTN calls are showing as “Potential SPAM” on called party phones. Its causing some real problems because these are legitimate calls that the customer in many cases has requested but they are ignoring it due to the message and if they don’t have voicemail set up or its full they have the perception we are not returning calls. I’m assuming the Caller ID name in the national Database is being substituted with this message by the wireless carriers. We don’t do any telemarketing so there is no reason why our calls should be flagged with SPAM. I’ve reached out and received little help from Verizon or AT&T. Wondering what other are doing to get numbers “white listed” as I’m sure I’m not the only one facing this. Thanks Jason


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C025b5c5e1ee24bafb68408d7d7e9e664%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637215271894155219&sdata=zqF5YXd0fzzHl21673j6mNrAMpXXNFuSYvppGmscXww%3D&reserved=0<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__nam11.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fpuck.nether.net-252Fmailman-252Flistinfo-252Fcisco-2Dvoip-26data-3D02-257C01-257C-257C75dbe9d323ec40a5edf108d7d7f75e30-257C84df9e7fe9f640afb435aaaaaaaaaaaa-257C1-257C0-257C637215329746893028-26sdata-3DFjAwP9kd4XohrE1D6CDkpWyq5W5u1VuY013TjvtN40U-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3DCrVsPA4meZ6vEtstSPLQqC5izq21_OrN_h8zxKzEuwc%26r%3DcxTKAF4Iaor9PiEwHMcKcEgAJ-ObtwqWBXjTvqngqNk%26m%3DCvj4-Sdyp0PoxAyIHhCZ8vl0yb5_ikyVlOrCX_Pu4xk%26s%3DFmOPKDcLAPBL_fZxIjlzzuDWv_Qt84tFuRC9iLpZtM8%26e%3D&data=02%7C01%7C%7C8912f68b583541d7b4ec08d7d7f8ad06%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637215335363783060&sdata=0slYTPfNpP0atlJnEyWzRUmIf%2F41HFdpKIsUqqjmycE%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200403/991cf908/attachment.htm>