Help with Inbound Reverse Number Lookup with Teams Voice

James-2859 5 Reputation points
2023-12-21T04:35:54.9866667+00:00

Hello,

I am currently in the middle of a PoC for Teams Voice, everything is going well. One thing I'd like to get working is Reverse Number Lookup for inbound external calls.

We have a fleet of work mobile phones, these phones are managed by Intune, the phone numbers are stored against user objects in on-prem Active Directory which is then synced to Microsoft Entra.

When one of these mobile phones calls into our teams environment it doesn't seem to do a reverse number lookup and just displays as +61 123 456 789 (external) for the incoming call.

Everything I've read has lead me to assume teams should be doing reverse number look up and trying to map the inbound number to a user or contact but this does not seem to be working:

"Phone System shows the incoming external phone number as the caller ID. If the number is associated with a user or contact in Microsoft Entra ID or a personal contact, the Skype for Business and Teams clients shows the caller ID based on that information. If the phone number isn't in Microsoft Entra ID or a personal contact, the telco-provided display name is shown if it's available."
Source: https://learn.microsoft.com/en-us/microsoftteams/caller-id-policies#inbound-caller-id-options

The phone numbers are stored against the mobile field in active directory and are in E164 format. The incoming calls look identical to how they appear in Entra.

Thanks in advance!

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
10,894 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. James-2859 5 Reputation points
    2023-12-22T02:41:29.44+00:00

    I found my problem, we had the numbers entered into active directory in the format of +61 1 234 567 890
    once we removed the spaces and had the numbers listed in ad/entra as +611234567890 RNL began working.

    1 person found this answer helpful.
    0 comments No comments

  2. Anonymous
    2023-12-21T07:29:59.51+00:00

    Hi @James-2859

    Does every device suffer from the same problem?

    This problem should be caused by the on-prem Active Directory synchronization with Microsoft Entra not being successful, please recheck whether Microsoft Entra has associated the number with the user.

    In the meantime, you can also try adding the number as a contact in Teams to ensure RNL is functioning properly.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.