Forum Discussion
Reverse Number Lookup for outgoing calls
- Jul 16, 2021Hi Markus,
Reverse Number Look up only works when the users are enabled on the Microsoft PBX as the Teams Client searches for the number look up in the PBX not in AAD
Now the reason why you are seeing the Local PBX users name and phone number into your teams client is because you have the user Phone Number and Contact Number saved into your contacts. It is not working as a Reverse Number Lookup. It is searching the Phone Number in your Teams Directory and displaying the name associated with it.
In both the cases your calls are always getting routed via PSTN only in the current set up.
With Regards,
Satish U
Reverse Number Look up only works when the users are enabled on the Microsoft PBX as the Teams Client searches for the number look up in the PBX not in AAD
Now the reason why you are seeing the Local PBX users name and phone number into your teams client is because you have the user Phone Number and Contact Number saved into your contacts. It is not working as a Reverse Number Lookup. It is searching the Phone Number in your Teams Directory and displaying the name associated with it.
In both the cases your calls are always getting routed via PSTN only in the current set up.
With Regards,
Satish U
thank you for your answer.
Just to make sure, that I understood it the correct way.
In case I initiate a call to a PSTN Number, Teams will check, if this number is assigned to one enabled "Teams PBX" user, correct? So it will not use the AAD for RNL. In case the number is associated with an enabled Teams User, it will show the correct contact otherwise, it will only show the PSTN number.
Thanks and greets,
Markus
- DanWeberFeb 17, 2022Copper Contributor
Markus_95, @Satish2085
My experience has been that outgoing phone calls placed from Microsoft Teams will always perform a reverse number lookup against phone numbers in AAD to attempt to match a user. If a match is found, a Teams call will be placed to that user rather than attempting PSTN or Direct Routing call. This has caused us issues as many users have the same office 'main number' assigned to their account in AD.- Andylau-TeamsMay 23, 2022Copper ContributorI did some tests in my environment. I have two kinds of users in my AAD: 1) User enabled Teams enterprise voice and the phone number in AAD is the same as the phone number provisioned in Teams.(e.g. +85213579 for User A). 2) User with a phone number in AAD which is the phone number from 3rd party PBX (+8522468 for User B).
Whatever I make Teams inbound or outbound calls, only the phone number provisioned in Teams enterprise voice could be matched while the phone number for 3rd party PBX did not match. i.e. when i dial +85213579, Teams client could match with User A; when I dial +8522468, Teams client just dial out the +8522468 and show the number only but not showing the name of User B...
Seems like Teams do RNL for Teams phone number only but not the AAD?- Markus_95May 26, 2022Brass Contributor
Hi,
yes that is exactly the behaviour I am also facing. Seems like, that Teams is only doing the RNL in ougoing calls against the Teams internal phone system "adressbook" which only contains Teams users with enterprise voice enabled... I think there is defintely place for improvement. In Skype for Business this was not a problem at all. Due to the fact that the phone numbers of a user are also shown in his teams contact, even if they are hosted on a third party PBX, why is it not possible to show the name when you are doing an outgoing call to their number.. The assocciation betweenn user and number is already there.Hopefully Microsoft will take this into consideration for the future.
Greets,
Markus