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.
Graeme Campbell commented
Surely this is just some sort of PAI lookup?
teams looks to only support the CID (e164) component of the PAI. Other systems essentially lookup the CID, and then prefix the CID with the text. Not sure if this can be handled from the SBC level on direct route systems??
Chip C commented
We're getting wrong names displayed because our enterprise pbx lists a single 10-digit caller id for any outbound call, and an arbitrary or random "matching" name from the organization is displayed. The assumption of one-to-one matching of phone numbers to people is flawed. For contact entries where an extension is shown, it should not match the 10-digit number to a particular address book entry.
John Davies commented
As it seems unclear whether this feature is available or not, I've been trying to test it as part of our Business Voice trial in the UK. None of my tests worked yesterday at all. But, having left some test data in Azure AD overnight, it has started working this morning with incoming calls to individuals. So far I have seen an AAD User's Office Phone number match and an AAD Contact's Office Phone match and their names appear on the desktop app pop-up as the calls comes in. The names even appear in Call History and on the Android app. If I make any data changes, these are not taking effect immediately or even within an hour, even including a local AD/Azure AD sync. I don't know why you have to wait so long and what you have to wait for - but bear this delay in mind if you can't get it working.
However I'm not yet seeing RNL names appear on the Teams pop up when incoming calls are routed via a call queue. But I seeing names appear when calls are routed to an individual by the auto attendant after the caller dialled an extension number.
Bryn Palmer commented
Pulling numbers from AzureAD automatically is definitely a need for us and is the only thing holding us back from a full Teams migration. The only entry on the Roadmap (53937) is labeled as Launched Q4 2019 which is also confusing.
please try this guide when creating the contacts:
Does this issue appear only with AAD Contacts or also with outlook Contacts?
Ron Tanner commented
I thought I saw a release note that said the caller name would show in history soon. Still not working although on my iphone I see it.
Claudia Price commented
Thank you! I am getting a lot of complaints about not seeing the caller ID name in the History. It would be nice to see both in the History the caller ID number and the name.
Been two months since the last comment from the MS engineering team. Are there any further updates?
We'd like to look up an incoming call in our database first and display information about the customer! If no information found we next will try look up in a public phone directory and display company name and address from there!
I tried to find a way with Teams and even through Graph API, but there seems no way to hook into an incoming call and get the number! Any information?
Rene Stolte commented
It works with iOS and Android but we are still waiting for the RNL with windows.
Akihiro Kawamura commented
Does this feature release?
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.