Combined codes

Combined troubleshooting codes.

Author: vac0224

articles/communication-services/concepts/telephony/troubleshooting-pstn-call-failures.md

@@ -13,7 +13,7 @@ localization_priority: Normal
 ---
 # Troubleshooting Azure Communication Services PSTN call failures
 
-When troubleshooting Azure Communication Services PSTN call failures, we recommended that you [enable logging](../analytics/enable-logging.md). Then you can use `ResultCategories`, `ParticipantEndReason`, and `ParticipantEndSubReason` values to determine why an individual call ended and whether the system detected any failures.
+When troubleshooting Azure Communication Services PSTN call failures, we recommended that you [enable logging](../analytics/enable-logging.md). Then you can use `ResultCategories`, `ParticipantEndReason`, and `ParticipantEndSubCode` values to determine why an individual call ended and whether the system detected any failures.
 
 ## Using ResultCategories to troubleshoot PSTN call failures
 
@@ -28,27 +28,27 @@ General reasons that a call ended:
 
 This information can help developers determine why a call ended without generating a detailed error log.
 
-If this level of detail isn't sufficient, then developers can use `ParticipantEndReason` and `ParticipantEndSubReason` to understand the reasons for call end in greater detail. For more information, see the next section.
+If this level of detail isn't sufficient, then developers can use `ParticipantEndReason` and `ParticipantEndSubCode` to understand the reasons for call end in greater detail. For more information, see the next section.
 
-## Using ParticipantEndReason and ParticipantEndSubReason to troubleshoot PSTN call failures
+## Using ParticipantEndReason and ParticipantEndSubCode to troubleshoot PSTN call failures
 
-The `ParticipantEndReason` and `ParticipantEndSubReason` are properties of the [Call summary log schema](../analytics/logs/voice-and-video-logs.md#call-summary-log-schema) and provide more details about why the call ended.
+The `ParticipantEndReason` and `ParticipantEndSubCode` are properties of the [Call summary log schema](../analytics/logs/voice-and-video-logs.md#call-summary-log-schema) and provide more details about why the call ended.
 
 When you're troubleshooting PSTN calls, use these two properties to understand why the call ended as follows:
 
 - **`ParticipantEndReason`**: A three-digit code that shows the general call status. This code explains why the call ended, and groups failures by category. For example, `ParticipantEndReason 404` tells us that caller/callee wasn't found, `ParticipantEndReason 500` means that a service error occurred, and so on. This code is based on the SIP response codes. For more information, see Wikipedia's [List of SIP response codes](https://en.wikipedia.org/wiki/List_of_SIP_response_codes).
 
-- **`ParticipantEndSubReason`** : A more specific response code, usually six digits long, that explains in greater detail why there was a problem with the call.
+- **`ParticipantEndSubCode`** : A more specific response code, usually six digits long, that explains in greater detail why there was a problem with the call.
 
-## Understanding the ParticipantEndSubReason codes relationship
+## Understanding the ParticipantEndSubCode relationship
 
-A key factor in troubleshooting Azure Communication Services PSTN calls is determining whether the final response code for the call comes from a Microsoft process or the users/operators Session Border Controller (SBC). An easy way to determine where the code originated is to look at the `ParticipantEndSubReason` response code.
+A key factor in troubleshooting Azure Communication Services PSTN calls is determining whether the final response code for the call comes from a Microsoft process or the users/operators Session Border Controller (SBC). An easy way to determine where the code originated is to look at the `ParticipantEndSubCode` response.
 
-If the `ParticipantEndSubReason` starts with **560**, it indicates that the response code is generated by the users/operators Session Border Controller (SBC), so developers should check their SBC configuration.
+If the `ParticipantEndSubCode` starts with **560**, it indicates that the response code is generated by the users/operators Session Border Controller (SBC), so developers should check their SBC configuration.
 
-- For example, if the `ParticipantEndSubReason` is **560403**, it means that the final response code is generated by the SBC, and the last three digits indicate SIP response code **403**. In this case, a developer should start troubleshooting the calls using the SBC logs.
+- For example, if the `ParticipantEndSubCode` is **560403**, it means that the final response code is generated by the SBC, and the last three digits indicate SIP response code **403**. In this case, a developer should start troubleshooting the calls using the SBC logs.
 
-For all other `ParticipantEndSubReason` codes that don't start with **560**, the final response code is generated by a Microsoft service.
+For all other `ParticipantEndSubCode` responses that don't start with **560**, the final response code is generated by a Microsoft service.
 
 ## Detailed information on individual error codes