With new Calling experience in Microsoft Teams and Direct Route settings, incoming calls from on-premises PBX and Microsoft Teams shows "Spam Likely" in call history - even though caller ID is a valid 4-digit number. This is working with Teams client that did not updated to new Calling experience. Is there a way to turn off "Spam Likely" in Teams via Policy?

Erik365Online, I used the information from your blog to disable the feature and now calls are incoming calls are showing normal. I enable it and it happens again. I also opened a case with Microsoft and they told me they could not provide more information on what SIP header they are using for that classification.

Just a follow up here, I got a ticket open with Microsoft and off course got a level 1 engineer who doesn't have a clue and he even said I know more than the guy.... so disappointed... Now waiting for another more Senior Engineer to pickup the ticket and see what they say. Almost 48 hours and haven't even got the right Engineer to look a this...

Hi Wilson007, Is this still ongoing or could it be fixed with the Microsoft Support?You might check the Teams Calling Policy to disable it now or later, did you already see and read that Microsoft plans to rollout spam call notifications for Teams which seems to be the "feature" you are already having and experiencing. I wrote an article about it: https://erik365.blog/2021/08/15/microsoft-teams-spam-call-notifications/ also covering the Teams Calling Policy parameters to enable/disable it, e.g globally with Set-CsTeamsCallingPolicy -Identity Global -SpamFilteringEnabledType "Disabled"

Good to hear.Like you, I'm also waiting on some more details (in the documentation) on the spam call notification behavior and process in regards on how a call is marked as spam, e.g. based on what evidence and data.

kshah1999 hi im calling thru teams. The people I am calling are saying I didnt want to answer the phone because it says "SPAM..." I am missing out on a lot of opportunity due to the people I am calling not answering the phone because it shows SPAM. What can I do to prevent the "SPAM" from showing up when I dial numbers.Thank youScott

Microsoft Teams Incoming call via Direct Route shows "Spam Likely" for 4-digit extension

scott950
Copper Contributor
Apr 24, 2023
kshah1999

hi im calling thru teams. The people I am calling are saying I didnt want to answer the phone because it says "SPAM..." I am missing out on a lot of opportunity due to the people I am calling not answering the phone because it shows SPAM.
What can I do to prevent the "SPAM" from showing up when I dial numbers.
Thank you
Scott
- kml75
  Copper Contributor
  Oct 25, 2023
  Hey scott950 did you finally find a workaround? We're encountering the same issue on our side.
  Many thanks!
  
  kml
Erik365Online
Steel Contributor
Apr 07, 2021
I'd claim that this additional info comes with SIP from the PBX or PSTN provider as SIP Header From Display Name. Or you user contact object, saved in Outlook if it affects only a single user.

I think you cannot change this in Teams neither via Shell nor TAC.
You could check your SBC for Teams Direct Routing and configure message manipulations to remove this info in legit calls.
Or you might better ask your pstn sip trunk provider/pbx admin which is connected to your SBC to ask if they use some sort of spam call information tagging. Maybe your provider could turn it off on your pstn sip trunk. Otherwise you usually could do this on your SBC.
- Wilson007
  Copper Contributor
  Apr 30, 2021
  I have verified this and the SBC is not sending any special information. It seems MS Teams client only accepts E.164 format as calling number which is wrong because it should allow internal extensions not to be labeled as "Spam Likely" Microsoft needs to find a solution to this. Customers are not happy about it.Erik365Online
  - Erik365Online
    Steel Contributor
    May 01, 2021
    Wilson007please check out the Microsoft Teams specifications for SIP etc. There are requirements named which must be satisfied to make it work properly.
    
    Phone System Direct Routing - Microsoft Teams | Microsoft Docs
    The SIP sent to Teams should be "clean" and comply with the specifications. In my deployments with coexistence I always sent E.164 from a SBC to Teams an no shortend numbers.
    For reverse number lookup, and correct displayed numbers for call backs you could configure a SBC contact lookup based on ldap/http or else depending on what your SBC is capable of. Furthermore, you could configure Teams dial plans for users to enable short dials, e.g. Site 1 3digits or else.

Forum Discussion

Microsoft Teams Incoming call via Direct Route shows "Spam Likely" for 4-digit extension

Share

Resources