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/quickstarts/telephony/includes/call-automation/redirect-pstn-call-csharp.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ ms.author: askaur
24
24
25
25
## Configure an Event Grid subscription
26
26
27
-
Call Automation uses Event Grid to deliver the `IncomingCall` event to a subscription of your choice. For this guide, we will use a web hook subscription pointing to your NGROK application proxy address.
27
+
Call Automation uses Event Grid to deliver the `IncomingCall` event to a subscription of your choice. For this guide, we'll use a web hook subscription pointing to your NGROK application proxy address.
28
28
29
29
1. Locate and copy the following to be used in the `armclient` command-line statement below:
30
30
- Azure subscription ID
@@ -41,10 +41,10 @@ Call Automation uses Event Grid to deliver the `IncomingCall` event to a subscri
This will produce a public URI you can use to receive the events from the Event Grid subscription.
45
-
5. Optional: Determine an API route path for the incoming call event together with your NGROK URI which will be used in the armclient command-line statement below, for example: `https://ff2f-75-155-253-232.ngrok.io/api/incomingcall`.
44
+
This command will produce a public URI you can use to receive the events from the Event Grid subscription.
45
+
5. Optional: Determine an API route path for the incoming call event together with your NGROK URI, which will be used in the armclient command-line statement below, for example: `https://ff2f-75-155-253-232.ngrok.io/api/incomingcall`.
46
46
6. Event Grid web hooks require a valid reachable endpoint before they can be created. As such, start your web service application and run the commands below.
47
-
7. Since the `IncomingCall` event is not yet published in the portal, you must run the following command-line statements to configure your subscription:
47
+
7. Since the `IncomingCall` event isn't yet published in the portal, you must run the following command-line statements to configure your subscription:
48
48
49
49
```console
50
50
armclient login
@@ -62,7 +62,7 @@ In the console window of your operating system, use the `dotnet` command to crea
62
62
63
63
## Install the NuGet package
64
64
65
-
During the preview phase the NuGet package can be obtained by configuring your package manager to use the [Azure SDK Dev Feed](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md#nuget-package-dev-feed)
65
+
During the preview phase, the NuGet package can be obtained by configuring your package manager to use the [Azure SDK Dev Feed](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md#nuget-package-dev-feed)
66
66
67
67
Obtain your connection string and configure your application
68
68
@@ -122,4 +122,4 @@ app.Run();
122
122
2. Your Event Grid subscription to the IncomingCall should execute and call your web server.
123
123
3. The call will be redirected to the endpoint(s) you specified in your application.
124
124
125
-
Since this call flow involves a redirected call instead of answering it, pre-call web hook callbacks to notify your application the other endpoint accepted the call are not published.
125
+
Since this call flow involves a redirected call instead of answering it, pre-call web hook callbacks to notify your application the other endpoint accepted the call aren't published.
0 commit comments