Skip to content

Commit a5fa69a

Browse files
authored
Merge pull request #178405 from tomkau/master
Updates to ad hoc interop
2 parents 53b35b4 + 9d6e07d commit a5fa69a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/communication-services/concepts/interop/calling-chat.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,11 +50,11 @@ const call = callAgent.startCall([teamsCallee]);
5050
**Limitations and known issues**
5151
- Teams users must be in "TeamsOnly" mode. Skype for Business users can't receive 1:1 calls from Communication Services users.
5252
- Escalation to a group call isn't supported.
53-
- Communication Services users are not displayed correctly in the Call history
5453
- Communication Services call recording isn't available for 1:1 calls.
5554
- Advanced call routing capabilities such as call forwarding, group call pickup, simulring, and voice mail are not supported.
5655
- Teams users can't set Communication Services users as forwarding/transfer targets.
57-
- LyncIpPhone fork is not supported.
56+
- There are a number of features in the Teams client that do not work as expected during 1:1 calls with Communication Services users.
57+
- Third party [devices for Teams](/MicrosoftTeams/devices/teams-ip-phones) are not supported.
5858

5959
## Chat
6060
With the Chat SDK, Communication Services users or endpoints can start 1:n chat with Teams users, identified by their Azure Active Directory (AAD) object ID. You can easily modify an existing application that creates chats with other Communication Services users, to instead create chats with Teams users:

0 commit comments

Comments
 (0)