Forum Discussion
Microsoft Teams Incoming call via Direct Route shows "Spam Likely" for 4-digit extension
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 vali...
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.
Well this was working just fine until "New calling experience" was rolled out in the latest Teams client version. You have to keep in mind that Direct Routing is not just meant to connect to the PSTN but also to be able to seamlessly communicate to on premise PBX systems which more often than not are not configured for E164 format. I use Cisco CUBE for most implementations which is very simple to configure and I do follow to the T the Cisco and Microsoft configuration guide so I'm not trying to reinvent the wheel here. What I need is for Microsoft to find a way to let 4 or 5 digits in the calling number come across the Teams client without any Spam Likely label which in my opinion is absurd. I know I can manipulate the digits in the CUBE and force an E164 number appear in the Teams client but that defeats the purpose because customers don't want to see the full number for their own business reasons. Believe me, I've tried persuading customers into E164 format but not all like the idea, specially when it interferes with business processes. Spam Likely labeling should be optional like a policy in my humble opinion. Erik365Online
- 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"
- 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.
- Maybe you should open a Microsoft Support (and/or Cisco support) case for further analysis if this was working before the updated calling expierence rolled out in that tenant.