CNAME dips are done by the called party carrier. Nothing you can do to change that other than change the calling party ANI or work with the calling/called party carrier to correct the database entry.
Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: cisco-voip <cisco-voip-boun...@puck.nether.net> on behalf of JASON BURWELL via cisco-voip <cisco-voip@puck.nether.net> Sent: Saturday, March 27, 2021 9:53:09 PM To: Kent Roberts <k...@fredf.org> Cc: cisco-voip@puck.nether.net <cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] [EXTERNAL] Re: Issue with Legit DIDs Flagged as "Potential SPAM" I’m having the same issue with a couple of the TFNs as well. Jason On Mar 27, 2021, at 9:44 PM, Kent Roberts <k...@fredf.org> wrote: 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. ________________________________ What if you send TF number, instead of a DID? On Mar 27, 2021, at 6:49 PM, JASON BURWELL via cisco-voip <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>> wrote: Hello All, An issue has come up again and I was hoping maybe someone here had delt with it and possibly had some advice. More and more, the DID numbers we send out as calling party number are being flagged as “Possible SPAM” or other types of “Probable SPAM” messages with the mobile phone carriers. As a result customers wont answer the call. These are legitimate customer calls and not any kind of cold calling or telemarketing. I took this up with Verizon and AT&T reps last year and got a lot of excuses and basically they told me there is no way to “whitelist” list numbers, the systems use some kind of AI processing to decide what calls to flag. So the issue has come up again because customers are requesting callback and when we call them back sometimes its flagged as possible SPAM so they don’t answer the call. Has anyone else found a way to deal with this? Hopefully once STIR/SHAKEN is fully implemented, they will stop doing this but until then its causing us quite a bit of headache. Thanks Jason _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip%26d%3DDwMFaQ%26c%3DCrVsPA4meZ6vEtstSPLQqC5izq21_OrN_h8zxKzEuwc%26r%3DcxTKAF4Iaor9PiEwHMcKcEgAJ-ObtwqWBXjTvqngqNk%26m%3DN7jXXUnOO2ej1jPjiQ6vD7r0zDNgZxT4GHCgZjACWKU%26s%3DDl0xYtGWR018UfYmZ62xzvOfvDX5AbWFfS9ObwtVkfA%26e%3D&data=04%7C01%7C%7C0bf5dd589a4c48af9e6e08d8f18c808b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637524933238146672%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9GgJlV2UZmhrScFAnOuoeyO6Qxb%2B6%2F5P%2Bw7AMDRZe6c%3D&reserved=0>
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
