7.1 MS-Diagnostic Public Errors
The following table lists the ms-diagnostics header (section 2.2.1.1) ErrorIds generated by the Lync server for the current release.
|
ErrorId |
Header |
SIP Request, Response |
Reason string |
|
|---|---|---|---|---|
|
0 |
ms-diagnostics |
Response |
Server Internal Error. |
|
|
1 |
ms-diagnostics |
Response |
Service Unavailable. |
|
|
2 |
ms-diagnostics |
Response |
See response code and reason phrase. |
|
|
3 |
ms-diagnostics |
Response |
Invalid forwarding location. |
|
|
4 |
ms-diagnostics |
Response |
Insufficient bandwidth to establish session. Do not attempt re-route. |
|
|
5 |
ms-diagnostics |
Response |
Insufficient bandwidth to establish session. Attempt PSTN re-route. |
|
|
6 |
ms-diagnostics |
Response |
Insufficient bandwidth to establish session. PSTN reroute blocked for caller. |
|
|
15 |
ms-diagnostics |
Response |
Dialog route set update failed. |
|
|
16 |
ms-diagnostics |
Response |
Registration route set update failed. |
|
|
17 |
ms-diagnostics |
Response |
Wait for dialog route set update timed out. |
|
|
21 |
ms-diagnostics |
Response |
Call failed to establish due to a media connectivity failure where one endpoint is of unknown type. |
|
|
22 |
ms-diagnostics |
Response |
Call failed to establish due to a media connectivity failure when both endpoints are internal. |
|
|
23 |
ms-diagnostics |
Response |
Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote. |
|
|
24 |
ms-diagnostics |
Response |
Call failed to establish due to a media connectivity failure when both endpoints are remote. |
|
|
25 |
ms-diagnostics |
Response |
A federated call failed to establish due to a media connectivity failure where both endpoints are internal. |
|
|
26 |
ms-diagnostics |
Response |
A federated call failed to establish due to a media connectivity failure where one endpoint is internal and the other is remote. |
|
|
27 |
ms-diagnostics |
Response |
A federated call failed to establish due to a media connectivity failure where both endpoints are remote. |
|
|
28 |
ms-diagnostics |
Response |
A public service provider call failed to establish due to a media connectivity failure with an internal endpoint. |
|
|
29 |
ms-diagnostics |
Response |
A public service provider call failed to establish due to a media connectivity failure with a remote endpoint. |
|
|
31 |
ms-diagnostics |
Response |
Call terminated on a mid-call media failure where one endpoint is of unknown type. |
|
|
32 |
ms-diagnostics |
Response |
Call terminated on mid-call media failure where both endpoints are internal. |
|
|
33 |
ms-diagnostics |
Response |
Call terminated on a mid-call media failure where one endpoint is internal and the other is remote. |
|
|
34 |
ms-diagnostics |
Response |
Call terminated on a mid-call media failure where both endpoints are remote. |
|
|
35 |
ms-diagnostics |
Response |
Federated call terminated on a mid-call media failure where both endpoints are internal. |
|
|
36 |
ms-diagnostics |
Response |
Federated call terminated on a mid-call media failure where one endpoint is internal and the other is remote. |
|
|
37 |
ms-diagnostics |
Response |
Federated call terminated on a mid-call media failure where both users are remote. |
|
|
38 |
ms-diagnostics |
Response |
Public service provider call terminated on a mid-call media failure with an internal endpoint. |
|
|
39 |
ms-diagnostics |
Response |
Public service provider call terminated on a mid-call media failure with a remote endpoint. |