7.2 SipStack

The following table lists the SipStack ErrorIds, numbered 1000 – 1999, generated by the Lync front-end server and Access Edge Server for the current release.

ErrorId	Header	SIP Request, Response	Reason string
1000	ms-diagnostics	Response	Final handshake failed.
1001	ms-diagnostics	Response	From URI not authorized to communicate with public IM providers.
1002	ms-diagnostics	Response	From URI not authorized to communicate with federated partners.
1003	ms-diagnostics	Response	User does not exist.
1004	ms-diagnostics	Response	Route set is no longer valid.
1005	ms-diagnostics	Response	Cannot route to destination domain.
1006	ms-diagnostics	Response	Error routing on client connection.
1007	ms-diagnostics	Response	Temporarily cannot route.
1008	ms-diagnostics	Response	Unable to resolve DNS SRV record.
1009	ms-diagnostics	Response	Conflicting SRV and host domains in DNS.
1010	ms-diagnostics	Response	Certificate trust with next-hop server could not be established.
1011	ms-diagnostics	Response	ms-diagnostics header not provided by previous hop.
1012	ms-diagnostics	Response	From URI is not authorized to communicate with users outside the enterprise.
1013	ms-diagnostics	Response	Significant time skew detected during authentication.
1014	ms-diagnostics	Response	Unable to resolve DNS A record.
1015	ms-diagnostics	Response	Cannot route from message source domain.
1016	ms-diagnostics	Response	Message asserted domain traffic type does not match source domain.
1017	ms-diagnostics	Response	Cannot route From and To domains in this combination.
1018	ms-diagnostics	Response	Parsing failure.
1019	ms-diagnostics	Response	Referred-By header parameters are not valid.
1020	ms-diagnostics	Response	Identity of the referrer could not be verified with the ms-identity parameter.
1021	ms-diagnostics	Response	Integrity of the referrer information could not be verified with the ms-identity-cookie parameter.
1022	ms-diagnostics	Response	Cannot process routing destination.
1023	ms-diagnostics	Response	The destination domain of the message resolved to a peer of an incompatible type.
1024	ms-diagnostics	Response	Message boss (on-behalf-of) domain traffic type does not match source domain.
1025	ms-diagnostics	Response	Allowed partner domain resolved by DNS SRV to a fully qualified domain name (FQDN) that matches a different routing rule.
1026	ms-diagnostics	Response	Domain resolved by DNS SRV to multiple fully qualified domain names (FQDN) that match different routing rules.
1027	ms-diagnostics	Response	Cannot route this type of SIP request to or from federated partners.
1028	ms-diagnostics	Response	Domain resolved by DNS SRV to a configured hosting service but the domain is not in the allow list.
1029	ms-diagnostics	Response	There is no configured route to process message destined to the enterprise edge.
1030	ms-diagnostics	Response	The destination in the edge route did not match any configured server and cannot be used for Request URI routing.
1031	ms-diagnostics	Response	The server could not contact the authentication authority (DC).
1032	ms-diagnostics	Response	Message diversion user domain traffic type does not match To user domain.
1033	ms-diagnostics	Response	Previous hop server component did not report diagnostic information.
1034	ms-diagnostics	Response	Previous hop federated peer did not report diagnostic information.
1035	ms-diagnostics	Response	Previous hop public IM provider did not report diagnostic information.
1036	ms-diagnostics	Response	Previous hop shared address space peer did not report diagnostic information.
1037	ms-diagnostics	Response	Previous hop client did not report diagnostic information.
1038	ms-diagnostics	Response	Failed to connect to a peer server .
1039	ms-diagnostics	Response	Failed to complete TLS negotiation with a peer server .
1040	ms-diagnostics	Response	Connection to a peer server failed.
1041	ms-diagnostics	Response	Peer server pool is out of service.
1042	ms-diagnostics	Response	Failed to connect to the local Edge Server.
1043	ms-diagnostics	Response	Failed to complete TLS negotiation with the local Edge Server.
1044	ms-diagnostics	Response	Connection to the local Edge Server failed.
1045	ms-diagnostics	Response	Local Edge Server pool is out of service.
1046	ms-diagnostics	Response	Failed to connect to a federated peer server .
1047	ms-diagnostics	Response	Failed to complete TLS negotiation with a federated peer server .
1048	ms-diagnostics	Response	Connection to a federated peer server failed.
1049	ms-diagnostics	Response	Federated peer server pool is out of service.
1050	ms-diagnostics	Response	Failed to connect to a public IM provider.
1051	ms-diagnostics	Response	Failed to complete TLS negotiation with a public IM provider.
1052	ms-diagnostics	Response	Connection to a public IM provider failed.
1053	ms-diagnostics	Response	Public IM provider is out of service.
1054	ms-diagnostics	Response	Failed to connect to a shared address space federated peer server .
1055	ms-diagnostics	Response	Failed to complete TLS negotiation with a shared address space federated peer server .
1056	ms-diagnostics	Response	Connection to a shared address space federated peer server failed.
1057	ms-diagnostics	Response	Shared address space federated peer is out of service.
1058	ms-diagnostics	Response	Error routing on remote client connection.
1059	ms-diagnostics	Response	Cannot route anonymous user to or from federated partner.
1060	ms-diagnostics	Response	Remote user client access is disabled.
1061	ms-diagnostics	Response	Anonymous user client access is disabled.
1062	ms-diagnostics	Response	Anonymous user domain cannot be routed to or from a federated partner.
1063	ms-diagnostics	Response	Cannot route to blocked IM Service Provider.
1064	ms-diagnostics	Response	Cannot route to blocked domain.
1065	ms-diagnostics	Response	Federation is disabled.
1066	ms-diagnostics	Response	Shared address space routing is disabled.
1067	ms-diagnostics	Response	Invalid status code present in response from untrusted source.
1068	ms-diagnostics	Response	Port is configured for health monitoring only.
1069	ms-diagnostics	Response	From URI not authorized for audio-video communication with federated partners.
1070	ms-diagnostics	Response	To URI not authorized for audio-video communication with federated partners.
1071	ms-diagnostics	Response	Error in shared address space configuration caused a routing loop at the local deployment edge.
1072	ms-diagnostics	Response	User not homed in this forest.
1073	ms-diagnostics	Response	Identity of the referred user (referee) could not be verified.
1074	ms-diagnostics	Response	Domain not hosted by this service.
1076	ms-diagnostics	Response	Protocol Stack Telemetry data.
1077	ms-diagnostics	Response	Frequent connectivity failures to federated partner.
1078	ms-diagnostics	Response	Request exceeded the Max-Forwards limit.
1079	ms-diagnostics	Response	The capabilities exchange request was refused.