Skip to content

Commit bff5ae9

Browse files
committed
address comment to add call direction to example scenario
1 parent d071790 commit bff5ae9

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ A key factor in troubleshooting Azure Communication Services PSTN calls is deter
4343

4444
If the `ParticipantEndSubCode` value starts with 560 or 540, it indicates that the user's/operator's SBC generated the response code. This is particularly useful for troubleshooting Direct Routing calls, as the subcode can help determine whether the error is from your SBC or the Microsoft service. A subcode starting with 560 represents an outbound call, while a subcode starting with 540 represents an inbound call. In either case, you should check the SBC logs.
4545

46-
For example, if the `ParticipantEndSubCode` value is `560403`, it means that the SBC generated the final response code, and the SIP response code from the SBC is 403. You should start troubleshooting the calls by checking your SBC logs.
46+
For example, if the `ParticipantEndSubCode` value is `560403`, it means that it was an outbound call, the SBC generated the final response code, and the SIP response code from the SBC was 403. You should start troubleshooting the calls by checking your SBC logs.
4747

4848
For `ParticipantEndSubCode` responses that don't start with 560 or 540, the Microsoft service generated the final response code.
4949

articles/communication-services/resources/troubleshooting/voice-video-calling/includes/codes/pstn.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This section provides troubleshooting information for various combinations of `P
1818

1919
As a general guideline, if the `ParticipantEndSubCode` value starts with 560 or 540, it indicates that the user's/operator's SBC generated the response code. This is particularly useful for troubleshooting Direct Routing calls, as the subcode can help determine whether the error is from your SBC or the Microsoft service. A subcode starting with 560 represents an outbound call, while a subcode starting with 540 represents an inbound call. In either case, you should check the SBC logs.
2020

21-
For example, if the `ParticipantEndSubCode` value is `560403`, it means that the SBC generated the final response code, and the SIP response code from the SBC is 403. You should start troubleshooting the calls by checking your SBC logs.
21+
For example, if the `ParticipantEndSubCode` value is `560403`, it means that it was an outbound call, the SBC generated the final response code, and the SIP response code from the SBC was 403. You should start troubleshooting the calls by checking your SBC logs.
2222

2323
For `ParticipantEndSubCode` responses that don't start with 560 or 540, the Microsoft service generated the final response code.
2424

0 commit comments

Comments
 (0)