Skip to content

Commit aec2f98

Browse files
authored
Update understanding-error-codes.md
1 parent 2fae150 commit aec2f98

File tree

1 file changed

+1
-1
lines changed
  • articles/communication-services/resources/troubleshooting/voice-video-calling/general-troubleshooting-strategies

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ There are different explanations for why a call ended. Here are the meanings of
3939
| 3101 | 410 | Call dropped due to unexpected network problem on the client, please check client's network and retry. | UnxpectedClientError | |
4040
| 3112 | 410 | Call setup failed due to network configuration problem on the client side, please check client's network configuration, and retry. | ExpectedError | |
4141
| 4097 | 0 | Call ended for all users by the meeting organizer. | Success | |
42-
| 4507 | 495 | Call ended as application didn't provide a valid Azure Communication Services token. | UnexpectedClientError |- Please make sure that your application implements token refresh mechanism correctly. |
42+
| 4507 | 495 | Call ended as application didn't provide a valid Azure Communication Services token. | UnexpectedClientError |- Ensure that your application implements token refresh mechanism correctly. |
4343
| 4521 | 0 | Call ended because user disconnected from the call abruptly, this may be a result of a user closing the application that hosted the call, eg a user terminated application, closed browser of browser tab without proper hang-up. | ExpectedError | |
4444
| 5000 | 0 | Call ended for this participant as it was removed from the conversation by another participant. | Success | |
4545
| 5003 | 0 | Call ended successfully, as all callee endpoints declined the call. | Success | |

0 commit comments

Comments
 (0)