You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/how-tos/calling-sdk/includes/manage-calls/manage-calls-windows.md
+11-10Lines changed: 11 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,16 +9,17 @@ ms.author: rifox
9
9
10
10
### Request access to the microphone
11
11
12
-
The app will require access to the microphone to run properly. In UWP apps, the microphone capability should be declared in the app manifest file.
13
-
he following steps exemplify how to achieve that.
12
+
The app requires access to the microphone to run properly. In UWP apps, the microphone capability should be declared in the app manifest file.
13
+
14
+
The following steps exemplify how to achieve that.
14
15
15
16
1. In the `Solution Explorer` panel, double click on the file with `.appxmanifest` extension.
16
17
2. Click on the `Capabilities` tab.
17
18
3. Select the `Microphone` check box from the capabilities list.
18
19
19
20
### Create UI buttons to place and hang up the call
20
21
21
-
This simple sample app will contain two buttons. One for placing the call and another to hang up a placed call.
22
+
This simple sample app contains two buttons. One for placing the call and another to hang up a placed call.
22
23
The following steps exemplify how to add these buttons to the app.
23
24
24
25
1. In the `Solution Explorer` panel, double click on the file named `MainPage.xaml` for UWP, or `MainWindows.xaml` for WinUI 3.
@@ -46,14 +47,14 @@ using Azure.Communication;
46
47
usingAzure.Communication.Calling;
47
48
```
48
49
49
-
Please keep`MainPage.xaml.cs` or `MainWindows.xaml.cs` open. The next steps will add more code to it.
50
+
Keep`MainPage.xaml.cs` or `MainWindows.xaml.cs` open. The next steps will add more code to it.
50
51
51
52
## Allow app interactions
52
53
53
54
The UI buttons previously added need to operate on top of a placed `Call`. It means that a `Call` data member should be added to the `MainPage` or `MainWindow` class.
54
55
Additionally, to allow the asynchronous operation creating `CallAgent` to succeed, a `CallAgent` data member should also be added to the same class.
55
56
56
-
Please add the following data members to the `MainPage` pr `MainWindow` class:
57
+
Add the following data members to the `MainPage` pr `MainWindow` class:
57
58
```csharp
58
59
CallAgentcallAgent;
59
60
Callcall;
@@ -91,7 +92,7 @@ The following classes and interfaces handle some of the major features of the Az
91
92
92
93
## Initialize the CallAgent
93
94
94
-
To create a `CallAgent` instance from `CallClient` you must use `CallClient.CreateCallAgent` method that asynchronously returns a `CallAgent` object once it is initialized.
95
+
To create a `CallAgent` instance from `CallClient`, you must use `CallClient.CreateCallAgent` method that asynchronously returns a `CallAgent` object once it's initialized.
95
96
96
97
To create `CallAgent`, you must pass a `CommunicationTokenCredential` object and a `CallAgentOptions` object. Keep in mind that `CommunicationTokenCredential` throws if a malformed token is passed.
97
98
@@ -110,11 +111,11 @@ var callAgentOptions = new CallAgentOptions()
`<AUTHENTICATION_TOKEN>`must be replaced by a valid credential token for your resource. Refer to the [user access token](../../../../quickstarts/identity/access-tokens.md) documentation if a credential token has to be sourced.
114
+
Change the `<AUTHENTICATION_TOKEN>`with a valid credential token for your resource. Refer to the [user access token](../../../../quickstarts/identity/access-tokens.md) documentation if a credential token has to be sourced.
114
115
115
116
## Create CallAgent and place a call
116
117
117
-
The objects needed for creating a `CallAgent` are now ready. It is time to asynchronously create `CallAgent` and place a call.
118
+
The objects needed for creating a `CallAgent` are now ready. It's time to asynchronously create `CallAgent` and place a call.
118
119
119
120
The following code should be added after handling the exception from the previous step.
Make sure Visual Studio will build the app for `x64`, `x86` or `ARM64`, then hit `F5` to start running the app. After that, click on the `Call` button to place a call to the callee defined.
148
+
Make sure Visual Studio builds the app for `x64`, `x86` or `ARM64`, then hit `F5` to start running the app. After that, click on the `Call` button to place a call to the callee defined.
148
149
149
-
Keep in mind that the first time the app runs, the system will prompt user for granting access to the microphone.
150
+
Keep in mind that the first time the app runs, the system prompts user for granting access to the microphone.
Copy file name to clipboardExpand all lines: articles/communication-services/overview.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Azure Communication Services supports various communication formats:
24
24
-[SMS](concepts/sms/concepts.md)
25
25
-[Email](concepts/email/email-overview.md)
26
26
27
-
You can connect custom client apps, custom services, and the publicly switched telephony network (PSTN) to your communications experience. You can acquire [phone numbers](./concepts/telephony/plan-solution.md) directly through Azure Communication Services REST APIs, SDKs, or the Azure portal; and use these numbers for SMS or calling applications or you can simply integrate email capabilities to your applications using production-ready email SDKs. Azure Communication Services [direct routing](./concepts/telephony/plan-solution.md) allows you to use SIP and session border controllers to connect your own PSTN carriers and bring your own phone numbers.
27
+
You can connect custom client apps, custom services, and the publicly switched telephony network (PSTN) to your communications experience. You can acquire [phone numbers](./concepts/telephony/plan-solution.md) directly through Azure Communication Services REST APIs, SDKs, or the Azure portal; and use these numbers for SMS or calling applications or you can integrate email capabilities to your applications using production-ready email SDKs. Azure Communication Services [direct routing](./concepts/telephony/plan-solution.md) allows you to use SIP and session border controllers to connect your own PSTN carriers and bring your own phone numbers.
28
28
29
29
In addition to REST APIs, [Azure Communication Services client libraries](./concepts/sdk-options.md) are available for various platforms and languages, including Web browsers (JavaScript), iOS (Swift), Android (Java), Windows (.NET). A [UI library](./concepts/ui-library/ui-library-overview.md) can accelerate development for Web, iOS, and Android apps. Azure Communication Services is identity agnostic and you control how end users are identified and authenticated.
30
30
@@ -33,7 +33,7 @@ Scenarios for Azure Communication Services include:
33
33
-**Business to Consumer (B2C).** Employees and services engage external customers using voice, video, and text chat in browser and native apps. An organization can send and receive SMS messages, or [operate an interactive voice response system (IVR)](https://github.com/microsoft/botframework-telephony/blob/main/EnableTelephony.md) using a phone number you acquire through Azure. [Integration with Microsoft Teams](./quickstarts/voice-video-calling/get-started-teams-interop.md) can be used to connect consumers to Teams meetings hosted by employees; ideal for remote healthcare, banking, and product support scenarios where employees might already be familiar with Teams.
34
34
-**Consumer to Consumer (C2C).** Build engaging consumer-to-consumer interaction with voice, video, and rich text chat. Any type of user interface can be built on Azure Communication Services SDKs, or use complete application samples and an open-source UI toolkit to help you get started quickly.
35
35
36
-
To learn more, check out our [Microsoft Mechanics video](https://www.youtube.com/watch?v=apBX7ASurgM) or the resources linked below.
36
+
To learn more, check out our [Microsoft Mechanics video](https://www.youtube.com/watch?v=apBX7ASurgM) or the resources linked next.
37
37
38
38
## Common scenarios
39
39
@@ -43,19 +43,19 @@ To learn more, check out our [Microsoft Mechanics video](https://www.youtube.com
43
43
|--- |--- |
44
44
|**[Create a Communication Services resource](./quickstarts/create-communication-resource.md)**|Begin using Azure Communication Services by using the Azure portal or Communication Services SDK to provision your first Communication Services resource. Once you have your Communication Services resource connection string, you can provision your first user access tokens.|
45
45
|**[Get a phone number](./quickstarts/telephony/get-phone-number.md)**|Use Azure Communication Services to provision and release telephone numbers. These telephone numbers can be used to initiate or receive phone calls and build SMS solutions.|
46
-
|**[Send an SMS from your app](./quickstarts/sms/send.md)**| Azure Communication Services SMS REST APIs and SDKs is used send and receive SMS messages from service applications.|
47
-
|**[Send an Email from your app](./quickstarts/email/send-email.md)**| Azure Communication Services Email REST APIs and SDKs is used send an email messages from service applications.|
46
+
|**[Send an SMS from your app](./quickstarts/sms/send.md)**| Azure Communication Services SMS REST APIs and SDKs are used to send and receive SMS messages from service applications.|
47
+
|**[Send an Email from your app](./quickstarts/email/send-email.md)**| Azure Communication Services Email REST APIs and SDKs are used to send email messages from service applications.|
48
48
49
49
After creating a Communication Services resource you can start building client scenarios, such as voice and video calling or text chat:
50
50
51
51
| Resource |Description |
52
52
|--- |--- |
53
53
|**[Create your first user access token](./quickstarts/identity/access-tokens.md)**|User access tokens authenticate clients against your Azure Communication Services resource. These tokens are provisioned and reissued using Communication Services Identity APIs and SDKs.|
54
54
|**[Get started with voice and video calling](./quickstarts/voice-video-calling/getting-started-with-calling.md)**| Azure Communication Services allows you to add voice and video calling to your browser or native apps using the Calling SDK. |
55
-
|**[Add telephony calling to your app](./quickstarts/telephony/pstn-call.md)**|With Azure Communication Services you can add telephony calling capabilities to your application.|
55
+
|**[Add telephony calling to your app](./quickstarts/telephony/pstn-call.md)**|With Azure Communication Services, you can add telephony calling capabilities to your application.|
56
56
|**[Join your calling app to a Teams meeting](./quickstarts/voice-video-calling/get-started-teams-interop.md)**|Azure Communication Services can be used to build custom meeting experiences that interact with Microsoft Teams. Users of your Communication Services solution(s) can interact with Teams participants over voice, video, chat, and screen sharing.|
57
57
|**[Get started with chat](./quickstarts/chat/get-started.md)**|The Azure Communication Services Chat SDK is used to add rich real-time text chat into your applications.|
58
-
|**[Connect a Microsoft Bot to a phone number](https://github.com/microsoft/botframework-telephony)**|Telephony channel is a channel in Microsoft Bot Framework that enables the bot to interact with users over the phone. It leverages the power of Microsoft Bot Framework combined with the Azure Communication Services and the Azure Speech Services. |
58
+
|**[Connect a Microsoft Bot to a phone number](https://github.com/microsoft/botframework-telephony)**|Telephony channel is a channel in Microsoft Bot Framework that enables the bot to interact with users over the phone. It uses the power of Microsoft Bot Framework combined with the Azure Communication Services and the Azure Speech Services. |
59
59
|**[Add visual communication experiences](https://aka.ms/acsstorybook)**| The UI Library for Azure Communication Services enables you to easily add rich, visual communication experiences to your applications for both calling and chat. |
60
60
61
61
## Samples
@@ -72,7 +72,7 @@ The following samples demonstrate end-to-end usage of the Azure Communication Se
72
72
73
73
## Platforms and SDK libraries
74
74
75
-
Learn more about the Azure Communication Services SDKs with the resources below. REST APIs are available for most functionality if you want to build your own clients or otherwise access the service over the Internet.
75
+
Learn more about the Azure Communication Services SDKs with the resources listed next. REST APIs are available for most functionality if you want to build your own clients or otherwise access the service over the Internet.
76
76
77
77
| Resource | Description |
78
78
|--- |--- |
@@ -89,9 +89,9 @@ Find comprehensive components, composites, and UX guidance in the [UI Library De
89
89
90
90
## Other Microsoft Communication Services
91
91
92
-
There are two other Microsoft communication products you may consider using that are not directly interoperable with Communication Services at this time:
92
+
There are two other Microsoft communication products you may consider using, these products aren't directly interoperable with Communication Services at this time:
93
93
94
-
-[Microsoft Graph Cloud Communication APIs](/graph/cloud-communications-concept-overview) allow organizations to build communication experiences tied to Azure Active Directory users with Microsoft 365 licenses. This is ideal for applications tied to Azure Active Directory or where you want to extend productivity experiences in Microsoft Teams. There are also APIs to build applications and customization within the [Teams experience.](/microsoftteams/platform/?preserve-view=true&view=msteams-client-js-latest)
94
+
-[Microsoft Graph Cloud Communication APIs](/graph/cloud-communications-concept-overview) allow organizations to build communication experiences tied to Azure Active Directory users with Microsoft 365 licenses. This workflow is ideal for applications tied to Azure Active Directory or where you want to extend productivity experiences in Microsoft Teams. There are also APIs to build applications and customization within the [Teams experience.](/microsoftteams/platform/?preserve-view=true&view=msteams-client-js-latest)
95
95
96
96
-[Azure PlayFab Party](/gaming/playfab/features/multiplayer/networking/) simplifies adding low-latency chat and data communication to games. While you can power gaming chat and networking systems with Communication Services, PlayFab is a tailored option and free on Xbox.
0 commit comments