Added TOC entries

Finalized Calling SDK and Call end include files, added TOC entries.

Author: vac0224

articles/communication-services/concepts/includes/codes/call-end.md

@@ -24,6 +24,7 @@ Error code details include:
 - Successful responses (**200-299**)
 - Client error (**400-499**)
 - Server error (**500-599**)
+- Global error (**600-699**)
 
 **Subcode** - Are defined as an integer, where each number indicates a unique reason, specific to a group of scenarios or specific scenario outcome.
 
@@ -54,13 +55,6 @@ There are different explanations for why a call ended. Here are the meanings of
 | 540487 | 487 | Call ended successfully as caller canceled the call. | Success | |
 | 560000 | 0 | Call ended successfully by remote PSTN participant. | Success |Possible causes: <br /> - User ended the call. <br /> - Call ended by media agent. |
 | 560486 | 486 | Call ended because remote PSTN participant was busy. The number called was already in a call or having technical issues. |
-
-
-## !Error codes not mentioned above!
-
-
-| SubCode | Code | Message | Result Categories | Advice |
-|--- |--- |--- |--- |--- |
 | | 404 | Call not found. | | Ensure that the number you're calling (or call you're joining) exists. |
 | | 408 | Call controller timed out. | | Call Controller timed out waiting for protocol messages from user endpoints. Ensure clients are connected and available. |
 | | 410 | Local media stack or media infrastructure error. | | Ensure that you're using the latest SDK in a supported environment. |

articles/communication-services/concepts/includes/codes/calling-sdk.md

@@ -24,6 +24,7 @@ Error code details include:
 - Successful responses (**200-299**)
 - Client error (**400-499**)
 - Server error (**500-599**)
+- Global error (**600-699**)
 
 **Subcode** - Are defined as an integer, where each number indicates a unique reason, specific to a group of scenarios or specific scenario outcome.
 
@@ -39,8 +40,8 @@ For client errors, if the resultCategories property is `ExpectedError`, the erro
 |--- |--- |--- |--- |--- |
 | 40101 | 408 | Failed to create CallAgent. Try again, if issue persists, gather browser console logs, `.HAR` file, and contact Azure Communication Services support. | UnexpectedClientError | |
 | 40104 | 408 | Failed to create CallAgent. Try again, if issue persists, gather browser console logs, `.HAR` file, and contact Azure Communication Services support. | UnexpectedClientError | |
-| 40114 | 408 | Failed to connect to Azure Communication Services infrastructure. Try again and check the browser's network requests. If the requests keep failing, gather browser console logs, `.HAR` file, and contact Azure Communication Services support. | UnexpectedClientError | For more information, see [network requirements](../../voice-video-calling/network-requirements.md) for more details. |
-| 40115 | 412 | Failed to create CallAgent, unable to initialize connection to Azure Communication Services infrastructure. Try again and check the browser's network requests. If the requests keep failing, gather browser console logs, `.HAR` file, and contact Azure Communication Services support. | UnexpectedClientError |For more information, see [network requirements](../../voice-video-calling/network-requirements.md) for more details. |
+| 40114 | 408 | Failed to connect to Azure Communication Services infrastructure. Try again and check the browser's network requests. If the requests keep failing, gather browser console logs, `.HAR` file, and contact Azure Communication Services support. | UnexpectedClientError | For more information, see [network requirements](../../voice-video-calling/network-requirements.md). |
+| 40115 | 412 | Failed to create CallAgent, unable to initialize connection to Azure Communication Services infrastructure. Try again and check the browser's network requests. If the requests keep failing, gather browser console logs, `.HAR` file, and contact Azure Communication Services support. | UnexpectedClientError |For more information, see [network requirements](../../voice-video-calling/network-requirements.md). |
 | 40216 | 500 | Failed to create CallAgent. Try again, if issue persists, gather browser console logs and contact Azure Communication Services support. | UnexpectedClientError | |
 | 40228 | 409 | Failed to create CallAgent, an instance of CallAgent associated with this identity already exists. Dispose the existing CallAgent, or create a new one with a different identity. | ExpectedError | |
 | 40230 | 409 | Failed to create TeamsCallAgent, an instance of TeamsCallAgent associated with this identity already exists. Dispose the existing TeamsCallAgent before creating a new one. | ExpectedError | |
@@ -59,7 +60,7 @@ For client errors, if the resultCategories property is `ExpectedError`, the erro
 | 41034 | 500 | Failed to resume the call. Try again, if the issue persists, gather browser console logs and contact Azure Communication Services support. | UnexpectedClientError ||
 | 41035 | 400 | Failed to start screen share, screen share is already started. | ExpectedError | Learn more about [how to start and stop screen sharing while on a call](../../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#start-and-stop-screen-sharing-while-on-a-call) |
 | 41041 | 400 | Failed to stop screen share, screen share is already stopped. | ExpectedError | Learn more about [how to start and stop screen sharing while on a call](../../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#start-and-stop-screen-sharing-while-on-a-call) |
-| 41048 | 410 | Failed to start video during call setup process. Ensure to allow video permissions in the browser's settings and in the OS settings, and ensure the camera device isn't being used by another process. | UnexpectedClientError | - The camera device may be disabled in the system. <br /> - Camera is being used by another process.|
+| 41048 | 410 | Failed to start video during call setup process. Ensure to allow video permissions in the browser's settings and in the OS settings, and ensure the camera device isn't being used by another process. | UnexpectedClientError | - The camera device might be disabled in the system. <br /> - Camera is being used by another process.|
 | 41056 | 412 | Failed to start or join to the call, Teams Enterprise voice policy isn't enabled for this Azure Communication Services resource. Follow the tutorial online to enable it. | ExpectedError | See on [how to enable users for Enterprise Voice online and Phone System Voicemail](/skypeforbusiness/skype-for-business-hybrid-solutions/plan-your-phone-system-cloud-pbx-solution/enable-users-for-enterprise-voice-online-and-phone-system-voicemail) to enable Teams Enterprise voice policy|
 | 41071 | 412 | Failed to start screen share, call isn't in Connected state. Subscribe to the Call's `statteChanged` event to know when the call is connected. | ExpectedError |Helpful links: <br /> - [Check call properties](../../../how-tos/calling-sdk/manage-calls.md?pivots=platform-web#check-call-properties) <br /> - [Subscribe to SDK events](../../../how-tos/calling-sdk/events.md?pivots=platform-web)</li></ul>|
 | 41073 | 412 | Failed to get or set custom MediaStream, this functionality is currently disabled by Azure Communication Services. | ExpectedError ||
@@ -82,16 +83,12 @@ For client errors, if the resultCategories property is `ExpectedError`, the erro
 | 43209 | 405 | Failed to render video stream, VideoStreamRenderer was disposed during initialization process. | ExpectedError ||
 | 43210 | 400 | Failed to dispose VideoStreamRenderer because it's already disposed. | ExpectedError ||
 | 43220 | 400 | Failed to create view, maximum number of active `RemoteVideoStream` views already reached. You can dispose of a previous one in order to create new one. | ExpectedError | Learn more about [how to properly support the best number of incoming video streams](../../troubleshooting-info.md?tabs=csharp%2Cjavascript%2Cdotnet#enable-and-access-call-logs) |
-
-## !Error codes not mentioned above!
-
-The Azure Communication Services Calling SDK uses the following error codes to help you troubleshoot calling issues. 
-
-| SubCode | Code | Message | Result Categories | Advice |
-|--- |--- |--- |--- |--- |
 | | 480 | Remote client endpoint not registered. | | Ensure that the remote endpoint is available. |
 | | 481 | Failed to handle incoming call. | | File a support request through the Azure portal. |
 | | 487 | Call canceled, locally declined, ended due to an endpoint mismatch issue, or failed to generate media offer. | | Expected behavior. |
 | | 490, 491, 496, 497, 498 | Local endpoint network issues. | | Check your network. |
 | | 503, 504 | Communication Services infrastructure error. | | File a support request through the Azure portal. |
-| | 603 | Call globally declined by remote Communication Services participant. | | Expected behavior. |
+| | 600 | Busy everywhere. Participant contacted successfully but returned busy signal. |  | Expected behavior. |
+| | 603 | Call globally declined by remote Communication Services participant. | | Expected behavior. |
+| | 604 | Doesn't exist anywhere. Requested URI doesn't exist. |  | Expected behavior. |
+| | 606 | Not acceptable. Participant successfully contacted but can't support the session described. |  | Expected behavior. |

articles/communication-services/concepts/sms/sms-faq.md

@@ -265,4 +265,4 @@ As with similar Azure services, customers are notified at least 30 days before t
 ## Emergency support
 ### Can a customer use Azure Communication Services for emergency purposes?
 
-Azure Communication Services does not support text-to-911 functionality in the United States, but it’s possible that you may have an obligation to do so under the rules of the Federal Communications Commission (FCC). You should assess whether the FCC’s text-to-911 rules apply to your service or application. To the extent you're covered by these rules, you are responsible for routing 911 text messages to emergency call centers that request them. You're free to determine your own text-to-911 delivery model, but one approach accepted by the FCC involves automatically launching the native dialer on the user’s mobile device to deliver 911 texts through the underlying mobile carrier.
+Azure Communication Services does not support text-to-911 functionality in the United States, but it’s possible that you may have an obligation to do so under the rules of the Federal Communications Commission (FCC). You should assess whether the FCC’s text-to-911 rules apply to your service or application. To the extent you're covered by these rules, you are responsible for routing 911 text messages to emergency call centers that request them. You're free to determine your own text-to-911 delivery model, but one approach accepted by the FCC involves automatically launching the native dialer on the user’s mobile device to deliver 911 texts through the underlying mobile carrier.

articles/communication-services/toc.yml

@@ -789,6 +789,9 @@ items:
       - name: End of Call Survey
         href: concepts/voice-video-calling/end-of-call-survey-concept.md
         displayName: diagnostics, Survey, feedback, quality, reliability, users, end, call, quick
+      - name: Troubleshooting PSTN call failures
+        href: concepts/telephony/troubleshooting-pstn-call-failures.md
+        displayName: diagnostics, Survey, feedback, quality, reliability, call, voip, troubleshooting
       - name: Troubleshooting VoIP call quality
         href: concepts/voice-video-calling/troubleshoot-web-voip-quality.md
         displayName: diagnostics, Survey, feedback, quality, reliability, call, voip, troubleshooting
@@ -1081,6 +1084,10 @@ items:
     href: resources/learn-modules.md
   - name: Troubleshooting Guides
     items:
+    - name: Troubleshooting in Azure Communication Services
+      href: concepts/troubleshooting-info.md
+    - name: Troubleshooting response codes
+      href: concepts/troubleshooting-codes.md
     - name: Voice and Video
       items:
       - name: General troubleshooting strategies