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

[UC Penguin]

What external phone number mask are you using?

Is it a valid number?

I’ve seen issues with configs that use invalid masks such as 612-000-0000. Carrier will reject the call with busy tone (Comcast).

Another issue that occurs is when a cell phone user calls your DID and is forwarded to another cell carrier. The carrier will either reject the call or display SPAM/SCAM Likely.

There are feature codes to disable this behavior on the called cell phone. For T-Mobile: https://www.t-mobile.com/news/scamblockparty

> On Apr 3, 2020, at 11:13, JASON BURWELL via cisco-voip <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
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200403/25e1d942/attachment.htm>