Response code consolidation

Moved Troubleshooting codes to Resources, combined all previous codes from Understanding Codes to Calling SDK and Call end include files. Updated TOC

Author: vac0224

articles/communication-services/concepts/includes/codes/call-automation-sdk.md

@@ -14,7 +14,7 @@ ms.service: azure-communication-services
 # Troubleshooting in Azure Communication Services
 <a name="calling-sdk-error-codes"></a>
 
-This document helps you troubleshoot issues that you may experience within your Communication Services solution. If you're troubleshooting SMS, you can [enable delivery reporting with Event Grid](../quickstarts/sms/handle-sms-events.md) to capture SMS delivery details.
+This document helps you troubleshoot issues that you might experience within your Communication Services solution. If you're troubleshooting SMS, you can [enable delivery reporting with Event Grid](../quickstarts/sms/handle-sms-events.md) to capture SMS delivery details.
 
 ## Getting help
 
@@ -328,7 +328,7 @@ You can find your current Teams license using [licenseDetails](/graph/api/resour
 
 ## Related articles
 - [Troubleshooting Azure Communication Services PSTN call failures](./telephony/troubleshooting-pstn-call-failures.md).
-- [Troubleshooting call end response codes for Calling SDK, Call Automation SDK, PSTN, Chat SDK, and SMS SDK](./troubleshooting-codes.md).
+- [Troubleshooting call end response codes for Calling SDK, Call Automation SDK, PSTN, Chat SDK, and SMS SDK](../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md)(./troubleshooting-codes.md).
 - Access logs for [voice and video](./analytics/logs/voice-and-video-logs.md), [chat](./analytics/logs/chat-logs.md), [email](./analytics/logs/email-logs.md), [network traversal](./analytics/logs/network-traversal-logs.md), [recording](./analytics/logs/recording-logs.md), [SMS](./analytics/logs/sms-logs.md) and [call automation](./analytics/logs/call-automation-logs.md).
 - [Metrics](metrics.md).
 - [Service limits](service-limits.md).

articles/communication-services/concepts/troubleshooting-info.md

@@ -41,15 +41,20 @@ There are different explanations for why a call ended. Here are the meanings of
 | 0 | 0 | Call ended successfully by local participant. | Success | |
 | 0 | 487 | Call ended successfully as caller canceled the call. | Success | |
 | 0 | 603 | Call ended successfully as it was declined from callee. | Success | |
+| 3100 | 410 | Call setup failed due to unexpected network problem on the client, please check client's network and retry. | UnxpectedClientError | - Ensure that you're using the latest SDK in a supported environment.<br> |
+| 3101 | 410 | Call dropped due to unexpected network problem on the client, please check client's network and retry. | UnxpectedClientError | |
+| 3112 | 410 |  Call setup failed due to network configuration problem on the client side, please check client's network configuration, and retry. | ExpectedError | |
 | 4097 | 0 | Call ended for all users by the meeting organizer. | Success | |
 | 4507 | 495 | Call ended as application didn't provide valid Azure Communication Services token. | UnexpectedClientError | Ensure that your application implements token refresh mechanism correctly. |
+| 4521 | 0 | Call ended because user disconnected from the call abruptly. This might be caused by a user closing the application that hosted the call, such as a user terminated the application by closing the browser tab without proper hang-up. | ExpectedError | |
 | 5000 | 0 | Call ended for this participant. Participant removed from the conversation by another participant. | Success | |
 | 5003 | 0 | Call ended successfully, as all callee endpoints declined the call. | Success | |
 | 5300 | 0 | Call ended for this participant. Participant removed from the conversation by another participant. | Success | |
 | 7000 | 0 | Call ended by Azure Communication Services platform. | Success | |
 | 10003 | 487 | Call was accepted elsewhere, by another endpoint of this user. | Success | |
 | 10004 | 487 | Call was canceled on timeout, no callee endpoint accepted on time. Ensure that user saw the notification and try to initiate that call again. | ExpectedError | |
 | 10024 | 487 | Call ended successfully. Call declined by all callee endpoints. | Success | - Try to place the call again. |
+| 10057 | 408 | Call failed, callee failed to finalize call setup, most likely callee lost network or terminated the application abruptly. Ensure clients are connected and available. | ExpectedError | |
 | 301005 | 410 | Participant removed from the call by the Azure Communication Services infrastructure due to loss of media connectivity with the same infrastructure. This usually happens if participant leaves the call abruptly or loses network connectivity. If the participant wants to continue the call, they can reconnect. | UnexpectedClientError | Ensure that you're using the latest SDK in a supported environment. |
 | 510403 | 403 | Call ended, previously marked as a spam and now blocked. | ExpectedError | - Ensure that your Communication Services token is valid and not expired. <br />  - Ensure to pass in `AlternateId` in the call options. |
 | 540487 | 487 | Call ended successfully as caller canceled the call. | Success | |

articles/communication-services/resources/troubleshooting/voice-video-calling/general-troubleshooting-strategies/understanding-error-codes.md

@@ -20,12 +20,12 @@ This article describes troubleshooting call end response codes for Calling SDK,
 ## Troubleshooting tips
 
 Consider the following tips when troubleshooting certain issues: 
-- Your application isn't receiving an `IncomingCall Event Grid` event: Make sure the application endpoint is [validated with Event Grid](../../event-grid/webhook-event-delivery.md) when creating an event subscription. The provisioning status for your event subscription is marked as succeeded if the validation was successful. 
+- Your application isn't receiving an `IncomingCall Event Grid` event: Make sure the application endpoint is [validated with Event Grid](../../../../event-grid/webhook-event-delivery.md) when creating an event subscription. The provisioning status for your event subscription is marked as succeeded if the validation was successful. 
 - For error `The field CallbackUri is invalid`: Call Automation doesn't support HTTP endpoints. Make sure the callback URL you provide supports HTTPS.
 - The `PlayAudio` action doesn't play anything: Currently only Wave file (.wav) format is supported for audio files. The audio content in the wave file must be mono (single-channel), 16-bit samples with a 16,000 (16 KHz) sampling rate.
 - Actions on PSTN endpoints aren't working: For `CreateCall`, `Transfer`, `AddParticipant`, and `Redirect` to phone numbers, you need to set the `SourceCallerId` in the action request. Unless you're using direct routing, the source caller ID must be a phone number owned by your Communication Services resource for the action to succeed. 
 
-For more information about issues tracked by the product team, see [Known issues](./known-issues.md).
+For more information about issues tracked by the product team, see [Known issues](../../../concepts/known-issues.md).
 
 > [!NOTE]
 > Message and Result Categories listed in the following tables are in public preview. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
@@ -57,5 +57,5 @@ For more information about issues tracked by the product team, see [Known issues
 
 ## Related articles
 
-- [Troubleshooting in Azure Communication Services](./troubleshooting-info.md)
-- [Troubleshooting Azure Communication Services PSTN call failures](./telephony/troubleshooting-pstn-call-failures.md)
+- [Troubleshooting in Azure Communication Services](../../../concepts/troubleshooting-info.md)
+- [Troubleshooting Azure Communication Services PSTN call failures](../../../concepts/telephony/troubleshooting-pstn-call-failures.md)

articles/communication-services/concepts/includes/codes/call-end.md renamed to articles/communication-services/resources/troubleshooting/voice-video-calling/includes/codes/call-end.md

@@ -1512,7 +1512,7 @@ items:
     - name: Troubleshooting in Azure Communication Services
       href: concepts/troubleshooting-info.md
     - name: Troubleshooting response codes
-      href: concepts/troubleshooting-codes.md
+      href: resources/troubleshooting/voice-video-calling/troubleshooting-codes.md
     - name: Voice and Video
       items:
       - name: General troubleshooting strategies