Forum Discussion
Chat to a contact after Reverse Number Lookup not working
Hello together,
I just would like to check if you encounter the same problem as in our case.
Assume the following scenario.
User A - Phone System with direct Routing - +491234
User B - Phone System with direct Routing - +4912345
Both users are in the same company.
User A is calling User B. Instead of calling the contact, User A is calling the number +4912345 in the calling App. Teams UI shows that User A is calling +4912345. Due to the fact das User B is using Phone System, the call will ring on this Teams client and after he accepts the call, the UI will show the contact of the number +4912345 (in this case User B) in the UI.  
When you try to send a chat message in the current call window, this is not possible, as Teams tries to send the chat to the number: +4912345. However sharing your screen is possible.
When you want to send a chat message to User B, you have to go into the Teams Client, search for User B and send a message to him by using this way.
I think this behaviour is a bit strange.
Greets,
Markus
2 Replies
- When dialing the number of another Teams user in the same organization Teams will do a VoIP call instead of a PSTN call. If the second user answer in their Teams client they should be able to add Chat, Video and Screen sharing as in a regular Teams call.
If the second user have forwarded the call to an external number, eg. mobile phone, then it will be a regular PSTN call without chat.
Check in the call logs for the user if you can see how the call is routed.- Markus_95Brass Contributor
LinusCansby thank you very much for your answer. I can confirm that Teams is initiating a VoiP call instead of doing a PSTN call. That is what I was expecting. However, when the other side accepts the call and I write a chat message in the call window to that contact, it will always tries to chat to the number I have dialed in the beginning and not to the user.
Here is an example:
This number is assigned to the user I have called. The user has no forwarding enabled.
For me it seems like that this is a bug.
Greets,
Markus