Merge pull request #286637 from alvin-l-han/main

Adding references to CreateCallFailed event (AA ask)

Author: prmerger-automator[bot]

articles/communication-services/concepts/call-automation/call-automation.md

@@ -147,6 +147,7 @@ The Call Automation events are sent to the web hook callback URI specified when
 | ----------------- | ------------ |
 | CallConnected      | The call has successfully started (when using Answer or Create action) or your application has successfully connected to an ongoing call (when using Connect action)|
 | CallDisconnected       | Your application has been disconnected from the call |
+| CreateCallFailed (in preview)| The call that your application has initiated could not be created |
 | ConnectFailed       | Your application failed to connect to a call (for connect call action only)|
 | CallTransferAccepted         | Transfer action has successfully completed and the transferee is connected to the target participant |
 | CallTransferFailed  | The transfer action has failed  |

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

@@ -166,6 +166,8 @@ The response provides you with CallConnection object that you can use to take fu
 2. `ParticipantsUpdated` event that contains the latest list of participants in the call.
 ![Sequence diagram for placing an outbound call.](media/make-call-flow.png)
 
+In the case where the call fails, you will receive a `CallDisconnected` and `CreateCallFailed` event with error codes for further troubleshooting.
+
 ## Connect to a call (in preview)
 
 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. 

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

@@ -69,7 +69,7 @@ CreateCallEventResult eventResult = await createCallResult.WaitForEventProcessor
 CallConnected returnedEvent = eventResult.SuccessResult;
 ```
 
-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.
+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.
 
 > [!NOTE]
 > If specific timeout was not given when waiting on EventProcessor, it will wait until its default timeout happens. The default timeout is 4 minutes.

articles/communication-services/resources/troubleshooting/voice-video-calling/includes/codes/call-automation-sdk.md

@@ -28,4 +28,5 @@ The following error codes are exposed by the Call Automation SDK.
 | | 500 | Internal server error | | Retry after a delay. If it persists, raise a support ticket. |
 | | 500 | Play Failed | | File a support request through the Azure portal. |
 | | 500 | Recognize Failed | | Check error message and confirm the audio file format is valid (WAV, 16 KHz, Mono). If the file format is valid, file a support request through Azure portal. |
-| | 502 | Bad gateway | | Retry after a delay with a fresh http client. |
+| | 502 | Bad gateway | | Retry after a delay with a fresh http client. |
+| | 503,504 | Communication Services infrastructure error. | | File a support request through the Azure portal. |