MS-Diagnostic ID reference page


MS-Diagnostic ID reference page


Diagnostic ID
Reason
Potential Resolution
23
Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote
This could indicate a network error or Audio/Video Edge service connectivity issues.
24
Call failed to establish due to a media connectivity failure when both endpoints are remote
This could indicate a network error or Audio/Video Edge service connectivity issues.
33
Call terminated on a mid-call media failure where one endpoint is internal and the other is remote
This could indicate configuration issues with the Audio/Video Edge service.
34
Call terminated on a mid-call media failure where both endpoints are remote.
This indicates that there was a connectivity issue between the two users. Validate connectivity between the two users.
1001
From URI not authorized to communicate with public IM providers.
Assign this user an external access policy that allows public Internet connectivity (EnablePublicCloudAccess parameter).
1002
From URI not authorized to communicate with federated partners.
Assign this user an external access policy that allows federation (EnableFederationAccess parameter).
1010
Certificate trust with next hop server couldn’t be established.
This points to a Certificate issue; check certificate trust and certificate name entries.
1012
From URI isn’t authorized to communicate with users outside the enterprise.
User isn’t enabled for federation or public IM.
1042
Failed to connect to the local Edge Server.
Connectivity issue with the Edge Server. Verify the server is online and configured correctly.
1043
Failed to complete TLS negotiation with the local Edge Server.
There is a certificate/FQDN mismatch on the Edge Server.
1046
Failed to connect to a federated peer server.
Validate connectivity to the federated partner server.
1047
Failed to complete TLS negotiation with a federated peer server.
Certificate issue, check trust and FQDN.
1048
Connection to a federated peer server failed.
Validate connectivity to the federated partner server.
1049
Federated peer server pool is out of service.
Contact the partner and validate the peer server is online.
1050
Failed to connect to a public IM provider.
Validate connectivity to the public IM provider federation gateway.
1051
Failed to complete the TLS negotiation with a public IM provider.
There is a certificate negotiation error between the Edge Server and the public IM provider federation gateway. Validate certificate trusts and certificate name entries.
1052
Connection to a public IM provider failed.
Validate connectivity to the public IM provider federation gateway.
1053
Public IM provider is out of service.
Contact the public IM provider to verify the federation service is online.
1058
An error occurred routing the remote client connection.
Connectivity has been lost by the remote client. Connection will be retried, if it fails, validate client connectivity to the Edge Server.
1060
Remote user client access is disabled.
Remote access is disabled on the server. Enable remote access on the server.
1065
Federation is disabled.
Federation disabled on Access Edge service, correct with Set-CsAccessEdgeConfiguration.
4003
From URI not enabled for remote access.
Remote Access is disabled for this user. Assign this user an external access policy that allows remote access (use the EnableOutsideAccess parameter).
7001
NAT/Firewall traversal service is not available.
Check connectivity between the A/V Conferencing Server and the Audio/Video Edge service.
9000
Request is malformed.
The remote client request is malformed; use tracing for additional information.
9001
Request is too large
The client request is too large; no resolution.
9002
Internal server error
Check the Lync event log for additional information.
9004
Server busy
The server is over-capacity; validate server capacity.
9005
Timeout
The connection to the MRAS service has timed out; validate connectivity to the Edge Server.
9006
Request is forbidden
Could be a spoofing attempt; use tracing for additional information.
9008
Version not supported
The (remote) client version isn’t supported.
9009
Other failure
None.
9010
Unsupported message type
Only SIP SERVICE requests are allowed.
9011
Unsupported content type
None.
9012
Draining
An administrator has prevented new connections.
27000
To-Uri Domain isn’t in the sender-tenant allow list.
Add the domain to the allow list on the sending side, New-CsAllowedDomain.
27001
To-Uri Domain is blocked by sender-tenant block list.
Domain is on the block list on the sender side.
27002
From-Uri Domain isn’t in the receiver-tenant allow list.
Add the domain to the allow list on the receiving side, New-CsAllowedDomain.
27003
From-Uri Domain is blocked by receiver-tenant block list.
Domain is on the block list on the receiving side.

Advertisements

About Paul B

My name is Paul Bloem and I am employed at Lexel Systems in New Zealand as a Principal Consultant for Unified Communications. I have been working on enterprise voice solutions for over 20 years. My first 10 years were spent working for a Telco in South Africa (Telcom SA). This is where all the groundwork happened as I was exposed to just about every aspect of telecommunication you could imagine. I develop an interest in PBX technologies and eventually became the go-to guy. Next, I had a 10 year run at Siemens South Africa, most of my time there was as a Technical Trainer. During this time VoIP hit the world stage, I had the privilege of introducing VoIP both as H.323 and later SIP across the Siemens HiPath 4000 solution stack. In 2008 I immigrated to New Zealand with my newly attained MCSE, I was ready to go where no PBX Techie had gone before. I was employed to explore OCS 2007 and that was pretty much the beginning of the end for me. I have been working on OCS and Lync ever since. My current role focuses exclusively on Lync and associated technologies.. That includes pre-sales, consulting, architecture and design, training and support. I even get to play in the development space from time to time - focus on play ;-) I was nominated as a Microsoft VTSP for Lync early in 2013 and also awarded Microsoft's MVP award for Lync in 2014.
This entry was posted in MS-Diagnostic ID reference page. Bookmark the permalink.

One Response to MS-Diagnostic ID reference page

  1. Pingback: Skype for Business – The effects of Packet Inspection | Mark Vale's Blog

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s