Skip to content

Commit a7bf280

Browse files
authored
simplified language
1 parent c06d95c commit a7bf280

File tree

1 file changed

+4
-40
lines changed

1 file changed

+4
-40
lines changed

articles/communication-services/how-tos/call-automation/actions-for-call-control.md

Lines changed: 4 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -167,10 +167,9 @@ The response provides you with CallConnection object that you can use to take fu
167167
![Sequence diagram for placing an outbound call.](media/make-call-flow.png)
168168

169169
## Connect to a call
170+
Connect action enables your service to establish a connection with an ongoing call and take actions on it. This is useful to manage a Rooms call or when client applications started a 1:1 or group call that Call automation isn't part of. Connection is established using the CallLocator property and can be of types: ServerCallLocator, GroupCallLocator, and RoomCallLocator. These IDs can be found when the call is originally established or a Room is created, and also published as part of [CallStarted](./../../../event-grid/communication-services-voice-video-events.md#microsoftcommunicationcallstarted) event.
170171

171-
Connect action enables your service to join an ongoing call to manage it and perform actions. Connection is established using the CallLocator property and can be of types: ServerCallLocator, GroupCallLocator, and RoomCallLocator.
172-
173-
ServerCallLocator takes the serverCallId and can be used to connect to any 1:1 or group call.
172+
To connect to any 1:1 or group call, use the ServerCallLocator. If you started a call using GroupCallId, you can also use the GroupCallLocator.
174173
### [csharp](#tab/csharp)
175174

176175
```csharp
@@ -205,41 +204,6 @@ call_connection_properties = client.connect_call(call_locator=server_call_locato
205204

206205
-----
207206

208-
GroupCallLocator takes a GroupCallId - this is relevant when a call was created using GroupCallId in the first place.
209-
### [csharp](#tab/csharp)
210-
211-
```csharp
212-
Uri callbackUri = new Uri("https://<myendpoint>/Events"); //the callback endpoint where you want to receive subsequent events
213-
CallLocator groupCallLocator = new GroupCallLocator("<GroupCallId>");
214-
ConnctCallResult response = await client.ConnectAsync(groupCallLocator, callbackUri);
215-
```
216-
217-
### [Java](#tab/java)
218-
219-
```java
220-
String callbackUri = "https://<myendpoint>/Events"; //the callback endpoint where you want to receive subsequent events
221-
CallLocator groupCallLocator = new GroupCallLocator("<GroupCallId>");
222-
ConnectCallResult response = client.connectCall(groupCallLocator, callbackUri).block();
223-
```
224-
225-
### [JavaScript](#tab/javascript)
226-
227-
```javascript
228-
const callbackUri = "https://<myendpoint>/Events"; // the callback endpoint where you want to receive subsequent events
229-
const groupCallLocator = { kind: "groupCallLocator", id: "<groupCallId>" };
230-
const response = await client.connectCall(groupCallLocator, callbackUri);
231-
```
232-
233-
### [Python](#tab/python)
234-
235-
```python
236-
callback_uri = "https://<myendpoint>/Events" # the callback endpoint where you want to receive subsequent events
237-
group_call_locator = GroupCallLocator("<group_call_id>")
238-
call_connection_properties = client.connect_call(call_locator=group_call_locator, callback_url=callback_uri)
239-
```
240-
241-
-----
242-
243207
To connect to a Rooms call, use RoomCallLocator which takes RoomId.
244208
### [csharp](#tab/csharp)
245209

@@ -278,8 +242,8 @@ call_connection_properties = client.connect_call(call_locator=room_call_locator,
278242
A successful response provides you with CallConnection object that you can use to take further actions on this call. Two events are published to the callback endpoint you provided earlier:
279243
1. `CallConnected` event notifying that you successfully connect to the call.
280244
2. `ParticipantsUpdated` event that contains the latest list of participants in the call.
281-
282-
Failure to connect to the call results in ConnectFailed event.
245+
246+
At any point after a successful connection, if your service is disconnected from this call you will be notified via a CallDisconected event. Failure to connect to the call in the first place results in ConnectFailed event.
283247

284248
![Sequence diagram for connecting to call.](media/connect-call-flow.png)
285249

0 commit comments

Comments
 (0)