PSTN Reverse Number Lookup (show username from Address book not PSTN number) in Teams Toast and Call History
When a PSTN user calls you on Microsoft Teams, if the number is in the address book I would like to be presented with the users name on the toast, not just the PSTN number. The same for call history or anywhere else a PSTN number appears in the client
Just following up to let you know we are making progress on this feature and will post when we have more news to share.
Akihiro Kawamura commented
Does this feature release?
[Deleted User] commented
Still awaiting this solution.
When our PABX user calls a Teams user via Ribbon SBC Direct Route, the toast popup shows the CNAM (based on SIP INVITE FROM field), but in the Teams call history, it just shows numbers. We have modified the Telephone field for all AD users to include the full E.164 phone number, which is synching to Azure AD. But Teams fails to lookup the number against Azure AD in order to find the user display name. So from a Call History perspective, RNL is still not working.
We absolutely need Teams to show DisplayName instead of phone number in the Call-History page.
Thanks for your recent update Alex. Looks like Microsoft is working on this specifically.
Azure AD Contact List resolution is a MUST as we have to move from Skype to Teams and this feature is urgently necessary - also adding a CTI Interface to spawn external applications for recognized numbers or users.
Also, in the current Teams client, it truncates the phone number even when there is room to display it all in the column, see attached screenshot. This doesn't make any sense! This is on a Surface Pro, in case it is a scaling issue with these high resolution screens.
Any update? Really need this for user acceptance.
Thomas Dähler commented
On our Tenant the reverse Number Lookup with AAD is working. But only when someone is calling (messageBox). In the call history it still shown only the number.....without name....
Do I have to do anything to make this work? I'm still getting number only; all numbers are properly detailed in (on-prem) AD/Azure AD.
When a user or guest joins a meeting by phone, they are asked for their name. Their name is announced as soon as they are allowed into the meeting. However, their display name on the call remains as the telephone number which they dialled in from.
It would be great if Speech recognition could be used to recognise the announced name and then change the phone number to the announced name.
This would be really helpful when there are a large number of participants on a call.
Today when users dial into a conference call from their landline or Mobile phone, the Number which the user dialled in from is displayed and the user is added to the lobby.
It would be good if Teams performed a lookup against Active Directory, and if the number that the user is dialling from is associated against an AD account, then the name of the User of the Account is displayed along with in brackets a Symbol of a phone to represent that they are dialling in from a phone.
Also the user can then be automatically admitted as they would now be an authenticated user.
Enjoying CNAM & Azure AD contacts now.
But… sometime in September you took away the history for calling queues in the desktop client! Why? Mobile client on Android still shows calling queue in history.
Yes, CNAM is suppose to be included:
Are you also working on showing CNAM when Outlook/AD contacts are unavailable?
Martin Jensen commented
If we enter an extension (4-digit) number, we get the correct E.164 number (with help from normalization rules). However, we do not get the corresponding Display Name from the GAL, only contacts from the current users Outlook contact store are displayed.
When staff call from direct routing connected PBX ,Teams should be able to resolve the number to name from AD/AAD/Exchange Global Addressbook.
Peter Cermak commented
Please we need this!
Mike Pietrorazio commented
Definitely need Reverse Number Lookup in Teams
David Zeidler commented
It's a shame how Microsoft trades business users, which rely on their phone systems. To cancel a must have features is like writing a text in word without being able to format it.
Maybe Microsoft should get back to reality. Yes, there are companys in the world which still using phones and want to know how is calling them.
Jens Timmermans commented
I will not migrate to Teams until we can see who's calling like we can in Skype for Business that use caller recognition from the GAL. I will definitely switch to another PBX in the cloud like 3CX if Skype for business gets dropped without this feature being implemented in Teams.