Skip to content

Commit eb0c86a

Browse files
authored
Update handle-events-with-event-processor.md
removing link
1 parent 77923c5 commit eb0c86a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/communication-services/how-tos/call-automation/handle-events-with-event-processor.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ CreateCallEventResult eventResult = await createCallResult.WaitForEventProcessor
6969
CallConnected returnedEvent = eventResult.SuccessResult;
7070
```
7171

72-
With EventProcessor, we can easily wait CallConnected event until the call is established. If the call was never established (that is, callee never picked up the phone), it throws Timeout Exception. If the creation of the call otherwise fails, you will receive the `CallDisconnected` and `CreateCallFailed` events with error codes to further troubleshoot (see [here](../../resources/troubleshooting/voice-video-calling/includes/codes/call-automation-sdk.md) for a list of Call Automation error codes).
72+
With EventProcessor, we can easily wait CallConnected event until the call is established. If the call was never established (that is, callee never picked up the phone), it throws Timeout Exception. If the creation of the call otherwise fails, you will receive the `CallDisconnected` and `CreateCallFailed` events with error codes to further troubleshoot.
7373

7474
> [!NOTE]
7575
> If specific timeout was not given when waiting on EventProcessor, it will wait until its default timeout happens. The default timeout is 4 minutes.

0 commit comments

Comments
 (0)